[Kernel-packages] [Bug 1511844] Re: [Acer Aspire ES1-711] System freezes occasionally

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [Acer Aspire ES1-711] System freezes occasionally

Status in linux package in Ubuntu:
  Expired

Bug description:
  Occasionally my system freezes totally in 15.04 and 15.10. Switching
  to Console via Ctrl-Alt-F1 or rebooting via Ctrl-Alt-Del does not
  work.

  Some days my system will run for many hours without any problem,  and
  on other days I experience 2 or 3 freezes in an hour time.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  freek  2223 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Oct 30 21:11:26 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=c4065390-4392-460d-b828-37b12c4605cb
  InstallationDate: Installed on 2015-07-13 (108 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Acer Aspire ES1-711
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed 
root=UUID=772134c4-7cb5-40d6-b0c7-a6bc4a98efe5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-27 (2 days ago)
  dmi.bios.date: 11/07/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA70_BM
  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.:bvrV1.05:bd11/07/2014:svnAcer:pnAspireES1-711:pvrV1.05:rvnAcer:rnEA70_BM:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire ES1-711
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511844/+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 792085] Re: Automatic remount of safely removed USB 3.0 drive

[Myk Dowling]

Confirm fixed in Xenial

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

Title:
  Automatic remount of safely removed USB 3.0 drive

Status in Nautilus:
  New
Status in thunar:
  Invalid
Status in linux package in Ubuntu:
  In Progress
Status in nautilus package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  Confirmed
Status in udev package in Ubuntu:
  Confirmed
Status in nautilus source package in Precise:
  New
Status in thunar source package in Precise:
  New
Status in udev source package in Precise:
  New
Status in linux source package in Trusty:
  In Progress
Status in nautilus source package in Trusty:
  New
Status in thunar source package in Trusty:
  New
Status in udev source package in Trusty:
  New
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in Fedora:
  Unknown
Status in openSUSE:
  Fix Released

Bug description:
  Binary package hint: nautilus

  When I choose "Safely remove drive" context menu entry for an external
  USB drive within a nautilus window or directly clicking on the desktop
  icon, after about 10 seconds the drive is automatically remounted and
  a Nautilus window showing the root folder opens.

  I have noticed that similar already happened with a very old Ubuntu
  version - Bug #110589 and as that is so long time ago I thought it is
  better to open a new bug. Reason of the problem might even be
  completely different.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: nautilus 1:2.32.2.1-0ubuntu13
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
  Uname: Linux 2.6.38-8-generic-pae i686
  Architecture: i386
  Date: Thu Jun  2 23:40:08 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

  break-fix: - 37be66767e3cae4fd16e064d8bb7f9f72bf5c045

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/792085/+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 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)

[Pedro R]

** Attachment removed: "acpi-dump"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653456/+attachment/4839389/+files/acpi-dump

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

Title:
  ASUS G752VS: Touchpad and Fn keys not working (Ubuntu
  16.04.1/16.10/17.04)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Non-Optimus laptop ASUS G752VS-GC063D-CST256.
  17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 
NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 
802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 
x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS.

  Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and
  17.04, among other problems I found that touchpad and Fn keys (all
  except volume control) doesn't work on my brand new ASUS G752VS.

  It is very hard even to try Ubuntu 16.10 and 17.04 because of the
  missing mouse pointer. This problem must be related to a video driver
  because if after installing one is capable to install Nvidia drivers -
  problem is solved. This problem doesn't exist both while trying and
  installing Ubuntu 16.04.1!

  I'm currently on Windows 10, and this bug report is made from Ubuntu
  16.04.1 LiveCD.

  
  dmesg | grep -i elan
  [  101.082929] input: ELAN1203:00 04F3:3043 Touchpad as 
/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11
  [  101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID 
v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00

  
  xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ G-SPY USB Gaming Mouse  id=10   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=13   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=14   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN1203:00 04F3:3043 Touchpad  id=15   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ G-SPY USB Gaming Mouse  id=9[slave  
keyboard (3)]
  ↳ USB2.0 HD UVC WebCamid=11   [slave  
keyboard (3)]
  ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=12   [slave  
keyboard (3)]
  ↳ Asus WMI hotkeysid=16   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=17   [slave  
keyboard (3)]

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

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

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

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

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

  I: Bus=0003 Vendor=04d9 Product=a070 Version=0110
  N: Name="G-SPY USB Gaming Mouse"
  P: Phys=usb-:00:14.0-2/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:04D9:A070.0001/input/input5
  U: Uniq=
  H: Handlers=sysrq kbd event5 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=e080ffdf01cf fffe
  B: MSC=10
  B: LED=1f

  I: Bus=0003 Vendor=04d9 Product=a070 Version=0110
  N: Name="G-SPY USB Gaming 

[Kernel-packages] [Bug 1673197] Re: Upgrading zfs-initramfs breaks booting from a zfs root

[Richard Laager]

/usr/share/initramfs-tools/conf.d/zfs has disappeared from the package
in zesty. That is the cause of this regression.

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

Title:
  Upgrading zfs-initramfs breaks booting from a zfs root

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  Upgrading to zfs-initramfs 0.6.5.9-4ubuntu1 breaks my boot.

  I've EFI and a small ext2 boot partition, and the rest of my SDD is a
  zfs pool. After upgrade I'm dropped in the initramfs shell and no
  zpools are available.

  Downgrading to 0.6.5.8-0ubuntu9 makes it boot again.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: zfs-initramfs 0.6.5.9-4ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Mar 15 18:29:04 2017
  InstallationDate: Installed on 2016-05-06 (312 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (113 days ago)

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

[Joseph Salisbury]

Thanks for the feedback, Jamie!

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

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

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)

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

[bugproxy]

--- Comment From achen...@us.ibm.com 2017-03-17 13:59 EDT---
Hi all,

I am looking though patches to see if there might have been others.  Is
there a way we can log into the machine to look around?  We are looking
to see if we can find a similar machine to use as well.  Thanks!

-- 
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:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in qemu source package in Xenial:
  Incomplete

Bug description:
  [Impact]

   * Some newer Power8 derivates fail to work correctly e.g. Power S822LC 
(8335-GTB) 

   * This is a toleration change (no exploitation) for those HW releases 
 following the SRU policy of "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."

   * Without the Fix that hardware won't run Xenial guests under current 
 Xenials Qemu version

   * The fix lets processors that support it run in PowerISA 2.07 
 compatibility mode (plus a few no-op changes as backport 
 dependencies)

  
  [Test Case]

   * Run a Xenial Guest in KVM on one of the specific HW revisions being 
 affected.

  [Regression Potential]

   * Changes are PPC only, so fallout should be contained to that
   * Patches were created by IBM and in Upstream qemu since 2.7
   * The effective change is rather small, only allow different compat 
 level on this other cpu class
   * There are a few refactoring changes needed to get the backport done, 
 while they should be a no-op that is a regression potential (still 
 limited to ppc64el)

  [Other Info]
   
   * Needed for certifying this Hardware for Ubuntu


  
  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)
   

[Kernel-packages] [Bug 1673796] Re: Ubuntu 16.10, Dell XPS 15 9550, DNS problem after suspend/resume

[Cruz Fernandez]

It started happening after upgrade from Ubuntu 16.04 to 16.10. Kernels
affected are: 4.8.0-42 and 4.8.0-41 AFAIK.

I'll install latest kernel probably tomorrow if possible and come back
to you @jsalisbury

Thanks for the fast response!

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

Title:
  Ubuntu 16.10, Dell XPS 15 9550, DNS problem after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After suspend/resume the wifi network comes back, but the DNS doesn't
  work. I've tried to ping a known IP and it works ok though.

  My normal solution is to restart the network totally (haven't found a
  smaller way to fix the skewed DNS server locally):

  sudo systemctl restart network-manager.service

  Not sure if I should report this on other package related to the DNS
  systemd resolve?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-42-generic 4.8.0-42.45
  ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17
  Uname: Linux 4.8.0-42-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   cruz   2658 F...m pulseaudio
   /dev/snd/controlC0:  cruz   2658 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Mar 17 11:34:54 2017
  HibernationDevice: RESUME=UUID=afd0c8e7-78e3-47d1-b086-10c627ac3d76
  InstallationDate: Installed on 2016-06-13 (277 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-42-generic 
root=UUID=0bdc13dd-b122-4879-8d8a-31cce3301ef5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-42-generic N/A
   linux-backports-modules-4.8.0-42-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2017-03-08 (8 days ago)
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  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/1673796/+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 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 Ubuntu with the latest updates 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 +++

  
  === Message 4 ===

  ...
  >read(3, 

[Kernel-packages] [Bug 1622894] Re: sg devices are not being created for SCSI storage controller devices starting from v4.4.0-30

[Joseph Salisbury]

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Invalid

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 1626436] Re: [4.8 regression] boot has become very slow

[Joseph Salisbury]

** Changed in: linux (Ubuntu Yakkety)
   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/1626436

Title:
  [4.8 regression] boot has become very slow

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

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 1633634] Re: sr-iov not working on ubuntu 16.04 kvm

[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/1633634

Title:
  sr-iov not working on ubuntu 16.04 kvm

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The exact same set up (hardware and commands I have made) worked
  perfectly on Ubuntu 14.04 but I can't get it working with 16.04. The
  only thing I have changed between the 2 setups is adding  to the network definition as the now default vfio also
  failed with

  qemu-system-x86_64: vfio_dma_map(0x55f1c4f8bb00, 0xfe00, 0x4000, 
0x7fa68770) = -14 (Bad address)
  qemu: hardware error: vfio: DMA mapping failed, unable to continue

  If I am doing something wrong I apologise, this is my first bug report
  and I'm still relatively new to Linux.

  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
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 14 20:11 seq
   crw-rw 1 root audio 116, 33 Oct 14 20:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Oct 14 23:05:26 2016
  HibernationDevice: RESUME=UUID=bb1632fb-69fe-4d67-bc51-8182d2546d91
  InstallationDate: Installed on 2016-10-08 (6 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: FUJITSU PRIMERGY TX1310 M1
  PciMultimedia:
   
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic 
root=UUID=07b95c7c-db77-4cee-8336-6f24b2072da6 ro pcie_aspm=off intel_iommu=on 
iommu=pt pci=assign-busses quiet splash 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.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2015
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V4.6.5.4 R1.5.0 for D3219-A1x
  dmi.board.name: D3219-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3219-A1
  dmi.chassis.type: 6
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: TX1310M1
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.4R1.5.0forD3219-A1x:bd09/15/2015:svnFUJITSU:pnPRIMERGYTX1310M1:pvr:rvnFUJITSU:rnD3219-A1:rvrS26361-D3219-A1:cvnFUJITSU:ct6:cvrTX1310M1:
  dmi.product.name: PRIMERGY TX1310 M1
  dmi.sys.vendor: FUJITSU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633634/+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 1653162] Re: System won't boot after upgrade to 16.04 with 4.4.0 kernel

[Joseph Salisbury]

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

Title:
  System won't boot after upgrade to 16.04 with 4.4.0 kernel

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:
  I have a Dell PowerEdge 1800 with Dell CERC 1.5/6ch RAID controller in
  it. Everything worked fine under Ubuntu 14.04.1. When I upgraded to
  16.04.1 the system won't boot. It can't find the root filesystem. I
  see errors about host adapter dead on the screen many times. This is
  with kernel 4.4.0-57 and with 4.8.0-32. When I switch back to kernel
  3.13.0-105 the system boots just fine.

  I have mptbios 5.06.04.
  The CERC card says bios version 4.1-0 [Build 7403]

  When booting into the ercovery kernel I'm getting error messages about host 
adapter dead.
  Eventually I get a message:
  "aacraid: aac_fib_send: first asynchronous command timed out.
  Usually a result of a PCI interrupt routing problem
  update moher board BIOS or consider utilizing one of
  the SAFE mode kernel options (acpi, apic etc)"

  
  Using kernel parameter "intel_iommu=on" doesn't help. This was suggested on a 
post that I saw about these errors.

  Booting with "noapic" didn't help.
  Booting with "noapic noacpi" didn't help.

  
  I've also tried the dkms modules from Adaptec and that doesn't seem to help 
either.

  
  I can't figure out how to upgrade the firmware or BIOS on the system from 
Ubuntu either.

  
  This may be related to this bug: 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552551?comments=all
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=beec17b5-eac8-4e94-ac99-65b63c428b77
  InstallationDate: Installed on 2014-02-24 (1039 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  IwConfig:
   eth1  no wireless extensions.
   
   lono wireless extensions.
  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: Dell Computer Corporation PowerEdge 1800
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-105-generic 
root=UUID=83e1b87e-adb9-4798-a6e0-18d401c91a4a ro nosplash noplymouth
  ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-105-generic N/A
   linux-backports-modules-3.13.0-105-generic  N/A
   linux-firmware  1.157.6
  RfKill:
   
  Tags:  xenial
  Uname: Linux 3.13.0-105-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-12-25 (3 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/01/2004
  dmi.bios.vendor: Dell Computer Corporation
  dmi.bios.version: A00
  dmi.board.name: 0X7500
  dmi.board.vendor: Dell Computer Corporation
  dmi.board.version: A00
  dmi.chassis.type: 17
  dmi.chassis.vendor: Dell Computer Corporation
  dmi.modalias: 
dmi:bvnDellComputerCorporation:bvrA00:bd09/01/2004:svnDellComputerCorporation:pnPowerEdge1800:pvr:rvnDellComputerCorporation:rn0X7500:rvrA00:cvnDellComputerCorporation:ct17:cvr:
  dmi.product.name: PowerEdge 1800
  dmi.sys.vendor: Dell Computer Corporation

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

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

** Changed in: linux (Ubuntu Vivid)
   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/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 1657994] Re: Regression: HDMI audio produces no sound (Skylake NUC)

[Joseph Salisbury]

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

** Changed in: linux (Ubuntu Yakkety)
   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/1657994

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

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

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 792085] Re: Automatic remount of safely removed USB 3.0 drive

[Joseph Salisbury]

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

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

** No longer affects: linux (Ubuntu Precise)

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

Title:
  Automatic remount of safely removed USB 3.0 drive

Status in Nautilus:
  New
Status in thunar:
  Invalid
Status in linux package in Ubuntu:
  In Progress
Status in nautilus package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  Confirmed
Status in udev package in Ubuntu:
  Confirmed
Status in nautilus source package in Precise:
  New
Status in thunar source package in Precise:
  New
Status in udev source package in Precise:
  New
Status in linux source package in Trusty:
  In Progress
Status in nautilus source package in Trusty:
  New
Status in thunar source package in Trusty:
  New
Status in udev source package in Trusty:
  New
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in Fedora:
  Unknown
Status in openSUSE:
  Fix Released

Bug description:
  Binary package hint: nautilus

  When I choose "Safely remove drive" context menu entry for an external
  USB drive within a nautilus window or directly clicking on the desktop
  icon, after about 10 seconds the drive is automatically remounted and
  a Nautilus window showing the root folder opens.

  I have noticed that similar already happened with a very old Ubuntu
  version - Bug #110589 and as that is so long time ago I thought it is
  better to open a new bug. Reason of the problem might even be
  completely different.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: nautilus 1:2.32.2.1-0ubuntu13
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
  Uname: Linux 2.6.38-8-generic-pae i686
  Architecture: i386
  Date: Thu Jun  2 23:40:08 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

  break-fix: - 37be66767e3cae4fd16e064d8bb7f9f72bf5c045

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/792085/+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 1571798] Re: Broadwell ECRC Support missing in Ubuntu

[Joseph Salisbury]

This bug has been stale for a bit.  Are there any 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/1571798

Title:
  Broadwell ECRC Support missing in Ubuntu

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Here is the problem statement from the Dell team:

  When booting into Ubuntu 14.04.4 with a Broadwell CPU and an Intel
  Quick Assist Card, the memory location that corresponds to ECRC is set
  to 0x01e0, when the BIOS is setting this location 0x00a0 pre-OS boot.
  This causes the card to not function unless we implement the following
  workaround using setpci.

  “setpci –s AA:BB.C 160.w=0”, where AA:BB.C is the PCI Root Path for
  the Intel Quick Assit Card.

  We’ve verified the memory location is correct when booting to other
  OSes, such as RHEL 7.2 and Windows Server 2012 R2.

  If there is any information you can give as to why this may be
  occurring in Ubuntu or where we may start to debug when the memory is
  changed, we would appreciate it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571798/+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 1581326] Re: Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS.

[Joseph Salisbury]

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

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

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

** Changed in: linux (Ubuntu Yakkety)
   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/1581326

Title:
  Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS.

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

Bug description:
  Booted into Ubuntu16.04(4.4.0-21-generic) OS with inbox driver-
  v12.100.00.00,

  Successfully discovered HBA and the devices connected to HBA.
  >>Launched SAS3IRCU utility and created a RAID volume (RAID0/RAID1/RAID10). 
volume successfully created and listed from SAS3IRCU utility.
  >>Tried to create a second RAID volume (RAID0/RAID1/RAID10) from SAS3IRCU 
utility. 
  Kernel crashed here while creating second volume.
  >>tried with all possible combinations of RAID volumes.

  Please find the attached kernel crash logs.

  >>cat /proc/version_signature 
  Ubuntu 4.4.0-21.37-generic 4.4.6 

  HBA used : LSI SAS3(Fury)

  Issue : Kernel gets crashed , when tried creating 2nd RAID volume.
  Expected : One should be able to create MAX 2 RAID volumes at any point of 
time successfully , without any kernel crash.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
  InstallationDate: Installed on 2016-05-11 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig:
   enp5s0f0  no wireless extensions.
   
   enp5s0f1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/28/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DRH-7TF/7F/iTF/iF
  dmi.board.vendor: Supermicro
  dmi.board.version: 1234567890
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnSupermicro:pnX9DRH-7TF/7F/iTF/iF:pvr1234567890:rvnSupermicro:rnX9DRH-7TF/7F/iTF/iF:rvr1234567890:cvnSupermicro:ct3:cvr1234567890:
  dmi.product.name: X9DRH-7TF/7F/iTF/iF
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
  InstallationDate: Installed on 2016-05-11 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig:
   enp5s0f0  no wireless extensions.
   
   enp5s0f1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio 

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

[Joseph Salisbury]

Does this bug still exist in Ubuntu 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/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 +++

  
  === Message 4 ===

  ...
  >read(3, 

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

[Joseph Salisbury]

** Changed in: linux (Ubuntu Zesty)
   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/1659340

Title:
  Linux kernel 4.8 hangs at boot up

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

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 1491654] Re: Intel P3700 PCIe SSD string shows ''Unknown'' during Ubuntu 14.04 installation

[Joseph Salisbury]

** Changed in: linux (Ubuntu Trusty)
   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 Zesty)
   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/1491654

Title:
  Intel P3700 PCIe SSD string shows ''Unknown'' during Ubuntu 14.04
  installation

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

Bug description:
  Current Behavior
  ==
  1. Intel P3700 PCIe SSD string shows "Unknow" during Ubuntu 14.04 install.

  Reference Verification
  ==
  1. Which version of previous BIOS/BMC/HW passed/failed? 1st Test
  2. Which similar project/product passed/failed? NA

  Steps to reproduce the problem
  ==
  1. Install Intel P3700 PCIe SSD*2 and SAS 12G HDD*8 with LSI 3108 into SUT.
  2. Power on system and install Ubuntu 14.04.
  3. Intel P3700 PCIe SSD string shows "Unknown" during OS install.

  Expected Behavior
  ==
  1. Intel P3700 PCIe SSD string should not show "Unknown" during Ubuntu 14.04 
install.

  Pcie SSD config:HDD/SSD:Intel,SSDPE2MD016T4,PCI-e,1.6TB,Gen3

  Copied from private bug:
  https://bugs.launchpad.net/quantatw/+bug/1454965

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491654/+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 1667536] Re: kernel uas module cannot allocate memory with more than two USB disks

[Joseph Salisbury]

I built another test kernel.  It can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1667536/

Can you test this kernel and see if it resolves this bug and/or runs
into the issue you hit in comment #4?

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

Title:
  kernel uas module cannot allocate memory with more than two USB disks

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  In Progress

Bug description:
  See https://bugzilla.kernel.org/show_bug.cgi?id=177551

  Patch is included.  Please merge this patch into 4.8.0 for Ubuntu
  16.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-39-generic 4.8.0-39.42
  ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
  Uname: Linux 4.8.0-39-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Thu Feb 23 19:54:42 2017
  HibernationDevice: RESUME=UUID=4c961713-40a8-4bb4-af57-9074c1016a4f
  InstallationDate: Installed on 2016-11-12 (103 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-39-generic.efi.signed 
root=UUID=dc70bb57-65b3-4439-9947-a2891f8f07c9 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-39-generic N/A
   linux-backports-modules-4.8.0-39-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-11-12 (103 days ago)
  dmi.bios.date: 09/04/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8215
  dmi.board.vendor: HP
  dmi.board.version: 83.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd09/04/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8215:rvr83.14: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/linux/+bug/1667536/+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 1490347] Re: [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy LMP Link Management Protocol) PIN codes

[Roger Lawhorn]

UPDATE:

I created my own bluez 5.43 unsigned packages and installed them.
The issue is still present.

Here are the steps I took:

It was suggested that bluez 5.4 fixes the issue. However, that package
is not available for ubuntu 16.04. I was able to build my own unsigned
and upgradable package using the following steps and I have bluez 5.43.
Still does not connect though.

sudo  apt-get install debhelper devscripts dh-autoreconf flex bison
libdbus-glib-1-dev libglib2.0-dev  libcap-ng-dev libudev-dev
libreadline-dev libical-dev check dh-systemd libebook1.2-dev

wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez_5.43.orig.tar.xz
wget 
https://launchpad.net/ubuntu/+archive/primary/+files/bluez_5.43-0ubuntu1.debian.tar.xz
wget 
https://launchpad.net/ubuntu/+archive/primary/+files/bluez_5.43-0ubuntu1.dsc

tar xf bluez_5.43.orig.tar.xz
cd bluez-5.43
tar xf ../bluez_5.43-0ubuntu1.debian.tar.xz
debchange --local=~lorenzen 'Backport to Xenial'
debuild -b -j4 -us -uc
cd ..
sudo dpkg -i *.deb

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

Title:
  [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy
  LMP Link Management Protocol) PIN codes

Status in Bluez Utilities:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Wily:
  Triaged
Status in bluez source package in Xenial:
  Confirmed

Bug description:
  Bluez 5.3 does not have support for pairing with devices (such as
  keyboards) that use a PIN code for pairing.

  A mouse pairs correctly.

  From my research it seems as if the ChromeOS project developed patches
  to fix this and they are supposed to have been included in Bluez 5.4
  (that statement dated April 2013) but I've not yet identified them.

  "The agent's implementation in bt_console/bluetoothctl upstream is
  incomplete, missing some functions like DisplayPincode."

  https://code.google.com/p/chromium/issues/detail?id=222661

  Along with the loss of Headset profiles meaning VoIP applications can
  no longer use HSP/HFP profiles (requiring functionality yet to land in
  Ofono) this cripples the use of Bluetooth for much else than A2DP or
  mouse input.

  Attempting to pair with, for example, an Apple Wireless Keyboard that
  pairs and works correctly with 14.04 LTS, fails totally on 15.10.

  The mouse shown below is already paired, connected, and working.

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes
  [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes
  [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48
  [bluetooth]# pair 00:0A:95:4B:BD:C2
  Attempting to pair with 00:0A:95:4B:BD:C2

  >>> at this point nothing is happening

  >>> so I press Enter on the keyboard and...
  [agent] PIN code: 791166
  >>> I type 791166 Enter and ...
  [agent] PIN code: 237744
  >>> I type 237744 Enter and...
  [agent] PIN code: 358866
  >>> I type 358866 Enter and...
  Request PIN code
  [agent] Enter PIN code: 1234
  >>> I type 1234 Enter on the keyboard and 1234 at the prompt...
  Failed to pair: org.bluez.Error.AuthenticationFailed

  This cycle repeats in various permuations. Sometimes the final
  "Request PIN code" does not appear.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1490347/+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 1511511] Re: USB keyboard stops working after pressing extended key

[Alejandro Díaz-Caro]

@Alexander: I would very much appreciate if you could share the driver
you have created...

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

Title:
  USB keyboard stops working after pressing extended key

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  USB keyboard Cougar K500 gaming keyboard has some additional extended
  keys, all of them making the keyboard stop responding if pressed under
  linux. The device is recovered only by unplugging the USB and plugging
  it again.

  The keyboard has been tested under Ubuntu 14.04.3 LTS, Ubuntu 15.04
  and Ubuntu 15.10 (the latter running as virtualbox guest). All tests
  failed with exactly the same behaviour.

  USB ID is: "060b:500a Solid Year".

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19 [modified: 
boot/vmlinuz-4.2.0-16-generic]
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pinfli 1055 F pulseaudio
  Date: Thu Oct 29 19:33:23 2015
  HibernationDevice: RESUME=UUID=f68f4b91-ea68-4e4b-9a10-8ed5bca2efbe
  InstallationDate: Installed on 2015-10-24 (5 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 060b:500a Solid Year 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=523dfd8b-b825-47e3-a116-cb85f901386c ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511511/+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 1673498] Re: move aufs.ko from -extra to linux-image package

[Kamal Mostafa]

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

** No longer affects: linux-gke (Ubuntu Aa-series)

** No longer affects: linux-gke (Ubuntu Precise)

** No longer affects: linux-gke (Ubuntu Trusty)

** No longer affects: linux-gke (Ubuntu Vivid)

** No longer affects: linux-gke (Ubuntu Yakkety)

** No longer affects: linux-gke (Ubuntu Zesty)

** Changed in: linux-gke (Ubuntu Xenial)
   Status: New => Fix Committed

** Changed in: linux-gke (Ubuntu Xenial)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

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

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

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

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

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

** Changed in: linux-gke (Ubuntu)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

Title:
  move aufs.ko from -extra to linux-image package

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-gke package in Ubuntu:
  Fix Committed
Status in linux source package in Precise:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux-gke source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in aa-series:
  New

Bug description:
  Docker is ordinarily configured to use aufs, but the aufs kernel
  module is only available after installing the linux-image-extra
  package.

  Please promote aufs.ko from the linux-image-extra package to the main
  linux-image package for all supported Ubuntu kernels and derivatives,
  so as to remove Docker's dependence on linux-image-extra.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1673498/+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 1667323] Re: Backlight control does not work and there are no entries in /sys/class/backlight

[Joseph Salisbury]

Can you test the following kernels to see when this bug was introduced
upstream:

4.4.41: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.40/
4.4.41: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.41/
4.4.42: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.42/
4.4.43: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.43/
4.4.44: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.44/

You don't have to test every kernel, just up until the kernel that first
has this bug.

Thanks in advance!

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

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

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

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

** Tags removed: needs-bisect
** Tags added: performing-bisect

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

Title:
  Backlight control does not work and there are no entries in
  /sys/class/backlight

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

Bug description:
  It was working fine until today. 
  The folder /sys/class/backlight/ use to have "acpi_video0/brightness", but 
now is empty. 
  I am using Nvidia Proprietary driver 340.101 (proprietary, tested). The 
problem persists even with the 304 driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  desgua 2028 F pulseaudio
   /dev/snd/controlC0:  desgua 2028 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Feb 23 11:31:18 2017
  HibernationDevice: RESUME=UUID=f23a6347-9483-460e-aa29-cbc47850f890
  InstallationDate: Installed on 2014-05-01 (1028 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lsusb:
   Bus 002 Device 003: ID 064e:a127 Suyin Corp. 
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic 
root=/dev/mapper/ubuntu--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-08-17 (189 days ago)
  dmi.bios.date: 12/03/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3659
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd12/03/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.23:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 049D212412102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667323/+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 1673805] [NEW] linux: 4.10.0-14.16 -proposed tracker

[Tim Gardner]

Public bug reported:

This bug is for tracking the 4.10.0-14.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

** Affects: kernel-development-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-development-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-development-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Zesty)
 Importance: Medium
 Status: Confirmed


** Tags: block-proposed kernel-release-tracking-bug zesty

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

** Tags added: block-proposed

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

** Tags added: zesty

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

** Also affects: kernel-development-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/regression-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-development-workflow
   Status: New => In Progress

** Changed in: kernel-development-workflow
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-development-workflow/regression-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/regression-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

Title:
  linux: 4.10.0-14.16 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow 

[Kernel-packages] [Bug 1661695] Re: screen flickering raedon

[Joseph Salisbury]

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

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

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

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

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

Title:
  screen flickering raedon

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

Bug description:
  4.4.0-53 WORKS FINE

  4.4.0-62 DOES NOT WORK (screen flickers)

  It seems there is a problem with powersafe:

  With auto:
  echo auto > /sys/class/drm/card0/device/power_dpm_force_performance_level

  you will see heavy screen flickering on higher display resolutions

  With low or high:
  echo low > /sys/class/drm/card0/device/power_dpm_force_performance_level or
  echo high > /sys/class/drm/card0/device/power_dpm_force_performance_level

  there is no screen flickering

  And having performance level set to HIGH at all times is not a
  workaround because it wears out the card. :(

  details:

  Linux CINNAMON 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

  ```
  Vendor: X.Org (0x1002)
  Device: AMD PITCAIRN (DRM 2.43.0 / 4.4.0-62-generic, LLVM 5.0.0) (0x6811)
  Version: 17.1.0
  Accelerated: yes
  Video memory: 2048MB
  Unified memory: no
  Preferred profile: core (0x1)
  Max core profile version: 4.2
  Max compat profile version: 3.0
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.0
  OpenGL vendor string: X.Org
  OpenGL renderer string: Gallium 0.4 on AMD PITCAIRN (DRM 2.43.0 / 
4.4.0-62-generic, LLVM 5.0.0)
  OpenGL core profile version string: 4.2 (Core Profile) Mesa 17.1.0-devel - 
padoka PPA
  OpenGL core profile shading language version string: 4.20
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile

  ```
  ---
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  atomi  3734 F pulseaudio
   /dev/snd/controlC0:  atomi  3734 F pulseaudio
   /dev/snd/controlC1:  atomi  3734 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=30254b0c-14d7-4c0e-9168-a8d492fa027b
  InstallationDate: Installed on 2016-12-27 (37 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=41cc7dce-52e8-4b29-9347-60afc0a7d0ed ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware1.157.6
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  Tags:  serena
  Uname: Linux 4.4.0-53-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661695/+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 1673498] Re: move aufs.ko from -extra to linux-image package

[Kamal Mostafa]

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

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

Title:
  move aufs.ko from -extra to linux-image package

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Precise:
  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
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in aa-series:
  New

Bug description:
  Docker is ordinarily configured to use aufs, but the aufs kernel
  module is only available after installing the linux-image-extra
  package.

  Please promote aufs.ko from the linux-image-extra package to the main
  linux-image package for all supported Ubuntu kernels and derivatives,
  so as to remove Docker's dependence on linux-image-extra.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1673498/+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 1673796] Re: Ubuntu 16.10, Dell XPS 15 9550, DNS problem after suspend/resume

[Joseph Salisbury]

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

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc2

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

Title:
  Ubuntu 16.10, Dell XPS 15 9550, DNS problem after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After suspend/resume the wifi network comes back, but the DNS doesn't
  work. I've tried to ping a known IP and it works ok though.

  My normal solution is to restart the network totally (haven't found a
  smaller way to fix the skewed DNS server locally):

  sudo systemctl restart network-manager.service

  Not sure if I should report this on other package related to the DNS
  systemd resolve?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-42-generic 4.8.0-42.45
  ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17
  Uname: Linux 4.8.0-42-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   cruz   2658 F...m pulseaudio
   /dev/snd/controlC0:  cruz   2658 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Mar 17 11:34:54 2017
  HibernationDevice: RESUME=UUID=afd0c8e7-78e3-47d1-b086-10c627ac3d76
  InstallationDate: Installed on 2016-06-13 (277 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-42-generic 
root=UUID=0bdc13dd-b122-4879-8d8a-31cce3301ef5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-42-generic N/A
   linux-backports-modules-4.8.0-42-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2017-03-08 (8 days ago)
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  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/1673796/+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 1673796] 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/1673796

Title:
  Ubuntu 16.10, Dell XPS 15 9550, DNS problem after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After suspend/resume the wifi network comes back, but the DNS doesn't
  work. I've tried to ping a known IP and it works ok though.

  My normal solution is to restart the network totally (haven't found a
  smaller way to fix the skewed DNS server locally):

  sudo systemctl restart network-manager.service

  Not sure if I should report this on other package related to the DNS
  systemd resolve?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-42-generic 4.8.0-42.45
  ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17
  Uname: Linux 4.8.0-42-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   cruz   2658 F...m pulseaudio
   /dev/snd/controlC0:  cruz   2658 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Mar 17 11:34:54 2017
  HibernationDevice: RESUME=UUID=afd0c8e7-78e3-47d1-b086-10c627ac3d76
  InstallationDate: Installed on 2016-06-13 (277 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-42-generic 
root=UUID=0bdc13dd-b122-4879-8d8a-31cce3301ef5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-42-generic N/A
   linux-backports-modules-4.8.0-42-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2017-03-08 (8 days ago)
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  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/1673796/+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 1673796] Re: Ubuntu 16.10, Dell XPS 15 9550, DNS problem after suspend/resume

[Joseph Salisbury]

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

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

Title:
  Ubuntu 16.10, Dell XPS 15 9550, DNS problem after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After suspend/resume the wifi network comes back, but the DNS doesn't
  work. I've tried to ping a known IP and it works ok though.

  My normal solution is to restart the network totally (haven't found a
  smaller way to fix the skewed DNS server locally):

  sudo systemctl restart network-manager.service

  Not sure if I should report this on other package related to the DNS
  systemd resolve?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-42-generic 4.8.0-42.45
  ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17
  Uname: Linux 4.8.0-42-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   cruz   2658 F...m pulseaudio
   /dev/snd/controlC0:  cruz   2658 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Mar 17 11:34:54 2017
  HibernationDevice: RESUME=UUID=afd0c8e7-78e3-47d1-b086-10c627ac3d76
  InstallationDate: Installed on 2016-06-13 (277 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-42-generic 
root=UUID=0bdc13dd-b122-4879-8d8a-31cce3301ef5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-42-generic N/A
   linux-backports-modules-4.8.0-42-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2017-03-08 (8 days ago)
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  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/1673796/+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 1673796] [NEW] Ubuntu 16.10, Dell XPS 15 9550, DNS problem after suspend/resume

[Cruz Fernandez]

Public bug reported:

After suspend/resume the wifi network comes back, but the DNS doesn't
work. I've tried to ping a known IP and it works ok though.

My normal solution is to restart the network totally (haven't found a
smaller way to fix the skewed DNS server locally):

sudo systemctl restart network-manager.service

Not sure if I should report this on other package related to the DNS
systemd resolve?

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-42-generic 4.8.0-42.45
ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17
Uname: Linux 4.8.0-42-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   cruz   2658 F...m pulseaudio
 /dev/snd/controlC0:  cruz   2658 F pulseaudio
CurrentDesktop: Unity
Date: Fri Mar 17 11:34:54 2017
HibernationDevice: RESUME=UUID=afd0c8e7-78e3-47d1-b086-10c627ac3d76
InstallationDate: Installed on 2016-06-13 (277 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
 Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
 Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 15 9550
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-42-generic 
root=UUID=0bdc13dd-b122-4879-8d8a-31cce3301ef5 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-42-generic N/A
 linux-backports-modules-4.8.0-42-generic  N/A
 linux-firmware1.161.1
SourcePackage: linux
UpgradeStatus: Upgraded to yakkety on 2017-03-08 (8 days ago)
dmi.bios.date: 12/22/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.19
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
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/1673796

Title:
  Ubuntu 16.10, Dell XPS 15 9550, DNS problem after suspend/resume

Status in linux package in Ubuntu:
  New

Bug description:
  After suspend/resume the wifi network comes back, but the DNS doesn't
  work. I've tried to ping a known IP and it works ok though.

  My normal solution is to restart the network totally (haven't found a
  smaller way to fix the skewed DNS server locally):

  sudo systemctl restart network-manager.service

  Not sure if I should report this on other package related to the DNS
  systemd resolve?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-42-generic 4.8.0-42.45
  ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17
  Uname: Linux 4.8.0-42-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   cruz   2658 F...m pulseaudio
   /dev/snd/controlC0:  cruz   2658 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Mar 17 11:34:54 2017
  HibernationDevice: RESUME=UUID=afd0c8e7-78e3-47d1-b086-10c627ac3d76
  InstallationDate: Installed on 2016-06-13 (277 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-42-generic 
root=UUID=0bdc13dd-b122-4879-8d8a-31cce3301ef5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-42-generic N/A
   linux-backports-modules-4.8.0-42-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2017-03-08 (8 days ago)
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  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 1672470] Re: ip_rcv_finish() NULL pointer kernel panic

[Dan Streetman]

** Description changed:

+ [Impact]
+ 
+ When using iptables rules affecting bridge traffic, and if affected
+ traffic is flowing through bridge while br_netfilter module is loaded or
+ unloaded, a kernel panic may occur.
+ 
+ [Test Case]
+ 
+ It's difficult to reproduce because of a very small race condition
+ window during br_netfilter load/unload when the module is receiving
+ traffic but has not yet registered its hooks (or, has unregistered its
+ hooks but still has traffic it's processing).  A system must be set up
+ using a bridge, and iptable netfilter rules must be set up to process
+ the bridge traffic.  Then the system should be rebooted until the
+ problem occurs, or the br_netfilter module should be loaded/unloaded
+ until the problem occurs.
+ 
+ [Regression Potential]
+ 
+ Changing how the br_netfilter module switches its fake dst for a real
+ dst may, if done incorrectly, result in more kernel panics if other code
+ tries to process the br_netfilter module's fake dst.
+ 
+ [Other Info]
+ 
  The br_netfilter module processes packets traveling through its bridge,
  and while processing each skb it places a special fake dst onto the skb.
  When the skb leaves the bridge, it removes the fake dst and places a
  real dst onto it.  However, it uses a hook to do this, and when the
  br_netfilter module is unloading it unregisters that hook.  Any skbs
  that are currently being processed in the bridge by the br_netfilter
  module, but that leave the bridge after the hook is unregistered (or,
  during br_netfilter module load, before the hook is registered) will
  still have the fake dst; when other code then tries to process that dst,
  it causes a kernel panic because the dst is invalid.
  
  Recent upstream discussion:
  https://www.spinics.net/lists/netdev/msg416912.html
  
- Upstream patch (not yet merged into net-next):
+ Upstream patch:
  https://patchwork.ozlabs.org/patch/738275/
+ upstream commit is a13b2082ece95247779b9995c4e91b4246bed023
  
  example panic report:
  
  [ 214.518262] BUG: unable to handle kernel NULL pointer dereference at (null)
  [ 214.612199] IP: [< (null)>] (null)
  [ 214.672744] PGD 0 [ 214.696887] Oops: 0010 [#1] SMP [ 214.735697] Modules 
linked in: br_netfilter(+) tun 8021q bridge stp llc bonding iTCO_wdt 
iTCO_vendor_support tpm_tis tpm kvm_intel kvm irqbypass sb_edac edac_core ixgbe 
mdio ipmi_si ipmi_msghandler lpc_ich mfd_core mousedev evdev igb dca 
procmemro(O) nokeyctl(O) noptrace(O)
  [ 215.029240] CPU: 34 PID: 0 Comm: swapper/34 Tainted: G O 4.4.39 #1
  [ 215.116720] Hardware name: Cisco Systems Inc UCSC-C220-M3L/UCSC-C220-M3L, 
BIOS C220M3.2.0.13a.0.0713160937 07/13/16
  [ 215.241644] task: 882038fb4380 ti: 8810392b task.ti: 
8810392b
  [ 215.331207] RIP: 0010:[<>] [< (null)>] (null)
  [ 215.420877] RSP: 0018:88103fec3880 EFLAGS: 00010286
  [ 215.484436] RAX: 881011631000 RBX: 881011067100 RCX: 

  [ 215.569836] RDX:  RSI:  RDI: 
881011067100
  [ 215.655234] RBP: 88103fec38a8 R08: 0008 R09: 
8810116300a0
  [ 215.740629] R10:  R11:  R12: 
881018917dce
  [ 215.826030] R13: 81c9be00 R14: 81c9be00 R15: 
881011630078
  [ 215.911432] FS: () GS:88103fec() 
knlGS:
  [ 216.008274] CS: 0010 DS:  ES:  CR0: 80050033
  [ 216.077032] CR2:  CR3: 001011b9d000 CR4: 
001406e0
  [ 216.162430] Stack:
  [ 216.186461] 8157d7f9 881011067100 881018917dce 
88101163
  [ 216.275407] 81c9be00 88103fec3918 8157e0db 

  [ 216.364352]    

  [ 216.453301] Call Trace:
  [ 216.482536]  [ 216.505533] [] ? 
ip_rcv_finish+0x99/0x320
  [ 216.575442] [] ip_rcv+0x25b/0x370
  [ 216.634842] [] __netif_receive_skb_core+0x2cb/0xa20
  [ 216.712965] [] __netif_receive_skb+0x18/0x60
  [ 216.783801] [] netif_receive_skb_internal+0x23/0x80
  [ 216.861921] [] netif_receive_skb+0x1c/0x70
  [ 216.930686] [] br_handle_frame_finish+0x1b9/0x5b0 [bridge]
  [ 217.016091] [] ? ___slab_alloc+0x1d0/0x440
  [ 217.084849] [] br_nf_pre_routing_finish+0x174/0x3d0 
[br_netfilter]
  [ 217.178568] [] ? br_nf_pre_routing+0x97/0x470 
[br_netfilter]
  [ 217.266052] [] ? br_handle_local_finish+0x80/0x80 [bridge]
  [ 217.351450] [] br_nf_pre_routing+0x1a7/0x470 
[br_netfilter]
  [ 217.437891] [] nf_iterate+0x5d/0x70
  [ 217.499367] [] nf_hook_slow+0x64/0xc0
  [ 217.562928] [] br_handle_frame+0x1b9/0x290 [bridge]
  [ 217.641048] [] ? br_handle_local_finish+0x80/0x80 [bridge]
  [ 217.726446] [] __netif_receive_skb_core+0x342/0xa20
  [ 217.804566] [] ? tcp4_gro_receive+0x126/0x1d0
  [ 217.876445] [] ? inet_gro_receive+0x1c6/0x250
  [ 217.948322] [] __netif_receive_skb+0x18/0x60
  [ 218.019161] [] netif_receive_skb_internal+0x23/0x80
  [ 

[Kernel-packages] [Bug 1672470] Re: ip_rcv_finish() NULL pointer kernel panic

[Dan Streetman]

I verified the Trusty kernel isn't affected, this only applies to Xenial
and later.

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

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

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

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

Title:
  ip_rcv_finish() NULL pointer kernel panic

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

Bug description:
  The br_netfilter module processes packets traveling through its
  bridge, and while processing each skb it places a special fake dst
  onto the skb.  When the skb leaves the bridge, it removes the fake dst
  and places a real dst onto it.  However, it uses a hook to do this,
  and when the br_netfilter module is unloading it unregisters that
  hook.  Any skbs that are currently being processed in the bridge by
  the br_netfilter module, but that leave the bridge after the hook is
  unregistered (or, during br_netfilter module load, before the hook is
  registered) will still have the fake dst; when other code then tries
  to process that dst, it causes a kernel panic because the dst is
  invalid.

  Recent upstream discussion:
  https://www.spinics.net/lists/netdev/msg416912.html

  Upstream patch (not yet merged into net-next):
  https://patchwork.ozlabs.org/patch/738275/

  example panic report:

  [ 214.518262] BUG: unable to handle kernel NULL pointer dereference at (null)
  [ 214.612199] IP: [< (null)>] (null)
  [ 214.672744] PGD 0 [ 214.696887] Oops: 0010 [#1] SMP [ 214.735697] Modules 
linked in: br_netfilter(+) tun 8021q bridge stp llc bonding iTCO_wdt 
iTCO_vendor_support tpm_tis tpm kvm_intel kvm irqbypass sb_edac edac_core ixgbe 
mdio ipmi_si ipmi_msghandler lpc_ich mfd_core mousedev evdev igb dca 
procmemro(O) nokeyctl(O) noptrace(O)
  [ 215.029240] CPU: 34 PID: 0 Comm: swapper/34 Tainted: G O 4.4.39 #1
  [ 215.116720] Hardware name: Cisco Systems Inc UCSC-C220-M3L/UCSC-C220-M3L, 
BIOS C220M3.2.0.13a.0.0713160937 07/13/16
  [ 215.241644] task: 882038fb4380 ti: 8810392b task.ti: 
8810392b
  [ 215.331207] RIP: 0010:[<>] [< (null)>] (null)
  [ 215.420877] RSP: 0018:88103fec3880 EFLAGS: 00010286
  [ 215.484436] RAX: 881011631000 RBX: 881011067100 RCX: 

  [ 215.569836] RDX:  RSI:  RDI: 
881011067100
  [ 215.655234] RBP: 88103fec38a8 R08: 0008 R09: 
8810116300a0
  [ 215.740629] R10:  R11:  R12: 
881018917dce
  [ 215.826030] R13: 81c9be00 R14: 81c9be00 R15: 
881011630078
  [ 215.911432] FS: () GS:88103fec() 
knlGS:
  [ 216.008274] CS: 0010 DS:  ES:  CR0: 80050033
  [ 216.077032] CR2:  CR3: 001011b9d000 CR4: 
001406e0
  [ 216.162430] Stack:
  [ 216.186461] 8157d7f9 881011067100 881018917dce 
88101163
  [ 216.275407] 81c9be00 88103fec3918 8157e0db 

  [ 216.364352]    

  [ 216.453301] Call Trace:
  [ 216.482536]  [ 216.505533] [] ? 
ip_rcv_finish+0x99/0x320
  [ 216.575442] [] ip_rcv+0x25b/0x370
  [ 216.634842] [] __netif_receive_skb_core+0x2cb/0xa20
  [ 216.712965] [] __netif_receive_skb+0x18/0x60
  [ 216.783801] [] netif_receive_skb_internal+0x23/0x80
  [ 216.861921] [] netif_receive_skb+0x1c/0x70
  [ 216.930686] [] br_handle_frame_finish+0x1b9/0x5b0 [bridge]
  [ 217.016091] [] ? ___slab_alloc+0x1d0/0x440
  [ 217.084849] [] br_nf_pre_routing_finish+0x174/0x3d0 
[br_netfilter]
  [ 217.178568] [] ? br_nf_pre_routing+0x97/0x470 
[br_netfilter]
  [ 217.266052] [] ? br_handle_local_finish+0x80/0x80 [bridge]
  [ 217.351450] [] br_nf_pre_routing+0x1a7/0x470 
[br_netfilter]
  [ 217.437891] [] nf_iterate+0x5d/0x70
  [ 217.499367] [] nf_hook_slow+0x64/0xc0
  [ 217.562928] [] br_handle_frame+0x1b9/0x290 [bridge]
  [ 217.641048] [] ? br_handle_local_finish+0x80/0x80 [bridge]
  [ 217.726446] [] __netif_receive_skb_core+0x342/0xa20
  [ 217.804566] [] ? tcp4_gro_receive+0x126/0x1d0
  [ 217.876445] [] ? inet_gro_receive+0x1c6/0x250
  [ 217.948322] [] __netif_receive_skb+0x18/0x60
  [ 218.019161] [] netif_receive_skb_internal+0x23/0x80
  [ 218.097281] [] napi_gro_receive+0xc3/0x110
  [ 218.166051] [] ixgbe_clean_rx_irq+0x52f/0xa70 [ixgbe]
  

[Kernel-packages] [Bug 1667567] Re: msleep() bug causes Nuvoton I2C TPM device driver delays

[Tim Gardner]

** Also affects: checksecurity (Ubuntu Zesty)
   Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
   Status: Incomplete

** Also affects: linux (Ubuntu Zesty)
   Importance: Undecided
   Status: Incomplete

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

** Changed in: linux (Ubuntu Zesty)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  msleep() bug causes Nuvoton I2C TPM device driver delays

Status in checksecurity package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Fix Committed
Status in checksecurity source package in Zesty:
  Incomplete
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  default desc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/checksecurity/+bug/1667567/+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 1490347] Re: [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy LMP Link Management Protocol) PIN codes

[Roger Lawhorn]

Same here.

Linux Mint 18.1 64bit Cinnamon Desktop (ubuntu 16.04), Bluetoothctl
v5.37.

After I wrote the below forum post I also implemented this udev change
which helped somewhat as I have an onboard bluetooth that I wanted to
disable after buying a "csr 4.0" usb dongle off of ebay. The GUI worked
better, but still no pair:

>sudo gedit /etc/udev/rules.d/81-bluetooth-hci.rules
SUBSYSTEM=="usb", ATTRS{idVendor}=="0cf3", ATTRS{idProduct}=="3004", 
ATTR{authorized}="0"

Here is the article I posted in a facebook forum with all the gory
details:

Been unable to use bluetooth for many years and many laptops. Bought a CSR v4.0 
dongle off of ebay.
>lsusb Bus 003 Device 011: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
>Dongle (HCI mode)

Even worse results.

In bluetoothctl (skipping the GUI):
[bluetooth]# list
Controller 00:1A:7D:DA:71:13 GT70-2PE #1 [default]
Controller 48:5A:B6:19:7F:30 GT70-2PE

#1 is the usb dongle I bought.
The other is the built-in Atheros in the laptop.

[bluetooth]# power on
Changing power on succeeded

[bluetooth]# scan on
Discovery started
[CHG] Controller 00:1A:7D:DA:71:13 Discovering: yes
[CHG] Device 48:5A:B6:19:7F:30 RSSI: -64
[CHG] Device 00:07:62:18:3D:C5 RSSI: -51

[bluetooth]# info 00:07:62:18:3D:C5
Device 00:07:62:18:3D:C5
Name: iMT525
Alias: iMT525
Class: 0x240404
Icon: audio-card
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: yes
RSSI: -51

I am trying to connect to the iMT525 speaker phone by Altec Lansing.

[bluetooth]# pair 00:07:62:18:3D:C5
Attempting to pair with 00:07:62:18:3D:C5
[CHG] Device 00:07:62:18:3D:C5 Connected: yes
Failed to pair: org.bluez.Error.AuthenticationRejected
[CHG] Device 00:07:62:18:3D:C5 Connected: no

Cannot pair though the default pair code is  for a sound device.

Any ideas?

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

Title:
  [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy
  LMP Link Management Protocol) PIN codes

Status in Bluez Utilities:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Wily:
  Triaged
Status in bluez source package in Xenial:
  Confirmed

Bug description:
  Bluez 5.3 does not have support for pairing with devices (such as
  keyboards) that use a PIN code for pairing.

  A mouse pairs correctly.

  From my research it seems as if the ChromeOS project developed patches
  to fix this and they are supposed to have been included in Bluez 5.4
  (that statement dated April 2013) but I've not yet identified them.

  "The agent's implementation in bt_console/bluetoothctl upstream is
  incomplete, missing some functions like DisplayPincode."

  https://code.google.com/p/chromium/issues/detail?id=222661

  Along with the loss of Headset profiles meaning VoIP applications can
  no longer use HSP/HFP profiles (requiring functionality yet to land in
  Ofono) this cripples the use of Bluetooth for much else than A2DP or
  mouse input.

  Attempting to pair with, for example, an Apple Wireless Keyboard that
  pairs and works correctly with 14.04 LTS, fails totally on 15.10.

  The mouse shown below is already paired, connected, and working.

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes
  [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes
  [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48
  [bluetooth]# pair 00:0A:95:4B:BD:C2
  Attempting to pair with 00:0A:95:4B:BD:C2

  >>> at this point nothing is happening

  >>> so I press Enter on the keyboard and...
  [agent] PIN code: 791166
  >>> I type 791166 Enter and ...
  [agent] PIN code: 237744
  >>> I type 237744 Enter and...
  [agent] PIN code: 358866
  >>> I type 358866 Enter and...
  Request PIN code
  [agent] Enter PIN code: 1234
  >>> I type 1234 Enter on the keyboard and 1234 at the prompt...
  Failed to pair: org.bluez.Error.AuthenticationFailed

  This cycle repeats in various permuations. Sometimes the final
  "Request PIN code" does not appear.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1490347/+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 1648388] Re: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting

[Joseph Salisbury]

Does the 4.11-rc1 kernel exhibit the bug on 14.04?

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

Title:
  Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system
  hangs while rebooting

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

Bug description:
  Install Ubuntu16.04 in RAID1 created by Intel RSTe no matter legacy mode or 
UEFI mode.
  System hangs while rebooting

  Not found the issue in RAID0
  No issue on Ubuntu14.04
  Driver-OS inbox support

  Below as error messages
  ===
  INFO:  task systemd-shutdow:1 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

  INFO:  task  jbd2/md126p2-8:1732 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

  INFO:  task ext4lazyinit:1873 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

  INFO:  task kworker/u66:4:3139 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  ===

  WORKAROUND: edit /etc/sysctl.conf with follow commands and the system don't 
hang while rebooting:
  vm.dirty_background_ratio=5
  vm.dirty_ratio=10
  kernel.panic=3
  kernel.hung_task_panic=1
  kernel.hung_task_timeout_secs=30

  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=f578df47-a1b8-4e66-bd37-904f943eb01b
  InstallationDate: Installed on 2016-12-15 (10 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  MachineType: Dell DCS6430G
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=bc552762-1955-44b8-a83e-2a414f0e0bd1 ro
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/22/2016
  dmi.bios.vendor: Dell
  dmi.bios.version: 2.0.3
  dmi.board.name: 038VV0
  dmi.board.vendor: Dell
  dmi.board.version: X01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell
  dmi.modalias: 
dmi:bvnDell:bvr2.0.3:bd03/22/2016:svnDell:pnDCS6430G:pvr:rvnDell:rn038VV0:rvrX01:cvnDell:ct23:cvr:
  dmi.product.name: DCS6430G
  dmi.sys.vendor: Dell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/+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 1673250] Re: Internal HUAWEI Mobile Broadband Module not showing up as USB device

[Joseph Salisbury]

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc2


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

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

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

Title:
  Internal HUAWEI Mobile Broadband Module not showing up as USB device

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  I am running an Acer P645 with internal USB UMTS modem.
  The modem works using a 16.04.1 live USB stick,
  but not on the installed on-disk 16.04.2.

  Below is the lsusb -v in from the live-USB where the UMTS modem works,
  first the USB Hub usb2, then the Huawei device. The information 
  from the running system where the modem does not show up is attached through 
apport.

  I also have access to dmesg on both systems, see further below
  for the successful case. I also tried to copy kernel and modules
  from the live-USB to the hadr disk, booted successfully,
  but still nothing in lsusb. I also tried a few times to use

  for i in /sys/bus/pci/drivers/[uoex]hci_hcd/*:*; do
    echo "${i##*/}" > "${i%/*}/unbind"
    echo "${i##*/}" > "${i%/*}/bind"
  done

  for resetting the bus, still the same.

  I would welcome some suggestions what to test, if there could be
  a firmware issue blocking the UMTS, if teh modem could be blacklisted
  (how do I check that ?) whether udev or systemd could be a problem,
  whether there could be a missing package in the HDD installation (which?!)
  or if UEFI in the boot chain ("sdhci: Secure Digital Host Controller 
Interface driver")
  could cause an issue.

  Or if it makes sense to manually run usb_modeswitch (how?)
  without the device even be in lsusb ?

  Yours,
  Steffen

  

  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   2.00
    bDeviceClass9 Hub
    bDeviceSubClass 0 Unused
    bDeviceProtocol 1 Single TT
    bMaxPacketSize064
    idVendor   0x1d6b Linux Foundation
    idProduct  0x0002 2.0 root hub
    bcdDevice4.04
    iManufacturer   3 Linux 4.4.0-31-generic xhci-hcd
    iProduct2 xHCI Host Controller
    iSerial 1 :00:14.0
    bNumConfigurations  1
    Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   25
  bNumInterfaces  1
  bConfigurationValue 1
  iConfiguration  0
  bmAttributes 0xe0
    Self Powered
    Remote Wakeup
  MaxPower0mA
  Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber0
    bAlternateSetting   0
    bNumEndpoints   1
    bInterfaceClass 9 Hub
    bInterfaceSubClass  0 Unused
    bInterfaceProtocol  0 Full speed (or root) hub
    iInterface  0
    Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x81  EP 1 IN
  bmAttributes3
    Transfer TypeInterrupt
    Synch Type   None
    Usage Type   Data
  wMaxPacketSize 0x0004  1x 4 bytes
  bInterval  12
  Hub Descriptor:
    bLength  11
    bDescriptorType  41
    nNbrPorts 9
    wHubCharacteristic 0x000a
  No power switching (usb 1.0)
  Per-port overcurrent protection
  TT think time 8 FS bits
    bPwrOn2PwrGood   10 * 2 milli seconds
    bHubContrCurrent  0 milli Ampere
    DeviceRemovable0x88 0x00
    PortPwrCtrlMask0xff 0xff
   Hub Port Status:
     Port 1: .0503 highspeed power enable connect
     Port 2: .0100 power
     Port 3: .0100 power
     Port 4: .0100 power
     Port 5: .0503 highspeed power enable connect
     Port 6: .0503 highspeed power enable connect
     Port 7: .0103 power enable connect
     Port 8: .0103 power enable connect
     Port 9: .0100 power
  Device Status: 0x0001
    Self Powered

  Bus 002 Device 006: ID 12d1:1570 Huawei Technologies Co., Ltd.
  

[Kernel-packages] [Bug 1673565] Re: BLUETOOTH

[Joseph Salisbury]

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

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc2


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

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

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

Title:
  BLUETOOTH

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth on my ELitebook doesnt work

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  muigai 1449 F pulseaudio
   /dev/snd/controlC0:  muigai 1449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Thu Mar 16 21:30:12 2017
  InstallationDate: Installed on 2016-04-25 (324 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook Folio 1040 G2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic 
root=UUID=ba86533b-18b7-4466-bc75-b3c1d7bf8771 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/19/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M76 Ver. 01.05
  dmi.board.name: 2270
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 81.29
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM76Ver.01.05:bd01/19/2016:svnHewlett-Packard:pnHPEliteBookFolio1040G2:pvrA3009DD18303:rvnHewlett-Packard:rn2270:rvrKBCVersion81.29:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook Folio 1040 G2
  dmi.product.version: A3009DD18303
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1673565/+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 1673635] Re: Touchpad doesn't work

[Joseph Salisbury]

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc2


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

Title:
  Touchpad doesn't work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Dell Inspiron N4110
  Touchpad doesn't work at all; not even in the LiveCD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1673635/+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 1672953] Re: ISST-LTE:pVM:roselp4:ubuntu16.04.2: number of numa_miss and numa_foreign wrong in numastat

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2017-March/083041.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/1672953

Title:
  ISST-LTE:pVM:roselp4:ubuntu16.04.2: number of numa_miss and
  numa_foreign wrong in numastat

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in aa-series:
  Fix Released

Bug description:
  == Comment: #0 - Ping Tian Han  - 2016-12-07 19:14:40 ==
  +++ This bug was initially created as a clone of Bug #148750 +++

  On roselp4, we got numastat as this:

  % sudo numastat  
 node0   node1
  numa_hit   0   0
  numa_miss  0  292054
  numa_foreign   0  292054
  interleave_hit 04100
  local_node 0   0
  other_node 0   0
  % uname -a   
  Linux roselp4 4.8.0-30-generic #32~16.04.1-Ubuntu SMP Fri Dec 2 03:43:52 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
  % 

  
  The number of numa_miss and numa_foreign looks wrong, because the manual says 
that "Each numa_miss has a numa_foreign on another node." and "Each 
numa_foreign has a numa_miss on another node." But the numbers of node0 are all 
zeros.

  
  == Comment: #18 - JIA HE  - 2017-02-20 00:24:26 ==
  hi, Ping Tian Han
  Please see the test result, is it what you expected?
  before the patches
  root@seedlp1:~# numastat
 node0   node2   node3
  numa_hit   0   0   0
  numa_miss  0  3525215466
  numa_foreign   0  3525215466
  interleave_hit 056285402
  local_node 0   0   0
  other_node 0   0   0
  root@seedlp1:~# 

  after the patches
  xinhui locking
  root@seedlp1:/boot# numastat
 node0   node2   node3
  numa_hit   0  2387664837
  numa_miss  0   0   0
  numa_foreign   0   0   0
  interleave_hit 048884777
  local_node 0   0   0
  other_node 0  2387664837

  == Comment: #19 - JIA HE  - 2017-02-20 00:28:14 ==
  New kernel is at 
http://kernel.stglabs.ibm.com/~hejianet/bug149763/linux-image-4.8.0-37-generic_4.8.0-37.39_ppc64el.deb

  md5: f3a57af05f0945f10b9d2841844f0fe4  linux-
  image-4.8.0-37-generic_4.8.0-37.39bug149763_ppc64el.deb

  == Comment: #20 - Ping Tian Han  - 2017-02-20 00:57:30 ==
  (In reply to comment #18)
  > hi, Ping Tian Han
  > Please see the test result, is it what you expected?
  > before the patches
  > root@seedlp1:~# numastat
  >node0   node2   node3
  > numa_hit   0   0   0
  > numa_miss  0  3525215466
  > numa_foreign   0  3525215466
  > interleave_hit 056285402
  > local_node 0   0   0
  > other_node 0   0   0
  > root@seedlp1:~# 
  > 
  > after the patches
  > xinhui locking
  > root@seedlp1:/boot# numastat
  >node0   node2   node3
  > numa_hit   0  2387664837
  > numa_miss  0   0   0
  > numa_foreign   0   0   0
  > interleave_hit 048884777
  > local_node 0   0   0
  > other_node 0  2387664837

  This looks good to me. Thanks.

  Please cherry pick the  patches below

  
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2df26639e708a88dcc22171949da638a9998f3bc

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=41b6167e8f746b475668f1da78599fc4284f18db

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

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

[Kernel-packages] [Bug 1672953] Re: ISST-LTE:pVM:roselp4:ubuntu16.04.2: number of numa_miss and numa_foreign wrong in numastat

[Tim Gardner]

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

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

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

** Changed in: linux (Ubuntu Aa-series)
   Status: New => Fix Released

** Changed in: linux (Ubuntu Zesty)
   Status: New => Fix Released

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

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu16.04.2: number of numa_miss and
  numa_foreign wrong in numastat

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in aa-series:
  Fix Released

Bug description:
  == Comment: #0 - Ping Tian Han  - 2016-12-07 19:14:40 ==
  +++ This bug was initially created as a clone of Bug #148750 +++

  On roselp4, we got numastat as this:

  % sudo numastat  
 node0   node1
  numa_hit   0   0
  numa_miss  0  292054
  numa_foreign   0  292054
  interleave_hit 04100
  local_node 0   0
  other_node 0   0
  % uname -a   
  Linux roselp4 4.8.0-30-generic #32~16.04.1-Ubuntu SMP Fri Dec 2 03:43:52 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
  % 

  
  The number of numa_miss and numa_foreign looks wrong, because the manual says 
that "Each numa_miss has a numa_foreign on another node." and "Each 
numa_foreign has a numa_miss on another node." But the numbers of node0 are all 
zeros.

  
  == Comment: #18 - JIA HE  - 2017-02-20 00:24:26 ==
  hi, Ping Tian Han
  Please see the test result, is it what you expected?
  before the patches
  root@seedlp1:~# numastat
 node0   node2   node3
  numa_hit   0   0   0
  numa_miss  0  3525215466
  numa_foreign   0  3525215466
  interleave_hit 056285402
  local_node 0   0   0
  other_node 0   0   0
  root@seedlp1:~# 

  after the patches
  xinhui locking
  root@seedlp1:/boot# numastat
 node0   node2   node3
  numa_hit   0  2387664837
  numa_miss  0   0   0
  numa_foreign   0   0   0
  interleave_hit 048884777
  local_node 0   0   0
  other_node 0  2387664837

  == Comment: #19 - JIA HE  - 2017-02-20 00:28:14 ==
  New kernel is at 
http://kernel.stglabs.ibm.com/~hejianet/bug149763/linux-image-4.8.0-37-generic_4.8.0-37.39_ppc64el.deb

  md5: f3a57af05f0945f10b9d2841844f0fe4  linux-
  image-4.8.0-37-generic_4.8.0-37.39bug149763_ppc64el.deb

  == Comment: #20 - Ping Tian Han  - 2017-02-20 00:57:30 ==
  (In reply to comment #18)
  > hi, Ping Tian Han
  > Please see the test result, is it what you expected?
  > before the patches
  > root@seedlp1:~# numastat
  >node0   node2   node3
  > numa_hit   0   0   0
  > numa_miss  0  3525215466
  > numa_foreign   0  3525215466
  > interleave_hit 056285402
  > local_node 0   0   0
  > other_node 0   0   0
  > root@seedlp1:~# 
  > 
  > after the patches
  > xinhui locking
  > root@seedlp1:/boot# numastat
  >node0   node2   node3
  > numa_hit   0  2387664837
  > numa_miss  0   0   0
  > numa_foreign   0   0   0
  > interleave_hit 048884777
  > local_node 0   0   0
  > other_node 0  2387664837

  This looks good to me. Thanks.

  Please cherry pick the  patches below

  
  

[Kernel-packages] [Bug 1396654] Re: C++ demangling support missing from perf

[Tim Gardner]

Added binutils-dev. libiberty-dev was already in the Build-deps

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

** Changed in: linux (Ubuntu Zesty)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  C++ demangling support missing from perf

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Incomplete
Status in linux source package in Yakkety:
  Incomplete
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  Hi,
  It appears that C++ demangling support is missing from linux-tools-3.16.0-24, 
on Utopic on arm64.

  Could the following please be added to the build dependencies for that 
package:
  libiberty-dev
  binutils-dev

  Installing the above and rebuilding the package fixed the problem for
  me.

  Cheers,
  --
  Steve
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  DistroRelease: Ubuntu 14.10
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,115200n8 ro
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  utopic utopic
  Uname: Linux 3.16.0-24-generic aarch64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to utopic on 2014-11-17 (9 days ago)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396654/+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 1671613] Re: POWER9: Additional power9 patches

[Tim Gardner]

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

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

Title:
  POWER9: Additional power9 patches

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

Bug description:
  Dear Canonical,

  Currently Ubuntu is having some issues on a POWER9 machine, as:

  
  [  443.933079] [ cut here ]
  [  443.933102] WARNING: CPU: 10 PID: 10243 at 
/build/linux-iMfvOW/linux-4.10.0/arch/powerpc/mm/fault.c:428 
do_page_fault+0x5d8/0x7d0
  [  443.933105] Modules linked in: vmx_crypto ofpart cmdlinepart 
ipmi_powernv powernv_flash ipmi_devintf mtd uio_pdrv_genirq ipmi_msghandler 
ibmpowernv opal_prd uio ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 ses 
enclosure scsi_transport_sas btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect 
sysimgblt fb_sys_fops crc32c_vpmsum drm i40e aacraid
  [  443.933206] CPU: 10 PID: 10243 Comm: apt-get Not tainted 
4.10.0-9-generic #11-Ubuntu
  [  443.933211] task: c007adbc2c00 task.stack: c007adc6
  [  443.933214] NIP: c00519d8 LR: c00515b4 CTR: 
0003
  [  443.933217] REGS: c007adc63b00 TRAP: 0700   Not tainted  
(4.10.0-9-generic)
  [  443.933219] MSR: 90029033 
  [  443.933237]   CR: 48248422  XER: 
  [  443.933240] CFAR: c005163c SOFTE: 1
 GPR00: c00515b4 c007adc63d80 c142c400 
c007ad0a3b60
 GPR04: 3fff7b7bc92c  0007fc02 

 GPR08: 0003 0001 c12ec400 

 GPR12: 4000 cfb85a00 0001 
3fff7d640ea8
 GPR16: 3fffdc1b6e78 3fffdc1b6e70 3fffdc1b6e68 
3fffdc1b6e58
 GPR20: 3fff7d640e00 ffc0 00030001 

 GPR24: 0054 c007b21e0b68 c007ad0a3b60 
c007b21e0b00
 GPR28: 3fff7b7bc92c 0800  
c007adc63ea0
  [  443.933307] NIP [c00519d8] do_page_fault+0x5d8/0x7d0
  [  443.933312] LR [c00515b4] do_page_fault+0x1b4/0x7d0
  [  443.933314] Call Trace:
  [  443.933320] [c007adc63d80] [c00515b4] 
do_page_fault+0x1b4/0x7d0 (unreliable)
  [  443.933328] [c007adc63e30] [c000a4e8] 
handle_page_fault+0x10/0x30
  [  443.92] Instruction dump:
  [  443.97] 6000 6042 71280007 4182fe1c 77a90800 4182fc94 
3d42ffec 892ab491
  [  443.933351] 2f89 409efc84 3921 992ab491 <0fe0> 4bfffc74 
7f86e378 7ec5b378
  [  443.933366] ---[ end trace 4798790ae3dab875 ]--- 

  
  ==

  
  We would like to include the following patches to fix it:

  * cee216a696b2004017a5ecb583366093d90b1568 mm/autonuma: don't use
  set_pte_at when updating protnone ptes

  * 288bc54949fc2625a4fd811a188fb200cc498946 mm/autonuma: let
  architecture override how the write bit should be stashed in a
  protnone pte.

  * 595cd8f256d24face93b2722927ec9c980419c26 mm/ksm: handle protnone
  saved writes when making page write protect

  * c137a2757b88658ce61c74b25ff650ecda7f09d8 switch ppc64 to its own
  implementation of saved write

  * db08f2030a173fdb95b2e8e28d82c4e8c04df2ac mm/gup: check for protnone
  only if it is a PTE entry

  * 9a8b300f2f7812ebf4630b8b40499da38b38e882 mm/thp/autonuma: use TNF
  flag instead of vm fault

  
   * power/mm: update pte_write and pte_wrprotect to handle savedwrite: 
http://ozlabs.org/~akpm/mmots/broken-out/power-mm-update-pte_write-and-pte_wrprotect-to-handle-savedwrite.patch

  * powerpc/mm: Handle protnone ptes on fork:
  http://ozlabs.org/~akpm/mmots/broken-out/powerpc-mm-handle-protnone-
  ptes-on-fork.patch

  
  Thanks

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

[Joseph Salisbury]

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

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

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

** This bug has been marked a duplicate of bug 1666421
   kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

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

Title:
  login screen freeze

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

Bug description:
  Running an up-to-date (as of Feb 25 2017) 16.04 / Unity on an old MSI
  U160 netbook.

  After a recent update to kernel 4.4.0-63 I have started getting frozen
  login screens. The touchpad and keyboard are completely dead (before I
  ever get to enter my password), and my only way out is to force
  shutdown.

  I can start GRUB on boot and go for an earlier version instead, but
  everything past 4.4.0-62 freezes in the same fashion (that's what I'm
  currently running as a temporary fix); a newer update to 4.4.0-64 has
  not fixed the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chirvasitua   1841 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Feb 25 03:42:57 2017
  HibernationDevice: RESUME=UUID=5e60245a-50f2-4f9c-97b2-d68560e38218
  InstallationDate: Installed on 2015-10-18 (495 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-N051
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=250be7ea-5182-43d2-b638-5c4a933b4942 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: EN051IMS.100
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-N051
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrEN051IMS.100:bd02/06/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-N051:pvrTobefilledbyO.E.M.:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-N051:rvrTobefilledbyO.E.M.:cvnMICRO-STARINTERNATIONALCO.,LTD:ct9:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-N051
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667920/+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 1673350] Re: dm-queue-length module is not included in installer/initramfs

[Mauricio Faria de Oliveira]

Thanks, @cyphermox and @smb.

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

Title:
  dm-queue-length module is not included in installer/initramfs

Status in hw-detect package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Fix Committed
Status in multipath-tools package in Ubuntu:
  Triaged
Status in hw-detect source package in Xenial:
  New
Status in initramfs-tools source package in Xenial:
  New
Status in linux source package in Xenial:
  In Progress
Status in multipath-tools source package in Xenial:
  New
Status in hw-detect source package in Yakkety:
  New
Status in initramfs-tools source package in Yakkety:
  New
Status in linux source package in Yakkety:
  New
Status in multipath-tools source package in Yakkety:
  New

Bug description:
  [Impact]
  Multipath users using EMC XtremIO storage as boot device or at install time 
may run into this issue. With the module unavailable the device is more often 
than not unavailable. Any users changing path selector to 'queue-length' with 
other storage devices may also be affected.

  [Test case]
  1) Install on multipath system using EMC XtremIO storage / OR:
   a) Start d-i install on qemu with multipath enabled
   b) exit to d-i menu
   c) modify /etc/multipath.conf to define path selector as 'queue-length' for 
the local qemu device.
   d) restart multipathd if necessary.
  2) Try to complete the install, setting up storage as multipath and using the 
multipath device as boot disk.
  3) Reboot to disk.

  In a success case, the install should complete successfully without
  requiring manual configuration from the user to support the multipath
  storage past the normal detection of multipath and partitioning.

  In a failure case, the install may not complete, or rebooting may fail
  or lead to a system booted on a single path of the multipath device
  (ie. / on /dev/sda2 rather than /dev/mpatha2).

  [Regression Potential]
  The inclusion of a new multipath path selector driver should not cause any 
regressions, but any failure to detect, configure or boot on multipath devices 
following this change on XtremIO hardware or otherwise would constitute a 
regression potentially caused by this change.

  ---

  ---Problem Description---
  dm-queue-length module is not included in installer/initramfs

  On Ubuntu, multipath devices using the 'queue-length' path selector
  are non-functional on both the installer and initramfs environments;
  because the 'dm-queue-length' kernel module is not included in them.

  The multipath-modules.udeb (src:linux) does not include it in the installer,
  nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs.

  One example is the EMC XtremIO storage, which has 'queue-length' defined as
  its path selector in the default multipath configuration, at least on 16.04.

  Other products may be affected if they are manually configured to use that
  path selector (e.g., via /etc/multipath.conf), and the mere switch of that
  might render the system _unbootable_ if booting from multipath, since the
  initramfs is affected.

  More recently this and another storage changed default path selectors out
  of 'queue-length', however, it's virtually possible for any storage system
  to be affected, with the described manual configuration change.  So, this
  change is also desired on for the next stable release, 17.04, and later.

  Patches are provided for 16.04 and 17.04.

  Error logs in LP comment #6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1673350/+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 1673350] Re: dm-queue-length module is not included in installer/initramfs

[Tim Gardner]

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

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

Title:
  dm-queue-length module is not included in installer/initramfs

Status in hw-detect package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Fix Committed
Status in multipath-tools package in Ubuntu:
  Triaged
Status in hw-detect source package in Xenial:
  New
Status in initramfs-tools source package in Xenial:
  New
Status in linux source package in Xenial:
  In Progress
Status in multipath-tools source package in Xenial:
  New
Status in hw-detect source package in Yakkety:
  New
Status in initramfs-tools source package in Yakkety:
  New
Status in linux source package in Yakkety:
  New
Status in multipath-tools source package in Yakkety:
  New

Bug description:
  [Impact]
  Multipath users using EMC XtremIO storage as boot device or at install time 
may run into this issue. With the module unavailable the device is more often 
than not unavailable. Any users changing path selector to 'queue-length' with 
other storage devices may also be affected.

  [Test case]
  1) Install on multipath system using EMC XtremIO storage / OR:
   a) Start d-i install on qemu with multipath enabled
   b) exit to d-i menu
   c) modify /etc/multipath.conf to define path selector as 'queue-length' for 
the local qemu device.
   d) restart multipathd if necessary.
  2) Try to complete the install, setting up storage as multipath and using the 
multipath device as boot disk.
  3) Reboot to disk.

  In a success case, the install should complete successfully without
  requiring manual configuration from the user to support the multipath
  storage past the normal detection of multipath and partitioning.

  In a failure case, the install may not complete, or rebooting may fail
  or lead to a system booted on a single path of the multipath device
  (ie. / on /dev/sda2 rather than /dev/mpatha2).

  [Regression Potential]
  The inclusion of a new multipath path selector driver should not cause any 
regressions, but any failure to detect, configure or boot on multipath devices 
following this change on XtremIO hardware or otherwise would constitute a 
regression potentially caused by this change.

  ---

  ---Problem Description---
  dm-queue-length module is not included in installer/initramfs

  On Ubuntu, multipath devices using the 'queue-length' path selector
  are non-functional on both the installer and initramfs environments;
  because the 'dm-queue-length' kernel module is not included in them.

  The multipath-modules.udeb (src:linux) does not include it in the installer,
  nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs.

  One example is the EMC XtremIO storage, which has 'queue-length' defined as
  its path selector in the default multipath configuration, at least on 16.04.

  Other products may be affected if they are manually configured to use that
  path selector (e.g., via /etc/multipath.conf), and the mere switch of that
  might render the system _unbootable_ if booting from multipath, since the
  initramfs is affected.

  More recently this and another storage changed default path selectors out
  of 'queue-length', however, it's virtually possible for any storage system
  to be affected, with the described manual configuration change.  So, this
  change is also desired on for the next stable release, 17.04, and later.

  Patches are provided for 16.04 and 17.04.

  Error logs in LP comment #6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1673350/+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 1673535] Re: drm/ast: Fix AST2400 POST failure without BMC FW or VBIOS

[Tim Gardner]

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

** This bug has been marked a duplicate of bug 1673118
   Zesty update to v4.10.3 stable release

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

Title:
  drm/ast: Fix AST2400 POST failure without BMC FW or VBIOS

Status in linux package in Ubuntu:
  New

Bug description:
  Canonical,

  Please add patch into 17.04:

  commit 3856081eede297b617560b85e948cfb00bb395ec

  
  drm/ast: Fix AST2400 POST failure without BMC FW or VBIOS
  
  The current POST code for the AST2300/2400 family doesn't work properly
  if the chip hasn't been initialized previously by either the BMC own FW
  or the VBIOS. This fixes it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1673535/+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 1673118] Re: Zesty update to v4.10.3 stable release

[Launchpad Bug Tracker]

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

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

Title:
  Zesty update to v4.10.3 stable release

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

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.10.3 stable release shall be
  applied:

  serial: 8250_pci: Add MKS Tenta SCOM-0800 and SCOM-0801 cards
  KVM: s390: Disable dirty log retrieval for UCONTROL guests
  KVM: VMX: use correct vmcs_read/write for guest segment selector/base
  Bluetooth: Add another AR3012 04ca:3018 device
  phy: qcom-ufs: Don't kfree devres resource
  phy: qcom-ufs: Fix misplaced jump label
  s390/qdio: clear DSCI prior to scanning multiple input queues
  s390/dcssblk: fix device size calculation in dcssblk_direct_access()
  s390/kdump: Use "LINUX" ELF note name instead of "CORE"
  s390/chsc: Add exception handler for CHSC instruction
  s390: TASK_SIZE for kernel threads
  s390/topology: correct allocation of topology information
  s390: make setup_randomness work
  s390: use correct input data address for setup_randomness
  net: mvpp2: fix DMA address calculation in mvpp2_txq_inc_put()
  cxl: Prevent read/write to AFU config space while AFU not configured
  cxl: fix nested locking hang during EEH hotplug
  brcmfmac: fix incorrect event channel deduction
  mnt: Tuck mounts under others instead of creating shadow/side mounts.
  IB/ipoib: Fix deadlock between rmmod and set_mode
  IB/IPoIB: Add destination address when re-queue packet
  IB/mlx5: Fix out-of-bound access
  IB/SRP: Avoid using IB_MR_TYPE_SG_GAPS
  IB/srp: Avoid that duplicate responses trigger a kernel bug
  IB/srp: Fix race conditions related to task management
  Btrfs: fix data loss after truncate when using the no-holes feature
  orangefs: Use RCU for destroy_inode
  memory/atmel-ebi: Fix ns <-> cycles conversions
  tracing: Fix return value check in trace_benchmark_reg()
  ktest: Fix child exit code processing
  ceph: remove req from unsafe list when unregistering it
  target: Fix NULL dereference during LUN lookup + active I/O shutdown
  drivers/pci/hotplug: Handle presence detection change properly
  drivers/pci/hotplug: Fix initial state for empty slot
  nlm: Ensure callback code also checks that the files match
  pwm: pca9685: Fix period change with same duty cycle
  xtensa: move parse_tag_fdt out of #ifdef CONFIG_BLK_DEV_INITRD
  nfit, libnvdimm: fix interleave set cookie calculation
  mac80211: flush delayed work when entering suspend
  mac80211: don't reorder frames with SN smaller than SSN
  mac80211: don't handle filtered frames within a BA session
  mac80211: use driver-indicated transmitter STA only for data frames
  drm/amdgpu: add more cases to DCE11 possible crtc mask setup
  drm/amdgpu/pm: check for headless before calling compute_clocks
  Revert "drm/amdgpu: update tile table for oland/hainan"
  drm/ast: Fix AST2400 POST failure without BMC FW or VBIOS
  drm/radeon: handle vfct with multiple vbios images
  drm/edid: Add EDID_QUIRK_FORCE_8BPC quirk for Rotel RSX-1058
  drm/ttm: Make sure BOs being swapped out are cacheable
  drm/vmwgfx: Work around drm removal of control nodes
  drm/imx: imx-tve: Do not set the regulator voltage
  drm/atomic: fix an error code in mode_fixup()
  drm/i915/gvt: Disable access to stolen memory as a guest
  drm: Cancel drm_fb_helper_dirty_work on unload
  drm: Cancel drm_fb_helper_resume_work on unload
  drm/i915: Recreate internal objects with single page segments if dmar fails
  drm/i915: Avoid spurious WARNs about the wrong pipe in the PPS code
  drm/i915: Check for timeout completion when waiting for the rq to submitted
  drm/i915: Pass timeout==0 on to i915_gem_object_wait_fence()
  drm/i915: Fix not finding the VBT when it overlaps with OPREGION_ASLE_EXT
  libceph: use BUG() instead of BUG_ON(1)
  x86, mm: fix gup_pte_range() vs DAX mappings
  x86/tlb: Fix tlb flushing when lguest clears PGE
  thp: fix another corner case of munlock() vs. THPs
  mm: do not call mem_cgroup_free() from within mem_cgroup_alloc()
  kasan: resched in quarantine_remove_cache()
  fat: fix using uninitialized fields of fat_inode/fsinfo_inode
  drivers: hv: Turn off write permission on the 

[Kernel-packages] [Bug 1671760] Re: Xen HVM guests running linux 4.10 fail to boot on Intel hosts

[Stefan Bader]

For Xenial, reinstalled Xen from proposed. Booted Zesty 4.10 HVM ok.

** Tags added: verification-done-xenial

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

Title:
  Xen HVM guests running linux 4.10 fail to boot on Intel hosts

Status in linux package in Ubuntu:
  Won't Fix
Status in xen package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Invalid
Status in xen source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Invalid
Status in xen source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Invalid
Status in xen source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Won't Fix
Status in xen source package in Zesty:
  Fix Released

Bug description:
  Starting with Linux kernel 4.10, the kernel does some sanity checking
  on the TSC_ADJUST MSR. Xen has implemented some support for that MSR
  in the hypervisor (Xen 4.3 and later) for HVM guests. But boot and
  secondary vCPUs are set up inconsistently. This causes the boot of a
  4.10 HVM guest to hang early on boot.

  This was fixed in the hypervisor by:

    commit 98297f09bd07bb63407909aae1d309d8adeb572e
    x86/hvm: do not set msr_tsc_adjust on hvm_set_guest_tsc_fixed

  That fix would be contained in 4.6.5 and 4.7.2 and would be in 4.8.1
  (not released, yet) which mean that Ubuntu 14.04/16.04/16.10 and 17.04
  currently are affected.

  ---

  SRU Justification:

  Impact: Without the TSC_ADJUST MSR fix, 4.10 and later kernels will
  get stuck at boot when running as (PV)HVM guests on Xen 4.3 and later.

  Fix: Above fix either individually applied or as part of Xen stable
  stream (for Xen 4.7.x and 4.6.x) resolves the issue.

  Testcase:
  - Requires Intel based host which supports the TSC_ADJUST MSR
  - Configured as Xen host
  - HVM guest running Zesty/17.04
  - Stuck at boot before, normal booting OS after

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671760/+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 1666897] Re: snaps with classic + jailmode confinement started to fail on zesty

[Denis Bernard]

This fix breaks Ubuntu 16.04: update-manager did a partial update. It
elected to keep snapd (2.22.6) and remove linux-generic and linux-image-
generic. This plus a kernel update (4.4.0.67), I ended up with kernel
4.4.0.67 without linux-image-extras of the same version. After reboot,
no network, no sound, and so on.

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

Title:
  snaps with classic + jailmode confinement started to fail on zesty

Status in snapd:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We just noticed that zesty stated to fail when a snap using classic
  confinement is installed in jailmode.

  $ snap install --jailmode --classic python0
  $ python0 (doesn't work)
  /snap/python0/2/usr/bin/python0: error while loading shared libraries: 
libm.so.6: failed to map segment from shared object

  And in the system log you can see:

  [ 2929.841318] audit: type=1400 audit(1487770576.927:40):
  apparmor="DENIED" operation="file_mmap" profile="snap.python0.python0"
  name="/snap/core/1264/lib/x86_64-linux-gnu/libm-2.23.so" pid=5235
  comm="python0" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1666897/+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 1671614] s2lp6g003 (s390x.zKVM) - tests ran: 10, failed: 0

[Brad Figg]

tests ran:  10, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-13.15-generic/s2lp6g003__4.10.0-13.15__2017-03-17_11-15-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/1671614

Title:
  linux: 4.10.0-13.15 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Confirmed
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This bug is for tracking the 4.10.0-13.15 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
  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/1671614/+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 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)

[Pedro R]

Kai-Heng Feng, thanks for your time.
Here it is the file as instructed.

** Attachment added: "acpi-dump"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653456/+attachment/4839389/+files/acpi-dump

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

Title:
  ASUS G752VS: Touchpad and Fn keys not working (Ubuntu
  16.04.1/16.10/17.04)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Non-Optimus laptop ASUS G752VS-GC063D-CST256.
  17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 
NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 
802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 
x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS.

  Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and
  17.04, among other problems I found that touchpad and Fn keys (all
  except volume control) doesn't work on my brand new ASUS G752VS.

  It is very hard even to try Ubuntu 16.10 and 17.04 because of the
  missing mouse pointer. This problem must be related to a video driver
  because if after installing one is capable to install Nvidia drivers -
  problem is solved. This problem doesn't exist both while trying and
  installing Ubuntu 16.04.1!

  I'm currently on Windows 10, and this bug report is made from Ubuntu
  16.04.1 LiveCD.

  
  dmesg | grep -i elan
  [  101.082929] input: ELAN1203:00 04F3:3043 Touchpad as 
/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11
  [  101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID 
v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00

  
  xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ G-SPY USB Gaming Mouse  id=10   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=13   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=14   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN1203:00 04F3:3043 Touchpad  id=15   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ G-SPY USB Gaming Mouse  id=9[slave  
keyboard (3)]
  ↳ USB2.0 HD UVC WebCamid=11   [slave  
keyboard (3)]
  ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=12   [slave  
keyboard (3)]
  ↳ Asus WMI hotkeysid=16   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=17   [slave  
keyboard (3)]

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

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

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

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

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

  I: Bus=0003 Vendor=04d9 Product=a070 Version=0110
  N: Name="G-SPY USB Gaming Mouse"
  P: Phys=usb-:00:14.0-2/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:04D9:A070.0001/input/input5
  U: Uniq=
  H: Handlers=sysrq kbd event5 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=e080ffdf01cf fffe
  B: MSC=10
  B: LED=1f

  I: 

[Kernel-packages] [Bug 1600624] Re: MacBook wifi doesn't work (brcmfmac)

[archenroot]

I had similar issue on Dell XPS 15 with:
02:00.0 Network controller: Broadcom Corporation BCM43602 802.11ac Wireless LAN 
SoC (rev 01)
Subsystem: Dell BCM43602 802.11ac Wireless LAN SoC
Kernel driver in use: brcmfmac
Kernel modules: brcmfmac

I resolved this by loading the proper firmware into kernel. I am using
Refind with support of UEFI bios, so my kernel is self loaded (no Grub
or Lilo, etc.) including the firmware for specific hardware.

Here are some hints how I resolved non-working wifi. The .txt file is
not available for some of brfmac devices (as my case as well).

Look here for detailed analysis and resolution, be patient as was also 
resolving how to properly load the firmware into kernel:
https://forums.gentoo.org/viewtopic-t-1060038.html?sid=0c86112016dd3a3410cd6a1fe9fe27d1

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

Title:
  MacBook wifi doesn't work (brcmfmac)

Status in linux package in Ubuntu:
  Expired

Bug description:
  wifi doesn't work at all. Output from dmesg:
  [...]
  brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt 
failed with error -2
  ...
  brcmf_cfg80211_reg_notifier: not a ISO3166 code

  There is no file brcmfmac43602-pcie.txt anywhere on the system.
  However, /lib/firmware/brcm/brcmfmac43602-pcie.bin does exist.

  Iw reg get outputs:
  sudo iw reg get
  country DK: DFS-ETSI
   (2402 - 2482 @ 40), (N/A, 20), (N/A)
   (5170 - 5250 @ 80), (N/A, 20), (N/A)
   (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS
   (5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS
   (57000 - 66000 @ 2160), (N/A, 40), (N/A)

  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/controlC1:  lars   2010 F pulseaudio
   /dev/snd/controlC0:  lars   2010 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Jul 10 19:41:18 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a45b9984-4de8-49e3-ba57-a98ae560ad61
  InstallationDate: Installed on 2016-01-30 (162 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=d3ba9d27-321b-45cb-99f2-776b10c1dc7a 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: Upgraded to xenial on 2016-04-22 (78 days ago)
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B15.1510261437
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B15.1510261437:bd10/26/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1600624/+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 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)

[aljosa]

Hello Kai-Heng Feng,
thank you very much for your instruction. Here it is, file "acpi-dump" attached.

** Attachment added: "acpi-dump"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653456/+attachment/4839363/+files/acpi-dump

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

Title:
  ASUS G752VS: Touchpad and Fn keys not working (Ubuntu
  16.04.1/16.10/17.04)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Non-Optimus laptop ASUS G752VS-GC063D-CST256.
  17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 
NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 
802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 
x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS.

  Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and
  17.04, among other problems I found that touchpad and Fn keys (all
  except volume control) doesn't work on my brand new ASUS G752VS.

  It is very hard even to try Ubuntu 16.10 and 17.04 because of the
  missing mouse pointer. This problem must be related to a video driver
  because if after installing one is capable to install Nvidia drivers -
  problem is solved. This problem doesn't exist both while trying and
  installing Ubuntu 16.04.1!

  I'm currently on Windows 10, and this bug report is made from Ubuntu
  16.04.1 LiveCD.

  
  dmesg | grep -i elan
  [  101.082929] input: ELAN1203:00 04F3:3043 Touchpad as 
/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11
  [  101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID 
v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00

  
  xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ G-SPY USB Gaming Mouse  id=10   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=13   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=14   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN1203:00 04F3:3043 Touchpad  id=15   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ G-SPY USB Gaming Mouse  id=9[slave  
keyboard (3)]
  ↳ USB2.0 HD UVC WebCamid=11   [slave  
keyboard (3)]
  ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=12   [slave  
keyboard (3)]
  ↳ Asus WMI hotkeysid=16   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=17   [slave  
keyboard (3)]

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

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

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

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

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

  I: Bus=0003 Vendor=04d9 Product=a070 Version=0110
  N: Name="G-SPY USB Gaming Mouse"
  P: Phys=usb-:00:14.0-2/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:04D9:A070.0001/input/input5
  U: Uniq=
  H: Handlers=sysrq kbd event5 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=e080ffdf01cf fffe
  B: 

[Kernel-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones

[Alessio Tona]

I got it to work, but you need to set it up manually every time you
reboot. First I close bluetooth and bluez by effectively stopping them
(not restarting), then starting them again using systemctl stop/start
bluetooth and sudo  /etc/init.d/bluetooth start/stop. Then I start bluez
manager and connect my device using setup via audio sink. Then you have
to manually change sound to the headphones. I am a newbie with scripts,
maybe someone more experienced than me can make a script that does all
these actions at boot.

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

Title:
  Fails to pair with Bose QC35 headphones

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  I am unable to pair the Bose QC35 BT headphones with Ubuntu, either
  Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez
  5.41 from installed from yakkety archive), nor using Ubuntu Touch rc-
  proposed build for Turbo #174. I'm trying to pair through the normal
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

  bluetoothctl: http://pastebin.ubuntu.com/23256457/
  btmon: http://pastebin.ubuntu.com/23256471/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+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 1671614] s2lp6g003 (s390x.zKVM) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-13.15-generic/s2lp6g003__4.10.0-13.15__2017-03-17_11-11-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/1671614

Title:
  linux: 4.10.0-13.15 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Confirmed
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This bug is for tracking the 4.10.0-13.15 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
  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/1671614/+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 1673741] 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/1673741

Title:
  package linux-image-generic 4.4.0.66.70 failed to install/upgrade:
  problemas de dependência - deixando desconfigurado

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  package linux-image-generic 4.4.0.66.70 failed to install/upgrade:
  problemas de dependência - deixando desconfigurado

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.66.70
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  leonardo   1737 F pulseaudio
  Date: Thu Mar 16 02:20:05 2017
  ErrorMessage: problemas de dependência - deixando desconfigurado
  HibernationDevice: RESUME=UUID=4293c5d0-9982-4218-8676-22c98ba5
  InstallationDate: Installed on 2016-12-28 (78 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=e09c2c9c-0307-47f9-add7-e9bad90ab57a ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.8
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-generic 4.4.0.66.70 failed to install/upgrade: 
problemas de dependência - deixando desconfigurado
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1601
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LX2 R2.0
  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.:bvr1601:bd11/27/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2R2.0: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/linux/+bug/1673741/+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 1673741] [NEW] package linux-image-generic 4.4.0.66.70 failed to install/upgrade: problemas de dependência - deixando desconfigurado

[Leonardo]

Public bug reported:

package linux-image-generic 4.4.0.66.70 failed to install/upgrade:
problemas de dependência - deixando desconfigurado

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-generic 4.4.0.66.70
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  leonardo   1737 F pulseaudio
Date: Thu Mar 16 02:20:05 2017
ErrorMessage: problemas de dependência - deixando desconfigurado
HibernationDevice: RESUME=UUID=4293c5d0-9982-4218-8676-22c98ba5
InstallationDate: Installed on 2016-12-28 (78 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: System manufacturer System Product Name
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=e09c2c9c-0307-47f9-add7-e9bad90ab57a ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.8
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-image-generic 4.4.0.66.70 failed to install/upgrade: 
problemas de dependência - deixando desconfigurado
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/27/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1601
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H61-M LX2 R2.0
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.:bvr1601:bd11/27/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2R2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-package third-party-packages xenial

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

Title:
  package linux-image-generic 4.4.0.66.70 failed to install/upgrade:
  problemas de dependência - deixando desconfigurado

Status in linux package in Ubuntu:
  New

Bug description:
  package linux-image-generic 4.4.0.66.70 failed to install/upgrade:
  problemas de dependência - deixando desconfigurado

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.66.70
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  leonardo   1737 F pulseaudio
  Date: Thu Mar 16 02:20:05 2017
  ErrorMessage: problemas de dependência - deixando desconfigurado
  HibernationDevice: RESUME=UUID=4293c5d0-9982-4218-8676-22c98ba5
  InstallationDate: Installed on 2016-12-28 (78 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=e09c2c9c-0307-47f9-add7-e9bad90ab57a ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.8
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-generic 4.4.0.66.70 failed to install/upgrade: 
problemas de dependência - deixando desconfigurado
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1601
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LX2 R2.0
  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.:bvr1601:bd11/27/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2R2.0: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:

[Kernel-packages] [Bug 1591669] Re: duplicate touchpad reported and syndaemon/synclient does not work

[fish]

Have a XPS 13 9350 DE and looks like I'm affected by the same issue and
also suspend/resume removes the device. Yet I have several issues and it
doesn't seem to matter whether the 'fake' touchpad was removed by
suspend/resume.

For me too the mouse isn't disabled when typing but this is only
sometimes a problem. It seems there is some other heuristic going on
which prevents accidentially moving the mouse (palm detection?). Other
times though it's a problem and I haven't figured out what this depends
on.

But my main problem is that the middle mouse emulation never worked for
me, just never isolated this enough to fill an issue. Going to test some
newer kernels too, maybe this is related to this issue here too.

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

Title:
  duplicate touchpad reported and syndaemon/synclient does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is on a Dell XPS 13 9350 DE running ubuntu 16.04.
  This laptop has a touchpad and a touchscreen.
  I'm reporting here about the touchpad.

  One can see from Xorg.0.log and "xinput list" that *two* touchpads are
  registered by the system

  one is called "DLL0704:01 06CB:76AE Touchpad"
  and the other "SynPS/2 Synaptics TouchPad"

  As a result, syndaemon is not working.
  To check this, open two terminals, press and hold some key, like "e" in one 
of them. It starts filling with "eee". Now while holding the key, use the 
touchpad to tap on the other terminal. Then "" fills the new terminal.
  Expected behaviour:
  tapping on the other terminal should have no effet, the "e"'s should continue 
to fill the first terminal.

  Moreover, configuring the touchpad with synclient is not working
  either.

  FIX:

  Since invoking
  xinput disable "SynPS/2 Synaptics TouchPad"
  has no effect, it is clear that this one is a "false" touchpad.

  Hence this fix is:
  Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf

  I added, line 29:

  Section "InputClass"
  Identifier "touchpad ignore SynPS/2 Synaptics duplicate"
  MatchProduct "SynPS/2 Synaptics TouchPad"
  Option "Ignore" "on"
  EndSection

  Now it works. The touchpad is correctly disabled when using the
  keyboard, and moreover I can configure it using synclient, or adding a
  file to /etc/X11/xorg.conf.d/

  Of course this fix is not universal because I had to use the precise
  name of the "false touchpad" as reported by xinput.

  
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  san1697 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7
  InstallationDate: Installed on 2016-06-03 (9 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia
   Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp.
   Bus 001 Device 002: ID 8087:0a2b Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed 
root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-24-generic N/A
   linux-backports-modules-4.4.0-24-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-24-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/01/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.name: 09JHRY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1591669/+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 569445] Re: [Lucid Beta2] Wifi connectivity dies after a minute, activity light flashes constantly

[madbiologist]

** Changed in: wireless-crda (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [Lucid Beta2] Wifi connectivity dies after a minute, activity light
  flashes constantly

Status in wireless-crda package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: wireless-crda

  I do hope I've picked the right package for this. Investigators, feel
  free to email me with whatever bash commands you need me to find out
  more about the hardware.

  The problem is that wireless in Lucid is dying for me after about a
  minute or so, and the activity light on my netbook just flashes. The
  wireless monitor at the top of the screen still thinks it's connected.
  It's like it's out of sync or something.

  This doesn't happen under Win7 on this hardware, nor does it happen to
  other devices in my house on the network. Also, I wasn't having this
  problem under Lucid Beta 1

  I have an Acer Aspire (Olympic Variant) 1410
  Win7 reports the adapter as Intel WiFi Link 1000 BGN

  The wireless router I'm using is a DLink DIR-628. The connection is
  OPEN.

  Helpme help you help me! Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-crda/+bug/569445/+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 569445] Re: [Lucid Beta2] Wifi connectivity dies after a minute, activity light flashes constantly

[madbiologist]

Official support for Ubuntu 10.04 "Lucid Lynx" has ended. If this bug is
still occurring on Ubuntu 16.10 "Yakkety Yak", please run ubuntu-bug to
file a new bug report so that we can get a fresh set of log files and
system info.


** Tags added: lucid

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

Title:
  [Lucid Beta2] Wifi connectivity dies after a minute, activity light
  flashes constantly

Status in wireless-crda package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: wireless-crda

  I do hope I've picked the right package for this. Investigators, feel
  free to email me with whatever bash commands you need me to find out
  more about the hardware.

  The problem is that wireless in Lucid is dying for me after about a
  minute or so, and the activity light on my netbook just flashes. The
  wireless monitor at the top of the screen still thinks it's connected.
  It's like it's out of sync or something.

  This doesn't happen under Win7 on this hardware, nor does it happen to
  other devices in my house on the network. Also, I wasn't having this
  problem under Lucid Beta 1

  I have an Acer Aspire (Olympic Variant) 1410
  Win7 reports the adapter as Intel WiFi Link 1000 BGN

  The wireless router I'm using is a DLink DIR-628. The connection is
  OPEN.

  Helpme help you help me! Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-crda/+bug/569445/+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 569445] Re: [Lucid Beta2] Wifi connectivity dies after a minute, activity light flashes constantly

[Launchpad Bug Tracker]

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

** Changed in: wireless-crda (Ubuntu)
   Status: New => Confirmed

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

Title:
  [Lucid Beta2] Wifi connectivity dies after a minute, activity light
  flashes constantly

Status in wireless-crda package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: wireless-crda

  I do hope I've picked the right package for this. Investigators, feel
  free to email me with whatever bash commands you need me to find out
  more about the hardware.

  The problem is that wireless in Lucid is dying for me after about a
  minute or so, and the activity light on my netbook just flashes. The
  wireless monitor at the top of the screen still thinks it's connected.
  It's like it's out of sync or something.

  This doesn't happen under Win7 on this hardware, nor does it happen to
  other devices in my house on the network. Also, I wasn't having this
  problem under Lucid Beta 1

  I have an Acer Aspire (Olympic Variant) 1410
  Win7 reports the adapter as Intel WiFi Link 1000 BGN

  The wireless router I'm using is a DLink DIR-628. The connection is
  OPEN.

  Helpme help you help me! Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-crda/+bug/569445/+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 1673350] Re: dm-queue-length module is not included in installer/initramfs

[Stefan Bader]

Prepared a patch and sent to the kernel-team mailing list.

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

Title:
  dm-queue-length module is not included in installer/initramfs

Status in hw-detect package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in multipath-tools package in Ubuntu:
  Triaged
Status in hw-detect source package in Xenial:
  New
Status in initramfs-tools source package in Xenial:
  New
Status in linux source package in Xenial:
  In Progress
Status in multipath-tools source package in Xenial:
  New
Status in hw-detect source package in Yakkety:
  New
Status in initramfs-tools source package in Yakkety:
  New
Status in linux source package in Yakkety:
  New
Status in multipath-tools source package in Yakkety:
  New

Bug description:
  [Impact]
  Multipath users using EMC XtremIO storage as boot device or at install time 
may run into this issue. With the module unavailable the device is more often 
than not unavailable. Any users changing path selector to 'queue-length' with 
other storage devices may also be affected.

  [Test case]
  1) Install on multipath system using EMC XtremIO storage / OR:
   a) Start d-i install on qemu with multipath enabled
   b) exit to d-i menu
   c) modify /etc/multipath.conf to define path selector as 'queue-length' for 
the local qemu device.
   d) restart multipathd if necessary.
  2) Try to complete the install, setting up storage as multipath and using the 
multipath device as boot disk.
  3) Reboot to disk.

  In a success case, the install should complete successfully without
  requiring manual configuration from the user to support the multipath
  storage past the normal detection of multipath and partitioning.

  In a failure case, the install may not complete, or rebooting may fail
  or lead to a system booted on a single path of the multipath device
  (ie. / on /dev/sda2 rather than /dev/mpatha2).

  [Regression Potential]
  The inclusion of a new multipath path selector driver should not cause any 
regressions, but any failure to detect, configure or boot on multipath devices 
following this change on XtremIO hardware or otherwise would constitute a 
regression potentially caused by this change.

  ---

  ---Problem Description---
  dm-queue-length module is not included in installer/initramfs

  On Ubuntu, multipath devices using the 'queue-length' path selector
  are non-functional on both the installer and initramfs environments;
  because the 'dm-queue-length' kernel module is not included in them.

  The multipath-modules.udeb (src:linux) does not include it in the installer,
  nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs.

  One example is the EMC XtremIO storage, which has 'queue-length' defined as
  its path selector in the default multipath configuration, at least on 16.04.

  Other products may be affected if they are manually configured to use that
  path selector (e.g., via /etc/multipath.conf), and the mere switch of that
  might render the system _unbootable_ if booting from multipath, since the
  initramfs is affected.

  More recently this and another storage changed default path selectors out
  of 'queue-length', however, it's virtually possible for any storage system
  to be affected, with the described manual configuration change.  So, this
  change is also desired on for the next stable release, 17.04, and later.

  Patches are provided for 16.04 and 17.04.

  Error logs in LP comment #6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1673350/+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 1614791] Re: stress-ng freezes system

[Colin Ian King]

Hi Kenneth, I've not had any updates on this bug from you, so I am going
to close it. If this is still and issue, please feel free to reopen this
bug.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Won't Fix

** Changed in: stress-ng (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  stress-ng freezes system

Status in linux package in Ubuntu:
  Won't Fix
Status in stress-ng package in Ubuntu:
  Won't Fix

Bug description:
  While running "stress-ng --aggressive --verify --timeout 2860 --log-
  file stress-ng-brk.log -v --brk 0", the system would freeze within an
  hour of running the test.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: stress-ng 0.05.23-1ubuntu2
  ProcVersionSignature: User Name 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic ppc64le
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: ppc64el
  Date: Fri Aug 19 01:04:30 2016
  ProcEnviron:
   SHELL=/bin/bash
   TERM=linux
   PATH=(custom, user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  ProcLoadAvg: 0.00 0.00 0.00 1/1200 10125
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 7809 00:14:652 0 EOF
   2: FLOCK  ADVISORY  WRITE 7797 00:14:646 0 EOF
   3: POSIX  ADVISORY  WRITE 7799 00:14:656 0 EOF
   4: POSIX  ADVISORY  WRITE 8810 00:14:670 0 EOF
   5: POSIX  ADVISORY  WRITE 4914 00:14:419 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-34-generic (buildd@bos01-ppc64el-022) (gcc 
version 5.3.1 20160413 (User Name/IBM 5.3.1-14ubuntu2.1) ) #53-User Name SMP 
Wed Jul 27 16:04:07 UTC 2016
  SourcePackage: stress-ng
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_smt: SMT=8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1614791/+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 1673350] Re: dm-queue-length module is not included in installer/initramfs

[Stefan Bader]

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Stefan Bader (smb)

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

** Also affects: hw-detect (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

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

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

Title:
  dm-queue-length module is not included in installer/initramfs

Status in hw-detect package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in multipath-tools package in Ubuntu:
  Triaged
Status in hw-detect source package in Xenial:
  New
Status in initramfs-tools source package in Xenial:
  New
Status in linux source package in Xenial:
  In Progress
Status in multipath-tools source package in Xenial:
  New
Status in hw-detect source package in Yakkety:
  New
Status in initramfs-tools source package in Yakkety:
  New
Status in linux source package in Yakkety:
  New
Status in multipath-tools source package in Yakkety:
  New

Bug description:
  [Impact]
  Multipath users using EMC XtremIO storage as boot device or at install time 
may run into this issue. With the module unavailable the device is more often 
than not unavailable. Any users changing path selector to 'queue-length' with 
other storage devices may also be affected.

  [Test case]
  1) Install on multipath system using EMC XtremIO storage / OR:
   a) Start d-i install on qemu with multipath enabled
   b) exit to d-i menu
   c) modify /etc/multipath.conf to define path selector as 'queue-length' for 
the local qemu device.
   d) restart multipathd if necessary.
  2) Try to complete the install, setting up storage as multipath and using the 
multipath device as boot disk.
  3) Reboot to disk.

  In a success case, the install should complete successfully without
  requiring manual configuration from the user to support the multipath
  storage past the normal detection of multipath and partitioning.

  In a failure case, the install may not complete, or rebooting may fail
  or lead to a system booted on a single path of the multipath device
  (ie. / on /dev/sda2 rather than /dev/mpatha2).

  [Regression Potential]
  The inclusion of a new multipath path selector driver should not cause any 
regressions, but any failure to detect, configure or boot on multipath devices 
following this change on XtremIO hardware or otherwise would constitute a 
regression potentially caused by this change.

  ---

  ---Problem Description---
  dm-queue-length module is not included in installer/initramfs

  On Ubuntu, multipath devices using the 'queue-length' path selector
  are non-functional on both the installer and initramfs environments;
  because the 'dm-queue-length' kernel module is not included in them.

  The multipath-modules.udeb (src:linux) does not include it in the installer,
  nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs.

  One example is the EMC XtremIO storage, which has 'queue-length' defined as
  its path selector in the default multipath configuration, at least on 16.04.

  Other products may be affected if they are manually configured to use that
  path selector (e.g., via /etc/multipath.conf), and the mere switch of that
  might render the system _unbootable_ if booting from multipath, since the
  initramfs is affected.

  More recently this and another storage changed default path selectors out
  of 'queue-length', however, it's virtually possible for any storage system
  to be affected, with the described manual configuration change.  So, this
  change is also desired on for the next stable release, 17.04, and later.

  Patches are provided for 16.04 and 17.04.

  Error logs in LP comment #6.

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