[Kernel-packages] [Bug 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5 when phone initiates connection

[Simon Fels]

@Tony: With your last comment: BlueZ 5.37 doesn't fix that problem too?
Or do you still see this with bluez 5.37?

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

Title:
  [Jawbone ERA] HFP features not working with Bluez5 when phone
  initiates connection

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

Bug description:
  While debugging some re-factoring work on the ofono upower plugin, I
  noticed that I wasn't able to answer or terminate calls using my
  Jawbone ERA headset.  I bought this headset last year, and although
  it's an older model, it's spec sheet states that it supports HSP 1.1,
  and HFP 1.5.

  I can pair the device with my krillin, and it properly auto connects (
  note, this seems to work better than my iPhone ).   In-call audio
  works for both incoming and outgoing calls, however I get no ringtone
  in the headset and as mentioned above, I can't answer or terminate the
  call.   I've verified on my iPhone6, that the headset works.  In
  addition to a ringtone in the earpiece, the headset also announces the
  incoming phone number.

  From looking at the ofono debug output, I'm never seeing a new HFP
  connection occur.  I noticed as the upower plugin uses a foreach_atom
  (HFP) style call to update the battery indicators on all attached HFP
  devices.

  I've tested this extensively on krillin, running rc-proposed:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 205
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-12-16 17:53:19
  version version: 205
  version ubuntu: 20151216
  version device: 20151204-2254a36
  version custom: 2015--36-46-vivid

  I've also tested on mako, rc-proposed ( #317 ).

  For reference here's the versions of bluez, ofono, and PulseAudio on
  the device:

  bluez 5.36-0ubuntu2~overlay1
  ofono  1.17.bzr6908+15.04.20151203-0ubuntu1~awe3
  pulseaudio1:6.0-0ubuntu9.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1527354/+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 1491340] Re: Bluetooth keyboard is configured with wrong keyboard layout

[Victor gonzalez]

** Tags added: bq-feedback

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

Title:
  Bluetooth keyboard is configured with wrong keyboard layout

Status in The Avila project:
  In Progress
Status in Canonical System Image:
  In Progress
Status in Canonical Pocket Desktop:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Phone: Meizu MX4 (15.04 r4)
  OS Language: German

  What you expected to happen:
  When connecting a Bluetooth keyboard I expect that the keyboard layout is the 
same as the keyboard hardware key layout (German) or that it is possible to 
change the keyboard layout in the Bluetooth setting for the connected Bluetooth 
device.

  What happened instead:
  The Bluetooth keyboard worked, but wasn't set to German key layout. In the 
Bluetooth device setting I couldn't find any option to change the Bluetooth 
keyboard key layout.

To manage notifications about this bug go to:
https://bugs.launchpad.net/avila/+bug/1491340/+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 1554371] 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/1554371

Title:
  [Regression] Volume keys not working after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Microsoft Sculpt Ergonomic Desktop (keyboard/mouse combo). It
  was working great with Ubuntu 15.10. After upgrading to 16.04, the
  media keys stop working after suspending and resuming. This seems to
  be the relevant error from Xorg.log:

  [   176.121] (EE) evdev: Microsoft Microsoft® 2.4GHz Transceiver v9.0:
  Unable to open evdev device "/dev/input/event6".

  The USB receiver creates 5 devices:

  lrwxrwxrwx 1 root root   9 Mar  7 20:17 
usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-event-kbd -> ../event4
  lrwxrwxrwx 1 root root   9 Mar  7 20:17 
usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-if01-event-mouse -> ../event5
  lrwxrwxrwx 1 root root   9 Mar  7 20:17 
usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-if01-mouse -> ../mouse1
  lrwxrwxrwx 1 root root   9 Mar  7 20:17 
usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-if02-event-kbd -> ../event6
  lrwxrwxrwx 1 root root   6 Mar  7 20:17 
usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-if02-kbd -> ../js0

  After suspending and resuming, the last 2 devices (event6 and js0)
  disappear.

  I have tried booting up into the Vivid and Trusty kernels, and the
  problem persists, so at first glance it doesn't seem to be an issue
  with the kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-4-generic 4.4.0-4.19
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  Uname: Linux 4.4.0-4-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  furkan 2733 F pulseaudio
   /dev/snd/controlC1:  furkan 2733 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar  7 20:17:56 2016
  HibernationDevice: RESUME=UUID=a8eb7091-e848-4e63-82a1-8fa9562a3a61
  InstallationDate: Installed on 2014-06-06 (640 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Gigabyte Technology Co., Ltd. GA-970A-D3
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-4-generic 
root=UUID=d254b01f-2bf2-4b57-acdc-c796786f4c4c ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-4-generic N/A
   linux-backports-modules-4.4.0-4-generic  N/A
   linux-firmware   1.156
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-01-04 (63 days ago)
  dmi.bios.date: 05/30/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F10
  dmi.board.name: GA-970A-D3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd05/30/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-D3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-970A-D3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1554371/+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 1498667] Re: [Toshiba P50W-B00F] Touchscreen no longer working

[Robert Ancell]

linux-
image-4.1.0-040100rc7-generic_4.1.0-040100rc7.201603071533_amd64.deb -
WWW

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

Title:
  [Toshiba P50W-B00F] Touchscreen no longer working

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

Bug description:
  Sometime in the last month or so my touchscreen stopped working on my
  Toshiba P50W. The dmesg log shows it constantly reconnecting to it:

  [  556.407964] usb 1-4: new full-speed USB device number 119 using xhci_hcd
  [  556.538341] usb 1-4: New USB device found, idVendor=04f3, idProduct=0381
  [  556.538347] usb 1-4: New USB device strings: Mfr=4, Product=14, 
SerialNumber=0
  [  556.538349] usb 1-4: Product: Touchscreen
  [  556.538351] usb 1-4: Manufacturer: ELAN
  [  556.538505] usb 1-4: ep 0x2 - rounding interval to 64 microframes, ep desc 
says 80 microframes
  [  556.547788] input: ELAN Touchscreen as 
/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:0381.04A1/input/input2374
  [  556.600478] hid-multitouch 0003:04F3:0381.04A1: input,hiddev0,hidraw4: USB 
HID v1.10 Device [ELAN Touchscreen] on usb-:00:14.0-4/input0
  [  556.600584] usb 1-4: USB disconnect, device number 119

  [  556.860456] usb 1-4: new full-speed USB device number 120 using xhci_hcd
  [  556.990494] usb 1-4: New USB device found, idVendor=04f3, idProduct=0381
  [  556.990500] usb 1-4: New USB device strings: Mfr=4, Product=14, 
SerialNumber=0
  [  556.990503] usb 1-4: Product: Touchscreen
  [  556.990506] usb 1-4: Manufacturer: ELAN
  [  556.990755] usb 1-4: ep 0x2 - rounding interval to 64 microframes, ep desc 
says 80 microframes
  [  557.001248] input: ELAN Touchscreen as 
/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:0381.04A2/input/input2376
  [  557.002517] hid-multitouch 0003:04F3:0381.04A2: input,hiddev0,hidraw4: USB 
HID v1.10 Device [ELAN Touchscreen] on usb-:00:14.0-4/input0
  [  557.013831] usb 1-4: USB disconnect, device number 120

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-11-generic 4.2.0-11.13
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bob2041 F pulseaudio
   /dev/snd/controlC0:  bob2041 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep 23 09:46:25 2015
  HibernationDevice: RESUME=UUID=5033984a-21af-482d-a1fd-c075e818cd12
  InstallationDate: Installed on 2013-12-26 (635 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: TOSHIBA Satellite P50W-B
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic 
root=UUID=885f0f10-b818-4eb4-8ff4-d067e16bef2f ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-11-generic N/A
   linux-backports-modules-4.2.0-11-generic  N/A
   linux-firmware1.148
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2013-12-26 (635 days ago)
  dmi.bios.date: 08/08/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.40:bd08/08/2014:svnTOSHIBA:pnSatelliteP50W-B:pvrPSVP2A-00F002:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite P50W-B
  dmi.product.version: PSVP2A-00F002
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1498667/+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 1554371] Re: [Regression] Volume keys not working after suspend/resume

[Furkan]

** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1554371/+attachment/4592321/+files/Xorg.0.log

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

Title:
  [Regression] Volume keys not working after suspend/resume

Status in linux package in Ubuntu:
  New

Bug description:
  I have a Microsoft Sculpt Ergonomic Desktop (keyboard/mouse combo). It
  was working great with Ubuntu 15.10. After upgrading to 16.04, the
  media keys stop working after suspending and resuming. This seems to
  be the relevant error from Xorg.log:

  [   176.121] (EE) evdev: Microsoft Microsoft® 2.4GHz Transceiver v9.0:
  Unable to open evdev device "/dev/input/event6".

  The USB receiver creates 5 devices:

  lrwxrwxrwx 1 root root   9 Mar  7 20:17 
usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-event-kbd -> ../event4
  lrwxrwxrwx 1 root root   9 Mar  7 20:17 
usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-if01-event-mouse -> ../event5
  lrwxrwxrwx 1 root root   9 Mar  7 20:17 
usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-if01-mouse -> ../mouse1
  lrwxrwxrwx 1 root root   9 Mar  7 20:17 
usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-if02-event-kbd -> ../event6
  lrwxrwxrwx 1 root root   6 Mar  7 20:17 
usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-if02-kbd -> ../js0

  After suspending and resuming, the last 2 devices (event6 and js0)
  disappear.

  I have tried booting up into the Vivid and Trusty kernels, and the
  problem persists, so at first glance it doesn't seem to be an issue
  with the kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-4-generic 4.4.0-4.19
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  Uname: Linux 4.4.0-4-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  furkan 2733 F pulseaudio
   /dev/snd/controlC1:  furkan 2733 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar  7 20:17:56 2016
  HibernationDevice: RESUME=UUID=a8eb7091-e848-4e63-82a1-8fa9562a3a61
  InstallationDate: Installed on 2014-06-06 (640 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Gigabyte Technology Co., Ltd. GA-970A-D3
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-4-generic 
root=UUID=d254b01f-2bf2-4b57-acdc-c796786f4c4c ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-4-generic N/A
   linux-backports-modules-4.4.0-4-generic  N/A
   linux-firmware   1.156
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-01-04 (63 days ago)
  dmi.bios.date: 05/30/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F10
  dmi.board.name: GA-970A-D3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd05/30/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-D3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-970A-D3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1554371/+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 1554371] [NEW] [Regression] Volume keys not working after suspend/resume

[Furkan]

Public bug reported:

I have a Microsoft Sculpt Ergonomic Desktop (keyboard/mouse combo). It
was working great with Ubuntu 15.10. After upgrading to 16.04, the media
keys stop working after suspending and resuming. This seems to be the
relevant error from Xorg.log:

[   176.121] (EE) evdev: Microsoft Microsoft® 2.4GHz Transceiver v9.0:
Unable to open evdev device "/dev/input/event6".

The USB receiver creates 5 devices:

lrwxrwxrwx 1 root root   9 Mar  7 20:17 
usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-event-kbd -> ../event4
lrwxrwxrwx 1 root root   9 Mar  7 20:17 
usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-if01-event-mouse -> ../event5
lrwxrwxrwx 1 root root   9 Mar  7 20:17 
usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-if01-mouse -> ../mouse1
lrwxrwxrwx 1 root root   9 Mar  7 20:17 
usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-if02-event-kbd -> ../event6
lrwxrwxrwx 1 root root   6 Mar  7 20:17 
usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-if02-kbd -> ../js0

After suspending and resuming, the last 2 devices (event6 and js0)
disappear.

I have tried booting up into the Vivid and Trusty kernels, and the
problem persists, so at first glance it doesn't seem to be an issue with
the kernel.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-4-generic 4.4.0-4.19
ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
Uname: Linux 4.4.0-4-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  furkan 2733 F pulseaudio
 /dev/snd/controlC1:  furkan 2733 F pulseaudio
CurrentDesktop: Unity
Date: Mon Mar  7 20:17:56 2016
HibernationDevice: RESUME=UUID=a8eb7091-e848-4e63-82a1-8fa9562a3a61
InstallationDate: Installed on 2014-06-06 (640 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Gigabyte Technology Co., Ltd. GA-970A-D3
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-4-generic 
root=UUID=d254b01f-2bf2-4b57-acdc-c796786f4c4c ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-4-generic N/A
 linux-backports-modules-4.4.0-4-generic  N/A
 linux-firmware   1.156
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-01-04 (63 days ago)
dmi.bios.date: 05/30/2012
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F10
dmi.board.name: GA-970A-D3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd05/30/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-D3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-970A-D3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug xenial

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

Title:
  [Regression] Volume keys not working after suspend/resume

Status in linux package in Ubuntu:
  New

Bug description:
  I have a Microsoft Sculpt Ergonomic Desktop (keyboard/mouse combo). It
  was working great with Ubuntu 15.10. After upgrading to 16.04, the
  media keys stop working after suspending and resuming. This seems to
  be the relevant error from Xorg.log:

  [   176.121] (EE) evdev: Microsoft Microsoft® 2.4GHz Transceiver v9.0:
  Unable to open evdev device "/dev/input/event6".

  The USB receiver creates 5 devices:

  lrwxrwxrwx 1 root root   9 Mar  7 20:17 
usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-event-kbd -> ../event4
  lrwxrwxrwx 1 root root   9 Mar  7 20:17 
usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-if01-event-mouse -> ../event5
  lrwxrwxrwx 1 root root   9 Mar  7 20:17 
usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-if01-mouse -> ../mouse1
  lrwxrwxrwx 1 root root   9 Mar  7 20:17 
usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-if02-event-kbd -> ../event6
  lrwxrwxrwx 1 root root   6 Mar  7 20:17 
usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-if02-kbd -> ../js0

  After suspending and resuming, the last 2 devices (event6 and js0)
  disappear.

  I have tried booting up into the Vivid and Trusty kernels, and the
  problem persists, so at first glance it doesn't seem to be an issue
  with the kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-4-generic 4.4.0-4.19
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  Uname: Linux 4.4.0-4-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  furkan 2733 F pulseaudio
   /dev/snd/controlC1:  furkan 2733 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar  7 20:17:56 2016
  HibernationDevice: 

[Kernel-packages] [Bug 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

[Simon Fels]

@Tony: Can you reproduce this once again and record the HCI packets by
running

 $ sudo btmon -w test.cap

Then attach test.cap here.

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

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  Connecting to the latest generation Apple BT keyboard ( the one with
  the USB port & no batteries ) fails on an Ubuntu Touch device, as when
  you press the "Connect" button on the device page, a dialog titled
  "Bluetooth Pairing Request" is displayed, with the following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris E4.5 Ubuntu Edition
Alias: Aquaris E4.5 Ubuntu Edition
Class: 0x1c020c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no

  [bluetooth]# devices
  Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
  Device DE:76:E2:04:9D:6F BB-9D6F
  Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
  Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
  Device 84:38:35:67:0C:3D ubuntu-0
  Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
  Device 00:21:3C:A0:14:A6 Jawbone ERA
  Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7

  Device info *before* pairing attempt:

  Device 04:69:F8:C2:A0:09
Name: tony espy’s Keyboard
Alias: tony espy’s Keyboard
Class: 0x002540
Icon: input-keyboard
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
Modalias: bluetooth:v004Cp0267d0066

  No changes in any of the attributes after *after* the pairing attempt
  ( output of info command is the same ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+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 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

[Simon Fels]

Just as a additional note: The actual pairing method is selected in the
kernel. See
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/smp.c#n859

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

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  Connecting to the latest generation Apple BT keyboard ( the one with
  the USB port & no batteries ) fails on an Ubuntu Touch device, as when
  you press the "Connect" button on the device page, a dialog titled
  "Bluetooth Pairing Request" is displayed, with the following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris E4.5 Ubuntu Edition
Alias: Aquaris E4.5 Ubuntu Edition
Class: 0x1c020c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no

  [bluetooth]# devices
  Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
  Device DE:76:E2:04:9D:6F BB-9D6F
  Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
  Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
  Device 84:38:35:67:0C:3D ubuntu-0
  Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
  Device 00:21:3C:A0:14:A6 Jawbone ERA
  Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7

  Device info *before* pairing attempt:

  Device 04:69:F8:C2:A0:09
Name: tony espy’s Keyboard
Alias: tony espy’s Keyboard
Class: 0x002540
Icon: input-keyboard
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
Modalias: bluetooth:v004Cp0267d0066

  No changes in any of the attributes after *after* the pairing attempt
  ( output of info command is the same ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+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 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

[Simon Fels]

And there we go:

Mar  7 15:08:44 ubuntu-phablet bluetoothd[890]: src/device.c:new_auth() 
Requesting agent authentication for 04:69:F8:C2:A0:09
Mar  7 15:08:44 ubuntu-phablet bluetoothd[890]: src/agent.c:agent_ref() 
0xb8c78950: ref=3
Mar  7 15:08:44 ubuntu-phablet bluetoothd[890]: 
src/agent.c:agent_request_confirmation() Calling Agent.RequestConfirmation: 
name=:1.119, path=/com/canonical/SettingsBluetoothAgent/adapteragent, 
passkey=800772

I expected bluez to call DisplayPasskey here rather than
RequestConfirmation. So what settings displays is correct (in terms of
what it was asked for).

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

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  Connecting to the latest generation Apple BT keyboard ( the one with
  the USB port & no batteries ) fails on an Ubuntu Touch device, as when
  you press the "Connect" button on the device page, a dialog titled
  "Bluetooth Pairing Request" is displayed, with the following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris E4.5 Ubuntu Edition
Alias: Aquaris E4.5 Ubuntu Edition
Class: 0x1c020c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no

  [bluetooth]# devices
  Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
  Device DE:76:E2:04:9D:6F BB-9D6F
  Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
  Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
  Device 84:38:35:67:0C:3D ubuntu-0
  Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
  Device 00:21:3C:A0:14:A6 Jawbone ERA
  Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7

  Device info *before* pairing attempt:

  Device 04:69:F8:C2:A0:09
Name: tony espy’s Keyboard
Alias: tony espy’s Keyboard
Class: 0x002540
Icon: input-keyboard
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
Modalias: bluetooth:v004Cp0267d0066

  No changes in any of the attributes after *after* the pairing attempt
  ( output of info command is the same ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+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 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

[Simon Fels]

Because what pairing method is selected is chosen further down the stack
so settings only reacts on what bluez tells it should do. I suspect the
keyboard uses pairing capability KeyboardOnly which then should lead to
passkey entry where the initiator displays and the responder inputs the
PIN (we use KeyboardDisplay) [see Core spec 4.0 page 1968].

However the described dialog on your side is incorrect as it just asks
the user to confirm or cancel which could still be an settings app issue
just displaying the dialog but also an issue down the stack.

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

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  Connecting to the latest generation Apple BT keyboard ( the one with
  the USB port & no batteries ) fails on an Ubuntu Touch device, as when
  you press the "Connect" button on the device page, a dialog titled
  "Bluetooth Pairing Request" is displayed, with the following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris E4.5 Ubuntu Edition
Alias: Aquaris E4.5 Ubuntu Edition
Class: 0x1c020c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no

  [bluetooth]# devices
  Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
  Device DE:76:E2:04:9D:6F BB-9D6F
  Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
  Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
  Device 84:38:35:67:0C:3D ubuntu-0
  Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
  Device 00:21:3C:A0:14:A6 Jawbone ERA
  Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7

  Device info *before* pairing attempt:

  Device 04:69:F8:C2:A0:09
Name: tony espy’s Keyboard
Alias: tony espy’s Keyboard
Class: 0x002540
Icon: input-keyboard
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
Modalias: bluetooth:v004Cp0267d0066

  No changes in any of the attributes after *after* the pairing attempt
  ( output of info command is the same ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+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 1540886] Re: xfrm and fwmark do not work on VXLAN xmit

[Atzm Watanabe]

Thank you for the advice.
I tried LTS Enablement Stack (linux-image-generic-lts-wily) and it worked fine 
to me.
So I don't need a backport.  I mark the issue status Invalid.

Thank you again!


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

Title:
  xfrm and fwmark do not work on VXLAN xmit

Status in linux package in Ubuntu:
  Invalid

Bug description:
  On Ubuntu 15.04, kernel 3.19.0-49-generic has known issue that xfrm and 
fwmark do not work on VXLAN xmit.
  This issue was fixed on upstream kernel: 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=239fb791d4ee194740e69fe9694f58ec404d1689

  I think the above patch should be backported because this may cause serious 
problems including security issues.
  For example, outgoing VXLAN packet will be sent without encryption even if 
IPsec security policy is configured properly.
  As the result, the packet which should be encrypted can be snooped.

  How to reproduce:

  When using ipsec-tools (for minimum reproducing steps):

  --- Node-A
  # modprobe esp4
  # modprobe af_key
  # modprobe xfrm4_mode_transport
  # setkey -c < flush;
  > spdflush;
  > add   esp 0x201 -E 3des-cbc 
0x7aeaca3f87d060a12f4a4487d5a5c3355920fae69a96c831;
  > add   esp 0x301 -E 3des-cbc 
0xf6ddb555acfd9d77b03ea3843f2653255afe8eb5573965df;
  > spdadd   udp -P out ipsec esp/transport//require;
  > spdadd   udp -P in  ipsec esp/transport//require;
  > EOL
  # ip link add vxlan100 type vxlan id 100 remote 
  # ip addr add 1.1.1.1/24 dev vxlan100
  # ip link set vxlan100 up

  --- Node-B
  # modprobe esp4
  # modprobe af_key
  # modprobe xfrm4_mode_transport
  # setkey -c < flush;
  > spdflush;
  > add   esp 0x201 -E 3des-cbc 
0x7aeaca3f87d060a12f4a4487d5a5c3355920fae69a96c831;
  > add   esp 0x301 -E 3des-cbc 
0xf6ddb555acfd9d77b03ea3843f2653255afe8eb5573965df;
  > spdadd   udp -P out ipsec esp/transport//require;
  > spdadd   udp -P in  ipsec esp/transport//require;
  > EOL
  # ip link add vxlan100 type vxlan id 100 remote 
  # ip addr add 1.1.1.2/24 dev vxlan100
  # ip link set vxlan100 up
  # ping 1.1.1.1

  Then packets which is encapsulated with VXLAN header will be shown in
  tcpdump, but they must be ESP packets.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540886/+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 1486997] Re: Copying a large file causes user interface to stop responding

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

Title:
  Copying a large file causes user interface to stop responding

Status in linux package in Ubuntu:
  Expired

Bug description:
  Any heavy and prolonged disc activity causes the UI, mouse, and
  terminal to stop responding. For example, copying several GB of data
  via `cp file1 file1-copy`. When the copy completes, or if it's
  interrupted, the user interface responds normally. The problem occurs
  even when there's several GB of memory to spare. Other kernel
  schedulers don't change anything.

  WORKAROUND: Disable swap.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-45-generic 3.16.0-45.60~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Aug 20 12:21:59 2015
  InstallationDate: Installed on 2015-07-13 (37 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: linux-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   phill  2715 F...m pulseaudio
   /dev/snd/controlC0:  phill  2715 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=fab564c9-5c8a-439f-8b9d-a10c8a4b75ad
  InstallationDate: Installed on 2015-07-13 (165 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: System manufacturer V-P5G45
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-56-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-56.75~14.04.1-generic 3.16.7-ckt20
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-56-generic N/A
   linux-backports-modules-3.16.0-56-generic  N/A
   linux-firmware 1.127.19
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.16.0-56-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/18/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0405
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: V-P5G45
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0405:bd05/18/2009:svnSystemmanufacturer:pnV-P5G45:pvrSystemVersion:rvnASUSTeKComputerINC.:rnV-P5G45:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: V-P5G45
  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/1486997/+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 1523444] Re: Xorg crahed with segfault

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

Title:
  Xorg crahed with segfault

Status in linux package in Ubuntu:
  Expired

Bug description:
  I was about to click on a button in Chromium when Xorg unexpectedly crashed.
  This bug just happened and I doubt that it is reproducible.
  This might be a kernel and not an xorg error, please re-categorize if needed.

  Relevant section from the Xorg files:
  [  6812.749] (EE) Backtrace:
  [  6812.749] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55f0bc03968e]
  [  6812.749] (EE) 1: /usr/bin/X (0x55f0bbe85000+0x1b89f9) [0x55f0bc03d9f9]
  [  6812.749] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f5e9cbbe000+0x352f0) 
[0x7f5e9cbf32f0]
  [  6812.749] (EE) 
  [  6812.749] (EE) Segmentation fault at address 0x0
  [  6812.749] (EE) 
  Fatal server error:
  [  6812.749] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [  6812.749] (EE) 
  [  6812.749] (EE) 

  Relevant section from syslog:
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582120] [ cut here 
]
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582137] WARNING: CPU: 3 PID: 1318 at 
/build/linux-26_gwp/linux-4.2.0/drivers/gpu/drm/i915/i915_gem.c:5269 
i915_gem_track_fb+0x129/0x140 [i915]()
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582139] 
WARN_ON(!(old->frontbuffer_bits & frontbuffer_bits))
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582139] Modules linked in: pci_stub 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) nfsv3 nfs_acl 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache hp_wmi spa
  rse_keymap intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp 
joydev snd_hda_codec_hdmi input_leds snd_hda_codec_realtek kvm_intel 
snd_hda_codec_generic kvm snd_hda_intel snd_hda_codec crct10dif_
  pclmul snd_hda_core crc32_pclmul snd_hwdep snd_pcm aesni_intel aes_x86_64 lrw 
gf128mul snd_seq_midi glue_helper snd_seq_midi_event ablk_helper cryptd 
snd_rawmidi snd_seq snd_seq_device serio_raw snd_timer snd so
  undcore mei_me mei lpc_ich 8250_fintek tpm_infineon mac_hid ipt_REJECT 
nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_recent xt_limit xt_tcpudp 
xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6ta
  ble_filter ip6_tables nf_conntrack_pptp nf_conntrack_proto_gre 
nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat 
nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables sunrpc 
parport_pc p
  pdev lp parport autofs4 hid_generic usbhid hid i915 psmouse i2c_algo_bit 
drm_kms_helper e1000e ahci drm libahci ptp pps_core wmi video
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582178] CPU: 3 PID: 1318 Comm: Xorg 
Tainted: G   OE   4.2.0-19-generic #23-Ubuntu
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582179] Hardware name: Hewlett-Packard 
HP EliteDesk 800 G1 SFF/1998, BIOS L01 v02.65 07/13/2015
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582180]   
466f5698 880212e8fac8 817e93f9
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582182]   
880212e8fb20 880212e8fb08 8107b3d6
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582183]  880211e43600 
0010 880211b7c000 880211b7c000
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582184] Call Trace:
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582188]  [] 
dump_stack+0x45/0x57
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582191]  [] 
warn_slowpath_common+0x86/0xc0
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582193]  [] 
warn_slowpath_fmt+0x55/0x70
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582200]  [] 
i915_gem_track_fb+0x129/0x140 [i915]
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582211]  [] 
intel_prepare_plane_fb+0xe7/0x1a0 [i915]
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582215]  [] 
drm_atomic_helper_prepare_planes+0x59/0xe0 [drm_kms_helper]
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582225]  [] ? 
drm_atomic_check_only+0x215/0x540 [drm]
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582235]  [] 
intel_atomic_commit+0x42/0x100 [i915]
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582242]  [] 
drm_atomic_commit+0x37/0x60 [drm]
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582245]  [] 
drm_atomic_helper_plane_set_property+0x87/0xc0 [drm_kms_helper]
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582250]  [] ? 
_object_find+0x69/0xa0 [drm]
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582255]  [] 
drm_mode_plane_set_obj_prop+0x2d/0x90 [drm]
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582261]  [] 
drm_mode_obj_set_property_ioctl+0x1c6/0x270 [drm]
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582265]  [] 
drm_ioctl+0x125/0x610 [drm]
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582267]  [] ? 
fsnotify+0x316/0x4a0
  Dec  7 11:39:25 ultra-d kernel: [ 6818.582272]  [] ? 
drm_mode_obj_get_properties_ioctl+0xa0/0xa0 [drm]
  Dec  

[Kernel-packages] [Bug 1506543] Re: openstack instances on arm64 lock up on polling and other situations fairly repeatably

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

Title:
  openstack instances on arm64 lock up on polling and other situations
  fairly repeatably

Status in linux package in Ubuntu:
  Expired

Bug description:
  While working on deploying arm64 builders in openstack, we found that
  it was pretty easy to wedge them.  Many hang just running ntpdate
  right off the bat.

  William Grant had more direct tests he did, but upgrading from 3.13 to
  3.19 didn't seem to fix things.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506543/+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 1531238] Re: [Acer Travelmate b115-m] Ubuntu 15.10 freezes

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

Title:
  [Acer Travelmate b115-m] Ubuntu 15.10 freezes

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hi,
  Ubuntu always freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nobbi  1603 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan  5 19:30:05 2016
  HibernationDevice: RESUME=UUID=66744591-69fa-47b6-8ad5-791748165035
  InstallationDate: Installed on 2015-10-26 (70 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:2c57 Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer TravelMate B115-M
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-19-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.26
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Roxy
  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.26:bd09/12/2014:svnAcer:pnTravelMateB115-M:pvrV1.26:rvnAcer:rnRoxy:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: TravelMate B115-M
  dmi.product.version: V1.26
  dmi.sys.vendor: Acer

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

Title:
  Reboot upon resume from suspend on Dell XPS 13

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  If you close the lid or choose suspend from the system menu then
  resume, the system reboots.  This didn't happen in the previous
  release of the kernel.  This is a Dell XPS 13 9350 (Skylake) with
  latest firmware 1.2.3

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-11-generic 4.4.0-11.26
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-11-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anmar  1575 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Mar  8 10:48:03 2016
  HibernationDevice: RESUME=UUID=94adb22b-7cde-416d-a17f-c3e5d40718da
  InstallationDate: Installed on 2016-03-02 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160301)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5682 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-11-generic.efi.signed 
root=UUID=9945d9bf-9e44-4308-a4ec-c1f92f9b330c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-11-generic N/A
   linux-backports-modules-4.4.0-11-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01: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/1554330/+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 1311368] Re: Won't install on precise (over ssh), blocking installation of ia32-libs

[Launchpad Bug Tracker]

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

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

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

Title:
  Won't install on precise (over ssh), blocking installation of
  ia32-libs

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  bluez package fails to install via apt-get, which prevents me from
  installing ia32-libs, on precise.  Running over ssh, not sure if that
  could be relevant.  I'm not interested in using the bluez package at
  all, this is a server.

  # apt-get install bluez
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following NEW packages will be installed:
bluez
  0 upgraded, 1 newly installed, 0 to remove and 39 not upgraded.
  Need to get 0 B/969 kB of archives.
  After this operation, 2,525 kB of additional disk space will be used.
  Selecting previously unselected package bluez.
  (Reading database ... 89815 files and directories currently installed.)
  Unpacking bluez (from .../bluez_4.98-2ubuntu7.1_amd64.deb) ...
  Processing triggers for man-db ...
  Processing triggers for ureadahead ...
  Setting up bluez (4.98-2ubuntu7.1) ...
  reload: Unknown instance: 
  invoke-rc.d: initscript dbus, action "force-reload" failed.
  start: Job failed to start
  invoke-rc.d: initscript bluetooth, action "start" failed.
  dpkg: error processing bluez (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   bluez
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  # apt-get install ia32-libs
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following extra packages will be installed:
bluez bluez-alsa:i386 ia32-libs-multiarch:i386
  Suggested packages:
libpam-ldap:i386 libpam-winbind:i386 libnss-ldap:i386
  The following NEW packages will be installed:
bluez bluez-alsa:i386 ia32-libs ia32-libs-multiarch:i386
  0 upgraded, 4 newly installed, 0 to remove and 39 not upgraded.
  Need to get 0 B/1,111 kB of archives.
  After this operation, 2,987 kB of additional disk space will be used.
  Do you want to continue [Y/n]? 
  Selecting previously unselected package bluez.
  (Reading database ... 89815 files and directories currently installed.)
  Unpacking bluez (from .../bluez_4.98-2ubuntu7.1_amd64.deb) ...
  Selecting previously unselected package bluez-alsa:i386.
  Unpacking bluez-alsa:i386 (from .../bluez-alsa_4.98-2ubuntu7.1_i386.deb) ...
  Selecting previously unselected package ia32-libs-multiarch:i386.
  Unpacking ia32-libs-multiarch:i386 (from 
.../ia32-libs-multiarch_20090808ubuntu36_i386.deb) ...
  Selecting previously unselected package ia32-libs.
  Unpacking ia32-libs (from .../ia32-libs_20090808ubuntu36_amd64.deb) ...
  Processing triggers for man-db ...
  Processing triggers for ureadahead ...
  Setting up bluez (4.98-2ubuntu7.1) ...
  reload: Unknown instance: 
  invoke-rc.d: initscript dbus, action "force-reload" failed.
  start: Job failed to start
  invoke-rc.d: initscript bluetooth, action "start" failed.
  dpkg: error processing bluez (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of bluez-alsa:i386:
   bluez-alsa:i386 depends on bluez; however:
Package bluez is not configured yet.
  dpkg: error processing bluez-alsa:i386 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of ia32-libs-multiarch:i386:
   ia32-libs-multiarch:i386 depends on bluez-alsa; however:
Package bluez-alsa:i386 is not configured yet.
  dpkg: error processing ia32-libs-multiarch:i386 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of ia32-libs:
   ia32-libs depends on ia32-libs-multiarch; however:
Package ia32-libs-multiarch is not installed.
Package ia32-libs-multiarch:i386 is not configured yet.
  dpkg: error processing ia32-libs (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
error from a previous failure.

Errors were encountered while processing:
   bluez
   bluez-alsa:i386
   ia32-libs-multiarch:i386
   ia32-libs
  E: Sub-process /usr/bin/dpkg returned an error code (1)

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

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

[Kernel-packages] [Bug 1554330] [NEW] Reboot upon resume from suspend on Dell XPS 13

[Anmar Oueja]

Public bug reported:

If you close the lid or choose suspend from the system menu then resume,
the system reboots.  This didn't happen in the previous release of the
kernel.  This is a Dell XPS 13 9350 (Skylake) with latest firmware 1.2.3

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-11-generic 4.4.0-11.26
ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
Uname: Linux 4.4.0-11-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  anmar  1575 F pulseaudio
CurrentDesktop: Unity
Date: Tue Mar  8 10:48:03 2016
HibernationDevice: RESUME=UUID=94adb22b-7cde-416d-a17f-c3e5d40718da
InstallationDate: Installed on 2016-03-02 (6 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160301)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:5682 Realtek Semiconductor Corp. 
 Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9350
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-11-generic.efi.signed 
root=UUID=9945d9bf-9e44-4308-a4ec-c1f92f9b330c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-11-generic N/A
 linux-backports-modules-4.4.0-11-generic  N/A
 linux-firmware1.156
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/08/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.3
dmi.board.name: 07TYC2
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9350
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  Reboot upon resume from suspend on Dell XPS 13

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  If you close the lid or choose suspend from the system menu then
  resume, the system reboots.  This didn't happen in the previous
  release of the kernel.  This is a Dell XPS 13 9350 (Skylake) with
  latest firmware 1.2.3

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-11-generic 4.4.0-11.26
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-11-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anmar  1575 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Mar  8 10:48:03 2016
  HibernationDevice: RESUME=UUID=94adb22b-7cde-416d-a17f-c3e5d40718da
  InstallationDate: Installed on 2016-03-02 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160301)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5682 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-11-generic.efi.signed 
root=UUID=9945d9bf-9e44-4308-a4ec-c1f92f9b330c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-11-generic N/A
   linux-backports-modules-4.4.0-11-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01: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/1554330/+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 1535147] Re: Kernel Panic error message using kernel 3.19.0-43-generic

[Christopher M. Penalver]

Jonathan Rogiest, this bug report is being closed due to your last
comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535147/comments/4
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

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

Title:
  Kernel Panic error message using  kernel 3.19.0-43-generic

Status in linux package in Ubuntu:
  Invalid

Bug description:
  After auto update to kernel 3.19.0-43-generic when rebooting computer
  computer gives terminal error "end Kernel panic - not syncing: VFS:
  Unable to mount root fs on unknown-block(0.0)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-42-generic 3.19.0-42.48~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-42.48~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-42-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan 17 17:12:34 2016
  InstallationDate: Installed on 2015-11-26 (52 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535147/+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 1547884] Re: Broadcom Corp. BCM5880 Secure Applications Processor eats too much power

[Christopher M. Penalver]

Martin Pecka, in order to allow additional upstream developers to examine the 
issue, at your earliest convenience, could you please test the latest upstream 
kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? 
Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the 
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the upstream kernel, please comment on which kernel version 
specifically you tested. If this issue is fixed in the mainline kernel, please 
add the following tags by clicking on the yellow circle with a black pencil 
icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

Once testing of the latest upstream kernel is complete, please mark this
report Status Confirmed. Please let us know your results.

Thank you for your understanding.

** Tags added: latest-bios-a16

** Changed in: linux (Ubuntu)
   Importance: Low => 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/1547884

Title:
  Broadcom Corp. BCM5880 Secure Applications Processor eats too much
  power

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $ lsusb
  Bus 004 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor

  $ sudo powertop
  Power est.  Usage   Events/sKategorie   Popis
24.3 W100,0%  Device USB device: 5880 
(Broadcom Corp)

  On my Dell Latitude E6540 I constantly see this USB device eating
  about 20 W of power (and I don't see a reason for this kind of device
  to take that much power). And yes, the fan is always running, even
  when the computer is completely idle.

  The computer has no fingerprint reader (though it was an optional
  accessory, so the chip is IMHO built to support it). I use the
  integrated smartcard reader (also handled by this chip). I've set up
  PAM and LightDM to support smartcard login. However, the power usage
  is the same regardless of whether a smartcard is inserted or not. I do
  not intentionally use the integrated TPM chip in any way.

  I faced this problem also on Ubuntu 14.04.3 with 3.19 kernel.

  Eventually, this could also be a bug in powertop, but the fan almost
  never stops (even with display backlight to minimum), so I think
  powertop could be correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 20 15:33:49 2016
  InstallationDate: Installed on 2013-11-05 (837 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (678 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peci1  2919 F pulseaudio
   /dev/snd/pcmC1D0p:   peci1  2919 F...m pulseaudio
   /dev/snd/controlC1:  peci1  2919 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=05314bb8-8590-474c-8af1-1c90dd3bb89c
  InstallationDate: Installed on 2013-11-05 (853 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Latitude E6540
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=501ffea4-2b36-441b-a8ca-34805170c396 ro i8042.nopnp quiet splash 
radeon.modeset=1 radeon.dpm=1 i915.modeset=1 

[Kernel-packages] [Bug 1554299] Re: drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in dpll_hw_state.wrpll (expected 0xb0210614, found 0x00000000)

[Christopher M. Penalver]

Martin Pecka, thank you for taking the time to report this bug and helping to 
make Ubuntu better. Please execute the following command only once, as it will 
automatically gather debugging information, in a terminal:
apport-collect 1554299

** Package changed: linux-lts-wily (Ubuntu) => linux (Ubuntu)

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

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

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

Title:
  drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in
  dpll_hw_state.wrpll (expected 0xb0210614, found 0x)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a followup of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501260 .

  Basically, running OpenGL applications (e.g. glxgears) on the primary
  display handled by Intel 915 card results in display freeze. The error
  message from the title of this bug is written to a VT console if I
  switch to it. It seems this bug only appears when multiple monitors
  are connected.

  Switching to a VT (Ctrl+Alt+F1) and back unfreezes the screen for a
  while. The screen only looks frozen, but normally reacts to mouse and
  keyboard events. This only happens if the GL window is displayed on my
  primary display (which is handled by the intel integrated chip). The
  notebook has 2 video outputs and a discrete AMD graphics, and I think
  only one of the outputs is handled by the AMD card, so I think one of
  the outputs is handled by the intel card and does not get frozen.

  Ubuntu 14.04.3 64bit.

  I think that before upgrading from 14.04.2 to 14.04.3 this did not
  happen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-30-generic 4.2.0-30.36~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  8 02:43:37 2016
  InstallationDate: Installed on 2013-11-05 (853 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (695 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1554299/+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 1554299] [NEW] drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in dpll_hw_state.wrpll (expected 0xb0210614, found 0x00000000)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

This is a followup of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501260 .

Basically, running OpenGL applications (e.g. glxgears) on the primary
display handled by Intel 915 card results in display freeze. The error
message from the title of this bug is written to a VT console if I
switch to it. It seems this bug only appears when multiple monitors are
connected.

Switching to a VT (Ctrl+Alt+F1) and back unfreezes the screen for a
while. The screen only looks frozen, but normally reacts to mouse and
keyboard events. This only happens if the GL window is displayed on my
primary display (which is handled by the intel integrated chip). The
notebook has 2 video outputs and a discrete AMD graphics, and I think
only one of the outputs is handled by the AMD card, so I think one of
the outputs is handled by the intel card and does not get frozen.

Ubuntu 14.04.3 64bit.

I think that before upgrading from 14.04.2 to 14.04.3 this did not
happen.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-4.2.0-30-generic 4.2.0-30.36~14.04.1
ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
Uname: Linux 4.2.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Mar  8 02:43:37 2016
InstallationDate: Installed on 2013-11-05 (853 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: linux-lts-wily
UpgradeStatus: Upgraded to trusty on 2014-04-12 (695 days ago)

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


** Tags: amd64 apport-bug trusty
-- 
drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in dpll_hw_state.wrpll 
(expected 0xb0210614, found 0x)
https://bugs.launchpad.net/bugs/1554299
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1538040] Re: Internal Hard drive extremely slow unless using barrier=0 on ext4

[Christopher M. Penalver]

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

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

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

Title:
  Internal Hard drive extremely slow unless using barrier=0 on ext4

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I have a brand new laptop (Asus N551VW, i7-6700HQ, 16 Gb ram) on which
  i installed Ubuntu 14.04 64bit and a new Samsung SSD 850 PRO 512Gb
  (latest firmware). I installed the default MySql 5.6.27 on the machine
  but I noticed a very VERY slow performance of the database (just
  creating a db and executing some migrations without any data takes
  around 33 seconds while on lower-hardware co-workers notebooks it
  takes like 3 seconds). Every sql statement seems to spend most time in
  "system lock" state, as i could see with a SHOW PROCESSLIST.

  I thought it to be an hard drive issue, but executing the hard drive
  benchmark in Ubuntu gives 500 Mb/s read and 350 Mb/s write speed,
  which looks mostly normal.

  I also tried updating to the new 4.2 kernel, but the issue still
  there. To make an experiment, i cloned the ssd on a normal hard drive,
  switched it in and connected the SSD externally with an usb box. I
  moved mysql data directory to the external disk, and retried the db
  creation: it took only 2.5 seconds.

  Just out of curiosity i tried the same operation on an internal non-
  ssd disk: when the hd is plugged inside the laptop with sata, the
  database creation takes more than 2 minutes, while with the data dir
  on external usb (with the same physical disk) it took less than 10
  seconds.

  WORKAROUND: Add barrier=0 to root drive mount options with no other
  modification caused the same script to take 1.5 seconds instead of 33,
  with a 22x increase in performance.

  I have opened his bug on askubuntu 
(http://askubuntu.com/questions/725182/ssd-extremely-slow-when-connected-with-internal-sata-ok-with-external-usb
 ) and it was suggested that this coud be an issue of the controller 
firmware/driver.
  The problem is present both in trusty's default kernel (3.19.0-47.53) and in 
the 4.2 (4.2.0-25.30).

  ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  valerio2776 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=e5eee076-9bfc-4547-bf85-0208b98b57a8
  InstallationDate: Installed on 2016-01-06 (60 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. N551VW
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=5231fd09-180d-4fd2-bad5-e989207b11e7 ro quiet splash 
elevator=deadline vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  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-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.127.20
  Tags:  trusty
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N551VW.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N551VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN551VW.205:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnN551VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N551VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Tim Gardner]

Why are we diverging from other architectures ? There is nothing in this
bug that describes any deleterious effects caused by these config
settings.

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

Title:
  kernel: update kernel configuration

Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Hendrik Brueckner  - 2016-02-08 
09:41:49 ==
  The below mentioned kernel configuration options are still not yet integrated 
into the Ubuntu kernel. In addition to the discussions on the skipper mailing 
list, hereby the bugzilla / launchpad to integrate and update the kernel 
configuration.

  > Short explaination for all requested changes:
  >
  > CONFIG_NUMA (and all related config options):
  > s390 gained fake NUMA support with kernel version 4.3. Performance
  > measurements did show that this helps for very large machines (lot's of
  > memory), and also doesn't hurt for small machines.  Therfore the config
  > option should be enabled.
  >
  > CONFIG_PREEMPT_NONE:
  > We only have performance numbers for non-preemptible kernels. While kernel
  > preemption generally should work from a functional point of view on s390,
  > we do not have numbers about the performance costs. Nor do we have any
  > production systems running with kernel preemption enabled currently.
  > Therefore let's please switch to PREEMPT_NONE which has proven to work.
  >
  > CONFIG_SCSI_SCAN_ASYNC:
  > Hendrik already requested to disable this config option.
  >
  > CONFIG_REGMAP,
  > CONFIG_NET_VENDOR_EMULEX,
  > CONFIG_BE2NET,
  > CONFIG_BE2NET_VXLAN,
  > CONFIG_NET_VENDOR_SYNOPSYS,
  > CONFIG_NVMEM:
  > Looks like all of these crept in with the kernel update to 4.3. None of
  > these are relevant to s390 and can be disabled.

  An updated config patch to the kernel version above will be added

  
  
  Kernel-Description: s390x -- clear out hardware related configuration item

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543165/+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 1551854] Re: LXD bootstrap issues on xenial

[Stéphane Graber]

** Package changed: linux (Ubuntu) => lxd (Ubuntu)

** Changed in: lxd (Ubuntu)
 Assignee: (unassigned) => Stéphane Graber (stgraber)

** Changed in: lxd (Ubuntu)
   Status: Incomplete => 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/1551854

Title:
  LXD bootstrap issues on xenial

Status in lxd package in Ubuntu:
  Fix Committed

Bug description:
  I'm using lxd with zfs block storage on xenial, and having issues with
  trusty containers. I've witnessed this problem when trying to
  bootstrap as well as after rebooting the host and a container failed
  to start.

  In the latter case, the container that failed to start was the juju
  controller:

  c@mawhrin-skel:~/omnibus-layers$ lxc list 
   [3/3]
  
+-+-++--++---+
  |NAME |  STATE  | 
 IPV4  | IPV6 |TYPE| SNAPSHOTS |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0 | STOPPED | 
   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-1 | RUNNING | 10.0.3.28 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-2 | RUNNING | 10.0.3.85 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-3 | RUNNING | 10.0.3.176 
(eth0)  |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-4 | RUNNING | 10.0.3.66 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-5 | RUNNING | 10.0.3.31 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-6 | RUNNING | 10.0.3.196 
(eth0)  |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-7 | RUNNING | 10.0.3.186 
(eth0)  |  | PERSISTENT | 0 |
  | | | 10.0.4.1 
(lxcbr0)  |  ||   |
  
+-+-++--++---+

  I manually started it, but found that no upstart services were
  started. Remembering this thread,
  https://lists.ubuntu.com/archives/juju/2016-February/006698.html, I
  checked /var/log/mountall.log in the machine-0 container, and sure
  enough:

  root@juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0:~# cat 
/var/log/upstart/mountall.log
  mount: permission denied
  mountall: mount /sys/kernel/debug [187] terminated with status 32
  mountall: Filesystem could not be mounted: /sys/kernel/debug

  The problem persists if I stop and start the container. If I remount
  /sys/kernel/debug on the host, then stop and start the container,
  upstart succeeds and the juju controller starts up.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-8-generic 4.4.0-8.23
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  c 24562 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Mar  1 10:52:45 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=007cedda-f922-4e4c-89b1-57b31f18292e
  InstallationDate: Installed on 2016-02-28 (2 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial 

[Kernel-packages] [Bug 1374759] Re: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old

[Thiago Martins]

I'm seeing this BUG on most recent Xenial Beta release (updated today).

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

Title:
  >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is
  ufstype=old

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in os-prober package in Ubuntu:
  Confirmed
Status in os-prober package in Debian:
  Fix Released

Bug description:
  [  556.734157] SGI XFS with ACLs, security attributes, realtime, large 
block/inode numbers, no debug enabled
  [  556.746268] JFS: nTxBlock = 8192, nTxLock = 65536
  [  556.763789] ntfs: driver 2.1.30 [Flags: R/O MODULE].
  [  556.792231] QNX4 filesystem 0.2.3 registered.
  [  557.922469] EXT4-fs (sda4): unable to read superblock
  [  557.925868] EXT4-fs (sda4): unable to read superblock
  [  557.928967] EXT4-fs (sda4): unable to read superblock
  [  557.931784] FAT-fs (sda4): bogus number of reserved sectors
  [  557.931791] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  557.946740] XFS (sda4): Invalid superblock magic number
  [  557.951904] FAT-fs (sda4): bogus number of reserved sectors
  [  557.951911] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  557.959099] MINIX-fs: unable to read superblock
  [  557.965712] attempt to access beyond end of device
  [  557.965721] sda4: rw=16, want=3, limit=2
  [  557.965725] hfsplus: unable to find HFS+ superblock
  [  557.968487] qnx4: no qnx4 filesystem (no root dir).
  [  557.971203] You didn't specify the type of your ufs filesystem

  mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep
  |nextstep-cd|openstep ...

  >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is 
ufstype=old
  [  557.974459] hfs: can't find a HFS filesystem on dev sda4
  [  564.034208] EXT4-fs (sda4): unable to read superblock
  [  564.040322] EXT4-fs (sda4): unable to read superblock
  [  564.043485] EXT4-fs (sda4): unable to read superblock
  [  564.047076] FAT-fs (sda4): bogus number of reserved sectors
  [  564.047083] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  564.059578] XFS (sda4): Invalid superblock magic number
  [  564.064473] FAT-fs (sda4): bogus number of reserved sectors
  [  564.064489] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  564.072080] MINIX-fs: unable to read superblock
  [  564.074564] attempt to access beyond end of device
  [  564.074571] sda4: rw=16, want=3, limit=2
  [  564.074576] hfsplus: unable to find HFS+ superblock
  [  564.076688] qnx4: no qnx4 filesystem (no root dir).
  [  564.078847] You didn't specify the type of your ufs filesystem

  mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep
  |nextstep-cd|openstep ...

  >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is 
ufstype=old
  [  564.080902] hfs: can't find a HFS filesystem on dev sda4
  [  570.554296] EXT4-fs (sda4): unable to read superblock
  [  570.557647] EXT4-fs (sda4): unable to read superblock
  [  570.560516] EXT4-fs (sda4): unable to read superblock
  [  570.563451] FAT-fs (sda4): bogus number of reserved sectors
  [  570.563460] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  570.574953] XFS (sda4): Invalid superblock magic number
  [  570.580796] FAT-fs (sda4): bogus number of reserved sectors
  [  570.580806] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  570.588340] MINIX-fs: unable to read superblock
  [  570.590983] attempt to access beyond end of device
  [  570.590993] sda4: rw=16, want=3, limit=2
  [  570.590999] hfsplus: unable to find HFS+ superblock
  [  570.593321] qnx4: no qnx4 filesystem (no root dir).
  [  570.595556] You didn't specify the type of your ufs filesystem

  mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep
  |nextstep-cd|openstep ...

  >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is 
ufstype=old
  [  570.597775] hfs: can't find a HFS filesystem on dev sda4
  [  576.795014] EXT4-fs (sda4): unable to read superblock
  [  576.797554] EXT4-fs (sda4): unable to read superblock
  [  576.800063] EXT4-fs (sda4): unable to read superblock
  [  576.802647] FAT-fs (sda4): bogus number of reserved sectors
  [  576.802655] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  576.813305] XFS (sda4): Invalid superblock magic number
  [  576.820257] FAT-fs (sda4): bogus number of reserved sectors
  [  576.820276] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  576.830945] MINIX-fs: unable to read superblock
  [  576.834108] attempt to access beyond end of device
  [  576.834119] sda4: rw=16, want=3, limit=2
  [  576.834125] hfsplus: unable to find HFS+ superblock
  [  576.837264] qnx4: no qnx4 filesystem (no root dir).
  [  576.840408] You didn't specify the type of your ufs filesystem

  mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep
  

[Kernel-packages] [Bug 1475078] Re: VirtIO (and probably other modules as well) is built-in, make it modular...

[Thiago Martins]

Any news about this guys?

I'm on Linux 4.4.0-11-generic  / Xenial and the kernel  isn't modular
yet!

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

Title:
  VirtIO (and probably other modules as well) is built-in, make it
  modular...

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Guys,

  Can Canonical ship Ubuntu with its Linux in a modular way?

  Honestly, don't understand why some modules are compiled as built-in,
  instead of modules, for example (NET/BLK/PCI/etc):

  ---
  ubuntu@vivid-1:~$ grep VIRTIO /boot/config-3.19.0-23-generic 
  CONFIG_NET_9P_VIRTIO=m
  CONFIG_VIRTIO_BLK=y
  CONFIG_SCSI_VIRTIO=m
  CONFIG_VIRTIO_NET=y
  CONFIG_CAIF_VIRTIO=m
  CONFIG_VIRTIO_CONSOLE=y
  CONFIG_HW_RANDOM_VIRTIO=m
  CONFIG_VIRTIO=y
  CONFIG_VIRTIO_PCI=y
  CONFIG_VIRTIO_BALLOON=y
  CONFIG_VIRTIO_MMIO=y
  CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y
  ---

  While on Debian, it is all modular, as expected:

  ---
  debian@jessie-1:~# grep VIRTIO /boot/config-3.16.0-4-amd64 
  CONFIG_NET_9P_VIRTIO=m
  CONFIG_VIRTIO_BLK=m
  CONFIG_SCSI_VIRTIO=m
  CONFIG_VIRTIO_NET=m
  CONFIG_VIRTIO_CONSOLE=m
  CONFIG_HW_RANDOM_VIRTIO=m
  CONFIG_VIRTIO=m
  CONFIG_VIRTIO_PCI=m
  CONFIG_VIRTIO_BALLOON=m
  # CONFIG_VIRTIO_MMIO is not set
  ---

  I see no reason to load this modules in a non-virtualized
  environments.

  Thoughts!?

  Best,
  Thiago

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-23-generic 3.19.0-23.24
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tmartins   3485 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jul 15 21:44:14 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-27 (261 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Apple Inc. MacBookAir4,2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic.efi.signed 
root=UUID=f64e109d-bc06-43ec-8ca8-d10e4f915d2e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-22-generic N/A
   linux-backports-modules-3.19.0-22-generic  N/A
   linux-firmware 1.143.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-02-02 (163 days ago)
  dmi.bios.date: 10/09/2013
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA41.88Z.0077.B11.1310091428
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-742912EFDBEE19B3
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir4,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-742912EFDBEE19B3
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B11.1310091428:bd10/09/2013:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3:
  dmi.product.name: MacBookAir4,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475078/+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 1481357] Re: [LTCTest][Kernel][OP810]Ubuntu14.04.3: kernel call trace while continuously switching between smt on/off and changing subcores

[Tim Gardner]

Install linux-generic which depends on all of the required kernel
packages.

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

Title:
  [LTCTest][Kernel][OP810]Ubuntu14.04.3: kernel call trace while
  continuously switching between smt on/off and changing subcores

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

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2015-07-14 
02:32:22 ==
  While running the below script, and nothing else was running in the system, 
host got the kernel call traces after around 15~20 mins

  #!/bin/bash -x
  while true;
  do for i in 1 2 4;
  do ppc64_cpu  --subcores-per-core=$i;
  ppc64_cpu --info
  ppc64_cpu --smt=off;
  ppc64_cpu --info
  sleep 1;
  lscpu
  ppc64_cpu --smt=on;
  ppc64_cpu --info
  sleep 1;
  lscpu
  done;
  sleep 1;
  done

  
  Environment:
  --
  $ cat /etc/issue
  Ubuntu 14.04.2 LTS \n \l

  $ uname -a
  Linux tul8fp 3.19.0-22-generic #22~14.04.1-Ubuntu SMP Wed Jun 17 10:03:39 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux

  $ lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):160
  On-line CPU(s) list:   
0,4,8,12,16,20,24,28,32,36,40,44,48,52,56,60,64,68,72,76,80,84,88,92,96,100,104,108,112,116,120,124,128,132,136,138-159
  Off-line CPU(s) list:  
1-3,5-7,9-11,13-15,17-19,21-23,25-27,29-31,33-35,37-39,41-43,45-47,49-51,53-55,57-59,61-63,65-67,69-71,73-75,77-79,81-83,85-87,89-91,93-95,97-99,101-103,105-107,109-111,113-115,117-119,121-123,125-127,129-131,133-135,137
  Thread(s) per core:2
  Core(s) per socket:10
  Socket(s): 2
  NUMA node(s):  2
  Model: 8335-GTA
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 
0,4,88,92,96,100,104,108,112,116,120,124,128,132,136,138-159
  NUMA node8 CPU(s): 
8,12,16,20,24,28,32,36,40,44,48,52,56,60,64,68,72,76,80,84

  $ tail -10 /proc/cpuinfo 
  processor : 159
  cpu   : POWER8 (raw), altivec supported
  clock : 2693.00MHz
  revision  : 2.0 (pvr 004d 0200)

  timebase  : 51200
  platform  : PowerNV
  model : 8335-GTA
  machine   : PowerNV 8335-GTA
  firmware  : OPAL v3

  Logs:-
  -

  
  # dmesg
  [79081.074088] INFO: task irqbalance:1897 blocked for more than 120 seconds.
  [79081.074333]   Not tainted 3.19.0-22-generic #22~14.04.1-Ubuntu
  [79081.074388] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [79081.074449] irqbalance  D 3fff9ac39d3c 0  1897  1 
0x0004
  [79081.074454] Call Trace:
  [79081.074470] [c007e8d035f0] [3fff9af5] 0x3fff9af5 
(unreliable)
  [79081.074477] [c007e8d037c0] [c0015934] __switch_to+0x204/0x350
  [79081.074482] [c007e8d03820] [c0a11508] __schedule+0x368/0x8d0
  [79081.074486] --- interrupt: 1000ba30 at 0xc007e8d039f0
  [79081.074486] LR = 0x10026a6c1d0
  [79081.074490] [c007e8d03a40] [c0a120a0] 
schedule_preempt_disabled+0x20/0x30 (unreliable)
  [79081.074494] [c007e8d03a60] [c0a1420c] 
__mutex_lock_slowpath+0xfc/0x1f0
  [79081.074497] [c007e8d03ae0] [c0a1436c] mutex_lock+0x6c/0x70
  [79081.074501] [c007e8d03b10] [c064488c] online_show+0x3c/0x90
  [79081.074503] [c007e8d03b90] [c0644fec] dev_attr_show+0x5c/0xc0
  [79081.074508] [c007e8d03bd0] [c035b7f4] 
sysfs_kf_seq_show+0x114/0x200
  [79081.074511] [c007e8d03c20] [c03591e4] kernfs_seq_show+0x54/0x70
  [79081.074515] [c007e8d03c50] [c02e74fc] seq_read+0xec/0x500
  [79081.074519] [c007e8d03cf0] [c035a474] 
kernfs_fop_read+0x184/0x220
  [79081.074523] [c007e8d03d50] [c02b520c] __vfs_read+0x6c/0x120
  [79081.074527] [c007e8d03d90] [c02b5364] vfs_read+0xa4/0x1c0
  [79081.074530] [c007e8d03de0] [c02b54ec] SyS_read+0x6c/0x110
  [79081.074534] [c007e8d03e30] [c0009258] system_call+0x38/0xd0
  [79081.074546] INFO: task ppc64_cpu:111047 blocked for more than 120 seconds.
  [79081.074597]   Not tainted 3.19.0-22-generic #22~14.04.1-Ubuntu
  [79081.074802] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [79081.074865] ppc64_cpu   D 3fff82892d08 0 111047 109995 
0x0004
  [79081.074868] Call Trace:
  [79081.074871] [c00f1c67f680] [c00f1c67f710] 0xc00f1c67f710 
(unreliable)
  [79081.074875] [c00f1c67f850] [c0015934] __switch_to+0x204/0x350
  [79081.074878] [c00f1c67f8b0] [c0a11508] __schedule+0x368/0x8d0
  

[Kernel-packages] [Bug 1553391] Re: linux: 4.4.0-11.26 -proposed tracker

[Adam Conrad]

** Changed in: kernel-development-workflow/promote-to-release
   Status: New => Fix Released

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

** Changed in: kernel-development-workflow/regression-testing
   Status: Incomplete => Fix Released

** Changed in: kernel-development-workflow/automated-testing
   Status: Incomplete => Fix Released

** Changed in: kernel-development-workflow
   Status: Incomplete => 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/1553391

Title:
  linux: 4.4.0-11.26 -proposed tracker

Status in Kernel Development Workflow:
  Fix Released
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:
  Fix Released
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Friday, 04. March 2016 22:33 UTC
  kernel-stable-Promote-to-proposed-end:Saturday, 05. March 2016 00:00 UTC
  proposed-announcement-sent:True
  kernel-phase:OnHold
  kernel-phase-changed:Monday, 07. March 2016 21:00 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1553391/+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 1501260] Re: drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in dpll_hw_state.wrpll (expected 0xb0210614, found 0x00000000

[Martin Pecka]

@penalvch: Reported: https://bugs.launchpad.net/ubuntu/+source/linux-
lts-wily/+bug/1554299

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

Title:
  drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in
  dpll_hw_state.wrpll (expected 0xb0210614, found 0x

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While surfing, I clicked on something,, X died, I was thrown back to a 
console and finally was able to log back in.
  dmesg is cluttered with:
   

  
  [79849.958943] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in 
dpll_hw_state.wrpll (expected 0xb0210614, found 0x)
  [79849.958944] [ cut here ]
  [79849.958962] WARNING: CPU: 0 PID: 14689 at 
/build/linux-1dujk3/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12326 
check_crtc_state+0x2c5/0x440 [i915]()
  [79849.958963] pipe state doesn't match!
  [79849.958981] Modules linked in: bnep bluetooth binfmt_misc nls_iso8859_1 
intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi 
coretemp snd_hda_codec_realtek input_leds snd_hda_codec_generic kvm_intel 
snd_hda_intel kvm snd_hda_codec snd_hda_core snd_hwdep snd_pcm crct10dif_pclmul 
snd_seq_midi snd_seq_midi_event snd_rawmidi crc32_pclmul ghash_clmulni_intel 
snd_seq snd_seq_device snd_timer mei_me aesni_intel snd mei aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd soundcore serio_raw 8250_fintek 
fujitsu_laptop lpc_ich tpm_infineon mac_hid parport_pc ppdev lp parport autofs4 
hid_generic usbhid hid i915 psmouse ahci libahci i2c_algo_bit drm_kms_helper 
e1000e drm ptp pps_core video
  [79849.958983] CPU: 0 PID: 14689 Comm: Xorg Tainted: GW   
4.2.0-11-generic #13-Ubuntu
  [79849.958983] Hardware name: FUJITSU ESPRIMO E920/D3222-A1, BIOS V4.6.5.4 
R1.34.0 for D3222-A1x 01/08/2015
  [79849.958985]  c0232ab0 88030edef538 817b0cc5 

  [79849.958986]  88030edef588 88030edef578 81076536 
88030edef5a8
  [79849.958986]  88030edef610 88030a600800 0001 
88030a600b50
  [79849.958987] Call Trace:
  [79849.958991]  [] dump_stack+0x45/0x57
  [79849.958994]  [] warn_slowpath_common+0x86/0xc0
  [79849.958995]  [] warn_slowpath_fmt+0x46/0x50
  [79849.959008]  [] ? intel_pipe_config_compare+0xa67/0xc60 
[i915]
  [79849.959015]  [] check_crtc_state+0x2c5/0x440 [i915]
  [79849.959024]  [] intel_modeset_check_state+0x20e/0x6b0 
[i915]
  [79849.959032]  [] intel_crtc_set_config+0x4c7/0x580 [i915]
  [79849.959042]  [] drm_mode_set_config_internal+0x66/0x100 
[drm]
  [79849.959045]  [] restore_fbdev_mode+0xc2/0xf0 
[drm_kms_helper]
  [79849.959048]  [] 
drm_fb_helper_restore_fbdev_mode_unlocked+0x29/0x70 [drm_kms_helper]
  [79849.959050]  [] drm_fb_helper_set_par+0x22/0x40 
[drm_kms_helper]
  [79849.959060]  [] intel_fbdev_set_par+0x1a/0x60 [i915]
  [79849.959062]  [] ? ttwu_do_activate.constprop.89+0x5d/0x70
  [79849.959064]  [] fb_set_var+0x238/0x460
  [79849.959066]  [] ? do_sys_poll+0x127/0x5a0
  [79849.959068]  [] fbcon_blank+0x2e9/0x330
  [79849.959070]  [] ? check_preempt_wakeup+0x193/0x220
  [79849.959071]  [] do_unblank_screen+0xd3/0x1a0
  [79849.959073]  [] vt_ioctl+0x4fb/0x12c0
  [79849.959074]  [] ? default_wake_function+0x12/0x20
  [79849.959076]  [] ? autoremove_wake_function+0x16/0x40
  [79849.959078]  [] tty_ioctl+0x3cc/0xbb0
  [79849.959079]  [] ? __wake_up+0x48/0x60
  [79849.959080]  [] ? wake_nocb_leader+0x4d/0x50
  [79849.959081]  [] ? __call_rcu_nocb_enqueue+0xcd/0xd0
  [79849.959083]  [] do_vfs_ioctl+0x285/0x470
  [79849.959084]  [] ? mntput+0x24/0x40
  [79849.959085]  [] ? __fput+0x190/0x220
  [79849.959086]  [] SyS_ioctl+0x79/0x90
  [79849.959088]  [] entry_SYSCALL_64_fastpath+0x16/0x75
  [79849.959089] ---[ end trace c15f693470bdbc48 ]---
  [79849.959131] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in 
dpll_hw_state.wrpll (expected 0xb0210614, found 0x)
  [79849.959131] [ cut here ]

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-11-generic 4.2.0-11.13
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hildeb25581 F pulseaudio
   /dev/snd/controlC1:  hildeb25581 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep 30 12:04:59 2015
  HibernationDevice: RESUME=UUID=d5037585-3853-4049-a410-b17d0c104ef3
  InstallationDate: Installed on 2014-06-19 (467 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: FUJITSU ESPRIMO E920
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1547884] Lspci.txt

[Martin Pecka]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1547884/+attachment/4592103/+files/Lspci.txt

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

Title:
  Broadcom Corp. BCM5880 Secure Applications Processor eats too much
  power

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $ lsusb
  Bus 004 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor

  $ sudo powertop
  Power est.  Usage   Events/sKategorie   Popis
24.3 W100,0%  Device USB device: 5880 
(Broadcom Corp)

  On my Dell Latitude E6540 I constantly see this USB device eating
  about 20 W of power (and I don't see a reason for this kind of device
  to take that much power). And yes, the fan is always running, even
  when the computer is completely idle.

  The computer has no fingerprint reader (though it was an optional
  accessory, so the chip is IMHO built to support it). I use the
  integrated smartcard reader (also handled by this chip). I've set up
  PAM and LightDM to support smartcard login. However, the power usage
  is the same regardless of whether a smartcard is inserted or not. I do
  not intentionally use the integrated TPM chip in any way.

  I faced this problem also on Ubuntu 14.04.3 with 3.19 kernel.

  Eventually, this could also be a bug in powertop, but the fan almost
  never stops (even with display backlight to minimum), so I think
  powertop could be correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 20 15:33:49 2016
  InstallationDate: Installed on 2013-11-05 (837 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (678 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peci1  2919 F pulseaudio
   /dev/snd/pcmC1D0p:   peci1  2919 F...m pulseaudio
   /dev/snd/controlC1:  peci1  2919 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=05314bb8-8590-474c-8af1-1c90dd3bb89c
  InstallationDate: Installed on 2013-11-05 (853 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Latitude E6540
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=501ffea4-2b36-441b-a8ca-34805170c396 ro i8042.nopnp quiet splash 
radeon.modeset=1 radeon.dpm=1 i915.modeset=1 radeon.runpm=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.127.20
  Tags:  trusty
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (695 days ago)
  UserGroups: adm autosshfs cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0CYT5F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0CYT5F:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6540
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

[Martin Pecka]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1547884/+attachment/4592107/+files/ProcInterrupts.txt

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

Title:
  Broadcom Corp. BCM5880 Secure Applications Processor eats too much
  power

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $ lsusb
  Bus 004 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor

  $ sudo powertop
  Power est.  Usage   Events/sKategorie   Popis
24.3 W100,0%  Device USB device: 5880 
(Broadcom Corp)

  On my Dell Latitude E6540 I constantly see this USB device eating
  about 20 W of power (and I don't see a reason for this kind of device
  to take that much power). And yes, the fan is always running, even
  when the computer is completely idle.

  The computer has no fingerprint reader (though it was an optional
  accessory, so the chip is IMHO built to support it). I use the
  integrated smartcard reader (also handled by this chip). I've set up
  PAM and LightDM to support smartcard login. However, the power usage
  is the same regardless of whether a smartcard is inserted or not. I do
  not intentionally use the integrated TPM chip in any way.

  I faced this problem also on Ubuntu 14.04.3 with 3.19 kernel.

  Eventually, this could also be a bug in powertop, but the fan almost
  never stops (even with display backlight to minimum), so I think
  powertop could be correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 20 15:33:49 2016
  InstallationDate: Installed on 2013-11-05 (837 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (678 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peci1  2919 F pulseaudio
   /dev/snd/pcmC1D0p:   peci1  2919 F...m pulseaudio
   /dev/snd/controlC1:  peci1  2919 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=05314bb8-8590-474c-8af1-1c90dd3bb89c
  InstallationDate: Installed on 2013-11-05 (853 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Latitude E6540
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=501ffea4-2b36-441b-a8ca-34805170c396 ro i8042.nopnp quiet splash 
radeon.modeset=1 radeon.dpm=1 i915.modeset=1 radeon.runpm=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.127.20
  Tags:  trusty
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (695 days ago)
  UserGroups: adm autosshfs cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0CYT5F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0CYT5F:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6540
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

[Martin Pecka]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1547884/+attachment/4592111/+files/UdevDb.txt

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

Title:
  Broadcom Corp. BCM5880 Secure Applications Processor eats too much
  power

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $ lsusb
  Bus 004 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor

  $ sudo powertop
  Power est.  Usage   Events/sKategorie   Popis
24.3 W100,0%  Device USB device: 5880 
(Broadcom Corp)

  On my Dell Latitude E6540 I constantly see this USB device eating
  about 20 W of power (and I don't see a reason for this kind of device
  to take that much power). And yes, the fan is always running, even
  when the computer is completely idle.

  The computer has no fingerprint reader (though it was an optional
  accessory, so the chip is IMHO built to support it). I use the
  integrated smartcard reader (also handled by this chip). I've set up
  PAM and LightDM to support smartcard login. However, the power usage
  is the same regardless of whether a smartcard is inserted or not. I do
  not intentionally use the integrated TPM chip in any way.

  I faced this problem also on Ubuntu 14.04.3 with 3.19 kernel.

  Eventually, this could also be a bug in powertop, but the fan almost
  never stops (even with display backlight to minimum), so I think
  powertop could be correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 20 15:33:49 2016
  InstallationDate: Installed on 2013-11-05 (837 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (678 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peci1  2919 F pulseaudio
   /dev/snd/pcmC1D0p:   peci1  2919 F...m pulseaudio
   /dev/snd/controlC1:  peci1  2919 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=05314bb8-8590-474c-8af1-1c90dd3bb89c
  InstallationDate: Installed on 2013-11-05 (853 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Latitude E6540
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=501ffea4-2b36-441b-a8ca-34805170c396 ro i8042.nopnp quiet splash 
radeon.modeset=1 radeon.dpm=1 i915.modeset=1 radeon.runpm=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.127.20
  Tags:  trusty
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (695 days ago)
  UserGroups: adm autosshfs cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0CYT5F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0CYT5F:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6540
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

[Martin Pecka]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1547884/+attachment/4592110/+files/RfKill.txt

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

Title:
  Broadcom Corp. BCM5880 Secure Applications Processor eats too much
  power

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $ lsusb
  Bus 004 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor

  $ sudo powertop
  Power est.  Usage   Events/sKategorie   Popis
24.3 W100,0%  Device USB device: 5880 
(Broadcom Corp)

  On my Dell Latitude E6540 I constantly see this USB device eating
  about 20 W of power (and I don't see a reason for this kind of device
  to take that much power). And yes, the fan is always running, even
  when the computer is completely idle.

  The computer has no fingerprint reader (though it was an optional
  accessory, so the chip is IMHO built to support it). I use the
  integrated smartcard reader (also handled by this chip). I've set up
  PAM and LightDM to support smartcard login. However, the power usage
  is the same regardless of whether a smartcard is inserted or not. I do
  not intentionally use the integrated TPM chip in any way.

  I faced this problem also on Ubuntu 14.04.3 with 3.19 kernel.

  Eventually, this could also be a bug in powertop, but the fan almost
  never stops (even with display backlight to minimum), so I think
  powertop could be correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 20 15:33:49 2016
  InstallationDate: Installed on 2013-11-05 (837 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (678 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peci1  2919 F pulseaudio
   /dev/snd/pcmC1D0p:   peci1  2919 F...m pulseaudio
   /dev/snd/controlC1:  peci1  2919 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=05314bb8-8590-474c-8af1-1c90dd3bb89c
  InstallationDate: Installed on 2013-11-05 (853 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Latitude E6540
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=501ffea4-2b36-441b-a8ca-34805170c396 ro i8042.nopnp quiet splash 
radeon.modeset=1 radeon.dpm=1 i915.modeset=1 radeon.runpm=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.127.20
  Tags:  trusty
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (695 days ago)
  UserGroups: adm autosshfs cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0CYT5F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0CYT5F:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6540
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

[Martin Pecka]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1547884/+attachment/4592104/+files/Lsusb.txt

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

Title:
  Broadcom Corp. BCM5880 Secure Applications Processor eats too much
  power

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $ lsusb
  Bus 004 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor

  $ sudo powertop
  Power est.  Usage   Events/sKategorie   Popis
24.3 W100,0%  Device USB device: 5880 
(Broadcom Corp)

  On my Dell Latitude E6540 I constantly see this USB device eating
  about 20 W of power (and I don't see a reason for this kind of device
  to take that much power). And yes, the fan is always running, even
  when the computer is completely idle.

  The computer has no fingerprint reader (though it was an optional
  accessory, so the chip is IMHO built to support it). I use the
  integrated smartcard reader (also handled by this chip). I've set up
  PAM and LightDM to support smartcard login. However, the power usage
  is the same regardless of whether a smartcard is inserted or not. I do
  not intentionally use the integrated TPM chip in any way.

  I faced this problem also on Ubuntu 14.04.3 with 3.19 kernel.

  Eventually, this could also be a bug in powertop, but the fan almost
  never stops (even with display backlight to minimum), so I think
  powertop could be correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 20 15:33:49 2016
  InstallationDate: Installed on 2013-11-05 (837 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (678 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peci1  2919 F pulseaudio
   /dev/snd/pcmC1D0p:   peci1  2919 F...m pulseaudio
   /dev/snd/controlC1:  peci1  2919 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=05314bb8-8590-474c-8af1-1c90dd3bb89c
  InstallationDate: Installed on 2013-11-05 (853 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Latitude E6540
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=501ffea4-2b36-441b-a8ca-34805170c396 ro i8042.nopnp quiet splash 
radeon.modeset=1 radeon.dpm=1 i915.modeset=1 radeon.runpm=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.127.20
  Tags:  trusty
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (695 days ago)
  UserGroups: adm autosshfs cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0CYT5F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0CYT5F:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6540
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

[Martin Pecka]

apport information

** Attachment added: "UdevLog.txt"
   
https://bugs.launchpad.net/bugs/1547884/+attachment/4592112/+files/UdevLog.txt

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

Title:
  Broadcom Corp. BCM5880 Secure Applications Processor eats too much
  power

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $ lsusb
  Bus 004 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor

  $ sudo powertop
  Power est.  Usage   Events/sKategorie   Popis
24.3 W100,0%  Device USB device: 5880 
(Broadcom Corp)

  On my Dell Latitude E6540 I constantly see this USB device eating
  about 20 W of power (and I don't see a reason for this kind of device
  to take that much power). And yes, the fan is always running, even
  when the computer is completely idle.

  The computer has no fingerprint reader (though it was an optional
  accessory, so the chip is IMHO built to support it). I use the
  integrated smartcard reader (also handled by this chip). I've set up
  PAM and LightDM to support smartcard login. However, the power usage
  is the same regardless of whether a smartcard is inserted or not. I do
  not intentionally use the integrated TPM chip in any way.

  I faced this problem also on Ubuntu 14.04.3 with 3.19 kernel.

  Eventually, this could also be a bug in powertop, but the fan almost
  never stops (even with display backlight to minimum), so I think
  powertop could be correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 20 15:33:49 2016
  InstallationDate: Installed on 2013-11-05 (837 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (678 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peci1  2919 F pulseaudio
   /dev/snd/pcmC1D0p:   peci1  2919 F...m pulseaudio
   /dev/snd/controlC1:  peci1  2919 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=05314bb8-8590-474c-8af1-1c90dd3bb89c
  InstallationDate: Installed on 2013-11-05 (853 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Latitude E6540
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=501ffea4-2b36-441b-a8ca-34805170c396 ro i8042.nopnp quiet splash 
radeon.modeset=1 radeon.dpm=1 i915.modeset=1 radeon.runpm=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.127.20
  Tags:  trusty
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (695 days ago)
  UserGroups: adm autosshfs cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0CYT5F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0CYT5F:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6540
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

[Martin Pecka]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1547884/+attachment/4592109/+files/PulseList.txt

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

Title:
  Broadcom Corp. BCM5880 Secure Applications Processor eats too much
  power

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $ lsusb
  Bus 004 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor

  $ sudo powertop
  Power est.  Usage   Events/sKategorie   Popis
24.3 W100,0%  Device USB device: 5880 
(Broadcom Corp)

  On my Dell Latitude E6540 I constantly see this USB device eating
  about 20 W of power (and I don't see a reason for this kind of device
  to take that much power). And yes, the fan is always running, even
  when the computer is completely idle.

  The computer has no fingerprint reader (though it was an optional
  accessory, so the chip is IMHO built to support it). I use the
  integrated smartcard reader (also handled by this chip). I've set up
  PAM and LightDM to support smartcard login. However, the power usage
  is the same regardless of whether a smartcard is inserted or not. I do
  not intentionally use the integrated TPM chip in any way.

  I faced this problem also on Ubuntu 14.04.3 with 3.19 kernel.

  Eventually, this could also be a bug in powertop, but the fan almost
  never stops (even with display backlight to minimum), so I think
  powertop could be correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 20 15:33:49 2016
  InstallationDate: Installed on 2013-11-05 (837 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (678 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peci1  2919 F pulseaudio
   /dev/snd/pcmC1D0p:   peci1  2919 F...m pulseaudio
   /dev/snd/controlC1:  peci1  2919 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=05314bb8-8590-474c-8af1-1c90dd3bb89c
  InstallationDate: Installed on 2013-11-05 (853 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Latitude E6540
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=501ffea4-2b36-441b-a8ca-34805170c396 ro i8042.nopnp quiet splash 
radeon.modeset=1 radeon.dpm=1 i915.modeset=1 radeon.runpm=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.127.20
  Tags:  trusty
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (695 days ago)
  UserGroups: adm autosshfs cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0CYT5F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0CYT5F:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6540
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

[Martin Pecka]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1547884/+attachment/4592105/+files/ProcCpuinfo.txt

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

Title:
  Broadcom Corp. BCM5880 Secure Applications Processor eats too much
  power

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $ lsusb
  Bus 004 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor

  $ sudo powertop
  Power est.  Usage   Events/sKategorie   Popis
24.3 W100,0%  Device USB device: 5880 
(Broadcom Corp)

  On my Dell Latitude E6540 I constantly see this USB device eating
  about 20 W of power (and I don't see a reason for this kind of device
  to take that much power). And yes, the fan is always running, even
  when the computer is completely idle.

  The computer has no fingerprint reader (though it was an optional
  accessory, so the chip is IMHO built to support it). I use the
  integrated smartcard reader (also handled by this chip). I've set up
  PAM and LightDM to support smartcard login. However, the power usage
  is the same regardless of whether a smartcard is inserted or not. I do
  not intentionally use the integrated TPM chip in any way.

  I faced this problem also on Ubuntu 14.04.3 with 3.19 kernel.

  Eventually, this could also be a bug in powertop, but the fan almost
  never stops (even with display backlight to minimum), so I think
  powertop could be correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 20 15:33:49 2016
  InstallationDate: Installed on 2013-11-05 (837 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (678 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peci1  2919 F pulseaudio
   /dev/snd/pcmC1D0p:   peci1  2919 F...m pulseaudio
   /dev/snd/controlC1:  peci1  2919 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=05314bb8-8590-474c-8af1-1c90dd3bb89c
  InstallationDate: Installed on 2013-11-05 (853 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Latitude E6540
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=501ffea4-2b36-441b-a8ca-34805170c396 ro i8042.nopnp quiet splash 
radeon.modeset=1 radeon.dpm=1 i915.modeset=1 radeon.runpm=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.127.20
  Tags:  trusty
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (695 days ago)
  UserGroups: adm autosshfs cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0CYT5F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0CYT5F:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6540
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

[Martin Pecka]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1547884/+attachment/4592102/+files/IwConfig.txt

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

Title:
  Broadcom Corp. BCM5880 Secure Applications Processor eats too much
  power

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $ lsusb
  Bus 004 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor

  $ sudo powertop
  Power est.  Usage   Events/sKategorie   Popis
24.3 W100,0%  Device USB device: 5880 
(Broadcom Corp)

  On my Dell Latitude E6540 I constantly see this USB device eating
  about 20 W of power (and I don't see a reason for this kind of device
  to take that much power). And yes, the fan is always running, even
  when the computer is completely idle.

  The computer has no fingerprint reader (though it was an optional
  accessory, so the chip is IMHO built to support it). I use the
  integrated smartcard reader (also handled by this chip). I've set up
  PAM and LightDM to support smartcard login. However, the power usage
  is the same regardless of whether a smartcard is inserted or not. I do
  not intentionally use the integrated TPM chip in any way.

  I faced this problem also on Ubuntu 14.04.3 with 3.19 kernel.

  Eventually, this could also be a bug in powertop, but the fan almost
  never stops (even with display backlight to minimum), so I think
  powertop could be correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 20 15:33:49 2016
  InstallationDate: Installed on 2013-11-05 (837 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (678 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peci1  2919 F pulseaudio
   /dev/snd/pcmC1D0p:   peci1  2919 F...m pulseaudio
   /dev/snd/controlC1:  peci1  2919 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=05314bb8-8590-474c-8af1-1c90dd3bb89c
  InstallationDate: Installed on 2013-11-05 (853 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Latitude E6540
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=501ffea4-2b36-441b-a8ca-34805170c396 ro i8042.nopnp quiet splash 
radeon.modeset=1 radeon.dpm=1 i915.modeset=1 radeon.runpm=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.127.20
  Tags:  trusty
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (695 days ago)
  UserGroups: adm autosshfs cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0CYT5F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0CYT5F:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6540
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

[Martin Pecka]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1547884/+attachment/4592108/+files/ProcModules.txt

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

Title:
  Broadcom Corp. BCM5880 Secure Applications Processor eats too much
  power

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $ lsusb
  Bus 004 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor

  $ sudo powertop
  Power est.  Usage   Events/sKategorie   Popis
24.3 W100,0%  Device USB device: 5880 
(Broadcom Corp)

  On my Dell Latitude E6540 I constantly see this USB device eating
  about 20 W of power (and I don't see a reason for this kind of device
  to take that much power). And yes, the fan is always running, even
  when the computer is completely idle.

  The computer has no fingerprint reader (though it was an optional
  accessory, so the chip is IMHO built to support it). I use the
  integrated smartcard reader (also handled by this chip). I've set up
  PAM and LightDM to support smartcard login. However, the power usage
  is the same regardless of whether a smartcard is inserted or not. I do
  not intentionally use the integrated TPM chip in any way.

  I faced this problem also on Ubuntu 14.04.3 with 3.19 kernel.

  Eventually, this could also be a bug in powertop, but the fan almost
  never stops (even with display backlight to minimum), so I think
  powertop could be correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 20 15:33:49 2016
  InstallationDate: Installed on 2013-11-05 (837 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (678 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peci1  2919 F pulseaudio
   /dev/snd/pcmC1D0p:   peci1  2919 F...m pulseaudio
   /dev/snd/controlC1:  peci1  2919 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=05314bb8-8590-474c-8af1-1c90dd3bb89c
  InstallationDate: Installed on 2013-11-05 (853 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Latitude E6540
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=501ffea4-2b36-441b-a8ca-34805170c396 ro i8042.nopnp quiet splash 
radeon.modeset=1 radeon.dpm=1 i915.modeset=1 radeon.runpm=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.127.20
  Tags:  trusty
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (695 days ago)
  UserGroups: adm autosshfs cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0CYT5F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0CYT5F:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6540
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

[Martin Pecka]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1547884/+attachment/4592106/+files/ProcEnviron.txt

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

Title:
  Broadcom Corp. BCM5880 Secure Applications Processor eats too much
  power

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $ lsusb
  Bus 004 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor

  $ sudo powertop
  Power est.  Usage   Events/sKategorie   Popis
24.3 W100,0%  Device USB device: 5880 
(Broadcom Corp)

  On my Dell Latitude E6540 I constantly see this USB device eating
  about 20 W of power (and I don't see a reason for this kind of device
  to take that much power). And yes, the fan is always running, even
  when the computer is completely idle.

  The computer has no fingerprint reader (though it was an optional
  accessory, so the chip is IMHO built to support it). I use the
  integrated smartcard reader (also handled by this chip). I've set up
  PAM and LightDM to support smartcard login. However, the power usage
  is the same regardless of whether a smartcard is inserted or not. I do
  not intentionally use the integrated TPM chip in any way.

  I faced this problem also on Ubuntu 14.04.3 with 3.19 kernel.

  Eventually, this could also be a bug in powertop, but the fan almost
  never stops (even with display backlight to minimum), so I think
  powertop could be correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 20 15:33:49 2016
  InstallationDate: Installed on 2013-11-05 (837 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (678 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peci1  2919 F pulseaudio
   /dev/snd/pcmC1D0p:   peci1  2919 F...m pulseaudio
   /dev/snd/controlC1:  peci1  2919 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=05314bb8-8590-474c-8af1-1c90dd3bb89c
  InstallationDate: Installed on 2013-11-05 (853 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Latitude E6540
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=501ffea4-2b36-441b-a8ca-34805170c396 ro i8042.nopnp quiet splash 
radeon.modeset=1 radeon.dpm=1 i915.modeset=1 radeon.runpm=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.127.20
  Tags:  trusty
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (695 days ago)
  UserGroups: adm autosshfs cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0CYT5F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0CYT5F:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6540
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

[Martin Pecka]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1547884/+attachment/4592113/+files/WifiSyslog.txt

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

Title:
  Broadcom Corp. BCM5880 Secure Applications Processor eats too much
  power

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $ lsusb
  Bus 004 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor

  $ sudo powertop
  Power est.  Usage   Events/sKategorie   Popis
24.3 W100,0%  Device USB device: 5880 
(Broadcom Corp)

  On my Dell Latitude E6540 I constantly see this USB device eating
  about 20 W of power (and I don't see a reason for this kind of device
  to take that much power). And yes, the fan is always running, even
  when the computer is completely idle.

  The computer has no fingerprint reader (though it was an optional
  accessory, so the chip is IMHO built to support it). I use the
  integrated smartcard reader (also handled by this chip). I've set up
  PAM and LightDM to support smartcard login. However, the power usage
  is the same regardless of whether a smartcard is inserted or not. I do
  not intentionally use the integrated TPM chip in any way.

  I faced this problem also on Ubuntu 14.04.3 with 3.19 kernel.

  Eventually, this could also be a bug in powertop, but the fan almost
  never stops (even with display backlight to minimum), so I think
  powertop could be correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 20 15:33:49 2016
  InstallationDate: Installed on 2013-11-05 (837 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (678 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peci1  2919 F pulseaudio
   /dev/snd/pcmC1D0p:   peci1  2919 F...m pulseaudio
   /dev/snd/controlC1:  peci1  2919 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=05314bb8-8590-474c-8af1-1c90dd3bb89c
  InstallationDate: Installed on 2013-11-05 (853 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Latitude E6540
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=501ffea4-2b36-441b-a8ca-34805170c396 ro i8042.nopnp quiet splash 
radeon.modeset=1 radeon.dpm=1 i915.modeset=1 radeon.runpm=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.127.20
  Tags:  trusty
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (695 days ago)
  UserGroups: adm autosshfs cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0CYT5F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0CYT5F:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6540
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

[Martin Pecka]

apport information

** Attachment added: "BootDmesg.txt"
   
https://bugs.launchpad.net/bugs/1547884/+attachment/4592099/+files/BootDmesg.txt

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

Title:
  Broadcom Corp. BCM5880 Secure Applications Processor eats too much
  power

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $ lsusb
  Bus 004 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor

  $ sudo powertop
  Power est.  Usage   Events/sKategorie   Popis
24.3 W100,0%  Device USB device: 5880 
(Broadcom Corp)

  On my Dell Latitude E6540 I constantly see this USB device eating
  about 20 W of power (and I don't see a reason for this kind of device
  to take that much power). And yes, the fan is always running, even
  when the computer is completely idle.

  The computer has no fingerprint reader (though it was an optional
  accessory, so the chip is IMHO built to support it). I use the
  integrated smartcard reader (also handled by this chip). I've set up
  PAM and LightDM to support smartcard login. However, the power usage
  is the same regardless of whether a smartcard is inserted or not. I do
  not intentionally use the integrated TPM chip in any way.

  I faced this problem also on Ubuntu 14.04.3 with 3.19 kernel.

  Eventually, this could also be a bug in powertop, but the fan almost
  never stops (even with display backlight to minimum), so I think
  powertop could be correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 20 15:33:49 2016
  InstallationDate: Installed on 2013-11-05 (837 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (678 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peci1  2919 F pulseaudio
   /dev/snd/pcmC1D0p:   peci1  2919 F...m pulseaudio
   /dev/snd/controlC1:  peci1  2919 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=05314bb8-8590-474c-8af1-1c90dd3bb89c
  InstallationDate: Installed on 2013-11-05 (853 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Latitude E6540
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=501ffea4-2b36-441b-a8ca-34805170c396 ro i8042.nopnp quiet splash 
radeon.modeset=1 radeon.dpm=1 i915.modeset=1 radeon.runpm=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.127.20
  Tags:  trusty
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (695 days ago)
  UserGroups: adm autosshfs cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0CYT5F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0CYT5F:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6540
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

[Martin Pecka]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1547884/+attachment/4592100/+files/CRDA.txt

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

Title:
  Broadcom Corp. BCM5880 Secure Applications Processor eats too much
  power

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $ lsusb
  Bus 004 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor

  $ sudo powertop
  Power est.  Usage   Events/sKategorie   Popis
24.3 W100,0%  Device USB device: 5880 
(Broadcom Corp)

  On my Dell Latitude E6540 I constantly see this USB device eating
  about 20 W of power (and I don't see a reason for this kind of device
  to take that much power). And yes, the fan is always running, even
  when the computer is completely idle.

  The computer has no fingerprint reader (though it was an optional
  accessory, so the chip is IMHO built to support it). I use the
  integrated smartcard reader (also handled by this chip). I've set up
  PAM and LightDM to support smartcard login. However, the power usage
  is the same regardless of whether a smartcard is inserted or not. I do
  not intentionally use the integrated TPM chip in any way.

  I faced this problem also on Ubuntu 14.04.3 with 3.19 kernel.

  Eventually, this could also be a bug in powertop, but the fan almost
  never stops (even with display backlight to minimum), so I think
  powertop could be correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 20 15:33:49 2016
  InstallationDate: Installed on 2013-11-05 (837 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (678 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peci1  2919 F pulseaudio
   /dev/snd/pcmC1D0p:   peci1  2919 F...m pulseaudio
   /dev/snd/controlC1:  peci1  2919 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=05314bb8-8590-474c-8af1-1c90dd3bb89c
  InstallationDate: Installed on 2013-11-05 (853 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Latitude E6540
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=501ffea4-2b36-441b-a8ca-34805170c396 ro i8042.nopnp quiet splash 
radeon.modeset=1 radeon.dpm=1 i915.modeset=1 radeon.runpm=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.127.20
  Tags:  trusty
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (695 days ago)
  UserGroups: adm autosshfs cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0CYT5F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0CYT5F:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6540
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

[Martin Pecka]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1547884/+attachment/4592101/+files/CurrentDmesg.txt

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

Title:
  Broadcom Corp. BCM5880 Secure Applications Processor eats too much
  power

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $ lsusb
  Bus 004 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor

  $ sudo powertop
  Power est.  Usage   Events/sKategorie   Popis
24.3 W100,0%  Device USB device: 5880 
(Broadcom Corp)

  On my Dell Latitude E6540 I constantly see this USB device eating
  about 20 W of power (and I don't see a reason for this kind of device
  to take that much power). And yes, the fan is always running, even
  when the computer is completely idle.

  The computer has no fingerprint reader (though it was an optional
  accessory, so the chip is IMHO built to support it). I use the
  integrated smartcard reader (also handled by this chip). I've set up
  PAM and LightDM to support smartcard login. However, the power usage
  is the same regardless of whether a smartcard is inserted or not. I do
  not intentionally use the integrated TPM chip in any way.

  I faced this problem also on Ubuntu 14.04.3 with 3.19 kernel.

  Eventually, this could also be a bug in powertop, but the fan almost
  never stops (even with display backlight to minimum), so I think
  powertop could be correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 20 15:33:49 2016
  InstallationDate: Installed on 2013-11-05 (837 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (678 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peci1  2919 F pulseaudio
   /dev/snd/pcmC1D0p:   peci1  2919 F...m pulseaudio
   /dev/snd/controlC1:  peci1  2919 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=05314bb8-8590-474c-8af1-1c90dd3bb89c
  InstallationDate: Installed on 2013-11-05 (853 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Latitude E6540
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=501ffea4-2b36-441b-a8ca-34805170c396 ro i8042.nopnp quiet splash 
radeon.modeset=1 radeon.dpm=1 i915.modeset=1 radeon.runpm=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.127.20
  Tags:  trusty
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (695 days ago)
  UserGroups: adm autosshfs cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0CYT5F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0CYT5F:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6540
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1547884/+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 1547884] Re: Broadcom Corp. BCM5880 Secure Applications Processor eats too much power

[Martin Pecka]

apport information

** Tags added: apport-collected

** Description changed:

  $ lsusb
  Bus 004 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor
  
  $ sudo powertop
  Power est.  Usage   Events/sKategorie   Popis
24.3 W100,0%  Device USB device: 5880 
(Broadcom Corp)
  
  On my Dell Latitude E6540 I constantly see this USB device eating about
  20 W of power (and I don't see a reason for this kind of device to take
  that much power). And yes, the fan is always running, even when the
  computer is completely idle.
  
  The computer has no fingerprint reader (though it was an optional
  accessory, so the chip is IMHO built to support it). I use the
  integrated smartcard reader (also handled by this chip). I've set up PAM
  and LightDM to support smartcard login. However, the power usage is the
  same regardless of whether a smartcard is inserted or not. I do not
  intentionally use the integrated TPM chip in any way.
  
  I faced this problem also on Ubuntu 14.04.3 with 3.19 kernel.
  
  Eventually, this could also be a bug in powertop, but the fan almost
  never stops (even with display backlight to minimum), so I think
  powertop could be correct.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-27-generic 4.2.0-27.32~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 20 15:33:49 2016
  InstallationDate: Installed on 2013-11-05 (837 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (678 days ago)
+ --- 
+ ApportVersion: 2.14.1-0ubuntu3.19
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  peci1  2919 F pulseaudio
+  /dev/snd/pcmC1D0p:   peci1  2919 F...m pulseaudio
+  /dev/snd/controlC1:  peci1  2919 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 14.04
+ HibernationDevice: RESUME=UUID=05314bb8-8590-474c-8af1-1c90dd3bb89c
+ InstallationDate: Installed on 2013-11-05 (853 days ago)
+ InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
+ MachineType: Dell Inc. Latitude E6540
+ Package: linux (not installed)
+ ProcFB:
+  0 inteldrmfb
+  1 radeondrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=501ffea4-2b36-441b-a8ca-34805170c396 ro i8042.nopnp quiet splash 
radeon.modeset=1 radeon.dpm=1 i915.modeset=1 radeon.runpm=0 vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
+ RelatedPackageVersions:
+  linux-restricted-modules-4.2.0-30-generic N/A
+  linux-backports-modules-4.2.0-30-generic  N/A
+  linux-firmware1.127.20
+ Tags:  trusty
+ Uname: Linux 4.2.0-30-generic x86_64
+ UpgradeStatus: Upgraded to trusty on 2014-04-12 (695 days ago)
+ UserGroups: adm autosshfs cdrom dip lpadmin plugdev sambashare sudo video
+ _MarkForUpload: True
+ dmi.bios.date: 09/01/2015
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: A16
+ dmi.board.name: 0CYT5F
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 9
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0CYT5F:rvrA00:cvnDellInc.:ct9:cvr:
+ dmi.product.name: Latitude E6540
+ dmi.product.version: 00
+ dmi.sys.vendor: Dell Inc.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1547884/+attachment/4592098/+files/AlsaInfo.txt

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

Title:
  Broadcom Corp. BCM5880 Secure Applications Processor eats too much
  power

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $ lsusb
  Bus 004 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor

  $ sudo powertop
  Power est.  Usage   Events/sKategorie   Popis
24.3 W100,0%  Device USB device: 5880 
(Broadcom Corp)

  On my Dell Latitude E6540 I constantly see this USB device eating
  about 20 W of power (and I don't see a reason for this kind of device
  to take that much power). And yes, the fan is always running, even
  when the computer is completely idle.

  The computer has no fingerprint reader (though it was an optional
  accessory, so the chip is IMHO built to support it). I use the
  integrated smartcard reader (also handled by this chip). I've set up
  PAM and LightDM to support smartcard login. However, the power usage
  is the same regardless of whether a smartcard is inserted or not. I do
  not intentionally use the integrated TPM chip in 

[Kernel-packages] [Bug 1510344] Re: Keyboard Backlight Turns on at boot

[piotrek]

similar with dall precision m4600 ubuntu 14.04, kernel 4.2.0. keyboard
backlight is turned on when power state changing (plug in, unplug, turn
on). it started after i upgrade kernel to version 4.2.0. earlier i was
using kernel 3.x (don't remember the exact version) and there was no
problem with keyboard backlight

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

Title:
  Keyboard Backlight Turns on at boot

Status in Dell Sputnik:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System: Dell XPS 13 9343

  Action: Boot computer

  Expected Behavior: Keyboard backlight would be off when computer is
  booted

  Actual Behavior: Keyboard backlight is on at boot

  This did not happen with Ubuntu 15.04

  There are new files in Ubuntu 15.10 -
  /sys/class/leds/dell::kbd_backlight$

  cat stop_timeout
  60s

   cat start_triggers 
  +keyboard +touchpad

  cat trigger 
  [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full 
BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 
rfkill0

  cat brightness 
  2

  ---

  Unsure if these files are important, but included in the report

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-2-generic 4.1.0-2.2
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2488 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2488 F pulseaudio
  CasperVersion: 1.362
  CurrentDesktop: Unity
  Date: Tue Oct 27 01:29:47 2015
  IwConfig:
   enx00249b0981e3  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-2-generic N/A
   linux-backports-modules-4.1.0-2-generic  N/A
   linux-firmware   1.145
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  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: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+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 1541456] Re: [Ubuntu 16.04] Update qla2xxx driver for POWER (QLogic)

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-11.26

---
linux (4.4.0-11.26) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1553391

  * Xenial update to v4.4.4 stable release (LP: #1553179)
- af_iucv: Validate socket address length in iucv_sock_bind()
- gro: Make GRO aware of lightweight tunnels.
- net: dp83640: Fix tx timestamp overflow handling.
- tunnels: Allow IPv6 UDP checksums to be correctly controlled.
- lwt: fix rx checksum setting for lwt devices tunneling over ipv6
- tcp: fix NULL deref in tcp_v4_send_ack()
- af_unix: fix struct pid memory leak
- pptp: fix illegal memory access caused by multiple bind()s
- sctp: allow setting SCTP_SACK_IMMEDIATELY by the application
- net: dsa: fix mv88e6xxx switches
- tipc: fix connection abort during subscription cancel
- inet: frag: Always orphan skbs inside ip_defrag()
- switchdev: Require RTNL mutex to be held when sending FDB notifications
- tcp: beware of alignments in tcp_get_info()
- ipv6: enforce flowi6_oif usage in ip6_dst_lookup_tail()
- ipv6/udp: use sticky pktinfo egress ifindex on connect()
- ipv6: addrconf: Fix recursive spin lock call
- ipv6: fix a lockdep splat
- unix: correctly track in-flight fds in sending process user_struct
- tcp: do not drop syn_recv on all icmp reports
- net:Add sysctl_max_skb_frags
- tg3: Fix for tg3 transmit queue 0 timed out when too many gso_segs
- enic: increment devcmd2 result ring in case of timeout
- sctp: translate network order to host order when users get a hmacid
- net: Copy inner L3 and L4 headers as unaligned on GRE TEB
- flow_dissector: Fix unaligned access in __skb_flow_dissector when used by
  eth_get_headlen
- bpf: fix branch offset adjustment on backjumps after patching ctx 
expansion
- bonding: Fix ARP monitor validation
- ipv4: fix memory leaks in ip_cmsg_send() callers
- af_unix: Don't set err in unix_stream_read_generic unless there was an 
error
- af_unix: Guard against other == sk in unix_dgram_sendmsg
- tipc: fix premature addition of node to lookup table
- tcp: md5: release request socket instead of listener
- qmi_wwan: add "4G LTE usb-modem U901"
- net/mlx4_en: Count HW buffer overrun only once
- net/mlx4_en: Avoid changing dev->features directly in run-time
- l2tp: Fix error creating L2TP tunnels
- pppoe: fix reference counting in PPPoE proxy
- net_sched fix: reclassification needs to consider ether protocol changes
- route: check and remove route cache when we get route
- tcp/dccp: fix another race at listener dismantle
- IFF_NO_QUEUE: Fix for drivers not calling ether_setup()
- rtnl: RTM_GETNETCONF: fix wrong return value
- tipc: unlock in error path
- unix_diag: fix incorrect sign extension in unix_lookup_by_ino
- sctp: Fix port hash table size computation
- ext4: fix bh->b_state corruption
- ARM: debug-ll: fix BCM63xx entry for multiplatform
- arm64: errata: Add -mpc-relative-literal-loads to build flags
- KVM: s390: fix guest fprs memory leak
- devm_memremap: Fix error value when memremap failed
- drm/gma500: Use correct unref in the gem bo create function
- ARM: 8457/1: psci-smp is built only for SMP
- lib/ucs2_string: Add ucs2 -> utf8 helper functions
- efi: Use ucs2_as_utf8 in efivarfs instead of open coding a bad version
- efi: Do variable name validation tests in utf8
- efi: Make our variable validation list include the guid
- efi: Make efivarfs entries immutable by default
- efi: Add pstore variables to the deletion whitelist
- lib/ucs2_string: Correct ucs2 -> utf8 conversion
- bcache: fix a livelock when we cause a huge number of cache misses
- bcache: Add a cond_resched() call to gc
- bcache: clear BCACHE_DEV_UNLINK_DONE flag when attaching a backing device
- bcache: fix a leak in bch_cached_dev_run()
- bcache: unregister reboot notifier if bcache fails to unregister device
- bcache: allows use of register in udev to avoid "device_busy" error.
- bcache: Change refill_dirty() to always scan entire disk if necessary
- dm thin: fix race condition when destroying thin pool workqueue
- can: ems_usb: Fix possible tx overflow
- usb: dwc3: Fix assignment of EP transfer resources
- USB: cp210x: add IDs for GE B650V3 and B850V3 boards
- USB: option: add support for SIM7100E
- USB: option: add "4G LTE usb-modem U901"
- drivers: android: correct the size of struct binder_uintptr_t for
  BC_DEAD_BINDER_DONE
- spi: omap2-mcspi: Prevent duplicate gpio_request
- iw_cxgb3: Fix incorrectly returning error on success
- drm/i915: shut up gen8+ SDE irq dmesg noise
- ocfs2: unlock inode if deleting inode from orphan fails
- mm: thp: fix SMP race condition between THP page fault and MADV_DONTNEED
- mm: numa: quickly fail allocations for 

[Kernel-packages] [Bug 1552627] Re: mlx4_en didn't choose time-stamping shift value according to HW frequency

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-11.26

---
linux (4.4.0-11.26) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1553391

  * Xenial update to v4.4.4 stable release (LP: #1553179)
- af_iucv: Validate socket address length in iucv_sock_bind()
- gro: Make GRO aware of lightweight tunnels.
- net: dp83640: Fix tx timestamp overflow handling.
- tunnels: Allow IPv6 UDP checksums to be correctly controlled.
- lwt: fix rx checksum setting for lwt devices tunneling over ipv6
- tcp: fix NULL deref in tcp_v4_send_ack()
- af_unix: fix struct pid memory leak
- pptp: fix illegal memory access caused by multiple bind()s
- sctp: allow setting SCTP_SACK_IMMEDIATELY by the application
- net: dsa: fix mv88e6xxx switches
- tipc: fix connection abort during subscription cancel
- inet: frag: Always orphan skbs inside ip_defrag()
- switchdev: Require RTNL mutex to be held when sending FDB notifications
- tcp: beware of alignments in tcp_get_info()
- ipv6: enforce flowi6_oif usage in ip6_dst_lookup_tail()
- ipv6/udp: use sticky pktinfo egress ifindex on connect()
- ipv6: addrconf: Fix recursive spin lock call
- ipv6: fix a lockdep splat
- unix: correctly track in-flight fds in sending process user_struct
- tcp: do not drop syn_recv on all icmp reports
- net:Add sysctl_max_skb_frags
- tg3: Fix for tg3 transmit queue 0 timed out when too many gso_segs
- enic: increment devcmd2 result ring in case of timeout
- sctp: translate network order to host order when users get a hmacid
- net: Copy inner L3 and L4 headers as unaligned on GRE TEB
- flow_dissector: Fix unaligned access in __skb_flow_dissector when used by
  eth_get_headlen
- bpf: fix branch offset adjustment on backjumps after patching ctx 
expansion
- bonding: Fix ARP monitor validation
- ipv4: fix memory leaks in ip_cmsg_send() callers
- af_unix: Don't set err in unix_stream_read_generic unless there was an 
error
- af_unix: Guard against other == sk in unix_dgram_sendmsg
- tipc: fix premature addition of node to lookup table
- tcp: md5: release request socket instead of listener
- qmi_wwan: add "4G LTE usb-modem U901"
- net/mlx4_en: Count HW buffer overrun only once
- net/mlx4_en: Avoid changing dev->features directly in run-time
- l2tp: Fix error creating L2TP tunnels
- pppoe: fix reference counting in PPPoE proxy
- net_sched fix: reclassification needs to consider ether protocol changes
- route: check and remove route cache when we get route
- tcp/dccp: fix another race at listener dismantle
- IFF_NO_QUEUE: Fix for drivers not calling ether_setup()
- rtnl: RTM_GETNETCONF: fix wrong return value
- tipc: unlock in error path
- unix_diag: fix incorrect sign extension in unix_lookup_by_ino
- sctp: Fix port hash table size computation
- ext4: fix bh->b_state corruption
- ARM: debug-ll: fix BCM63xx entry for multiplatform
- arm64: errata: Add -mpc-relative-literal-loads to build flags
- KVM: s390: fix guest fprs memory leak
- devm_memremap: Fix error value when memremap failed
- drm/gma500: Use correct unref in the gem bo create function
- ARM: 8457/1: psci-smp is built only for SMP
- lib/ucs2_string: Add ucs2 -> utf8 helper functions
- efi: Use ucs2_as_utf8 in efivarfs instead of open coding a bad version
- efi: Do variable name validation tests in utf8
- efi: Make our variable validation list include the guid
- efi: Make efivarfs entries immutable by default
- efi: Add pstore variables to the deletion whitelist
- lib/ucs2_string: Correct ucs2 -> utf8 conversion
- bcache: fix a livelock when we cause a huge number of cache misses
- bcache: Add a cond_resched() call to gc
- bcache: clear BCACHE_DEV_UNLINK_DONE flag when attaching a backing device
- bcache: fix a leak in bch_cached_dev_run()
- bcache: unregister reboot notifier if bcache fails to unregister device
- bcache: allows use of register in udev to avoid "device_busy" error.
- bcache: Change refill_dirty() to always scan entire disk if necessary
- dm thin: fix race condition when destroying thin pool workqueue
- can: ems_usb: Fix possible tx overflow
- usb: dwc3: Fix assignment of EP transfer resources
- USB: cp210x: add IDs for GE B650V3 and B850V3 boards
- USB: option: add support for SIM7100E
- USB: option: add "4G LTE usb-modem U901"
- drivers: android: correct the size of struct binder_uintptr_t for
  BC_DEAD_BINDER_DONE
- spi: omap2-mcspi: Prevent duplicate gpio_request
- iw_cxgb3: Fix incorrectly returning error on success
- drm/i915: shut up gen8+ SDE irq dmesg noise
- ocfs2: unlock inode if deleting inode from orphan fails
- mm: thp: fix SMP race condition between THP page fault and MADV_DONTNEED
- mm: numa: quickly fail allocations for 

[Kernel-packages] [Bug 1552314] Re: [s390x] zfcp.ko missing from scsi-modules udeb

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-11.26

---
linux (4.4.0-11.26) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1553391

  * Xenial update to v4.4.4 stable release (LP: #1553179)
- af_iucv: Validate socket address length in iucv_sock_bind()
- gro: Make GRO aware of lightweight tunnels.
- net: dp83640: Fix tx timestamp overflow handling.
- tunnels: Allow IPv6 UDP checksums to be correctly controlled.
- lwt: fix rx checksum setting for lwt devices tunneling over ipv6
- tcp: fix NULL deref in tcp_v4_send_ack()
- af_unix: fix struct pid memory leak
- pptp: fix illegal memory access caused by multiple bind()s
- sctp: allow setting SCTP_SACK_IMMEDIATELY by the application
- net: dsa: fix mv88e6xxx switches
- tipc: fix connection abort during subscription cancel
- inet: frag: Always orphan skbs inside ip_defrag()
- switchdev: Require RTNL mutex to be held when sending FDB notifications
- tcp: beware of alignments in tcp_get_info()
- ipv6: enforce flowi6_oif usage in ip6_dst_lookup_tail()
- ipv6/udp: use sticky pktinfo egress ifindex on connect()
- ipv6: addrconf: Fix recursive spin lock call
- ipv6: fix a lockdep splat
- unix: correctly track in-flight fds in sending process user_struct
- tcp: do not drop syn_recv on all icmp reports
- net:Add sysctl_max_skb_frags
- tg3: Fix for tg3 transmit queue 0 timed out when too many gso_segs
- enic: increment devcmd2 result ring in case of timeout
- sctp: translate network order to host order when users get a hmacid
- net: Copy inner L3 and L4 headers as unaligned on GRE TEB
- flow_dissector: Fix unaligned access in __skb_flow_dissector when used by
  eth_get_headlen
- bpf: fix branch offset adjustment on backjumps after patching ctx 
expansion
- bonding: Fix ARP monitor validation
- ipv4: fix memory leaks in ip_cmsg_send() callers
- af_unix: Don't set err in unix_stream_read_generic unless there was an 
error
- af_unix: Guard against other == sk in unix_dgram_sendmsg
- tipc: fix premature addition of node to lookup table
- tcp: md5: release request socket instead of listener
- qmi_wwan: add "4G LTE usb-modem U901"
- net/mlx4_en: Count HW buffer overrun only once
- net/mlx4_en: Avoid changing dev->features directly in run-time
- l2tp: Fix error creating L2TP tunnels
- pppoe: fix reference counting in PPPoE proxy
- net_sched fix: reclassification needs to consider ether protocol changes
- route: check and remove route cache when we get route
- tcp/dccp: fix another race at listener dismantle
- IFF_NO_QUEUE: Fix for drivers not calling ether_setup()
- rtnl: RTM_GETNETCONF: fix wrong return value
- tipc: unlock in error path
- unix_diag: fix incorrect sign extension in unix_lookup_by_ino
- sctp: Fix port hash table size computation
- ext4: fix bh->b_state corruption
- ARM: debug-ll: fix BCM63xx entry for multiplatform
- arm64: errata: Add -mpc-relative-literal-loads to build flags
- KVM: s390: fix guest fprs memory leak
- devm_memremap: Fix error value when memremap failed
- drm/gma500: Use correct unref in the gem bo create function
- ARM: 8457/1: psci-smp is built only for SMP
- lib/ucs2_string: Add ucs2 -> utf8 helper functions
- efi: Use ucs2_as_utf8 in efivarfs instead of open coding a bad version
- efi: Do variable name validation tests in utf8
- efi: Make our variable validation list include the guid
- efi: Make efivarfs entries immutable by default
- efi: Add pstore variables to the deletion whitelist
- lib/ucs2_string: Correct ucs2 -> utf8 conversion
- bcache: fix a livelock when we cause a huge number of cache misses
- bcache: Add a cond_resched() call to gc
- bcache: clear BCACHE_DEV_UNLINK_DONE flag when attaching a backing device
- bcache: fix a leak in bch_cached_dev_run()
- bcache: unregister reboot notifier if bcache fails to unregister device
- bcache: allows use of register in udev to avoid "device_busy" error.
- bcache: Change refill_dirty() to always scan entire disk if necessary
- dm thin: fix race condition when destroying thin pool workqueue
- can: ems_usb: Fix possible tx overflow
- usb: dwc3: Fix assignment of EP transfer resources
- USB: cp210x: add IDs for GE B650V3 and B850V3 boards
- USB: option: add support for SIM7100E
- USB: option: add "4G LTE usb-modem U901"
- drivers: android: correct the size of struct binder_uintptr_t for
  BC_DEAD_BINDER_DONE
- spi: omap2-mcspi: Prevent duplicate gpio_request
- iw_cxgb3: Fix incorrectly returning error on success
- drm/i915: shut up gen8+ SDE irq dmesg noise
- ocfs2: unlock inode if deleting inode from orphan fails
- mm: thp: fix SMP race condition between THP page fault and MADV_DONTNEED
- mm: numa: quickly fail allocations for 

[Kernel-packages] [Bug 1553179] Re: Xenial update to v4.4.4 stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-11.26

---
linux (4.4.0-11.26) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1553391

  * Xenial update to v4.4.4 stable release (LP: #1553179)
- af_iucv: Validate socket address length in iucv_sock_bind()
- gro: Make GRO aware of lightweight tunnels.
- net: dp83640: Fix tx timestamp overflow handling.
- tunnels: Allow IPv6 UDP checksums to be correctly controlled.
- lwt: fix rx checksum setting for lwt devices tunneling over ipv6
- tcp: fix NULL deref in tcp_v4_send_ack()
- af_unix: fix struct pid memory leak
- pptp: fix illegal memory access caused by multiple bind()s
- sctp: allow setting SCTP_SACK_IMMEDIATELY by the application
- net: dsa: fix mv88e6xxx switches
- tipc: fix connection abort during subscription cancel
- inet: frag: Always orphan skbs inside ip_defrag()
- switchdev: Require RTNL mutex to be held when sending FDB notifications
- tcp: beware of alignments in tcp_get_info()
- ipv6: enforce flowi6_oif usage in ip6_dst_lookup_tail()
- ipv6/udp: use sticky pktinfo egress ifindex on connect()
- ipv6: addrconf: Fix recursive spin lock call
- ipv6: fix a lockdep splat
- unix: correctly track in-flight fds in sending process user_struct
- tcp: do not drop syn_recv on all icmp reports
- net:Add sysctl_max_skb_frags
- tg3: Fix for tg3 transmit queue 0 timed out when too many gso_segs
- enic: increment devcmd2 result ring in case of timeout
- sctp: translate network order to host order when users get a hmacid
- net: Copy inner L3 and L4 headers as unaligned on GRE TEB
- flow_dissector: Fix unaligned access in __skb_flow_dissector when used by
  eth_get_headlen
- bpf: fix branch offset adjustment on backjumps after patching ctx 
expansion
- bonding: Fix ARP monitor validation
- ipv4: fix memory leaks in ip_cmsg_send() callers
- af_unix: Don't set err in unix_stream_read_generic unless there was an 
error
- af_unix: Guard against other == sk in unix_dgram_sendmsg
- tipc: fix premature addition of node to lookup table
- tcp: md5: release request socket instead of listener
- qmi_wwan: add "4G LTE usb-modem U901"
- net/mlx4_en: Count HW buffer overrun only once
- net/mlx4_en: Avoid changing dev->features directly in run-time
- l2tp: Fix error creating L2TP tunnels
- pppoe: fix reference counting in PPPoE proxy
- net_sched fix: reclassification needs to consider ether protocol changes
- route: check and remove route cache when we get route
- tcp/dccp: fix another race at listener dismantle
- IFF_NO_QUEUE: Fix for drivers not calling ether_setup()
- rtnl: RTM_GETNETCONF: fix wrong return value
- tipc: unlock in error path
- unix_diag: fix incorrect sign extension in unix_lookup_by_ino
- sctp: Fix port hash table size computation
- ext4: fix bh->b_state corruption
- ARM: debug-ll: fix BCM63xx entry for multiplatform
- arm64: errata: Add -mpc-relative-literal-loads to build flags
- KVM: s390: fix guest fprs memory leak
- devm_memremap: Fix error value when memremap failed
- drm/gma500: Use correct unref in the gem bo create function
- ARM: 8457/1: psci-smp is built only for SMP
- lib/ucs2_string: Add ucs2 -> utf8 helper functions
- efi: Use ucs2_as_utf8 in efivarfs instead of open coding a bad version
- efi: Do variable name validation tests in utf8
- efi: Make our variable validation list include the guid
- efi: Make efivarfs entries immutable by default
- efi: Add pstore variables to the deletion whitelist
- lib/ucs2_string: Correct ucs2 -> utf8 conversion
- bcache: fix a livelock when we cause a huge number of cache misses
- bcache: Add a cond_resched() call to gc
- bcache: clear BCACHE_DEV_UNLINK_DONE flag when attaching a backing device
- bcache: fix a leak in bch_cached_dev_run()
- bcache: unregister reboot notifier if bcache fails to unregister device
- bcache: allows use of register in udev to avoid "device_busy" error.
- bcache: Change refill_dirty() to always scan entire disk if necessary
- dm thin: fix race condition when destroying thin pool workqueue
- can: ems_usb: Fix possible tx overflow
- usb: dwc3: Fix assignment of EP transfer resources
- USB: cp210x: add IDs for GE B650V3 and B850V3 boards
- USB: option: add support for SIM7100E
- USB: option: add "4G LTE usb-modem U901"
- drivers: android: correct the size of struct binder_uintptr_t for
  BC_DEAD_BINDER_DONE
- spi: omap2-mcspi: Prevent duplicate gpio_request
- iw_cxgb3: Fix incorrectly returning error on success
- drm/i915: shut up gen8+ SDE irq dmesg noise
- ocfs2: unlock inode if deleting inode from orphan fails
- mm: thp: fix SMP race condition between THP page fault and MADV_DONTNEED
- mm: numa: quickly fail allocations for 

[Kernel-packages] [Bug 1552332] Re: [Ubuntu 16.04] Help to flush kernel panics to console

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-11.26

---
linux (4.4.0-11.26) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1553391

  * Xenial update to v4.4.4 stable release (LP: #1553179)
- af_iucv: Validate socket address length in iucv_sock_bind()
- gro: Make GRO aware of lightweight tunnels.
- net: dp83640: Fix tx timestamp overflow handling.
- tunnels: Allow IPv6 UDP checksums to be correctly controlled.
- lwt: fix rx checksum setting for lwt devices tunneling over ipv6
- tcp: fix NULL deref in tcp_v4_send_ack()
- af_unix: fix struct pid memory leak
- pptp: fix illegal memory access caused by multiple bind()s
- sctp: allow setting SCTP_SACK_IMMEDIATELY by the application
- net: dsa: fix mv88e6xxx switches
- tipc: fix connection abort during subscription cancel
- inet: frag: Always orphan skbs inside ip_defrag()
- switchdev: Require RTNL mutex to be held when sending FDB notifications
- tcp: beware of alignments in tcp_get_info()
- ipv6: enforce flowi6_oif usage in ip6_dst_lookup_tail()
- ipv6/udp: use sticky pktinfo egress ifindex on connect()
- ipv6: addrconf: Fix recursive spin lock call
- ipv6: fix a lockdep splat
- unix: correctly track in-flight fds in sending process user_struct
- tcp: do not drop syn_recv on all icmp reports
- net:Add sysctl_max_skb_frags
- tg3: Fix for tg3 transmit queue 0 timed out when too many gso_segs
- enic: increment devcmd2 result ring in case of timeout
- sctp: translate network order to host order when users get a hmacid
- net: Copy inner L3 and L4 headers as unaligned on GRE TEB
- flow_dissector: Fix unaligned access in __skb_flow_dissector when used by
  eth_get_headlen
- bpf: fix branch offset adjustment on backjumps after patching ctx 
expansion
- bonding: Fix ARP monitor validation
- ipv4: fix memory leaks in ip_cmsg_send() callers
- af_unix: Don't set err in unix_stream_read_generic unless there was an 
error
- af_unix: Guard against other == sk in unix_dgram_sendmsg
- tipc: fix premature addition of node to lookup table
- tcp: md5: release request socket instead of listener
- qmi_wwan: add "4G LTE usb-modem U901"
- net/mlx4_en: Count HW buffer overrun only once
- net/mlx4_en: Avoid changing dev->features directly in run-time
- l2tp: Fix error creating L2TP tunnels
- pppoe: fix reference counting in PPPoE proxy
- net_sched fix: reclassification needs to consider ether protocol changes
- route: check and remove route cache when we get route
- tcp/dccp: fix another race at listener dismantle
- IFF_NO_QUEUE: Fix for drivers not calling ether_setup()
- rtnl: RTM_GETNETCONF: fix wrong return value
- tipc: unlock in error path
- unix_diag: fix incorrect sign extension in unix_lookup_by_ino
- sctp: Fix port hash table size computation
- ext4: fix bh->b_state corruption
- ARM: debug-ll: fix BCM63xx entry for multiplatform
- arm64: errata: Add -mpc-relative-literal-loads to build flags
- KVM: s390: fix guest fprs memory leak
- devm_memremap: Fix error value when memremap failed
- drm/gma500: Use correct unref in the gem bo create function
- ARM: 8457/1: psci-smp is built only for SMP
- lib/ucs2_string: Add ucs2 -> utf8 helper functions
- efi: Use ucs2_as_utf8 in efivarfs instead of open coding a bad version
- efi: Do variable name validation tests in utf8
- efi: Make our variable validation list include the guid
- efi: Make efivarfs entries immutable by default
- efi: Add pstore variables to the deletion whitelist
- lib/ucs2_string: Correct ucs2 -> utf8 conversion
- bcache: fix a livelock when we cause a huge number of cache misses
- bcache: Add a cond_resched() call to gc
- bcache: clear BCACHE_DEV_UNLINK_DONE flag when attaching a backing device
- bcache: fix a leak in bch_cached_dev_run()
- bcache: unregister reboot notifier if bcache fails to unregister device
- bcache: allows use of register in udev to avoid "device_busy" error.
- bcache: Change refill_dirty() to always scan entire disk if necessary
- dm thin: fix race condition when destroying thin pool workqueue
- can: ems_usb: Fix possible tx overflow
- usb: dwc3: Fix assignment of EP transfer resources
- USB: cp210x: add IDs for GE B650V3 and B850V3 boards
- USB: option: add support for SIM7100E
- USB: option: add "4G LTE usb-modem U901"
- drivers: android: correct the size of struct binder_uintptr_t for
  BC_DEAD_BINDER_DONE
- spi: omap2-mcspi: Prevent duplicate gpio_request
- iw_cxgb3: Fix incorrectly returning error on success
- drm/i915: shut up gen8+ SDE irq dmesg noise
- ocfs2: unlock inode if deleting inode from orphan fails
- mm: thp: fix SMP race condition between THP page fault and MADV_DONTNEED
- mm: numa: quickly fail allocations for 

[Kernel-packages] [Bug 1553391] Re: linux: 4.4.0-11.26 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-11.26

---
linux (4.4.0-11.26) xenial; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1553391

  * Xenial update to v4.4.4 stable release (LP: #1553179)
- af_iucv: Validate socket address length in iucv_sock_bind()
- gro: Make GRO aware of lightweight tunnels.
- net: dp83640: Fix tx timestamp overflow handling.
- tunnels: Allow IPv6 UDP checksums to be correctly controlled.
- lwt: fix rx checksum setting for lwt devices tunneling over ipv6
- tcp: fix NULL deref in tcp_v4_send_ack()
- af_unix: fix struct pid memory leak
- pptp: fix illegal memory access caused by multiple bind()s
- sctp: allow setting SCTP_SACK_IMMEDIATELY by the application
- net: dsa: fix mv88e6xxx switches
- tipc: fix connection abort during subscription cancel
- inet: frag: Always orphan skbs inside ip_defrag()
- switchdev: Require RTNL mutex to be held when sending FDB notifications
- tcp: beware of alignments in tcp_get_info()
- ipv6: enforce flowi6_oif usage in ip6_dst_lookup_tail()
- ipv6/udp: use sticky pktinfo egress ifindex on connect()
- ipv6: addrconf: Fix recursive spin lock call
- ipv6: fix a lockdep splat
- unix: correctly track in-flight fds in sending process user_struct
- tcp: do not drop syn_recv on all icmp reports
- net:Add sysctl_max_skb_frags
- tg3: Fix for tg3 transmit queue 0 timed out when too many gso_segs
- enic: increment devcmd2 result ring in case of timeout
- sctp: translate network order to host order when users get a hmacid
- net: Copy inner L3 and L4 headers as unaligned on GRE TEB
- flow_dissector: Fix unaligned access in __skb_flow_dissector when used by
  eth_get_headlen
- bpf: fix branch offset adjustment on backjumps after patching ctx 
expansion
- bonding: Fix ARP monitor validation
- ipv4: fix memory leaks in ip_cmsg_send() callers
- af_unix: Don't set err in unix_stream_read_generic unless there was an 
error
- af_unix: Guard against other == sk in unix_dgram_sendmsg
- tipc: fix premature addition of node to lookup table
- tcp: md5: release request socket instead of listener
- qmi_wwan: add "4G LTE usb-modem U901"
- net/mlx4_en: Count HW buffer overrun only once
- net/mlx4_en: Avoid changing dev->features directly in run-time
- l2tp: Fix error creating L2TP tunnels
- pppoe: fix reference counting in PPPoE proxy
- net_sched fix: reclassification needs to consider ether protocol changes
- route: check and remove route cache when we get route
- tcp/dccp: fix another race at listener dismantle
- IFF_NO_QUEUE: Fix for drivers not calling ether_setup()
- rtnl: RTM_GETNETCONF: fix wrong return value
- tipc: unlock in error path
- unix_diag: fix incorrect sign extension in unix_lookup_by_ino
- sctp: Fix port hash table size computation
- ext4: fix bh->b_state corruption
- ARM: debug-ll: fix BCM63xx entry for multiplatform
- arm64: errata: Add -mpc-relative-literal-loads to build flags
- KVM: s390: fix guest fprs memory leak
- devm_memremap: Fix error value when memremap failed
- drm/gma500: Use correct unref in the gem bo create function
- ARM: 8457/1: psci-smp is built only for SMP
- lib/ucs2_string: Add ucs2 -> utf8 helper functions
- efi: Use ucs2_as_utf8 in efivarfs instead of open coding a bad version
- efi: Do variable name validation tests in utf8
- efi: Make our variable validation list include the guid
- efi: Make efivarfs entries immutable by default
- efi: Add pstore variables to the deletion whitelist
- lib/ucs2_string: Correct ucs2 -> utf8 conversion
- bcache: fix a livelock when we cause a huge number of cache misses
- bcache: Add a cond_resched() call to gc
- bcache: clear BCACHE_DEV_UNLINK_DONE flag when attaching a backing device
- bcache: fix a leak in bch_cached_dev_run()
- bcache: unregister reboot notifier if bcache fails to unregister device
- bcache: allows use of register in udev to avoid "device_busy" error.
- bcache: Change refill_dirty() to always scan entire disk if necessary
- dm thin: fix race condition when destroying thin pool workqueue
- can: ems_usb: Fix possible tx overflow
- usb: dwc3: Fix assignment of EP transfer resources
- USB: cp210x: add IDs for GE B650V3 and B850V3 boards
- USB: option: add support for SIM7100E
- USB: option: add "4G LTE usb-modem U901"
- drivers: android: correct the size of struct binder_uintptr_t for
  BC_DEAD_BINDER_DONE
- spi: omap2-mcspi: Prevent duplicate gpio_request
- iw_cxgb3: Fix incorrectly returning error on success
- drm/i915: shut up gen8+ SDE irq dmesg noise
- ocfs2: unlock inode if deleting inode from orphan fails
- mm: thp: fix SMP race condition between THP page fault and MADV_DONTNEED
- mm: numa: quickly fail allocations for 

[Kernel-packages] [Bug 1554279] 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/1554279

Title:
  Times advances twice as fast with refined-jiffies

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When the clocksource is set to "refined-jiffies" it ticks twice as
  fast. This is not an issue when it is changed to "tsc".

  The problem existed in earlier kernels too.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-76-generic 3.13.0-76.120
  ProcVersionSignature: Ubuntu 3.13.0-76.120-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-76-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 24 12:48 seq
   crw-rw 1 root audio 116, 33 Feb 24 12:48 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.19
  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:
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Tue Mar  8 00:47:45 2016
  HibernationDevice: RESUME=UUID=96b67b5e-eb31-44ac-881d-56edc3d7910d
  InstallationDate: Installed on 2014-05-16 (661 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  MachineType: Dell Inc. PowerEdge R720
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-76-generic.efi.signed 
root=UUID=9740a566-6efd-4b42-a82e-26e3cf6a76aa ro acpi=off nomdmonddf nomdmonisw
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-76-generic N/A
   linux-backports-modules-3.13.0-76-generic  N/A
   linux-firmware 1.127.20
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.2
  dmi.board.name: 0X3D66
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.2:bd01/16/2014:svnDellInc.:pnPowerEdgeR720:pvr:rvnDellInc.:rn0X3D66:rvrA01:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R720
  dmi.sys.vendor: Dell Inc.

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

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

Re: [Kernel-packages] [Bug 1535147] Re: Kernel Panic error message using kernel 3.19.0-43-generic

[Jonathan Rogiest]

Thanks Christopher. Issue has been resolved with new kernel update.

On 06/03/16 15:40, Christopher M. Penalver wrote:
> Jonathan Rogiest, thank you for taking the time to report this bug and 
> helping to make Ubuntu better. Please execute the following command only 
> once, as it will automatically gather debugging information, in a terminal:
> apport-collect 1535147
>
> ** Package changed: linux-lts-vivid (Ubuntu) => linux (Ubuntu)
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>

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

Title:
  Kernel Panic error message using  kernel 3.19.0-43-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After auto update to kernel 3.19.0-43-generic when rebooting computer
  computer gives terminal error "end Kernel panic - not syncing: VFS:
  Unable to mount root fs on unknown-block(0.0)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-42-generic 3.19.0-42.48~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-42.48~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-42-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan 17 17:12:34 2016
  InstallationDate: Installed on 2015-11-26 (52 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535147/+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 1554279] [NEW] Times advances twice as fast with refined-jiffies

[Nicholas Westlake]

Public bug reported:

When the clocksource is set to "refined-jiffies" it ticks twice as fast.
This is not an issue when it is changed to "tsc".

The problem existed in earlier kernels too.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-76-generic 3.13.0-76.120
ProcVersionSignature: Ubuntu 3.13.0-76.120-generic 3.13.11-ckt30
Uname: Linux 3.13.0-76-generic x86_64
NonfreeKernelModules: nvidia
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Feb 24 12:48 seq
 crw-rw 1 root audio 116, 33 Feb 24 12:48 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.1-0ubuntu3.19
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:
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Tue Mar  8 00:47:45 2016
HibernationDevice: RESUME=UUID=96b67b5e-eb31-44ac-881d-56edc3d7910d
InstallationDate: Installed on 2014-05-16 (661 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
MachineType: Dell Inc. PowerEdge R720
PciMultimedia:
 
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-76-generic.efi.signed 
root=UUID=9740a566-6efd-4b42-a82e-26e3cf6a76aa ro acpi=off nomdmonddf nomdmonisw
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-76-generic N/A
 linux-backports-modules-3.13.0-76-generic  N/A
 linux-firmware 1.127.20
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/16/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.2.2
dmi.board.name: 0X3D66
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.2:bd01/16/2014:svnDellInc.:pnPowerEdgeR720:pvr:rvnDellInc.:rn0X3D66:rvrA01:cvnDellInc.:ct23:cvr:
dmi.product.name: PowerEdge R720
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug trusty

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

Title:
  Times advances twice as fast with refined-jiffies

Status in linux package in Ubuntu:
  New

Bug description:
  When the clocksource is set to "refined-jiffies" it ticks twice as
  fast. This is not an issue when it is changed to "tsc".

  The problem existed in earlier kernels too.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-76-generic 3.13.0-76.120
  ProcVersionSignature: Ubuntu 3.13.0-76.120-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-76-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 24 12:48 seq
   crw-rw 1 root audio 116, 33 Feb 24 12:48 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.19
  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:
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Tue Mar  8 00:47:45 2016
  HibernationDevice: RESUME=UUID=96b67b5e-eb31-44ac-881d-56edc3d7910d
  InstallationDate: Installed on 2014-05-16 (661 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  MachineType: Dell Inc. PowerEdge R720
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-76-generic.efi.signed 
root=UUID=9740a566-6efd-4b42-a82e-26e3cf6a76aa ro acpi=off nomdmonddf nomdmonisw
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-76-generic N/A
   linux-backports-modules-3.13.0-76-generic  N/A
   linux-firmware 1.127.20
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.2
  dmi.board.name: 0X3D66
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
 

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

[bugproxy]

--- Comment From ye...@us.ibm.com 2016-03-07 19:07 EDT---
(In reply to comment #35)
> Provided 3.19.0-50-generic linux kernel image is not bootable  in my
> machine, as it does not have the ipr module in initramfs, hence failing to
> find the root disk.
>
..
...
>
> Regards,
> -Satheesh.

I hit similar problem when I installed 3.19.0-51-generic, but this
problem can be fixed by installing the extra package:" linux-image-
extra-3.19.0-51-generic"

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

Title:
  [LTCTest][Kernel][OP810]Ubuntu14.04.3: kernel call trace while
  continuously switching between smt on/off and changing subcores

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

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2015-07-14 
02:32:22 ==
  While running the below script, and nothing else was running in the system, 
host got the kernel call traces after around 15~20 mins

  #!/bin/bash -x
  while true;
  do for i in 1 2 4;
  do ppc64_cpu  --subcores-per-core=$i;
  ppc64_cpu --info
  ppc64_cpu --smt=off;
  ppc64_cpu --info
  sleep 1;
  lscpu
  ppc64_cpu --smt=on;
  ppc64_cpu --info
  sleep 1;
  lscpu
  done;
  sleep 1;
  done

  
  Environment:
  --
  $ cat /etc/issue
  Ubuntu 14.04.2 LTS \n \l

  $ uname -a
  Linux tul8fp 3.19.0-22-generic #22~14.04.1-Ubuntu SMP Wed Jun 17 10:03:39 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux

  $ lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):160
  On-line CPU(s) list:   
0,4,8,12,16,20,24,28,32,36,40,44,48,52,56,60,64,68,72,76,80,84,88,92,96,100,104,108,112,116,120,124,128,132,136,138-159
  Off-line CPU(s) list:  
1-3,5-7,9-11,13-15,17-19,21-23,25-27,29-31,33-35,37-39,41-43,45-47,49-51,53-55,57-59,61-63,65-67,69-71,73-75,77-79,81-83,85-87,89-91,93-95,97-99,101-103,105-107,109-111,113-115,117-119,121-123,125-127,129-131,133-135,137
  Thread(s) per core:2
  Core(s) per socket:10
  Socket(s): 2
  NUMA node(s):  2
  Model: 8335-GTA
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 
0,4,88,92,96,100,104,108,112,116,120,124,128,132,136,138-159
  NUMA node8 CPU(s): 
8,12,16,20,24,28,32,36,40,44,48,52,56,60,64,68,72,76,80,84

  $ tail -10 /proc/cpuinfo 
  processor : 159
  cpu   : POWER8 (raw), altivec supported
  clock : 2693.00MHz
  revision  : 2.0 (pvr 004d 0200)

  timebase  : 51200
  platform  : PowerNV
  model : 8335-GTA
  machine   : PowerNV 8335-GTA
  firmware  : OPAL v3

  Logs:-
  -

  
  # dmesg
  [79081.074088] INFO: task irqbalance:1897 blocked for more than 120 seconds.
  [79081.074333]   Not tainted 3.19.0-22-generic #22~14.04.1-Ubuntu
  [79081.074388] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [79081.074449] irqbalance  D 3fff9ac39d3c 0  1897  1 
0x0004
  [79081.074454] Call Trace:
  [79081.074470] [c007e8d035f0] [3fff9af5] 0x3fff9af5 
(unreliable)
  [79081.074477] [c007e8d037c0] [c0015934] __switch_to+0x204/0x350
  [79081.074482] [c007e8d03820] [c0a11508] __schedule+0x368/0x8d0
  [79081.074486] --- interrupt: 1000ba30 at 0xc007e8d039f0
  [79081.074486] LR = 0x10026a6c1d0
  [79081.074490] [c007e8d03a40] [c0a120a0] 
schedule_preempt_disabled+0x20/0x30 (unreliable)
  [79081.074494] [c007e8d03a60] [c0a1420c] 
__mutex_lock_slowpath+0xfc/0x1f0
  [79081.074497] [c007e8d03ae0] [c0a1436c] mutex_lock+0x6c/0x70
  [79081.074501] [c007e8d03b10] [c064488c] online_show+0x3c/0x90
  [79081.074503] [c007e8d03b90] [c0644fec] dev_attr_show+0x5c/0xc0
  [79081.074508] [c007e8d03bd0] [c035b7f4] 
sysfs_kf_seq_show+0x114/0x200
  [79081.074511] [c007e8d03c20] [c03591e4] kernfs_seq_show+0x54/0x70
  [79081.074515] [c007e8d03c50] [c02e74fc] seq_read+0xec/0x500
  [79081.074519] [c007e8d03cf0] [c035a474] 
kernfs_fop_read+0x184/0x220
  [79081.074523] [c007e8d03d50] [c02b520c] __vfs_read+0x6c/0x120
  [79081.074527] [c007e8d03d90] [c02b5364] vfs_read+0xa4/0x1c0
  [79081.074530] [c007e8d03de0] [c02b54ec] SyS_read+0x6c/0x110
  [79081.074534] [c007e8d03e30] [c0009258] system_call+0x38/0xd0
  [79081.074546] INFO: task ppc64_cpu:111047 blocked for more than 120 seconds.
  [79081.074597]   Not tainted 3.19.0-22-generic #22~14.04.1-Ubuntu
  [79081.074802] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 

[Kernel-packages] [Bug 1552668] Re: BUG: unable to handle kernel paging request at 00007f4cd3dac000

[Le Gluon Du Net]

Ubuntu xenial crashed when I unplugged my USB 3 key.

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

Title:
  BUG: unable to handle kernel paging request at 7f4cd3dac000

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No idea what happened.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-9-generic 4.4.0-9.24
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniel 2422 F pulseaudio
  Date: Thu Mar  3 12:32:55 2016
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: 0010:location  location anon_vma_clone+0x99/0x200
  Failure: oops
  HibernationDevice: RESUME=UUID=9bc14055-971b-4ccc-a5b7-f42c3d313c8c
  InstallationDate: Installed on 2015-04-30 (307 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 429149G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9-generic 
root=UUID=457973fc-512e-4b6a-b65b-85f15fa85b7b ro console=tty1 console=ttyS0 
panic=-1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu9
  SourcePackage: linux
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  Title: BUG: unable to handle kernel paging request at 7f4cd3dac000
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET46WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 429149G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 429149G
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552668/+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 1554263] [NEW] CVE-2012-6701

[Steve Beattie]

*** This bug is a security vulnerability ***

Public security bug reported:

vfs: make AIO use the proper rw_verify_area() area helpers

Break-Fix: - a70b52ec1aaeaf60f4739edb1b422827cb6f3893

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

** Affects: linux-armadaxp (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-flo (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-goldfish (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-lts-quantal (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-utopic (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-mako (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-manta (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-raspi2 (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux (Ubuntu Precise)
 Importance: Medium
 Status: Fix Committed

** Affects: linux-armadaxp (Ubuntu Precise)
 Importance: Medium
 Status: Fix Released

** Affects: linux-flo (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-quantal (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-utopic (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-mako (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-manta (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Precise)
 Importance: Medium
 Status: Fix Committed

** Affects: linux (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-armadaxp (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-flo (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-quantal (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-utopic (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu Trusty)
 Importance: Medium
 Status: Fix Committed

** Affects: linux-mako (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-manta (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-armadaxp (Ubuntu Vivid)
 Importance: Undecided
 Status: New

** Affects: linux-flo (Ubuntu Vivid)
 Importance: Undecided
 Status: New

** Affects: linux-goldfish (Ubuntu Vivid)
 Importance: Undecided
 Status: New

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

** Affects: 

[Kernel-packages] [Bug 1554262] Re: CVE-2016-2854

[Steve Beattie]

CVE-2016-2854

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

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

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

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

** Also affects: linux-ti-omap4 (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

** Also affects: linux-ti-omap4 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

** Changed in: linux-lts-trusty (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Precise)
   Status: New => Invalid

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

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

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

** Changed in: linux-raspi2 (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-mako (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-goldfish (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-flo (Ubuntu Precise)
   Status: New => Invalid

** Description changed:

- Placeholder
+ [AUFS Xattr Setgid Privilege Escalation]

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: linux-lts-trusty (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-trusty (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Precise)
   

[Kernel-packages] [Bug 1554263] Re: CVE-2012-6701

[Steve Beattie]

CVE-2012-6701

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

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

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

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

** Also affects: linux-ti-omap4 (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

** Also affects: linux-ti-omap4 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Trusty)
   Status: New => Invalid

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

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

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

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

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

** Changed in: linux-ti-omap4 (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Precise)
   Status: New => Fix Released

** Changed in: linux-armadaxp (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Trusty)
   Status: New => Fix Committed

** Changed in: linux-lts-saucy (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Precise)
   Status: New => Invalid

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

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

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

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

** Changed in: linux-raspi2 (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-mako (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: 

[Kernel-packages] [Bug 1554262] [NEW] CVE-2016-2854

[Steve Beattie]

*** This bug is a security vulnerability ***

Public security bug reported:

[AUFS Xattr Setgid Privilege Escalation]

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

** Affects: linux-armadaxp (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-flo (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-goldfish (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-lts-quantal (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-utopic (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-mako (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-manta (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-raspi2 (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-ti-omap4 (Ubuntu)
 Importance: Low
 Status: Invalid

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

** Affects: linux-armadaxp (Ubuntu Precise)
 Importance: Low
 Status: New

** Affects: linux-flo (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-quantal (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu Precise)
 Importance: Low
 Status: New

** Affects: linux-lts-utopic (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-mako (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-manta (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Precise)
 Importance: Low
 Status: New

** Affects: linux (Ubuntu Trusty)
 Importance: Low
 Status: New

** Affects: linux-armadaxp (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-flo (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-quantal (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-utopic (Ubuntu Trusty)
 Importance: Low
 Status: New

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

** Affects: linux-lts-wily (Ubuntu Trusty)
 Importance: Low
 Status: New

** Affects: linux-lts-xenial (Ubuntu Trusty)
 Importance: Low
 Status: New

** Affects: linux-mako (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-manta (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

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

** Affects: linux-armadaxp (Ubuntu Vivid)
 Importance: Undecided
 Status: New

** Affects: linux-flo (Ubuntu Vivid)
 Importance: Undecided
 Status: New

** Affects: linux-goldfish (Ubuntu Vivid)
 Importance: Undecided
 Status: New

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

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

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

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

** Affects: 

[Kernel-packages] [Bug 1547400] Re: aufs fails to handle sanitize xattrs in workdir, copies SUID binaries from no-suid fuse mounts

[Steve Beattie]

** Tags added: kernel-cve-skip-description

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Also affects: linux-lts-quantal (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-saucy (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

** Also affects: linux-lts-trusty (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-vivid (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

** Also affects: linux-lts-xenial (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Xenial)
   Importance: Medium
   Status: Confirmed

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

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

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

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

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

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

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

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

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

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: linux-lts-trusty (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-trusty (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Precise)
   Importance: 

[Kernel-packages] [Bug 1554260] Re: CVE-2016-2847

[Steve Beattie]

CVE-2016-2847

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

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

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

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

** Also affects: linux-ti-omap4 (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

** Also affects: linux-ti-omap4 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

** Changed in: linux-lts-trusty (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Precise)
   Status: New => Invalid

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

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

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

** Changed in: linux-raspi2 (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-mako (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-goldfish (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-flo (Ubuntu Precise)
   Status: New => Invalid

** Description changed:

- Placeholder
+ pipe: limit the per-user amount of pages allocated in pipes
+ 
+ Break-Fix: - 759c01142a5d0f364a462346168a56de28a80f52

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: linux-lts-trusty (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-trusty (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: 

[Kernel-packages] [Bug 1554260] [NEW] CVE-2016-2847

[Steve Beattie]

*** This bug is a security vulnerability ***

Public security bug reported:

pipe: limit the per-user amount of pages allocated in pipes

Break-Fix: - 759c01142a5d0f364a462346168a56de28a80f52

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

** Affects: linux-armadaxp (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-flo (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-goldfish (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-lts-quantal (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-utopic (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-mako (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-manta (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-raspi2 (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-ti-omap4 (Ubuntu)
 Importance: Low
 Status: Invalid

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

** Affects: linux-armadaxp (Ubuntu Precise)
 Importance: Low
 Status: New

** Affects: linux-flo (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-quantal (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu Precise)
 Importance: Low
 Status: New

** Affects: linux-lts-utopic (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-mako (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-manta (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Precise)
 Importance: Low
 Status: New

** Affects: linux (Ubuntu Trusty)
 Importance: Low
 Status: New

** Affects: linux-armadaxp (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-flo (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-quantal (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-utopic (Ubuntu Trusty)
 Importance: Low
 Status: New

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

** Affects: linux-lts-wily (Ubuntu Trusty)
 Importance: Low
 Status: New

** Affects: linux-lts-xenial (Ubuntu Trusty)
 Importance: Low
 Status: New

** Affects: linux-mako (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-manta (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

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

** Affects: linux-armadaxp (Ubuntu Vivid)
 Importance: Undecided
 Status: New

** Affects: linux-flo (Ubuntu Vivid)
 Importance: Undecided
 Status: New

** Affects: linux-goldfish (Ubuntu Vivid)
 Importance: Undecided
 Status: New

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

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

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

** Affects: linux-lts-trusty (Ubuntu 

[Kernel-packages] [Bug 1554258] Re: CVE-2015-1339

[Steve Beattie]

CVE-2015-1339

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

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

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

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

** Also affects: linux-ti-omap4 (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

** Also affects: linux-ti-omap4 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Fix Committed

** Changed in: linux-lts-quantal (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Trusty)
   Status: New => Invalid

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

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

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

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

** Changed in: linux-ti-omap4 (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Trusty)
   Status: New => Fix Committed

** Changed in: linux-lts-saucy (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Precise)
   Status: New => Invalid

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

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

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

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

** Changed in: linux-mako (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-goldfish (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-flo (Ubuntu Precise)
   Status: New => Invalid

** Description changed:

- Placeholder
+ Local denial of service via memory exhaustion caused by repeatedly
+ opening and closing the /dev/cuse device file. A local attacker, 

[Kernel-packages] [Bug 1554258] [NEW] CVE-2015-1339

[Steve Beattie]

*** This bug is a security vulnerability ***

Public security bug reported:

Local denial of service via memory exhaustion caused by repeatedly
opening and closing the /dev/cuse device file. A local attacker, with
admin privileges, could use this flaw to exhaust all available memory.

Break-Fix: cc080e9e9be16ccf26135d366d7d2b65209f1d56
2c5816b4beccc8ba709144539f6fdd764f8fa49c

** Affects: linux (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-armadaxp (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-flo (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-goldfish (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-lts-quantal (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-utopic (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-mako (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-manta (Ubuntu)
 Importance: Low
 Status: New

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

** Affects: linux-ti-omap4 (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-armadaxp (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-flo (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-quantal (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-utopic (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-mako (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-manta (Ubuntu Precise)
 Importance: Low
 Status: Invalid

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

** Affects: linux-ti-omap4 (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-armadaxp (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-flo (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-quantal (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-utopic (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu Trusty)
 Importance: Low
 Status: Fix Committed

** Affects: linux-lts-xenial (Ubuntu Trusty)
 Importance: Low
 Status: Fix Committed

** Affects: linux-mako (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-manta (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Trusty)
 Importance: Undecided
 Status: New

** Affects: linux-ti-omap4 (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

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

** Affects: linux-armadaxp (Ubuntu Vivid)
 Importance: Undecided
 Status: New

** Affects: linux-flo (Ubuntu Vivid)
 Importance: Undecided
 Status: New

** Affects: linux-goldfish (Ubuntu Vivid)
 Importance: Undecided
 Status: New

** Affects: linux-lts-quantal (Ubuntu Vivid)
 Importance: Undecided
 

[Kernel-packages] [Bug 1544367] Re: CVE-2016-0617

[Steve Beattie]

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

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

Title:
  CVE-2016-0617

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  New
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-ec2 source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  New
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  New
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Invalid
Status in linux-lts-wily source package in Trusty:
  Invalid
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  New
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-ec2 source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status 

[Kernel-packages] [Bug 1554256] [NEW] CVE-2015-8830

[Steve Beattie]

*** This bug is a security vulnerability ***

Public security bug reported:

aio write triggers integer overflow in some network protocols

Break-Fix: - 4c185ce06dca14f5cea192f5a2c981ef50663f2b

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

** Affects: linux-armadaxp (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-flo (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-goldfish (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-lts-quantal (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-utopic (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-mako (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-manta (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-raspi2 (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-armadaxp (Ubuntu Precise)
 Importance: Medium
 Status: New

** Affects: linux-flo (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-quantal (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu Precise)
 Importance: Medium
 Status: New

** Affects: linux-lts-utopic (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-mako (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-manta (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Precise)
 Importance: Medium
 Status: New

** Affects: linux (Ubuntu Trusty)
 Importance: Medium
 Status: New

** Affects: linux-armadaxp (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-flo (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-quantal (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-utopic (Ubuntu Trusty)
 Importance: Medium
 Status: New

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

** Affects: linux-lts-wily (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu Trusty)
 Importance: Medium
 Status: Fix Committed

** Affects: linux-mako (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-manta (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-armadaxp (Ubuntu Vivid)
 Importance: Undecided
 Status: New

** Affects: linux-flo (Ubuntu Vivid)
 Importance: Undecided
 Status: New

** Affects: linux-goldfish (Ubuntu Vivid)
 Importance: Undecided
 Status: New

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

** Affects: linux-lts-raring (Ubuntu Vivid)
 

[Kernel-packages] [Bug 1554256] Re: CVE-2015-8830

[Steve Beattie]

CVE-2015-8830

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

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

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

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

** Also affects: linux-ti-omap4 (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

** Also affects: linux-ti-omap4 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

** Changed in: linux-lts-trusty (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Trusty)
   Status: New => Invalid

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

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

** Changed in: linux-ti-omap4 (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Trusty)
   Status: New => Fix Committed

** Changed in: linux-lts-saucy (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Precise)
   Status: New => Invalid

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

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

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

** Changed in: linux-raspi2 (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-mako (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-goldfish (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-flo (Ubuntu Precise)
   Status: New => Invalid

** Description changed:

- Placeholder
+ aio write triggers integer overflow in some network protocols
+ 
+ Break-Fix: - 4c185ce06dca14f5cea192f5a2c981ef50663f2b

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

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

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

** 

[Kernel-packages] [Bug 1545029] Re: CVE-2015-8812

[Steve Beattie]

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

** Changed in: linux-lts-xenial (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  CVE-2015-8812

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  New
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  New
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  New
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  New
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-lts-wily source package in Trusty:
  New
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  New
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-ec2 source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in 

[Kernel-packages] [Bug 1546173] Re: CVE-2016-2383

[Steve Beattie]

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

** Changed in: linux-lts-xenial (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  CVE-2016-2383

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  New
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-ec2 source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  New
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  New
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Invalid
Status in linux-lts-wily source package in Trusty:
  New
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  New
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-ec2 source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in 

[Kernel-packages] [Bug 1549203] Re: CVE-2016-2550

[Steve Beattie]

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

** Changed in: linux-lts-xenial (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  CVE-2016-2550

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux source package in Trusty:
  New
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-lts-wily source package in Trusty:
  New
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  New
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source package in Wily:
  New
Status in linux-manta source package in Wily:
  New
Status in linux-raspi2 source package in Wily:
  New
Status in linux-ti-omap4 source package in Wily:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

[Kernel-packages] [Bug 1498667] Re: [Toshiba P50W-B00F] Touchscreen no longer working

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
623f0e137c0fedb81bbf3d88be4ed300eee163da

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1498667

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  [Toshiba P50W-B00F] Touchscreen no longer working

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

Bug description:
  Sometime in the last month or so my touchscreen stopped working on my
  Toshiba P50W. The dmesg log shows it constantly reconnecting to it:

  [  556.407964] usb 1-4: new full-speed USB device number 119 using xhci_hcd
  [  556.538341] usb 1-4: New USB device found, idVendor=04f3, idProduct=0381
  [  556.538347] usb 1-4: New USB device strings: Mfr=4, Product=14, 
SerialNumber=0
  [  556.538349] usb 1-4: Product: Touchscreen
  [  556.538351] usb 1-4: Manufacturer: ELAN
  [  556.538505] usb 1-4: ep 0x2 - rounding interval to 64 microframes, ep desc 
says 80 microframes
  [  556.547788] input: ELAN Touchscreen as 
/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:0381.04A1/input/input2374
  [  556.600478] hid-multitouch 0003:04F3:0381.04A1: input,hiddev0,hidraw4: USB 
HID v1.10 Device [ELAN Touchscreen] on usb-:00:14.0-4/input0
  [  556.600584] usb 1-4: USB disconnect, device number 119

  [  556.860456] usb 1-4: new full-speed USB device number 120 using xhci_hcd
  [  556.990494] usb 1-4: New USB device found, idVendor=04f3, idProduct=0381
  [  556.990500] usb 1-4: New USB device strings: Mfr=4, Product=14, 
SerialNumber=0
  [  556.990503] usb 1-4: Product: Touchscreen
  [  556.990506] usb 1-4: Manufacturer: ELAN
  [  556.990755] usb 1-4: ep 0x2 - rounding interval to 64 microframes, ep desc 
says 80 microframes
  [  557.001248] input: ELAN Touchscreen as 
/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:0381.04A2/input/input2376
  [  557.002517] hid-multitouch 0003:04F3:0381.04A2: input,hiddev0,hidraw4: USB 
HID v1.10 Device [ELAN Touchscreen] on usb-:00:14.0-4/input0
  [  557.013831] usb 1-4: USB disconnect, device number 120

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-11-generic 4.2.0-11.13
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bob2041 F pulseaudio
   /dev/snd/controlC0:  bob2041 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep 23 09:46:25 2015
  HibernationDevice: RESUME=UUID=5033984a-21af-482d-a1fd-c075e818cd12
  InstallationDate: Installed on 2013-12-26 (635 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: TOSHIBA Satellite P50W-B
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic 
root=UUID=885f0f10-b818-4eb4-8ff4-d067e16bef2f ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-11-generic N/A
   linux-backports-modules-4.2.0-11-generic  N/A
   linux-firmware1.148
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2013-12-26 (635 days ago)
  dmi.bios.date: 08/08/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.40:bd08/08/2014:svnTOSHIBA:pnSatelliteP50W-B:pvrPSVP2A-00F002:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite P50W-B
  dmi.product.version: PSVP2A-00F002
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1498667/+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 1538040] Re: Internal Hard drive extremely slow unless using barrier=0 on ext4

[Valerio]

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

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

Title:
  Internal Hard drive extremely slow unless using barrier=0 on ext4

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a brand new laptop (Asus N551VW, i7-6700HQ, 16 Gb ram) on which
  i installed Ubuntu 14.04 64bit and a new Samsung SSD 850 PRO 512Gb
  (latest firmware). I installed the default MySql 5.6.27 on the machine
  but I noticed a very VERY slow performance of the database (just
  creating a db and executing some migrations without any data takes
  around 33 seconds while on lower-hardware co-workers notebooks it
  takes like 3 seconds). Every sql statement seems to spend most time in
  "system lock" state, as i could see with a SHOW PROCESSLIST.

  I thought it to be an hard drive issue, but executing the hard drive
  benchmark in Ubuntu gives 500 Mb/s read and 350 Mb/s write speed,
  which looks mostly normal.

  I also tried updating to the new 4.2 kernel, but the issue still
  there. To make an experiment, i cloned the ssd on a normal hard drive,
  switched it in and connected the SSD externally with an usb box. I
  moved mysql data directory to the external disk, and retried the db
  creation: it took only 2.5 seconds.

  Just out of curiosity i tried the same operation on an internal non-
  ssd disk: when the hd is plugged inside the laptop with sata, the
  database creation takes more than 2 minutes, while with the data dir
  on external usb (with the same physical disk) it took less than 10
  seconds.

  WORKAROUND: Add barrier=0 to root drive mount options with no other
  modification caused the same script to take 1.5 seconds instead of 33,
  with a 22x increase in performance.

  I have opened his bug on askubuntu 
(http://askubuntu.com/questions/725182/ssd-extremely-slow-when-connected-with-internal-sata-ok-with-external-usb
 ) and it was suggested that this coud be an issue of the controller 
firmware/driver.
  The problem is present both in trusty's default kernel (3.19.0-47.53) and in 
the 4.2 (4.2.0-25.30).

  ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  valerio2776 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=e5eee076-9bfc-4547-bf85-0208b98b57a8
  InstallationDate: Installed on 2016-01-06 (60 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. N551VW
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=5231fd09-180d-4fd2-bad5-e989207b11e7 ro quiet splash 
elevator=deadline vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  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-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.127.20
  Tags:  trusty
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N551VW.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N551VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN551VW.205:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnN551VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N551VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1538040/+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 1551854] Re: LXD bootstrap issues on xenial

[Stéphane Graber]

Ok, so investigation shows that:

 - LXD bind-mounts all that stuff, it doesn't have a choice as it's not 
privileged enough to mount things itself
 - mountall fails to run if its "optional" filesystems fail to mount (because 
that makes a lot of sense...)
 - systemd sets up the host filesystems, on a clean boot they all seem fine
 - "something" apparently remounts debugfs ro sometimes, this breaks containers
 - "something" apparently makes the /proc/sys/fs/binfmt_misc autofs go nuts 
(loop of symlinks) which also breaks containers

We could try to teach mountall to do the right thing with optional mount
and ignore their failures, however we'd need to SRU that to trusty and
precise and then nag other distros in doing the same (centos, oracle,
rhel, ...) before we can get rid of our workaround.

As a clean Xenial system does work properly, I think it would be best to
figure out what's messing with debugfs and binfmt_misc post-boot and fix
whatever it is to stop doing that.

Would be useful if the bug reporters could document exactly what they
did on their system between the time it worked fine and the time it
stopped working so we can figure out what's messing with those mounts.

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

Title:
  LXD bootstrap issues on xenial

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using lxd with zfs block storage on xenial, and having issues with
  trusty containers. I've witnessed this problem when trying to
  bootstrap as well as after rebooting the host and a container failed
  to start.

  In the latter case, the container that failed to start was the juju
  controller:

  c@mawhrin-skel:~/omnibus-layers$ lxc list 
   [3/3]
  
+-+-++--++---+
  |NAME |  STATE  | 
 IPV4  | IPV6 |TYPE| SNAPSHOTS |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0 | STOPPED | 
   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-1 | RUNNING | 10.0.3.28 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-2 | RUNNING | 10.0.3.85 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-3 | RUNNING | 10.0.3.176 
(eth0)  |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-4 | RUNNING | 10.0.3.66 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-5 | RUNNING | 10.0.3.31 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-6 | RUNNING | 10.0.3.196 
(eth0)  |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-7 | RUNNING | 10.0.3.186 
(eth0)  |  | PERSISTENT | 0 |
  | | | 10.0.4.1 
(lxcbr0)  |  ||   |
  
+-+-++--++---+

  I manually started it, but found that no upstart services were
  started. Remembering this thread,
  https://lists.ubuntu.com/archives/juju/2016-February/006698.html, I
  checked /var/log/mountall.log in the machine-0 container, and sure
  enough:

  root@juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0:~# cat 
/var/log/upstart/mountall.log
  mount: permission denied
  mountall: 

[Kernel-packages] [Bug 1538040] Re: Internal Hard drive extremely slow unless using barrier=0 on ext4

[Valerio]

Tested with kernel 4.5rc7 and the issue is still there...sigh.

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

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

Title:
  Internal Hard drive extremely slow unless using barrier=0 on ext4

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a brand new laptop (Asus N551VW, i7-6700HQ, 16 Gb ram) on which
  i installed Ubuntu 14.04 64bit and a new Samsung SSD 850 PRO 512Gb
  (latest firmware). I installed the default MySql 5.6.27 on the machine
  but I noticed a very VERY slow performance of the database (just
  creating a db and executing some migrations without any data takes
  around 33 seconds while on lower-hardware co-workers notebooks it
  takes like 3 seconds). Every sql statement seems to spend most time in
  "system lock" state, as i could see with a SHOW PROCESSLIST.

  I thought it to be an hard drive issue, but executing the hard drive
  benchmark in Ubuntu gives 500 Mb/s read and 350 Mb/s write speed,
  which looks mostly normal.

  I also tried updating to the new 4.2 kernel, but the issue still
  there. To make an experiment, i cloned the ssd on a normal hard drive,
  switched it in and connected the SSD externally with an usb box. I
  moved mysql data directory to the external disk, and retried the db
  creation: it took only 2.5 seconds.

  Just out of curiosity i tried the same operation on an internal non-
  ssd disk: when the hd is plugged inside the laptop with sata, the
  database creation takes more than 2 minutes, while with the data dir
  on external usb (with the same physical disk) it took less than 10
  seconds.

  WORKAROUND: Add barrier=0 to root drive mount options with no other
  modification caused the same script to take 1.5 seconds instead of 33,
  with a 22x increase in performance.

  I have opened his bug on askubuntu 
(http://askubuntu.com/questions/725182/ssd-extremely-slow-when-connected-with-internal-sata-ok-with-external-usb
 ) and it was suggested that this coud be an issue of the controller 
firmware/driver.
  The problem is present both in trusty's default kernel (3.19.0-47.53) and in 
the 4.2 (4.2.0-25.30).

  ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  valerio2776 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=e5eee076-9bfc-4547-bf85-0208b98b57a8
  InstallationDate: Installed on 2016-01-06 (60 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. N551VW
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=5231fd09-180d-4fd2-bad5-e989207b11e7 ro quiet splash 
elevator=deadline vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  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-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.127.20
  Tags:  trusty
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N551VW.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N551VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN551VW.205:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnN551VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N551VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1538040/+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 1547619] Re: Intermittent screen blinking with 4k external mini display port with 4.4 kernels

[Gronor]

People reported 4.5.0-040500rc6 fixes the bug for them.

You can see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719
for reference

I am on 4.5.0 RC6 myself and for me it is not fixed. It is a lot better,
screen blinking is reduced a lot but it still happens from time to time.

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

Title:
  Intermittent screen blinking with 4k external mini display port with
  4.4 kernels

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

Bug description:
  When using an external 4K monitor plugged into the mini display port on my 
Dell XPS 13 9343 using both the laptop screen and the external monitor 
(external monitor is left and laptop screen right), when using all of the 
following kernels:
  4.4.0-2.16-generic
  4.4.0-4.19-generic
  4.4.0-6.21-generic
  4.4.0-7.22-generic

  the external monitor will sometimes blink off for about a second or
  two, then back on. What is weird is this seems to only happen when
  typing into a gnome-terminal as opposed to firefox or evolution.
  Simply changing to a gnome-terminal and typing into it doesn't cause
  the blinking, but it might happen immediately or it might take several
  minutes.

  4.3.0-7.18-generic worked fine and I can go hours and hours in a
  gnome-terminal with no issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-6-generic 4.4.0-6.21
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jamie  5882 F pulseaudio
   /dev/snd/controlC1:  jamie  5882 F pulseaudio
   /dev/snd/controlC0:  jamie  5882 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Feb 19 12:09:28 2016
  HibernationDevice: RESUME=UUID=27fa6713-c8c2-4eb8-9766-ba6918bc1cfb
  InstallationDate: Installed on 2015-06-13 (250 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-6-generic.efi.signed 
root=UUID=7bc4dcd2-0bd8-4e42-b8b7-9f1ed6b8a3e9 ro libata.force=noncq kaslr 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-6-generic N/A
   linux-backports-modules-4.4.0-6-generic  N/A
   linux-firmware   1.156
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-01-12 (38 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

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

[Steve Beattie]

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

** Changed in: linux-ti-omap4 (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Precise)
   Status: New => Invalid

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

Title:
  CVE-2015-7885

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-lts-wily source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in 

[Kernel-packages] [Bug 1548867] Re: After upgrading to 4.2.0.30 there's no desktop

[Marco van Zwetselaar]

4.2.8-040208ckt2-generic_4.2.8-040208ckt2.201603071309 has the bug,
sorry :-/

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

Title:
  After upgrading to 4.2.0.30 there's no desktop

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

Bug description:
  Hi,

  This morning I've updated my Ubuntu 15.10 to kernel 4.2.0.30 and now
  can't enter to the desktop. In fact, the laptop freezes after grub
  screen.

  If start from the recovery, from "upstart" option I get a message like
  "upstart: broken pipe". And I enter to "recovery mode" options  and
  after resume with the normal start the desktop loads but only with
  1024x768 or 800x600

  I've have to start with the previous kernel, the 4.2.0.27. Then all
  works as expected and I log to my desktop as usual.

  Thank you very much.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert 2638 F pulseaudio
   /dev/snd/controlC1:  albert 2638 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=3ea73c4c-4dc5-4f7f-8c97-d2f477414305
  InstallationDate: Installed on 2016-01-20 (34 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Hewlett-Packard HP G62 Notebook PC
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=es_ES
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=e34b1243-4d35-4e1d-ab47-19304b7c369b ro recovery nomodeset
  ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/15/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.29
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 143C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 62.3D
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.29:bd03/15/2011:svnHewlett-Packard:pnHPG62NotebookPC:pvr059411252710001020100:rvnHewlett-Packard:rn143C:rvr62.3D:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP G62 Notebook PC
  dmi.product.version: 059411252710001020100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548867/+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 1551854] Re: LXD bootstrap issues on xenial

[Casey Marshall]

Haven't seen it in a few days. I'll reboot and see if I can reproduce
it. It usually happens after rebooting the host, when launching new
containers or existing ones would autostart.

Info you requested. I think the /usr/share/lxc/... might have been a red
herring. I'm exclusively using LXD on this xenial host, not messing with
the old lxc commands.

$ dpkg -l lxc liblxc1 lxd lxd-client lxcfs
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion  Architecture 
Description
+++-===---
ii  liblxc1 2.0.0~rc5-0ubuntu1   amd64
Linux Containers userspace tools (library)
ii  lxc 2.0.0~rc5-0ubuntu1   all  
Transitional package for lxc1
ii  lxcfs   2.0.0~rc2-0ubuntu2   amd64
FUSE based filesystem for LXC
ii  lxd 2.0.0~rc1-0ubuntu3   amd64
Container hypervisor based on LXC - daemon
ii  lxd-client  2.0.0~rc1-0ubuntu3   amd64
Container hypervisor based on LXC - client

$ lxc info
apicompat: 0
auth: trusted
environment:
  addresses:
  - 192.168.88.234:8443
  - 192.168.122.1:8443
  - 10.0.3.1:8443
  architectures:
  - x86_64
  - i686
  certificate: |
-BEGIN CERTIFICATE-
MIIFqjCCA5KgAwIBAgIQXpne6Qjwhg8de+RmyV1+mTANBgkqhkiG9w0BAQsFADA6
MRwwGgYDVQQKExNsaW51eGNvbnRhaW5lcnMub3JnMRowGAYDVQQDDBFyb290QG1h
d2hyaW4tc2tlbDAeFw0xNjAyMjgwMzEyMzdaFw0yNjAyMjUwMzEyMzdaMDoxHDAa
BgNVBAoTE2xpbnV4Y29udGFpbmVycy5vcmcxGjAYBgNVBAMMEXJvb3RAbWF3aHJp
bi1za2VsMIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAzv/3uX3JWduq
wmtbyTABmfJkup6Z5Lh4lKPXgL/H2gQ/mlccORKm1eDZhAGmv9UuQGeMRHEneJqD
V9c3f7/9cJBwvz2loKlppWj0ohAzTP91L8paeUSfP4X9EAr702Qjyb2ig+xWv5tM
cJxbdl0zGpjYO1P+xmUdthSidsFrzWQPXptOlcZvak7n0QL5GlkVXdqX+she2Pbs
ONtyTaBSpF3zEYv6cM9ZeJYL4Hl7LEQ1/p8ojpOyaxO8B1Cn/gIbuDqgzRwmei90
Aca06YDF4SHVcl8qFajrwkPF3jWW5pgS8sAJlYoq2+ROhl0CnpdBl4AiJrvfFsIs
RL8dKSuFA6AcLhYooWgMy6UWR8mLbmYHp04ThuBDoRaTt0uGLDlTAfMg7e8Gwpz+
aEwxSzzQhvJYr4e6TSP1C4zXNqS5mUHfm6RtfEccVFmq6vyqZGELAyREce76J88V
FMf/V+KYlQYUxo0JH2k+BYMO4Iigar0+8p8o8drqh6Lks5zTP6idsKa0LSWA4rwm
3+5hjnVJtFa9CVCItJW3r0+nczwtAbjvRojkr7Yb2Kifufhilb+I695qSk+Toug3
HKOODTqc9sbH+urmfr7jBBexACtWVX/tMptWFnBmcqoN4ptSZutY7CPf+KR//9p0
8fFRQP+ItmElJHRFO+madGOBMVrC7j8CAwEAAaOBqzCBqDAOBgNVHQ8BAf8EBAMC
BaAwEwYDVR0lBAwwCgYIKwYBBQUHAwEwDAYDVR0TAQH/BAIwADBzBgNVHREEbDBq
ggxtYXdocmluLXNrZWyCETE5Mi4xNjguODguMjM0LzI0ghxmZTgwOjozZWE5OmY0
ZmY6ZmU1Njo0N2RjLzY0ggsxMC4wLjMuMS8yNIIcZmU4MDo6NThkNTpjMmZmOmZl
ZTQ6NzJiYy82NDANBgkqhkiG9w0BAQsFAAOCAgEAB6aFItuxlZm5+2/IB2eCVAM0
eQbO6dfvfF2khfiEbWWaKPtkZSYKlDIcoOph35obnNMQjT+y4zlnF/fepvjq8P1R
yGd+Q+GMcXWVRht3uIMW2ZqwNqOujunyn9+Hl1SYi1dV1g/CH9lJt8I7FKIvyieh
siZRe5Zp7TdPREkIJveuz8qB3X87WVh9bqvMpoX91Mgrjzd3qATef/tN0HP+b26Y
XjtRz9rhOkUfJx9b5HsyBLuGOQS979twl9LPKc1WsIrJaavY1JBT7SIwX3W7u7CU
UWueEQoVvA9pkgeL8NXYYoHOkkrfW3oqExkuA1pqucMt8iRjn88njV57Vk576tjZ
+bNqLL6R4xoUvnr9VIwq7tMLvodK/E5WvsmP5GrdMru2sa/xd+fS0137oOYqP4Qb
T296jMcehHg5Gg1ZR1DbTqzWFPKb+CtXU+bqI68Hplq5Lemufsman2C2dthmKwcm
OumpykWiH9vNKauY52VR8iffppBsH7jup1+yVtIOiT4Whp5LGBtZdYri7GE77qv+
qtBL7HdeBJxsBadRIfjdeLZlZPlMX7hV+v8Bzxz9fGuPKSnxDdpoPw1XF+zP1YAn
VeDCRo7oCFV40nVFyb5wCreDoegtSFuQt7/Guv9u/gQSfmGoY1QyjlaHh2pJAAgS
CPRGObnrdrQMMEqLDaI=
-END CERTIFICATE-
  driver: lxc
  driverversion: 2.0.0.rc5
  kernel: Linux
  kernelarchitecture: x86_64
  kernelversion: 4.4.0-10-generic
  server: lxd
  serverpid: 2382
  serverversion: 2.0.0.rc1
  storage: zfs
  storageversion: "5"
config:
  core.https_address: '[::]'
  storage.zfs_pool_name: lxdpool
public: false

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

Title:
  LXD bootstrap issues on xenial

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using lxd with zfs block storage on xenial, and having issues with
  trusty containers. I've witnessed this problem when trying to
  bootstrap as well as after rebooting the host and a container failed
  to start.

  In the latter case, the container that failed to start was the juju
  controller:

  c@mawhrin-skel:~/omnibus-layers$ lxc list 
   [3/3]
  
+-+-++--++---+
  |NAME |  STATE  | 
 IPV4   

[Kernel-packages] [Bug 1534440] Re: CVE-2015-7566

[Steve Beattie]

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

** Changed in: linux-lts-wily (Ubuntu Trusty)
   Status: New => Fix Committed

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

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

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

** Changed in: linux-lts-xenial (Ubuntu Trusty)
   Status: New => Fix Committed

** Changed in: linux-lts-vivid (Ubuntu Trusty)
   Status: New => Fix Committed

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

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

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  CVE-2015-7566

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  New
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Committed
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  New
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  New
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
Status in linux-lts-wily source package in Trusty:
  Fix Committed
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  New
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in 

[Kernel-packages] [Bug 1551854] Re: LXD bootstrap issues on xenial

[Stéphane Graber]

Please can everyone affected by this issue post the output of: dpkg -l
lxc liblxc1 lxd lxd-client lxcfs

It's very difficult to figure out what's wrong when we don't even know
the version being used.

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

Title:
  LXD bootstrap issues on xenial

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using lxd with zfs block storage on xenial, and having issues with
  trusty containers. I've witnessed this problem when trying to
  bootstrap as well as after rebooting the host and a container failed
  to start.

  In the latter case, the container that failed to start was the juju
  controller:

  c@mawhrin-skel:~/omnibus-layers$ lxc list 
   [3/3]
  
+-+-++--++---+
  |NAME |  STATE  | 
 IPV4  | IPV6 |TYPE| SNAPSHOTS |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0 | STOPPED | 
   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-1 | RUNNING | 10.0.3.28 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-2 | RUNNING | 10.0.3.85 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-3 | RUNNING | 10.0.3.176 
(eth0)  |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-4 | RUNNING | 10.0.3.66 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-5 | RUNNING | 10.0.3.31 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-6 | RUNNING | 10.0.3.196 
(eth0)  |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-7 | RUNNING | 10.0.3.186 
(eth0)  |  | PERSISTENT | 0 |
  | | | 10.0.4.1 
(lxcbr0)  |  ||   |
  
+-+-++--++---+

  I manually started it, but found that no upstart services were
  started. Remembering this thread,
  https://lists.ubuntu.com/archives/juju/2016-February/006698.html, I
  checked /var/log/mountall.log in the machine-0 container, and sure
  enough:

  root@juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0:~# cat 
/var/log/upstart/mountall.log
  mount: permission denied
  mountall: mount /sys/kernel/debug [187] terminated with status 32
  mountall: Filesystem could not be mounted: /sys/kernel/debug

  The problem persists if I stop and start the container. If I remount
  /sys/kernel/debug on the host, then stop and start the container,
  upstart succeeds and the juju controller starts up.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-8-generic 4.4.0-8.23
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  c 24562 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Mar  1 10:52:45 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=007cedda-f922-4e4c-89b1-57b31f18292e
  InstallationDate: Installed on 2016-02-28 (2 

[Kernel-packages] [Bug 1551854] Re: LXD bootstrap issues on xenial

[Stéphane Graber]

Oh and "lxc info" too for good measure (just in case lxd wasn't
restarted post-upgrade).

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

Title:
  LXD bootstrap issues on xenial

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using lxd with zfs block storage on xenial, and having issues with
  trusty containers. I've witnessed this problem when trying to
  bootstrap as well as after rebooting the host and a container failed
  to start.

  In the latter case, the container that failed to start was the juju
  controller:

  c@mawhrin-skel:~/omnibus-layers$ lxc list 
   [3/3]
  
+-+-++--++---+
  |NAME |  STATE  | 
 IPV4  | IPV6 |TYPE| SNAPSHOTS |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0 | STOPPED | 
   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-1 | RUNNING | 10.0.3.28 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-2 | RUNNING | 10.0.3.85 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-3 | RUNNING | 10.0.3.176 
(eth0)  |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-4 | RUNNING | 10.0.3.66 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-5 | RUNNING | 10.0.3.31 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-6 | RUNNING | 10.0.3.196 
(eth0)  |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-7 | RUNNING | 10.0.3.186 
(eth0)  |  | PERSISTENT | 0 |
  | | | 10.0.4.1 
(lxcbr0)  |  ||   |
  
+-+-++--++---+

  I manually started it, but found that no upstart services were
  started. Remembering this thread,
  https://lists.ubuntu.com/archives/juju/2016-February/006698.html, I
  checked /var/log/mountall.log in the machine-0 container, and sure
  enough:

  root@juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0:~# cat 
/var/log/upstart/mountall.log
  mount: permission denied
  mountall: mount /sys/kernel/debug [187] terminated with status 32
  mountall: Filesystem could not be mounted: /sys/kernel/debug

  The problem persists if I stop and start the container. If I remount
  /sys/kernel/debug on the host, then stop and start the container,
  upstart succeeds and the juju controller starts up.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-8-generic 4.4.0-8.23
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  c 24562 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Mar  1 10:52:45 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=007cedda-f922-4e4c-89b1-57b31f18292e
  InstallationDate: Installed on 2016-02-28 (2 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  MachineType: LENOVO 2306CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1496927] Re: [Hyper-V] udev trying to modify owner and mode of /dev/vmbus/hv_vss

[Joseph Salisbury]

Commit ed9ba608e is in Xenial as of the Ubuntu-4.4.0-9.24 kernel.  So if
commit ed9ba608e is the real fix, this bug should already be 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/1496927

Title:
  [Hyper-V] udev trying to modify owner and mode of /dev/vmbus/hv_vss

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

Bug description:
  While testing Ubuntu 15.10 Wily Werewolf (development branch) 64 bit
  we found the below issue.

  Repro rate: 100%
  Repro details:
  Hyper-V: Server 2012 (no R2) - WS 2012 is the only affected platform
  Daily build version: 2015.09.10
  Kernel: kernel 4.2.0-7-generic

  During the below event, we also noticed that system-udevd is
  constantly around 100% CPU on the VM, taking a lot of cycles.

  On Server 2012 we don't have the Live backup with VSS feature, so
  these messages should not occur in the first place.

  After 20 minutes we have over 3000 messages in the logs, all like below:
  Sep 14 17:43:33 ubuntu systemd-udevd[14292]: setting owner of 
/dev/vmbus/hv_vss to uid=0, gid=0 failed: No such file or directory
  Sep 14 17:44:00 ubuntu systemd-udevd[14292]: setting mode of 
/dev/vmbus/hv_vss to 020600 failed: No such file or directory
  Sep 14 17:44:00 ubuntu systemd-udevd[14292]: setting owner of 
/dev/vmbus/hv_vss to uid=0, gid=0 failed: No such file or directory
  Sep 14 17:44:01 ubuntu systemd-udevd[14292]: setting mode of 
/dev/vmbus/hv_vss to 020600 failed: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1496927/+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 1551854] Re: LXD bootstrap issues on xenial

[Stéphane Graber]

I'd like to note that LXD works differently from LXC here.

In LXC we mount debugfs through ubuntu.common.conf whereas with lxd, we
simply bind-mount /sys/kernel/debug from the host if it exists.

LXD doesn't use any of the /usr/share/lxc/* files. If it does on your
system, then you most definitely aren't running LXD 2.0.

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

Title:
  LXD bootstrap issues on xenial

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using lxd with zfs block storage on xenial, and having issues with
  trusty containers. I've witnessed this problem when trying to
  bootstrap as well as after rebooting the host and a container failed
  to start.

  In the latter case, the container that failed to start was the juju
  controller:

  c@mawhrin-skel:~/omnibus-layers$ lxc list 
   [3/3]
  
+-+-++--++---+
  |NAME |  STATE  | 
 IPV4  | IPV6 |TYPE| SNAPSHOTS |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0 | STOPPED | 
   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-1 | RUNNING | 10.0.3.28 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-2 | RUNNING | 10.0.3.85 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-3 | RUNNING | 10.0.3.176 
(eth0)  |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-4 | RUNNING | 10.0.3.66 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-5 | RUNNING | 10.0.3.31 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-6 | RUNNING | 10.0.3.196 
(eth0)  |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-7 | RUNNING | 10.0.3.186 
(eth0)  |  | PERSISTENT | 0 |
  | | | 10.0.4.1 
(lxcbr0)  |  ||   |
  
+-+-++--++---+

  I manually started it, but found that no upstart services were
  started. Remembering this thread,
  https://lists.ubuntu.com/archives/juju/2016-February/006698.html, I
  checked /var/log/mountall.log in the machine-0 container, and sure
  enough:

  root@juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0:~# cat 
/var/log/upstart/mountall.log
  mount: permission denied
  mountall: mount /sys/kernel/debug [187] terminated with status 32
  mountall: Filesystem could not be mounted: /sys/kernel/debug

  The problem persists if I stop and start the container. If I remount
  /sys/kernel/debug on the host, then stop and start the container,
  upstart succeeds and the juju controller starts up.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-8-generic 4.4.0-8.23
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  c 24562 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Mar  1 10:52:45 2016
  EcryptfsInUse: Yes
  HibernationDevice: 

[Kernel-packages] [Bug 1551854] Re: LXD bootstrap issues on xenial

[Seth Forshee]

Casey: Any luck reproducing? I'd still like to see what 'mount | grep
debugfs' in the host shows when this is happening.

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

Title:
  LXD bootstrap issues on xenial

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using lxd with zfs block storage on xenial, and having issues with
  trusty containers. I've witnessed this problem when trying to
  bootstrap as well as after rebooting the host and a container failed
  to start.

  In the latter case, the container that failed to start was the juju
  controller:

  c@mawhrin-skel:~/omnibus-layers$ lxc list 
   [3/3]
  
+-+-++--++---+
  |NAME |  STATE  | 
 IPV4  | IPV6 |TYPE| SNAPSHOTS |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0 | STOPPED | 
   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-1 | RUNNING | 10.0.3.28 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-2 | RUNNING | 10.0.3.85 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-3 | RUNNING | 10.0.3.176 
(eth0)  |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-4 | RUNNING | 10.0.3.66 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-5 | RUNNING | 10.0.3.31 
(eth0)   |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-6 | RUNNING | 10.0.3.196 
(eth0)  |  | PERSISTENT | 0 |
  
+-+-++--++---+
  | juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-7 | RUNNING | 10.0.3.186 
(eth0)  |  | PERSISTENT | 0 |
  | | | 10.0.4.1 
(lxcbr0)  |  ||   |
  
+-+-++--++---+

  I manually started it, but found that no upstart services were
  started. Remembering this thread,
  https://lists.ubuntu.com/archives/juju/2016-February/006698.html, I
  checked /var/log/mountall.log in the machine-0 container, and sure
  enough:

  root@juju-5f4bd172-ad22-4726-8d84-47185ab31b54-machine-0:~# cat 
/var/log/upstart/mountall.log
  mount: permission denied
  mountall: mount /sys/kernel/debug [187] terminated with status 32
  mountall: Filesystem could not be mounted: /sys/kernel/debug

  The problem persists if I stop and start the container. If I remount
  /sys/kernel/debug on the host, then stop and start the container,
  upstart succeeds and the juju controller starts up.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-8-generic 4.4.0-8.23
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  c 24562 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Mar  1 10:52:45 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=007cedda-f922-4e4c-89b1-57b31f18292e
  InstallationDate: Installed on 2016-02-28 (2 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  MachineType: LENOVO 2306CTO
  ProcFB: 0 inteldrmfb
  

[Kernel-packages] [Bug 1496927] Re: [Hyper-V] udev trying to modify owner and mode of /dev/vmbus/hv_vss

[Joseph Salisbury]

I believe the following commit will fix this bug:

commit ed9ba608e4851144af8c7061cbb19f751c73e998
Author: Olaf Hering 
Date:   Mon Dec 14 16:01:42 2015 -0800

Drivers: hv: vss: run only on supported host versions


I built a Wily test kernel with this commit, which can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1496927/

Can you confirm this test kernel fixes 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/1496927

Title:
  [Hyper-V] udev trying to modify owner and mode of /dev/vmbus/hv_vss

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

Bug description:
  While testing Ubuntu 15.10 Wily Werewolf (development branch) 64 bit
  we found the below issue.

  Repro rate: 100%
  Repro details:
  Hyper-V: Server 2012 (no R2) - WS 2012 is the only affected platform
  Daily build version: 2015.09.10
  Kernel: kernel 4.2.0-7-generic

  During the below event, we also noticed that system-udevd is
  constantly around 100% CPU on the VM, taking a lot of cycles.

  On Server 2012 we don't have the Live backup with VSS feature, so
  these messages should not occur in the first place.

  After 20 minutes we have over 3000 messages in the logs, all like below:
  Sep 14 17:43:33 ubuntu systemd-udevd[14292]: setting owner of 
/dev/vmbus/hv_vss to uid=0, gid=0 failed: No such file or directory
  Sep 14 17:44:00 ubuntu systemd-udevd[14292]: setting mode of 
/dev/vmbus/hv_vss to 020600 failed: No such file or directory
  Sep 14 17:44:00 ubuntu systemd-udevd[14292]: setting owner of 
/dev/vmbus/hv_vss to uid=0, gid=0 failed: No such file or directory
  Sep 14 17:44:01 ubuntu systemd-udevd[14292]: setting mode of 
/dev/vmbus/hv_vss to 020600 failed: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1496927/+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 1501260] Re: drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in dpll_hw_state.wrpll (expected 0xb0210614, found 0x00000000

[Christopher M. Penalver]

Martin Pecka, it will help immensely if you filed a new report with the Ubuntu 
repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in
  dpll_hw_state.wrpll (expected 0xb0210614, found 0x

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While surfing, I clicked on something,, X died, I was thrown back to a 
console and finally was able to log back in.
  dmesg is cluttered with:
   

  
  [79849.958943] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in 
dpll_hw_state.wrpll (expected 0xb0210614, found 0x)
  [79849.958944] [ cut here ]
  [79849.958962] WARNING: CPU: 0 PID: 14689 at 
/build/linux-1dujk3/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12326 
check_crtc_state+0x2c5/0x440 [i915]()
  [79849.958963] pipe state doesn't match!
  [79849.958981] Modules linked in: bnep bluetooth binfmt_misc nls_iso8859_1 
intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi 
coretemp snd_hda_codec_realtek input_leds snd_hda_codec_generic kvm_intel 
snd_hda_intel kvm snd_hda_codec snd_hda_core snd_hwdep snd_pcm crct10dif_pclmul 
snd_seq_midi snd_seq_midi_event snd_rawmidi crc32_pclmul ghash_clmulni_intel 
snd_seq snd_seq_device snd_timer mei_me aesni_intel snd mei aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd soundcore serio_raw 8250_fintek 
fujitsu_laptop lpc_ich tpm_infineon mac_hid parport_pc ppdev lp parport autofs4 
hid_generic usbhid hid i915 psmouse ahci libahci i2c_algo_bit drm_kms_helper 
e1000e drm ptp pps_core video
  [79849.958983] CPU: 0 PID: 14689 Comm: Xorg Tainted: GW   
4.2.0-11-generic #13-Ubuntu
  [79849.958983] Hardware name: FUJITSU ESPRIMO E920/D3222-A1, BIOS V4.6.5.4 
R1.34.0 for D3222-A1x 01/08/2015
  [79849.958985]  c0232ab0 88030edef538 817b0cc5 

  [79849.958986]  88030edef588 88030edef578 81076536 
88030edef5a8
  [79849.958986]  88030edef610 88030a600800 0001 
88030a600b50
  [79849.958987] Call Trace:
  [79849.958991]  [] dump_stack+0x45/0x57
  [79849.958994]  [] warn_slowpath_common+0x86/0xc0
  [79849.958995]  [] warn_slowpath_fmt+0x46/0x50
  [79849.959008]  [] ? intel_pipe_config_compare+0xa67/0xc60 
[i915]
  [79849.959015]  [] check_crtc_state+0x2c5/0x440 [i915]
  [79849.959024]  [] intel_modeset_check_state+0x20e/0x6b0 
[i915]
  [79849.959032]  [] intel_crtc_set_config+0x4c7/0x580 [i915]
  [79849.959042]  [] drm_mode_set_config_internal+0x66/0x100 
[drm]
  [79849.959045]  [] restore_fbdev_mode+0xc2/0xf0 
[drm_kms_helper]
  [79849.959048]  [] 
drm_fb_helper_restore_fbdev_mode_unlocked+0x29/0x70 [drm_kms_helper]
  [79849.959050]  [] drm_fb_helper_set_par+0x22/0x40 
[drm_kms_helper]
  [79849.959060]  [] intel_fbdev_set_par+0x1a/0x60 [i915]
  [79849.959062]  [] ? ttwu_do_activate.constprop.89+0x5d/0x70
  [79849.959064]  [] fb_set_var+0x238/0x460
  [79849.959066]  [] ? do_sys_poll+0x127/0x5a0
  [79849.959068]  [] fbcon_blank+0x2e9/0x330
  [79849.959070]  [] ? check_preempt_wakeup+0x193/0x220
  [79849.959071]  [] do_unblank_screen+0xd3/0x1a0
  [79849.959073]  [] vt_ioctl+0x4fb/0x12c0
  [79849.959074]  [] ? default_wake_function+0x12/0x20
  [79849.959076]  [] ? autoremove_wake_function+0x16/0x40
  [79849.959078]  [] tty_ioctl+0x3cc/0xbb0
  [79849.959079]  [] ? __wake_up+0x48/0x60
  [79849.959080]  [] ? wake_nocb_leader+0x4d/0x50
  [79849.959081]  [] ? __call_rcu_nocb_enqueue+0xcd/0xd0
  [79849.959083]  [] do_vfs_ioctl+0x285/0x470
  [79849.959084]  [] ? mntput+0x24/0x40
  [79849.959085]  [] ? __fput+0x190/0x220
  [79849.959086]  [] SyS_ioctl+0x79/0x90
  [79849.959088]  [] entry_SYSCALL_64_fastpath+0x16/0x75
  [79849.959089] ---[ end trace c15f693470bdbc48 ]---
  [79849.959131] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in 
dpll_hw_state.wrpll (expected 0xb0210614, found 0x)
  [79849.959131] [ cut here ]

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-11-generic 4.2.0-11.13
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hildeb25581 F pulseaudio
   /dev/snd/controlC1:  hildeb25581 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep 30 12:04:59 2015
  HibernationDevice: RESUME=UUID=d5037585-3853-4049-a410-b17d0c104ef3
  InstallationDate: Installed on 2014-06-19 (467 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   

[Kernel-packages] [Bug 1553391] Regression Testing completed but no status tags applied

[Brad Figg]

The regression-testing task was set to Fix Released but neither the qa-
testing-passed or qa-testing-failed tag was applied


** Changed in: kernel-development-workflow/regression-testing
   Status: Fix Released => Incomplete

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

** Description changed:

  This bug is for tracking the 4.4.0-11.26 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Friday, 04. March 2016 22:33 UTC
- kernel-phase-changed:Friday, 04. March 2016 22:33 UTC
- kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Saturday, 05. March 2016 00:00 UTC
  proposed-announcement-sent:True
+ kernel-phase:OnHold
+ kernel-phase-changed:Monday, 07. March 2016 21:00 UTC

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

Title:
  linux: 4.4.0-11.26 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Friday, 04. March 2016 22:33 UTC
  kernel-stable-Promote-to-proposed-end:Saturday, 05. March 2016 00:00 UTC
  proposed-announcement-sent:True
  kernel-phase:OnHold
  kernel-phase-changed:Monday, 07. March 2016 21:00 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1553391/+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 1530171] Re: [Regression] Thinkpad dock: External monitors not recognized after 15.04 upgrade

[Christopher M. Penalver]

Robert Schetterer, it will help immensely if you filed a new report with the 
Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  [Regression] Thinkpad dock: External monitors not recognized after
  15.04 upgrade

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  External monitors are not recognized in display settings when plugged
  into any dock port.

  They *are* recognized after a reboot (not after logout).
  After plugging out and the in again they are not recognized.

  A monitor plugged in and out of the non-dock VGA is recognized instantly.
  After plugging in or out of the non-dock VGA, monitors plugged to dock ports 
are recognized (which serves as a crazy workaround for me now)
  (update: this works sometimes, sometimes not).

  Everything used to work with 14.10, but stopped with 15.04.

  A recent test with 1510 live CD did not fix this.
  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: 2016-01-04 01:09:49,649 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroRelease: Ubuntu 15.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:501e]
  InstallationDate: Installed on 2015-03-05 (311 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: LENOVO 20AUS00N00
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-43-generic 
root=UUID=82cd15d9-7510-4d2f-a698-28fa51216e13 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10
  Tags:  vivid ubuntu compiz-0.9
  Uname: Linux 3.19.0-43-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2016-01-04 (6 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare saned sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J4ET67WW(1.67)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AUS00N00
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ4ET67WW(1.67):bd08/13/2014:svnLENOVO:pn20AUS00N00:pvrThinkPadL540:rvnLENOVO:rn20AUS00N00:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AUS00N00
  dmi.product.version: ThinkPad L540
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.1+15.04.20150922-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Wed Jan  6 15:29:10 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5568
   vendor CMN
  xserver.version: 2:1.17.1-0ubuntu3.1

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

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

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

[Christopher M. Penalver]

a1291762, as per
http://h20564.www2.hp.com/hpsc/swd/public/readIndex?sp4ts.oid=3781730=8=4060
an update to your computer's buggy, insecure, and outdated BIOS is
available (F.20). If you update to this following
https://help.ubuntu.com/community/BIOSUpdate does it change anything?

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful.

Also, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible:
1) Please provide the output of the following terminal command (not perform an 
apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on if there was an improvement 
or not.
3) Please mark this report Status Confirmed.

If it's not reproducible, please mark this as Invalid.

Thank you for your understanding.

** Tags added: bios-outdated-f.20

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

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

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1501260] Re: drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in dpll_hw_state.wrpll (expected 0xb0210614, found 0x00000000

[Martin Pecka]

I'm also affected by this bug, when running both glxgears and Gazebo
simulator (or, its graphical client using OpenGL).

Switching to a terminal (Ctrl+Alt+F1) and back unfreezes the screen for
a while. The screen only looks frozen, but normally reacts to mouse and
keyboard events. This only happens if the GL window is displayed on my
primary display (which is handled by the intel integrated chip). The
notebook has 2 video outputs and a discrete AMD graphics, and I think
only one of the outputs is handled by the AMD card, so I think one of
the outputs is handled by the intel card and does not get frozen.

Ubuntu 14.04.3 64bit.

I think that before upgrading from 14.04.2 to 14.04.3 this did not
happen.

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

Title:
  drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in
  dpll_hw_state.wrpll (expected 0xb0210614, found 0x

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While surfing, I clicked on something,, X died, I was thrown back to a 
console and finally was able to log back in.
  dmesg is cluttered with:
   

  
  [79849.958943] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in 
dpll_hw_state.wrpll (expected 0xb0210614, found 0x)
  [79849.958944] [ cut here ]
  [79849.958962] WARNING: CPU: 0 PID: 14689 at 
/build/linux-1dujk3/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12326 
check_crtc_state+0x2c5/0x440 [i915]()
  [79849.958963] pipe state doesn't match!
  [79849.958981] Modules linked in: bnep bluetooth binfmt_misc nls_iso8859_1 
intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi 
coretemp snd_hda_codec_realtek input_leds snd_hda_codec_generic kvm_intel 
snd_hda_intel kvm snd_hda_codec snd_hda_core snd_hwdep snd_pcm crct10dif_pclmul 
snd_seq_midi snd_seq_midi_event snd_rawmidi crc32_pclmul ghash_clmulni_intel 
snd_seq snd_seq_device snd_timer mei_me aesni_intel snd mei aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd soundcore serio_raw 8250_fintek 
fujitsu_laptop lpc_ich tpm_infineon mac_hid parport_pc ppdev lp parport autofs4 
hid_generic usbhid hid i915 psmouse ahci libahci i2c_algo_bit drm_kms_helper 
e1000e drm ptp pps_core video
  [79849.958983] CPU: 0 PID: 14689 Comm: Xorg Tainted: GW   
4.2.0-11-generic #13-Ubuntu
  [79849.958983] Hardware name: FUJITSU ESPRIMO E920/D3222-A1, BIOS V4.6.5.4 
R1.34.0 for D3222-A1x 01/08/2015
  [79849.958985]  c0232ab0 88030edef538 817b0cc5 

  [79849.958986]  88030edef588 88030edef578 81076536 
88030edef5a8
  [79849.958986]  88030edef610 88030a600800 0001 
88030a600b50
  [79849.958987] Call Trace:
  [79849.958991]  [] dump_stack+0x45/0x57
  [79849.958994]  [] warn_slowpath_common+0x86/0xc0
  [79849.958995]  [] warn_slowpath_fmt+0x46/0x50
  [79849.959008]  [] ? intel_pipe_config_compare+0xa67/0xc60 
[i915]
  [79849.959015]  [] check_crtc_state+0x2c5/0x440 [i915]
  [79849.959024]  [] intel_modeset_check_state+0x20e/0x6b0 
[i915]
  [79849.959032]  [] intel_crtc_set_config+0x4c7/0x580 [i915]
  [79849.959042]  [] drm_mode_set_config_internal+0x66/0x100 
[drm]
  [79849.959045]  [] restore_fbdev_mode+0xc2/0xf0 
[drm_kms_helper]
  [79849.959048]  [] 
drm_fb_helper_restore_fbdev_mode_unlocked+0x29/0x70 [drm_kms_helper]
  [79849.959050]  [] drm_fb_helper_set_par+0x22/0x40 
[drm_kms_helper]
  [79849.959060]  [] intel_fbdev_set_par+0x1a/0x60 [i915]
  [79849.959062]  [] ? ttwu_do_activate.constprop.89+0x5d/0x70
  [79849.959064]  [] fb_set_var+0x238/0x460
  [79849.959066]  [] ? do_sys_poll+0x127/0x5a0
  [79849.959068]  [] fbcon_blank+0x2e9/0x330
  [79849.959070]  [] ? check_preempt_wakeup+0x193/0x220
  [79849.959071]  [] do_unblank_screen+0xd3/0x1a0
  [79849.959073]  [] vt_ioctl+0x4fb/0x12c0
  [79849.959074]  [] ? default_wake_function+0x12/0x20
  [79849.959076]  [] ? autoremove_wake_function+0x16/0x40
  [79849.959078]  [] tty_ioctl+0x3cc/0xbb0
  [79849.959079]  [] ? __wake_up+0x48/0x60
  [79849.959080]  [] ? wake_nocb_leader+0x4d/0x50
  [79849.959081]  [] ? __call_rcu_nocb_enqueue+0xcd/0xd0
  [79849.959083]  [] do_vfs_ioctl+0x285/0x470
  [79849.959084]  [] ? mntput+0x24/0x40
  [79849.959085]  [] ? __fput+0x190/0x220
  [79849.959086]  [] SyS_ioctl+0x79/0x90
  [79849.959088]  [] entry_SYSCALL_64_fastpath+0x16/0x75
  [79849.959089] ---[ end trace c15f693470bdbc48 ]---
  [79849.959131] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in 
dpll_hw_state.wrpll (expected 0xb0210614, found 0x)
  [79849.959131] [ cut here ]

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-11-generic 4.2.0-11.13
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  

[Kernel-packages] [Bug 1547838] UdevDb.txt

[a1291762]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1547838/+attachment/4591813/+files/UdevDb.txt

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

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

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-49-generic 3.19.0-49.55~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  Uname: Linux 3.19.0-49-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Sat Feb 20 21:23:29 2016
  InstallationDate: Installed on 2015-12-31 (50 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.19.0-49-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=0cffa533-89ec-44d8-b5f9-6efe69c1b955
  InstallationDate: Installed on 2015-12-31 (67 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: Hewlett-Packard HP EliteBook 8530w
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-49-generic 
root=UUID=d4c67c71-679c-4b9d-8e20-848149e8aedf ro debug ignore_loglevel 
crashkernel=384M-:128M
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-49-generic N/A
   linux-backports-modules-3.19.0-49-generic  N/A
   linux-firmware 1.127.20
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.19.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 06/08/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PDV Ver. F.12
  dmi.board.name: 30E7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 90.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PDVVer.F.12:bd06/08/2010:svnHewlett-Packard:pnHPEliteBook8530w:pvrF.12:rvnHewlett-Packard:rn30E7:rvrKBCVersion90.27:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8530w
  dmi.product.version: F.12
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing 

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

[a1291762]

apport information

** Tags added: apport-collected

** Description changed:

  This is a rather old USB ethernet adapter. It worked fine for me with
  older distributions (including Ubuntu 10.04). I noticed it causing
  problems after upgrading to 14.04 and stopped using it as a result
  (since I needed reliable USB ethernet for work). I was also not
  completely sure if it was this device causing the issue or interplay
  between this device and a number of other networking USB devices that
  were used at work.
  
  I'd like to use this ethernet adapter at home but the machine is running
  Ubuntu 14.04 and the issue persists.
  
  I have collected some information that might help. I'm happy to try more
  things to collect information if that will help.
  
  I'm running Ubuntu 14.04 server 64-bit. I just rebooted so I'm running
  the latest updates.
  
  I was told to run ubuntu-bug linux but I'm not sure how much useful
  stuff is included in that. I'm including the kernel log which has some
  bad stuff happening in it. Not sure if it got the system-freezing oops
  or just the errors leading up to that.
  
  It feels like a bug in the driver that corrupts memory because I see
  issues with network-related things (eg. a ping crashed, but the next
  ping didn't), leading to a full-system freeze.
  
  This machine has been happily running Ubuntu for a looong time (though
  it was only recently upgraded to Ubuntu 14.04, previously it had been
  running 10.04). I have not had stability issues with the machine but
  plugging in the USB Ethernet reliably makes it freeze within minutes.
  The symptoms also match what I saw on my machine at work.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-49-generic 3.19.0-49.55~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  Uname: Linux 3.19.0-49-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Sat Feb 20 21:23:29 2016
  InstallationDate: Installed on 2015-12-31 (50 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.19.0-49-generic.
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.14.1-0ubuntu3.19
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
+ CRDA: Error: [Errno 2] No such file or directory
+ Card0.Amixer.info: Error: [Errno 2] No such file or directory
+ Card0.Amixer.values: Error: [Errno 2] No such file or directory
+ DistroRelease: Ubuntu 14.04
+ HibernationDevice: RESUME=UUID=0cffa533-89ec-44d8-b5f9-6efe69c1b955
+ InstallationDate: Installed on 2015-12-31 (67 days ago)
+ InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
+ MachineType: Hewlett-Packard HP EliteBook 8530w
+ Package: linux (not installed)
+ ProcFB: 0 nouveaufb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-49-generic 
root=UUID=d4c67c71-679c-4b9d-8e20-848149e8aedf ro debug ignore_loglevel 
crashkernel=384M-:128M
+ ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
+ RelatedPackageVersions:
+  linux-restricted-modules-3.19.0-49-generic N/A
+  linux-backports-modules-3.19.0-49-generic  N/A
+  linux-firmware 1.127.20
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags:  trusty
+ Uname: Linux 3.19.0-49-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ WifiSyslog:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 06/08/2010
+ dmi.bios.vendor: Hewlett-Packard
+ dmi.bios.version: 68PDV Ver. F.12
+ dmi.board.name: 30E7
+ dmi.board.vendor: Hewlett-Packard
+ dmi.board.version: KBC Version 90.27
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Hewlett-Packard
+ dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PDVVer.F.12:bd06/08/2010:svnHewlett-Packard:pnHPEliteBook8530w:pvrF.12:rvnHewlett-Packard:rn30E7:rvrKBCVersion90.27:cvnHewlett-Packard:ct10:cvr:
+ dmi.product.name: HP EliteBook 8530w
+ dmi.product.version: F.12
+ dmi.sys.vendor: Hewlett-Packard

** Attachment added: "AlsaDevices.txt"
   
https://bugs.launchpad.net/bugs/1547838/+attachment/4591799/+files/AlsaDevices.txt

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

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a rather old USB ethernet adapter. It 

[Kernel-packages] [Bug 1547838] Lspci.txt

[a1291762]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1547838/+attachment/4591805/+files/Lspci.txt

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

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

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-49-generic 3.19.0-49.55~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  Uname: Linux 3.19.0-49-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Sat Feb 20 21:23:29 2016
  InstallationDate: Installed on 2015-12-31 (50 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.19.0-49-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=0cffa533-89ec-44d8-b5f9-6efe69c1b955
  InstallationDate: Installed on 2015-12-31 (67 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: Hewlett-Packard HP EliteBook 8530w
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-49-generic 
root=UUID=d4c67c71-679c-4b9d-8e20-848149e8aedf ro debug ignore_loglevel 
crashkernel=384M-:128M
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-49-generic N/A
   linux-backports-modules-3.19.0-49-generic  N/A
   linux-firmware 1.127.20
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.19.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 06/08/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PDV Ver. F.12
  dmi.board.name: 30E7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 90.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PDVVer.F.12:bd06/08/2010:svnHewlett-Packard:pnHPEliteBook8530w:pvrF.12:rvnHewlett-Packard:rn30E7:rvrKBCVersion90.27:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8530w
  dmi.product.version: F.12
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing 

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

[a1291762]

It seems this is a known issue...
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/997020

I have set w3m as the text-mode browser (it was already installed) and
run apport-collect. It wants to upload nearly 600K, quite a bit more
than the other command gave.

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

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

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-49-generic 3.19.0-49.55~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  Uname: Linux 3.19.0-49-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Sat Feb 20 21:23:29 2016
  InstallationDate: Installed on 2015-12-31 (50 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.19.0-49-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=0cffa533-89ec-44d8-b5f9-6efe69c1b955
  InstallationDate: Installed on 2015-12-31 (67 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: Hewlett-Packard HP EliteBook 8530w
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-49-generic 
root=UUID=d4c67c71-679c-4b9d-8e20-848149e8aedf ro debug ignore_loglevel 
crashkernel=384M-:128M
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-49-generic N/A
   linux-backports-modules-3.19.0-49-generic  N/A
   linux-firmware 1.127.20
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.19.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 06/08/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PDV Ver. F.12
  dmi.board.name: 30E7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 90.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PDVVer.F.12:bd06/08/2010:svnHewlett-Packard:pnHPEliteBook8530w:pvrF.12:rvnHewlett-Packard:rn30E7:rvrKBCVersion90.27:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8530w
  dmi.product.version: F.12
  dmi.sys.vendor: Hewlett-Packard

To 

[Kernel-packages] [Bug 1547838] ProcEnviron.txt

[a1291762]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1547838/+attachment/4591809/+files/ProcEnviron.txt

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

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

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-49-generic 3.19.0-49.55~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  Uname: Linux 3.19.0-49-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Sat Feb 20 21:23:29 2016
  InstallationDate: Installed on 2015-12-31 (50 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.19.0-49-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=0cffa533-89ec-44d8-b5f9-6efe69c1b955
  InstallationDate: Installed on 2015-12-31 (67 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: Hewlett-Packard HP EliteBook 8530w
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-49-generic 
root=UUID=d4c67c71-679c-4b9d-8e20-848149e8aedf ro debug ignore_loglevel 
crashkernel=384M-:128M
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-49-generic N/A
   linux-backports-modules-3.19.0-49-generic  N/A
   linux-firmware 1.127.20
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.19.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 06/08/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PDV Ver. F.12
  dmi.board.name: 30E7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 90.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PDVVer.F.12:bd06/08/2010:svnHewlett-Packard:pnHPEliteBook8530w:pvrF.12:rvnHewlett-Packard:rn30E7:rvrKBCVersion90.27:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8530w
  dmi.product.version: F.12
  dmi.sys.vendor: Hewlett-Packard

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

-- 

[Kernel-packages] [Bug 1547838] PciMultimedia.txt

[a1291762]

apport information

** Attachment added: "PciMultimedia.txt"
   
https://bugs.launchpad.net/bugs/1547838/+attachment/4591807/+files/PciMultimedia.txt

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

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

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-49-generic 3.19.0-49.55~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  Uname: Linux 3.19.0-49-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Sat Feb 20 21:23:29 2016
  InstallationDate: Installed on 2015-12-31 (50 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.19.0-49-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=0cffa533-89ec-44d8-b5f9-6efe69c1b955
  InstallationDate: Installed on 2015-12-31 (67 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: Hewlett-Packard HP EliteBook 8530w
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-49-generic 
root=UUID=d4c67c71-679c-4b9d-8e20-848149e8aedf ro debug ignore_loglevel 
crashkernel=384M-:128M
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-49-generic N/A
   linux-backports-modules-3.19.0-49-generic  N/A
   linux-firmware 1.127.20
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.19.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 06/08/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PDV Ver. F.12
  dmi.board.name: 30E7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 90.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PDVVer.F.12:bd06/08/2010:svnHewlett-Packard:pnHPEliteBook8530w:pvrF.12:rvnHewlett-Packard:rn30E7:rvrKBCVersion90.27:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8530w
  dmi.product.version: F.12
  dmi.sys.vendor: Hewlett-Packard

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

[Kernel-packages] [Bug 1530171] Re: [Regression] Thinkpad dock: External monitors not recognized after 15.04 upgrade

[Robert Schetterer]

I am tested wily ,xenial, kubuntu, kernels 4.2 , 4.4 on brand new thinkpad 
t450s with thinkpad pro dock 90w.
The laptop and the dock has latest fimware !
Intel graphics driver is at latest state too.
Also tested latest 4.5 drm intel nightly. All external displays work  always 
when directly attached to the laptop.
But with laptop docked, external displays are only running after boot, but fail 
when wake up from sleep mode configured in kde
closing lid. This is a very common user powersetting an is awaited to work. 
Most of the times external displays could reconfigured i.e by script produced 
from arandr ( gtk gui wrapper for xrandr ). But a universal script workaround 
seems complicated with acpi, systemd in userland for all thinkable combinations 
of possible displays ( up to three include lcd on laptop are possible).

It should simply work out of the box.

Additional info i invested a lot of time in kernel logs and trying grub start 
parameter, cause there were other ugly bug with intel 915 driver ( pci lied SDE 
etc fixed in 4.5 ) , there is also a point in the bios configure 10s to wait 
for notice external displays. Also 2014 the dock had a bug ( also on windows 
with external displays which was fixed by new firmware ).
It seems simply the dock does not pass external displays connected after laptop 
and external displays got sleep mode after wake up, prove is made by 
plug/unplugging external display and reenable it in kde. Also open windows were 
only reconstructed
after awake with kernel 4.4 /4.5 after manual reenable, with kernel 4.2 most of 
the time also plasma crashes and simply undock
crash x-server too. Any idea what to look next ?
Regards

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

Title:
  [Regression] Thinkpad dock: External monitors not recognized after
  15.04 upgrade

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  External monitors are not recognized in display settings when plugged
  into any dock port.

  They *are* recognized after a reboot (not after logout).
  After plugging out and the in again they are not recognized.

  A monitor plugged in and out of the non-dock VGA is recognized instantly.
  After plugging in or out of the non-dock VGA, monitors plugged to dock ports 
are recognized (which serves as a crazy workaround for me now)
  (update: this works sometimes, sometimes not).

  Everything used to work with 14.10, but stopped with 15.04.

  A recent test with 1510 live CD did not fix this.
  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: 2016-01-04 01:09:49,649 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroRelease: Ubuntu 15.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:501e]
  InstallationDate: Installed on 2015-03-05 (311 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: LENOVO 20AUS00N00
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-43-generic 
root=UUID=82cd15d9-7510-4d2f-a698-28fa51216e13 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10
  Tags:  vivid ubuntu compiz-0.9
  Uname: Linux 3.19.0-43-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2016-01-04 (6 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare saned sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J4ET67WW(1.67)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AUS00N00
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ4ET67WW(1.67):bd08/13/2014:svnLENOVO:pn20AUS00N00:pvrThinkPadL540:rvnLENOVO:rn20AUS00N00:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AUS00N00
  dmi.product.version: ThinkPad L540
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.1+15.04.20150922-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1