date:20160112

Shuhao, if the issue is confirmed on the latest mainline kernel (4.4)
then that is enough to mark it back to Confirmed as noted in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521245/comments/7
.

Given that you are having different results on different hardware, the
difference is due to either hardware failure, or the drivers are
different for the two sets of hardware, causing different outcomes for
the same device.

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

Title:
  Kinect Device keeps on disconnecting and reconnecting every two
  seconds

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an original xbox 360 kinect and when I try to use it with wily,
  it seems to keeps connecting and reconnecting. This does not occur on
  15.04 on my other machine.

  Sample log:

  Nov 30 10:57:16 thinkpadt420 kernel: [ 2746.676018] usb 4-1.2.2: new 
high-speed USB device number 61 using ehci-pci
  Nov 30 10:57:16 thinkpadt420 kernel: [ 2746.771890] usb 4-1.2.2: New USB 
device found, idVendor=045e, idProduct=02ae
  Nov 30 10:57:16 thinkpadt420 kernel: [ 2746.771900] usb 4-1.2.2: New USB 
device strings: Mfr=2, Product=1, SerialNumber=3
  Nov 30 10:57:16 thinkpadt420 kernel: [ 2746.771905] usb 4-1.2.2: Product: 
Xbox NUI Camera
  Nov 30 10:57:16 thinkpadt420 kernel: [ 2746.771910] usb 4-1.2.2: 
Manufacturer: Microsoft
  Nov 30 10:57:16 thinkpadt420 kernel: [ 2746.771914] usb 4-1.2.2: 
SerialNumber: 
  Nov 30 10:57:16 thinkpadt420 kernel: [ 2746.772645] gspca_main: kinect-2.14.0 
probing 045e:02ae
  Nov 30 10:57:16 thinkpadt420 mtp-probe: checking bus 4, device 61: 
"/sys/devices/pci:00/:00:1d.0/usb4/4-1/4-1.2/4-1.2.2"
  Nov 30 10:57:16 thinkpadt420 mtp-probe: bus: 4, device: 61 was not an MTP 
device
  Nov 30 10:57:17 thinkpadt420 kernel: [ 2747.205869] usb 4-1.2: USB 
disconnect, device number 59
  Nov 30 10:57:17 thinkpadt420 kernel: [ 2747.205880] usb 4-1.2.1: USB 
disconnect, device number 60
  Nov 30 10:57:17 thinkpadt420 kernel: [ 2747.206406] usb 4-1.2.2: USB 
disconnect, device number 61
  Nov 30 10:57:17 thinkpadt420 kernel: [ 2747.816793] usb 4-1.2: new high-speed 
USB device number 62 using ehci-pci
  Nov 30 10:57:18 thinkpadt420 kernel: [ 2747.909585] usb 4-1.2: New USB device 
found, idVendor=045e, idProduct=02c2
  Nov 30 10:57:18 thinkpadt420 kernel: [ 2747.909595] usb 4-1.2: New USB device 
strings: Mfr=0, Product=0, SerialNumber=0
  Nov 30 10:57:18 thinkpadt420 kernel: [ 2747.910267] hub 4-1.2:1.0: USB hub 
found
  Nov 30 10:57:18 thinkpadt420 kernel: [ 2747.910358] hub 4-1.2:1.0: 2 ports 
detected
  Nov 30 10:57:19 thinkpadt420 kernel: [ 2749.041712] usb 4-1.2.1: new 
high-speed USB device number 63 using ehci-pci
  Nov 30 10:57:19 thinkpadt420 kernel: [ 2749.136571] usb 4-1.2.1: New USB 
device found, idVendor=045e, idProduct=02ad
  Nov 30 10:57:19 thinkpadt420 kernel: [ 2749.136581] usb 4-1.2.1: New USB 
device strings: Mfr=1, Product=2, SerialNumber=3
  Nov 30 10:57:19 thinkpadt420 kernel: [ 2749.136586] usb 4-1.2.1: Product: 
Xbox Kinect Audio, © 2011 Microsoft Corporation. All rights reserved.
  Nov 30 10:57:19 thinkpadt420 kernel: [ 2749.136591] usb 4-1.2.1: 
Manufacturer: Microsoft
  Nov 30 10:57:19 thinkpadt420 kernel: [ 2749.136595] usb 4-1.2.1: 
SerialNumber: B70777100842334B
  Nov 30 10:57:19 thinkpadt420 mtp-probe: checking bus 4, device 63: 
"/sys/devices/pci:00/:00:1d.0/usb4/4-1/4-1.2/4-1.2.1"
  Nov 30 10:57:19 thinkpadt420 mtp-probe: bus: 4, device: 63 was not an MTP 
device

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   shuhao 1666 F...m pulseaudio
   /dev/snd/controlC0:  shuhao 1666 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Nov 30 10:53:22 2015
  HibernationDevice: RESUME=UUID=c55683f4-2e8a-4ea2-961f-22cc50468a0c
  InstallationDate: Installed on 2015-11-30 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 4180J4C
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-18-generic.efi.signed 
root=/dev/mapper/xubuntu--vg-root ro noprompt quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.2
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 0

[Kernel-packages] [Bug 1481266] Re: Two finger zoom / pinch and 4-finger gesture does no work on MSFT0001:00 06CB:75BD touchpad

jeremy, 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.

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

Title:
  Two finger zoom / pinch and 4-finger gesture does no work on
  MSFT0001:00 06CB:75BD touchpad

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  CID: 201408-15450 Dell Inspiron 7548

  The 2-finger zoom / pinch and 4-finger tapping gesture does not work
  on this system.

  The touchpad name from xinput is: MSFT0001:00 06CB:75BD

  (BTW, three finger double tap gesture works fine)

  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.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug  4 05:37:13 2015
  InstallationDate: Installed on 2015-08-03 (1 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.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1587 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1587 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=222354f0-98bb-407d-9716-52624f680341
  InstallationDate: Installed on 2015-08-03 (1 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Dell Inc. Inspiron 7548
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-45-generic 
root=UUID=5a44bb44-c9f3-4565-a5f1-b6672d5bdc08 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-45-generic N/A
   linux-backports-modules-3.16.0-45-generic  N/A
   linux-firmware 1.127.14
  Tags:  trusty
  Uname: Linux 3.16.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/19/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd11/19/2014:svnDellInc.:pnInspiron7548:pvrA00:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 7548
  dmi.product.version: A00
  dmi.sys.vendor: Dell Inc.

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

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

Title:
  banshee stops respondiing during media import

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

Bug description:
  Trying to import media to banshee in ubuntu 16.04 freezes banshee.
  Import works fine in rhythmbox. Problem only with banshee

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-5-generic 4.3.0-5.16
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  krishnan   1972 F pulseaudio
   /dev/snd/controlC0:  krishnan   1972 F pulseaudio
  Date: Wed Jan 13 10:20:16 2016
  HibernationDevice: RESUME=UUID=1f4f89ff-6e3c-4610-8450-a25509f5b5c5
  InstallationDate: Installed on 2015-12-26 (17 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  MachineType: LENOVO INVALID
  ProcFB:
   0 radeondrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-5-generic.efi.signed 
root=UUID=0bf37a84-dc7d-4bd4-999a-f8df2baffc39 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-5-generic N/A
   linux-backports-modules-4.3.0-5-generic  N/A
   linux-firmware   1.155
  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: 04/23/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83CN12WW(V1.01)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo G505s
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G505s
  dmi.modalias: 
dmi:bvnLENOVO:bvr83CN12WW(V1.01):bd04/23/2013:svnLENOVO:pnINVALID:pvrLenovoG505s:rvnLENOVO:rnLenovoG505s:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG505s:
  dmi.product.name: INVALID
  dmi.product.version: Lenovo G505s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1533480/+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 1533480] [NEW] banshee stops respondiing during media import

2016-01-12 Thread krishnan sampath

Public bug reported:

Trying to import media to banshee in ubuntu 16.04 freezes banshee.
Import works fine in rhythmbox. Problem only with banshee

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.3.0-5-generic 4.3.0-5.16
ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
Uname: Linux 4.3.0-5-generic x86_64
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  krishnan   1972 F pulseaudio
 /dev/snd/controlC0:  krishnan   1972 F pulseaudio
Date: Wed Jan 13 10:20:16 2016
HibernationDevice: RESUME=UUID=1f4f89ff-6e3c-4610-8450-a25509f5b5c5
InstallationDate: Installed on 2015-12-26 (17 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
MachineType: LENOVO INVALID
ProcFB:
 0 radeondrmfb
 1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-5-generic.efi.signed 
root=UUID=0bf37a84-dc7d-4bd4-999a-f8df2baffc39 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.3.0-5-generic N/A
 linux-backports-modules-4.3.0-5-generic  N/A
 linux-firmware   1.155
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: 04/23/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 83CN12WW(V1.01)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo G505s
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G505s
dmi.modalias: 
dmi:bvnLENOVO:bvr83CN12WW(V1.01):bd04/23/2013:svnLENOVO:pnINVALID:pvrLenovoG505s:rvnLENOVO:rnLenovoG505s:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG505s:
dmi.product.name: INVALID
dmi.product.version: Lenovo G505s
dmi.sys.vendor: LENOVO

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

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


** Tags: amd64 apport-bug xenial

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

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

Title:
  banshee stops respondiing during media import

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

Bug description:
  Trying to import media to banshee in ubuntu 16.04 freezes banshee.
  Import works fine in rhythmbox. Problem only with banshee

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-5-generic 4.3.0-5.16
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  krishnan   1972 F pulseaudio
   /dev/snd/controlC0:  krishnan   1972 F pulseaudio
  Date: Wed Jan 13 10:20:16 2016
  HibernationDevice: RESUME=UUID=1f4f89ff-6e3c-4610-8450-a25509f5b5c5
  InstallationDate: Installed on 2015-12-26 (17 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  MachineType: LENOVO INVALID
  ProcFB:
   0 radeondrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-5-generic.efi.signed 
root=UUID=0bf37a84-dc7d-4bd4-999a-f8df2baffc39 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-5-generic N/A
   linux-backports-modules-4.3.0-5-generic  N/A
   linux-firmware   1.155
  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: 04/23/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83CN12WW(V1.01)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo G505s
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G505s
  dmi.modalias: 
dmi:bvnLENOVO:bvr83CN12WW(V1.01):bd04/23/2013:svnLENOVO:pnINVALID:pvrLenovoG505s:rvnLENOVO:rnLenovoG505s:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG505s:
  dmi.product.name: INVALID
  dmi.product.version: Lenovo G505s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1533480/+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 1521245] Re: Kinect Device keeps on disconnecting and reconnecting every two seconds

2016-01-12 Thread Shuhao

I'm going to leave this as incomplete as I cannot find a kernel version
where this doesn't show up. There's only one computer that I have that
doesn't experience this issue and it is on 15.04.

At this point I'm suspecting some system service fiddling with the usb
system? Consider how regular the intervals are. Is there a list of the
services somewhere that I can look at and then check individually?

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

Title:
  Kinect Device keeps on disconnecting and reconnecting every two
  seconds

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an original xbox 360 kinect and when I try to use it with wily,
  it seems to keeps connecting and reconnecting. This does not occur on
  15.04 on my other machine.

  Sample log:

  Nov 30 10:57:16 thinkpadt420 kernel: [ 2746.676018] usb 4-1.2.2: new 
high-speed USB device number 61 using ehci-pci
  Nov 30 10:57:16 thinkpadt420 kernel: [ 2746.771890] usb 4-1.2.2: New USB 
device found, idVendor=045e, idProduct=02ae
  Nov 30 10:57:16 thinkpadt420 kernel: [ 2746.771900] usb 4-1.2.2: New USB 
device strings: Mfr=2, Product=1, SerialNumber=3
  Nov 30 10:57:16 thinkpadt420 kernel: [ 2746.771905] usb 4-1.2.2: Product: 
Xbox NUI Camera
  Nov 30 10:57:16 thinkpadt420 kernel: [ 2746.771910] usb 4-1.2.2: 
Manufacturer: Microsoft
  Nov 30 10:57:16 thinkpadt420 kernel: [ 2746.771914] usb 4-1.2.2: 
SerialNumber: 
  Nov 30 10:57:16 thinkpadt420 kernel: [ 2746.772645] gspca_main: kinect-2.14.0 
probing 045e:02ae
  Nov 30 10:57:16 thinkpadt420 mtp-probe: checking bus 4, device 61: 
"/sys/devices/pci:00/:00:1d.0/usb4/4-1/4-1.2/4-1.2.2"
  Nov 30 10:57:16 thinkpadt420 mtp-probe: bus: 4, device: 61 was not an MTP 
device
  Nov 30 10:57:17 thinkpadt420 kernel: [ 2747.205869] usb 4-1.2: USB 
disconnect, device number 59
  Nov 30 10:57:17 thinkpadt420 kernel: [ 2747.205880] usb 4-1.2.1: USB 
disconnect, device number 60
  Nov 30 10:57:17 thinkpadt420 kernel: [ 2747.206406] usb 4-1.2.2: USB 
disconnect, device number 61
  Nov 30 10:57:17 thinkpadt420 kernel: [ 2747.816793] usb 4-1.2: new high-speed 
USB device number 62 using ehci-pci
  Nov 30 10:57:18 thinkpadt420 kernel: [ 2747.909585] usb 4-1.2: New USB device 
found, idVendor=045e, idProduct=02c2
  Nov 30 10:57:18 thinkpadt420 kernel: [ 2747.909595] usb 4-1.2: New USB device 
strings: Mfr=0, Product=0, SerialNumber=0
  Nov 30 10:57:18 thinkpadt420 kernel: [ 2747.910267] hub 4-1.2:1.0: USB hub 
found
  Nov 30 10:57:18 thinkpadt420 kernel: [ 2747.910358] hub 4-1.2:1.0: 2 ports 
detected
  Nov 30 10:57:19 thinkpadt420 kernel: [ 2749.041712] usb 4-1.2.1: new 
high-speed USB device number 63 using ehci-pci
  Nov 30 10:57:19 thinkpadt420 kernel: [ 2749.136571] usb 4-1.2.1: New USB 
device found, idVendor=045e, idProduct=02ad
  Nov 30 10:57:19 thinkpadt420 kernel: [ 2749.136581] usb 4-1.2.1: New USB 
device strings: Mfr=1, Product=2, SerialNumber=3
  Nov 30 10:57:19 thinkpadt420 kernel: [ 2749.136586] usb 4-1.2.1: Product: 
Xbox Kinect Audio, © 2011 Microsoft Corporation. All rights reserved.
  Nov 30 10:57:19 thinkpadt420 kernel: [ 2749.136591] usb 4-1.2.1: 
Manufacturer: Microsoft
  Nov 30 10:57:19 thinkpadt420 kernel: [ 2749.136595] usb 4-1.2.1: 
SerialNumber: B70777100842334B
  Nov 30 10:57:19 thinkpadt420 mtp-probe: checking bus 4, device 63: 
"/sys/devices/pci:00/:00:1d.0/usb4/4-1/4-1.2/4-1.2.1"
  Nov 30 10:57:19 thinkpadt420 mtp-probe: bus: 4, device: 63 was not an MTP 
device

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   shuhao 1666 F...m pulseaudio
   /dev/snd/controlC0:  shuhao 1666 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Nov 30 10:53:22 2015
  HibernationDevice: RESUME=UUID=c55683f4-2e8a-4ea2-961f-22cc50468a0c
  InstallationDate: Installed on 2015-11-30 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 4180J4C
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-18-generic.efi.signed 
root=/dev/mapper/xubuntu--vg-root ro noprompt quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.2
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2013
  dmi.bios.vendor

[Kernel-packages] [Bug 1515920] Re: Touchpad detected as mouse

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

Title:
  Touchpad detected as mouse

Status in linux package in Ubuntu:
  Expired

Bug description:
  I'm following the bug reporting documentation here:

  
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all.

  I just bought a new computer, and installed ubuntu.

  Unfortunately the touchpad is detected as a mouse and I'm not sure how
  I can find the brand of the touchpad device.

  I'm attaching some logs that should helpful, let me know anything else
  I can add.

  ( I'm on Ubuntu 15.10 )
  --- 
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  domy   1641 F pulseaudio
   /dev/snd/controlC1:  domy   1641 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=da3d19ac-8610-4f3a-865f-5da55088fe06
  InstallationDate: Installed on 2015-11-13 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: DELL XPS13-8808
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=90d57801-3d9b-4faf-aae7-c9abe467e2b3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.2
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/30/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.6.5
  dmi.board.name: XPS13-8808
  dmi.board.vendor: DELL
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd04/30/2015:svnDELL:pnXPS13-8808:pvr:rvnDELL:rnXPS13-8808:rvr:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: XPS13-8808
  dmi.sys.vendor: DELL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1515920/+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 1481266] Re: Two finger zoom / pinch and 4-finger gesture does no work on MSFT0001:00 06CB:75BD touchpad

2016-01-12 Thread jeremy

I am still having the same problem here is my output to confirm the bios
has been updated.

itsalwaysbroken:~/projects$ sudo dmidecode -s bios-version && sudo dmidecode -s 
bios-release-date
A05
07/20/2015


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

Title:
  Two finger zoom / pinch and 4-finger gesture does no work on
  MSFT0001:00 06CB:75BD touchpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201408-15450 Dell Inspiron 7548

  The 2-finger zoom / pinch and 4-finger tapping gesture does not work
  on this system.

  The touchpad name from xinput is: MSFT0001:00 06CB:75BD

  (BTW, three finger double tap gesture works fine)

  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.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug  4 05:37:13 2015
  InstallationDate: Installed on 2015-08-03 (1 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.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1587 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1587 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=222354f0-98bb-407d-9716-52624f680341
  InstallationDate: Installed on 2015-08-03 (1 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Dell Inc. Inspiron 7548
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-45-generic 
root=UUID=5a44bb44-c9f3-4565-a5f1-b6672d5bdc08 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-45-generic N/A
   linux-backports-modules-3.16.0-45-generic  N/A
   linux-firmware 1.127.14
  Tags:  trusty
  Uname: Linux 3.16.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/19/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd11/19/2014:svnDellInc.:pnInspiron7548:pvrA00:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 7548
  dmi.product.version: A00
  dmi.sys.vendor: Dell Inc.

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

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

apport-collect 1533461

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

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

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

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

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

Title:
  No headset microphone is detected in sound settings on a Dell laptop

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Steps:

  1. Plug in a headset to the headset audio jack
  2. Go to Sound settings -> Input tab and check if the headset mic is listed

  This is bug is for tracking purposes only, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1533461/+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 1533461] [NEW] No headset microphone is detected in sound settings on a Dell laptop

2016-01-12 Thread Hui Wang

Public bug reported:

Steps:

1. Plug in a headset to the headset audio jack
2. Go to Sound settings -> Input tab and check if the headset mic is listed

This is bug is for tracking purposes only, please do not triage.

** Affects: hwe-next
 Importance: High
 Assignee: Hui Wang (hui.wang)
 Status: New

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Hui Wang (hui.wang)
 Status: New

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

** Changed in: hwe-next
   Importance: Undecided => High

** Changed in: hwe-next
 Assignee: (unassigned) => Hui Wang (hui.wang)

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

Title:
  No headset microphone is detected in sound settings on a Dell laptop

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Steps:

  1. Plug in a headset to the headset audio jack
  2. Go to Sound settings -> Input tab and check if the headset mic is listed

  This is bug is for tracking purposes only, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1533461/+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 1153618] Re: Support Realtek RTS5227 card reader

2016-01-12 Thread Alberto Quattrini Li

The problem the the Realtek RTS5227 card reader appears in the last
kernel available on Ubuntu 14.04 (kernel 3.16.0-57), as pointed out by
Steven Ellis, with basically the same output from dmesg and lspci as
Steven Ellis.

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

Title:
  Support Realtek RTS5227 card reader

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Quantal:
  Fix Released
Status in linux source package in Raring:
  Fix Released
Status in linux package in Fedora:
  Unknown

Bug description:
  Support of Realtek RTS5227 card reader is currently missing in the
  kernel, though the support is already in upstream, we need to backport
  it from upstream to enable this device.

  03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd.
  Device [10ec:5227] (rev 01)

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

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

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

2016-01-12 Thread Dexuan Cui

Sorry, I was moved to another project so I couldn't debug the issue with
full-time.

Hi Joshua R. Poulson (jrp),  can you please find more resource for this
bug?

My previous debugging made me think the root cause might be in the
storvsc driver code, but unluckily I'm not an expert in that area. :-(

Recently there are some storvsc fixes posted in LKML and some of them haven't 
been accepted in the upstream kernel.
I think I can re-try the bug when all of the recent fixes are in the upstream 
to see if the situation will change.

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1532975] Re: Screen periodically goes black for a second

boukeas, thank you for reporting this and helping make Ubuntu better.

As per
http://h20564.www2.hp.com/hpsc/swd/public/readIndex?sp4ts.oid=6943803&swLangOid=8&swEnvOid=4192
an update to your computer's buggy and outdated BIOS is available
(1.16). 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. As well, 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-1.16

** Package changed: xorg (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/1532975

Title:
  Screen periodically goes black for a second

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am using Ubuntu 14.04.3 on a HP ProBook 430 G2/2246. It is often the
  case that my screen goes black for a second and then recovers. It is
  my impression that this only happens when the computer has been idle
  -- even for a very short time -- so I have disabled screen locking and
  dimming and I have also removed the gnome-screensaver package, yet the
  problem persists.

  I took a look at /var/log/syslog and discovered an identical set of
  error messages (dump traces, mainly) for every time this happens. I am
  attaching a file with this set of messages.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
  Uname: Linux 3.16.0-57-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  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
  Date: Tue Jan 12 00:02:52 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:2246]
  InstallationDate: Installed on 2015-04-20 (266 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Hewlett-Packard HP ProBook 430 G2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-57-generic 
root=UUID=3a069045-f0b3-46ac-b25f-057beaa48b7e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M74 Ver. 01.04
  dmi.board.name: 2246
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 67.22
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM74Ver.01.04:bd08/16/2014:svnHewlett-Packard:pnHPProBook430G2:pvrA3008CD10003:rvnHewlett-Packard:rn2246:rvrKBCVersion67.22:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 430 G2
  dmi.product.version: A3008CD10003
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1.01
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Dec 31 15:19:11 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   14425 
   vendor SEC
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

To manage notifications about this bug

[Kernel-packages] [Bug 1532975] [NEW] Screen periodically goes black for a second

You have been subscribed to a public bug:

I am using Ubuntu 14.04.3 on a HP ProBook 430 G2/2246. It is often the
case that my screen goes black for a second and then recovers. It is my
impression that this only happens when the computer has been idle --
even for a very short time -- so I have disabled screen locking and
dimming and I have also removed the gnome-screensaver package, yet the
problem persists.

I took a look at /var/log/syslog and discovered an identical set of
error messages (dump traces, mainly) for every time this happens. I am
attaching a file with this set of messages.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
Uname: Linux 3.16.0-57-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.19
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
Date: Tue Jan 12 00:02:52 2016
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:2246]
InstallationDate: Installed on 2015-04-20 (266 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: Hewlett-Packard HP ProBook 430 G2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-57-generic 
root=UUID=3a069045-f0b3-46ac-b25f-057beaa48b7e ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/16/2014
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: M74 Ver. 01.04
dmi.board.name: 2246
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 67.22
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM74Ver.01.04:bd08/16/2014:svnHewlett-Packard:pnHPProBook430G2:pvrA3008CD10003:rvnHewlett-Packard:rn2246:rvrKBCVersion67.22:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 430 G2
dmi.product.version: A3008CD10003
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1.01
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Dec 31 15:19:11 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   14425 
 vendor SEC
xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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


** Tags: amd64 apport-bug bios-outdated-1.16 compiz-0.9 trusty ubuntu
-- 
Screen periodically goes black for a second
https://bugs.launchpad.net/bugs/1532975
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 1533323] Re: Linux kernel holds lost ethernet connections

Patrik Nilsson, thank you for reporting this and helping make Ubuntu
better.

As per http://us.acer.com/ac/en/US/content/drivers an update to your
computer's buggy and outdated BIOS is available (1.29). 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. As well, 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-1.29

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

Title:
  Linux kernel holds lost ethernet connections

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If a connection to a router is lost while you have active ethernet
  connections to hosts (on the Internet), networking can't be resumed
  before all connections are closed. Many software packages repeatedly
  try to resume their lost connections, which must lead to a human
  intervention to quit all software before the connection to the router
  is re-established.

  Seems as it is the kernel that prevents connections to the router, by
  holding lost connections.

  Even if you in disable networking by selecting "Enable Networking"
  from the drop down menu, and re-enable it, you can't get through to
  the router before all user software has quit and closed all
  connections holding the lost host connections.

  This bug has existed for a long time(=years), but I have never learnt
  what the error could be.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-43-generic 3.19.0-43.49
  ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-43-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrik 1870 F pulseaudio
   /dev/snd/controlC1:  patrik 1870 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 12 19:51:10 2016
  HibernationDevice: RESUME=UUID=541b29a6-2b6e-4caa-989c-9eb69dca7d9f
  InstallationDate: Installed on 2015-07-12 (184 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Acer Aspire V3-331
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-43-generic 
root=/dev/mapper/hostname--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-43-generic N/A
   linux-backports-modules-3.19.0-43-generic  N/A
   linux-firmware 1.143.7
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V3-331
  dmi.board.vendor: Acer
  dmi.board.version: V1.05
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd06/09/2014:svnAcer:pnAspireV3-331:pvrV1.05:rvnAcer:rnAspireV3-331:rvrV1.05:cvnAcer:ct10:cvrV1.05:
  dmi.product.name: Aspire V3-331
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533323/+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 1533221] Re: Issues with new Skylake hardware

Ian Booth, thank you for reporting this and helping make Ubuntu better.

Given attempting to deal with more than one issue in one report is unwieldy,
let this report focus on only the first issue mentioned:
"1. Intel HD graphics Booting with intel graphics enabled results in a lockup
loading lightdm or logging in results in the greeter screen appearing again."

Regarding the other issues mentioned, it will be most helpful to file a
new report, one report per issue. Please feel free to subscribe me to
them.

Focusing on the scope of this report, could you please both boot into a
Ubuntu kernel (not mainline/upstream), and configuration allowing you to
run apport-collect again?

Unfortunately, apport-collect'ing while booted into a mainline kernel
doesn't provide helpful information.

Thank you for your understanding.

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

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

** Summary changed:

- Issues with new Skylake hardware
+ Booting with intel graphics enabled results in a lockup

** Description changed:

- I have various hardware issues on a new Skylake laptop. The laptop has a
- Nvidia GTX730 graphics card which can be switched off via bumblebee or
- prime
-
- 1. Intel HD graphics
- Booting with intel graphics enabled results in a lockup loading lightdm or
logging in results in the greeter screen appearing again.
-
- 2. Intel 8260 wireless
- I have to run a recent mainline kernel (4.4 or similar) to get wireless.
-
- 3. nvidia card
- Trying to install wily from a USB stick results in a splash screen lock up
before it gets to the install screen. This appears related to the noveau
drivers. I have to use the graphics ppa to install the nvidia drivers. But it
is not an issue in the 3.9 kernel because to install what I have to do is:
- i. install vivid (everything works except wireless)
- ii. use wired network to install nvidia drivers
- iii. use wired network to upgrade to wily
- iv. use wired network to install mainline 4.4 kernel
-
- 4. Display brightness function keys
- These don't work. Other function keys do. The other keys show output in
acpi_listen but the brightness keys don't The settings applet can be used to
adjust brightness, as can writing a value to /proc/blah
-
- 5. lshw shows other unclaimed hardware eg I think fingerprint scanner?
- output attached.
- ---
- ApportVersion: 2.19.1-0ubuntu5
- Architecture: amd64
- CurrentDesktop: Unity
- DistroRelease: Ubuntu 15.10
- NonfreeKernelModules: nvidia_modeset nvidia
- Package: linux (not installed)
- Tags: wily
- Uname: Linux 4.4.0-040400-generic x86_64
- UnreportableReason: The running kernel is not an Ubuntu kernel
- UpgradeStatus: No upgrade log present (probably fresh install)
- UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
- _MarkForUpload: True
+ Booting with intel graphics enabled results in a lockup loading lightdm
+ or logging in results in the greeter screen appearing again. The laptop
+ has a Nvidia GTX730 graphics card which can be switched off via
+ bumblebee or prime.

** Attachment removed: "ProcEnviron.txt"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+attachment/4548584/+files/ProcEnviron.txt

** Attachment removed: "JournalErrors.txt"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+attachment/4548583/+files/JournalErrors.txt

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

Title:
Booting with intel graphics enabled results in a lockup

Status in linux package in Ubuntu:
Incomplete

Bug description:
Booting with intel graphics enabled results in a lockup loading
lightdm or logging in results in the greeter screen appearing again.
The laptop has a Nvidia GTX730 graphics card which can be switched off
via bumblebee or prime.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+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 1533009] Re: arm64: "unsupported RELA relocation"

2016-01-12 Thread Ming Lei

When I built 4.3.0-7-generic on arm64(mustang) Wily with the following
steps,

 fakeroot debian/rules clean
 fakeroot debian/rules binary-generic

by this compiler:

ubuntu@ubuntu:~$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/aarch64-linux-gnu/5/lto-wrapper
Target: aarch64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
5.2.1-22ubuntu2' --with-bugurl=file:///usr/share/doc/gcc-5/README.Bugs
--enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++
--prefix=/usr --program-suffix=-5 --enable-shared
--enable-linker-build-id --libexecdir=/usr/lib
--without-included-gettext --enable-threads=posix --libdir=/usr/lib
--enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-libquadmath --enable-plugin --with-system-zlib
--disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-5-arm64/jre
--enable-java-home
--with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-5-arm64
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-5-arm64
--with-arch-directory=aarch64
--with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-multiarch
--disable-werror --enable-checking=release --build=aarch64-linux-gnu
--host=aarch64-linux-gnu --target=aarch64-linux-gnu


the built image just works well:

  ubuntu@ubuntu:~$ uname -a
  Linux ubuntu 4.3.0-7-generic #18 SMP Tue Jan 12 10:19:24 EST 2016
  aarch64 aarch64 aarch64 GNU/Linux


But I can see the issue when booting a kernel from the following package[1]:

 http://launchpadlibrarian.net/230287220/linux-
image-4.3.0-5-generic_4.3.0-5.16_arm64.deb

It is a build environment issue instead of kernel issue, please see
comments from Ard Biesheuvel  [2]:

RELA #275 is the relocation against ADRP instructions, which GCC
should not emit anymore when -mcmodel=large is in effect.

Can you confirm that the modules have been rebuilt with this config as
well? Can you double check the GCC command line (with V=1) when doing
'make modules' to ensure that '-mcmodel=large' is being passed? Can
you check with 'readelf -r' which objects still contain
R_AARCH64_ADR_PREL_PG_HI21 relocations?

I have checked the gcc flag in my building environment, and '-mcmodel=large' is
passed, and CONFIG_ARM64_ERRATUM_843419 is enabled too.

I don't know how the image in [1] is built, so could anyone check the build
environment for this building?


[1] 
http://launchpadlibrarian.net/230287220/linux-image-4.3.0-5-generic_4.3.0-5.16_arm64.deb
[2] http://www.spinics.net/lists/arm-kernel/msg449991.html


On Tue, Jan 12, 2016 at 7:47 PM, Raghuram Kota
 wrote:
> ** Tags added: hs-arm64
>
> --
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1533009
>
> Title:
>   arm64: "unsupported RELA relocation"
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   linux-image-4.3.0-5-generic 4.3.0-5.16 arm64 fails to load modules
>   (and therefore boot). It emits messages like the following for each
>   attempted module load:
>
>   [2.156817] module libahci: unsupported RELA relocation: 275
>
>   This is reminiscent of LP: #1502946 - except that fix appears to still
>   be in-tact. What has changed, however, is the build environment. If I
>   rebuild the same kernel source in a wily chroot, it boots fine.
>
>   Marking "Confirmed" because Paulo Pisatti reported this to me, and I
>   reproduced.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533009/+subscriptions

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

Title:
  arm64: "unsupported RELA relocation"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  linux-image-4.3.0-5-generic 4.3.0-5.16 arm64 fails to load modules
  (and therefore boot). It emits messages like the following for each
  attempted module load:

  [2.156817] module libahci: unsupported RELA relocation: 275

  This is reminiscent of LP: #1502946 - except that fix appears to still
  be in-tact. What has changed, however, is the build environment. If I
  rebuild the same kernel source in a wily chroot, it boots fine.

  Marking "Confirmed" because Paulo Pisatti reported this to me, and I
  reproduced.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533009/+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 1533143] Re: "Regresion" Suspend to RAM doesn't work in Macbook Air

Tommy_CZ, thank you for reporting this and helping make Ubuntu better.

As per https://support.apple.com/en-us/HT201518 an update to your
computer's buggy and outdated BIOS is available (MBA41.0077.B12). 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. As well, 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-b12

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

Title:
  "Regresion" Suspend to RAM doesn't work in Macbook Air

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Suspend to RAM doesn't work in Macbook Air, the laptop doesn't go to sleep...
  It worked few kernels ago.

  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
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tomas  1433 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Jan 12 11:28:14 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=4fe32243-909c-4784-93b9-325d71ffcf4b
  InstallationDate: Installed on 2015-11-26 (46 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Apple Inc. MacBookAir4,2
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=8e519819-8ecd-465f-ae90-a80d67972566 ro rootflags=subvol=@ 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] Adresář nebo soubor neexistuje: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1533143/+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 1532942] Re: [EEH] Recursive fenced PHB during EEH recovery on Broadcom Shiner adapter

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

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

Title:
  [EEH] Recursive fenced PHB during EEH recovery on Broadcom Shiner
  adapter

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Recursive PHB error from EEH recovery on Shiner adapter

  ---uname output---
  Ubuntu 14.04.3 LTS (3.19.0-30)
   
  Machine Type = Firestone 

  ---Steps to Reproduce---
   When injecting EEH error (frozen PE) to BCM57800 on ubuntu 14.04.3, the EEH 
error is recovered automatically. However I saw recursive fenced PHB error 
during the recovery, which isn't the expected behaviour. After checking the 
ubuntu's kernel source repository, I found one patch, which as merged to 
powerpc/next branch recently, is missed as below. This bug is opened to 
tracking the backporting. Please help to mirror to Canonical accordingly, 
thanks!
   
  This bug was opened to track the backporting (as below) to ubuntu's distro. 
Please help mirrored to Cacinonical accordingly.

  https://git.kernel.org/cgit/linux/kernel/git/next/linux-
  next.git/commit/?id=353169acf1858bb2dc3f91475dafabce547de14c which
  reads "powerpc/eeh: Fix recursive fenced PHB on Broadcom shiner
  adapter"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532942/+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 1533043] Re: AUFS can hang up; Please update to v20160111

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

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

** Tags added: cherry-pick

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

Title:
  AUFS can hang up; Please update to v20160111

Status in linux package in Ubuntu:
  Triaged

Bug description:
  AUFS  can hang up (more precisely, produces unkillable processes) with some 
kernels that contain the commit 296291cdd1629c308114504b850dc343eabc278.
  - 14.04LTS:  
http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git/commit/?id=b8702f3cf9c06914476fb3206039131c2c3d8450
  - 15.04: 
http://kernel.ubuntu.com/git/ubuntu/ubuntu-vivid.git/commit/?id=6b08592b8acc677d5b9bb7986343fdd6e0ad3303
  - 15.10: 
http://kernel.ubuntu.com/git/ubuntu/ubuntu-wily.git/commit/?id=4d291df30fb7a94d13c6d38addf8d85d38f0111b

  Many docker users have been experiencing this issue:
  https://github.com/docker/docker/issues/18180

  
  The issue has been fixed since AUFS v20160111: 
http://permalink.gmane.org/gmane.linux.file-systems.aufs.user/5345
  So I suggest updating AUFS to v20160111.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533043/+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 1533009] Re: arm64: "unsupported RELA relocation"

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

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

Title:
  arm64: "unsupported RELA relocation"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  linux-image-4.3.0-5-generic 4.3.0-5.16 arm64 fails to load modules
  (and therefore boot). It emits messages like the following for each
  attempted module load:

  [2.156817] module libahci: unsupported RELA relocation: 275

  This is reminiscent of LP: #1502946 - except that fix appears to still
  be in-tact. What has changed, however, is the build environment. If I
  rebuild the same kernel source in a wily chroot, it boots fine.

  Marking "Confirmed" because Paulo Pisatti reported this to me, and I
  reproduced.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533009/+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 1533118] Re: Support new WWAN modules

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

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

Title:
  Support new WWAN modules

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  DW5812 [413c:81bb] - commit 670c0d62
  DW5813 [413c:81bc] - commit fb83d5f2

  $ git show 987aaad93a4cc217b84d6caa115bffdc0959eb46
  commit 987aaad93a4cc217b84d6caa115bffdc0959eb46
  Merge: 45af550 fb83d5f
  Author: David S. Miller 
  Date:   Mon Dec 21 14:51:40 2015 -0500

  Merge branch 'cdc_ncm-new-Dell-devices'
  
  Daniele Palmas says:
  
  
  net: usb: cdc_ncm: Adding support for two new Dell devices
  
  This patch series add support in the cdc_ncm driver for two devices
  based on the same platform, that are different only for carrier
  customization.
  
  V2: Added comment for highlighting FLAG_NOARP usage for those devices
  
  
  Signed-off-by: David S. Miller 

  
  These commits are in 4.4 already.  This issue is for vivid only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1533118/+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 1532909] Re: Dell XPS 13 - 9333 Kernel problems after update to wily

afrank, thank you for reporting this and helping make Ubuntu better.

As per http://www.dell.com/support/home/us/en/19/product-
support/product/xps-13-9333/drivers/advanced an update to your
computer's buggy and outdated BIOS is available (A08). 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. As well, 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-a08

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

Title:
  Dell XPS 13 - 9333 Kernel problems after update to wily

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Immediately after upgrade to wily faced several problems  on Dell XPS 13 - 
9333:
  - standard boot does not complete - need to manually select upstart or 
recovery as home partition is LUKS encrypted using cryptsetup and standard boot 
does not prompt for password any more. Instead of password prompt fsck.xfs (/ 
is on xfs) is shown.

  - repetedly get kernel oops - USB mouse and USB keyboard have
  irregular hangs omitting mouse movement and strokes

  Jan 11 10:28:31 cygnus kernel: [ 8814.972861] [drm:intel_pipe_config_compare 
[i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0)
  Jan 11 10:28:31 cygnus kernel: [ 8814.972866] [ cut here 
]
  Jan 11 10:28:31 cygnus kernel: [ 8814.972888] WARNING: CPU: 0 PID: 3225 at 
/build/linux-AFqQDb/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12328 
check_crtc_state+0x2c5/0x440 [i915]()
  Jan 11 10:28:31 cygnus kernel: [ 8814.972890] pipe state doesn't match!
  Jan 11 10:28:31 cygnus kernel: [ 8814.972891] Modules linked in: 
nls_iso8859_1 uas usb_storage rfcomm ctr ccm pci_stub vboxpci(OE) 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter ip_tables x_tables bnep 
binfmt_misc drbg ansi_cprng algif_skcipher af_alg ax88179_178a usbnet mii 
joydev hid_rmi dell_wmi sparse_keymap arc4 uvcvideo dell_laptop dcdbas 
dell_smm_hwmon videobuf2_vmalloc videobuf2_memops dm_crypt intel_rapl 
videobuf2_core iosf_mbi v4l2_common btusb x86_pkg_temp_thermal btrtl 
intel_powerclamp btbcm btintel coretemp bluetooth kvm_intel videodev media kvm 
hid_multitouch crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd iwlmvm mac80211 input_leds serio_raw 
iwlwifi snd_hda_codec_hdmi lpc_ich snd_hda_codec_realtek snd_hda_codec_generic 
cfg80211 shpchp snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep 
snd_soc_rt5640 snd_soc_rl6231 snd_soc_core snd_compress a
 c97_bus snd_pcm_dmaengine snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq acpi_als kfifo_buf industrialio snd_seq_device snd_timer snd soundcore 
dw_dmac dw_dmac_core snd_soc_sst_acpi i2c_designware_platform 8250_dw 
spi_pxa2xx_platform i2c_designware_core dell_rbtn intel_smartconnect mac_hid 
parport_pc ppdev lp parport xfs libcrc32c hid_generic i915 i2c_algo_bit 
drm_kms_helper psmouse drm ahci wmi libahci video sdhci_acpi sdhci i2c_hid 
usbhid hid
  Jan 11 10:28:31 cygnus kernel: [ 8814.972974] CPU: 0 PID: 3225 Comm: Xorg 
Tainted: GW  OE   4.2.0-23-generic #28-Ubuntu
  Jan 11 10:28:31 cygnus kernel: [ 8814.972975] Hardware name: Dell Inc. XPS13 
9333/0D13CR, BIOS A05 09/11/2014
  Jan 11 10:28:31 cygnus kernel: [ 8814.972977]   
a86f54fd 880215f277c8 817e94c9
  Jan 11 10:28:31 cygnus kernel: [ 8814.972980]   
880215f27820 880215f27808 8107b3d6
  Jan 11 10:28:31 cygnus kernel: [ 8814.972983]  880215f27848 
880215f278b0 88021255f000 0001
  Jan 11 10:28:31 cygnus kernel: [ 8814.972986] Call Trace:
  Jan 11 10:28:31 cygnus kernel: [ 8814.972992]  [] 
dump_stack+0x45/0x57
  Jan 11 10:28:31 cygnus kernel: [ 8814.972997]  [] 
warn_slowpath_common+0x86/0xc0
  Jan 11 10:28:31 cygnus kernel: [ 8814.973000]  [] 
warn_slowpath_fmt+0x55/0x70
  Jan 11 10:28:31 cygnus kernel: [ 8814.973020]  [] ? 
intel_pipe_config_compare+0xb31/0xc60 [i915]
  Jan

[Kernel-packages] [Bug 1532886] Re: s390x kernels are inconsistent for cloud stuff

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

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

Title:
  s390x kernels are inconsistent for cloud stuff

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

Bug description:
  So to do virtual machine / cloudy stuff things in the kernel config,
  are not how one would expect them to be. Whilst investigating that
  I've went ahead to compare all our kernel configs.

  amd64/config.common.amd64:CONFIG_VIRTIO_BLK=y
  amd64/config.common.amd64:CONFIG_VIRTIO_NET=y
  arm64/config.common.arm64:CONFIG_VIRTIO_BLK=y
  arm64/config.common.arm64:CONFIG_VIRTIO_NET=y
  armhf/config.common.armhf:CONFIG_VIRTIO_BLK=y
  armhf/config.common.armhf:CONFIG_VIRTIO_NET=y
  i386/config.common.i386:CONFIG_VIRTIO_BLK=y
  i386/config.common.i386:CONFIG_VIRTIO_NET=y
  powerpc/config.common.powerpc:CONFIG_VIRTIO_BLK=y
  powerpc/config.common.powerpc:CONFIG_VIRTIO_NET=y
  ppc64el/config.common.ppc64el:CONFIG_VIRTIO_BLK=y
  ppc64el/config.common.ppc64el:CONFIG_VIRTIO_NET=y

  but...
  s390x/config.common.s390x:CONFIG_VIRTIO_BLK=m
  s390x/config.common.s390x:CONFIG_VIRTIO_NET=m

  
  It would make sense to set CONFIG_VIRTIO_BLK and _NET to "=y" on s390x.

  Also:

  amd64/config.common.amd64:CONFIG_KVM=m
  arm64/config.common.arm64:CONFIG_KVM=y
  armhf/config.common.armhf:CONFIG_KVM=y
  i386/config.common.i386:CONFIG_KVM=m
  powerpc/config.common.powerpc:CONFIG_KVM=y
  ppc64el/config.common.ppc64el:CONFIG_KVM=y
  s390x/config.common.s390x:CONFIG_KVM=m

  Is a bit of mixed bag... x86+s390x have it as a module, yet
  arm*+powerpc* have it built in? Maybe all arches should be =y ?

  another one:
  Is there something special about ZLIB_DEFLATE on s390x?

  amd64/config.common.amd64:CONFIG_ZLIB_DEFLATE=y
  arm64/config.common.arm64:CONFIG_ZLIB_DEFLATE=y
  armhf/config.common.armhf:CONFIG_ZLIB_DEFLATE=y
  i386/config.common.i386:CONFIG_ZLIB_DEFLATE=y
  powerpc/config.common.powerpc:CONFIG_ZLIB_DEFLATE=y
  ppc64el/config.common.ppc64el:CONFIG_ZLIB_DEFLATE=y

  s390x/config.common.s390x:CONFIG_ZLIB_DEFLATE=m

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532886/+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 1532914] Re: Surelock GA2 SP1: capiredp01: cxl_init_adapter fails for CAPI devices 0000:01:00.0 and 0005:01:00.0 after upgrading to 840.10 Platform firmware build fips840/b1208b

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

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

Title:
  Surelock GA2 SP1: capiredp01: cxl_init_adapter fails for CAPI devices
  :01:00.0 and 0005:01:00.0 after upgrading to 840.10 Platform
  firmware build fips840/b1208b_1604.840

Status in linux package in Ubuntu:
  New

Bug description:
  Problem Description
  
  I upgraded the Platform firmware to the 840.10 Platform firmware build 
(b1208b_1604.840) to prepare for Surelock GA2 SP1 testing.  After the upgrade, 
I used the ipmitool to power on capiredfsp.aus.stglabs.ibm.com and boot the 
Ubuntu 15.10 partition (capiredp01.aus.stglabs.ibm.com) in OPAL firmware mode.  
In petitboot, I saw messages for "cxl-pci :01:00.0: cxl_init_adapter 
failed: -5" and "cxl-pci 0005:01:00.0: cxl_init_adapter failed: -5."  After the 
partition started running, I didn't see any AFU devices in /dev/cxl/ or 
/sys/class/cxl/ although I was able to see PCI devices for the hardware 
accelerators (:01:00.0 and 0005:01:00.0) with the lspci command.

  ubuntu@capiredp01:~$ ls -l /dev/cxl/
  ls: cannot access /dev/cxl/: No such file or directory
  ubuntu@capiredp01:~$ ls -l /sys/class/cxl/
  total 0
  ubuntu@capiredp01:~$ sudo lscfg | grep -i afu
  ubuntu@capiredp01:~$ sudo lspci|egrep -i "04cf|0477"
  :01:00.0 Processing accelerators: IBM Device 04cf (rev 01)
  0005:01:00.0 Processing accelerators: IBM Device 04cf (rev 01)
  ubuntu@capiredp01:~$ lsscsi -g
  [0:0:0:0]enclosu IBM  VSBPD12M1 6GSAS03  -  /dev/sg1 
  [0:0:1:0]cd/dvd  IBM. RMBO0140512  RA65  /dev/sr0   /dev/sg2 
  [0:3:0:0]no dev  IBM  57D7001SISIOA0150  -  /dev/sg0 
  [1:0:0:0]enclosu IBM  VSBPD12M1 6GSAS03  -  /dev/sg4 
  [1:0:1:0]diskIBM  HUC109030CSS600  E5C6  /dev/sda   /dev/sg5 
  [1:0:2:0]diskIBM  HUC101212CSS600  A5AA  /dev/sdb   /dev/sg6 
  [1:0:3:0]diskIBM  HUC101212CSS600  A5AA  /dev/sdc   /dev/sg7 
  [1:0:4:0]diskIBM  HUC101212CSS600  A5AA  /dev/sdd   /dev/sg8 
  [1:0:5:0]diskIBM  ST1200MM0007 BF04  /dev/sde   /dev/sg9 
  [1:0:6:0]diskIBM  ST1200MM0007 BF04  /dev/sdf   /dev/sg10
  [1:3:0:0]no dev  IBM  57D7001SISIOA0150  -  /dev/sg3 

  
  This is a regression: the Linux kernel has failed to synchronize the PSL 
timebase.
  The corresponding error message is in the dmesg log attached in comment #4:

  [1.687586] PSL: Timebase sync: giving up!

  CAPI devices are not enabled, because of this failure.

  PSL Timebase sync should not be a requirement for CAPI initialization,
  nor should it make an initialized card become unavailable.  Currently,
  timebase is an unused function of CAPI with hopes of adoption in the
  future.  Support of this feature should be considered optional at this
  time.

  I'm not sure what the fastest way to fix this is, but it needs to be
  fixed as quickly as possible.  CAPI is broken in Ubuntu 15.10.

  I can reproduce the bug, regardless of the skiboot level, with recent kernels.
  Older kernels behave as expected, regardless of the skiboot level.

  Firmware is not the cause of the regression, and kernel probably is.
  I sent this out to the capi-linux distro too, but I'll comment here as well.  
I'm not sure what is being looked at to determine the PSL timebase sync failed. 
 As far as I know all PSL versions should support timebase.  The only timebase 
error the PSL logs is if CAPP returns a status that says timebase has an error. 
 I'd think if that is the issue that timebase has not been correctly enabled or 
sequenced correctly in the host CAPP.  The PSL can't be enabled for timebase 
until the CAPP unit in the host has been enabled.

  I have installed a recent mainline Linux kernel (4.4.0-rc8) on
  capiredp01. I have rebooted this kernel and verified that the PSL
  timebase syncs without problem.

  I will now compare the source code of Ubuntu kernel 4.2.0-19 (that
  hits the bug) with the source of mainline kernel 4.4.0-rc8 (that
  operates as expected).

  I have updated the Ubuntu kernel and modules with:

  $ sudo apt-get install linux-image-4.2.0-23-generic
  $ sudo apt-get install linux-image-extra-4.2.0-23-generic

  I have rebooted Ubuntu kernel linux-image-4.2.0-23-generic, and found that 
the cxl driver hits the bug.
  I have also downloaded the source for this Ubuntu kernel (and modules) with:

  $ sudo apt-get source linux-image-4.2.0-23-generic

  I have recompiled and installed, and noticed that the resulting kernel
  bears the version 4.2.6 (??). I have rebooted this Ubuntu kernel 4.2.6
  built from the Ubuntu source for 4.2.0-23-generic, and found that the
  timebase sync occurs normally.

  In short, the kernels linux-4.2.6 and linux-4.4.0-rc8 (that I have
  built from

[Kernel-packages] [Bug 1532746] Re: SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl

Dea1993, thank you for reporting this and helping make Ubuntu better.

At your earliest convenience, could you please test the latest upstream
kernel available from the very top line at the top of the page from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release
names are irrelevant for testing, and please do not test the daily
folder)? Install instructions are available at
https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow
additional upstream developers to examine the issue.

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.

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

Thank you for your understanding.

** Tags added: latest-bios-f.13

** Tags added: xenial

** Tags added: lucid precise trusty

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

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

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

Title:
  SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've a problem with the keyboard of notebook HP Pavilion 15 ab062nl.
  the problem is with SHIFT ALT and CTRL buttons of the keyboard.

  for example when i use ALT-TAB shortcut, after few seconds, the ALT-TAB menu 
disappear as if i release ALT key, but isn't so.
  another example is when i navigate on web, when i scroll page with mouse 
wheel, sometimes the page start to resize, as if i'm pressing CTRL command 
while scroll, or if i'm writing a text, sometimes, borwser launch shortcut, as 
if i'm pressing CTRL while i type text, for exaple if i'm typing "b" letter, 
opens bookmarks...

  another example is while i'm typing text, if i press SHIFT key and
  start typing, begins to write uppercase letters and after a while,
  writes lowercase like I released shift, but i'm still pressing shift.

  for example if i press SHIFT+s, the result is this:
  SSs
  some letters are uppercase, but others are lowercase.

  i haven't found a solution.
  the only way to solve momentarily the problem, is pressing for some seconds 
the only SHIFT key, after that, the problems disappears indefinitely, or until 
the next restart.

  This problem occurs with all ubuntu version (x86 and x86_64), now i'm
  using Ubuntu 15.10, but i've also tried ubuntu 15.04, ubuntu 14.04,
  ubuntu 12.04, ubuntu 10.04.

  furthermore i've this problem also with other GNU/Linux Distributions (i've 
tried Fedora, OpenSuse, ArchLinux, Antergos, Debian, SteamOS).
  but isn't and hardware problem, because on Windows 8.1 and Windows 10 i 
haven't these problems.

  i've also tried to plug in an externa USB keyboard, and if i use
  external USB keybaord i haven't problems.

  i think is a problem of compatibility, with integrated keyboard of
  this notebook.

  i've tried to monitor these problems using XEV, and the results is
  that also if i'm not using notebook, sometimes XEV reads an INPUT of
  one of these 3 key (SHIFT, ALT, CTRL), and while i'm pressing one of
  these 3 key, XEV see also if i release and immedialty after press
  again the key.

  this is an example of the input while i press Left_ALT key for a while

  KeyPress event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 129987, (-142,152), root:(452,476),
  state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False
   
  KeyRelease event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 130147, (-142,152), root:(452,476),
  state 0x18, keycode 64 (keysym 0xffe9,

[Kernel-packages] [Bug 1532721] Re: Devices not working with kernel 4.2.0-23 on ThinkPad X230.

Matteo Dell'Amico, thank you for reporting this and helping make Ubuntu
better.

As per http://support.lenovo.com/us/en/products/Laptops-and-
netbooks/ThinkPad-X-Series-
laptops/ThinkPad-X230?linkTrack=Homepage:Body_Search%20Products an
update to your computer's buggy and outdated BIOS is available (2.65).
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-2.65

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

Title:
  Devices not working with kernel 4.2.0-23 on ThinkPad X230.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  when I run kernel 4.2.0-23, several devices don't work (USB devices,
  wireless card, DisplayPort on the docking station) on my Lenovo
  ThinkPad X230. Everything works OK with the previous 4.2.0-22 version.

  I'm filing the bug running the 4.2.0-22 version since I don't have
  Internet connectivity otherwise. I'm attaching version.log and lspci-
  vnvn.log from the problematic kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-23-generic 4.2.0-23.28
  ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  della  1980 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jan 11 10:23:11 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-18 (388 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: LENOVO 2325S1S
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic 
root=UUID=b34c9743-ba73-44ab-b2d1-39aa547cfbe6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-22-generic N/A
   linux-backports-modules-4.2.0-22-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-11-05 (66 days ago)
  dmi.bios.date: 02/22/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET92WW (2.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325S1S
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: J70023973
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET92WW(2.52):bd02/22/2013:svnLENOVO:pn2325S1S:pvrThinkPadX230:rvnLENOVO:rn2325S1S:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325S1S
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532721/+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 1532613] Re: NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [merssh:18253]

Martin Schaaf, thank you for reporting this and helping make Ubuntu
better. However, your crash report is manually attached.

Please follow these instructions to have apport report a new bug about your 
crash that can be dealt with by the automatic retracer. First, execute at a 
terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y 
dist-upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in 
/etc/default/apport and restart. Now reproduce the crash, then open a terminal, 
navigate to your /var/crash directory and file your report with:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

where _my_crash_report.crash is the crash you would like to report. By
default, this sends the crash to the Ubuntu Error Tracker
infrastructure, which is different than Launchpad. For more on this,
please see https://wiki.ubuntu.com/ErrorTracker .

However, if after doing this you would still like to have a crash report posted 
to Launchpad, for example to ease triage and add others to your report, one 
would need to open the following file via a terminal:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and file the crash report via:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

However, this report is being closed since the process outlined above
will deal with this issue more efficiently.

Also, please do not attach your crash report manually to this report and
reopen it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

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

** Attachment removed: "linux-image-3.19.0-43-generic.265328.crash"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532613/+attachment/4547634/+files/linux-image-3.19.0-43-generic.265328.crash

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [merssh:18253]

Status in linux package in Ubuntu:
  Invalid

Bug description:
  crash
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ms 2933 F pulseaudio
   /dev/snd/controlC1:  ms 2933 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-24 (78 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Apple Inc. MacBookPro11,1
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-43-generic.efi.signed 
root=UUID=fa975207-3163-46bd-a0d9-4aa53180bce3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-43.49~14.04.1-generic 3.19.8-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-43-generic N/A
   linux-backports-modules-3.19.0-43-generic  N/A
   linux-firmware 1.127.19
  Tags:  trusty
  Uname: Linux 3.19.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B16.1509081438
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B16.1509081438:bd09/08/2015:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.name: MacBookPro11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532613/+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 1532592] Re: General Protection Fault - kswapd

Matt Keller, thank you for taking the time to report this and trying to
help make Ubuntu better. However, Debian is not a software package
provided by the official Ubuntu repositories. Because of this the Ubuntu
project can not support or fix your particular bug. Please report this
bug to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories.

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

Title:
  General Protection Fault - kswapd

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I just rebuilt my home server with new hardware, and installed the
  latest Debian 8.2 fresh Friday night.  Yesterday, a general protection
  fault occurred while I was running mkvmerge.  I ran mkvmerge several
  times before and after this incident, and was unable to reproduce the
  problem.  My software raid array was resyncing when this occurred.

  dmesg, lspci -nn, and lspci -v output attached (concatenated into one
  file).

  Jan  9 17:38:32 mimir kernel: [ 4080.304356] general protection fault:  
[#1] SMP
  Jan  9 17:38:32 mimir kernel: [ 4080.305018] Modules linked in: fuse 
usb_storage nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc 
nls_utf8 nls_cp437 vfat fat x86_pkg_temp_thermal coretemp kvm_intel 
snd_hda_codec_hdmi kvm crc32_pclmul snd_hda_codec_realtek snd_hda_codec_generic 
ppdev aesni_intel efi_pstore snd_hda_intel aes_x86_64 lrw snd_hda_controller 
gf128mul glue_helper ablk_helper snd_hda_codec cryptd snd_hwdep snd_pcm psmouse 
snd_timer serio_raw snd pcspkr evdev efivars soundcore shpchp parport_pc 
parport battery wmi video tpm_infineon tpm_tis acpi_cpufreq tpm button 
processor acpi_pad autofs4 ext4 crc16 mbcache jbd2 dm_mod hid_apple hid_generic 
usbhid raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq md_mod sg sd_mod crc_t10dif crct10dif_generic crct10dif_pclmul 
crct10dif_common crc32c_intel ahci libahci xhci_hcd usbcore libata r8169 mii 
usb_common scsi_mod fan thermal thermal_sys i2c_hid hid i2c_core
  Jan  9 17:38:32 mimir kernel: [ 4080.310311] CPU: 0 PID: 40 Comm: kswapd0 Not 
tainted 3.16.0-4-amd64 #1 Debian 3.16.7-ckt20-1+deb8u2
  Jan  9 17:38:32 mimir kernel: [ 4080.310962] Hardware name: Gigabyte 
Technology Co., Ltd. To be filled by O.E.M./Z170-HD3P-CF, BIOS F5 01/08/2016
  Jan  9 17:38:32 mimir kernel: [ 4080.311622] task: 880265eef670 ti: 
880265ef task.ti: 880265ef
  Jan  9 17:38:32 mimir kernel: [ 4080.312299] RIP: 0010:[]  
[] page_evictable+0x13/0x40
  Jan  9 17:38:32 mimir kernel: [ 4080.312965] RSP: 0018:880265ef3a60  
EFLAGS: 00010286
  Jan  9 17:38:32 mimir kernel: [ 4080.313619] RAX: f7ff88019aa659e8 RBX: 
ea0006dfcdb8 RCX: ffd6
  Jan  9 17:38:32 mimir kernel: [ 4080.314262] RDX:  RSI: 
 RDI: ea0006dfcdb8
  Jan  9 17:38:32 mimir kernel: [ 4080.314902] RBP: ea0006dfcdd8 R08: 
0001 R09: 8802539beb48
  Jan  9 17:38:32 mimir kernel: [ 4080.315529] R10: 880265ef3a08 R11: 
ff80 R12: 880265ef3be8
  Jan  9 17:38:32 mimir kernel: [ 4080.316215] R13: ea0006dfcdb8 R14: 
0001 R15: 880265ef3af8
  Jan  9 17:38:32 mimir kernel: [ 4080.316830] FS:  () 
GS:880271c0() knlGS:
  Jan  9 17:38:32 mimir kernel: [ 4080.317449] CS:  0010 DS:  ES:  CR0: 
80050033
  Jan  9 17:38:32 mimir kernel: [ 4080.318049] CR2: 7f1dc30e8000 CR3: 
000266a61000 CR4: 003407f0
  Jan  9 17:38:32 mimir kernel: [ 4080.318651] DR0:  DR1: 
 DR2: 
  Jan  9 17:38:32 mimir kernel: [ 4080.319246] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Jan  9 17:38:32 mimir kernel: [ 4080.319849] Stack:
  Jan  9 17:38:32 mimir kernel: [ 4080.320487]  880265ef3dc0 
8114f62e  88019aa659e8
  Jan  9 17:38:32 mimir kernel: [ 4080.321084]  001f 
  880265eef670
  Jan  9 17:38:32 mimir kernel: [ 4080.321673]  00c0ef38 
001f  880271ff8e00
  Jan  9 17:38:32 mimir kernel: [ 4080.322261] Call Trace:
  Jan  9 17:38:32 mimir kernel: [ 4080.322852]  [] ? 
shrink_page_list+0x15e/0xa50
  Jan  9 17:38:32 mimir kernel: [ 4080.323443]  [] ? 
shrink_inactive_list+0x192/0x500
  Jan  9 17:38:32 mimir kernel: [ 4080.324040]  [] ? 
shrink_lruvec+0x511/0x6a0
  Jan  9 17:38:32 mimir kernel: [ 4080.326400]  [] ? 
shrink_zone+0x74/0x1b0
  Jan  9 17:38:32 mimir kernel: [ 4080.328964]  [] ? 
balance_pgdat+0x38e/0x5c0
  Jan  9 17:38:32 mimir kernel: [ 4080.331479]  [] ? 
kswapd+0x15f/0x3f0
  Jan  9 17:38:32 m

[Kernel-packages] [Bug 1532523] Re: Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type 20A7)

Haw Loeung, thank you for reporting this and helping make Ubuntu better.

Intel has a nice high level on the definition of PCC, and how it would
relate here
https://firmware.intel.com/sites/default/files/resources/PCC%20White%20Paper_0.pdf
. With this in mind, given no tangible issues have been noted, the error
message is considered innocuous.

However, to further root cause, if you remove all the non-default kernel 
parameters, is it still reproducible:
apparmor=0 elevator=noop intel_pstate=enable i915.enable_rc6=7 
i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=0

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

Title:
  Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type
  20A7)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  May be the same issue or duplicate as LP:1528684. I've just updated
  the BIOS to the latest (1.23) as per
  http://support.lenovo.com/au/en/products/Laptops-and-
  netbooks/ThinkPad-X-Series-laptops/ThinkPad-X1-Carbon-Type-
  20A7-20A8/downloads/DS039783 and am still seeing this error:

  | [hloeung@ragnar tmp]$ dmesg | grep -i error
  | [0.157751] Error parsing PCC subspaces from PCCT

  Both bootup info and dmidecode output shows latest:

  | [hloeung@ragnar tmp]$ sudo dmidecode -s bios-version && sudo dmidecode -s 
bios-release-date
  | GRET46WW (1.23 )
  | 11/04/2015

  Running Xenial Alpha 1:

  | [hloeung@ragnar tmp]$ cat /etc/*release
  | DISTRIB_ID=Ubuntu
  | DISTRIB_RELEASE=16.04
  | DISTRIB_CODENAME=xenial
  | DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)"

  | [hloeung@ragnar tmp]$ uname -a
  | Linux ragnar.local 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.3.0-5-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hloeung1241 F pulseaudio
   /dev/snd/controlC1:  hloeung1241 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  Card1.Amixer.info: Error: [Errno 2] No such file or directory
  Card1.Amixer.values: Error: [Errno 2] No such file or directory
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2014-04-24 (625 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: LENOVO 20A7CT01WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-5-generic 
root=UUID=77266758-9b87-4544-8a2c-f3c7aa3b3a7c ro quiet splash apparmor=0 
elevator=noop intel_pstate=enable i915.enable_rc6=7 i915_enable_fbc=1 
i915.lvds_downclock=1 drm.vblankoffdelay=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-5-generic N/A
   linux-backports-modules-4.3.0-5-generic  N/A
   linux-firmware   1.155
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.3.0-5-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 11/04/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GRET46WW (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20A7CT01WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98420 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGRET46WW(1.23):bd11/04/2015:svnLENOVO:pn20A7CT01WW:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7CT01WW:rvr0B98420STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20A7CT01WW
  dmi.product.version: ThinkPad X1 Carbon 2nd
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532523/+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 1426216] Re: pci driver messages - BAR 13: no space for

2016-01-12 Thread Luciano Chavez

Doing cleanup and marking bug as Invalid as it was.

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

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

Title:
  pci driver messages - BAR 13: no space for

Status in linux package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  pci driver messages - BAR 13: no space for 

  ---uname output---
  3.18.0-12-generic
   
  Machine Type = POWER8 

  ---Steps to Reproduce---
  Install Ubuntu 15.04 daily build running bare-metal
  After the installation following messages are seen in dmesg. 
  Not sure if these indicate a problem. Can some one look at these and confirm 
if this is problem or can be ignored ?

  Messages from dmesg log

  [0.714476] pci_bus 0001:00: max bus depth: 3 pci_try_num: 4
  [0.714519] pci 0001:04:00.0: reg 0x16c: [mem 0x-0x 64bit]
  [0.714541] pci 0001:04:00.0: reg 0x174: [mem 0x-0x 64bit]
  [0.714577] pci 0001:00:00.0: BAR 15: assigned [mem 
0x3b101000-0x3b103fff 64bit pref]
  [0.714579] pci 0001:00:00.0: BAR 14: assigned [mem 
0x3fe08000-0x3fe081ff]
  [0.714581] pci 0001:00:00.0: BAR 13: no space for [io  size 0x3000]
  [0.714583] pci 0001:00:00.0: BAR 13: failed to assign [io  size 0x3000]
  [0.714586] pci 0001:01:00.0: BAR 15: assigned [mem 
0x3b101000-0x3b103fff 64bit pref]
  [0.714588] pci 0001:01:00.0: BAR 14: assigned [mem 
0x3fe08000-0x3fe0817f]
  [0.714590] pci 0001:01:00.0: BAR 0: assigned [mem 
0x3fe08180-0x3fe08183]
  [0.714595] pci 0001:01:00.0: BAR 13: no space for [io  size 0x3000]
  [0.714597] pci 0001:01:00.0: BAR 13: failed to assign [io  size 0x3000]
  [0.714600] pci 0001:02:01.0: BAR 15: assigned [mem 
0x3b101000-0x3b101fff 64bit pref]
  [0.714602] pci 0001:02:08.0: BAR 15: assigned [mem 
0x3b102000-0x3b102fff 64bit pref]
  [0.714604] pci 0001:02:09.0: BAR 15: assigned [mem 
0x3b103000-0x3b103fff 64bit pref]
  [0.714606] pci 0001:02:01.0: BAR 14: assigned [mem 
0x3fe08000-0x3fe0807f]
  [0.714608] pci 0001:02:08.0: BAR 14: assigned [mem 
0x3fe08080-0x3fe080ff]
  [0.714609] pci 0001:02:09.0: BAR 14: assigned [mem 
0x3fe08100-0x3fe0817f]
  [0.714611] pci 0001:02:01.0: BAR 13: no space for [io  size 0x1000]
  [0.714613] pci 0001:02:01.0: BAR 13: failed to assign [io  size 0x1000]
  [0.714614] pci 0001:02:08.0: BAR 13: no space for [io  size 0x1000]
  [0.714616] pci 0001:02:08.0: BAR 13: failed to assign [io  size 0x1000]
  [0.714618] pci 0001:02:09.0: BAR 13: no space for [io  size 0x1000]
  [0.714619] pci 0001:02:09.0: BAR 13: failed to assign [io  size 0x1000]
  [0.714622] pci 0001:03:00.0: BAR 6: assigned [mem 
0x3fe08000-0x3fe08003 pref]
  [0.714624] pci 0001:03:00.1: BAR 6: assigned [mem 
0x3fe08004-0x3fe08007 pref]
  [0.714627] pci 0001:03:00.0: BAR 2: assigned [mem 
0x3fe08008-0x3fe080083fff 64bit]
  [0.714641] pci 0001:03:00.1: BAR 2: assigned [mem 
0x3fe080084000-0x3fe080087fff 64bit]
  [0.714656] pci 0001:03:00.0: BAR 0: assigned [mem 
0x3fe080088000-0x3fe080088fff 64bit]
  [0.714670] pci 0001:03:00.1: BAR 0: assigned [mem 
0x3fe080089000-0x3fe080089fff 64bit]
  [0.714685] pci 0001:03:00.0: BAR 4: no space for [io  size 0x0100]
  [0.714686] pci 0001:03:00.0: BAR 4: failed to assign [io  size 0x0100]
  [0.714688] pci 0001:03:00.1: BAR 4: no space for [io  size 0x0100]
  [0.714690] pci 0001:03:00.1: BAR 4: failed to assign [io  size 0x0100]
  [0.714691] pci 0001:02:01.0: PCI bridge to [bus 03]

  # lspci 
  :00:00.0 PCI bridge: IBM Device 03dc
  0001:00:00.0 PCI bridge: IBM Device 03dc
  0001:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:02:08.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:02:09.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:03:00.0 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre 
Channel Host Adapter (rev 03)
  0001:03:00.1 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre 
Channel Host Adapter (rev 03)
  0001:04:00.0 RAID bus controller: IBM PCI-E IPR SAS Adapter (ASIC) (rev 01)
  0002:00:00.0 PCI bridge: IBM Device 03dc
  0003:00:00.0 PCI bridge: IBM Device 03dc
  0003:01:00.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
  0003:02:01.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
  0003:02:08.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
  0003:02:09.0 PCI bridge: PLX Technology, Inc. Device

[Kernel-packages] [Bug 1532523] Re: Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type 20A7)

** Tags added: latest-bios-1.23

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

Title:
  Error parsing PCC subspaces from PCCT on ThinkPad X1 Carbon (Type
  20A7)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  May be the same issue or duplicate as LP:1528684. I've just updated
  the BIOS to the latest (1.23) as per
  http://support.lenovo.com/au/en/products/Laptops-and-
  netbooks/ThinkPad-X-Series-laptops/ThinkPad-X1-Carbon-Type-
  20A7-20A8/downloads/DS039783 and am still seeing this error:

  | [hloeung@ragnar tmp]$ dmesg | grep -i error
  | [0.157751] Error parsing PCC subspaces from PCCT

  Both bootup info and dmidecode output shows latest:

  | [hloeung@ragnar tmp]$ sudo dmidecode -s bios-version && sudo dmidecode -s 
bios-release-date
  | GRET46WW (1.23 )
  | 11/04/2015

  Running Xenial Alpha 1:

  | [hloeung@ragnar tmp]$ cat /etc/*release
  | DISTRIB_ID=Ubuntu
  | DISTRIB_RELEASE=16.04
  | DISTRIB_CODENAME=xenial
  | DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)"

  | [hloeung@ragnar tmp]$ uname -a
  | Linux ragnar.local 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.3.0-5-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hloeung1241 F pulseaudio
   /dev/snd/controlC1:  hloeung1241 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  Card1.Amixer.info: Error: [Errno 2] No such file or directory
  Card1.Amixer.values: Error: [Errno 2] No such file or directory
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2014-04-24 (625 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: LENOVO 20A7CT01WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-5-generic 
root=UUID=77266758-9b87-4544-8a2c-f3c7aa3b3a7c ro quiet splash apparmor=0 
elevator=noop intel_pstate=enable i915.enable_rc6=7 i915_enable_fbc=1 
i915.lvds_downclock=1 drm.vblankoffdelay=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-5-generic N/A
   linux-backports-modules-4.3.0-5-generic  N/A
   linux-firmware   1.155
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.3.0-5-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 11/04/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GRET46WW (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20A7CT01WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98420 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGRET46WW(1.23):bd11/04/2015:svnLENOVO:pn20A7CT01WW:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7CT01WW:rvr0B98420STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20A7CT01WW
  dmi.product.version: ThinkPad X1 Carbon 2nd
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532523/+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 1531653] Re: Macbook Pro Retina 11, 1 SD Card Reader Doesn't Work

Randy Syring, the next step would be to install Ubuntu to another
partition with default settings (i.e. no out-of-tree modules) if you
need to preserve the original install.

Once this is in place, at your earliest convenience, could you please
test the latest upstream kernel available from the very top line at the
top of the page from http://kernel.ubuntu.com/~kernel-
ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and
please do not test the daily folder)? Install instructions are available
at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow
additional upstream developers to examine the issue.

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.

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

Thank you for your understanding.

** Tags added: xenial

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

Title:
  Macbook Pro Retina 11,1 SD Card Reader Doesn't Work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Macbook Pro (MBP) Retina 11,1 with an SD card reader that
  will not work.

  The SD card reader:

  * has device code 05ac:8406
  * does work in OS X.
  * does not work in SystemRescueCD running kernel 3.14.56-std461-amd64
  - I have a friend with an identical Macbook Pro and his SD card reader 
does work in SystemRescueCD
  * Does not show up in lsusb
  * Does not display any messages in dmesg when an SD card is inserted
  * Device 05ac:8406 does not show up in dmesg
  * Does not work in kernel 4.2.0-22.27~14.04.1.  All issues reported here seem 
to be the same regardless if I use 3.13 or 4.2.
  * Uses the following drivers on my friends MBP: sd, usb-storage, usb, xhci_hcd

  The last point made me look closer at the xhci_hcd logs:

  rsyring@loftex:~$ dmesg | grep xhci_hcd
  [2.681478] xhci_hcd :00:14.0: xHCI Host Controller
  [2.681498] xhci_hcd :00:14.0: new USB bus registered, assigned bus 
number 1
  [2.681589] xhci_hcd :00:14.0: cache line size of 256 is not supported
  [2.681607] xhci_hcd :00:14.0: irq 63 for MSI/MSI-X
  [2.681755] usb usb1: Manufacturer: Linux 3.13.0-57-generic xhci_hcd
  [2.682098] xhci_hcd :00:14.0: xHCI Host Controller
  [2.682115] xhci_hcd :00:14.0: new USB bus registered, assigned bus 
number 2
  [2.682219] usb usb2: Manufacturer: Linux 3.13.0-57-generic xhci_hcd
  [3.980423] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
  [9.352422] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   14.560476] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   20.549170] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   25.757227] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   26.129482] usb 1-1: new high-speed USB device number 2 using xhci_hcd
  [   26.321707] usb 1-3: new full-speed USB device number 3 using xhci_hcd
  [   26.505802] usb 1-5: new full-speed USB device number 4 using xhci_hcd
  [   26.603224] usb 2-1.1: new SuperSpeed USB device number 6 using xhci_hcd
  [   26.754245] usb 1-1.2: new low-speed USB device number 5 using xhci_hcd
  [   26.954315] usb 1-1.4: new low-speed USB device number 6 using xhci_hcd
  [   27.050323] usb 1-3.1: new full-speed USB device number 7 using xhci_hcd
  [   27.142383] usb 1-3.2: new full-speed USB device number 8 using xhci_hcd
  [   27.234476] usb 1-3.3: new full-speed USB device number 9 using xhci_hcd
  [   81.685139] usb 1-1.4: new low-speed USB device number 10 using xhci_hcd

  The "Timeout while waiting" messages are suspicious to me.  dmesg on
  my friend's MBP  does not show those messages.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-57-generic 3.13.0-57.95
  ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
  Uname: Linux 3.13.

[Kernel-packages] [Bug 1532513] Re: kswapd 100% CPU usage and running out of memory without swap being used

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

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

Title:
  kswapd 100% CPU usage and running out of memory without swap  being
  used

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug closely resembles bug 1518457 and others, but is reported
  separately as the affected kernel versions do not match, see comments
  #45, #43 and #8 on 1518457.

  The issue first occured on a production workload (JIRA running on
  Tomcat) on an EC2 t2.small instance after upgrading to 15.10. The
  issue happens when running out of memory, typicall during busy hours
  or when nightly Python backup script runs. To reproduce the issue, I
  use t2.micro (1GiB RAM) because the problem then arises just by
  starting the JIRA application. I do not see the problem on 14.04 or
  15.05 on the same server.

  Symptoms: kswapd0 falls into a busy loop and spins on 100% CPU usage
  and swap not being used/barely being used. The system can be recovered
  with `echo 1 > /proc/sys/vm/drop_caches`, but with high traffic/little
  free memory, the problem returns immediately.

  Swappiness has not been changed (vm.swappiness = 60). I can reproduce
  this consitently on Ubuntu AMIs (https://cloud-
  images.ubuntu.com/locator/ec2/). I've used AMI ami-c4140aa8 (eu-
  central-1). I can provide SSH access to a machine on request and have
  public Puppet scripts to configure a new server.

  I've attached scripts and logs from an up to date 15.10  and 15.04
  instance to compare results with and without the bug. Note that the
  CPU numbers in the vmstat output doesn't specify which process, but
  top has showed that the majority of user time is the java process and
  the majority of system time is the kswapd0 process.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-23-generic 4.2.0-23.28
  ProcVersionSignature: User Name 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 10 03:56 seq
   crw-rw 1 root audio 116, 33 Jan 10 03:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  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: N/A
  Date: Sun Jan 10 04:07:30 2016
  Ec2AMI: ami-c4140aa8
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-central-1b
  Ec2InstanceType: t2.micro
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 xen
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic 
root=UUID=56681ffc-93a4-47c9-b487-b67be12205d9 ro console=tty1 console=ttyS0 
net.ifnames=0
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-23-generic N/A
   linux-backports-modules-4.2.0-23-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/07/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532513/+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 1532303] Re: [Ubuntu 16.04] SR-IOV optimized vNIC (new device driver for POWER8)

2016-01-12 Thread Steve Langasek

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

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

Title:
  [Ubuntu 16.04] SR-IOV optimized vNIC (new device driver for POWER8)

Status in linux package in Ubuntu:
  New

Bug description:
  This new device driver enables high performance virtual networking
  which combines the isolation, QoS, and shared resources benefits of
  SR-IOV with the Live LPAR Mobility capabilities of a virtual adapter.
  The SR-IOV VF will be attached to the VIOS partition and mapped
  directly to the Linux client for exclusive use; this is the device
  driver for this new virtual adapter.

  This is the kernel part for this feature request.

  The ibmvnic driver has recently been included in David Miller's net-
  next tree.  It should be included in Linux 4.5.

  git commit : http://git.kernel.org/cgit/linux/kernel/git/davem/net-
  next.git/commit/?id=032c5e82847a2214c3196a90f0aeba0ce252de58

  This is a feature request to include this new driver in Ubuntu 16.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532303/+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 1532267] Re: Bluetooth Qualcomm Atheros QCA9565 / AR9565 [168c:0036] not recognized

2016-01-12 Thread Jeremy

Leonardo, is it possible to remove a cover from the computer to see the
model number on the wifi card and post it along with any other info,
front and back?  Pictures is nothing else is possible

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

Title:
  Bluetooth Qualcomm Atheros QCA9565 / AR9565 [168c:0036]  not
  recognized

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I have installed Ubuntu 14.04 on my Acer Aspire E5-573G, and the
  bluetooth was not recognized, but wifi is working perfectly. This
  problem occurred from kernel 3.19 - 4.4-rc8.

  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter [168c:0036] (rev 01)
   Subsystem: Lite-On Communications Inc Device [11ad:0803]
   Kernel driver in use: ath9k

  The result of lsusb;
  Bus 003 Device 002: ID 8087:8001 Intel Corp.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
  Bus 001 Device 003: ID 1bcf:2c81 Sunplus Innovation Technology Inc.
  Bus 001 Device 005: ID 046d:c534 Logitech, Inc.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-23-generic 4.2.0-23.28~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-23.28~14.04.1-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan  8 14:41:21 2016
  InstallationDate: Installed on 2015-12-25 (13 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-wily
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lmrodrigues   2174 F pulseaudio
   /dev/snd/controlC1:  lmrodrigues   2174 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=898c0089-7a66-4b09-b59b-0953113ce894
  InstallationDate: Installed on 2015-12-25 (15 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Acer Aspire E5-573G
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic 
root=UUID=37df17cf-666c-4aa5-b851-ef8e5f7ce3e4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-23.28~14.04.1-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-23-generic N/A
   linux-backports-modules-4.2.0-23-generic  N/A
   linux-firmware1.144+ar3012
  Tags:  trusty
  Uname: Linux 4.2.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.31
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  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.31:bd09/25/2015:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-573G
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532267/+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 1532303] [NEW] [Ubuntu 16.04] SR-IOV optimized vNIC (new device driver for POWER8)

You have been subscribed to a public bug:

This new device driver enables high performance virtual networking which
combines the isolation, QoS, and shared resources benefits of SR-IOV
with the Live LPAR Mobility capabilities of a virtual adapter. The SR-
IOV VF will be attached to the VIOS partition and mapped directly to the
Linux client for exclusive use; this is the device driver for this new
virtual adapter.

This is the kernel part for this feature request.

The ibmvnic driver has recently been included in David Miller's net-next
tree.  It should be included in Linux 4.5.

git commit : http://git.kernel.org/cgit/linux/kernel/git/davem/net-
next.git/commit/?id=032c5e82847a2214c3196a90f0aeba0ce252de58

This is a feature request to include this new driver in Ubuntu 16.04.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64 bot-comment bugnameltc-134639 severity-high 
targetmilestone-inin1604
-- 
[Ubuntu 16.04] SR-IOV optimized vNIC (new device driver for POWER8)
https://bugs.launchpad.net/bugs/1532303
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 1532267] Re: Bluetooth Qualcomm Atheros QCA9565 / AR9565 [168c:0036] not recognized

Leonardo Marques Rodrigues, the issue you are reporting is an upstream
one. Could you please report this problem following the instructions
verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the
appropriate mailing list (TO Marcel Holtmann, Gustavo Padovan, and Johan
Hedberg CC linux-bluetooth)?

Please provide a direct URL to your post to the mailing list when it
becomes available so that it may be tracked.

Thank you for your understanding.

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

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

Title:
  Bluetooth Qualcomm Atheros QCA9565 / AR9565 [168c:0036]  not
  recognized

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I have installed Ubuntu 14.04 on my Acer Aspire E5-573G, and the
  bluetooth was not recognized, but wifi is working perfectly. This
  problem occurred from kernel 3.19 - 4.4-rc8.

  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter [168c:0036] (rev 01)
   Subsystem: Lite-On Communications Inc Device [11ad:0803]
   Kernel driver in use: ath9k

  The result of lsusb;
  Bus 003 Device 002: ID 8087:8001 Intel Corp.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
  Bus 001 Device 003: ID 1bcf:2c81 Sunplus Innovation Technology Inc.
  Bus 001 Device 005: ID 046d:c534 Logitech, Inc.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-23-generic 4.2.0-23.28~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-23.28~14.04.1-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan  8 14:41:21 2016
  InstallationDate: Installed on 2015-12-25 (13 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-wily
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lmrodrigues   2174 F pulseaudio
   /dev/snd/controlC1:  lmrodrigues   2174 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=898c0089-7a66-4b09-b59b-0953113ce894
  InstallationDate: Installed on 2015-12-25 (15 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Acer Aspire E5-573G
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic 
root=UUID=37df17cf-666c-4aa5-b851-ef8e5f7ce3e4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-23.28~14.04.1-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-23-generic N/A
   linux-backports-modules-4.2.0-23-generic  N/A
   linux-firmware1.144+ar3012
  Tags:  trusty
  Uname: Linux 4.2.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.31
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  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.31:bd09/25/2015:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-573G
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532267/+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 1532498] Re: Atheros wifi qca6174 hw3.2 is not supported

** Tags added: xenial

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

Title:
  Atheros wifi qca6174 hw3.2 is not supported

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Wifi hardware not supported under Ubuntu 15.10 kernel 4.2.0-23-generic

  $ dmesg | grep ath10k
  [1.729989] ath10k_pci :3b:00.0: enabling device ( -> 0002)
  [1.733061] ath10k_pci :3b:00.0: pci irq msi-x interrupts 8 irq_mode 0 
reset_mode 0
  [1.935127] ath10k_pci :3b:00.0: Direct firmware load for 
ath10k/cal-pci-:3b:00.0.bin failed with error -2
  [1.938035] ath10k_pci :3b:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/board-pci-168c:003e:144d:412f.bin failed with error -2
  [1.938038] ath10k_pci :3b:00.0: failed to load spec board file, 
falling back to generic: -2
  [1.938624] ath10k_pci :3b:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
  [1.938627] ath10k_pci :3b:00.0: could not fetch firmware file 
'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
  [4.064026] ath10k_pci :3b:00.0: qca6174 hw3.2 (0x0503, 
0x00340aff, 168c:003e:144d:412f fallback) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 api 
4 htt 3.26 wmi 4 cal otp max_sta 32
  [4.064029] ath10k_pci :3b:00.0: debug 0 debugfs 1 tracing 1 dfs 0 
testmode 0
  [5.061061] ath10k_pci :3b:00.0: suspend timed out - target pause 
event never came
  [8.136872] ath10k_pci :3b:00.0 wlp59s0: renamed from wlan0
  [   13.371834] ath10k_pci :3b:00.0: failed to enable dynamic BW: -11
  [   16.371511] ath10k_pci :3b:00.0: could not suspend target (-11)
  [   24.658229] ath10k_pci :3b:00.0: failed to enable dynamic BW: -11
  [   27.657788] ath10k_pci :3b:00.0: could not suspend target (-11)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-23-generic 4.2.0-23.28
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dwebber1658 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Jan  9 18:20:08 2016
  HibernationDevice: RESUME=UUID=0df65023-ded0-4eac-aa6d-d8494ecd7206
  InstallationDate: Installed on 2015-12-22 (18 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 940Z5L
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic.efi.signed 
root=UUID=24c27814-5135-4a80-9ce1-b932e2513949 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-23-generic N/A
   linux-backports-modules-4.2.0-23-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P04AFC.084.151020.SH
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP940Z5L-X01US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8554A1H-C01-G001-S0001+10.0.10240
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP04AFC.084.151020.SH:bd10/20/2015:svnSAMSUNGELECTRONICSCO.,LTD.:pn940Z5L:pvrP04AFC:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP940Z5L-X01US:rvrSGL8554A1H-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 940Z5L
  dmi.product.version: P04AFC
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532498/+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 1505178] Re: MFG: Habanero: hxestorage exerciser logs task blocked messages in dmesg when running disks under PMC Sierra

2016-01-12 Thread Michael Hohnbaum

Canonical does not have access to this hardware, will need IBM to
propose a fix.

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

Title:
  MFG: Habanero: hxestorage exerciser logs task blocked messages in
  dmesg when running disks under PMC Sierra

Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0  ==

  When running STX on Habanero systems with PMC Sierra, the following
  linux error messages are found when running "dmesg -T
  --level=alert,crit,err" after the run.

  [Fri Oct  2 12:36:52 2015] INFO: task hxestorage:18049 blocked for more than 
120 seconds.
  [Fri Oct  2 12:36:52 2015]   Tainted: G   OE  3.19.0-25-generic 
#26~14.04.1-Ubuntu
  [Fri Oct  2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  [Fri Oct  2 12:36:52 2015] INFO: task hxestorage:18177 blocked for more than 
120 seconds.
  [Fri Oct  2 12:36:52 2015]   Tainted: G   OE  3.19.0-25-generic 
#26~14.04.1-Ubuntu
  [Fri Oct  2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  [Fri Oct  2 12:36:52 2015] INFO: task hxestorage:18181 blocked for more than 
120 seconds.
  [Fri Oct  2 12:36:52 2015]   Tainted: G   OE  3.19.0-25-generic 
#26~14.04.1-Ubuntu
  [Fri Oct  2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  [Fri Oct  2 12:36:52 2015] INFO: task hxestorage:18185 blocked for more than 
120 seconds.
  [Fri Oct  2 12:36:52 2015]   Tainted: G   OE  3.19.0-25-generic 
#26~14.04.1-Ubuntu
  [Fri Oct  2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  [Fri Oct  2 12:36:52 2015] INFO: task hxestorage:18189 blocked for more than 
120 seconds.
  [Fri Oct  2 12:36:52 2015]   Tainted: G   OE  3.19.0-25-generic 
#26~14.04.1-Ubuntu
  [Fri Oct  2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  [Fri Oct  2 12:36:52 2015] INFO: task hxestorage:18194 blocked for more than 
120 seconds.
  [Fri Oct  2 12:36:52 2015]   Tainted: G   OE  3.19.0-25-generic 
#26~14.04.1-Ubuntu
  [Fri Oct  2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  [Fri Oct  2 12:36:52 2015] INFO: task hxestorage:18200 blocked for more than 
120 seconds.
  [Fri Oct  2 12:36:52 2015]   Tainted: G   OE  3.19.0-25-generic 
#26~14.04.1-Ubuntu
  [Fri Oct  2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  [Fri Oct  2 12:36:52 2015] INFO: task hxestorage:18205 blocked for more than 
120 seconds.
  [Fri Oct  2 12:36:52 2015]   Tainted: G   OE  3.19.0-25-generic 
#26~14.04.1-Ubuntu
  [Fri Oct  2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  [Fri Oct  2 12:36:52 2015] INFO: task hxestorage:18213 blocked for more than 
120 seconds.
  [Fri Oct  2 12:36:52 2015]   Tainted: G   OE  3.19.0-25-generic 
#26~14.04.1-Ubuntu
  [Fri Oct  2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  [Fri Oct  2 12:36:52 2015] INFO: task hxestorage:18221 blocked for more than 
120 seconds.
  [Fri Oct  2 12:36:52 2015]   Tainted: G   OE  3.19.0-25-generic 
#26~14.04.1-Ubuntu
  [Fri Oct  2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.

  We are running the following code levels.

 ver 1.5.4.3 - OS, HTX, Firmware and Machine details

 OS: GNU/Linux
 OS Version: Ubuntu 14.04.3 LTS \n \l
 Kernel Version: 3.19.0-25-generic
HTX Version: htxubuntu-357
  Host Name: rcx2c357
  Machine Serial No: 1035C5A 
 Machine Type/Model: 8348-21C

  
  We have a very limited number of PMC Sierra configs.  I've seen this error on 
both EC3S and ECSY PMC adapter types.  We've only run systems with 6TB drives 
or a mix of 6TB and 8TB disk drives so far.

  
  == Comment: #5  ==
  Call Trace:

  dmesg -T

  ---
  [Fri Oct  2 12:36:52 2015] INFO: task hxestorage:18049 blocked for more than 
120 seconds.
  [Fri Oct  2 12:36:52 2015]   Tainted: G   OE  3.19.0-25-generic 
#26~14.04.1-Ubuntu
  [Fri Oct  2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  [Fri Oct  2 12:36:52 2015] hxestorage  D 3fff78c69a20 0 18049
451 0x0004
  [Fri Oct  2 12:36:52 2015] Call Trace:
  [Fri Oct  2 12:36:52 2015] [c0791de17490] [c079111f8980] 
0xc079111f8980 (unreliable)
  [Fri Oct  2 12:36:52 2015] [c0791de17660] [c0015934] 
__switch_to+0x204/0x350
  [Fri Oct  2 12:36:52 2015] [c0791de176c0] [c0a11948] 
__schedule+

[Kernel-packages] [Bug 1517142] Re: ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

2016-01-12 Thread Michael Hohnbaum

IBM, any updates on the recommended fix for this issue?

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

Title:
  ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Issues were found in iSCSI tests with hardware remote targets.
  Specifically, kernel crash happens due to dereferencing a null pointer
  (sc->device->lun at libiscsi.c:369, with sc==NULL). During the crash,
  lots of messages regarding lists invalid accesses are showed in kernel
  log.

  The commit 659743b02c41 ("[SCSI] libiscsi: Reduce locking contention
  in fast path") appears to be the cause.

  Reverting the commit solve the issue, at least until we can discuss and
  find the exact problem (and its solution) in the commit
  659743b02c41 ("[SCSI] libiscsi: Reduce locking contention in fast path").

  A test kernel was patched to revert the offend commit - Prashantha is
  running tests to check if the problem is solved.

  With the patched kernel, I am unable to recreate the crash. The patch appears
  to be working.

  A discussion is ongoing in linux-scsi mailing list, to revert the
  patch upstream (look the following link).

  http://marc.info/?l=linux-scsi&m=144730474819919

  Another quick discussion, started by me, it's on open-iscsi mailing
  list, on Google Groups:

  https://groups.google.com/forum/#!topic/open-iscsi/0S5fEM_Aafk

  The iscsi maintainer wants to revert, but patch co-author wants more
  study before reverting. Prashantha is performing some performance
  analysis to check the impact of the patch on iscsi performance.

  Mirroring to Launchpad for Canonical's awareness. Once the discussion
  settles on the final solution, a patch or link to the upstream commit
  will be provided for Canonical to review for acceptance in the 14.04
  LTS kernel and SRU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517142/+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 1531653] Re: Macbook Pro Retina 11, 1 SD Card Reader Doesn't Work

2016-01-12 Thread Randy Syring

Christopher Penalver, I have downloaded today's ISO and booted my laptop
with it.  No changes noted.  Inserting an SD card did show any messages
in dmesg and the card reader device does not show up in lsusb or dmesg.

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

Title:
  Macbook Pro Retina 11,1 SD Card Reader Doesn't Work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Macbook Pro (MBP) Retina 11,1 with an SD card reader that
  will not work.

  The SD card reader:

  * has device code 05ac:8406
  * does work in OS X.
  * does not work in SystemRescueCD running kernel 3.14.56-std461-amd64
  - I have a friend with an identical Macbook Pro and his SD card reader 
does work in SystemRescueCD
  * Does not show up in lsusb
  * Does not display any messages in dmesg when an SD card is inserted
  * Device 05ac:8406 does not show up in dmesg
  * Does not work in kernel 4.2.0-22.27~14.04.1.  All issues reported here seem 
to be the same regardless if I use 3.13 or 4.2.
  * Uses the following drivers on my friends MBP: sd, usb-storage, usb, xhci_hcd

  The last point made me look closer at the xhci_hcd logs:

  rsyring@loftex:~$ dmesg | grep xhci_hcd
  [2.681478] xhci_hcd :00:14.0: xHCI Host Controller
  [2.681498] xhci_hcd :00:14.0: new USB bus registered, assigned bus 
number 1
  [2.681589] xhci_hcd :00:14.0: cache line size of 256 is not supported
  [2.681607] xhci_hcd :00:14.0: irq 63 for MSI/MSI-X
  [2.681755] usb usb1: Manufacturer: Linux 3.13.0-57-generic xhci_hcd
  [2.682098] xhci_hcd :00:14.0: xHCI Host Controller
  [2.682115] xhci_hcd :00:14.0: new USB bus registered, assigned bus 
number 2
  [2.682219] usb usb2: Manufacturer: Linux 3.13.0-57-generic xhci_hcd
  [3.980423] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
  [9.352422] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   14.560476] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   20.549170] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   25.757227] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   26.129482] usb 1-1: new high-speed USB device number 2 using xhci_hcd
  [   26.321707] usb 1-3: new full-speed USB device number 3 using xhci_hcd
  [   26.505802] usb 1-5: new full-speed USB device number 4 using xhci_hcd
  [   26.603224] usb 2-1.1: new SuperSpeed USB device number 6 using xhci_hcd
  [   26.754245] usb 1-1.2: new low-speed USB device number 5 using xhci_hcd
  [   26.954315] usb 1-1.4: new low-speed USB device number 6 using xhci_hcd
  [   27.050323] usb 1-3.1: new full-speed USB device number 7 using xhci_hcd
  [   27.142383] usb 1-3.2: new full-speed USB device number 8 using xhci_hcd
  [   27.234476] usb 1-3.3: new full-speed USB device number 9 using xhci_hcd
  [   81.685139] usb 1-1.4: new low-speed USB device number 10 using xhci_hcd

  The "Timeout while waiting" messages are suspicious to me.  dmesg on
  my friend's MBP  does not show those messages.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-57-generic 3.13.0-57.95
  ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
  Uname: Linux 3.13.0-57-generic x86_64
  NonfreeKernelModules: wl zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rsyring5051 F pulseaudio
   /dev/snd/controlC0:  rsyring5051 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Jan  6 17:57:28 2016
  HibernationDevice: RESUME=UUID=8b8a41c8-2030-4f92-b7d6-1143a081ec85
  InstallationDate: Installed on 2014-02-15 (690 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  MachineType: Apple Inc. MacBookPro11,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \vmlinuz-3.13.0-57-generic.efi.signed root=ZFS=/ROOT ro 
libata.force=noncq 
cryptopts=target=cryptdev,source=/dev/disk/by-uuid/6993c5ec-7308-420d-bbe2-1ed18c15e2bc,discard
 boot=zfs initrd=\initrd.img-3.13.0-57-generic
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-57-generic N/A
   linux-backports-modules-3.13.0-57-generic  N/A
   linux-firmware 1.127.19
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-07-21 (534 days ago)
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B16.1509081438
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B16.1509081438:bd09/0

[Kernel-packages] [Bug 1533351] Re: DLPAR operation fails on Bell adapter with Ubuntu 14.04.3 OS

2016-01-12 Thread Luciano Chavez

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

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

Title:
  DLPAR operation fails on Bell adapter with Ubuntu 14.04.3 OS

Status in linux-lts-utopic package in Ubuntu:
  Invalid

Bug description:
  == Comment: #0 - HARSHA THYAGARAJA  - 2015-11-06 
04:10:32 ==
  ---Problem Description---
  DLPAR operation fails on Bell adapter 
   
  Contact Information = hathy...@in.ibm.com, iranna.an...@in.ibm.com 
   
  ---uname output---
  Linux tuletapio1-lp5 3.13.0-67-generic #110-Ubuntu SMP Fri Oct 23 13:24:51 
UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8286-41A 
   
  ---Steps to Reproduce---

   Necessary packages installed are:
  devices.chrp.base.servicerm_2.5.0.1-15111_ppc64el.deb
  dynamicrm_2.0.1-3_ppc64el.deb
  rsct.core_3.2.0.6-15111_ppc64el.deb
  rsct.core.utils_3.2.0.6-15111_ppc64el.deb
  src_3.2.0.6-15111_ppc64el.deb

  On the OS:
   root@tuletapio1-lp5:~# startsrc -g rsct
  0513-059 The ctcas Subsystem has been started. Subsystem PID is 1382.
  0513-029 The ctrmc Subsystem is already active.
  Multiple instances are not supported.


  root@tuletapio1-lp5:~# startsrc -g rsct_rm
  0513-029 The IBM.MgmtDomainRM Subsystem is already active.
  Multiple instances are not supported.
  0513-059 The IBM.ERRM Subsystem has been started. Subsystem PID is 1389.
  0513-029 The IBM.HostRM Subsystem is already active.
  Multiple instances are not supported.
  0513-059 The IBM.AuditRM Subsystem has been started. Subsystem PID is 1390.
  0513-059 The IBM.SensorRM Subsystem has been started. Subsystem PID is 1393.
  0513-029 The IBM.DRM Subsystem is already active.
  Multiple instances are not supported.
  0513-029 The IBM.ServiceRM Subsystem is already active.
  Multiple instances are not supported.

  
   
  root@tuletapio1-lp5:~# lssrc -a
  Subsystem GroupPID Status 
   ctrmcrsct 921 active
   IBM.DRM  rsct_rm  1025active
   IBM.MgmtDomainRM rsct_rm  1130active
   IBM.HostRM   rsct_rm  1143active
   IBM.ServiceRMrsct_rm  1183active
   ctcasrsct 1382active
   IBM.ERRM rsct_rm  1389active
   IBM.AuditRM  rsct_rm  1390active
   IBM.SensorRM rsct_rm  1393active


  In the HMC:
  Run the command: 
  hscroot@pwrio-hmc:~> lshwres -r io -m tuletapio1-fsp --rsubtype slot --filter 
"lpar_names=tuletapio1-lp5-iranna"
  
unit_phys_loc=U78C9.001.WZS00CH,bus_id=24,phys_loc=C6,drc_index=21010018,lpar_name=tuletapio1-lp5-iranna,lpar_id=5,slot_io_pool_id=none,description=Quad
 Async EIA-232 PCI-Express 
Adapter,feature_codes=none,pci_vendor_id=114F,pci_device_id=00B6,pci_subs_vendor_id=114F,pci_subs_device_id=00B6,pci_class=,pci_revision_id=AA,bus_grouping=0,iop=0,parent_slot_drc_index=none,drc_name=U78C9.001.WZS00CH-P1-C6,interposer_present=0,interposer_pcie=0,lpar_assignment_capable=1,dynamic_lpar_assignment_capable=1

  
  hscroot@pwrio-hmc:~> chhwres -r io -m tuletapio1-fsp -o r --id 5 -l 21010018


  HSCL2929 The dynamic removal of I/O resources failed: The I/O slot dynamic 
partitioning operation failed.  Here are the I/O slot IDs that failed and the 
reasons for failure:
 
  Validating PHB DLPAR capability...yes.
  failed to open /sys/bus/pci/slots/U78C9.001.WZS00CH-P1-C6/power: No such file 
or directory
  failed to disable hotplug children
  kernel remove failed for PHB 24, rc = -1

  
  Observed in the terminal:

  Nov  4 05:26:43 tuletapio1-lp5 kernel: [  553.125671] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:44 tuletapio1-lp5 kernel: [  554.125766] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:45 tuletapio1-lp5 kernel: [  555.125862] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:46 tuletapio1-lp5 kernel: [  556.125957] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:47 tuletapio1-lp5 kernel: [  557.126052] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:48 tuletapio1-lp5 kernel: [  558.126148] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:49 tuletapio1-lp5 kernel: [  559.126243] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:50 tuletapio1-lp5 kernel: [  560.126338] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:51 tuletapio1-lp5 kernel: [  561.126432] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:52 tuletapio1-lp5 kernel: [  562.126527] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:53 tuletapio1-lp5 kernel: [  563.126622] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:54 tuletapio1-lp5 kernel: [  564.126717] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:55 tuletapio1-lp5 kernel: [  565.126813] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:56 tuletapio1-lp5 kernel: [  566.126908] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:57 tuletapio1-lp5 kernel: [  567.127004] rpadlpar

[Kernel-packages] [Bug 1532267] Re: Bluetooth Qualcomm Atheros QCA9565 / AR9565 [168c:0036] not recognized

2016-01-12 Thread Leonardo Marques Rodrigues

Christopher,

The command apt-cache policy linux-firmware, returned this output:

linux-firmware:
  Installed: 1.127.19
  Candidate: 1.127.19
  Version table:
 *** 1.127.19 0
500 http://br.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1.127.18 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
 1.127 0
500 http://br.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

Thank you for attention.

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

Title:
  Bluetooth Qualcomm Atheros QCA9565 / AR9565 [168c:0036]  not
  recognized

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have installed Ubuntu 14.04 on my Acer Aspire E5-573G, and the
  bluetooth was not recognized, but wifi is working perfectly. This
  problem occurred from kernel 3.19 - 4.4-rc8.

  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter [168c:0036] (rev 01)
   Subsystem: Lite-On Communications Inc Device [11ad:0803]
   Kernel driver in use: ath9k

  The result of lsusb;
  Bus 003 Device 002: ID 8087:8001 Intel Corp.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
  Bus 001 Device 003: ID 1bcf:2c81 Sunplus Innovation Technology Inc.
  Bus 001 Device 005: ID 046d:c534 Logitech, Inc.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-23-generic 4.2.0-23.28~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-23.28~14.04.1-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan  8 14:41:21 2016
  InstallationDate: Installed on 2015-12-25 (13 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-wily
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lmrodrigues   2174 F pulseaudio
   /dev/snd/controlC1:  lmrodrigues   2174 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=898c0089-7a66-4b09-b59b-0953113ce894
  InstallationDate: Installed on 2015-12-25 (15 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Acer Aspire E5-573G
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic 
root=UUID=37df17cf-666c-4aa5-b851-ef8e5f7ce3e4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-23.28~14.04.1-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-23-generic N/A
   linux-backports-modules-4.2.0-23-generic  N/A
   linux-firmware1.144+ar3012
  Tags:  trusty
  Uname: Linux 4.2.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.31
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  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.31:bd09/25/2015:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-573G
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532267/+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 1521678] Re: perf enahancements for ppc64

2016-01-12 Thread Steve Langasek

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

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

Title:
  perf enahancements for ppc64

Status in linux package in Ubuntu:
  New

Bug description:
  perf kvm stat record/report is not supported on powerpc currently.
  With perf kvm stat record/report analysis of kvm exit events and
  hypervisor calls can be done. The statistics for these events can be
  shown individually for each running VM in the host and can be very
  useful in giving an idea of the performance of a VM under a certain
  workload.

  This can show how many number of KVM exits have happened during a
  certain period of time. Along with the total number of exits, all the
  exits are grouped according to their specific exit reasons. Also,
  frequency for individual exit reasons is shown. Same can be done with
  hypervisor calls too.

  Updating this with two more features :
  - perf intr regs sampling support. Patches are currently in v3.
  https://lkml.org/lkml/2015/11/3/25

  - Guest symbol resolution:
  To enable perf kvm record for powerpc, we need to sample the instruction 
pointer from kvm guest_exit tracepoint. The patches for this feature are 
currently being sent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521678/+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 1521678] [NEW] perf enahancements for ppc64

You have been subscribed to a public bug:

perf kvm stat record/report is not supported on powerpc currently. With
perf kvm stat record/report analysis of kvm exit events and hypervisor
calls can be done. The statistics for these events can be shown
individually for each running VM in the host and can be very useful in
giving an idea of the performance of a VM under a certain workload.

This can show how many number of KVM exits have happened during a
certain period of time. Along with the total number of exits, all the
exits are grouped according to their specific exit reasons. Also,
frequency for individual exit reasons is shown. Same can be done with
hypervisor calls too.

Updating this with two more features :
- perf intr regs sampling support. Patches are currently in v3.
https://lkml.org/lkml/2015/11/3/25

- Guest symbol resolution:
To enable perf kvm record for powerpc, we need to sample the instruction 
pointer from kvm guest_exit tracepoint. The patches for this feature are 
currently being sent.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64 bot-comment bugnameltc-133242 severity-medium 
targetmilestone-inin1604
-- 
perf enahancements for ppc64
https://bugs.launchpad.net/bugs/1521678
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 1533023] Re: linux-lts-vivid: 3.19.0-45.51~14.04.1 -proposed tracker

All builds are complete, packages in this bug can be copied to
-proposed.

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 3.19.0-45.51~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 12. January 2016 02:02 UTC
- kernel-stable-phase:Prepare
- kernel-stable-phase-changed:Tuesday, 12. January 2016 02:02 UTC
  kernel-stable-master-bug:1532815
+ kernel-stable-phase:CopyToProposed
+ kernel-stable-Prepare-package-end:Tuesday, 12. January 2016 23:02 UTC
+ kernel-stable-Promote-to-proposed-start:Tuesday, 12. January 2016 23:02 UTC
+ kernel-stable-phase-changed:Tuesday, 12. January 2016 23:02 UTC

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 12. January 2016 02:02 UTC
  kernel-stable-master-bug:1532815
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 12. January 2016 23:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 12. January 2016 23:02 UTC
  kernel-stable-phase-changed:Tuesday, 12. January 2016 23:02 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1533023/+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 1533382] Missing required logs.

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

apport-collect 1533382

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

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

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

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

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

Title:
  A note on virtio blk and net modules

Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If VIRTIO_BLK and VIRTIO_NET become =m, instead of current =y the
  following should happen:

  VIRTIO_NET should be in the nic-modules udeb, and seeded into the d-i
  builds.

  VIRTIO_BLK can stay in block-modules-udeb, and in general is not
  needed in the d-i build, as it can be fetched over the VIRTIO_NET
  provided network.

  VIRTIO_BLK needs to be available (e.g. server udebs pool, for offline
  s390x installations)

  
  on the kernel side

  virtio-blk and virtio-nic most certainly need to be the in the "main"
  package of a flavor, and not in -extra.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1533382/+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 1506327] Re: ISST-KVM: R3-0: Tuleta: PowerKVM : flyg3 : Boot during installation hangs at "Booting Linux via __start()"

2016-01-12 Thread Steve Langasek

** Package changed: debian-installer (Ubuntu) => linux (Ubuntu)

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

Title:
  ISST-KVM: R3-0: Tuleta: PowerKVM : flyg3 : Boot during installation
  hangs at "Booting Linux via __start()"

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0  ==
  ---Problem Description---

  The installation of ubuntu1510 is hanging at the below given point:

  
  PowerKVM host info:

  [root@flykvm ~]# uname -a
  Linux flykvm 3.18.21-352.el7_1.pkvm3_1_0.3400.1.ppc64le #1 SMP Tue Sep 29 
13:30:10 CDT 2015 ppc64le ppc64le ppc64le GNU/Linux
  [root@flykvm ~]# 

  [root@flykvm ~]# 
  [root@flykvm ~]# cat /etc/os-release 
  NAME="IBM_PowerKVM"
  VERSION="3.1.0"
  ID=ibm_powerkvm
  VERSION_ID="3.1.0"
  BUILD_ID="35-beta"
  PRETTY_NAME="IBM_PowerKVM 3.1.0"
  ANSI_COLOR="0;34"
  CPE_NAME="cpe:/o:ibm:beta:pkvm3_1"
  [root@flykvm ~]#

  
  ---console logs---
  [root@flykvm ~]# virsh start --console flyg3
  Domain flyg3 started
  Connected to domain flyg3
  Escape character is ^]

  
  SLOF **
  QEMU Starting
   Build Date = Sep 21 2015 16:58:03
   FW Version = mockbuild@ release 20150921
   Press "s" to enter Open Firmware.

  Populating /vdevice methods
  Populating /vdevice/v-scsi@2000
 SCSI: Looking for devices
8002 CD-ROM   : "QEMU QEMU CD-ROM  2.3."
8001 DISK : "QEMU QEMU HARDDISK2.3."
8000 DISK : "QEMU QEMU HARDDISK2.3."
  Populating /vdevice/vty@30001000
  Populating /vdevice/nvram@7100
   00 2000 (D) : 106b 003fserial bus [ usb-ohci ]
   00 1000 (D) : 1af4 1000virtio [ net ]
   00 0800 (D) : 15b3 1011network [ network ]
  No NVRAM common partition, re-initializing...
  Scanning USB 
OHCI: initializing
  Using default console: /vdevice/vty@30001000
   
Welcome to Open Firmware

Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
This program and the accompanying materials are made available
under the terms of the BSD License available at
http://www.opensource.org/licenses/bsd-license.php

  
  Trying to load:  from: /vdevice/v-scsi@2000/disk@8000 ... 
  E3404: Not a bootable device!
  Trying to load:  from: /vdevice/v-scsi@2000/disk@8002 ...   
Successfully loaded
   

  
 GNU GRUB  version 2.02~beta2-28

   
++
   |*Install
| 
   | Rescue mode
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
| 
   
++

Use the ^ and v keys to select which entry is highlighted.  
Press enter to boot the selected OS, `e' to edit the commands   
before booting or `c' for a command-line.   

 

  
  OF stdout device is: /vdevice/vty@30001000
  Preparing to boot Linux version 4.2.0-14-generic (buildd@denneed03) (gcc 
version 5.2.1 20150930 (Ubuntu 5.2.1-19ubuntu1) ) #16-Ubuntu SMP Fri Oct 2 
05:18:10 UTC 2015 (Ubuntu 4.2.0-14.16-generic 4.2.2)
  Detected machine type: 0101
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/install/vmlinux tasks=standard 
pkgsel/language-pack-patterns= pkgsel/install-language-support=false --- quiet
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 043b
alloc_top: 3000
alloc_top_hi : 0001
rmo_top  : 3000
ram_top  : 0001
  instantiating rtas at 0x2fff... done
  prom_hold_cp

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

2016-01-12 Thread bugproxy

--- Comment From michael.neul...@au1.ibm.com 2016-01-12 17:17 EDT---
(In reply to comment #26)
> Canonical, can you please replace
>
> CONFIG_TICK_CPU_ACCOUNTING=y
> # CONFIG_VIRT_CPU_ACCOUNTING_NATIVE is not set
>
> by
>
> CONFIG_VIRT_CPU_ACCOUNTING=y
> # CONFIG_TICK_CPU_ACCOUNTING is not set
> CONFIG_VIRT_CPU_ACCOUNTING_NATIVE=y
>
> in the default ppc64le Linux kernel configuration file?

What's the actual bug?  Why does this config option cause it to not
sync?

I object to just flipping this config option. We need to root cause the
issue rather papering it over with this.  This config option improves
context swtiching time (for every process in the system), so I really
don't want to turn it off.

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

Title:
  Surelock GA2 SP1: capiredp01: cxl_init_adapter fails for CAPI devices
  :01:00.0 and 0005:01:00.0 after upgrading to 840.10 Platform
  firmware build fips840/b1208b_1604.840

Status in linux package in Ubuntu:
  New

Bug description:
  Problem Description
  
  I upgraded the Platform firmware to the 840.10 Platform firmware build 
(b1208b_1604.840) to prepare for Surelock GA2 SP1 testing.  After the upgrade, 
I used the ipmitool to power on capiredfsp.aus.stglabs.ibm.com and boot the 
Ubuntu 15.10 partition (capiredp01.aus.stglabs.ibm.com) in OPAL firmware mode.  
In petitboot, I saw messages for "cxl-pci :01:00.0: cxl_init_adapter 
failed: -5" and "cxl-pci 0005:01:00.0: cxl_init_adapter failed: -5."  After the 
partition started running, I didn't see any AFU devices in /dev/cxl/ or 
/sys/class/cxl/ although I was able to see PCI devices for the hardware 
accelerators (:01:00.0 and 0005:01:00.0) with the lspci command.

  ubuntu@capiredp01:~$ ls -l /dev/cxl/
  ls: cannot access /dev/cxl/: No such file or directory
  ubuntu@capiredp01:~$ ls -l /sys/class/cxl/
  total 0
  ubuntu@capiredp01:~$ sudo lscfg | grep -i afu
  ubuntu@capiredp01:~$ sudo lspci|egrep -i "04cf|0477"
  :01:00.0 Processing accelerators: IBM Device 04cf (rev 01)
  0005:01:00.0 Processing accelerators: IBM Device 04cf (rev 01)
  ubuntu@capiredp01:~$ lsscsi -g
  [0:0:0:0]enclosu IBM  VSBPD12M1 6GSAS03  -  /dev/sg1 
  [0:0:1:0]cd/dvd  IBM. RMBO0140512  RA65  /dev/sr0   /dev/sg2 
  [0:3:0:0]no dev  IBM  57D7001SISIOA0150  -  /dev/sg0 
  [1:0:0:0]enclosu IBM  VSBPD12M1 6GSAS03  -  /dev/sg4 
  [1:0:1:0]diskIBM  HUC109030CSS600  E5C6  /dev/sda   /dev/sg5 
  [1:0:2:0]diskIBM  HUC101212CSS600  A5AA  /dev/sdb   /dev/sg6 
  [1:0:3:0]diskIBM  HUC101212CSS600  A5AA  /dev/sdc   /dev/sg7 
  [1:0:4:0]diskIBM  HUC101212CSS600  A5AA  /dev/sdd   /dev/sg8 
  [1:0:5:0]diskIBM  ST1200MM0007 BF04  /dev/sde   /dev/sg9 
  [1:0:6:0]diskIBM  ST1200MM0007 BF04  /dev/sdf   /dev/sg10
  [1:3:0:0]no dev  IBM  57D7001SISIOA0150  -  /dev/sg3 

  
  This is a regression: the Linux kernel has failed to synchronize the PSL 
timebase.
  The corresponding error message is in the dmesg log attached in comment #4:

  [1.687586] PSL: Timebase sync: giving up!

  CAPI devices are not enabled, because of this failure.

  PSL Timebase sync should not be a requirement for CAPI initialization,
  nor should it make an initialized card become unavailable.  Currently,
  timebase is an unused function of CAPI with hopes of adoption in the
  future.  Support of this feature should be considered optional at this
  time.

  I'm not sure what the fastest way to fix this is, but it needs to be
  fixed as quickly as possible.  CAPI is broken in Ubuntu 15.10.

  I can reproduce the bug, regardless of the skiboot level, with recent kernels.
  Older kernels behave as expected, regardless of the skiboot level.

  Firmware is not the cause of the regression, and kernel probably is.
  I sent this out to the capi-linux distro too, but I'll comment here as well.  
I'm not sure what is being looked at to determine the PSL timebase sync failed. 
 As far as I know all PSL versions should support timebase.  The only timebase 
error the PSL logs is if CAPP returns a status that says timebase has an error. 
 I'd think if that is the issue that timebase has not been correctly enabled or 
sequenced correctly in the host CAPP.  The PSL can't be enabled for timebase 
until the CAPP unit in the host has been enabled.

  I have installed a recent mainline Linux kernel (4.4.0-rc8) on
  capiredp01. I have rebooted this kernel and verified that the PSL
  timebase syncs without problem.

  I will now compare the source code of Ubuntu kernel 4.2.0-19 (that
  hits the bug) with the source of mainline kernel 4.4.0-rc8 (that
  operates as expected).

  I have updated the Ubuntu kernel and modules with:

  $ sudo apt-get install linux-image-4

[Kernel-packages] [Bug 1533043] Re: AUFS can hang up; Please update to v20160111

2016-01-12 Thread Mike Atlas

For what it's worth, Dockerized containers running common open-source
applications (Cassandra, Mongo, Flynn) have stumbled hard on this - and
of course, it's not just on Ubuntu, but all Linux kernels with
296291cdd: https://bugzilla.kernel.org/show_bug.cgi?id=109971 -

Akihiro has been a champion in tracking down the cause, reproduction of
the problem, a patch, and pushing for a fix in all the right places.
Give this guy a high five or a beer if you know him in person, he's
helping a lot of people out with his efforts.

** Bug watch added: Linux Kernel Bug Tracker #109971
   http://bugzilla.kernel.org/show_bug.cgi?id=109971

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

Title:
  AUFS can hang up; Please update to v20160111

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  AUFS  can hang up (more precisely, produces unkillable processes) with some 
kernels that contain the commit 296291cdd1629c308114504b850dc343eabc278.
  - 14.04LTS:  
http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git/commit/?id=b8702f3cf9c06914476fb3206039131c2c3d8450
  - 15.04: 
http://kernel.ubuntu.com/git/ubuntu/ubuntu-vivid.git/commit/?id=6b08592b8acc677d5b9bb7986343fdd6e0ad3303
  - 15.10: 
http://kernel.ubuntu.com/git/ubuntu/ubuntu-wily.git/commit/?id=4d291df30fb7a94d13c6d38addf8d85d38f0111b

  Many docker users have been experiencing this issue:
  https://github.com/docker/docker/issues/18180

  
  The issue has been fixed since AUFS v20160111: 
http://permalink.gmane.org/gmane.linux.file-systems.aufs.user/5345
  So I suggest updating AUFS to v20160111.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533043/+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 1506327] [NEW] ISST-KVM: R3-0: Tuleta: PowerKVM : flyg3 : Boot during installation hangs at "Booting Linux via __start()"

You have been subscribed to a public bug:

== Comment: #0  ==
---Problem Description---

The installation of ubuntu1510 is hanging at the below given point:


PowerKVM host info:

[root@flykvm ~]# uname -a
Linux flykvm 3.18.21-352.el7_1.pkvm3_1_0.3400.1.ppc64le #1 SMP Tue Sep 29 
13:30:10 CDT 2015 ppc64le ppc64le ppc64le GNU/Linux
[root@flykvm ~]# 

[root@flykvm ~]# 
[root@flykvm ~]# cat /etc/os-release 
NAME="IBM_PowerKVM"
VERSION="3.1.0"
ID=ibm_powerkvm
VERSION_ID="3.1.0"
BUILD_ID="35-beta"
PRETTY_NAME="IBM_PowerKVM 3.1.0"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:ibm:beta:pkvm3_1"
[root@flykvm ~]#


---console logs---
[root@flykvm ~]# virsh start --console flyg3
Domain flyg3 started
Connected to domain flyg3
Escape character is ^]


SLOF **
QEMU Starting
 Build Date = Sep 21 2015 16:58:03
 FW Version = mockbuild@ release 20150921
 Press "s" to enter Open Firmware.

Populating /vdevice methods
Populating /vdevice/v-scsi@2000
   SCSI: Looking for devices
  8002 CD-ROM   : "QEMU QEMU CD-ROM  2.3."
  8001 DISK : "QEMU QEMU HARDDISK2.3."
  8000 DISK : "QEMU QEMU HARDDISK2.3."
Populating /vdevice/vty@30001000
Populating /vdevice/nvram@7100
 00 2000 (D) : 106b 003fserial bus [ usb-ohci ]
 00 1000 (D) : 1af4 1000virtio [ net ]
 00 0800 (D) : 15b3 1011network [ network ]
No NVRAM common partition, re-initializing...
Scanning USB 
  OHCI: initializing
Using default console: /vdevice/vty@30001000
 
  Welcome to Open Firmware

  Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
  This program and the accompanying materials are made available
  under the terms of the BSD License available at
  http://www.opensource.org/licenses/bsd-license.php


Trying to load:  from: /vdevice/v-scsi@2000/disk@8000 ... 
E3404: Not a bootable device!
Trying to load:  from: /vdevice/v-scsi@2000/disk@8002 ...   
Successfully loaded
 


   GNU GRUB  version 2.02~beta2-28

 ++
 |*Install| 
 | Rescue mode|
 ||
 ||
 ||
 ||
 ||
 ||
 ||
 ||
 ||
 || 
 ++

  Use the ^ and v keys to select which entry is highlighted.  
  Press enter to boot the selected OS, `e' to edit the commands   
  before booting or `c' for a command-line.   
   


OF stdout device is: /vdevice/vty@30001000
Preparing to boot Linux version 4.2.0-14-generic (buildd@denneed03) (gcc 
version 5.2.1 20150930 (Ubuntu 5.2.1-19ubuntu1) ) #16-Ubuntu SMP Fri Oct 2 
05:18:10 UTC 2015 (Ubuntu 4.2.0-14.16-generic 4.2.2)
Detected machine type: 0101
Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
Calling ibm,client-architecture-support... done
command line: BOOT_IMAGE=/install/vmlinux tasks=standard 
pkgsel/language-pack-patterns= pkgsel/install-language-support=false --- quiet
memory layout at init:
  memory_limit :  (16 MB aligned)
  alloc_bottom : 043b
  alloc_top: 3000
  alloc_top_hi : 0001
  rmo_top  : 3000
  ram_top  : 0001
instantiating rtas at 0x2fff... done
prom_hold_cpus: skipped
copying OF device tree...
Building dt strings...
Building dt structure...
Device tree strings 0x043c -> 0x043c0b7d
Device tree struct  0x043d -> 0x043e
Quiescing Open Firmware ...
Booting Linux via __start() ...---HUNG


[root@flykvm ~]# virsh dumpxml flyg3

  flyg3
  5f7bd054-6e7b-45e4-b0dc-9e8234ae13ac
  99090432
  6291456
  6291456
  
100139008
  
  32
  
/machine
  
  
hvm


  
  


  

  
  
  destroy
  restart
  restart
  
/usr/bin/qemu-sys

[Kernel-packages] [Bug 1533382] Re: A note on virtio blk and net modules

2016-01-12 Thread Dimitri John Ledkov

 xnox: Why did you add block-modules to generic/s390x.cfg?
 xnox: "Add block-modules (depends on virtio-modules) for s390x" 
seems pointless with the kernel change to make those builtin.  I think I'll 
revert that commit.
 xnox: Or was there some other reason?
* infinity shrugs and leaves it there for now.
* mwenning has quit (Quit: Leaving)
* foka_ (~f...@198-48-131-98.cpe.pppoe.ca) has joined
 infinity, so apw wanted to make it a module on all platforms, rather 
than changing it to =y on s390x.
 infinity, so i made the change, just in case. The net difference now is 
adding nbd module to the installer.
 infinity, i don't know if apw will revert it to a =m everywhere. If he 
does, we will need block-modules in all/most d-i flavours.
 xnox: It should still be in virtio-modules anyway (if it's =m), I'd 
say it's a bug that it was in block-modules.
 xnox: But this works for now, I won't be too picky (already uploaded 
your change).
 ok.
 infinity, let me point that virtio-blk was in the wrong package to apw. 
cause we were slightly dilusional about it.
 infinity, the whole bug was i went to boot cloud images, and virtio-blk 
was not in the initramfs, and was only in the -extra image
 xnox: Err, surely this was about virtio-net anyway?
 anyway all good now.
 xnox: virtio-blk shouldn't be needed to boot the installer, it 
should be fetched over the network.
 virtio-net and virtio-blk. Both were =m in -extra package and in 
block/virtio-udebs split
 and i do need virtio-net and virtio-blk in the cloud-images initramfs.
 virtio-blk can be fetched over the network true, in the d-i case.
 Right, moving them to -virtual (either in image or =y) is correct, 
and yes, you need them in the cloud-init initrd, but that has nothing to do 
with d-i.
 So, we probably should revert your change before we forget this 
conversation. :P
 right. and apw wants to drop them from =y -> =m everywhere, as otherwise 
they are always loaded, and never unloaded.
 And then make sure the kernel debs/udebs are correct if they go =m
 right.
 let me copy the irc log into a bug with actions to be done.
 I'm not convinced virtio-modules needs to exist at all, except maybe 
as a dep of block-modules and nic-modules, if it has some common bits.
 virtio-net should be in nic- and virtio-blk should be in block-, the 
more I think about it.
 There's nothing about those drivers that make them any more 
"special" than any other block or nic device.
 there is virtio-scsi and virtio-something else.
 in virtio-udebs.
 but yeah vitio-nic should be in nic-modules

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

Title:
  A note on virtio blk and net modules

Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  If VIRTIO_BLK and VIRTIO_NET become =m, instead of current =y the
  following should happen:

  VIRTIO_NET should be in the nic-modules udeb, and seeded into the d-i
  builds.

  VIRTIO_BLK can stay in block-modules-udeb, and in general is not
  needed in the d-i build, as it can be fetched over the VIRTIO_NET
  provided network.

  VIRTIO_BLK needs to be available (e.g. server udebs pool, for offline
  s390x installations)

  
  on the kernel side

  virtio-blk and virtio-nic most certainly need to be the in the "main"
  package of a flavor, and not in -extra.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1533382/+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 1533382] [NEW] A note on virtio blk and net modules

2016-01-12 Thread Dimitri John Ledkov

Public bug reported:

If VIRTIO_BLK and VIRTIO_NET become =m, instead of current =y the
following should happen:

VIRTIO_NET should be in the nic-modules udeb, and seeded into the d-i
builds.

VIRTIO_BLK can stay in block-modules-udeb, and in general is not needed
in the d-i build, as it can be fetched over the VIRTIO_NET provided
network.

VIRTIO_BLK needs to be available (e.g. server udebs pool, for offline
s390x installations)


on the kernel side

virtio-blk and virtio-nic most certainly need to be the in the "main"
package of a flavor, and not in -extra.

** Affects: debian-installer (Ubuntu)
 Importance: Undecided
 Status: New

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

** Also affects: debian-installer (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  A note on virtio blk and net modules

Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  If VIRTIO_BLK and VIRTIO_NET become =m, instead of current =y the
  following should happen:

  VIRTIO_NET should be in the nic-modules udeb, and seeded into the d-i
  builds.

  VIRTIO_BLK can stay in block-modules-udeb, and in general is not
  needed in the d-i build, as it can be fetched over the VIRTIO_NET
  provided network.

  VIRTIO_BLK needs to be available (e.g. server udebs pool, for offline
  s390x installations)

  
  on the kernel side

  virtio-blk and virtio-nic most certainly need to be the in the "main"
  package of a flavor, and not in -extra.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1533382/+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 1404409] Re: [regression] Intel 10Gb NIC Crashes

2016-01-12 Thread Richard Laager

This has been stable on all systems for quite some time now. I don't
know what fixed it. It might be the SR-IOV thing. I'm marking it
Incomplete, since I can't reproduce it any more.

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

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

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

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

Title:
  [regression] Intel 10Gb NIC Crashes

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Trusty:
  Incomplete
Status in linux source package in Utopic:
  Incomplete
Status in linux source package in Vivid:
  Incomplete

Bug description:
  I posted this to net...@vger.kernel.org as well:
  http://www.spinics.net/lists/netdev/msg309110.html

  I think the next step is to try to bisect this down to a specific commit. I'm 
starting to look at the instructions here:
  https://wiki.ubuntu.com/Kernel/KernelBisection

  -

  Previous history of this thread:
  http://thread.gmane.org/gmane.linux.network/326672

  On 2014-11-04 22:57:19, Tom Herbert wrote:
  > Using vlan and bonding? vlan_dev_hard_start_xmit called. A possible
  > cause is that bonding interface is out of sync with slave interface
  > w.r.t. GSO features. Do we know if this worked in 3.14, 3.15?

  I'm seeing the same sort of crash/warning (skb_war_bad_offload). It's
  happening on Intel 10 Gig NICs using the ixgbe driver. I'm using bridges
  (for virtual machines) on top of VLANs on top of 802.3ad bonding. I'm
  using an MTU of 9000 on the bond0 interface, but 1500 everywhere else.

  I'm always bonding two ports: one one system, I'm bonding two ports on
  identical one-port NICs; on another system, I'm bonding two ports on a
  single two-port NIC. Both systems exhibit the same behavior.

  Everything has worked fine for a couple years on Ubuntu 12.04 Precise
  (Linux 3.2.0). It immediately broke when I upgraded to Ubuntu 14.04
  Trusty (Linux 3.13.0). I can also reproduce this using the packaged
  version of Linux 3.16.0 on Trusty.

  In contrast to other reports of this bug, disabling scatter gather on
  the physical interfaces (e.g. eth0) does *not* stop the crashes
  (assuming I disabled it correctly).

  I currently have two systems (one with Precise, one with Trusty)
  available to do any testing that you'd find helpful.

  Here's a first pass at getting some debugging data.

  The broken system (Ubuntu 14.04 Trusty):

  rlaager@BROKEN:~$ uname -a
  Linux BROKEN 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC
  2014 x86_64 x86_64 x86_64 GNU/Linux

  rlaager@BROKEN:~$ ethtool -k p6p1
  Features for p6p1:
  rx-checksumming: on
  tx-checksumming: on
  tx-checksum-ipv4: on
  tx-checksum-ip-generic: off [fixed]
  tx-checksum-ipv6: on
  tx-checksum-fcoe-crc: on [fixed]
  tx-checksum-sctp: on
  scatter-gather: on
  tx-scatter-gather: on
  tx-scatter-gather-fraglist: off [fixed]
  tcp-segmentation-offload: on
  tx-tcp-segmentation: on
  tx-tcp-ecn-segmentation: off [fixed]
  tx-tcp6-segmentation: on
  udp-fragmentation-offload: off [fixed]
  generic-segmentation-offload: on
  generic-receive-offload: on
  large-receive-offload: off
  rx-vlan-offload: on
  tx-vlan-offload: on
  ntuple-filters: off
  receive-hashing: on
  highdma: on [fixed]
  rx-vlan-filter: on
  vlan-challenged: off [fixed]
  tx-lockless: off [fixed]
  netns-local: off [fixed]
  tx-gso-robust: off [fixed]
  tx-fcoe-segmentation: on [fixed]
  tx-gre-segmentation: off [fixed]
  tx-ipip-segmentation: off [fixed]
  tx-sit-segmentation: off [fixed]
  tx-udp_tnl-segmentation: off [fixed]
  tx-mpls-segmentation: off [fixed]
  fcoe-mtu: off [fixed]
  tx-nocache-copy: on
  loopback: off [fixed]
  rx-fcs: off [fixed]
  rx-all: off
  tx-vlan-stag-hw-insert: off [fixed]
  rx-vlan-stag-hw-parse: off [fixed]
  rx-vlan-stag-filter: off [fixed]
  l2-fwd-offload: off

  rlaager@BROKEN:~$ ethtool -k bond0
  Features for bond0:
  rx-checksumming: off [fixed]
  tx-checksumming: on
  tx-checksum-ipv4: off [fixed]
  tx-checksum-ip-generic: on
  tx-checksum-ipv6: off [fixed]
  tx-checksum-fcoe-crc: off [fixed]
  tx-checksum-sctp: off [fixed]
  scatter-gather: on
  tx-scatter-gather: on
  tx-scatter-gather-fraglist: off [requested on]
  tcp-segmentation-offload: on
  tx-tcp-segmentation: on
  tx-tcp-ecn-segmentation: on
  tx-tcp6-segmentation: on
  udp-fragmentation-offload: off [fixed]
  generic-segmentation-offload: on
  generic-receive-offload: on
  large-receive-offload: off
  rx-vlan-offload: on
  tx-vlan-offload: on
  ntuple-filters: off [fixed]
  receive-hashing: off [fixe

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

2016-01-12 Thread bugproxy

--- Comment From cha...@us.ibm.com 2016-01-12 16:25 EDT---
Hello Harsha,

The bug report states this problem occurred with 14.04.3 version
3.13.0-67 of the kernel. Does this problem also occur with the latest
Trusty linux-generic-lts-vivid 3.19.0.43.28 version? The code in
question was removed some time ago and so I think the patch mentioned is
not needed there. Please let us know what you see with this kernel.

https://launchpad.net/ubuntu/trusty/ppc64el/linux-generic-lts-vivid

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

Title:
  DLPAR operation fails on Bell adapter with Ubuntu 14.04.3 OS

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

Bug description:
  == Comment: #0 - HARSHA THYAGARAJA  - 2015-11-06 
04:10:32 ==
  ---Problem Description---
  DLPAR operation fails on Bell adapter 
   
  Contact Information = hathy...@in.ibm.com, iranna.an...@in.ibm.com 
   
  ---uname output---
  Linux tuletapio1-lp5 3.13.0-67-generic #110-Ubuntu SMP Fri Oct 23 13:24:51 
UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8286-41A 
   
  ---Steps to Reproduce---

   Necessary packages installed are:
  devices.chrp.base.servicerm_2.5.0.1-15111_ppc64el.deb
  dynamicrm_2.0.1-3_ppc64el.deb
  rsct.core_3.2.0.6-15111_ppc64el.deb
  rsct.core.utils_3.2.0.6-15111_ppc64el.deb
  src_3.2.0.6-15111_ppc64el.deb

  On the OS:
   root@tuletapio1-lp5:~# startsrc -g rsct
  0513-059 The ctcas Subsystem has been started. Subsystem PID is 1382.
  0513-029 The ctrmc Subsystem is already active.
  Multiple instances are not supported.


  root@tuletapio1-lp5:~# startsrc -g rsct_rm
  0513-029 The IBM.MgmtDomainRM Subsystem is already active.
  Multiple instances are not supported.
  0513-059 The IBM.ERRM Subsystem has been started. Subsystem PID is 1389.
  0513-029 The IBM.HostRM Subsystem is already active.
  Multiple instances are not supported.
  0513-059 The IBM.AuditRM Subsystem has been started. Subsystem PID is 1390.
  0513-059 The IBM.SensorRM Subsystem has been started. Subsystem PID is 1393.
  0513-029 The IBM.DRM Subsystem is already active.
  Multiple instances are not supported.
  0513-029 The IBM.ServiceRM Subsystem is already active.
  Multiple instances are not supported.

  
   
  root@tuletapio1-lp5:~# lssrc -a
  Subsystem GroupPID Status 
   ctrmcrsct 921 active
   IBM.DRM  rsct_rm  1025active
   IBM.MgmtDomainRM rsct_rm  1130active
   IBM.HostRM   rsct_rm  1143active
   IBM.ServiceRMrsct_rm  1183active
   ctcasrsct 1382active
   IBM.ERRM rsct_rm  1389active
   IBM.AuditRM  rsct_rm  1390active
   IBM.SensorRM rsct_rm  1393active


  In the HMC:
  Run the command: 
  hscroot@pwrio-hmc:~> lshwres -r io -m tuletapio1-fsp --rsubtype slot --filter 
"lpar_names=tuletapio1-lp5-iranna"
  
unit_phys_loc=U78C9.001.WZS00CH,bus_id=24,phys_loc=C6,drc_index=21010018,lpar_name=tuletapio1-lp5-iranna,lpar_id=5,slot_io_pool_id=none,description=Quad
 Async EIA-232 PCI-Express 
Adapter,feature_codes=none,pci_vendor_id=114F,pci_device_id=00B6,pci_subs_vendor_id=114F,pci_subs_device_id=00B6,pci_class=,pci_revision_id=AA,bus_grouping=0,iop=0,parent_slot_drc_index=none,drc_name=U78C9.001.WZS00CH-P1-C6,interposer_present=0,interposer_pcie=0,lpar_assignment_capable=1,dynamic_lpar_assignment_capable=1

  
  hscroot@pwrio-hmc:~> chhwres -r io -m tuletapio1-fsp -o r --id 5 -l 21010018


  HSCL2929 The dynamic removal of I/O resources failed: The I/O slot dynamic 
partitioning operation failed.  Here are the I/O slot IDs that failed and the 
reasons for failure:
 
  Validating PHB DLPAR capability...yes.
  failed to open /sys/bus/pci/slots/U78C9.001.WZS00CH-P1-C6/power: No such file 
or directory
  failed to disable hotplug children
  kernel remove failed for PHB 24, rc = -1

  
  Observed in the terminal:

  Nov  4 05:26:43 tuletapio1-lp5 kernel: [  553.125671] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:44 tuletapio1-lp5 kernel: [  554.125766] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:45 tuletapio1-lp5 kernel: [  555.125862] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:46 tuletapio1-lp5 kernel: [  556.125957] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:47 tuletapio1-lp5 kernel: [  557.126052] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:48 tuletapio1-lp5 kernel: [  558.126148] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:49 tuletapio1-lp5 kernel: [  559.126243] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:50 tuletapio1-lp5 kernel: [  560.126338] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:51 tuletapio1-lp5 kernel: [  561.126432] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:52 tuletapio1-lp5 kernel: [  562.126527] rpadlpar_io: slot PHB 
24 removed
  Nov

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

2016-01-12 Thread Michael

Hi all,

I've been following this bugreport for the past 6 months since I have the same 
problem on a backup server.
Running the latest Debian on a Hyper-V host. During the night there are several 
rsync backups going on. The issue only happens maybe once every 3 or 4 weeks 
because there's not much load on this server. The filesystem goes in ro mode 
and it has to be rebooted to get it working again. The same symptoms as have 
been described here several times...

Since jsalisbury has now a script to create the needed load to reproduce
the error within hours, I can always get a separate test VM running with
Debian or Ubuntu to test further possible fixes if wanted.

Just thought I'd post this, in the hope that people will continue
looking for a solution... There are plenty of people with this problem
it seems!

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1533351] Re: DLPAR operation fails on Bell adapter with Ubuntu 14.04.3 OS

2016-01-12 Thread Gary Gaydos

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

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

Title:
  DLPAR operation fails on Bell adapter with Ubuntu 14.04.3 OS

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

Bug description:
  == Comment: #0 - HARSHA THYAGARAJA  - 2015-11-06 
04:10:32 ==
  ---Problem Description---
  DLPAR operation fails on Bell adapter 
   
  Contact Information = hathy...@in.ibm.com, iranna.an...@in.ibm.com 
   
  ---uname output---
  Linux tuletapio1-lp5 3.13.0-67-generic #110-Ubuntu SMP Fri Oct 23 13:24:51 
UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8286-41A 
   
  ---Steps to Reproduce---

   Necessary packages installed are:
  devices.chrp.base.servicerm_2.5.0.1-15111_ppc64el.deb
  dynamicrm_2.0.1-3_ppc64el.deb
  rsct.core_3.2.0.6-15111_ppc64el.deb
  rsct.core.utils_3.2.0.6-15111_ppc64el.deb
  src_3.2.0.6-15111_ppc64el.deb

  On the OS:
   root@tuletapio1-lp5:~# startsrc -g rsct
  0513-059 The ctcas Subsystem has been started. Subsystem PID is 1382.
  0513-029 The ctrmc Subsystem is already active.
  Multiple instances are not supported.


  root@tuletapio1-lp5:~# startsrc -g rsct_rm
  0513-029 The IBM.MgmtDomainRM Subsystem is already active.
  Multiple instances are not supported.
  0513-059 The IBM.ERRM Subsystem has been started. Subsystem PID is 1389.
  0513-029 The IBM.HostRM Subsystem is already active.
  Multiple instances are not supported.
  0513-059 The IBM.AuditRM Subsystem has been started. Subsystem PID is 1390.
  0513-059 The IBM.SensorRM Subsystem has been started. Subsystem PID is 1393.
  0513-029 The IBM.DRM Subsystem is already active.
  Multiple instances are not supported.
  0513-029 The IBM.ServiceRM Subsystem is already active.
  Multiple instances are not supported.

  
   
  root@tuletapio1-lp5:~# lssrc -a
  Subsystem GroupPID Status 
   ctrmcrsct 921 active
   IBM.DRM  rsct_rm  1025active
   IBM.MgmtDomainRM rsct_rm  1130active
   IBM.HostRM   rsct_rm  1143active
   IBM.ServiceRMrsct_rm  1183active
   ctcasrsct 1382active
   IBM.ERRM rsct_rm  1389active
   IBM.AuditRM  rsct_rm  1390active
   IBM.SensorRM rsct_rm  1393active


  In the HMC:
  Run the command: 
  hscroot@pwrio-hmc:~> lshwres -r io -m tuletapio1-fsp --rsubtype slot --filter 
"lpar_names=tuletapio1-lp5-iranna"
  
unit_phys_loc=U78C9.001.WZS00CH,bus_id=24,phys_loc=C6,drc_index=21010018,lpar_name=tuletapio1-lp5-iranna,lpar_id=5,slot_io_pool_id=none,description=Quad
 Async EIA-232 PCI-Express 
Adapter,feature_codes=none,pci_vendor_id=114F,pci_device_id=00B6,pci_subs_vendor_id=114F,pci_subs_device_id=00B6,pci_class=,pci_revision_id=AA,bus_grouping=0,iop=0,parent_slot_drc_index=none,drc_name=U78C9.001.WZS00CH-P1-C6,interposer_present=0,interposer_pcie=0,lpar_assignment_capable=1,dynamic_lpar_assignment_capable=1

  
  hscroot@pwrio-hmc:~> chhwres -r io -m tuletapio1-fsp -o r --id 5 -l 21010018


  HSCL2929 The dynamic removal of I/O resources failed: The I/O slot dynamic 
partitioning operation failed.  Here are the I/O slot IDs that failed and the 
reasons for failure:
 
  Validating PHB DLPAR capability...yes.
  failed to open /sys/bus/pci/slots/U78C9.001.WZS00CH-P1-C6/power: No such file 
or directory
  failed to disable hotplug children
  kernel remove failed for PHB 24, rc = -1

  
  Observed in the terminal:

  Nov  4 05:26:43 tuletapio1-lp5 kernel: [  553.125671] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:44 tuletapio1-lp5 kernel: [  554.125766] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:45 tuletapio1-lp5 kernel: [  555.125862] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:46 tuletapio1-lp5 kernel: [  556.125957] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:47 tuletapio1-lp5 kernel: [  557.126052] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:48 tuletapio1-lp5 kernel: [  558.126148] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:49 tuletapio1-lp5 kernel: [  559.126243] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:50 tuletapio1-lp5 kernel: [  560.126338] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:51 tuletapio1-lp5 kernel: [  561.126432] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:52 tuletapio1-lp5 kernel: [  562.126527] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:53 tuletapio1-lp5 kernel: [  563.126622] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:54 tuletapio1-lp5 kernel: [  564.126717] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:55 tuletapio1-lp5 kernel: [  565.126813] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:56 tuletapio1-lp5 kernel: [  566.126908] rpadlpar_io: slot PHB 
24 removed
  Nov  4 05:26:57 tuletapio1-lp5 kernel: [  567.127004] rpadlpar_io: slot PHB 
24 r

[Kernel-packages] [Bug 1533351] [NEW] DLPAR operation fails on Bell adapter with Ubuntu 14.04.3 OS

You have been subscribed to a public bug:

== Comment: #0 - HARSHA THYAGARAJA  - 2015-11-06 04:10:32 
==
---Problem Description---
DLPAR operation fails on Bell adapter 
 
Contact Information = hathy...@in.ibm.com, iranna.an...@in.ibm.com 
 
---uname output---
Linux tuletapio1-lp5 3.13.0-67-generic #110-Ubuntu SMP Fri Oct 23 13:24:51 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = 8286-41A 
 
---Steps to Reproduce---

 Necessary packages installed are:
devices.chrp.base.servicerm_2.5.0.1-15111_ppc64el.deb
dynamicrm_2.0.1-3_ppc64el.deb
rsct.core_3.2.0.6-15111_ppc64el.deb
rsct.core.utils_3.2.0.6-15111_ppc64el.deb
src_3.2.0.6-15111_ppc64el.deb

On the OS:
 root@tuletapio1-lp5:~# startsrc -g rsct
0513-059 The ctcas Subsystem has been started. Subsystem PID is 1382.
0513-029 The ctrmc Subsystem is already active.
Multiple instances are not supported.


root@tuletapio1-lp5:~# startsrc -g rsct_rm
0513-029 The IBM.MgmtDomainRM Subsystem is already active.
Multiple instances are not supported.
0513-059 The IBM.ERRM Subsystem has been started. Subsystem PID is 1389.
0513-029 The IBM.HostRM Subsystem is already active.
Multiple instances are not supported.
0513-059 The IBM.AuditRM Subsystem has been started. Subsystem PID is 1390.
0513-059 The IBM.SensorRM Subsystem has been started. Subsystem PID is 1393.
0513-029 The IBM.DRM Subsystem is already active.
Multiple instances are not supported.
0513-029 The IBM.ServiceRM Subsystem is already active.
Multiple instances are not supported.


 
root@tuletapio1-lp5:~# lssrc -a
Subsystem GroupPID Status 
 ctrmcrsct 921 active
 IBM.DRM  rsct_rm  1025active
 IBM.MgmtDomainRM rsct_rm  1130active
 IBM.HostRM   rsct_rm  1143active
 IBM.ServiceRMrsct_rm  1183active
 ctcasrsct 1382active
 IBM.ERRM rsct_rm  1389active
 IBM.AuditRM  rsct_rm  1390active
 IBM.SensorRM rsct_rm  1393active


In the HMC:
Run the command: 
hscroot@pwrio-hmc:~> lshwres -r io -m tuletapio1-fsp --rsubtype slot --filter 
"lpar_names=tuletapio1-lp5-iranna"
unit_phys_loc=U78C9.001.WZS00CH,bus_id=24,phys_loc=C6,drc_index=21010018,lpar_name=tuletapio1-lp5-iranna,lpar_id=5,slot_io_pool_id=none,description=Quad
 Async EIA-232 PCI-Express 
Adapter,feature_codes=none,pci_vendor_id=114F,pci_device_id=00B6,pci_subs_vendor_id=114F,pci_subs_device_id=00B6,pci_class=,pci_revision_id=AA,bus_grouping=0,iop=0,parent_slot_drc_index=none,drc_name=U78C9.001.WZS00CH-P1-C6,interposer_present=0,interposer_pcie=0,lpar_assignment_capable=1,dynamic_lpar_assignment_capable=1


hscroot@pwrio-hmc:~> chhwres -r io -m tuletapio1-fsp -o r --id 5 -l 21010018


HSCL2929 The dynamic removal of I/O resources failed: The I/O slot dynamic 
partitioning operation failed.  Here are the I/O slot IDs that failed and the 
reasons for failure:
   
Validating PHB DLPAR capability...yes.
failed to open /sys/bus/pci/slots/U78C9.001.WZS00CH-P1-C6/power: No such file 
or directory
failed to disable hotplug children
kernel remove failed for PHB 24, rc = -1


Observed in the terminal:

Nov  4 05:26:43 tuletapio1-lp5 kernel: [  553.125671] rpadlpar_io: slot PHB 24 
removed
Nov  4 05:26:44 tuletapio1-lp5 kernel: [  554.125766] rpadlpar_io: slot PHB 24 
removed
Nov  4 05:26:45 tuletapio1-lp5 kernel: [  555.125862] rpadlpar_io: slot PHB 24 
removed
Nov  4 05:26:46 tuletapio1-lp5 kernel: [  556.125957] rpadlpar_io: slot PHB 24 
removed
Nov  4 05:26:47 tuletapio1-lp5 kernel: [  557.126052] rpadlpar_io: slot PHB 24 
removed
Nov  4 05:26:48 tuletapio1-lp5 kernel: [  558.126148] rpadlpar_io: slot PHB 24 
removed
Nov  4 05:26:49 tuletapio1-lp5 kernel: [  559.126243] rpadlpar_io: slot PHB 24 
removed
Nov  4 05:26:50 tuletapio1-lp5 kernel: [  560.126338] rpadlpar_io: slot PHB 24 
removed
Nov  4 05:26:51 tuletapio1-lp5 kernel: [  561.126432] rpadlpar_io: slot PHB 24 
removed
Nov  4 05:26:52 tuletapio1-lp5 kernel: [  562.126527] rpadlpar_io: slot PHB 24 
removed
Nov  4 05:26:53 tuletapio1-lp5 kernel: [  563.126622] rpadlpar_io: slot PHB 24 
removed
Nov  4 05:26:54 tuletapio1-lp5 kernel: [  564.126717] rpadlpar_io: slot PHB 24 
removed
Nov  4 05:26:55 tuletapio1-lp5 kernel: [  565.126813] rpadlpar_io: slot PHB 24 
removed
Nov  4 05:26:56 tuletapio1-lp5 kernel: [  566.126908] rpadlpar_io: slot PHB 24 
removed
Nov  4 05:26:57 tuletapio1-lp5 kernel: [  567.127004] rpadlpar_io: slot PHB 24 
removed
Nov  4 05:26:58 tuletapio1-lp5 kernel: [  568.127099] rpadlpar_io: slot PHB 24 
removed
Nov  4 05:26:59 tuletapio1-lp5 kernel: [  569.127193] rpadlpar_io: slot PHB 24 
removed

The terminal dumps above messages continuously that the adapter has been
removed but lspci -nn still showed the entry for the adapter

root@tuletapio1-lp5:~# lspci -nn
01:00.0 PCI bridge [0604]: PLX Technology, Inc. PEX8112 x1 Lane PCI 
Express-to-PCI Bridge [10b5:8112] (rev ff)
02:00.0 Serial control

[Kernel-packages] [Bug 1529654] Re: Ubuntu 14.04 3.13.0.74-generic keyboard doesn't respond; okay in 3.13.0.71

David Ing, in order to avoid diagnosing the dependency issue when
attempting to use the enablement stack (just to see if the issue is
resolved in it), you may want to simply reinstall with a later version
of Ubuntu where this issue is confirmed to already be fixed. ISOs are
available at http://releases.ubuntu.com/ . This would also benefit you
when doing future in-place upgrades.

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

Title:
  Ubuntu 14.04 3.13.0.74-generic keyboard doesn't respond; okay in
  3.13.0.71

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I booted the computer this morning, the keyboard and mouse
  (actually a Lenovo keyboard with trackpoint) wouldn't respond.  I
  swapped keyboards, and got the same problem.

  This is happening under kernel 3.13.0.74-generic.  When I use grub to
  boot under the previous 3.13.0.71 kernel, things are working fine.

  In the past few days, I had noticed that dpkg errors were holding up
  updates, so I did repairs and updates worked fine.

  I am typing this from the computer booted under 3.13.0.71-generic, and
  obviously can not do so under 3.13.0.74-generic.

  -

  $ lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  What I expected to happen:  After boot, keyboard and mouse should
  respond.

  What happened instead:  This computer has Mate Desktop installed on top of 
Ubuntu 14.04.  The Mate Desktop appears, but the keyboard and mouse 
(trackpoint) do not respond.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  daviding   1877 F pulseaudio
   /dev/snd/controlC2:  daviding   1877 F pulseaudio
   /dev/snd/controlC0:  daviding   1877 F pulseaudio
   /dev/snd/pcmC0D0p:   daviding   1877 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7168f469-6882-4d5b-991f-5a6b711c844f
  InstallationDate: Installed on 2014-08-29 (498 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=a8ed2bff-1f42-41d5-805e-1f7c2472853c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  WifiSyslog: Jan 10 12:29:37 m5a88 kernel: [11681.824137] 
systemd-hostnamed[3332]: Warning: nss-myhostname is not installed. Changing the 
local hostname might make it unresolveable. Please install nss-myhostname!
  _MarkForUpload: True
  dmi.bios.date: 05/01/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1702
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A88-M
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1702:bd05/01/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A88-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1529654/+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 1525324] Re: kernel/bonding: wrong netlink messages when deleting a bonding interface

Nicolas Dichtel, could you please attach the requested information as
outlined in
https://help.ubuntu.com/community/ReportingBugs#Filing_bugs_when_offline_or_using_a_headless_setup
?

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

Title:
  kernel/bonding: wrong netlink messages when deleting a bonding
  interface

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Here is the bug:

  root@ubuntu1404:~# modprobe bonding
  root@ubuntu1404:~# modprobe dummy
  root@ubuntu1404:~# ip link set dummy0 master bond0
  root@ubuntu1404:~# ip monitor link&
  [1] 1065
  root@ubuntu1404:~# ip link del bond0
  Deleted 6: bond0:  mtu 1500 qdisc noop state DOWN 
group default 
  link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
  7: dummy0:  mtu 1500 qdisc noqueue state 
UNKNOWN group default 
  link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
  7: dummy0:  mtu 1500 qdisc noqueue state UNKNOWN 
group default 
  link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
  6: bond0:  mtu 1500 qdisc noop state DOWN group 
default 
  link/ether e6:49:16:3b:17:fe brd ff:ff:ff:ff:ff:ff
  6: bond0:  mtu 1500 qdisc noop state DOWN group 
default 
  root@ubuntu1404:~# link/ether e6:49:16:3b:17:fe brd ff:ff:ff:ff:ff:ff
  7: dummy0:  mtu 1500 qdisc noqueue state DOWN group default 
  link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
  7: dummy0:  mtu 1500 qdisc noqueue state DOWN group default 
  link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
  ^C
  root@ubuntu1404:~# uname -a
  Linux ubuntu1404 3.13.0-71-generic #114-Ubuntu SMP Tue Dec 1 02:34:22 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux
  root@ubuntu1404:~#

  A netlink message advertise that bond0 is deleted and after that two
  netlink messages are sent telling that bond0 exists again.

  This bug has been fixed by these upstream commits:
  56bfa7ee7c88 unregister_netdevice : move RTM_DELLINK to until after ndo_uninit
  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=56bfa7ee7c88
  395eea6ccf2b rtnetlink: delay RTM_DELLINK notification until after 
ndo_uninit()
  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=395eea6ccf2b

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525324/+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 1386490] Re: HP ProLiant m400 nic doesn't work after trusty

2016-01-12 Thread Bjorn Helgaas

The git link in comment #17 is stale because it references a branch
name, which is often re-used.

I think
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?h=9a6d7298b0833614c411f774c46514efb1bd5651
is a permanent link to the same thing.

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

Title:
  HP ProLiant m400 nic doesn't work after trusty

Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Utopic:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in debian-installer source package in Vivid:
  Fix Released
Status in linux source package in Vivid:
  Fix Released

Bug description:
  Starting in 3.15, arm64 began defaulting to non-coherent dma_ops:

  commit c7a4a7658d689f664050c45493d79adf053f226e
  Author: Ritesh Harjani 
  Date:   Wed Apr 23 06:29:46 2014 +0100

  arm64: Make default dma_ops to be noncoherent

  Firmware (dtb in the case of the m400) is responsible for telling the
  kernel when a device requires coherent dma_ops. However, as of utopic,
  this property is not being inherited by downstream devices.
  Specifically, the xgene-pcie device is marked as coherent, but the
  devices behind it (mellanox card) still get initialized with non-
  coherent ops.

  This results in the mlx4 driver bailing out with the following messages:
  [   18.703635] mlx4_core :01:00.0: command 0x23 timed out (go bit not 
cleared)
  [   18.710911] mlx4_core :01:00.0: Failed to initialize queue pair table, 
aborting

  
  There's an upstream discussion on the topic here:
http://www.spinics.net/lists/arm-kernel/msg362320.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1386490/+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 1520040] Re: [drm:gen8_irq_handler [i915_bpo]] ERROR The master control interrupt lied (SDE)!

Johan De Meersman, 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/1520040

Title:
  [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt
  lied (SDE)!

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Device: notebook Dell Inspiron 5548

  Operating system: 64-bit XUbuntu Linux 14.04 LTS

  Processor: Intel Core i7-5500U

  Kernel: 3.19.0-33-generic #38~14.04.1-Ubuntu SMP x86_64

  Video: dual chip. These are the two display controllers:
  - Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260] display 
controller 3300Hz (requires kernel module / device driver "fglrx"); and
  - Intel Corporation Broadwell-U Integrated Graphics VGA compatible controller 
3300Hz (requires kernel module / device driver "i915").

  Problem: my notebook's operating system is switching to runlevel 0
  (power off) randomly, subtly and thus unexpectedly. And if I 'cat
  /var/log/kern.log |grep -i i915' I get a lot of "[drm:gen8_irq_handler
  [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!"
  messages. I'm under the impression that either the kernel or the
  kernel module "i915_bpo" is buggy.

  My notebook's problem can't be related to overheating, because it's a
  brand-new notebook (less than 1 month old) and I've already monitored
  its temperature parameters: nothing abnormal is happening. Also, I'm
  using a cooling laptop base/pad.

  Other kernels I've tested, with which the same issue happens:
  - 3.19.0-18-generic (kernel module: i915_bpo)
  - 3.19.0-23-generic (kernel module: i915_bpo)
  - 3.19.0-28-generic (kernel module: i915_bpo)
  - 4.2.0-18-generic (kernel module: i915)

  Temporary workaround: I downgraded to kernel "3.13.0-36-generic",
  which isn't buggy with its "i915_bdw.ko" (version 3.0) kernel object
  (module). Full path for this module:
  /lib/modules/3.13.0-36-generic/kernel/ubuntu/i915/i915_bdw.ko

  Notes:
  - "bdw" stands for "Broadwell"
  - "bpo", I believe, stands for "backport"

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-33-generic 3.19.0-33.38~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  NonfreeKernelModules: wl fglrx
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Nov 25 23:44:39 2015
  InstallationDate: Installed on 2015-11-03 (22 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yuriyrs2832 F pulseaudio
   /dev/snd/controlC1:  yuriyrs2832 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=a08f36f9-0611-4894-9da9-8b1dcc960a86
  InstallationDate: Installed on 2015-11-03 (24 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Inspiron 5548
  NonfreeKernelModules: fglrx wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-33-generic.efi.signed 
root=UUID=4f05c2b3-c971-4bf8-bcb6-a76d60b68e45 ro quiet splash 
video.use_native_backlight=1 intremap=no_x2apic_optout vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-33-generic N/A
   linux-backports-modules-3.19.0-33-generic  N/A
   linux-firmware 1.127.18
  Tags:  trusty
  Uname: Linux 3.19.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy fuse lpadmin netdev 
plugdev sambashare scanner sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 10/12/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0YDTG3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A06
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd10/12/2015:svnDellInc.:pnInspiron5548:pvrA06:rvnDellInc.:rn0YDTG3:rvrA02:cvnDellInc.:ct8:cvrA06:
  dmi.product.name: Inspiron 5548
  dmi.product.version: A06
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1036704] Re: Unable to configure device with bluez-simple-agent

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

Title:
  Unable to configure device with bluez-simple-agent

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Unable to use bluez-simple-agent to set up connection in Xubuntu 12.04
  on Asus T91m laptop with internal or USB Bluetooth hardware.

  onebir@T91:~$ lsb_release -rd
  Description:  Ubuntu 12.04.1 LTS
  Release:  12.04
  onebir@T91:~$ apt-cache show bluez python-gobject python-dbus | egrep 
"Package|Version"
  Package: bluez
  Version: 4.98-2ubuntu7
  Package: python-gobject
  Version: 3.2.2-1~precise
  Package: python-gobject
  Version: 3.2.0-3
  Package: python-dbus
  Version: 1.0.0-1ubuntu1

  #Trying inbulit card - not sure of hardware
  onebir@T91:~$ hcitool dev
  Devices:
  hci000:25:D3:A4:4A:A7
  onebir@T91:~$ hcitool scan
  Scanning ...
  onebir@T91:~$ sudo bluez-simple-agent hci 00:25:D3:A4:4A:A7
  [sudo] password for bir:
  Traceback (most recent call last):
File "/usr/bin/bluez-simple-agent", line 102, in 
  path = manager.FindAdapter(args[0])
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in 
__call__
  return self._proxy_method(*args, **keywords)
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in 
__call__
  **keywords)
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in 
call_blocking
  message, timeout)
  dbus.exceptions.DBusException: org.bluez.Error.NoSuchAdapter: No such adapter

  # Plug in USB Bluetooth dongle  as used in *
  onebir@T91:~$ hcitool dev
  Devices:
  hci000:25:D3:A4:4A:A7
  hci100:1F:81:00:08:30
  onebir@T91:~$ sudo bluez-simple-agent hci 00:1F:81:00:08:30
  Traceback (most recent call last):
File "/usr/bin/bluez-simple-agent", line 102, in 
  path = manager.FindAdapter(args[0])
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in 
__call__
  return self._proxy_method(*args, **keywords)
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in 
__call__
  **keywords)
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in 
call_blocking
  message, timeout)
  dbus.exceptions.DBusException: org.bluez.Error.NoSuchAdapter: No such adapter

  *https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1036106

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1036704/+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 1036106] Re: Unable to configure device with bluez-simple-agent

2016-01-12 Thread Brian Murray

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

** This bug has been marked a duplicate of bug 1036704
   Unable to configure device with bluez-simple-agent

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

Title:
  Unable to configure device with bluez-simple-agent

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Note - I'm having this problem on Xubuntu 11.10 - apologies if this is
  in the wrong place.

  1) Built-in bluetooth
  onebir@dell640m:~/Desktop$ lsb_release -rd
  Description:  Ubuntu 11.10
  Release:  11.10
  onebir@dell640m:~/Desktop$ lsusb | grep -i bluetooth
  Bus 003 Device 002: ID 413c:8103 Dell Computer Corp. Wireless 350 Bluetooth
  onebir@dell640m:~/Desktop$ hcitool dev
  Devices:
hci100:16:41:57:F5:55
  onebir@dell640m:~/Desktop$ sudo hcitool scan
  [sudo] password for onebir: 
  Scanning ...
  $

  Looks ok, so decided to go through BluetoothSetup in Ubuntu docs (using 11.04 
instructions, latest available):
  onebir@dell640m:~$ sudo apt-get install bluez python-gobject python-dbus
  ...snip...
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  # But what are the newest versions...
  onebir@dell640m:~$ apt-cache show bluez python-gobject python-dbus  |egrep 
"Package|Version"
  Package: bluez
  Version: 4.96-0ubuntu3
  Package: python-dbus
  Version: 0.84.0-2
  Package: python-gobject
  Version: 3.0.0-0ubuntu2
  Package: bluez
  Version: 4.96-0ubuntu4
  Package: python-gobject
  Version: 3.0.0-0ubuntu4
  # Why two versions of bluez & python-gobject? :s Anyway...
  onebir@dell640m:~$ hcitool dev
  Devices:
hci100:16:41:57:F5:55
  onebir@dell640m:~$ sudo bluez-simple-agent hci1 00:16:41:57:F5:55
  Creating device failed: org.bluez.Error.ConnectionAttemptFailed: Page Timeout

  2) Plugged in $2 USB dongle to retry.
  onebir@dell640m:~$ lsusb
  ...snip...
  Bus 003 Device 002: ID 413c:8103 Dell Computer Corp. Wireless 350 Bluetooth
  Bus 004 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
  onebir@dell640m:~$ hcitool dev
  Devices:
hci000:16:41:57:F5:55 # built-in one
hci100:1F:81:00:08:30 # USB one
  onebir@dell640m:~$ sudo bluez-simple-agent hci1 00:1F:81:00:08:30
  [sudo] password for onebir: 
  Creating device failed: org.bluez.Error.ConnectionAttemptFailed: Page Timeout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1036106/+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 1527902] Re: 3.13.0-71: IPv6 UDP DNS packets are not received

2016-01-12 Thread Kamal Mostafa

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

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

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

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

** Also affects: linux (Ubuntu Xenial)
   Importance: High
 Assignee: Kamal Mostafa (kamalmostafa)
   Status: In Progress

** Also affects: linux-lts-trusty (Ubuntu Xenial)
   Importance: High
 Assignee: Kamal Mostafa (kamalmostafa)
   Status: In Progress

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

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

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

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

** No longer affects: linux-lts-trusty (Ubuntu Trusty)

** No longer affects: linux-lts-trusty (Ubuntu Vivid)

** No longer affects: linux-lts-trusty (Ubuntu Wily)

** No longer affects: linux-lts-trusty (Ubuntu Xenial)

** No longer affects: linux (Ubuntu Precise)

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

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

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

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

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

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

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

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

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

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

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

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

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

Title:
  3.13.0-71: IPv6 UDP DNS packets are not received

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-lts-trusty package in Ubuntu:
  In Progress
Status in linux-lts-utopic package in Ubuntu:
  Fix Committed
Status in linux-lts-trusty source package in Precise:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  After upgrading linux kernel from version 3.13.0-68 to 3.13.0-71 then
  Kopete (IM messenger) stopped working, cannot connect to any jabber
  server.

  I started debugging this problem and found out that, problem resolve
  when I boot back 3.13.0-68 kernel version (without touching any system
  files or packages). When I boot 3.13.0-71 Kopete always does not
  connect.

  Next I debugged that problem on 3.13.0-71 is just when
  /etc/resolv.conf contains only IPv6 addresses of DNS servers.

  Problem is comes down to dns resolver (jabber in Kopete has its own
  for SRV records) and syscall recvfrom() (on IPv6 socket) always return
  error -EAGAIN without any data returned. But wireshark see that DNS
  response was recevied.

  So it looks like that after 3.13.0-68 kernel was included some change
  which broke receiving UDP packets via IPv6 socket. IPv4 is OK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527902/+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 1533304] Re: Kernel Bug: IPv6 Neighbor Discovery

2016-01-12 Thread Joseph Ishac

This is not a kernel crash or panic but rather a behavior bug.
Furthermore, our test machines do not have Internet access.  If there is
particular information that would aid in this report, please note it
directly.

Kernel in use:
$ uname -srv
Linux 3.13.0-74-generic #118-Ubuntu SMP Thu Dec 17 22:52:10 UTC 2015

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

Title:
  Kernel Bug: IPv6 Neighbor Discovery

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We have discovered what appears to be a bug with the handling of ICMP6
  router solicitations on tun interfaces in the Linux kernel.  In
  particular, if an application is not immediately bound to the tun
  interface, router solicitations are never sent out of the interface.
  This issue can be replicated easily using the attached scripts.

  First, a tun interface is created with permissions for the local user,
  sudo is used so the script will prompt for the user password.

  $ bash rftun0_create.sh
  rftun0 created
  16: rftun0:  mtu 1500 qdisc noop state DOWN 
group default qlen 500
  link/none 

  Then the interface is configured, given an address, and brought "up"
  however since there is no application bound to the interface yet there
  is no carrier.

  $ bash rftun0_up.sh
  net.ipv6.conf.rftun0.forwarding = 0
  net.ipv6.conf.rftun0.accept_ra = 1
  net.ipv6.conf.rftun0.autoconf = 1
  net.ipv6.conf.rftun0.accept_ra_rt_info_max_plen = 128
  net.ipv6.conf.rftun0.accept_ra_rtr_pref = 1
  net.ipv6.conf.rftun0.router_solicitation_delay = 1
  net.ipv6.conf.rftun0.router_solicitation_interval = 2
  net.ipv6.conf.rftun0.router_solicitations = 200
  rftun0 up
  16: rftun0:  mtu 1400 qdisc 
pfifo_fast state DOWN group default qlen 500
  link/none 
  inet6 fe80::600:4339:125f:760c/64 scope link 
 valid_lft forever preferred_lft forever

  
  A simple client is then run to bind to the tun interface and read the first 
three packets.  If things are going well we should see 3 router solicitations, 
however we instead see no traffic.

  $ python simple_tun_client.py 
  Timed out...
  Timed out...
  Timed out...

  If we bring the interface down and try again with no delay between
  bringing the interface up and binding the application we see things
  work as expected.

  $ bash rftun0_down.sh 

  rftun0 down
  16: rftun0:  mtu 1400 qdisc pfifo_fast state 
DOWN group default qlen 500
  link/none 

  $ bash rftun0_up.sh && python simple_tun_client.py 
  net.ipv6.conf.rftun0.forwarding = 0
  net.ipv6.conf.rftun0.accept_ra = 1
  net.ipv6.conf.rftun0.autoconf = 1
  net.ipv6.conf.rftun0.accept_ra_rt_info_max_plen = 128
  net.ipv6.conf.rftun0.accept_ra_rtr_pref = 1
  net.ipv6.conf.rftun0.router_solicitation_delay = 1
  net.ipv6.conf.rftun0.router_solicitation_interval = 2
  net.ipv6.conf.rftun0.router_solicitations = 200
  rftun0 up
  16: rftun0:  mtu 1400 qdisc 
pfifo_fast state DOWN group default qlen 500
  link/none 
  inet6 fe80::600:1512:6243:38fe/64 scope link 
 valid_lft forever preferred_lft forever
  Read packet from tunnel. 48 bytes.
  
60083afffe8006001512624338feff0200028500c6e3
  Read packet from tunnel. 48 bytes.
  
60083afffe8006001512624338feff0200028500c6e3
  Read packet from tunnel. 48 bytes.
  
60083afffe8006001512624338feff0200028500c6e3

  Furthermore, I can rerun the simple client and continue to receive
  router solicitations.

  Attempting the same procedure again with a small delay replicates the
  original issue.  Notice the sleep statement in between the rftun0_up
  script and the simple tun client.

  $ bash rftun0_down.sh 
  rftun0 down
  16: rftun0:  mtu 1400 qdisc pfifo_fast state 
DOWN group default qlen 500
  link/none 

  $ bash rftun0_up.sh && sleep 5 && python simple_tun_client.py 

  net.ipv6.conf.rftun0.forwarding = 0
  net.ipv6.conf.rftun0.accept_ra = 1
  net.ipv6.conf.rftun0.autoconf = 1
  net.ipv6.conf.rftun0.accept_ra_rt_info_max_plen = 128
  net.ipv6.conf.rftun0.accept_ra_rtr_pref = 1
  net.ipv6.conf.rftun0.router_solicitation_delay = 1
  net.ipv6.conf.rftun0.router_solicitation_interval = 2
  net.ipv6.conf.rftun0.router_solicitations = 200
  rftun0 up
  16: rftun0:  mtu 1400 qdisc 
pfifo_fast state DOWN group default qlen 500
  link/none 
  inet6 fe80::600:25f2:67d0:37fc/64 scope link 
 valid_lft forever preferred_lft forever
  Timed out...
  Timed out...
  Timed out...

  This test can be repeated as necessary.  On my system, sleep times of
  2 seconds or larger seem to always produce the issue, while sleep
  times of 1 s

[Kernel-packages] [Bug 1532928] Re: linux-ti-omap4: 3.2.0-1476.99 -proposed tracker

All builds are complete, packages in this bug can be copied to
-proposed.

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

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

Title:
  linux-ti-omap4: 3.2.0-1476.99 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 11. January 2016 20:00 UTC
  kernel-stable-master-bug:1532774
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 12. January 2016 16:01 UTC
  kernel-stable-phase-changed:Tuesday, 12. January 2016 16:01 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 12. January 2016 16:01 UTC
  kernel-stable-Certification-testing-end:Tuesday, 12. January 2016 16:01 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1532928/+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 1532956] Re: linux-lts-trusty: 3.13.0-75.119~precise1 -proposed tracker

All builds are complete, packages in this bug can be copied to
-proposed.

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 3.13.0-75.119~precise1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 11. January 2016 21:02 UTC
- kernel-stable-phase:Prepare
- kernel-stable-phase-changed:Monday, 11. January 2016 21:02 UTC
  kernel-stable-master-bug:1532781
+ kernel-stable-phase:CopyToProposed
+ kernel-stable-Prepare-package-end:Tuesday, 12. January 2016 19:02 UTC
+ kernel-stable-Promote-to-proposed-start:Tuesday, 12. January 2016 19:02 UTC
+ kernel-stable-phase-changed:Tuesday, 12. January 2016 19:02 UTC

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

Title:
  linux-lts-trusty: 3.13.0-75.119~precise1 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-75.119~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 11. January 2016 21:02 UTC
  kernel-stable-master-bug:1532781
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 12. January 2016 19:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 12. January 2016 19:02 UTC
  kernel-stable-phase-changed:Tuesday, 12. January 2016 19:02 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1532956/+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 1533323] Re: Linux kernel holds lost ethernet connections

2016-01-12 Thread Patrik Nilsson

** Description changed:

  If a connection to a router is lost while you have active ethernet
  connections to hosts (on the Internet), networking can't be resumed
  before all connections are closed. Many software packages repeatedly try
  to resume their lost connections, which must lead to a human
  intervention to quit all software before the connection to the router is
  re-established.
  
  Seems as it is the kernel that prevents connections to the router, by
  holding lost connections.
  
  Even if you in disable networking by selecting "Enable Networking" from
  the drop down menu, and re-enable it, you can't get through to the
  router before all user software has quit and closed all connections
  holding the lost host connections.
  
- This bug has existed for a long time, but I have never learnt what the
- error could be.
+ This bug has existed for a long time(=years), but I have never learnt
+ what the error could be.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-43-generic 3.19.0-43.49
  ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-43-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  patrik 1870 F pulseaudio
-  /dev/snd/controlC1:  patrik 1870 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  patrik 1870 F pulseaudio
+  /dev/snd/controlC1:  patrik 1870 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 12 19:51:10 2016
  HibernationDevice: RESUME=UUID=541b29a6-2b6e-4caa-989c-9eb69dca7d9f
  InstallationDate: Installed on 2015-07-12 (184 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Acer Aspire V3-331
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-43-generic 
root=/dev/mapper/hostname--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-3.19.0-43-generic N/A
-  linux-backports-modules-3.19.0-43-generic  N/A
-  linux-firmware 1.143.7
+  linux-restricted-modules-3.19.0-43-generic N/A
+  linux-backports-modules-3.19.0-43-generic  N/A
+  linux-firmware 1.143.7
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V3-331
  dmi.board.vendor: Acer
  dmi.board.version: V1.05
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd06/09/2014:svnAcer:pnAspireV3-331:pvrV1.05:rvnAcer:rnAspireV3-331:rvrV1.05:cvnAcer:ct10:cvrV1.05:
  dmi.product.name: Aspire V3-331
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer

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

Title:
  Linux kernel holds lost ethernet connections

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  If a connection to a router is lost while you have active ethernet
  connections to hosts (on the Internet), networking can't be resumed
  before all connections are closed. Many software packages repeatedly
  try to resume their lost connections, which must lead to a human
  intervention to quit all software before the connection to the router
  is re-established.

  Seems as it is the kernel that prevents connections to the router, by
  holding lost connections.

  Even if you in disable networking by selecting "Enable Networking"
  from the drop down menu, and re-enable it, you can't get through to
  the router before all user software has quit and closed all
  connections holding the lost host connections.

  This bug has existed for a long time(=years), but I have never learnt
  what the error could be.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-43-generic 3.19.0-43.49
  ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-43-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrik 1870 F pulseaudio
   /dev/snd/controlC1:  patrik 1870 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 12 19:51:10 2016
  HibernationDevice: RESUME=UUID=541b29a6-2b6e-4caa-989c-9eb69dca7d9f
  InstallationDate: Installed on 2015-07-12 (184 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Acer Aspire V3-331
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-43-generic 
root=/dev/mapper/hostname--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-43-g

[Kernel-packages] [Bug 1533023] Re: linux-lts-vivid: 3.19.0-45.51~14.04.1 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 12. January 2016 02:02 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 12. January 2016 02:02 UTC
  kernel-stable-master-bug:1532815

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1533023/+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 1533323] [NEW] Linux kernel holds lost ethernet connections

2016-01-12 Thread Patrik Nilsson

Public bug reported:

If a connection to a router is lost while you have active ethernet
connections to hosts (on the Internet), networking can't be resumed
before all connections are closed. Many software packages repeatedly try
to resume their lost connections, which must lead to a human
intervention to quit all software before the connection to the router is
re-established.

Seems as it is the kernel that prevents connections to the router, by
holding lost connections.

Even if you in disable networking by selecting "Enable Networking" from
the drop down menu, and re-enable it, you can't get through to the
router before all user software has quit and closed all connections
holding the lost host connections.

This bug has existed for a long time(=years), but I have never learnt
what the error could be.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-43-generic 3.19.0-43.49
ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10
Uname: Linux 3.19.0-43-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  patrik 1870 F pulseaudio
 /dev/snd/controlC1:  patrik 1870 F pulseaudio
CurrentDesktop: Unity
Date: Tue Jan 12 19:51:10 2016
HibernationDevice: RESUME=UUID=541b29a6-2b6e-4caa-989c-9eb69dca7d9f
InstallationDate: Installed on 2015-07-12 (184 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Acer Aspire V3-331
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-43-generic 
root=/dev/mapper/hostname--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-43-generic N/A
 linux-backports-modules-3.19.0-43-generic  N/A
 linux-firmware 1.143.7
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/09/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.05
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Aspire V3-331
dmi.board.vendor: Acer
dmi.board.version: V1.05
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.05
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd06/09/2014:svnAcer:pnAspireV3-331:pvrV1.05:rvnAcer:rnAspireV3-331:rvrV1.05:cvnAcer:ct10:cvrV1.05:
dmi.product.name: Aspire V3-331
dmi.product.version: V1.05
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug vivid

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

Title:
  Linux kernel holds lost ethernet connections

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  If a connection to a router is lost while you have active ethernet
  connections to hosts (on the Internet), networking can't be resumed
  before all connections are closed. Many software packages repeatedly
  try to resume their lost connections, which must lead to a human
  intervention to quit all software before the connection to the router
  is re-established.

  Seems as it is the kernel that prevents connections to the router, by
  holding lost connections.

  Even if you in disable networking by selecting "Enable Networking"
  from the drop down menu, and re-enable it, you can't get through to
  the router before all user software has quit and closed all
  connections holding the lost host connections.

  This bug has existed for a long time(=years), but I have never learnt
  what the error could be.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-43-generic 3.19.0-43.49
  ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-43-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrik 1870 F pulseaudio
   /dev/snd/controlC1:  patrik 1870 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 12 19:51:10 2016
  HibernationDevice: RESUME=UUID=541b29a6-2b6e-4caa-989c-9eb69dca7d9f
  InstallationDate: Installed on 2015-07-12 (184 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Acer Aspire V3-331
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-43-generic 
root=/dev/mapper/hostname--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-43-generic N/A
   linux-backports-modules-3.19.0-43-generic  N/A
   linux-firmware 1.143.7
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V3-331
  dmi.board.vendor: Acer
  dmi.board.ve

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

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

Title:
  Linux kernel holds lost ethernet connections

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  If a connection to a router is lost while you have active ethernet
  connections to hosts (on the Internet), networking can't be resumed
  before all connections are closed. Many software packages repeatedly
  try to resume their lost connections, which must lead to a human
  intervention to quit all software before the connection to the router
  is re-established.

  Seems as it is the kernel that prevents connections to the router, by
  holding lost connections.

  Even if you in disable networking by selecting "Enable Networking"
  from the drop down menu, and re-enable it, you can't get through to
  the router before all user software has quit and closed all
  connections holding the lost host connections.

  This bug has existed for a long time(=years), but I have never learnt
  what the error could be.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-43-generic 3.19.0-43.49
  ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-43-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrik 1870 F pulseaudio
   /dev/snd/controlC1:  patrik 1870 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 12 19:51:10 2016
  HibernationDevice: RESUME=UUID=541b29a6-2b6e-4caa-989c-9eb69dca7d9f
  InstallationDate: Installed on 2015-07-12 (184 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Acer Aspire V3-331
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-43-generic 
root=/dev/mapper/hostname--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-43-generic N/A
   linux-backports-modules-3.19.0-43-generic  N/A
   linux-firmware 1.143.7
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V3-331
  dmi.board.vendor: Acer
  dmi.board.version: V1.05
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd06/09/2014:svnAcer:pnAspireV3-331:pvrV1.05:rvnAcer:rnAspireV3-331:rvrV1.05:cvnAcer:ct10:cvrV1.05:
  dmi.product.name: Aspire V3-331
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533323/+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 1359689] Re: cryptsetup password prompt not shown

2016-01-12 Thread shr00mie

i'm trying to install 15.10 and this problem is present from install.

i7 3770
GTX 680

probably need to tool around with /etc/default/grub and see if one of
those configs will work, but would be nice if one didn't have to go
through a grub customization to get this to work out of the box.

initially with default driver it looks like this
http://i.imgur.com/ENT4Buv.jpg

after installing prep nvidia driver and setting the i think it was gfx_payload 
option to my resolution, i was able to get the normal looking screen, but input 
appeared as plain text in the top left corner of the screen and did absolutely 
nothing.
http://i.imgur.com/akiQuU9.jpg

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

Title:
  cryptsetup password prompt not shown

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Triaged

Bug description:
  Currently in utopic the following happens when booting an encrypted
  setup:

  Press enter in grub, after a while screen freezes (or turns completely
  black) and stays like that. When I press the down key, I can see the
  password prompt. When I press the up key again, I get to the graphical
  password prompt.

  This is demonstrated in the following screencast:
  https://drive.google.com/file/d/0B7EMvd1LJKgZREJocHBueEhpa2s/edit?usp=sharing

  Maybe this is related to the version of plymouth utopic currently uses, a 
similar debian bug report seems to be resolved with a newer version 0.9.0-6, 
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752752.
  --- 
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-08-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821)
  Package: plymouth 0.9.0-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Tags:  utopic
  Uname: Linux 3.16.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-08-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821)
  MachineType: Dell Inc. Precision M4600
  Package: plymouth 0.9.0-0ubuntu3
  PackageArchitecture: amd64
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic 
root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ 
cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu
 quiet splash vt.handoff=7
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic 
root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ 
cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu
 quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Tags:  utopic
  TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  Uname: Linux 3.16.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/10/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd03/10/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689/+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 1531747] Re: overlay: mkdir fails if directory exists in lowerdir in a user namespace

2016-01-12 Thread Seth Forshee

On Tue, Jan 12, 2016 at 05:16:28PM -, Serge Hallyn wrote:
> in ovl_clear_empty(), the opaque bit is set on the dir in workingdir
> 
> in ovl_create_over_whiteout() (the case we're currently looking at) it is
> also being set in the working dir.
> 
> in ovl_rename2(), it is set in two places, on the upper dentries for
> both the old and new.
> 
> So it is never set on the lowerdir, at least.

Ah. So if it's never set on the lowerdir that does remove much of the
concern.

> I'm still looking, but it may be safe to say that all needed inode
> checks are already done before we call ovl_set_opaque() so that we
> can indeed just use prepare_kernel_cred(NULL) instead of prepare_cred().

Cool.

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

Title:
  overlay: mkdir fails if directory exists in lowerdir in a user
  namespace

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

Bug description:
  If a directory exists in the lowerdir but not in the mounted
  overlay, then mkdir of the directory in the target dir results
  in a mysterious -EPERM.  I've seen this both in wily kernel
  (4.2.0-22-generic #27-Ubuntu) and in a hand-built xenial
  master-next (with unrelated patches added).

  =
  #!/bin/sh -ex
  dir=`mktemp -d`
  cleanup() {
   umount -l $dir/t
   rm -rf $dir
  }

  trap cleanup EXIT

  echo "dir is $dir"
  mkdir -p $dir/l $dir/u $dir/w $dir/t
  mkdir $dir/l/dev
  mount -t overlay -o lowerdir=$dir/l,upperdir=$dir/u,workdir=$dir/w o $dir/t
  stat $dir/t/dev
  rmdir $dir/t/dev
  mkdir $dir/t/dev
  echo $?
  echo "mkdir should have succeeded"
  =

  The above will work on the host, but fail in a user namespace, i.e
  in a regular lxd container.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1531747/+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 1531747] Re: overlay: mkdir fails if directory exists in lowerdir in a user namespace

2016-01-12 Thread Seth Forshee

On Tue, Jan 12, 2016 at 04:56:24PM -, Serge Hallyn wrote:
> Quoting Seth Forshee (seth.forshee...@canonical.com):
> > I don't know why #2 is that much grosser than what's there now. It's
> 
> I didn't mean gross as in eeuw, I meant not fine-grained enough.
> 
> Because the capability will apply to inode permissions checks,
> and we only want it to be used for the check authorizing the
> writing of the trusted.overlay.opaque xattr.

That makes more sense. And that's the part that concerns me the most
too.

> > already only taking the cap for setting the xattr, and taking
> > CAP_SYS_ADMIN in init_user_ns seems to be what it's really wanting to do
> 
> Maybe - that's what I'm not sure about.  As you said earlier, in the
> upstream code only an admin can do the actual mount.  The fact that an
> unpriv user can create the mount may change assumptions about the
> underlying fs's.

Yeah, that's something I'm just not sure about. It seems like by
allowing the unprivileged user to mount in the first place we're
implicitly saying that it's okay to write these xattrs to the underlying
fs based on checks which happen at mount time. I don't know what checks
are actually done at mount time though; unless we've augmented them they
may be minimal based on the assumption that only CAP_SYS_ADMIN can
mount.

> > If we were to use ns_capable, which namespace do we use?
> 
> I don't know.  We're almost better off shipping a new version of
> vfs_xattr() which is only for use by kernel writers.

Maybe so.

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

Title:
  overlay: mkdir fails if directory exists in lowerdir in a user
  namespace

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

Bug description:
  If a directory exists in the lowerdir but not in the mounted
  overlay, then mkdir of the directory in the target dir results
  in a mysterious -EPERM.  I've seen this both in wily kernel
  (4.2.0-22-generic #27-Ubuntu) and in a hand-built xenial
  master-next (with unrelated patches added).

  =
  #!/bin/sh -ex
  dir=`mktemp -d`
  cleanup() {
   umount -l $dir/t
   rm -rf $dir
  }

  trap cleanup EXIT

  echo "dir is $dir"
  mkdir -p $dir/l $dir/u $dir/w $dir/t
  mkdir $dir/l/dev
  mount -t overlay -o lowerdir=$dir/l,upperdir=$dir/u,workdir=$dir/w o $dir/t
  stat $dir/t/dev
  rmdir $dir/t/dev
  mkdir $dir/t/dev
  echo $?
  echo "mkdir should have succeeded"
  =

  The above will work on the host, but fail in a user namespace, i.e
  in a regular lxd container.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1531747/+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 1533304] [NEW] Kernel Bug: IPv6 Neighbor Discovery

2016-01-12 Thread Joseph Ishac

Public bug reported:

We have discovered what appears to be a bug with the handling of ICMP6
router solicitations on tun interfaces in the Linux kernel.  In
particular, if an application is not immediately bound to the tun
interface, router solicitations are never sent out of the interface.
This issue can be replicated easily using the attached scripts.

First, a tun interface is created with permissions for the local user,
sudo is used so the script will prompt for the user password.

$ bash rftun0_create.sh
rftun0 created
16: rftun0:  mtu 1500 qdisc noop state DOWN group 
default qlen 500
link/none 

Then the interface is configured, given an address, and brought "up"
however since there is no application bound to the interface yet there
is no carrier.

$ bash rftun0_up.sh
net.ipv6.conf.rftun0.forwarding = 0
net.ipv6.conf.rftun0.accept_ra = 1
net.ipv6.conf.rftun0.autoconf = 1
net.ipv6.conf.rftun0.accept_ra_rt_info_max_plen = 128
net.ipv6.conf.rftun0.accept_ra_rtr_pref = 1
net.ipv6.conf.rftun0.router_solicitation_delay = 1
net.ipv6.conf.rftun0.router_solicitation_interval = 2
net.ipv6.conf.rftun0.router_solicitations = 200
rftun0 up
16: rftun0:  mtu 1400 qdisc 
pfifo_fast state DOWN group default qlen 500
link/none 
inet6 fe80::600:4339:125f:760c/64 scope link 
   valid_lft forever preferred_lft forever


A simple client is then run to bind to the tun interface and read the first 
three packets.  If things are going well we should see 3 router solicitations, 
however we instead see no traffic.

$ python simple_tun_client.py 
Timed out...
Timed out...
Timed out...

If we bring the interface down and try again with no delay between
bringing the interface up and binding the application we see things work
as expected.

$ bash rftun0_down.sh   
  
rftun0 down
16: rftun0:  mtu 1400 qdisc pfifo_fast state DOWN 
group default qlen 500
link/none 

$ bash rftun0_up.sh && python simple_tun_client.py 
net.ipv6.conf.rftun0.forwarding = 0
net.ipv6.conf.rftun0.accept_ra = 1
net.ipv6.conf.rftun0.autoconf = 1
net.ipv6.conf.rftun0.accept_ra_rt_info_max_plen = 128
net.ipv6.conf.rftun0.accept_ra_rtr_pref = 1
net.ipv6.conf.rftun0.router_solicitation_delay = 1
net.ipv6.conf.rftun0.router_solicitation_interval = 2
net.ipv6.conf.rftun0.router_solicitations = 200
rftun0 up
16: rftun0:  mtu 1400 qdisc 
pfifo_fast state DOWN group default qlen 500
link/none 
inet6 fe80::600:1512:6243:38fe/64 scope link 
   valid_lft forever preferred_lft forever
Read packet from tunnel. 48 bytes.
60083afffe8006001512624338feff0200028500c6e3
Read packet from tunnel. 48 bytes.
60083afffe8006001512624338feff0200028500c6e3
Read packet from tunnel. 48 bytes.
60083afffe8006001512624338feff0200028500c6e3

Furthermore, I can rerun the simple client and continue to receive
router solicitations.

Attempting the same procedure again with a small delay replicates the
original issue.  Notice the sleep statement in between the rftun0_up
script and the simple tun client.

$ bash rftun0_down.sh 
rftun0 down
16: rftun0:  mtu 1400 qdisc pfifo_fast state DOWN 
group default qlen 500
link/none 

$ bash rftun0_up.sh && sleep 5 && python simple_tun_client.py   
  
net.ipv6.conf.rftun0.forwarding = 0
net.ipv6.conf.rftun0.accept_ra = 1
net.ipv6.conf.rftun0.autoconf = 1
net.ipv6.conf.rftun0.accept_ra_rt_info_max_plen = 128
net.ipv6.conf.rftun0.accept_ra_rtr_pref = 1
net.ipv6.conf.rftun0.router_solicitation_delay = 1
net.ipv6.conf.rftun0.router_solicitation_interval = 2
net.ipv6.conf.rftun0.router_solicitations = 200
rftun0 up
16: rftun0:  mtu 1400 qdisc 
pfifo_fast state DOWN group default qlen 500
link/none 
inet6 fe80::600:25f2:67d0:37fc/64 scope link 
   valid_lft forever preferred_lft forever
Timed out...
Timed out...
Timed out...

This test can be repeated as necessary.  On my system, sleep times of 2
seconds or larger seem to always produce the issue, while sleep times of
1 second seem to work most of the time.

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


** Tags: kernel-bug

** Attachment added: "Contains the scripts used in the writeup"
   
https://bugs.launchpad.net/bugs/1533304/+attachment/4548681/+files/scripts.tgz

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

Title:
  Kernel Bug: IPv6 Neighbor Discovery

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We have discovered what appears to be a bug with the handling of ICMP6
  router solicitations on tun interfaces in the Linux kernel.  In
  particular, if an application is not immediately bound to the tun
  interface, router solicitations are never se

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

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

apport-collect 1533304

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

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

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

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

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

Title:
  Kernel Bug: IPv6 Neighbor Discovery

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We have discovered what appears to be a bug with the handling of ICMP6
  router solicitations on tun interfaces in the Linux kernel.  In
  particular, if an application is not immediately bound to the tun
  interface, router solicitations are never sent out of the interface.
  This issue can be replicated easily using the attached scripts.

  First, a tun interface is created with permissions for the local user,
  sudo is used so the script will prompt for the user password.

  $ bash rftun0_create.sh
  rftun0 created
  16: rftun0:  mtu 1500 qdisc noop state DOWN 
group default qlen 500
  link/none 

  Then the interface is configured, given an address, and brought "up"
  however since there is no application bound to the interface yet there
  is no carrier.

  $ bash rftun0_up.sh
  net.ipv6.conf.rftun0.forwarding = 0
  net.ipv6.conf.rftun0.accept_ra = 1
  net.ipv6.conf.rftun0.autoconf = 1
  net.ipv6.conf.rftun0.accept_ra_rt_info_max_plen = 128
  net.ipv6.conf.rftun0.accept_ra_rtr_pref = 1
  net.ipv6.conf.rftun0.router_solicitation_delay = 1
  net.ipv6.conf.rftun0.router_solicitation_interval = 2
  net.ipv6.conf.rftun0.router_solicitations = 200
  rftun0 up
  16: rftun0:  mtu 1400 qdisc 
pfifo_fast state DOWN group default qlen 500
  link/none 
  inet6 fe80::600:4339:125f:760c/64 scope link 
 valid_lft forever preferred_lft forever

  
  A simple client is then run to bind to the tun interface and read the first 
three packets.  If things are going well we should see 3 router solicitations, 
however we instead see no traffic.

  $ python simple_tun_client.py 
  Timed out...
  Timed out...
  Timed out...

  If we bring the interface down and try again with no delay between
  bringing the interface up and binding the application we see things
  work as expected.

  $ bash rftun0_down.sh 

  rftun0 down
  16: rftun0:  mtu 1400 qdisc pfifo_fast state 
DOWN group default qlen 500
  link/none 

  $ bash rftun0_up.sh && python simple_tun_client.py 
  net.ipv6.conf.rftun0.forwarding = 0
  net.ipv6.conf.rftun0.accept_ra = 1
  net.ipv6.conf.rftun0.autoconf = 1
  net.ipv6.conf.rftun0.accept_ra_rt_info_max_plen = 128
  net.ipv6.conf.rftun0.accept_ra_rtr_pref = 1
  net.ipv6.conf.rftun0.router_solicitation_delay = 1
  net.ipv6.conf.rftun0.router_solicitation_interval = 2
  net.ipv6.conf.rftun0.router_solicitations = 200
  rftun0 up
  16: rftun0:  mtu 1400 qdisc 
pfifo_fast state DOWN group default qlen 500
  link/none 
  inet6 fe80::600:1512:6243:38fe/64 scope link 
 valid_lft forever preferred_lft forever
  Read packet from tunnel. 48 bytes.
  
60083afffe8006001512624338feff0200028500c6e3
  Read packet from tunnel. 48 bytes.
  
60083afffe8006001512624338feff0200028500c6e3
  Read packet from tunnel. 48 bytes.
  
60083afffe8006001512624338feff0200028500c6e3

  Furthermore, I can rerun the simple client and continue to receive
  router solicitations.

  Attempting the same procedure again with a small delay replicates the
  original issue.  Notice the sleep statement in between the rftun0_up
  script and the simple tun client.

  $ bash rftun0_down.sh 
  rftun0 down
  16: rftun0:  mtu 1400 qdisc pfifo_fast state 
DOWN group default qlen 500
  link/none 

  $ bash rftun0_up.sh && sleep 5 && python simple_tun_client.py 

  net.ipv6.conf.rftun0.forwarding = 0
  net.ipv6.conf.rftun0.accept_ra = 1
  net.ipv6.conf.rftun0.autoconf = 1
  net.ipv6.conf.rftun0.accept_ra_rt_info_max_plen = 128
  net.ipv6.conf.rftun0.accept_ra_rtr_pref = 1
  net.ipv6.conf.rftun0.router_solicitation_delay = 1
  net.ipv6.conf.rftun0.router_solicitation_interval = 2
  net.ipv6.conf.rftun0.router_solicitations = 200
  rftun0 up
  16: rftun0:  mtu 1400 qdisc 
pfifo_fast state DOWN group default qlen 500
  link/none 
  inet6 fe80::600:25f2:67d0:37fc/64 scope link 
 valid_lft forever preferred_lft forever
  Timed out...
  Timed out...
  Timed out...

  This test can be rep

Re: [Kernel-packages] [Bug 1531747] Re: overlay: mkdir fails if directory exists in lowerdir in a user namespace

2016-01-12 Thread Serge Hallyn

in ovl_clear_empty(), the opaque bit is set on the dir in workingdir

in ovl_create_over_whiteout() (the case we're currently looking at) it is
also being set in the working dir.

in ovl_rename2(), it is set in two places, on the upper dentries for
both the old and new.

So it is never set on the lowerdir, at least.

I'm still looking, but it may be safe to say that all needed inode
checks are already done before we call ovl_set_opaque() so that we
can indeed just use prepare_kernel_cred(NULL) instead of prepare_cred().

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

Title:
  overlay: mkdir fails if directory exists in lowerdir in a user
  namespace

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

Bug description:
  If a directory exists in the lowerdir but not in the mounted
  overlay, then mkdir of the directory in the target dir results
  in a mysterious -EPERM.  I've seen this both in wily kernel
  (4.2.0-22-generic #27-Ubuntu) and in a hand-built xenial
  master-next (with unrelated patches added).

  =
  #!/bin/sh -ex
  dir=`mktemp -d`
  cleanup() {
   umount -l $dir/t
   rm -rf $dir
  }

  trap cleanup EXIT

  echo "dir is $dir"
  mkdir -p $dir/l $dir/u $dir/w $dir/t
  mkdir $dir/l/dev
  mount -t overlay -o lowerdir=$dir/l,upperdir=$dir/u,workdir=$dir/w o $dir/t
  stat $dir/t/dev
  rmdir $dir/t/dev
  mkdir $dir/t/dev
  echo $?
  echo "mkdir should have succeeded"
  =

  The above will work on the host, but fail in a user namespace, i.e
  in a regular lxd container.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1531747/+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 1531747] Re: overlay: mkdir fails if directory exists in lowerdir in a user namespace

2016-01-12 Thread Serge Hallyn

Quoting Seth Forshee (seth.forshee...@canonical.com):
> I don't know why #2 is that much grosser than what's there now. It's

I didn't mean gross as in eeuw, I meant not fine-grained enough.

Because the capability will apply to inode permissions checks,
and we only want it to be used for the check authorizing the
writing of the trusted.overlay.opaque xattr.

> already only taking the cap for setting the xattr, and taking
> CAP_SYS_ADMIN in init_user_ns seems to be what it's really wanting to do

Maybe - that's what I'm not sure about.  As you said earlier, in the
upstream code only an admin can do the actual mount.  The fact that an
unpriv user can create the mount may change assumptions about the
underlying fs's.

> there. The difference now though is that before that capability would
> have been required to do the mount and now it isn't.

Right.

> If we were to use ns_capable, which namespace do we use?

I don't know.  We're almost better off shipping a new version of
vfs_xattr() which is only for use by kernel writers.

If we had your patch we could maybe check against the sb->user_ns?

> current_user_ns? Then that check becomes worthless because any user can
> make a new namespace to bypass it. If we had the s_user_ns patches it

Quit saying in the next paragraph what I say in reply to the previous!

> might make sense to use that, but that probably doesn't solve the
> problem anyway since the lower mount was probably mounted in
> init_user_ns.

Good point, hadn't thought of that.

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

Title:
  overlay: mkdir fails if directory exists in lowerdir in a user
  namespace

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

Bug description:
  If a directory exists in the lowerdir but not in the mounted
  overlay, then mkdir of the directory in the target dir results
  in a mysterious -EPERM.  I've seen this both in wily kernel
  (4.2.0-22-generic #27-Ubuntu) and in a hand-built xenial
  master-next (with unrelated patches added).

  =
  #!/bin/sh -ex
  dir=`mktemp -d`
  cleanup() {
   umount -l $dir/t
   rm -rf $dir
  }

  trap cleanup EXIT

  echo "dir is $dir"
  mkdir -p $dir/l $dir/u $dir/w $dir/t
  mkdir $dir/l/dev
  mount -t overlay -o lowerdir=$dir/l,upperdir=$dir/u,workdir=$dir/w o $dir/t
  stat $dir/t/dev
  rmdir $dir/t/dev
  mkdir $dir/t/dev
  echo $?
  echo "mkdir should have succeeded"
  =

  The above will work on the host, but fail in a user namespace, i.e
  in a regular lxd container.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1531747/+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 1533277] [NEW] package linux-image-3.19.0-43-generic 3.19.0-43.49~14.04.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de sa

2016-01-12 Thread ricardo

Public bug reported:

me presenta error de un programa del sistema

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-3.19.0-43-generic 3.19.0-43.49~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
Date: Thu Jan  7 12:23:11 2016
ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 2
InstallationDate: Installed on 2015-12-14 (29 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.5
 apt  1.0.1ubuntu2.10
SourcePackage: linux-lts-vivid
Title: package linux-image-3.19.0-43-generic 3.19.0-43.49~14.04.1 failed to 
install/upgrade: el subproceso instalado el script post-installation devolvió 
el código de salida de error 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package trusty

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

Title:
  package linux-image-3.19.0-43-generic 3.19.0-43.49~14.04.1 failed to
  install/upgrade: el subproceso instalado el script post-installation
  devolvió el código de salida de error 2

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

Bug description:
  me presenta error de un programa del sistema

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-43-generic 3.19.0-43.49~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
  Date: Thu Jan  7 12:23:11 2016
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 2
  InstallationDate: Installed on 2015-12-14 (29 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.10
  SourcePackage: linux-lts-vivid
  Title: package linux-image-3.19.0-43-generic 3.19.0-43.49~14.04.1 failed to 
install/upgrade: el subproceso instalado el script post-installation devolvió 
el código de salida de error 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1533277/+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 1532928] Re: linux-ti-omap4: 3.2.0-1476.99 -proposed tracker

2016-01-12 Thread Luis Henriques

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => New

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

Title:
  linux-ti-omap4: 3.2.0-1476.99 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 11. January 2016 20:00 UTC
  kernel-stable-master-bug:1532774
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 12. January 2016 16:01 UTC
  kernel-stable-phase-changed:Tuesday, 12. January 2016 16:01 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 12. January 2016 16:01 UTC
  kernel-stable-Certification-testing-end:Tuesday, 12. January 2016 16:01 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1532928/+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 1529654] Re: Ubuntu 14.04 3.13.0.74-generic keyboard doesn't respond; okay in 3.13.0.71

2016-01-12 Thread David Ing

@Christopher, I downloaded the Ubuntu 16.04 (Xenial Xerus) Daily Build
64-bit version onto a USB key, and am successfully running live.

I got the "gfxboot.c32 not a com32r image" problem initially, found the
solution to use the tab key, and now have the computer running.

Firefox browser watching Youtube is running fine. Unfortunately, I
can't access the data on my hard drive, Files gives me the message ...

> This location could not be displayed.
> You do have not permissions necessary to view the contents of "daviding".

... so my ability to perform additional testing is limited.

The keyboard and mouse problem that I had reported with 14.04
3.13.0.74-generic doesn't appear to be here. Do I just wait until
another kernel is released as a simple matter of course, and hope that
the problem is fixed by then?

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

Title:
Ubuntu 14.04 3.13.0.74-generic keyboard doesn't respond; okay in
3.13.0.71

Status in linux package in Ubuntu:
Incomplete

Bug description:
When I booted the computer this morning, the keyboard and mouse
(actually a Lenovo keyboard with trackpoint) wouldn't respond. I
swapped keyboards, and got the same problem.

This is happening under kernel 3.13.0.74-generic. When I use grub to
boot under the previous 3.13.0.71 kernel, things are working fine.

In the past few days, I had noticed that dpkg errors were holding up
updates, so I did repairs and updates worked fine.

I am typing this from the computer booted under 3.13.0.71-generic, and
obviously can not do so under 3.13.0.74-generic.

$ lsb_release -rd
Description: Ubuntu 14.04.3 LTS
Release: 14.04

What I expected to happen: After boot, keyboard and mouse should
respond.

What happened instead: This computer has Mate Desktop installed on top of
Ubuntu 14.04. The Mate Desktop appears, but the keyboard and mouse
(trackpoint) do not respond.
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: daviding 1877 F pulseaudio
/dev/snd/controlC2: daviding 1877 F pulseaudio
/dev/snd/controlC0: daviding 1877 F pulseaudio
/dev/snd/pcmC0D0p: daviding 1877 F...m pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=7168f469-6882-4d5b-991f-5a6b711c844f
InstallationDate: Installed on 2014-08-29 (498 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
(20140722.2)
IwConfig:
eth0 no wireless extensions.

lono wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic
root=UUID=a8ed2bff-1f42-41d5-805e-1f7c2472853c ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
RelatedPackageVersions:
linux-restricted-modules-3.13.0-71-generic N/A
linux-backports-modules-3.13.0-71-generic N/A
linux-firmware 1.127.19
RfKill:

Tags: trusty
Uname: Linux 3.13.0-71-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
WifiSyslog: Jan 10 12:29:37 m5a88 kernel: [11681.824137]
systemd-hostnamed[3332]: Warning: nss-myhostname is not installed. Changing the
local hostname might make it unresolveable. Please install nss-myhostname!
_MarkForUpload: True
dmi.bios.date: 05/01/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1702
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M5A88-M
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1702:bd05/01/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A88-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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

[Kernel-packages] [Bug 1532928] Re: linux-ti-omap4: 3.2.0-1476.98 -proposed tracker

2016-01-12 Thread Luis Henriques

** Changed in: kernel-sru-workflow/upload-to-ppa
   Status: New => Fix Released

** Summary changed:

- linux-ti-omap4: 3.2.0-1476.98 -proposed tracker
+ linux-ti-omap4: 3.2.0-1476.99 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Fix Released => New

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

Title:
  linux-ti-omap4: 3.2.0-1476.99 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 11. January 2016 20:00 UTC
  kernel-stable-master-bug:1532774
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 12. January 2016 16:01 UTC
  kernel-stable-phase-changed:Tuesday, 12. January 2016 16:01 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 12. January 2016 16:01 UTC
  kernel-stable-Certification-testing-end:Tuesday, 12. January 2016 16:01 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1532928/+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 1533249] Re: Re-enable vlan TX acceleration

2016-01-12 Thread Tim Gardner

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

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

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

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

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

Title:
  Re-enable vlan TX acceleration

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

Bug description:
  
  Unable to send TCP/UDP traffic between VLAN on ConnectX4LX, due to vlan TX 
acceleration is off.

  Scenario

 Configure static VLAN on CX4LX and try to run iperf TCP/UDP.
 There are no traffic TCP/UDP even that the ICMP traffic pass (using 
ping between vlan's)
   

 #server #   iperf -s

#Client: #   iperf -c 

  
  Setup info: 

  OS: Ubuntu14.04.4
  Kernel  4.2.0-22

  Upstream commits that fix this issue

  c44d84d net/mlx5e: Fix inline header size calculation
  59fb571 net/mlx5e: Fix LSO vlan insertion
  13c5224 net/mlx5e: Re-eanble client vlan TX acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533249/+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 1532956] Re: linux-lts-trusty: 3.13.0-75.119~precise1 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

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

Title:
  linux-lts-trusty: 3.13.0-75.119~precise1 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-75.119~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 11. January 2016 21:02 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Monday, 11. January 2016 21:02 UTC
  kernel-stable-master-bug:1532781

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1532956/+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 1532928] Re: linux-ti-omap4: 3.2.0-1476.98 -proposed tracker

All builds are complete, packages in this bug can be copied to
-proposed.

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: ubuntu-armel-kernel (ubuntu-armel-kernel) => Luis Henriques 
(henrix)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 11. January 2016 20:00 UTC
- kernel-stable-phase:Prepare
- kernel-stable-phase-changed:Monday, 11. January 2016 20:00 UTC
  kernel-stable-master-bug:1532774
+ kernel-stable-phase:CopyToProposed
+ kernel-stable-Prepare-package-end:Tuesday, 12. January 2016 16:01 UTC
+ kernel-stable-phase-changed:Tuesday, 12. January 2016 16:01 UTC
+ kernel-stable-Promote-to-proposed-start:Tuesday, 12. January 2016 16:01 UTC
+ kernel-stable-Certification-testing-end:Tuesday, 12. January 2016 16:01 UTC

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

Title:
  linux-ti-omap4: 3.2.0-1476.99 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 11. January 2016 20:00 UTC
  kernel-stable-master-bug:1532774
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 12. January 2016 16:01 UTC
  kernel-stable-phase-changed:Tuesday, 12. January 2016 16:01 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 12. January 2016 16:01 UTC
  kernel-stable-Certification-testing-end:Tuesday, 12. January 2016 16:01 UTC

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1532928/+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 1532989] Re: bluetooth device list not populating after fresh flash

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

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

Title:
  bluetooth device list not populating after fresh flash

Status in Canonical System Image:
  New
Status in canonical-pocket-desktop:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  Every time i flash, needing to connect my bt mouse/keyboard, i open
  u-s-s and go to the bt icon, select it and tap on "connect a
  device"...little orange spinner spins...but list never populates.

  I have to log on to the device shell and restart indicator-bluetooth
  at which point the list will populate.

  I _think_ this is only occurring after a fresh flash, but i am not
  sure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532989/+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 1532989] Re: bluetooth device list not populating after fresh flash

2016-01-12 Thread Dubstar_04

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

** This bug has been marked a duplicate of bug 1530807
   Bluetooth cannot be activated.

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

Title:
  bluetooth device list not populating after fresh flash

Status in Canonical System Image:
  New
Status in canonical-pocket-desktop:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  Every time i flash, needing to connect my bt mouse/keyboard, i open
  u-s-s and go to the bt icon, select it and tap on "connect a
  device"...little orange spinner spins...but list never populates.

  I have to log on to the device shell and restart indicator-bluetooth
  at which point the list will populate.

  I _think_ this is only occurring after a fresh flash, but i am not
  sure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532989/+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 1532989] Re: bluetooth device list not populating after fresh flash

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

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

** Changed in: indicator-bluetooth (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/1532989

Title:
  bluetooth device list not populating after fresh flash

Status in Canonical System Image:
  New
Status in canonical-pocket-desktop:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  Every time i flash, needing to connect my bt mouse/keyboard, i open
  u-s-s and go to the bt icon, select it and tap on "connect a
  device"...little orange spinner spins...but list never populates.

  I have to log on to the device shell and restart indicator-bluetooth
  at which point the list will populate.

  I _think_ this is only occurring after a fresh flash, but i am not
  sure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532989/+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 1529287] Re: Qualcomm Atheros QCA6174 doesn't work in Ubuntu 15.10, firmware crash

2016-01-12 Thread regnuh

Moonsky219,

Same problem here, tried changing a few things in my router with no
luck, the workaround for me now is to use the 2.4ghz.

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

Title:
  Qualcomm Atheros QCA6174 doesn't work in Ubuntu 15.10, firmware crash

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Network manager can get SSID list, but cannot connect to them. I am
  using usb tethering to submit this bug report.

  Ubuntu 4.2.0-22.27-generic 4.2.6

  linux-firmware:
Installed: 1.149.3
Candidate: 1.149.3

  05:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter [168c:003e] (rev 20)
Subsystem: Bigfoot Networks, Inc. Killer N1525 Wireless-AC [1a56:1525]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: ath10k_pci

  dmesg | grep ath10k
  [5.870066] ath10k_pci :05:00.0: pci irq msi interrupts 1 irq_mode 0 
reset_mode 0
  [6.077120] ath10k_pci :05:00.0: Direct firmware load for 
ath10k/cal-pci-:05:00.0.bin failed with error -2
  [6.077858] ath10k_pci :05:00.0: Direct firmware load for 
ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin failed with error -2
  [6.077860] ath10k_pci :05:00.0: failed to load spec board file, 
falling back to generic: -2
  [8.016656] ath10k_pci :05:00.0: qca6174 hw2.1 (0x0501, 
0x003405ff, 168c:003e:1a56:1525 fallback) fw WLAN.RM.1.1-00141 api 5 htt 3.1 
wmi 4 cal otp max_sta 32
  [8.016659] ath10k_pci :05:00.0: debug 0 debugfs 1 tracing 1 dfs 0 
testmode 0
  [8.096136] ath10k_pci :05:00.0 wlp5s0: renamed from wlan0
  [   16.620429] ath10k_pci :05:00.0: no channel configured; ignoring 
frame(s)!
  [  818.272930] ath10k_pci :05:00.0: firmware crashed! (uuid 
80769440-063f-4b24-afb0-58b4073b7f9e)
  [  818.272935] ath10k_pci :05:00.0: qca6174 hw2.1 (0x0501, 
0x003405ff, 168c:003e:1a56:1525 fallback) fw WLAN.RM.1.1-00141 api 5 htt 3.1 
wmi 4 cal otp max_sta 32
  [  818.272937] ath10k_pci :05:00.0: debug 0 debugfs 1 tracing 1 dfs 0 
testmode 0
  [  818.274942] ath10k_pci :05:00.0: firmware register dump:
  [  818.274945] ath10k_pci :05:00.0: [00]: 0x0501 0x15B3 
0x00939797 0x00955B31
  [  818.274947] ath10k_pci :05:00.0: [04]: 0x00939797 0x00060330 
0x 0x
  [  818.274948] ath10k_pci :05:00.0: [08]: 0x00413980 0x 
0x 0x
  [  818.274949] ath10k_pci :05:00.0: [12]: 0x0009 0x 
0x0096C09C 0x0096C0A7
  [  818.274950] ath10k_pci :05:00.0: [16]: 0x0096BDBC 0x009287BD 
0x 0x009287BD
  [  818.274952] ath10k_pci :05:00.0: [20]: 0x40939797 0x0041A700 
0x00407124 0x
  [  818.274953] ath10k_pci :05:00.0: [24]: 0x8093D6C4 0x0041A760 
0x004059D0 0xC0939797
  [  818.274954] ath10k_pci :05:00.0: [28]: 0x8094777F 0x0041A780 
0x0046D5D8 0x0001
  [  818.274955] ath10k_pci :05:00.0: [32]: 0x800AA427 0x0041A7B0 
0x0046D5D8 0x0001
  [  818.274957] ath10k_pci :05:00.0: [36]: 0x800AA58E 0x0041A7D0 
0x00424824 0x0001
  [  818.274958] ath10k_pci :05:00.0: [40]: 0x80994D90 0x0041A7F0 
0x00424824 0x0041A838
  [  818.274959] ath10k_pci :05:00.0: [44]: 0x80996DC6 0x0041A820 
0x0046F888 0x00412984
  [  818.274960] ath10k_pci :05:00.0: [48]: 0x800B43F5 0x0041A860 
0x004222F8 0x5008
  [  818.274961] ath10k_pci :05:00.0: [52]: 0x809A6ACC 0x0041A8F0 
0x0042930C 0x0042CA24
  [  818.274963] ath10k_pci :05:00.0: [56]: 0x809A6120 0x0041A930 
0x0041A958 0x00427110
  [  818.285238] ath10k_pci :05:00.0: failed to poke peer 94:b4:0f:ad:ee:70 
param for ps workaround on vdev 0: -108
  [  819.784174] ath10k_pci :05:00.0: firmware crashed! (uuid 
2b0b4e85-367f-436b-b319-a4802a36b5f2)
  [  819.784186] ath10k_pci :05:00.0: qca6174 hw2.1 (0x0501, 
0x003405ff, 168c:003e:1a56:1525 fallback) fw WLAN.RM.1.1-00141 api 5 htt 3.1 
wmi 4 cal otp max_sta 32
  [  819.784189] ath10k_pci :05:00.0: debug 0 debugfs 1 tracing 1 dfs 0 
testmode 0
  [  819.786201] ath10k_pci :05:00.0: firmware register dump:
  [  819.786205] ath10k_pci :05:00.0: [00]: 0x0501 0x15B3 
0x00939797 0x00955B31
  [  819.786207] ath10k_pci :05:00.0: [04]: 0x00939797 0x00060330 
0x 0x
  [  819.786218] ath10k_pci :05:00.0: [08]: 0x00413980 0x 
0x 0x
  [  819.786220] ath10k_pci :05:00.0: [12]: 0x0009 0x 
0x0096C09C 0x0096C0A7
  [  819.786222] ath10k_pci :05:00.0: [16]: 0x0096BDBC 0x009287BD 
0x 0x
  [  819.786224] ath10k_pci :05:00.0: [20]: 0x40939797 0x0041A700 
0x00407124 0x
  [  819.786225] ath10k_pci :05:00.0: [24]: 0x80

[Kernel-packages] [Bug 1532928] Re: linux-ti-omap4: -proposed tracker

2016-01-12 Thread Luis Henriques

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

** Summary changed:

- linux-ti-omap4:  -proposed tracker
+ linux-ti-omap4: 3.2.0-1476.98 -proposed tracker

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

Title:
  linux-ti-omap4: 3.2.0-1476.98 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 11. January 2016 20:00 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Monday, 11. January 2016 20:00 UTC
  kernel-stable-master-bug:1532774

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1532928/+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 1533249] Re: Re-enable vlan TX acceleration

2016-01-12 Thread Tim Gardner

** Summary changed:

- Re-enabe vlan TX acceleration
+ Re-enable vlan TX acceleration

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

Title:
  Re-enable vlan TX acceleration

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  Unable to send TCP/UDP traffic between VLAN on ConnectX4LX, due to vlan TX 
acceleration is off.

  Scenario

 Configure static VLAN on CX4LX and try to run iperf TCP/UDP.
 There are no traffic TCP/UDP even that the ICMP traffic pass (using 
ping between vlan's)
   

 #server #   iperf -s

#Client: #   iperf -c 

  
  Setup info: 

  OS: Ubuntu14.04.4
  Kernel  4.2.0-22

  Upstream commits that fix this issue

  c44d84d net/mlx5e: Fix inline header size calculation
  59fb571 net/mlx5e: Fix LSO vlan insertion
  13c5224 net/mlx5e: Re-eanble client vlan TX acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533249/+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 1531747] Re: overlay: mkdir fails if directory exists in lowerdir in a user namespace

2016-01-12 Thread Seth Forshee

I don't know why #2 is that much grosser than what's there now. It's
already only taking the cap for setting the xattr, and taking
CAP_SYS_ADMIN in init_user_ns seems to be what it's really wanting to do
there. The difference now though is that before that capability would
have been required to do the mount and now it isn't.

If we were to use ns_capable, which namespace do we use?
current_user_ns? Then that check becomes worthless because any user can
make a new namespace to bypass it. If we had the s_user_ns patches it
might make sense to use that, but that probably doesn't solve the
problem anyway since the lower mount was probably mounted in
init_user_ns.

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

Title:
  overlay: mkdir fails if directory exists in lowerdir in a user
  namespace

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

Bug description:
  If a directory exists in the lowerdir but not in the mounted
  overlay, then mkdir of the directory in the target dir results
  in a mysterious -EPERM.  I've seen this both in wily kernel
  (4.2.0-22-generic #27-Ubuntu) and in a hand-built xenial
  master-next (with unrelated patches added).

  =
  #!/bin/sh -ex
  dir=`mktemp -d`
  cleanup() {
   umount -l $dir/t
   rm -rf $dir
  }

  trap cleanup EXIT

  echo "dir is $dir"
  mkdir -p $dir/l $dir/u $dir/w $dir/t
  mkdir $dir/l/dev
  mount -t overlay -o lowerdir=$dir/l,upperdir=$dir/u,workdir=$dir/w o $dir/t
  stat $dir/t/dev
  rmdir $dir/t/dev
  mkdir $dir/t/dev
  echo $?
  echo "mkdir should have succeeded"
  =

  The above will work on the host, but fail in a user namespace, i.e
  in a regular lxd container.

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