[Kernel-packages] [Bug 1578358] CRDA.txt

2016-06-07 Thread Christophe 
apport information

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

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

Title:
  Bug with wistron_btns while booting

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I've successfully installed Linux Mint XCFE 17.1 on my (old) notebook,
  but the computer is blocked during the boot. It seems that
  wistron_btns is the problem.

  The error I get are (see log) :

  "BUG: soft lockup - CPU#0 stuck for 23s! [systemd-udevd:402]"
  "wistron_btns: Unknown key code 70"

  My computer is a Medion WIM 2030 with :
  - Pentium M 1.7 (non-PAE, I've installed Mint with forcepae)
  - 1,25 Go RAM
  - 80 Go hard disk
  - Intel PRO/Wireless 2200BG Network connection
  - Some buttons to active the wifi, open Firefox,... that work well with 
Windows XP (dual boot)

  What can I do to make it boot ?

  Thanks for your help !

  Christophe
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christophe   2095 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=be4028df-46ce-414e-ae59-5ce4cf71e286
  InstallationDate: Installed on 2016-05-03 (34 days ago)
  InstallationMedia: Linux Mint 17.1 "Rebecca" - Release i386 20150108
  MachineType: Medion WIM 2030
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=074c8ee5-8552-487a-923c-1e6b42451da7 ro forcepae quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  rebecca
  Uname: Linux 3.13.0-37-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2004
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R01-A0Q
  dmi.board.name: WIM 2030
  dmi.board.vendor: Medion
  dmi.board.version: Rev.A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR01-A0Q:bd09/10/2004:svnMedion:pnWIM2030:pvr:rvnMedion:rnWIM2030:rvrRev.A:cvnMedion:ct10:cvrN/A:
  dmi.product.name: WIM 2030
  dmi.sys.vendor: Medion

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

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

[Kernel-packages] [Bug 1578358] CurrentDmesg.txt

2016-06-07 Thread Christophe 
apport information

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

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

Title:
  Bug with wistron_btns while booting

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I've successfully installed Linux Mint XCFE 17.1 on my (old) notebook,
  but the computer is blocked during the boot. It seems that
  wistron_btns is the problem.

  The error I get are (see log) :

  "BUG: soft lockup - CPU#0 stuck for 23s! [systemd-udevd:402]"
  "wistron_btns: Unknown key code 70"

  My computer is a Medion WIM 2030 with :
  - Pentium M 1.7 (non-PAE, I've installed Mint with forcepae)
  - 1,25 Go RAM
  - 80 Go hard disk
  - Intel PRO/Wireless 2200BG Network connection
  - Some buttons to active the wifi, open Firefox,... that work well with 
Windows XP (dual boot)

  What can I do to make it boot ?

  Thanks for your help !

  Christophe
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christophe   2095 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=be4028df-46ce-414e-ae59-5ce4cf71e286
  InstallationDate: Installed on 2016-05-03 (34 days ago)
  InstallationMedia: Linux Mint 17.1 "Rebecca" - Release i386 20150108
  MachineType: Medion WIM 2030
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=074c8ee5-8552-487a-923c-1e6b42451da7 ro forcepae quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  rebecca
  Uname: Linux 3.13.0-37-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2004
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R01-A0Q
  dmi.board.name: WIM 2030
  dmi.board.vendor: Medion
  dmi.board.version: Rev.A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR01-A0Q:bd09/10/2004:svnMedion:pnWIM2030:pvr:rvnMedion:rnWIM2030:rvrRev.A:cvnMedion:ct10:cvrN/A:
  dmi.product.name: WIM 2030
  dmi.sys.vendor: Medion

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

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

[Kernel-packages] [Bug 1578358] UdevDb.txt

2016-06-07 Thread Christophe 
apport information

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

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

Title:
  Bug with wistron_btns while booting

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I've successfully installed Linux Mint XCFE 17.1 on my (old) notebook,
  but the computer is blocked during the boot. It seems that
  wistron_btns is the problem.

  The error I get are (see log) :

  "BUG: soft lockup - CPU#0 stuck for 23s! [systemd-udevd:402]"
  "wistron_btns: Unknown key code 70"

  My computer is a Medion WIM 2030 with :
  - Pentium M 1.7 (non-PAE, I've installed Mint with forcepae)
  - 1,25 Go RAM
  - 80 Go hard disk
  - Intel PRO/Wireless 2200BG Network connection
  - Some buttons to active the wifi, open Firefox,... that work well with 
Windows XP (dual boot)

  What can I do to make it boot ?

  Thanks for your help !

  Christophe
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christophe   2095 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=be4028df-46ce-414e-ae59-5ce4cf71e286
  InstallationDate: Installed on 2016-05-03 (34 days ago)
  InstallationMedia: Linux Mint 17.1 "Rebecca" - Release i386 20150108
  MachineType: Medion WIM 2030
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=074c8ee5-8552-487a-923c-1e6b42451da7 ro forcepae quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  rebecca
  Uname: Linux 3.13.0-37-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2004
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R01-A0Q
  dmi.board.name: WIM 2030
  dmi.board.vendor: Medion
  dmi.board.version: Rev.A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR01-A0Q:bd09/10/2004:svnMedion:pnWIM2030:pvr:rvnMedion:rnWIM2030:rvrRev.A:cvnMedion:ct10:cvrN/A:
  dmi.product.name: WIM 2030
  dmi.sys.vendor: Medion

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

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

[Kernel-packages] [Bug 1578358] ProcCpuinfo.txt

2016-06-07 Thread Christophe 
apport information

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

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

Title:
  Bug with wistron_btns while booting

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I've successfully installed Linux Mint XCFE 17.1 on my (old) notebook,
  but the computer is blocked during the boot. It seems that
  wistron_btns is the problem.

  The error I get are (see log) :

  "BUG: soft lockup - CPU#0 stuck for 23s! [systemd-udevd:402]"
  "wistron_btns: Unknown key code 70"

  My computer is a Medion WIM 2030 with :
  - Pentium M 1.7 (non-PAE, I've installed Mint with forcepae)
  - 1,25 Go RAM
  - 80 Go hard disk
  - Intel PRO/Wireless 2200BG Network connection
  - Some buttons to active the wifi, open Firefox,... that work well with 
Windows XP (dual boot)

  What can I do to make it boot ?

  Thanks for your help !

  Christophe
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christophe   2095 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=be4028df-46ce-414e-ae59-5ce4cf71e286
  InstallationDate: Installed on 2016-05-03 (34 days ago)
  InstallationMedia: Linux Mint 17.1 "Rebecca" - Release i386 20150108
  MachineType: Medion WIM 2030
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=074c8ee5-8552-487a-923c-1e6b42451da7 ro forcepae quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  rebecca
  Uname: Linux 3.13.0-37-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2004
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R01-A0Q
  dmi.board.name: WIM 2030
  dmi.board.vendor: Medion
  dmi.board.version: Rev.A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR01-A0Q:bd09/10/2004:svnMedion:pnWIM2030:pvr:rvnMedion:rnWIM2030:rvrRev.A:cvnMedion:ct10:cvrN/A:
  dmi.product.name: WIM 2030
  dmi.sys.vendor: Medion

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

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

[Kernel-packages] [Bug 1578358] IwConfig.txt

2016-06-07 Thread Christophe 
apport information

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

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

Title:
  Bug with wistron_btns while booting

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I've successfully installed Linux Mint XCFE 17.1 on my (old) notebook,
  but the computer is blocked during the boot. It seems that
  wistron_btns is the problem.

  The error I get are (see log) :

  "BUG: soft lockup - CPU#0 stuck for 23s! [systemd-udevd:402]"
  "wistron_btns: Unknown key code 70"

  My computer is a Medion WIM 2030 with :
  - Pentium M 1.7 (non-PAE, I've installed Mint with forcepae)
  - 1,25 Go RAM
  - 80 Go hard disk
  - Intel PRO/Wireless 2200BG Network connection
  - Some buttons to active the wifi, open Firefox,... that work well with 
Windows XP (dual boot)

  What can I do to make it boot ?

  Thanks for your help !

  Christophe
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christophe   2095 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=be4028df-46ce-414e-ae59-5ce4cf71e286
  InstallationDate: Installed on 2016-05-03 (34 days ago)
  InstallationMedia: Linux Mint 17.1 "Rebecca" - Release i386 20150108
  MachineType: Medion WIM 2030
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=074c8ee5-8552-487a-923c-1e6b42451da7 ro forcepae quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  rebecca
  Uname: Linux 3.13.0-37-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2004
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R01-A0Q
  dmi.board.name: WIM 2030
  dmi.board.vendor: Medion
  dmi.board.version: Rev.A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR01-A0Q:bd09/10/2004:svnMedion:pnWIM2030:pvr:rvnMedion:rnWIM2030:rvrRev.A:cvnMedion:ct10:cvrN/A:
  dmi.product.name: WIM 2030
  dmi.sys.vendor: Medion

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

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

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

2016-06-07 Thread Christophe 
apport information

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

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

Title:
  Bug with wistron_btns while booting

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I've successfully installed Linux Mint XCFE 17.1 on my (old) notebook,
  but the computer is blocked during the boot. It seems that
  wistron_btns is the problem.

  The error I get are (see log) :

  "BUG: soft lockup - CPU#0 stuck for 23s! [systemd-udevd:402]"
  "wistron_btns: Unknown key code 70"

  My computer is a Medion WIM 2030 with :
  - Pentium M 1.7 (non-PAE, I've installed Mint with forcepae)
  - 1,25 Go RAM
  - 80 Go hard disk
  - Intel PRO/Wireless 2200BG Network connection
  - Some buttons to active the wifi, open Firefox,... that work well with 
Windows XP (dual boot)

  What can I do to make it boot ?

  Thanks for your help !

  Christophe
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christophe   2095 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=be4028df-46ce-414e-ae59-5ce4cf71e286
  InstallationDate: Installed on 2016-05-03 (34 days ago)
  InstallationMedia: Linux Mint 17.1 "Rebecca" - Release i386 20150108
  MachineType: Medion WIM 2030
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=074c8ee5-8552-487a-923c-1e6b42451da7 ro forcepae quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  rebecca
  Uname: Linux 3.13.0-37-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2004
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R01-A0Q
  dmi.board.name: WIM 2030
  dmi.board.vendor: Medion
  dmi.board.version: Rev.A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR01-A0Q:bd09/10/2004:svnMedion:pnWIM2030:pvr:rvnMedion:rnWIM2030:rvrRev.A:cvnMedion:ct10:cvrN/A:
  dmi.product.name: WIM 2030
  dmi.sys.vendor: Medion

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

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

[Kernel-packages] [Bug 1578358] PccardctlStatus.txt

2016-06-07 Thread Christophe 
apport information

** Attachment added: "PccardctlStatus.txt"
   
https://bugs.launchpad.net/bugs/1578358/+attachment/4679084/+files/PccardctlStatus.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/1578358

Title:
  Bug with wistron_btns while booting

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I've successfully installed Linux Mint XCFE 17.1 on my (old) notebook,
  but the computer is blocked during the boot. It seems that
  wistron_btns is the problem.

  The error I get are (see log) :

  "BUG: soft lockup - CPU#0 stuck for 23s! [systemd-udevd:402]"
  "wistron_btns: Unknown key code 70"

  My computer is a Medion WIM 2030 with :
  - Pentium M 1.7 (non-PAE, I've installed Mint with forcepae)
  - 1,25 Go RAM
  - 80 Go hard disk
  - Intel PRO/Wireless 2200BG Network connection
  - Some buttons to active the wifi, open Firefox,... that work well with 
Windows XP (dual boot)

  What can I do to make it boot ?

  Thanks for your help !

  Christophe
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christophe   2095 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=be4028df-46ce-414e-ae59-5ce4cf71e286
  InstallationDate: Installed on 2016-05-03 (34 days ago)
  InstallationMedia: Linux Mint 17.1 "Rebecca" - Release i386 20150108
  MachineType: Medion WIM 2030
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=074c8ee5-8552-487a-923c-1e6b42451da7 ro forcepae quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  rebecca
  Uname: Linux 3.13.0-37-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2004
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R01-A0Q
  dmi.board.name: WIM 2030
  dmi.board.vendor: Medion
  dmi.board.version: Rev.A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR01-A0Q:bd09/10/2004:svnMedion:pnWIM2030:pvr:rvnMedion:rnWIM2030:rvrRev.A:cvnMedion:ct10:cvrN/A:
  dmi.product.name: WIM 2030
  dmi.sys.vendor: Medion

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

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

[Kernel-packages] [Bug 1578358] UdevLog.txt

2016-06-07 Thread Christophe 
apport information

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

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

Title:
  Bug with wistron_btns while booting

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I've successfully installed Linux Mint XCFE 17.1 on my (old) notebook,
  but the computer is blocked during the boot. It seems that
  wistron_btns is the problem.

  The error I get are (see log) :

  "BUG: soft lockup - CPU#0 stuck for 23s! [systemd-udevd:402]"
  "wistron_btns: Unknown key code 70"

  My computer is a Medion WIM 2030 with :
  - Pentium M 1.7 (non-PAE, I've installed Mint with forcepae)
  - 1,25 Go RAM
  - 80 Go hard disk
  - Intel PRO/Wireless 2200BG Network connection
  - Some buttons to active the wifi, open Firefox,... that work well with 
Windows XP (dual boot)

  What can I do to make it boot ?

  Thanks for your help !

  Christophe
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christophe   2095 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=be4028df-46ce-414e-ae59-5ce4cf71e286
  InstallationDate: Installed on 2016-05-03 (34 days ago)
  InstallationMedia: Linux Mint 17.1 "Rebecca" - Release i386 20150108
  MachineType: Medion WIM 2030
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=074c8ee5-8552-487a-923c-1e6b42451da7 ro forcepae quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  rebecca
  Uname: Linux 3.13.0-37-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2004
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R01-A0Q
  dmi.board.name: WIM 2030
  dmi.board.vendor: Medion
  dmi.board.version: Rev.A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR01-A0Q:bd09/10/2004:svnMedion:pnWIM2030:pvr:rvnMedion:rnWIM2030:rvrRev.A:cvnMedion:ct10:cvrN/A:
  dmi.product.name: WIM 2030
  dmi.sys.vendor: Medion

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

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

[Kernel-packages] [Bug 1578358] WifiSyslog.txt

2016-06-07 Thread Christophe 
apport information

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

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

Title:
  Bug with wistron_btns while booting

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I've successfully installed Linux Mint XCFE 17.1 on my (old) notebook,
  but the computer is blocked during the boot. It seems that
  wistron_btns is the problem.

  The error I get are (see log) :

  "BUG: soft lockup - CPU#0 stuck for 23s! [systemd-udevd:402]"
  "wistron_btns: Unknown key code 70"

  My computer is a Medion WIM 2030 with :
  - Pentium M 1.7 (non-PAE, I've installed Mint with forcepae)
  - 1,25 Go RAM
  - 80 Go hard disk
  - Intel PRO/Wireless 2200BG Network connection
  - Some buttons to active the wifi, open Firefox,... that work well with 
Windows XP (dual boot)

  What can I do to make it boot ?

  Thanks for your help !

  Christophe
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christophe   2095 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=be4028df-46ce-414e-ae59-5ce4cf71e286
  InstallationDate: Installed on 2016-05-03 (34 days ago)
  InstallationMedia: Linux Mint 17.1 "Rebecca" - Release i386 20150108
  MachineType: Medion WIM 2030
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=074c8ee5-8552-487a-923c-1e6b42451da7 ro forcepae quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  rebecca
  Uname: Linux 3.13.0-37-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2004
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R01-A0Q
  dmi.board.name: WIM 2030
  dmi.board.vendor: Medion
  dmi.board.version: Rev.A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR01-A0Q:bd09/10/2004:svnMedion:pnWIM2030:pvr:rvnMedion:rnWIM2030:rvrRev.A:cvnMedion:ct10:cvrN/A:
  dmi.product.name: WIM 2030
  dmi.sys.vendor: Medion

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

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

[Kernel-packages] [Bug 1555353] Re: integer overflow in xt_alloc_table_info

2016-06-07 Thread Steve Beattie 
** Tags added: kernel-cve-tracking-bug

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

Title:
  integer overflow in xt_alloc_table_info

Status in linux package in Ubuntu:
  Fix Released
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-snapdragon package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-snapdragon source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Invalid
Status in linux-lts-wily source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  Fix Released
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-snapdragon source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Wily:
  Fix Released
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source package in Wily:
  New
Status in linux-manta source package in Wily:
  New
Status in linux-raspi2 source package in Wily:
  Fix Released
Status in linux-snapdragon source package in Wily:
  Invalid
Status in linux-ti-omap4 source package in Wily:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-armadaxp source package in Xenial:
  Invalid
Status in linux-flo source package in Xenial:
  New
Status in linux-goldfish source package in Xenial:
  New
Status in linux-lts-quantal source package in Xenial:
  Invalid
Status in linux-lts-raring source package in Xenial:
  Invalid
Status in linux-lts-saucy source package in Xenial:
  Invalid
Status in linux-lts-trusty source package in Xenial:
  Invalid
Status in linux-lts-utopic source package in Xenial:
  Invalid
Status in linux-lts-vivid source package in Xenial:
  Invalid
Status in linux-lts-wily source package in Xenial:
  Invalid
Status in linux-lts-xenial source package in Xenial:
  Invalid
Status in linux-mako source package

[Kernel-packages] [Bug 1578358] PulseList.txt

2016-06-07 Thread Christophe 
apport information

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

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

Title:
  Bug with wistron_btns while booting

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I've successfully installed Linux Mint XCFE 17.1 on my (old) notebook,
  but the computer is blocked during the boot. It seems that
  wistron_btns is the problem.

  The error I get are (see log) :

  "BUG: soft lockup - CPU#0 stuck for 23s! [systemd-udevd:402]"
  "wistron_btns: Unknown key code 70"

  My computer is a Medion WIM 2030 with :
  - Pentium M 1.7 (non-PAE, I've installed Mint with forcepae)
  - 1,25 Go RAM
  - 80 Go hard disk
  - Intel PRO/Wireless 2200BG Network connection
  - Some buttons to active the wifi, open Firefox,... that work well with 
Windows XP (dual boot)

  What can I do to make it boot ?

  Thanks for your help !

  Christophe
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christophe   2095 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=be4028df-46ce-414e-ae59-5ce4cf71e286
  InstallationDate: Installed on 2016-05-03 (34 days ago)
  InstallationMedia: Linux Mint 17.1 "Rebecca" - Release i386 20150108
  MachineType: Medion WIM 2030
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=074c8ee5-8552-487a-923c-1e6b42451da7 ro forcepae quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  rebecca
  Uname: Linux 3.13.0-37-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2004
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R01-A0Q
  dmi.board.name: WIM 2030
  dmi.board.vendor: Medion
  dmi.board.version: Rev.A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR01-A0Q:bd09/10/2004:svnMedion:pnWIM2030:pvr:rvnMedion:rnWIM2030:rvrRev.A:cvnMedion:ct10:cvrN/A:
  dmi.product.name: WIM 2030
  dmi.sys.vendor: Medion

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

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

[Kernel-packages] [Bug 1578358] Re: Bug with wistron_btns while booting

2016-06-07 Thread Christophe 
apport information

** Tags added: apport-collected rebecca

** Description changed:

  Hello,
  
  I've successfully installed Linux Mint XCFE 17.1 on my (old) notebook,
  but the computer is blocked during the boot. It seems that wistron_btns
  is the problem.
  
  The error I get are (see log) :
  
  "BUG: soft lockup - CPU#0 stuck for 23s! [systemd-udevd:402]"
  "wistron_btns: Unknown key code 70"
  
  My computer is a Medion WIM 2030 with :
  - Pentium M 1.7 (non-PAE, I've installed Mint with forcepae)
  - 1,25 Go RAM
  - 80 Go hard disk
  - Intel PRO/Wireless 2200BG Network connection
  - Some buttons to active the wifi, open Firefox,... that work well with 
Windows XP (dual boot)
  
  What can I do to make it boot ?
  
  Thanks for your help !
  
  Christophe
+ --- 
+ ApportVersion: 2.14.1-0ubuntu3.21
+ Architecture: i386
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  christophe   2095 F pulseaudio
+ DistroRelease: Ubuntu 14.04
+ HibernationDevice: RESUME=UUID=be4028df-46ce-414e-ae59-5ce4cf71e286
+ InstallationDate: Installed on 2016-05-03 (34 days ago)
+ InstallationMedia: Linux Mint 17.1 "Rebecca" - Release i386 20150108
+ MachineType: Medion WIM 2030
+ Package: linux (not installed)
+ PccardctlIdent:
+  Socket 0:
+no product info available
+  Socket 1:
+no product info available
+ ProcEnviron:
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 radeondrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=074c8ee5-8552-487a-923c-1e6b42451da7 ro forcepae quiet splash 
vt.handoff=7
+ ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
+ RelatedPackageVersions:
+  linux-restricted-modules-3.13.0-37-generic N/A
+  linux-backports-modules-3.13.0-37-generic  N/A
+  linux-firmware 1.127.7
+ RfKill:
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
+ Tags:  rebecca
+ Uname: Linux 3.13.0-37-generic i686
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 09/10/2004
+ dmi.bios.vendor: Phoenix Technologies LTD
+ dmi.bios.version: R01-A0Q
+ dmi.board.name: WIM 2030
+ dmi.board.vendor: Medion
+ dmi.board.version: Rev.A
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Medion
+ dmi.chassis.version: N/A
+ dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR01-A0Q:bd09/10/2004:svnMedion:pnWIM2030:pvr:rvnMedion:rnWIM2030:rvrRev.A:cvnMedion:ct10:cvrN/A:
+ dmi.product.name: WIM 2030
+ dmi.sys.vendor: Medion

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

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

Title:
  Bug with wistron_btns while booting

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I've successfully installed Linux Mint XCFE 17.1 on my (old) notebook,
  but the computer is blocked during the boot. It seems that
  wistron_btns is the problem.

  The error I get are (see log) :

  "BUG: soft lockup - CPU#0 stuck for 23s! [systemd-udevd:402]"
  "wistron_btns: Unknown key code 70"

  My computer is a Medion WIM 2030 with :
  - Pentium M 1.7 (non-PAE, I've installed Mint with forcepae)
  - 1,25 Go RAM
  - 80 Go hard disk
  - Intel PRO/Wireless 2200BG Network connection
  - Some buttons to active the wifi, open Firefox,... that work well with 
Windows XP (dual boot)

  What can I do to make it boot ?

  Thanks for your help !

  Christophe
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christophe   2095 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=be4028df-46ce-414e-ae59-5ce4cf71e286
  InstallationDate: Installed on 2016-05-03 (34 days ago)
  InstallationMedia: Linux Mint 17.1 "Rebecca" - Release i386 20150108
  MachineType: Medion WIM 2030
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=074c8ee5-8552-487a-923c-1e6b42451da7 ro forcepae quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  rebecca
  Uname: Linux 3.13.0-37-generic i686

[Kernel-packages] [Bug 1578358] ProcInterrupts.txt

2016-06-07 Thread Christophe 
apport information

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

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

Title:
  Bug with wistron_btns while booting

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I've successfully installed Linux Mint XCFE 17.1 on my (old) notebook,
  but the computer is blocked during the boot. It seems that
  wistron_btns is the problem.

  The error I get are (see log) :

  "BUG: soft lockup - CPU#0 stuck for 23s! [systemd-udevd:402]"
  "wistron_btns: Unknown key code 70"

  My computer is a Medion WIM 2030 with :
  - Pentium M 1.7 (non-PAE, I've installed Mint with forcepae)
  - 1,25 Go RAM
  - 80 Go hard disk
  - Intel PRO/Wireless 2200BG Network connection
  - Some buttons to active the wifi, open Firefox,... that work well with 
Windows XP (dual boot)

  What can I do to make it boot ?

  Thanks for your help !

  Christophe
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christophe   2095 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=be4028df-46ce-414e-ae59-5ce4cf71e286
  InstallationDate: Installed on 2016-05-03 (34 days ago)
  InstallationMedia: Linux Mint 17.1 "Rebecca" - Release i386 20150108
  MachineType: Medion WIM 2030
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=074c8ee5-8552-487a-923c-1e6b42451da7 ro forcepae quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  rebecca
  Uname: Linux 3.13.0-37-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2004
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R01-A0Q
  dmi.board.name: WIM 2030
  dmi.board.vendor: Medion
  dmi.board.version: Rev.A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR01-A0Q:bd09/10/2004:svnMedion:pnWIM2030:pvr:rvnMedion:rnWIM2030:rvrRev.A:cvnMedion:ct10:cvrN/A:
  dmi.product.name: WIM 2030
  dmi.sys.vendor: Medion

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

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

[Kernel-packages] [Bug 1578358] BootDmesg.txt

2016-06-07 Thread Christophe 
apport information

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

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

Title:
  Bug with wistron_btns while booting

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I've successfully installed Linux Mint XCFE 17.1 on my (old) notebook,
  but the computer is blocked during the boot. It seems that
  wistron_btns is the problem.

  The error I get are (see log) :

  "BUG: soft lockup - CPU#0 stuck for 23s! [systemd-udevd:402]"
  "wistron_btns: Unknown key code 70"

  My computer is a Medion WIM 2030 with :
  - Pentium M 1.7 (non-PAE, I've installed Mint with forcepae)
  - 1,25 Go RAM
  - 80 Go hard disk
  - Intel PRO/Wireless 2200BG Network connection
  - Some buttons to active the wifi, open Firefox,... that work well with 
Windows XP (dual boot)

  What can I do to make it boot ?

  Thanks for your help !

  Christophe
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christophe   2095 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=be4028df-46ce-414e-ae59-5ce4cf71e286
  InstallationDate: Installed on 2016-05-03 (34 days ago)
  InstallationMedia: Linux Mint 17.1 "Rebecca" - Release i386 20150108
  MachineType: Medion WIM 2030
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=074c8ee5-8552-487a-923c-1e6b42451da7 ro forcepae quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  rebecca
  Uname: Linux 3.13.0-37-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2004
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R01-A0Q
  dmi.board.name: WIM 2030
  dmi.board.vendor: Medion
  dmi.board.version: Rev.A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR01-A0Q:bd09/10/2004:svnMedion:pnWIM2030:pvr:rvnMedion:rnWIM2030:rvrRev.A:cvnMedion:ct10:cvrN/A:
  dmi.product.name: WIM 2030
  dmi.sys.vendor: Medion

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

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

[Kernel-packages] [Bug 1578358] Lsusb.txt

2016-06-07 Thread Christophe 
apport information

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

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

Title:
  Bug with wistron_btns while booting

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I've successfully installed Linux Mint XCFE 17.1 on my (old) notebook,
  but the computer is blocked during the boot. It seems that
  wistron_btns is the problem.

  The error I get are (see log) :

  "BUG: soft lockup - CPU#0 stuck for 23s! [systemd-udevd:402]"
  "wistron_btns: Unknown key code 70"

  My computer is a Medion WIM 2030 with :
  - Pentium M 1.7 (non-PAE, I've installed Mint with forcepae)
  - 1,25 Go RAM
  - 80 Go hard disk
  - Intel PRO/Wireless 2200BG Network connection
  - Some buttons to active the wifi, open Firefox,... that work well with 
Windows XP (dual boot)

  What can I do to make it boot ?

  Thanks for your help !

  Christophe
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christophe   2095 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=be4028df-46ce-414e-ae59-5ce4cf71e286
  InstallationDate: Installed on 2016-05-03 (34 days ago)
  InstallationMedia: Linux Mint 17.1 "Rebecca" - Release i386 20150108
  MachineType: Medion WIM 2030
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=074c8ee5-8552-487a-923c-1e6b42451da7 ro forcepae quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  rebecca
  Uname: Linux 3.13.0-37-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/10/2004
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R01-A0Q
  dmi.board.name: WIM 2030
  dmi.board.vendor: Medion
  dmi.board.version: Rev.A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR01-A0Q:bd09/10/2004:svnMedion:pnWIM2030:pvr:rvnMedion:rnWIM2030:rvrRev.A:cvnMedion:ct10:cvrN/A:
  dmi.product.name: WIM 2030
  dmi.sys.vendor: Medion

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

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

[Kernel-packages] [Bug 1577516] Re: WiFi disconnects suddenly automatic with reason=4 locally_generated=1

2016-06-07 Thread Ettore Atalan 
Okay, it's a Samsung NP300E7A-A02DE.

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

Title:
  WiFi disconnects suddenly automatic with reason=4 locally_generated=1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I'm experiencing suddenly automatic WiFi disconnects after upgrading
  to Ubuntu 16.04. Syslog reports "reason=4 locally_generated=1". Ubuntu
  15.10 didn't show this problem.

  Regards,
  Atalanttore
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ben2016 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2e2e5512-9f35-4996-9c32-4ee11f0ed624
  InstallationDate: Installed on 2012-05-05 (1457 days ago)
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120423)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E4A/300E5A/300E7A/3430EA/3530EA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=484a35a0-ae5f-45d9-afa1-982bbb6ef909 ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lp lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/02/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 09QA
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 300E4A/300E5A/300E7A/3430EA/3530EA
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr09QA:bd11/02/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E4A/300E5A/300E7A/3430EA/3530EA:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn300E4A/300E5A/300E7A/3430EA/3530EA:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 300E4A/300E5A/300E7A/3430EA/3530EA
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

-- 
Mailing list: https://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 1583288] Re: Realtek Wifi card rtl8723be [10ec:b723] WiFi not available

2016-06-07 Thread Peter Ludwig 
Hi Podsgrove,

I really understand what you mean. I told my friends too to buy HP
because before it was always running smooth with all available Linux
distros. But this is crazy. Two HP 455 Laptops with these stupid wifi
adapters. As if there were not other adapter avail.

I just hope this will change soon or I will to advice my friends to
switch brand too.

Regards

Peter

Am 07.06.2016 um 16:42 schrieb Podsgrove:
> Thanks for your reply but one look at the complications of reporting a
> bug put me off. I am not a fan of Unity and had planned to install
> Lubuntu but the best I have able to achieve is to install the LXDE
> desktop on an out-of-date OS. This comes with the added bonus of a
> battery indicator that does not work and an annoying login bongo noise
> that keeps coming back despite all efforts to disable it.  It is
> annoying that HP have chosen to market a Linux laptop that does not
> work with the majority of Linux distros. The only ones I have found
> that work (apart from HP's modified Ubuntu) are Console Linux and
> Puppy, neither of which I particularly like.
> I guess I am just a grumpy old git but next time I buy a computer I
> will cough up the Microsoft tax and get one that works with Linux!
>
> Podsgrove
>  Sent using Hushmail
> On 07/06/2016 at 11:41 AM, "Christopher M. Penalver"  wrote:Podsgrove,
> it will help immensely if you filed a new report with Ubuntu (not
> Mint) via the default 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/1583288

Title:
  Realtek Wifi card rtl8723be [10ec:b723] WiFi not available

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I am here on a HP Pavilion Laptop with beatsaudio. No Model Number -
  nothing.But I have this problem on other HP (455) Notebooks too.

  OS tried: OpenSuse / Kubuntu / Linux Mint Mate (card does not work out
  of the box / no scanning)

  The Wifi card is: (in Germany!)

  --

   lspci -nn | grep -iA2 net
  02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE 
PCIe Wireless Network Adapter [10ec:b723]

  --

  I am now under kernel:
  4.4.0-21-generic

  I installed the newest kernel because in some threads people said the card 
woule be available in the newest kernel. But this was not the case. I mean the 
card is there but does not scan nor see any wifi networks.
  -

  Before I tried everything I could find to get my wifi running but I do
  not even see one spot. So no connection at all. I even cloned git and
  compiled the driver - the compiling and installation worked fine. I
  tried the old and the new driver.

  By the way the BT seems to be fine - although I have not checked cause
  I do not need BT.

  -
  Here is what I tried:

  rfkill list all; hciconfig -a
  0: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no
  1: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no
  hci0: Type: BR/EDR Bus: USB
   BD Address: 2C:33:7A:3F:E4:3E ACL MTU: 820:8 SCO MTU: 255:16
   UP RUNNING PSCAN
   RX bytes:1327 acl:0 sco:0 events:139 errors:0
   TX bytes:25058 acl:0 sco:0 commands:139 errors:0
   Features: 0xff 0xff 0xff 0xfe 0xdb 0xff 0x7b 0x87
   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
   Link policy: RSWITCH HOLD SNIFF PARK
   Link mode: SLAVE ACCEPT
   Name: 'mint-0'
   Class: 0x740100
   Service Classes: Rendering, Object Transfer, Audio, Telephony
   Device Class: Computer, Uncategorized
   HCI Version: 4.0 (0x6) Revision: 0xe2f
   LMP Version: 4.0 (0x6) Subversion: 0x9f73
   Manufacturer: Realtek Semiconductor Corporation (93)

  -

  I added the options sugested in rtl8723be.conf

  options rtl8723be fwlps=0 swlps=0

  But this did not help either.

  --

  lsmod reports:

  rfcomm 69632 12
  rtl8723be 139264 0
  btcoexist 180224 1 rtl8723be
  rtl_pci 40960 1 rtl8723be
  rtlwifi 98304 3 btcoexist,rtl_pci,rtl8723be
  hp_wmi 16384 0
  mac80211 733184 3 rtl_pci,rtlwifi,rtl8723be
  sparse_keymap 16384 1 hp_wmi
  kvm 532480 0
  irqbypass 16384 1 kvm
  btusb 45056 0
  crct10dif_pclmul 16384 0
  btrtl 16384 1 btusb
  btbcm 16384 1 btusb
  ...

  ---

  dmesg | grep rtl reports:

  [ 8.982260] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000b 
lmp_ver=06 lmp_subver=8723
  [ 8.982262] Bluetooth: hci0: rtl: loading rtl_bt/rtl8723b_fw.bin
  [ 9.064265] rtlwifi: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 9.403770] Using firmware

Re: [Kernel-packages] [Bug 1583288] Re: Realtek Wifi card rtl8723be [10ec:b723] WiFi not available

2016-06-07 Thread Peter Ludwig 
Hi Christopher,

I have another client with a "Kubuntu" version - almost same HP
Notebook. This wifi adapter I did not get up running at all. If it might
be of any help. Please let me know.

Regards

Peter


Am 07.06.2016 um 12:34 schrieb Christopher M. Penalver:
> Podsgrove, it will help immensely if you filed a new report with Ubuntu (not 
> Mint) via the default 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/1583288

Title:
  Realtek Wifi card rtl8723be [10ec:b723] WiFi not available

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I am here on a HP Pavilion Laptop with beatsaudio. No Model Number -
  nothing.But I have this problem on other HP (455) Notebooks too.

  OS tried: OpenSuse / Kubuntu / Linux Mint Mate (card does not work out
  of the box / no scanning)

  The Wifi card is: (in Germany!)

  --

   lspci -nn | grep -iA2 net
  02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE 
PCIe Wireless Network Adapter [10ec:b723]

  --

  I am now under kernel:
  4.4.0-21-generic

  I installed the newest kernel because in some threads people said the card 
woule be available in the newest kernel. But this was not the case. I mean the 
card is there but does not scan nor see any wifi networks.
  -

  Before I tried everything I could find to get my wifi running but I do
  not even see one spot. So no connection at all. I even cloned git and
  compiled the driver - the compiling and installation worked fine. I
  tried the old and the new driver.

  By the way the BT seems to be fine - although I have not checked cause
  I do not need BT.

  -
  Here is what I tried:

  rfkill list all; hciconfig -a
  0: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no
  1: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no
  hci0: Type: BR/EDR Bus: USB
   BD Address: 2C:33:7A:3F:E4:3E ACL MTU: 820:8 SCO MTU: 255:16
   UP RUNNING PSCAN
   RX bytes:1327 acl:0 sco:0 events:139 errors:0
   TX bytes:25058 acl:0 sco:0 commands:139 errors:0
   Features: 0xff 0xff 0xff 0xfe 0xdb 0xff 0x7b 0x87
   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
   Link policy: RSWITCH HOLD SNIFF PARK
   Link mode: SLAVE ACCEPT
   Name: 'mint-0'
   Class: 0x740100
   Service Classes: Rendering, Object Transfer, Audio, Telephony
   Device Class: Computer, Uncategorized
   HCI Version: 4.0 (0x6) Revision: 0xe2f
   LMP Version: 4.0 (0x6) Subversion: 0x9f73
   Manufacturer: Realtek Semiconductor Corporation (93)

  -

  I added the options sugested in rtl8723be.conf

  options rtl8723be fwlps=0 swlps=0

  But this did not help either.

  --

  lsmod reports:

  rfcomm 69632 12
  rtl8723be 139264 0
  btcoexist 180224 1 rtl8723be
  rtl_pci 40960 1 rtl8723be
  rtlwifi 98304 3 btcoexist,rtl_pci,rtl8723be
  hp_wmi 16384 0
  mac80211 733184 3 rtl_pci,rtlwifi,rtl8723be
  sparse_keymap 16384 1 hp_wmi
  kvm 532480 0
  irqbypass 16384 1 kvm
  btusb 45056 0
  crct10dif_pclmul 16384 0
  btrtl 16384 1 btusb
  btbcm 16384 1 btusb
  ...

  ---

  dmesg | grep rtl reports:

  [ 8.982260] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000b 
lmp_ver=06 lmp_subver=8723
  [ 8.982262] Bluetooth: hci0: rtl: loading rtl_bt/rtl8723b_fw.bin
  [ 9.064265] rtlwifi: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 9.403770] Using firmware rtlwifi/rtl8723befw.bin
  [ 9.404023] rtlwifi: channel plan 0x20
  [ 9.404027] rtlwifi: country code 11
  [ 9.422483] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
  [ 9.423458] rtlwifi: wireless switch is on

  

  modinfo rtl8723be

  filename: 
/lib/modules/4.4.0-21-generic/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8723be/rtl8723be.ko
  firmware: rtlwifi/rtl8723befw.bin
  description: Realtek 8723BE 802.11n PCI wireless
  license: GPL
  author: Realtek WlanFAE 
  author: PageHe 
  srcversion: 00619764255210776FAB54D
  alias: pci:v10ECdB723sv*sd*bc*sc*i*
  depends: rtlwifi,rtl_pci,btcoexist,mac80211
  vermagic: 4.4.0-21-generic SMP mod_unload modversions
  parm: swlps:bool
  parm: swenc:using hardware crypto (default 0 [hardware])
   (bool)
  parm: ips:using no link power save (default 1 is open)
   (bool)
  parm: fwlps:using linked fw control power save (default 1 is open)
   (bool)
  parm: msi:Set to 1 to use MSI interrupts

[Kernel-packages] [Bug 1589109] Re: I have to unplug the cable to turn xubuntu 16.04 off

2016-06-07 Thread Joseph Salisbury 
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7-rc1 kernel[0].

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

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

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


Thanks in advance.

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


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

Title:
  I have to unplug the cable to turn xubuntu 16.04 off

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  xubuntu 16.04 on a clevo m7xsun: the regular way of turning my
  computer down means, always, having to unplug the cable:

  I click on turn off and sometimes the screen freezes on the background
  and stays like that until I unplug the cable.

  Sometimes I get a blank screen and stays like that until I unplug the
  cable.

  Sometimes I get to see what the computer does (what programs are being
  shut down) and freezes on a certain process and stays like that until
  I unplug the cable...

  I have been doing it like this since 12.04, but now I'm afraid it's
  affecting the hdd.

  Apport should appear down here...
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sherman3715 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=221b0d1c-45c9-4eb3-bd93-8c0821623374
  InstallationDate: Installed on 2012-04-12 (1514 days ago)
  InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 
(20120328)
  Lsusb:
   Bus 001 Device 003: ID 0bda:8189 Realtek Semiconductor Corp. RTL8187B 
Wireless 802.11g 54Mbps Network Adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: clevo M7X0SUN
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=4bf1857c-94fa-4b07-8f1d-9beb131666fa ro acpi_osi=Linux 
acpi_backlight=nvidia
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.4.0-23-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (40 days ago)
  UserGroups: adm audio cdrom dialout dip fax fuse libvirtd lpadmin netdev 
plugdev sambashare scanner sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 05/04/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.asset.tag: 1234567890
  dmi.board.name: M7X0SUN
  dmi.board.vendor: clevo
  dmi.board.version: Bottom
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: SiS
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/04/2009:svnclevo:pnM7X0SUN:pvrRev.A1:rvnclevo:rnM7X0SUN:rvrBottom:cvnSiS:ct1:cvrN/A:
  dmi.product.name: M7X0SUN
  dmi.product.version: Rev. A1
  dmi.sys.vendor: clevo

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

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

[Kernel-packages] [Bug 1588944] Re: Incorrect 0% remaining battery detected forcing suspend

2016-06-07 Thread Dave Chiluk 
** Summary changed:

- Incorrect low-battery detected forcing suspend
+ Incorrect 0% remaining battery detected forcing suspend

** Changed in: indicator-power (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/1588944

Title:
  Incorrect 0% remaining battery detected forcing suspend

Status in indicator-power package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is detecting that my battery has depleted to low or 0% which
  results in the OS forcing suspend.  Normally this would be correct
  behavior, but in my case the battery has closer to 90% of remaining
  battery left.

  I have experienced this with 4.4.0-22 and 4.4.0-23, and am currently
  running 4.4.0-21 to see if it reproduces there as well.

  I do have -proposed enabled so it's a bit hard to determine if this is
  the kernel or something higher up the stack.

  This does seem to be mildly reproducible. 4.4.0-23 being the most
  problematic kernel so far.

  Of course this is a relatively new laptop so this could be a hardware
  issue as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chiluk 2462 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jun  3 14:07:17 2016
  HibernationDevice: RESUME=UUID=4f4ea88e-642e-4be5-bdf0-bbc7f47f5628
  InstallationDate: Installed on 2016-04-25 (38 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b531 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FBCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=249f91bb-7789-41cc-9cc0-8ba25d7f55bb ro quiet splash pcie_aspm=force 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET40W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FBCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FBCTO1WW:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FBCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FBCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1588944/+subscriptions

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

[Kernel-packages] [Bug 1588944] Re: Incorrect low-battery detected forcing suspend

2016-06-07 Thread Dave Chiluk 
Sorry Joe, this may be related to userspace as well, as I was able to
reproduce this with other kernels as well.  Although not as reliably.

** Also affects: indicator-power (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/1588944

Title:
  Incorrect low-battery detected forcing suspend

Status in indicator-power package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is detecting that my battery has depleted to low or 0% which
  results in the OS forcing suspend.  Normally this would be correct
  behavior, but in my case the battery has closer to 90% of remaining
  battery left.

  I have experienced this with 4.4.0-22 and 4.4.0-23, and am currently
  running 4.4.0-21 to see if it reproduces there as well.

  I do have -proposed enabled so it's a bit hard to determine if this is
  the kernel or something higher up the stack.

  This does seem to be mildly reproducible. 4.4.0-23 being the most
  problematic kernel so far.

  Of course this is a relatively new laptop so this could be a hardware
  issue as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chiluk 2462 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jun  3 14:07:17 2016
  HibernationDevice: RESUME=UUID=4f4ea88e-642e-4be5-bdf0-bbc7f47f5628
  InstallationDate: Installed on 2016-04-25 (38 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b531 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FBCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=249f91bb-7789-41cc-9cc0-8ba25d7f55bb ro quiet splash pcie_aspm=force 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET40W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FBCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FBCTO1WW:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FBCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FBCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1588944/+subscriptions

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

[Kernel-packages] [Bug 1588539] Re: boot from USB stick doesn't work

2016-06-07 Thread Joseph Salisbury 
Also, can you verify the integrity of the .iso file before burning your CD 
image? If you're unfamiliar with getting an MD5 sum, instructions can be found 
here:
https://help.ubuntu.com/community/HowToMD5SUM

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

Title:
  boot from USB stick doesn't work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I tried 2 images; ubuntu 16.04 64bit and kubuntu 16.04 64 bit. For each image 
I installed to a USB stick 8GB; one time using dd command under kubuntu 12.04 
and the other time LiLi USB creator under windows 7.
  Same result in all cases, the computer sees the USB stick and starts a boot, 
but that fails without any usefull error message. It just prints

  boot

  no key (incl. [TAB], ESC ) is giving any other result then

  boot

  after 30 sec the computer boots from next device - without problems.

  I have a AMD Phenom II X6, 16 Gb RAM, NVIDIA grafik card.

  regards,
  Marcus Menzel

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

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

[Kernel-packages] [Bug 1574382] Re: Default sound device changes after resuming system

2016-06-07 Thread Joseph Salisbury 
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to
email the appropriate mailing list. If no response is received, then a
bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-
reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

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

Title:
  Default sound device changes after resuming system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 and 15.10, too
  After resuming from sleep, the default sound device is set to another one, I 
have to go in the sound settings and click on the primary one to get back. Did 
not see this bug after rebooting or power on.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vanyo  2021 F pulseaudio
   /dev/snd/controlC0:  vanyo  2021 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=09b833a2-0d71-4754-acb3-f94c71921de4
  InstallationDate: Installed on 2016-02-26 (59 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=155d6a5c-c997-4711-a3d2-bd61d31d2cff ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (4 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0350.2015.0812.1722
  dmi.board.name: NUC5i7RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H73774-102
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0350.2015.0812.1722:bd08/12/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i7RYB:rvrH73774-102:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1588539] Re: boot from USB stick doesn't work

2016-06-07 Thread Joseph Salisbury 
Can you see if this issue also happens with the latest daily image?  It can be 
downloaded from:
http://cdimage.ubuntu.com/daily-live/current/

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

Title:
  boot from USB stick doesn't work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I tried 2 images; ubuntu 16.04 64bit and kubuntu 16.04 64 bit. For each image 
I installed to a USB stick 8GB; one time using dd command under kubuntu 12.04 
and the other time LiLi USB creator under windows 7.
  Same result in all cases, the computer sees the USB stick and starts a boot, 
but that fails without any usefull error message. It just prints

  boot

  no key (incl. [TAB], ESC ) is giving any other result then

  boot

  after 30 sec the computer boots from next device - without problems.

  I have a AMD Phenom II X6, 16 Gb RAM, NVIDIA grafik card.

  regards,
  Marcus Menzel

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

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

[Kernel-packages] [Bug 1587009] Re: hvc0 not present

2016-06-07 Thread Joseph Salisbury 
Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

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


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

Title:
  hvc0 not present

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  i have installed Ubuntu 16.04 with debootstrap on a XenServer 6.2.

  i have also installed xe-guest-utilities, grub-xen and linux-image-
  virtual.

  when booting the VM, i don't see anything in the XenCenter console.

  i think this is because there is no hvc0 tty.

  as written here, it should start automatically:
  http://0pointer.de/blog/projects/serial-console.html

  > lscpu
  Hypervisor vendor: Microsoft
  Virtualization type:   full

  maybe Ubuntu don't recognize Xen?

  how can i get this working?

  229-4ubuntu4

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

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

[Kernel-packages] [Bug 1589195] Re: Machine saying "no bluetooth adaptors found" even though is has been working till few days ago.

2016-06-07 Thread Joseph Salisbury 
Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of a
regression, and when this regression was introduced.   If this is a
regression, we can perform a kernel bisect to identify the commit that
introduced the problem.

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

Title:
  Machine saying "no bluetooth adaptors found" even though is has  been
  working till few days ago.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 3
  B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0002 Rev= 3.13
  S:  Manufacturer=Linux 3.13.0-87-generic ehci_hcd
  S:  Product=EHCI Host Controller
  S:  SerialNumber=:00:1d.0
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

  T:  Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480  MxCh= 8
  D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=8087 ProdID=0020 Rev= 0.00
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=256ms

  T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 3
  B:  Alloc=  0/800 us ( 0%), #Int=  1, #Iso=  0
  D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0002 Rev= 3.13
  S:  Manufacturer=Linux 3.13.0-87-generic ehci_hcd
  S:  Product=EHCI Host Controller
  S:  SerialNumber=:00:1a.0
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

  T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480  MxCh= 6
  D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=8087 ProdID=0020 Rev= 0.00
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=256ms

  T:  Bus=01 Lev=02 Prnt=02 Port=02 Cnt=01 Dev#= 19 Spd=12   MxCh= 0
  D:  Ver= 1.01 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
  P:  Vendor=147e ProdID=2016 Rev= 0.02
  S:  Manufacturer=UPEK
  S:  Product=Biometric Coprocessor
  C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
  I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)
  E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
  E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
  E:  Ad=83(I) Atr=03(Int.) MxPS=   4 Ivl=20ms
  tony@tony-ThinkPad-T410:~$ ubuntu-bug linux
  tony@tony-ThinkPad-T410:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-87-generic 3.13.0-87.133
  ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-87-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tony   2215 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Jun  5 08:46:15 2016
  HibernationDevice: RESUME=UUID=09a23d02-daef-4fd6-9db4-bff9e7f69b6c
  InstallationDate: Installed on 2014-06-27 (708 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 019: ID 147e:2016 Upek Biometric Touchchip/Touchstrip 
Fingerprint Sensor
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 25U
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-87-generic 
root=UUID=d5cfd6a7-f53e-4c84-876a-bce38ae571d0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-87-generic N/A
   linux-backports-modules-3.13.0-87-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET72WW (1.32 )
  dmi.board.name: 25U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias:

[Kernel-packages] [Bug 1590069] Re: vDSO syscalls don't work on yakkety/master-next (and unstable/master)

2016-06-07 Thread Tim Gardner 
Hmm, bare metal Yakkety with the same 4.6.0-7.8 kernel works. I attached
the copy of tester.c that I'm using.

** Attachment added: "Test program"
   
https://bugs.launchpad.net/ubuntu/yakkety/+source/linux/+bug/1590069/+attachment/4679067/+files/tester.c

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

Title:
  vDSO syscalls don't work on yakkety/master-next (and unstable/master)

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

Bug description:
  Hi guys,

  I'm having a problem where vDSO syscalls don't work on yakkety-next:

  dev:~ uname -a
  Linux dev 4.6.0-8-generic #9 SMP Mon Jun 6 14:21:30 MDT 2016 x86_64 x86_64 
x86_64 GNU/Linux
  dev:~ cat tester.c 
  #include 
  #include 
  #include 

  int main()
  {
struct timeval tv;
struct timezone tz;

while (1) {
sleep(1);
if (gettimeofday(, ) < 0) {
perror("gettimeofday");
}
}

return 0;
  }
  dev:~ make tester
  make: 'tester' is up to date.
  dev:~ strace tester
  strace: Can't stat 'tester': No such file or directory
  dev:~ 1 strace ./tester
  execve("./tester", ["./tester"], [/* 35 vars */]) = 0
  brk(NULL)   = 0x19e4000
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbca234b000
  access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or 
directory)
  open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=44113, ...}) = 0
  mmap(NULL, 44113, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fbca234
  close(3)= 0
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
  read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"..., 
832) = 832
  fstat(3, {st_mode=S_IFREG|0755, st_size=1864888, ...}) = 0
  mmap(NULL, 3967488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7fbca1d5f000
  mprotect(0x7fbca1f1f000, 2093056, PROT_NONE) = 0
  mmap(0x7fbca211e000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1bf000) = 0x7fbca211e000
  mmap(0x7fbca2124000, 14848, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fbca2124000
  close(3)= 0
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbca233f000
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbca233e000
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbca233d000
  arch_prctl(ARCH_SET_FS, 0x7fbca233e700) = 0
  mprotect(0x7fbca211e000, 16384, PROT_READ) = 0
  mprotect(0x60, 4096, PROT_READ) = 0
  mprotect(0x7fbca234d000, 4096, PROT_READ) = 0
  munmap(0x7fbca234, 44113)   = 0
  nanosleep({1, 0}, 0x7fffc8ec71f0)   = 0
  gettimeofday({1465317034, 813437}, {tz_minuteswest=0, tz_dsttime=0}) = 0
  nanosleep({1, 0}, 0x7fffc8ec71f0)   = 0
  gettimeofday({1465317035, 813718}, {tz_minuteswest=0, tz_dsttime=0}) = 0
  nanosleep({1, 0}, 0x7fffc8ec71f0)   = 0
  gettimeofday({1465317036, 814008}, {tz_minuteswest=0, tz_dsttime=0}) = 0
  nanosleep({1, 0}, ^Cstrace: Process 15793 detached
   

  whereas on a normal machine, they do:

  ~ uname -a
  Linux hopstrocity 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux
  ~ cat tester.c 
  #include 
  #include 
  #include 

  int main()
  {
struct timeval tv;
struct timezone tz;

while (1) {
sleep(1);
if (gettimeofday(, ) < 0) {
perror("gettimeofday");
}
}

return 0;
  }

  ~ make tester
  make: 'tester' is up to date.
  ~ strace ./tester
  execve("./tester", ["./tester"], [/* 60 vars */]) = 0
  brk(NULL)   = 0x12c7000
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fb544a9b000
  access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or 
directory)
  open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=143083, ...}) = 0
  mmap(NULL, 143083, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fb544a78000
  close(3)= 0
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
  read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"..., 
832) = 832
  fstat(3, {st_mode=S_IFREG|0755, st_size=1864888, ...}) = 0

[Kernel-packages] [Bug 1589704] Re: workaround cavium thunderx silicon erratum 23144

2016-06-07 Thread Robert Richter 
Upstream commit (in v4.7-rc2):

 fbf8f40e1658 irqchip/gicv3-its: numa: Enable workaround for Cavium
thunderx erratum 23144

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

Title:
  workaround cavium thunderx silicon erratum 23144

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

Bug description:
  [Impact]
  This impacts 2 socket Cavium ThunderX systems using pass-1.1 silicon, and can 
result in IO hangs.

  [Test Case]
  $ dmesg | grep "ITS command queue timeout"

  [Regression Risk]
  The workaround is in gicv3 specific code, and only activated when the hw 
revision in the IIDR matches ThunderX pass 1.x silicon, so risk to other 
platforms is minimal.

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

-- 
Mailing list: https://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 1590069] Re: vDSO syscalls don't work on yakkety/master-next (and unstable/master)

2016-06-07 Thread Tycho Andersen 
On Tue, Jun 07, 2016 at 05:23:58PM -, Tim Gardner wrote:
> Tycho - I cannot reproduce this on bare metal running linux 4.6.0-7.8
> from ppa:canonical-kernel-team/ppa using Xenial user space. Lemme try
> Yakkety user space.

The kernel I used had a 4.6.0-8 version number, I assume because I'm
using the -next branch and not what's currently in master. Could that
be the difference?

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

Title:
  vDSO syscalls don't work on yakkety/master-next (and unstable/master)

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

Bug description:
  Hi guys,

  I'm having a problem where vDSO syscalls don't work on yakkety-next:

  dev:~ uname -a
  Linux dev 4.6.0-8-generic #9 SMP Mon Jun 6 14:21:30 MDT 2016 x86_64 x86_64 
x86_64 GNU/Linux
  dev:~ cat tester.c 
  #include 
  #include 
  #include 

  int main()
  {
struct timeval tv;
struct timezone tz;

while (1) {
sleep(1);
if (gettimeofday(, ) < 0) {
perror("gettimeofday");
}
}

return 0;
  }
  dev:~ make tester
  make: 'tester' is up to date.
  dev:~ strace tester
  strace: Can't stat 'tester': No such file or directory
  dev:~ 1 strace ./tester
  execve("./tester", ["./tester"], [/* 35 vars */]) = 0
  brk(NULL)   = 0x19e4000
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbca234b000
  access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or 
directory)
  open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=44113, ...}) = 0
  mmap(NULL, 44113, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fbca234
  close(3)= 0
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
  read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"..., 
832) = 832
  fstat(3, {st_mode=S_IFREG|0755, st_size=1864888, ...}) = 0
  mmap(NULL, 3967488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7fbca1d5f000
  mprotect(0x7fbca1f1f000, 2093056, PROT_NONE) = 0
  mmap(0x7fbca211e000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1bf000) = 0x7fbca211e000
  mmap(0x7fbca2124000, 14848, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fbca2124000
  close(3)= 0
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbca233f000
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbca233e000
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbca233d000
  arch_prctl(ARCH_SET_FS, 0x7fbca233e700) = 0
  mprotect(0x7fbca211e000, 16384, PROT_READ) = 0
  mprotect(0x60, 4096, PROT_READ) = 0
  mprotect(0x7fbca234d000, 4096, PROT_READ) = 0
  munmap(0x7fbca234, 44113)   = 0
  nanosleep({1, 0}, 0x7fffc8ec71f0)   = 0
  gettimeofday({1465317034, 813437}, {tz_minuteswest=0, tz_dsttime=0}) = 0
  nanosleep({1, 0}, 0x7fffc8ec71f0)   = 0
  gettimeofday({1465317035, 813718}, {tz_minuteswest=0, tz_dsttime=0}) = 0
  nanosleep({1, 0}, 0x7fffc8ec71f0)   = 0
  gettimeofday({1465317036, 814008}, {tz_minuteswest=0, tz_dsttime=0}) = 0
  nanosleep({1, 0}, ^Cstrace: Process 15793 detached
   

  whereas on a normal machine, they do:

  ~ uname -a
  Linux hopstrocity 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux
  ~ cat tester.c 
  #include 
  #include 
  #include 

  int main()
  {
struct timeval tv;
struct timezone tz;

while (1) {
sleep(1);
if (gettimeofday(, ) < 0) {
perror("gettimeofday");
}
}

return 0;
  }

  ~ make tester
  make: 'tester' is up to date.
  ~ strace ./tester
  execve("./tester", ["./tester"], [/* 60 vars */]) = 0
  brk(NULL)   = 0x12c7000
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fb544a9b000
  access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or 
directory)
  open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=143083, ...}) = 0
  mmap(NULL, 143083, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fb544a78000
  close(3)= 0
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
  read(3,

[Kernel-packages] [Bug 1590069] Re: vDSO syscalls don't work on yakkety/master-next (and unstable/master)

2016-06-07 Thread Tim Gardner 
Tycho - I cannot reproduce this on bare metal running linux 4.6.0-7.8
from ppa:canonical-kernel-team/ppa using Xenial user space. Lemme try
Yakkety user space.

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

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

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

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

Title:
  vDSO syscalls don't work on yakkety/master-next (and unstable/master)

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

Bug description:
  Hi guys,

  I'm having a problem where vDSO syscalls don't work on yakkety-next:

  dev:~ uname -a
  Linux dev 4.6.0-8-generic #9 SMP Mon Jun 6 14:21:30 MDT 2016 x86_64 x86_64 
x86_64 GNU/Linux
  dev:~ cat tester.c 
  #include 
  #include 
  #include 

  int main()
  {
struct timeval tv;
struct timezone tz;

while (1) {
sleep(1);
if (gettimeofday(, ) < 0) {
perror("gettimeofday");
}
}

return 0;
  }
  dev:~ make tester
  make: 'tester' is up to date.
  dev:~ strace tester
  strace: Can't stat 'tester': No such file or directory
  dev:~ 1 strace ./tester
  execve("./tester", ["./tester"], [/* 35 vars */]) = 0
  brk(NULL)   = 0x19e4000
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbca234b000
  access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or 
directory)
  open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=44113, ...}) = 0
  mmap(NULL, 44113, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fbca234
  close(3)= 0
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
  read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"..., 
832) = 832
  fstat(3, {st_mode=S_IFREG|0755, st_size=1864888, ...}) = 0
  mmap(NULL, 3967488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7fbca1d5f000
  mprotect(0x7fbca1f1f000, 2093056, PROT_NONE) = 0
  mmap(0x7fbca211e000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1bf000) = 0x7fbca211e000
  mmap(0x7fbca2124000, 14848, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fbca2124000
  close(3)= 0
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbca233f000
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbca233e000
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbca233d000
  arch_prctl(ARCH_SET_FS, 0x7fbca233e700) = 0
  mprotect(0x7fbca211e000, 16384, PROT_READ) = 0
  mprotect(0x60, 4096, PROT_READ) = 0
  mprotect(0x7fbca234d000, 4096, PROT_READ) = 0
  munmap(0x7fbca234, 44113)   = 0
  nanosleep({1, 0}, 0x7fffc8ec71f0)   = 0
  gettimeofday({1465317034, 813437}, {tz_minuteswest=0, tz_dsttime=0}) = 0
  nanosleep({1, 0}, 0x7fffc8ec71f0)   = 0
  gettimeofday({1465317035, 813718}, {tz_minuteswest=0, tz_dsttime=0}) = 0
  nanosleep({1, 0}, 0x7fffc8ec71f0)   = 0
  gettimeofday({1465317036, 814008}, {tz_minuteswest=0, tz_dsttime=0}) = 0
  nanosleep({1, 0}, ^Cstrace: Process 15793 detached
   

  whereas on a normal machine, they do:

  ~ uname -a
  Linux hopstrocity 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux
  ~ cat tester.c 
  #include 
  #include 
  #include 

  int main()
  {
struct timeval tv;
struct timezone tz;

while (1) {
sleep(1);
if (gettimeofday(, ) < 0) {
perror("gettimeofday");
}
}

return 0;
  }

  ~ make tester
  make: 'tester' is up to date.
  ~ strace ./tester
  execve("./tester", ["./tester"], [/* 60 vars */]) = 0
  brk(NULL)   = 0x12c7000
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fb544a9b000
  access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or 
directory)
  open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=143083, ...}) = 0
  mmap(NULL, 143083, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fb544a78000
  close(3)= 0
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  open("/lib/x86_64-linux-gnu/libc.so.6",

[Kernel-packages] [Bug 1590072] Re: kernel 4.4.0-21.37-generic in 16.04 sees no disks on HP ProLiant BL465c Gen8 if IOMMU is enabled

2016-06-07 Thread Daniel 
Can't send the apport-collect while I don't have the full OS installed.


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

Title:
  kernel 4.4.0-21.37-generic in 16.04 sees no disks on HP ProLiant
  BL465c Gen8  if IOMMU is enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When trying to install 16.04 LTS on a BL465c Gen8, the default kernel
  4.4.0-21.37-generic does not detect the disks with IOMMU enabled.

  Using the HP iLO Cli, shows that the server have some hardware error:

  enclosure68-a> show server status 4
  Blade #4 Status:
  Power: On
  Current Wattage used: 343
  Health: Failed
  Unit Identification LED: Blinking
  Virtual Fan: 100%
  Diagnostic Status:
  Internal DataOK
  Management Processor OK
  I/O ConfigurationOK
  PowerOK
  Cooling  OK
  Location OK
  Device Failure   Failed
  Device Degraded  OK
  VCM Configured   Other
  iLO Network  OK
  Mezzanine Card   OK

  This device failure in the blade is OK after a reboot.

  Disabling IOMMU on BIOS and the 16.04 installation goes successfully. 
  I tried to enable IOMMU after the installation and the problem appears. The 
disk is not detected and it can't boot normally.
  Ubuntu 14.04 LTS boots and run fine on these machines.

  dmesg ouput with IOMMU enabled.

  [   82.295300] HP HPSA Driver (v 3.4.14-0)
  [   82.295327] hpsa :03:00.0: can't disable ASPM; OS doesn't have ASPM 
control
  [   82.295350] hpsa :03:00.0: MSI-X capable controller
  [   82.295993] pps_core: LinuxPPS API ver. 1 registered
  [   82.295996] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo 
Giometti 
  [   82.297857] PTP clock support registered
  [   82.316730] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 
1.712.30-0 (2014/02/10)
  [   82.320096] AVX version of gcm_enc/dec engaged.
  [   82.320100] AES CTR mode by8 optimization enabled
  [   82.320501] ACPI: PCI Interrupt Link [I0C0] enabled at IRQ 36
  [   82.320614] bnx2x :04:00.0: msix capability found
  [   82.320755] bnx2x :04:00.0: part number 0-0-0-0
  [   82.443473] ACPI: PCI Interrupt Link [I0C1] enabled at IRQ 37
  [   82.443510] bnx2x :04:00.1: msix capability found
  [   82.443615] bnx2x :04:00.1: part number 0-0-0-0
  [   82.563309] ipmi_si IPI0001:00: Found new BMC (man_id: 0x0b, prod_id: 
0x2020, dev_id: 0x13)
  [   82.563320] ipmi_si IPI0001:00: IPMI kcs interface initialized
  [   82.566422] bnx2x :04:00.0 eno1: renamed from eth0
  [   82.585454] bnx2x :04:00.1 eno2: renamed from eth1
  [  207.105793] hpsa :03:00.0: board not ready, timed out.

  dmesg with IOMMU disabled.

  [   80.818467] HP HPSA Driver (v 3.4.14-0)
  [   80.818493] hpsa :03:00.0: can't disable ASPM; OS doesn't have ASPM 
control
  [   80.818514] hpsa :03:00.0: MSI-X capable controller
  [   80.818878] hpsa :03:00.0: Logical aborts not supported
  [   80.818881] hpsa :03:00.0: HP SSD Smart Path aborts not supported
  [   80.819325] pps_core: LinuxPPS API ver. 1 registered
  [   80.819328] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo 
Giometti 
  [   80.821272] PTP clock support registered
  [   80.838135] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 
1.712.30-0 (2014/02/10)
  [   80.838402] bnx2x :04:00.0: msix capability found
  [   80.838535] bnx2x :04:00.0: part number 0-0-0-0
  [   80.841536] AVX version of gcm_enc/dec engaged.
  [   80.841541] AES CTR mode by8 optimization enabled
  [   80.864399] scsi host4: hpsa
  [   80.872507] hpsa :03:00.0: scsi 4:3:0:0: added RAID  HP
   P220icontroller SSDSmartPathCap- En- Exp=1
  [   80.872513] hpsa :03:00.0: scsi 4:0:0:0: masked Direct-Access ATA  
VK0240GDJXU  PHYS DRV SSDSmartPathCap- En- Exp=0
  [   80.872517] hpsa :03:00.0: scsi 4:0:1:0: masked Direct-Access ATA  
VK0240GDJXU  PHYS DRV SSDSmartPathCap- En- Exp=0
  [   80.872521] hpsa :03:00.0: scsi 4:1:0:0: added Direct-Access HP
   LOGICAL VOLUME   RAID-1(+0) SSDSmartPathCap- En- Exp=1
  [   80.873094] scsi 4:0:0:0: RAID  HP   P220i6.68 
PQ: 0 ANSI: 5
  [   80.873416] scsi 4:1:0:0: Direct-Access HP   LOGICAL VOLUME   6.68 
PQ: 0 ANSI: 5
  [

[Kernel-packages] [Bug 1535470] Re: Backlight brightness keys not working

2016-06-07 Thread dhenry 
Well, the main purpose of my comment was to give some hints to Ian with
his laptop, in case it could help him, because we have some common
hardware parts...

I can fill a new bug for my case, but what do you mean by "Ubuntu repository 
kernel"?
Currently, I'm running the 4.6 kernel from ~kernel-ppa/mainline/, which is also 
(in some way) an Ubuntu repository, isn't it?
Should I switch back to the standard 4.4 kernel from main repository in order 
to fill my bug?

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

Title:
  Backlight brightness keys not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Originally described in bug 1533221. This is a new bug to track this
  additional issue separately.

  The above bug has h/w info attached etc. This is a new skylake
  chipset.

  Backlight function keys are not working. I have tried various
  combinations of:

  acpi_osi=Linux acpi_backlight=native
  acpi_osi=Linux acpi_backlight=vendor
  acpi_osi=! acpi_backlight=vendor
  etc, etc

  with no luck.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian2218 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=df036c01-8f22-4d8f-ad55-6add4f99f5f4
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 5986:066d Acer, Inc 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65_P67RGRERA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-0-generic 
root=UUID=2077d068-d7ee-4407-89e1-7d2b884173de ro acpi_osi=Linux 
acpi_backlight=native drm.debug=14
  ProcVersionSignature: Ubuntu 4.4.0-0.12-generic 4.4.0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-0-generic N/A
   linux-backports-modules-4.4.0-0-generic  N/A
   linux-firmware   1.155
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.4.0-0-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.10
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_P67RGRERA
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.10:bd11/20/2015:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P65_P67RGRERA
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

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

2016-06-07 Thread Brad Figg 
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1590069

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

Title:
  vDSO syscalls don't work on yakkety/master-next (and unstable/master)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi guys,

  I'm having a problem where vDSO syscalls don't work on yakkety-next:

  dev:~ uname -a
  Linux dev 4.6.0-8-generic #9 SMP Mon Jun 6 14:21:30 MDT 2016 x86_64 x86_64 
x86_64 GNU/Linux
  dev:~ cat tester.c 
  #include 
  #include 
  #include 

  int main()
  {
struct timeval tv;
struct timezone tz;

while (1) {
sleep(1);
if (gettimeofday(, ) < 0) {
perror("gettimeofday");
}
}

return 0;
  }
  dev:~ make tester
  make: 'tester' is up to date.
  dev:~ strace tester
  strace: Can't stat 'tester': No such file or directory
  dev:~ 1 strace ./tester
  execve("./tester", ["./tester"], [/* 35 vars */]) = 0
  brk(NULL)   = 0x19e4000
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbca234b000
  access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or 
directory)
  open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=44113, ...}) = 0
  mmap(NULL, 44113, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fbca234
  close(3)= 0
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
  read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"..., 
832) = 832
  fstat(3, {st_mode=S_IFREG|0755, st_size=1864888, ...}) = 0
  mmap(NULL, 3967488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7fbca1d5f000
  mprotect(0x7fbca1f1f000, 2093056, PROT_NONE) = 0
  mmap(0x7fbca211e000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1bf000) = 0x7fbca211e000
  mmap(0x7fbca2124000, 14848, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fbca2124000
  close(3)= 0
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbca233f000
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbca233e000
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbca233d000
  arch_prctl(ARCH_SET_FS, 0x7fbca233e700) = 0
  mprotect(0x7fbca211e000, 16384, PROT_READ) = 0
  mprotect(0x60, 4096, PROT_READ) = 0
  mprotect(0x7fbca234d000, 4096, PROT_READ) = 0
  munmap(0x7fbca234, 44113)   = 0
  nanosleep({1, 0}, 0x7fffc8ec71f0)   = 0
  gettimeofday({1465317034, 813437}, {tz_minuteswest=0, tz_dsttime=0}) = 0
  nanosleep({1, 0}, 0x7fffc8ec71f0)   = 0
  gettimeofday({1465317035, 813718}, {tz_minuteswest=0, tz_dsttime=0}) = 0
  nanosleep({1, 0}, 0x7fffc8ec71f0)   = 0
  gettimeofday({1465317036, 814008}, {tz_minuteswest=0, tz_dsttime=0}) = 0
  nanosleep({1, 0}, ^Cstrace: Process 15793 detached
   

  whereas on a normal machine, they do:

  ~ uname -a
  Linux hopstrocity 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux
  ~ cat tester.c 
  #include 
  #include 
  #include 

  int main()
  {
struct timeval tv;
struct timezone tz;

while (1) {
sleep(1);
if (gettimeofday(, ) < 0) {
perror("gettimeofday");
}
}

return 0;
  }

  ~ make tester
  make: 'tester' is up to date.
  ~ strace ./tester
  execve("./tester", ["./tester"], [/* 60 vars */]) = 0
  brk(NULL)   = 0x12c7000
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fb544a9b000
  access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or 
directory)
  open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=143083, ...}) = 0
  mmap(NULL, 143083, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fb544a78000
  close(3)= 0
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)

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

2016-06-07 Thread Brad Figg 
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1590072

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

Title:
  kernel 4.4.0-21.37-generic in 16.04 sees no disks on HP ProLiant
  BL465c Gen8  if IOMMU is enabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When trying to install 16.04 LTS on a BL465c Gen8, the default kernel
  4.4.0-21.37-generic does not detect the disks with IOMMU enabled.

  Using the HP iLO Cli, shows that the server have some hardware error:

  enclosure68-a> show server status 4
  Blade #4 Status:
  Power: On
  Current Wattage used: 343
  Health: Failed
  Unit Identification LED: Blinking
  Virtual Fan: 100%
  Diagnostic Status:
  Internal DataOK
  Management Processor OK
  I/O ConfigurationOK
  PowerOK
  Cooling  OK
  Location OK
  Device Failure   Failed
  Device Degraded  OK
  VCM Configured   Other
  iLO Network  OK
  Mezzanine Card   OK

  This device failure in the blade is OK after a reboot.

  Disabling IOMMU on BIOS and the 16.04 installation goes successfully. 
  I tried to enable IOMMU after the installation and the problem appears. The 
disk is not detected and it can't boot normally.
  Ubuntu 14.04 LTS boots and run fine on these machines.

  dmesg ouput with IOMMU enabled.

  [   82.295300] HP HPSA Driver (v 3.4.14-0)
  [   82.295327] hpsa :03:00.0: can't disable ASPM; OS doesn't have ASPM 
control
  [   82.295350] hpsa :03:00.0: MSI-X capable controller
  [   82.295993] pps_core: LinuxPPS API ver. 1 registered
  [   82.295996] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo 
Giometti 
  [   82.297857] PTP clock support registered
  [   82.316730] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 
1.712.30-0 (2014/02/10)
  [   82.320096] AVX version of gcm_enc/dec engaged.
  [   82.320100] AES CTR mode by8 optimization enabled
  [   82.320501] ACPI: PCI Interrupt Link [I0C0] enabled at IRQ 36
  [   82.320614] bnx2x :04:00.0: msix capability found
  [   82.320755] bnx2x :04:00.0: part number 0-0-0-0
  [   82.443473] ACPI: PCI Interrupt Link [I0C1] enabled at IRQ 37
  [   82.443510] bnx2x :04:00.1: msix capability found
  [   82.443615] bnx2x :04:00.1: part number 0-0-0-0
  [   82.563309] ipmi_si IPI0001:00: Found new BMC (man_id: 0x0b, prod_id: 
0x2020, dev_id: 0x13)
  [   82.563320] ipmi_si IPI0001:00: IPMI kcs interface initialized
  [   82.566422] bnx2x :04:00.0 eno1: renamed from eth0
  [   82.585454] bnx2x :04:00.1 eno2: renamed from eth1
  [  207.105793] hpsa :03:00.0: board not ready, timed out.

  dmesg with IOMMU disabled.

  [   80.818467] HP HPSA Driver (v 3.4.14-0)
  [   80.818493] hpsa :03:00.0: can't disable ASPM; OS doesn't have ASPM 
control
  [   80.818514] hpsa :03:00.0: MSI-X capable controller
  [   80.818878] hpsa :03:00.0: Logical aborts not supported
  [   80.818881] hpsa :03:00.0: HP SSD Smart Path aborts not supported
  [   80.819325] pps_core: LinuxPPS API ver. 1 registered
  [   80.819328] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo 
Giometti 
  [   80.821272] PTP clock support registered
  [   80.838135] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 
1.712.30-0 (2014/02/10)
  [   80.838402] bnx2x :04:00.0: msix capability found
  [   80.838535] bnx2x :04:00.0: part number 0-0-0-0
  [   80.841536] AVX version of gcm_enc/dec engaged.
  [   80.841541] AES CTR mode by8 optimization enabled
  [   80.864399] scsi host4: hpsa
  [   80.872507] hpsa :03:00.0: scsi 4:3:0:0: added RAID  HP
   P220icontroller SSDSmartPathCap- En- Exp=1
  [   80.872513] hpsa :03:00.0: scsi 4:0:0:0: masked Direct-Access ATA  
VK0240GDJXU  PHYS DRV SSDSmartPathCap- En- Exp=0
  [   80.872517] hpsa :03:00.0: scsi 4:0:1:0: masked Direct-Access ATA  
VK0240GDJXU

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

2016-06-07 Thread Frank Heimes 
** Changed in: ubuntu-z-systems
   Status: Triaged => 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/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr  6 12:57:10 s390-dasd[6877]: INFO: s390-dasd: no channel found
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-zfcp' selected
  Apr  6 12:57:10 s390-zfcp[6891]:

[Kernel-packages] [Bug 1590072] Re: kernel 4.4.0-21.37-generic in 16.04 sees no disks on HP ProLiant BL465c Gen8 if IOMMU is enabled

2016-06-07 Thread Daniel 
** Attachment added: "dmesg-iommu-disabled"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590072/+attachment/4679049/+files/dmesg-iommu-disabled

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

Title:
  kernel 4.4.0-21.37-generic in 16.04 sees no disks on HP ProLiant
  BL465c Gen8  if IOMMU is enabled

Status in linux package in Ubuntu:
  New

Bug description:
  When trying to install 16.04 LTS on a BL465c Gen8, the default kernel
  4.4.0-21.37-generic does not detect the disks with IOMMU enabled.

  Using the HP iLO Cli, shows that the server have some hardware error:

  enclosure68-a> show server status 4
  Blade #4 Status:
  Power: On
  Current Wattage used: 343
  Health: Failed
  Unit Identification LED: Blinking
  Virtual Fan: 100%
  Diagnostic Status:
  Internal DataOK
  Management Processor OK
  I/O ConfigurationOK
  PowerOK
  Cooling  OK
  Location OK
  Device Failure   Failed
  Device Degraded  OK
  VCM Configured   Other
  iLO Network  OK
  Mezzanine Card   OK

  This device failure in the blade is OK after a reboot.

  Disabling IOMMU on BIOS and the 16.04 installation goes successfully. 
  I tried to enable IOMMU after the installation and the problem appears. The 
disk is not detected and it can't boot normally.
  Ubuntu 14.04 LTS boots and run fine on these machines.

  dmesg ouput with IOMMU enabled.

  [   82.295300] HP HPSA Driver (v 3.4.14-0)
  [   82.295327] hpsa :03:00.0: can't disable ASPM; OS doesn't have ASPM 
control
  [   82.295350] hpsa :03:00.0: MSI-X capable controller
  [   82.295993] pps_core: LinuxPPS API ver. 1 registered
  [   82.295996] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo 
Giometti 
  [   82.297857] PTP clock support registered
  [   82.316730] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 
1.712.30-0 (2014/02/10)
  [   82.320096] AVX version of gcm_enc/dec engaged.
  [   82.320100] AES CTR mode by8 optimization enabled
  [   82.320501] ACPI: PCI Interrupt Link [I0C0] enabled at IRQ 36
  [   82.320614] bnx2x :04:00.0: msix capability found
  [   82.320755] bnx2x :04:00.0: part number 0-0-0-0
  [   82.443473] ACPI: PCI Interrupt Link [I0C1] enabled at IRQ 37
  [   82.443510] bnx2x :04:00.1: msix capability found
  [   82.443615] bnx2x :04:00.1: part number 0-0-0-0
  [   82.563309] ipmi_si IPI0001:00: Found new BMC (man_id: 0x0b, prod_id: 
0x2020, dev_id: 0x13)
  [   82.563320] ipmi_si IPI0001:00: IPMI kcs interface initialized
  [   82.566422] bnx2x :04:00.0 eno1: renamed from eth0
  [   82.585454] bnx2x :04:00.1 eno2: renamed from eth1
  [  207.105793] hpsa :03:00.0: board not ready, timed out.

  dmesg with IOMMU disabled.

  [   80.818467] HP HPSA Driver (v 3.4.14-0)
  [   80.818493] hpsa :03:00.0: can't disable ASPM; OS doesn't have ASPM 
control
  [   80.818514] hpsa :03:00.0: MSI-X capable controller
  [   80.818878] hpsa :03:00.0: Logical aborts not supported
  [   80.818881] hpsa :03:00.0: HP SSD Smart Path aborts not supported
  [   80.819325] pps_core: LinuxPPS API ver. 1 registered
  [   80.819328] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo 
Giometti 
  [   80.821272] PTP clock support registered
  [   80.838135] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 
1.712.30-0 (2014/02/10)
  [   80.838402] bnx2x :04:00.0: msix capability found
  [   80.838535] bnx2x :04:00.0: part number 0-0-0-0
  [   80.841536] AVX version of gcm_enc/dec engaged.
  [   80.841541] AES CTR mode by8 optimization enabled
  [   80.864399] scsi host4: hpsa
  [   80.872507] hpsa :03:00.0: scsi 4:3:0:0: added RAID  HP
   P220icontroller SSDSmartPathCap- En- Exp=1
  [   80.872513] hpsa :03:00.0: scsi 4:0:0:0: masked Direct-Access ATA  
VK0240GDJXU  PHYS DRV SSDSmartPathCap- En- Exp=0
  [   80.872517] hpsa :03:00.0: scsi 4:0:1:0: masked Direct-Access ATA  
VK0240GDJXU  PHYS DRV SSDSmartPathCap- En- Exp=0
  [   80.872521] hpsa :03:00.0: scsi 4:1:0:0: added Direct-Access HP
   LOGICAL VOLUME   RAID-1(+0) SSDSmartPathCap- En- Exp=1
  [   80.873094] scsi 4:0:0:0: RAID  HP   P220i6.68 
PQ: 0 ANSI: 5
  [   80.873416] scsi 4:1:0:0: Direct-Access HP   LOGICAL VOLUME   6.68 
PQ: 0

[Kernel-packages] [Bug 1590072] Re: kernel 4.4.0-21.37-generic in 16.04 sees no disks on HP ProLiant BL465c Gen8 if IOMMU is enabled

2016-06-07 Thread Daniel 
** Attachment added: "dmesg-iommu-enabled"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590072/+attachment/4679048/+files/dmesg-iommu-enabled

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

Title:
  kernel 4.4.0-21.37-generic in 16.04 sees no disks on HP ProLiant
  BL465c Gen8  if IOMMU is enabled

Status in linux package in Ubuntu:
  New

Bug description:
  When trying to install 16.04 LTS on a BL465c Gen8, the default kernel
  4.4.0-21.37-generic does not detect the disks with IOMMU enabled.

  Using the HP iLO Cli, shows that the server have some hardware error:

  enclosure68-a> show server status 4
  Blade #4 Status:
  Power: On
  Current Wattage used: 343
  Health: Failed
  Unit Identification LED: Blinking
  Virtual Fan: 100%
  Diagnostic Status:
  Internal DataOK
  Management Processor OK
  I/O ConfigurationOK
  PowerOK
  Cooling  OK
  Location OK
  Device Failure   Failed
  Device Degraded  OK
  VCM Configured   Other
  iLO Network  OK
  Mezzanine Card   OK

  This device failure in the blade is OK after a reboot.

  Disabling IOMMU on BIOS and the 16.04 installation goes successfully. 
  I tried to enable IOMMU after the installation and the problem appears. The 
disk is not detected and it can't boot normally.
  Ubuntu 14.04 LTS boots and run fine on these machines.

  dmesg ouput with IOMMU enabled.

  [   82.295300] HP HPSA Driver (v 3.4.14-0)
  [   82.295327] hpsa :03:00.0: can't disable ASPM; OS doesn't have ASPM 
control
  [   82.295350] hpsa :03:00.0: MSI-X capable controller
  [   82.295993] pps_core: LinuxPPS API ver. 1 registered
  [   82.295996] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo 
Giometti 
  [   82.297857] PTP clock support registered
  [   82.316730] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 
1.712.30-0 (2014/02/10)
  [   82.320096] AVX version of gcm_enc/dec engaged.
  [   82.320100] AES CTR mode by8 optimization enabled
  [   82.320501] ACPI: PCI Interrupt Link [I0C0] enabled at IRQ 36
  [   82.320614] bnx2x :04:00.0: msix capability found
  [   82.320755] bnx2x :04:00.0: part number 0-0-0-0
  [   82.443473] ACPI: PCI Interrupt Link [I0C1] enabled at IRQ 37
  [   82.443510] bnx2x :04:00.1: msix capability found
  [   82.443615] bnx2x :04:00.1: part number 0-0-0-0
  [   82.563309] ipmi_si IPI0001:00: Found new BMC (man_id: 0x0b, prod_id: 
0x2020, dev_id: 0x13)
  [   82.563320] ipmi_si IPI0001:00: IPMI kcs interface initialized
  [   82.566422] bnx2x :04:00.0 eno1: renamed from eth0
  [   82.585454] bnx2x :04:00.1 eno2: renamed from eth1
  [  207.105793] hpsa :03:00.0: board not ready, timed out.

  dmesg with IOMMU disabled.

  [   80.818467] HP HPSA Driver (v 3.4.14-0)
  [   80.818493] hpsa :03:00.0: can't disable ASPM; OS doesn't have ASPM 
control
  [   80.818514] hpsa :03:00.0: MSI-X capable controller
  [   80.818878] hpsa :03:00.0: Logical aborts not supported
  [   80.818881] hpsa :03:00.0: HP SSD Smart Path aborts not supported
  [   80.819325] pps_core: LinuxPPS API ver. 1 registered
  [   80.819328] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo 
Giometti 
  [   80.821272] PTP clock support registered
  [   80.838135] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 
1.712.30-0 (2014/02/10)
  [   80.838402] bnx2x :04:00.0: msix capability found
  [   80.838535] bnx2x :04:00.0: part number 0-0-0-0
  [   80.841536] AVX version of gcm_enc/dec engaged.
  [   80.841541] AES CTR mode by8 optimization enabled
  [   80.864399] scsi host4: hpsa
  [   80.872507] hpsa :03:00.0: scsi 4:3:0:0: added RAID  HP
   P220icontroller SSDSmartPathCap- En- Exp=1
  [   80.872513] hpsa :03:00.0: scsi 4:0:0:0: masked Direct-Access ATA  
VK0240GDJXU  PHYS DRV SSDSmartPathCap- En- Exp=0
  [   80.872517] hpsa :03:00.0: scsi 4:0:1:0: masked Direct-Access ATA  
VK0240GDJXU  PHYS DRV SSDSmartPathCap- En- Exp=0
  [   80.872521] hpsa :03:00.0: scsi 4:1:0:0: added Direct-Access HP
   LOGICAL VOLUME   RAID-1(+0) SSDSmartPathCap- En- Exp=1
  [   80.873094] scsi 4:0:0:0: RAID  HP   P220i6.68 
PQ: 0 ANSI: 5
  [   80.873416] scsi 4:1:0:0: Direct-Access HP   LOGICAL VOLUME   6.68 
PQ: 0 ANSI:

[Kernel-packages] [Bug 1590072] [NEW] kernel 4.4.0-21.37-generic in 16.04 sees no disks on HP ProLiant BL465c Gen8 if IOMMU is enabled

2016-06-07 Thread Daniel 
Public bug reported:

When trying to install 16.04 LTS on a BL465c Gen8, the default kernel
4.4.0-21.37-generic does not detect the disks with IOMMU enabled.

Using the HP iLO Cli, shows that the server have some hardware error:

enclosure68-a> show server status 4
Blade #4 Status:
Power: On
Current Wattage used: 343
Health: Failed
Unit Identification LED: Blinking
Virtual Fan: 100%
Diagnostic Status:
Internal DataOK
Management Processor OK
I/O ConfigurationOK
PowerOK
Cooling  OK
Location OK
Device Failure   Failed
Device Degraded  OK
VCM Configured   Other
iLO Network  OK
Mezzanine Card   OK

This device failure in the blade is OK after a reboot.

Disabling IOMMU on BIOS and the 16.04 installation goes successfully. 
I tried to enable IOMMU after the installation and the problem appears. The 
disk is not detected and it can't boot normally.
Ubuntu 14.04 LTS boots and run fine on these machines.

dmesg ouput with IOMMU enabled.

[   82.295300] HP HPSA Driver (v 3.4.14-0)
[   82.295327] hpsa :03:00.0: can't disable ASPM; OS doesn't have ASPM 
control
[   82.295350] hpsa :03:00.0: MSI-X capable controller
[   82.295993] pps_core: LinuxPPS API ver. 1 registered
[   82.295996] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo 
Giometti 
[   82.297857] PTP clock support registered
[   82.316730] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 
1.712.30-0 (2014/02/10)
[   82.320096] AVX version of gcm_enc/dec engaged.
[   82.320100] AES CTR mode by8 optimization enabled
[   82.320501] ACPI: PCI Interrupt Link [I0C0] enabled at IRQ 36
[   82.320614] bnx2x :04:00.0: msix capability found
[   82.320755] bnx2x :04:00.0: part number 0-0-0-0
[   82.443473] ACPI: PCI Interrupt Link [I0C1] enabled at IRQ 37
[   82.443510] bnx2x :04:00.1: msix capability found
[   82.443615] bnx2x :04:00.1: part number 0-0-0-0
[   82.563309] ipmi_si IPI0001:00: Found new BMC (man_id: 0x0b, prod_id: 
0x2020, dev_id: 0x13)
[   82.563320] ipmi_si IPI0001:00: IPMI kcs interface initialized
[   82.566422] bnx2x :04:00.0 eno1: renamed from eth0
[   82.585454] bnx2x :04:00.1 eno2: renamed from eth1
[  207.105793] hpsa :03:00.0: board not ready, timed out.

dmesg with IOMMU disabled.

[   80.818467] HP HPSA Driver (v 3.4.14-0)
[   80.818493] hpsa :03:00.0: can't disable ASPM; OS doesn't have ASPM 
control
[   80.818514] hpsa :03:00.0: MSI-X capable controller
[   80.818878] hpsa :03:00.0: Logical aborts not supported
[   80.818881] hpsa :03:00.0: HP SSD Smart Path aborts not supported
[   80.819325] pps_core: LinuxPPS API ver. 1 registered
[   80.819328] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo 
Giometti 
[   80.821272] PTP clock support registered
[   80.838135] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 
1.712.30-0 (2014/02/10)
[   80.838402] bnx2x :04:00.0: msix capability found
[   80.838535] bnx2x :04:00.0: part number 0-0-0-0
[   80.841536] AVX version of gcm_enc/dec engaged.
[   80.841541] AES CTR mode by8 optimization enabled
[   80.864399] scsi host4: hpsa
[   80.872507] hpsa :03:00.0: scsi 4:3:0:0: added RAID  HP  
 P220icontroller SSDSmartPathCap- En- Exp=1
[   80.872513] hpsa :03:00.0: scsi 4:0:0:0: masked Direct-Access ATA
  VK0240GDJXU  PHYS DRV SSDSmartPathCap- En- Exp=0
[   80.872517] hpsa :03:00.0: scsi 4:0:1:0: masked Direct-Access ATA
  VK0240GDJXU  PHYS DRV SSDSmartPathCap- En- Exp=0
[   80.872521] hpsa :03:00.0: scsi 4:1:0:0: added Direct-Access HP  
 LOGICAL VOLUME   RAID-1(+0) SSDSmartPathCap- En- Exp=1
[   80.873094] scsi 4:0:0:0: RAID  HP   P220i6.68 
PQ: 0 ANSI: 5
[   80.873416] scsi 4:1:0:0: Direct-Access HP   LOGICAL VOLUME   6.68 
PQ: 0 ANSI: 5
[   80.873775] scsi 4:0:0:0: Attached scsi generic sg1 type 12
[   80.874046] sd 4:1:0:0: Attached scsi generic sg2 type 0
[   80.874081] sd 4:1:0:0: [sda] 468792000 512-byte logical blocks: (240 GB/224 
GiB)
[   80.874308] sd 4:1:0:0: [sda] Write Protect is off
[   80.874312] sd 4:1:0:0: [sda] Mode Sense: 73 00 00 08
[   80.874395] sd 4:1:0:0: [sda] Write cache: disabled, read cache: enabled, 
doesn't support DPO or FUA
[   80.875958] sd 4:1:0:0: [sda] Attached SCSI disk

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


** Tags: blade

** Attachment added:

[Kernel-packages] [Bug 1590069] [NEW] vDSO syscalls don't work on yakkety/master-next (and unstable/master)

2016-06-07 Thread Tycho Andersen 
Public bug reported:

Hi guys,

I'm having a problem where vDSO syscalls don't work on yakkety-next:

dev:~ uname -a
Linux dev 4.6.0-8-generic #9 SMP Mon Jun 6 14:21:30 MDT 2016 x86_64 x86_64 
x86_64 GNU/Linux
dev:~ cat tester.c 
#include 
#include 
#include 

int main()
{
struct timeval tv;
struct timezone tz;

while (1) {
sleep(1);
if (gettimeofday(, ) < 0) {
perror("gettimeofday");
}
}

return 0;
}
dev:~ make tester
make: 'tester' is up to date.
dev:~ strace tester
strace: Can't stat 'tester': No such file or directory
dev:~ 1 strace ./tester
execve("./tester", ["./tester"], [/* 35 vars */]) = 0
brk(NULL)   = 0x19e4000
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbca234b000
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=44113, ...}) = 0
mmap(NULL, 44113, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fbca234
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1864888, ...}) = 0
mmap(NULL, 3967488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7fbca1d5f000
mprotect(0x7fbca1f1f000, 2093056, PROT_NONE) = 0
mmap(0x7fbca211e000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1bf000) = 0x7fbca211e000
mmap(0x7fbca2124000, 14848, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fbca2124000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbca233f000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbca233e000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbca233d000
arch_prctl(ARCH_SET_FS, 0x7fbca233e700) = 0
mprotect(0x7fbca211e000, 16384, PROT_READ) = 0
mprotect(0x60, 4096, PROT_READ) = 0
mprotect(0x7fbca234d000, 4096, PROT_READ) = 0
munmap(0x7fbca234, 44113)   = 0
nanosleep({1, 0}, 0x7fffc8ec71f0)   = 0
gettimeofday({1465317034, 813437}, {tz_minuteswest=0, tz_dsttime=0}) = 0
nanosleep({1, 0}, 0x7fffc8ec71f0)   = 0
gettimeofday({1465317035, 813718}, {tz_minuteswest=0, tz_dsttime=0}) = 0
nanosleep({1, 0}, 0x7fffc8ec71f0)   = 0
gettimeofday({1465317036, 814008}, {tz_minuteswest=0, tz_dsttime=0}) = 0
nanosleep({1, 0}, ^Cstrace: Process 15793 detached
 

whereas on a normal machine, they do:

~ uname -a
Linux hopstrocity 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
~ cat tester.c 
#include 
#include 
#include 

int main()
{
struct timeval tv;
struct timezone tz;

while (1) {
sleep(1);
if (gettimeofday(, ) < 0) {
perror("gettimeofday");
}
}

return 0;
}

~ make tester
make: 'tester' is up to date.
~ strace ./tester
execve("./tester", ["./tester"], [/* 60 vars */]) = 0
brk(NULL)   = 0x12c7000
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fb544a9b000
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=143083, ...}) = 0
mmap(NULL, 143083, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fb544a78000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1864888, ...}) = 0
mmap(NULL, 3967488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7fb5444af000
mprotect(0x7fb54466f000, 2093056, PROT_NONE) = 0
mmap(0x7fb54486e000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1bf000) = 0x7fb54486e000
mmap(0x7fb544874000, 14848, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fb544874000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fb544a77000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fb544a76000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fb544a75000
arch_prctl(ARCH_SET_FS, 0x7fb544a76700) = 0
mprotect(0x7fb54486e000,

[Kernel-packages] [Bug 1590069] Re: vDSO syscalls don't work on yakkety/master-next (and unstable/master)

2016-06-07 Thread Tycho Andersen 
A nice canary for this is that there's no .dynamic section in vdso.so:

$ readelf --program-headers arch/x86/entry/vdso/vdso64.so

Elf file type is EXEC (Executable file)
Entry point 0x600
There are 4 program headers, starting at offset 64

Program Headers:
  Type   Offset VirtAddr   PhysAddr
 FileSizMemSiz  Flags  Align
  LOAD   0x 0x 0x
 0x0b39 0x0b39  R E1000
  DYNAMIC0x 0x 0x
 0x 0x  R  8
readelf: Error: no .dynamic section in the dynamic segment
  NOTE   0x0460 0x0460 0x0460
 0x003c 0x003c  R  4
  GNU_EH_FRAME   0x049c 0x049c 0x049c
 0x003c 0x003c  R  4

 Section to Segment mapping:
  Segment Sections...
   00 .rodata .note .eh_frame_hdr .eh_frame .text .altinstructions 
.altinstr_replacement 
   01 
   02 .note 
   03 .eh_frame_hdr

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

Title:
  vDSO syscalls don't work on yakkety/master-next (and unstable/master)

Status in linux package in Ubuntu:
  New

Bug description:
  Hi guys,

  I'm having a problem where vDSO syscalls don't work on yakkety-next:

  dev:~ uname -a
  Linux dev 4.6.0-8-generic #9 SMP Mon Jun 6 14:21:30 MDT 2016 x86_64 x86_64 
x86_64 GNU/Linux
  dev:~ cat tester.c 
  #include 
  #include 
  #include 

  int main()
  {
struct timeval tv;
struct timezone tz;

while (1) {
sleep(1);
if (gettimeofday(, ) < 0) {
perror("gettimeofday");
}
}

return 0;
  }
  dev:~ make tester
  make: 'tester' is up to date.
  dev:~ strace tester
  strace: Can't stat 'tester': No such file or directory
  dev:~ 1 strace ./tester
  execve("./tester", ["./tester"], [/* 35 vars */]) = 0
  brk(NULL)   = 0x19e4000
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbca234b000
  access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or 
directory)
  open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=44113, ...}) = 0
  mmap(NULL, 44113, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fbca234
  close(3)= 0
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
  read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"..., 
832) = 832
  fstat(3, {st_mode=S_IFREG|0755, st_size=1864888, ...}) = 0
  mmap(NULL, 3967488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7fbca1d5f000
  mprotect(0x7fbca1f1f000, 2093056, PROT_NONE) = 0
  mmap(0x7fbca211e000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1bf000) = 0x7fbca211e000
  mmap(0x7fbca2124000, 14848, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fbca2124000
  close(3)= 0
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbca233f000
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbca233e000
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fbca233d000
  arch_prctl(ARCH_SET_FS, 0x7fbca233e700) = 0
  mprotect(0x7fbca211e000, 16384, PROT_READ) = 0
  mprotect(0x60, 4096, PROT_READ) = 0
  mprotect(0x7fbca234d000, 4096, PROT_READ) = 0
  munmap(0x7fbca234, 44113)   = 0
  nanosleep({1, 0}, 0x7fffc8ec71f0)   = 0
  gettimeofday({1465317034, 813437}, {tz_minuteswest=0, tz_dsttime=0}) = 0
  nanosleep({1, 0}, 0x7fffc8ec71f0)   = 0
  gettimeofday({1465317035, 813718}, {tz_minuteswest=0, tz_dsttime=0}) = 0
  nanosleep({1, 0}, 0x7fffc8ec71f0)   = 0
  gettimeofday({1465317036, 814008}, {tz_minuteswest=0, tz_dsttime=0}) = 0
  nanosleep({1, 0}, ^Cstrace: Process 15793 detached
   

  whereas on a normal machine, they do:

  ~ uname -a
  Linux hopstrocity 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux
  ~ cat tester.c 
  #include 
  #include 
  #include 

  int main()
  {
struct timeval tv;
struct timezone tz;

while (1) {
sleep(1);
if (gettimeofday(, ) < 0) {
perror("gettimeofday");
}
}

return 0;
  }

  ~ make tester
  make: 'tester' is up to date.
  ~ strace ./tester

[Kernel-packages] [Bug 1233466] Re: Hot-Add Memory failing for lack of udev rule

2016-06-07 Thread Ubuntu Foundations Team Bug Bot 
** Tags added: patch

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

Title:
  Hot-Add Memory failing for lack of udev rule

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

Bug description:
  It appears that the Hot-Add mechanism is not working because of lack
  of a udev rule. The required rule is attached to this bug. Please
  include it.

  Furthermore, please ensure that the following patches are included:

  https://git.kernel.org/cgit/linux/kernel/git/next/linux-
  next.git/commit/drivers/hv?id=20138d6cb838aa01bb1b382dcb5f3d3a119ff2cb

  https://git.kernel.org/cgit/linux/kernel/git/next/linux-
  next.git/commit/drivers/hv?id=c5e2254f8d63a6654149aa32ac5f2b7dd66a976d

  https://git.kernel.org/cgit/linux/kernel/git/next/linux-
  next.git/commit/drivers/hv?id=ed07ec93e83ec471d365ce084e43ad90fd205903

  The above patches should be in but just wanted to ensure that you guys
  got these.

  Thanks again for the great last minute help.
  Abhishek

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

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

[Kernel-packages] [Bug 1571798] Re: Broadwell ECRC Support missing in Ubuntu

2016-06-07 Thread John Mazzie 
This version is working correctly.

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

Title:
  Broadwell ECRC Support missing in Ubuntu

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1233466] Re: Hot-Add Memory failing for lack of udev rule

2016-06-07 Thread Benjamin Drung 
Can we also enable the hotplug udev rules for QEMU guests? See the
attached git format-patch.

** Patch added: "0001-Enable-CPU-and-RAM-hotplug-on-QEMU.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1233466/+attachment/4679035/+files/0001-Enable-CPU-and-RAM-hotplug-on-QEMU.patch

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

Title:
  Hot-Add Memory failing for lack of udev rule

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

Bug description:
  It appears that the Hot-Add mechanism is not working because of lack
  of a udev rule. The required rule is attached to this bug. Please
  include it.

  Furthermore, please ensure that the following patches are included:

  https://git.kernel.org/cgit/linux/kernel/git/next/linux-
  next.git/commit/drivers/hv?id=20138d6cb838aa01bb1b382dcb5f3d3a119ff2cb

  https://git.kernel.org/cgit/linux/kernel/git/next/linux-
  next.git/commit/drivers/hv?id=c5e2254f8d63a6654149aa32ac5f2b7dd66a976d

  https://git.kernel.org/cgit/linux/kernel/git/next/linux-
  next.git/commit/drivers/hv?id=ed07ec93e83ec471d365ce084e43ad90fd205903

  The above patches should be in but just wanted to ensure that you guys
  got these.

  Thanks again for the great last minute help.
  Abhishek

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

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

[Kernel-packages] [Bug 1589997] Re: The device on /dev/sdx is not created when inserting new devices

2016-06-07 Thread Joan 
Unfortunately apport-collect does not work in my system (I guess that
apport-kde is not in a very good shape, can I provide the logs in
another way?

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

Title:
  The device on /dev/sdx is not created when inserting new devices

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am on kubuntu xenial (upgraded from 15.10), from a couple of weeks I 
noticed that the pendrives i insert to my computer are detected but the devices 
under /dev are no longer created.
  I if reboot the pc with the pendrive already plugged in it works without 
issues. I'm suspecting from udev because of this text in syslog (full output in 
the summary)

  Jun  7 15:02:55 pc systemd-udevd[24747]: inotify_add_watch(9,
  /dev/sdb, 10) failed: No such file or directory

  I'm up to date on all the packages
  - linux-image-4.4.0-22-generic
  - udev - 229-4ubuntu6

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

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

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

2016-06-07 Thread bugproxy 
--- Comment From thorsten.di...@de.ibm.com 2016-06-07 11:45 EDT---
Hi Dimitri,

any customer using a zEC12, z13 with zfcp Adaptor connected via FC Switch to 
DS8000 any model having uCode Level 7.5 or newer might be affected. V7000 
Storage is not affected, AFAICS today.
So, this is quite a big audience.
Considering that the kernel of 14.04/14.04.1 is supported until April 2021, I 
think that during this support timeframe customers will definitely hit this 
bug. We saw it on various setups here.
Since that problem prevents customers from installing Ubuntu at all 
(unblacklisting scsi_dh_alua and rebuilding the initrd is IMO not a "supported 
workaround"), our project management might raise severity soon.
So, IMO best idea is to get in touch with the maintainer of scsi_dh_alua to 
retrieve some ideas, which of all the patches might be the ones that fix the 
problem in 4.4. - if you do not want to apply them all.
Well, finally it's up to you/Canonical.

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

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer

[Kernel-packages] [Bug 1576764] Re: Kernel bug caused by XRandR / Video Drivers

2016-06-07 Thread frew 
DMIDecode output:

GLET83WW (2.37 )
03/31/2016

It is not improved.

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

Title:
  Kernel bug caused by XRandR / Video Drivers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Here are two stack traces showing the issue:

  
  Apr 29 08:33:05 zfp kernel: [34730.860474] general protection fault:  
[#1] SMP 
  Apr 29 08:33:05 zfp kernel: [34730.860507] Modules linked in: ctr ccm xt_nat 
xt_tcpudp ipt_REJECT nf_reject_ipv4 pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) rfcomm veth ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
xt_conntrack nf_nat nf_conntrack br_netfilter bridge stp llc overlay 
xt_multiport iptable_filter ip_tables x_tables bnep arc4 snd_usb_audio 
snd_usbmidi_lib uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core v4l2_common videodev media btusb btrtl btbcm btintel intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel bluetooth kvm 
irqbypass input_leds joydev serio_raw iwlmvm mac80211 snd_seq_midi 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_seq_midi_event iwlwifi 
snd_hda_codec_generic thinkpad_acpi snd_rawmidi nvram cfg80211 rtsx_pci_ms 
snd_hda_intel memstick lpc_ich snd_hda_codec mei_me mei snd_hda_core snd_hwdep 
snd_pcm ie31200_edac snd_seq edac_core snd_seq_
 device snd_timer snd soundcore shpchp mac_hid sch_fq_codel nfsd auth_rpcgss 
nfs_acl lockd grace sunrpc parport_pc ppdev lp parport autofs4 drbg ansi_cprng 
algif_skcipher af_alg dm_crypt hid_thingm hid_generic hid_logitech_hidpp 
hid_logitech_dj usbhid hid rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul 
aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd nouveau i915 
psmouse ahci libahci mxm_wmi ttm rtsx_pci i2c_algo_bit drm_kms_helper e1000e 
syscopyarea sysfillrect sysimgblt fb_sys_fops drm ptp pps_core wmi fjes video
  Apr 29 08:33:05 zfp kernel: [34730.861171] CPU: 1 PID: 1523 Comm: Xorg 
Tainted: G   OE   4.4.0-21-generic #37-Ubuntu
  Apr 29 08:33:05 zfp kernel: [34730.861203] Hardware name: LENOVO 
20AN006LUS/20AN006LUS, BIOS GLET77WW (2.31 ) 01/27/2015
  Apr 29 08:33:05 zfp kernel: [34730.861233] task: 8800a92b1b80 ti: 
880428664000 task.ti: 880428664000
  Apr 29 08:33:05 zfp kernel: [34730.861261] RIP: 0010:[]  
[] drm_dp_payload_send_msg+0x15b/0x210 [drm_kms_helper]
  Apr 29 08:33:05 zfp kernel: [34730.861308] RSP: 0018:880428667ad8  
EFLAGS: 00010282
  Apr 29 08:33:05 zfp kernel: [34730.861328] RAX: 8800a92b1b80 RBX: 
0a26771717294f2d RCX: 880425e1d908
  Apr 29 08:33:05 zfp kernel: [34730.861354] RDX: 8000 RSI: 
0a26771717294f2d RDI: 880425e1d908
  Apr 29 08:33:05 zfp kernel: [34730.861380] RBP: 880428667b28 R08: 
0001a040 R09: c012216b
  Apr 29 08:33:05 zfp kernel: [34730.861406] R10: ea000211bc00 R11: 
 R12: 88042bf57810
  Apr 29 08:33:05 zfp kernel: [34730.861432] R13: 880425e1d650 R14: 
880425e1d650 R15: 8804249e1800
  Apr 29 08:33:05 zfp kernel: [34730.861458] FS:  7feb611c4a00() 
GS:88043e24() knlGS:
  Apr 29 08:33:05 zfp kernel: [34730.861488] CS:  0010 DS:  ES:  CR0: 
80050033
  Apr 29 08:33:05 zfp kernel: [34730.861509] CR2: 55f2ae2e4b30 CR3: 
0004279e9000 CR4: 001406e0
  Apr 29 08:33:05 zfp kernel: [34730.861534] Stack:
  Apr 29 08:33:05 zfp kernel: [34730.861543]  587ca201012a25ee 880425e1d908 
880428667b00 0001
  Apr 29 08:33:05 zfp kernel: [34730.861574]  3e400d66 0001 
88042bf57810 880425e1d650
  Apr 29 08:33:05 zfp kernel: [34730.861605]  0001 880425e1d9a0 
880428667b68 c01227f2
  Apr 29 08:33:05 zfp kernel: [34730.861636] Call Trace:
  Apr 29 08:33:05 zfp kernel: [34730.861651]  [] 
drm_dp_update_payload_part2+0xc2/0x130 [drm_kms_helper]
  Apr 29 08:33:05 zfp kernel: [34730.861700]  [] 
intel_mst_enable_dp+0xe7/0x110 [i915]
  Apr 29 08:33:05 zfp kernel: [34730.861739]  [] 
haswell_crtc_enable+0x421/0x870 [i915]
  Apr 29 08:33:05 zfp kernel: [34730.861779]  [] ? 
intel_frontbuffer_flush+0x42/0x80 [i915]
  Apr 29 08:33:05 zfp kernel: [34730.861819]  [] 
intel_atomic_commit+0x454/0x6f0 [i915]
  Apr 29 08:33:05 zfp kernel: [34730.861857]  [] 
drm_atomic_commit+0x37/0x60 [drm]
  Apr 29 08:33:05 zfp kernel: [34730.861884]  [] 
drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper]
  Apr 29 08:33:05 zfp kernel: [34730.861922]  [] 
drm_mode_set_config_internal+0x62/0x100 [drm]
  Apr 29 08:33:05 zfp kernel: [34730.861958]  [] 
drm_mode_setcrtc+0x3d2/0x4f0 [drm]
  Apr 29 08:33:05 zfp kernel: [34730.861988]  [] 
drm_ioctl+0x152/0x540 [drm]
  Apr 29 08:33:05 zfp kernel: [34730.862017]  []

[Kernel-packages] [Bug 1587265] Re: ubuntu not work with tickless kernel boot option

2016-06-07 Thread Joseph Salisbury 
Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of a
regression, and when this regression was introduced.   If this is a
regression, we can perform a kernel bisect to identify the commit that
introduced the problem.


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

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

** Tags added: kernel-da-key

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

Title:
  ubuntu not work with tickless kernel boot option

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For redhat, we have such guide like 
  
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/pdf/Performance_Tuning_Guide/Red_Hat_Enterprise_Linux-7-Performance_Tuning_Guide-en-US.pdf

  and for tickless kernel, (use dynamic tickless ways)

  1. config grub with following cmdline

  $ cat /etc/default/grub 
  # If you change this file, run 'update-grub' afterwards to update
  # /boot/grub/grub.cfg.
  # For full documentation of the options in this file, see:
  #   info -f grub -n 'Simple configuration'

  GRUB_DEFAULT=0
  GRUB_HIDDEN_TIMEOUT=0
  GRUB_HIDDEN_TIMEOUT_QUIET=true
  GRUB_TIMEOUT=10
  GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash isolcpus=1-2 nohz_full=1-2"
  GRUB_CMDLINE_LINUX=""


  I used nohz_full here, and it is CPU 1, 2 here.

  2. update-grub after that.
  3. Then reboot system

  4. execute following 
  $ sudo perf stat  -C  1  -e irq_vectors:local_timer_entry taskset -c 1 stress 
-t 1 -c 1
  stress: info: [3869] dispatching hogs: 1 cpu, 0 io, 0 vm, 0 hdd
  stress: info: [3869] successful run completed in 1s

   Performance counter stats for 'CPU(s) 1':

 252  irq_vectors:local_timer_entry

 1.001491203 seconds time elapsed

  
  It always 252, (the default 250 HZ), seems tickless kernel option not have 
any effect, whether config it or not, both have same results.

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

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

[Kernel-packages] [Bug 1589704] Re: workaround cavium thunderx silicon erratum 23144

2016-06-07 Thread dann frazier 
** Summary changed:

- workaround cavium thunderx silicon erratum
+ workaround cavium thunderx silicon erratum 23144

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

Title:
  workaround cavium thunderx silicon erratum 23144

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

Bug description:
  [Impact]
  This impacts 2 socket Cavium ThunderX systems using pass-1.1 silicon, and can 
result in IO hangs.

  [Test Case]
  $ dmesg | grep "ITS command queue timeout"

  [Regression Risk]
  The workaround is in gicv3 specific code, and only activated when the hw 
revision in the IIDR matches ThunderX pass 1.x silicon, so risk to other 
platforms is minimal.

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

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

[Kernel-packages] [Bug 1589910] Re: [regression trusty] oops/sig 4: power7_enter_nap_mode+0x0/0x18

2016-06-07 Thread Kamal Mostafa 
** Changed in: linux (Ubuntu Trusty)
   Status: In Progress => Fix Committed

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

Title:
  [regression trusty] oops/sig 4: power7_enter_nap_mode+0x0/0x18

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  Arch: ppc64el
  Release: Trusty/14.04

  [ 0.194023] Oops: Exception in kernel mode, sig: 4 [#3]
  [ 0.194128] SMP NR_CPUS=2048 NUMA PowerNV
  [ 0.194225] Modules linked in:
  [ 0.194316] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G D 3.13.0-48-generic 
#80-Ubuntu
  [ 0.194403] task: c007f26957c0 ti: c007f2728000 task.ti: 
c007f2728000
  [ 0.194477] NIP: c1598930 LR: c001897c CTR: c002abfc
  [ 0.194551] REGS: c007f272b800 TRAP: 0e40 Tainted: G D (3.13.0-48-generic)
  [ 0.194651] MSR: 90081001  CR: 22004088 XER: 
  [ 0.194788] CFAR: c002ace4 SOFTE: 0
  ...
  [ 0.195869] NIP [c1598930] power7_enter_nap_mode+0x0/0x18

  SRU Justification:

  = Impact =
  Since kernel 3.13.0-46 there was a incorrect backport of a stable patch which 
causes several oops messages and ends with an automatic reboot. Which renders 
all kernels since then to be unbootable on ppc64el. This happens because 
instead of the function address to power7_enter_nap_mode, the change 
accidentally loads the address of a related symbol table.

  = Fix =
  Pick up the alternate declaration of the function label as it is in the 
original upstream change (commmit 8117ac6 powerpc/powernv: Switch off MMU 
before entering nap/sleep/rvwinkle mode). In 3.13 this requires one more change 
because there is one call site that refers to a label name which would be 
implicitly generated by the macro that gets replaced. This was done upstream, 
too, in (b1576fe powerpc: No need to use dot symbols when branching to a 
function).

  = Testcase =
  Trying to boot current Trusty kernels on a Power8 host fails all the time. 
With the change applied the host comes up without errors.

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

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

[Kernel-packages] [Bug 1311289] Re: 168c:0032 [TravelMate B113-E] Has issues with bluetooth

2016-06-07 Thread Wildman 
I have upgradet kernel to 4.5.3 but this do not helps me...

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

Title:
  168c:0032 [TravelMate B113-E] Has issues with bluetooth

Status in linux package in Ubuntu:
  Expired

Bug description:
  I have Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032]
  (rev 01) on Acer TM B113-E notebook.

  When I use ath9k with 3.11 kernel then all works fine. WiFi and Bluetooth 
works as well.
  I have problem with bluetooth when install some later kernels(I'm test 
3.15rc1 and (3.13 or 3.14)) from http://kernel.ubuntu.com/~kernel-ppa/mainline/
  After this installation I have not bluetooth device! When I switch Wi-Fi by 
acpi key, I can switch only Wi-Fi to on or off state(I saw status by "rfkill 
list"). Bluetooth device will not reconize for me...
  But if I will power off  notebook and disconnect battery, then after power on 
I'm get working Bluetooth.

  I could not pay attention to this troubles but now we have Ubuntu 14.04(I 
tested on Kubuntu 14.04).
  After installed Kubuntu 14.04 I have working only Wi-Fi. Power off+disconnect 
battery and other probes(such as I probe to install non-free firmware) do not 
have results. System do not recognize BT device... I can not see this device in 
rfkill list and in KDE's System Settings->Bluetooth...
  In 3.11 kernel and later kernel I have problem with bluetooth after sleeping 
too. Module do not start after resume. I wrote script with manual starting of 
btusb module and get working BT after resume.

  WORKAROUND: In modprobe.conf blacklist acer_wmi and add:
  options ath9k btcoex_enable=1

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-19.13-lowlatency 3.11.10.5
  Uname: Linux 3.11.0-19-lowlatency x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asm3180 F pulseaudio
  Date: Tue Apr 22 22:07:32 2014
  HibernationDevice: RESUME=UUID=e179b479-7a1f-4d86-919c-809b7e5d9e8e
  InstallationDate: Installed on 2013-10-19 (184 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Acer TravelMate B113
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-19-lowlatency 
root=UUID=94f29b75-e824-41b5-aa40-c5734a2d4804 ro pciehp.pciehp_force=1 
pciehp.pciehp_poll=1 quiet splash pcie_aspm=force i915.i915_enable_fbc=1 
drm.vblankoffdelay=1 i915.semaphores=1 i915.lvds_downclock=1 nmi_watchdog=0 
acpi_backlight=vendor elevator=noop
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-19-lowlatency N/A
   linux-backports-modules-3.11.0-19-lowlatency  N/A
   linux-firmware1.116.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: BA10_HX
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09
  dmi.modalias: 
dmi:bvnAcer:bvrV1.09:bd10/30/2012:svnAcer:pnTravelMateB113:pvrV1.09:rvnAcer:rnBA10_HX:rvrType2-BoardVersion:cvnAcer:ct10:cvrV1.09:
  dmi.product.name: TravelMate B113
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1311289] Re: 168c:0032 [TravelMate B113-E] Has issues with bluetooth

2016-06-07 Thread Wildman 
sudo cat /sys/kernel/debug/usb/devices

T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 2
B:  Alloc=  0/800 us ( 0%), #Int=  1, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 4.05
S:  Manufacturer=Linux 4.5.3-040503-lowlatency ehci_hcd
S:  Product=EHCI Host Controller
S:  SerialNumber=:00:1d.0
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480  MxCh= 4
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=8087 ProdID=0024 Rev= 0.00
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=256ms

T:  Bus=02 Lev=02 Prnt=02 Port=02 Cnt=01 Dev#=  3 Spd=480  MxCh= 0
D:  Ver= 2.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=8564 ProdID=1000 Rev=11.00
S:  Manufacturer=JetFlash
S:  Product=Mass Storage Device
S:  SerialNumber=35ELAUAKUC18B58S
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=300mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E:  Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 2
B:  Alloc=  4/800 us ( 1%), #Int=  2, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 4.05   

  
S:  Manufacturer=Linux 4.5.3-040503-lowlatency ehci_hcd 

  
S:  Product=EHCI Host Controller

  
S:  SerialNumber=:00:1a.0   

  
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA  

  
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub   

  
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms   

  


  
T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480  MxCh= 4  

  
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1

  
P:  Vendor=8087 ProdID=0024 Rev= 0.00   

  
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA  

  
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub   

  
E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=256ms   

  


  
T:  Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#=  5 Spd=12   MxCh= 0  

  
D:  Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1

  
P:  Vendor=13d3 ProdID=3362 Rev= 0.02
S:  Manufacturer=Atheros Communications
S:  Product=Bluetooth USB Host Controller
S:  SerialNumber=Alaska Day 2006
C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=1ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk)

[Kernel-packages] [Bug 1587078] Re: OOM in guest Ubuntu with inflated balloon

2016-06-07 Thread Joseph Salisbury 
You say this bug affects Ubuntu 14.10.  Does it not affect prior
releases such as 14.04(Xenial)?

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

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

** Tags added: kernel-da-key yakkety

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

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

Title:
  OOM in guest Ubuntu with inflated balloon

Status in linux package in Ubuntu:
  Triaged

Bug description:
  There is QEMU/KVM and a Linux OS running inside the guest.
  Inside the Linux guest a balloon consumes memory in accordance with
  commands performed on the host side in QEMU. Rapid increases of memory 
consumption
  inside the guest may end up with guest OOMs
  since memory locked by balloon couldn’t be returned to the guest OS/vm in 
time.

  The problem is addressed in mainstream Linux with the following
  patchset:

  commit 5a10b7dbf904bfe01bb9fcc6298f7df09eed77d5
  Author: Raushaniya Maksudova 
  Date:   Mon Nov 10 09:36:29 2014 +1030
  virtio_balloon: free some memory from balloon on OOM

  Excessive virtio_balloon inflation can cause invocation of OOM-killer,
  when Linux is under severe memory pressure. Various mechanisms are
  responsible for correct virtio_balloon memory management. Nevertheless
  it is often the case that these control tools does not have enough time
  to react on fast changing memory load. As a result OS runs out of memory
  and invokes OOM-killer. The balancing of memory by use of the virtio
  balloon should not cause the termination of processes while there are
  pages in the balloon. Now there is no way for virtio balloon driver to
  free some memory at the last moment before some process will be get
  killed by OOM-killer.

  This does not provide a security breach as balloon itself is running
  inside guest OS and is working in the cooperation with the host. Thus
  some improvements from guest side should be considered as normal.

  To solve the problem, introduce a virtio_balloon callback which is
  expected to be called from the oom notifier call chain in out_of_memory()
  function. If virtio balloon could release some memory, it will make
  the system to return and retry the allocation that forced the out of
  memory killer to run.

  Allocate virtio  feature bit for this: it is not set by default,
  the the guest will not deflate virtio balloon on OOM without explicit
  permission from host.

  Signed-off-by: Raushaniya Maksudova 
  Signed-off-by: Denis V. Lunev 
  Acked-by: Michael S. Tsirkin 
  Signed-off-by: Rusty Russell 

  commit 1fd9c67203af91977bf3b964ff3744cf74fc6f3f
  Author: Raushaniya Maksudova 
  Date:   Mon Nov 10 09:35:29 2014 +1030

  virtio_balloon: return the amount of freed memory from
  leak_balloon()

  This value would be useful in the next patch to provide the amount of
  the freed memory for OOM killer.

  Signed-off-by: Raushaniya Maksudova 
  Signed-off-by: Denis V. Lunev 
  CC: Rusty Russell 
  CC: Michael S. Tsirkin 
  Signed-off-by: Rusty Russell 

  The problem is present in Ubuntu 14.10

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

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

[Kernel-packages] [Bug 1587475] Re: Kernel panic on btrfs mount and ls

2016-06-07 Thread Joseph Salisbury 
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7-rc1 kernel[0].

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

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

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


Thanks in advance.

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

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

** Tags removed: trusty
** Tags added: kernel-da-key xenial

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

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

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

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

Title:
  Kernel panic on btrfs mount and ls

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

Bug description:
  Kernel panic happens after mount and ls specific btrfs image

  Way to reproduce:
  1. download and unpack btrfs image from tar(sparse file)(tar -Sxf img.tar)
  2. mount btrfs (sudo mount -t btrfs -o rw,noatime,compress=no,commit=5 
71bb49cf-26f1-484a-832c-e966f43adca9.img broken)
  3. list files in mount point (ls -al broken)

  the system down to kernel panic with log above

  (looks like 3.19.x and 4.2.x not affected, only 4.4.x)

  dmesg log:
  May 31 13:02:21 fs-new kernel: [  694.744630] BTRFS error (device loop0): 
parent transid verify failed on 30425088 wanted 120 found 119
  May 31 13:02:21 fs-new kernel: [  694.747077] BTRFS error (device loop0): 
parent transid verify failed on 30425088 wanted 120 found 119
  May 31 13:02:21 fs-new kernel: [  694.747128] [ cut here 
]
  May 31 13:02:21 fs-new kernel: [  694.747135] WARNING: CPU: 0 PID: 13795 at 
/build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/lib/idr.c:1051 
ida_remove+0xfa/0x130()
  May 31 13:02:21 fs-new kernel: [  694.747136] ida_remove called for id=47 
which is not allocated.
  May 31 13:02:21 fs-new kernel: [  694.747137] Modules linked in: ufs qnx4 
hfsplus hfs minix ntfs msdos jfs xfs libcrc32c nfsv3 vboxsf xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack zram 
lz4_compress xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables autofs4 
ppdev vboxvideo ttm crct10dif_pclmul crc32_pclmul drm_kms_helper drm 
aesni_intel aes_x86_64 lrw input_leds gf128mul nfsd glue_helper ablk_helper 
cryptd auth_rpcgss serio_raw nfs_acl nfs fb_sys_fops syscopyarea lockd 
sysfillrect grace 8250_fintek parport_pc sysimgblt vboxguest i2c_piix4 sunrpc 
video mac_hid fscache lp parport zfs(POE) zunicode(POE) zcommon(POE) 
znvpair(POE) spl(OE) zavl(POE) btrfs xor raid6_pq psmouse e1000 fjes pata_acpi
  May 31 13:02:21 fs-new kernel: [  694.747182] CPU: 0 PID: 13795 Comm: ls 
Tainted: P   OE   4.4.0-22-generic #40~14.04.1-Ubuntu
  May 31 13:02:21 fs-new kernel: [  694.747183] Hardware name: innotek GmbH 
VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
  May 31 13:02:21 fs-new kernel: [  694.747185]   
8800024e7a88 813cde6c 8800024e7ad0
  May 31 13:02:21 fs-new kernel: [  694.747187]  81af5298 
8800024e7ac0 8107d856 
  May 31 13:02:21 fs-new kernel: [  694.747189]  81fce200 
88003c827a00 88003616e068 0001
  May 31 13:02:21 fs-new kernel: [  694.747191] Call Trace:
  May 31 13:02:21 fs-new kernel: [  694.747195]  [] 
dump_stack+0x63/0x87
  May 31 13:02:21 fs-new kernel: [  694.747199]  [] 
warn_slowpath_common+0x86/0xc0
  May 31 13:02:21 fs-new kernel: [  694.747201]  [] 
warn_slowpath_fmt+0x4c/0x50
  May 31 13:02:21 fs-new kernel: [  694.747214]  [] ? 
free_percpu+0xba/0x180
  May 31 13:02:21 fs-new kernel: [  694.747217]  [] 
ida_remove+0xfa/0x130
  May 31 13:02:21 fs-new kernel: [  694.747220]  [] 
free_anon_bdev+0x2c/0x50
  May 31 13:02:21 fs-new kernel: [  694.747239]  [] 
free_fs_root+0xbe/0xe0 [btrfs]
  May 31 13:02:21 fs-new kernel: [  694.747251]  [] 
btrfs_get_fs_root+0x216/0x250 [btrfs]
  May 31 13:02:21 fs-new kernel: [  694.747264]  [] ? 
memcmp_extent_buffer+0xbd/0x120 [btrfs]
  May 31 13:02:21 fs-new kernel: [  694.747277]  [] 
btrfs_lookup_dentry+0x28c/0x4c0 [btrfs]
  May 31 13:02:21 fs-new kernel: [  694.747288]  [] 
btrfs_lookup+0x12/0x40 [btrfs]
  May 31 13:02:21 fs-new kernel: [  694.747291]  [] 
lookup_real+0x1d/0x50
  May 31 13:02:21 fs-new kernel: [  694.747293]  [] 
__lookup_hash+0x33/0x40
  May 31 13:02:21 fs-new kernel: [  694.747295]  []

[Kernel-packages] [Bug 1587510] Re: Thinkpad keyboard backlight is not properly restored on resume from suspend

2016-06-07 Thread Joseph Salisbury 
** Changed in: linux (Ubuntu)
   Status: In Progress => Triaged

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

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

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

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

Title:
  Thinkpad keyboard backlight is not properly restored on resume from
  suspend

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

Bug description:
  This is fixed in: https://github.com/torvalds/linux/commit/afcedeb

  Please backport this to Yakkety and to Xenial (once lp:1574498 fix is 
released)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marco  2143 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=e95ce812-4be1-4186-9f30-e10d6d6430f5
  InstallationDate: Installed on 2016-05-02 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160415)
  MachineType: LENOVO 20F9CTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=328bf97f-143a-483c-8ca9-282e1bfbdf79 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 04/14/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET43W (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20F9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET43W(1.11):bd04/14/2016:svnLENOVO:pn20F9CTO1WW:pvrThinkPadT460s:rvnLENOVO:rn20F9CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20F9CTO1WW
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1583288] Re: Realtek Wifi card rtl8723be [10ec:b723] WiFi not available

2016-06-07 Thread Podsgrove 
Thanks for your reply but one look at the complications of reporting a
bug put me off. I am not a fan of Unity and had planned to install
Lubuntu but the best I have able to achieve is to install the LXDE
desktop on an out-of-date OS. This comes with the added bonus of a
battery indicator that does not work and an annoying login bongo noise
that keeps coming back despite all efforts to disable it.  It is
annoying that HP have chosen to market a Linux laptop that does not
work with the majority of Linux distros. The only ones I have found
that work (apart from HP's modified Ubuntu) are Console Linux and
Puppy, neither of which I particularly like.
I guess I am just a grumpy old git but next time I buy a computer I
will cough up the Microsoft tax and get one that works with Linux!

Podsgrove
 Sent using Hushmail
On 07/06/2016 at 11:41 AM, "Christopher M. Penalver"  wrote:Podsgrove,
it will help immensely if you filed a new report with Ubuntu (not
Mint) via the default 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 subscribed to the
bug
report.
https://bugs.launchpad.net/bugs/1583288

Title:
  Realtek Wifi card rtl8723be [10ec:b723] WiFi not available

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I am here on a HP Pavilion Laptop with beatsaudio. No Model Number -
  nothing.But I have this problem on other HP (455) Notebooks too.

  OS tried: OpenSuse / Kubuntu / Linux Mint Mate (card does not work
out
  of the box / no scanning)

  The Wifi card is: (in Germany!)

  --

   lspci -nn | grep -iA2 net
  02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd.
RTL8723BE PCIe Wireless Network Adapter [10ec:b723]

  --

  I am now under kernel:
  4.4.0-21-generic

  I installed the newest kernel because in some threads people said
the card woule be available in the newest kernel. But this was not the
case. I mean the card is there but does not scan nor see any wifi
networks.
  -

  Before I tried everything I could find to get my wifi running but I
do
  not even see one spot. So no connection at all. I even cloned git
and
  compiled the driver - the compiling and installation worked fine. I
  tried the old and the new driver.

  By the way the BT seems to be fine - although I have not checked
cause
  I do not need BT.

  -
  Here is what I tried:

  rfkill list all; hciconfig -a
  0: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no
  1: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no
  hci0: Type: BR/EDR Bus: USB
   BD Address: 2C:33:7A:3F:E4:3E ACL MTU: 820:8 SCO MTU: 255:16
   UP RUNNING PSCAN
   RX bytes:1327 acl:0 sco:0 events:139 errors:0
   TX bytes:25058 acl:0 sco:0 commands:139 errors:0
   Features: 0xff 0xff 0xff 0xfe 0xdb 0xff 0x7b 0x87
   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
   Link policy: RSWITCH HOLD SNIFF PARK
   Link mode: SLAVE ACCEPT
   Name: 'mint-0'
   Class: 0x740100
   Service Classes: Rendering, Object Transfer, Audio, Telephony
   Device Class: Computer, Uncategorized
   HCI Version: 4.0 (0x6) Revision: 0xe2f
   LMP Version: 4.0 (0x6) Subversion: 0x9f73
   Manufacturer: Realtek Semiconductor Corporation (93)

  -

  I added the options sugested in rtl8723be.conf

  options rtl8723be fwlps=0 swlps=0

  But this did not help either.

  --

  lsmod reports:

  rfcomm 69632 12
  rtl8723be 139264 0
  btcoexist 180224 1 rtl8723be
  rtl_pci 40960 1 rtl8723be
  rtlwifi 98304 3 btcoexist,rtl_pci,rtl8723be
  hp_wmi 16384 0
  mac80211 733184 3 rtl_pci,rtlwifi,rtl8723be
  sparse_keymap 16384 1 hp_wmi
  kvm 532480 0
  irqbypass 16384 1 kvm
  btusb 45056 0
  crct10dif_pclmul 16384 0
  btrtl 16384 1 btusb
  btbcm 16384 1 btusb
  ...

  ---

  dmesg | grep rtl reports:

  [ 8.982260] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000b
lmp_ver=06 lmp_subver=8723
  [ 8.982262] Bluetooth: hci0: rtl: loading rtl_bt/rtl8723b_fw.bin
  [ 9.064265] rtlwifi: module verification failed: signature and/or
required key missing - tainting kernel
  [ 9.403770] Using firmware rtlwifi/rtl8723befw.bin
  [ 9.404023] rtlwifi: channel plan 0x20
  [ 9.404027] rtlwifi: country code 11
  [ 9.422483] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
  [ 9.423458] rtlwifi: wireless switch is on

  

  modinfo rtl8723be

  filename:
/lib/modules/4.4.0-21-generic/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8723be/rtl8723be.ko
  firmware: rtlwifi/rtl8723befw.bin
  description: Realtek 8723BE 802.11n PCI wireless
  license: GPL

[Kernel-packages] [Bug 1587510] Re: Thinkpad keyboard backlight is not properly restored on resume from suspend

2016-06-07 Thread Joseph Salisbury 
** Changed in: linux (Ubuntu)
   Status: Triaged => In Progress

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

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

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

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

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

Title:
  Thinkpad keyboard backlight is not properly restored on resume from
  suspend

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

Bug description:
  This is fixed in: https://github.com/torvalds/linux/commit/afcedeb

  Please backport this to Yakkety and to Xenial (once lp:1574498 fix is 
released)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marco  2143 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=e95ce812-4be1-4186-9f30-e10d6d6430f5
  InstallationDate: Installed on 2016-05-02 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160415)
  MachineType: LENOVO 20F9CTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=328bf97f-143a-483c-8ca9-282e1bfbdf79 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 04/14/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET43W (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20F9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET43W(1.11):bd04/14/2016:svnLENOVO:pn20F9CTO1WW:pvrThinkPadT460s:rvnLENOVO:rn20F9CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20F9CTO1WW
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1587885] Re: NULL pointer dereference in radeon drm code

2016-06-07 Thread Joseph Salisbury 
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7-rc1 kernel[0].

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

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

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


Thanks in advance.

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

** Tags added: kernel-da-key

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

Title:
  NULL pointer dereference in radeon drm code

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On one of my systems I use, display connector 0 does not have DDC.
  This results in the DRM code trying to use radeon_connector->ddc_bus
  when it is not set. This is known to have been an issue since the 3.2
  series kernels.

  Known Problem Kernels: uBuntu 12.04 LTS (linux-3.2.55), uBuntu-MATE 14.04 LTS 
(linux-3.16.7) and uBuntu-MATE 16.04 LTS (linux-4.4.8) and linux-4.6.0 (git:/
  /git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux).

  Trying to use the uBuntu-MATE 16.04 LTS LiveCD ubuntu-mate-16.04
  -desktop-amd64.iso (from uBuntu-MATE website) showed the problem.

  Using a serial console I extracted the following information when
  trying to boot from a uBuntu-MATE 16.04 LTS LiveCD USB Stick (it had
  been upgraded from 4.4.0-21-generic in an attempt to get something
  usable):

  
  [0.00] Linux version 4.4.0-22-generic (buildd@lgw01-41) (gcc version 
5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) #40-Ubuntu SMP Thu May 12 22:03:46 
UTC 2
  016 (Ubuntu 4.4.0-22.40-generic 4.4.8)
  [0.00] Command line: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/ubuntu-mate.seed boot=casper locale=en_GB 
console-setup/layoutcode=gb console=u
  art,io,0x3f8,115200n8 earlyprintk=ttyS0,115200n8 debug ---
  [0.00] KERNEL supported cpus:
  [0.00]   Intel GenuineIntel
  [0.00]   AMD AuthenticAMD
  [0.00]   Centaur CentaurHauls
  
  [0.00] efi: EFI v2.00 by Phoenix Technologies Ltd.
  [0.00] efi: EFI v2.00 by Phoenix Technologies Ltd.
  [0.00] efi: [0.00] efi:  ACPI=0x973c7000  ACPI=0x973c7000  
ACPI 2.0=0x973c7014  ACPI 2.0=0x973c7014  SMBIOS=0x9726b000  SMBIOS=0x9726b000 

  [0.00] SMBIOS 2.6 present.
  [0.00] SMBIOS 2.6 present.
  [0.00] DMI: AMD Corporation EBrazos Platform/Persimmon, BIOS LV-683 
Version: 1.1 02/14/2012
  [0.00] DMI: AMD Corporation EBrazos Platform/Persimmon, BIOS LV-683 
Version: 1.1 02/14/2012
  
  [8.262990] [drm] ib test on ring 5 succeeded
  [8.288897] [drm] Radeon Display Connectors
  [8.293175] [drm] Connector 0:
  [8.296252] [drm]   DP-1
  [8.298791] [drm]   Encoders:
  [8.301770] [drm] DFP1: INTERNAL_UNIPHY
  [8.305973] [drm] Connector 1:
  [8.309043] [drm]   DP-2
  [8.311598] [drm]   HPD2
  [8.314169] [drm]   DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c 
0x644c
  [8.321609] [drm]   Encoders:
  [8.324589] [drm] DFP2: INTERNAL_UNIPHY
  [8.328793] [drm] Connector 2:
  [8.331856] [drm]   VGA-1
  [8.332316] scsi 0:0:0:0: Direct-Access SMI  USB DISK 1100 
PQ: 0 ANSI: 0 CCS
  [8.342947] [drm]   DDC: 0x64d8 0x64d8 0x64dc 0x64dc 0x64e0 0x64e0 0x64e4 
0x64e4
  [8.350341] [drm]   Encoders:
  [8.353310] [drm] CRT1: INTERNAL_KLDSCP_DAC1
  [8.358195] BUG: unable to handle kernel NULL pointer dereference at 
0409
  [8.366104] IP:[8.367176] sd 0:0:0:0: Attached scsi generic sg1 type 0
  [8.368538] sd 0:0:0:0: [sdb] 7831552 512-byte logical blocks: (4.01 
GB/3.73 GiB)
  [8.369421] sd 0:0:0:0: [sdb] Write Protect is off
  [8.369427] sd 0:0:0:0: [sdb] Mode Sense: 43 00 00 00
  [8.370288] sd 0:0:0:0: [sdb] No Caching mode page found
  [8.370292] sd 0:0:0:0: [sdb] Assuming drive cache: write through
  [8.374944]  sdb: sdb1
  [8.378398] sd 0:0:0:0: [sdb] Attached SCSI removable disk

  [8.409733]  [] radeon_dp_getsinktype+0x1a/0x30 [radeon]
  [8.416805] PGD 0 
  [8.418841] Oops:  [#1] SMP 
  [8.422104] Modules linked in: hid_generic e1000e psmouse amdkfd usbhid 
uas amd_iommu_v2 ptp radeon(+) pps_core e1000(+) hid i2c_algo_bit ttm 
drm_kms_helper
   usb_storage syscopyarea sysfillrect sysimgblt ahci fb_sys_fops libahci drm 
video fjes
  [8.444029] CPU: 0 PID: 131 Comm: systemd-udevd Not tainted 
4.4.0-22-generic #40-Ubuntu
  [8.452036] Hardware name: AMD Corporation EBrazos Platform/Persimmon, 
BIOS LV-683 Version: 1.1 02/14/2012
  [8.461708] task: 88014780be80 ti: 880147888000 task.ti: 
880147888000
  [8.469194] RIP: 0010:[]  []

[Kernel-packages] [Bug 1587510] Re: Thinkpad keyboard backlight is not properly restored on resume from suspend

2016-06-07 Thread Joseph Salisbury 
** Also affects: linux (Ubuntu Xenial)
   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/1587510

Title:
  Thinkpad keyboard backlight is not properly restored on resume from
  suspend

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

Bug description:
  This is fixed in: https://github.com/torvalds/linux/commit/afcedeb

  Please backport this to Yakkety and to Xenial (once lp:1574498 fix is 
released)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marco  2143 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=e95ce812-4be1-4186-9f30-e10d6d6430f5
  InstallationDate: Installed on 2016-05-02 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160415)
  MachineType: LENOVO 20F9CTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=328bf97f-143a-483c-8ca9-282e1bfbdf79 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 04/14/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET43W (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20F9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET43W(1.11):bd04/14/2016:svnLENOVO:pn20F9CTO1WW:pvrThinkPadT460s:rvnLENOVO:rn20F9CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20F9CTO1WW
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

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

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

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

2016-06-07 Thread Brad Figg 
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1589997

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

Title:
  The device on /dev/sdx is not created when inserting new devices

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am on kubuntu xenial (upgraded from 15.10), from a couple of weeks I 
noticed that the pendrives i insert to my computer are detected but the devices 
under /dev are no longer created.
  I if reboot the pc with the pendrive already plugged in it works without 
issues. I'm suspecting from udev because of this text in syslog (full output in 
the summary)

  Jun  7 15:02:55 pc systemd-udevd[24747]: inotify_add_watch(9,
  /dev/sdb, 10) failed: No such file or directory

  I'm up to date on all the packages
  - linux-image-4.4.0-22-generic
  - udev - 229-4ubuntu6

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

-- 
Mailing list: https://launchpad.net/~kernel-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-06-07 Thread Emsi 
Testing...

-- 
You 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
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  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 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

2016-06-07 Thread Mike Rushton 
45996492e5c85aa0ac93a95d1b2d1ed56851c865 failed

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

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

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

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

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

[Kernel-packages] [Bug 1589997] Re: The device on /dev/sdx is not created when inserting new devices

2016-06-07 Thread Martin Pitt 
** Package changed: udev (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/1589997

Title:
  The device on /dev/sdx is not created when inserting new devices

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am on kubuntu xenial (upgraded from 15.10), from a couple of weeks I 
noticed that the pendrives i insert to my computer are detected but the devices 
under /dev are no longer created.
  I if reboot the pc with the pendrive already plugged in it works without 
issues. I'm suspecting from udev because of this text in syslog (full output in 
the summary)

  Jun  7 15:02:55 pc systemd-udevd[24747]: inotify_add_watch(9,
  /dev/sdb, 10) failed: No such file or directory

  I'm up to date on all the packages
  - linux-image-4.4.0-22-generic
  - udev - 229-4ubuntu6

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

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

[Kernel-packages] [Bug 1585598] Re: steady decrease in available memory (RAM) under 16.04

2016-06-07 Thread Joseph Salisbury 
** Tags added: kernel-da-key

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

Title:
  steady decrease in available memory (RAM) under 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just upgraded to 16.04 from 15.10, and now the memory usage
  steadily increases from when I first boot up. After just an hour or
  two, all 20GB of RAM is used up, even if nothing is running, and I am
  forced to reboot (rebooting frequently is incompatible with my normal
  tasks).

  Here is output from free, spaced about half a second apart:

  [0753][me@-t450s:~]$ free  -m
totalusedfree  shared  buff/cache   
available
  Mem:  19958100158087147   13148   
11648
  Swap: 20358   0   20358
  [0753][me@-t450s:~]$ free  -m
totalusedfree  shared  buff/cache   
available
  Mem:  19958100158067148   13151   
11647
  Swap: 20358   0   20358
  [0753][me@-t450s:~]$ free  -m
totalusedfree  shared  buff/cache   
available
  Mem:  19958100158047149   13153   
11646
  Swap: 20358   0   20358
  [0753][me@-t450s:~]$ free  -m
totalusedfree  shared  buff/cache   
available
  Mem:  19958100158017151   13156   
11644
  Swap: 20358   0   20358


  htop shows that 8GB is in use, although there are no applications
  using much.  I understand from free that it is all buffered/cached?

  Both htop and free suggest that the memory is really not available. 
  I do not know where it is going.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  cpbl   2571 F pulseaudio
   /dev/snd/controlC1:  cpbl   2571 F pulseaudio
   /dev/snd/controlC0:  cpbl   2571 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed May 25 07:54:14 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e5d0a2bb-27cf-494a-849c-1985d165fbd7
  InstallationDate: Installed on 2016-02-12 (102 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20BXCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=ea2fb511-8d62-4b96-bdaa-4b3f7bf79cc6 ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-05-24 (0 days ago)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

2016-06-07 Thread Andrey Kislyuk 
The Ubuntu 14.04 cloud images remain broken on m3.large and c3.large. Is
there a way to expedite building them with the fix? It seems that the
Ubuntu release process is broken, if bugs like this make it into the LTS
images and then don't get a clear timeline or priority for getting
fixed.

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

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

Bug description:
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 4.4.0-21-generic (buildd@lgw01-21) (gcc version 
5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 18:33:37 
UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=8ea401db-b84b-4cd6-a628-d72f30bbf1e5 ro console=tty1 console=ttyS0
  [0.00] KERNEL supported cpus:
  [0.00]   Intel GenuineIntel
  [0.00]   AMD AuthenticAMD
  [0.00]   Centaur CentaurHauls
  [0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
  [0.00] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point 
registers'
  [0.00] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
  [0.00] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers'
  [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 
bytes, using 'standard' format.
  [0.00] x86/fpu: Using 'eager' FPU context switches.
  [0.00] e820: BIOS-provided physical RAM map:
  [0.00] BIOS-e820: [mem 0x-0x0009dfff] usable
  [0.00] BIOS-e820: [mem 0x0009e000-0x0009] reserved
  [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved
  [0.00] BIOS-e820: [mem 0x0010-0xefff] usable
  [0.00] BIOS-e820: [mem 0xfc00-0x] reserved
  [0.00] BIOS-e820: [mem 0x0001-0x0001efff] usable
  [0.00] NX (Execute Disable) protection: active
  [0.00] SMBIOS 2.4 present.
  [0.00] Hypervisor detected: Xen
  [0.00] Xen version 4.2.
  [0.00] Netfront and the Xen platform PCI driver have been compiled 
for this kernel: unplug emulated NICs.
  [0.00] Blkfront and the Xen platform PCI driver have been compiled 
for this kernel: unplug emulated disks.
  [0.00] You might have to change the root device
  [0.00] from /dev/hd[a-d] to /dev/xvd[a-d]
  [0.00] in your root= kernel command line option
  [0.00] e820: last_pfn = 0x1f max_arch_pfn = 0x4
  [0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
  [0.00] e820: last_pfn = 0xf max_arch_pfn = 0x4
  [0.00] found SMP MP-table at [mem 0x000fbba0-0x000fbbaf] mapped at 
[880fbba0]
  [0.00] Scanning 1 areas for low memory corruption
  [0.00] RAMDISK: [mem 0x3407e000-0x36036fff]
  [0.00] ACPI: Early table checksum verification disabled
  [0.00] ACPI: RSDP 0x000EA020 24 (v02 Xen   )
  [0.00] ACPI: XSDT 0xFC00F5A0 54 (v01 XenHVM  
 HVML )
  [0.00] ACPI: FACP 0xFC00F260 F4 (v04 XenHVM  
 HVML )
  [0.00] ACPI: DSDT 0xFC0035E0 00BBF6 (v02 XenHVM  
 INTL 20090123)
  [0.00] ACPI: FACS 0xFC0035A0 40
  [0.00] ACPI: FACS 0xFC0035A0 40
  [0.00] ACPI: APIC 0xFC00F360 D8 (v02 XenHVM  
 HVML )
  [0.00] ACPI: HPET 0xFC00F4B0 38 (v01 XenHVM  
 HVML )
  [0.00] ACPI: WAET 0xFC00F4F0 28 (v01 XenHVM  
 HVML )
  [0.00] ACPI: SSDT 0xFC00F520 31 (v02 XenHVM  
 INTL 20090123)
  [0.00] ACPI: SSDT 0xFC00F560 31 (v02 XenHVM  
 INTL 20090123)
  [0.00] No NUMA configuration found
  [0.00] Faking a node at [mem 0x-0x0001efff]
  [0.00] NODE_DATA(0) allocated [mem 0x1efff7000-0x1efffbfff]
  [0.00] Zone ranges:
  [0.00]   DMA  [mem 0x1000-0x00ff]
  [0.00]   DMA32[mem 0x0100-0x]
  [0.00]   Normal   [mem 0x0001-0x0001efff]
  [0.00]   Device   empty
  [0.00] Movable zone start for each node
  [0.00] Early

[Kernel-packages] [Bug 1578358] Re: Bug with wistron_btns while booting

2016-06-07 Thread Joseph Salisbury 
Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

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

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

Title:
  Bug with wistron_btns while booting

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I've successfully installed Linux Mint XCFE 17.1 on my (old) notebook,
  but the computer is blocked during the boot. It seems that
  wistron_btns is the problem.

  The error I get are (see log) :

  "BUG: soft lockup - CPU#0 stuck for 23s! [systemd-udevd:402]"
  "wistron_btns: Unknown key code 70"

  My computer is a Medion WIM 2030 with :
  - Pentium M 1.7 (non-PAE, I've installed Mint with forcepae)
  - 1,25 Go RAM
  - 80 Go hard disk
  - Intel PRO/Wireless 2200BG Network connection
  - Some buttons to active the wifi, open Firefox,... that work well with 
Windows XP (dual boot)

  What can I do to make it boot ?

  Thanks for your help !

  Christophe

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

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

[Kernel-packages] [Bug 1585668] Re: Random file corruption when writing large files to hba mounted volume

2016-06-07 Thread Joseph Salisbury 
** Tags added: kernel-da-key

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

Title:
  Random file corruption when writing large files to hba mounted volume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We have an Ubuntu 16.04 LTS server with a 3Par volume via QLogic HBA.
  When mounted, writing large files to it repeatedly produces the
  following errors:

  [435753.554230] sd 5:0:0:1: [sde] tag#10 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
  [435753.554232] sd 5:0:0:1: [sde] tag#10 Sense Key : Illegal Request [current]
  [435753.554233] sd 5:0:0:1: [sde] tag#10 Add. Sense: Invalid field in cdb
  [435753.554235] sd 5:0:0:1: [sde] tag#10 CDB: Write same(16) 93 08 00 00 00 
00 04 7f ff f7 00 7f ff ff 00 00
  [435753.554236] blk_update_request: critical target error, dev sde, sector 
75497463

  We see similar errors with XFS and EXT4. ZFS seems to work fine
  though.  Here's how to recreate:

  // create a large file
  $ sudo dd if=/dev/urandom of=/random_file.bin bs=1048576 count=800

  // 3Par volume is /dev/sde
  $ sudo mkfs.xfs /dev/sde

  // mount to /test
  $ sudo mount /dev/sde /test

  // watch syslog
  $ tail -f /var/log/syslog &

  $ sudo cp /random_file.bin /test

  WORKAROUND: sudo sh -c 'echo 16384 >
  /sys/block/sde/queue/max_sectors_kb'

  We made this permanent by adding a udev rule:
  $ cat /etc/udev/rules.d/61-block-max-sectors.rules
  ACTION=="add|change", KERNEL=="sd[a-z]", SUBSYSTEM=="block", 
DRIVERS=="qla2xxx", RUN+="/bin/sh -c '/bin/echo 16384 > 
/sys/block/%k/queue/max_sectors_kb'"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 24 12:30 seq
   crw-rw 1 root audio 116, 33 May 24 12:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed May 25 10:18:33 2016
  HibernationDevice: RESUME=UUID=8e53840e-3198-4383-ac8b-0a811ed2d0b0
  InstallationDate: Installed on 2016-05-19 (5 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R310
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=459ae48a-619a-4e7e-8001-bbdf1968a944 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.2
  dmi.board.name: 05XKKK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R310
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1589997] [NEW] The device on /dev/sdx is not created when inserting new devices

2016-06-07 Thread Launchpad Bug Tracker 
You have been subscribed to a public bug:

I am on kubuntu xenial (upgraded from 15.10), from a couple of weeks I noticed 
that the pendrives i insert to my computer are detected but the devices under 
/dev are no longer created.
I if reboot the pc with the pendrive already plugged in it works without 
issues. I'm suspecting from udev because of this text in syslog (full output in 
the summary)

Jun  7 15:02:55 pc systemd-udevd[24747]: inotify_add_watch(9, /dev/sdb,
10) failed: No such file or directory

I'm up to date on all the packages
- linux-image-4.4.0-22-generic
- udev - 229-4ubuntu6

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

-- 
The device on /dev/sdx is not created when inserting new devices
https://bugs.launchpad.net/bugs/1589997
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 1589704] Re: workaround cavium thunderx silicon erratum

2016-06-07 Thread dann frazier 
** Changed in: linux (Ubuntu Xenial)
   Status: Confirmed => In Progress

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

Title:
  workaround cavium thunderx silicon erratum

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

Bug description:
  [Impact]
  This impacts 2 socket Cavium ThunderX systems using pass-1.1 silicon, and can 
result in IO hangs.

  [Test Case]
  $ dmesg | grep "ITS command queue timeout"

  [Regression Risk]
  The workaround is in gicv3 specific code, and only activated when the hw 
revision in the IIDR matches ThunderX pass 1.x silicon, so risk to other 
platforms is minimal.

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

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

[Kernel-packages] [Bug 1586838] Re: bcache causes a kernel bug when adding a new cache device

2016-06-07 Thread Joseph Salisbury 
Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

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

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

Title:
  bcache causes a kernel bug when adding a new cache device

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04 on virtualbox 5.0.20. VirtualBoxAddition is installed.

  The issue happens on both out-of-box 4.4.0 kernel and the later-
  installed 4.4.11 kernel. 100% re-producible. The same issue applies to
  both virtual hard drive (/dev/sdb) and file-base block device
  (/dev/loop2) I created within Ubuntu.

  $ sudo make-bcache -C /dev/sdb

  The error shows (through dmesg):
  [   47.616016] [ cut here ]
  [   47.616035] kernel BUG at 
/home/kernel/COD/linux/drivers/md/bcache/super.c:1822!
  [   47.616051] invalid opcode:  [#1] SMP
  [   47.616063] Modules linked in: vboxsf(OE) ppdev vboxvideo(OE) ttm 
drm_kms_helper input_leds joydev drm serio_raw lpc_ich fb_sys_fops syscopyarea 
i2c_piix4 sysfillrect sysimgblt 8250_fintek parport_pc vboxguest(OE) parport 
mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 multipath linear bcache raid0 hid_generic usbhid hid 
crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper 
ablk_helper cryptd psmouse fjes ahci libahci pata_acpi video
  [   47.616255] CPU: 2 PID: 1247 Comm: bcache-register Tainted: G   OE 
  4.4.11-040411-generic #201605182255
  [   47.616277] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS 
VirtualBox 12/01/2006
  [   47.616295] task: 88003514 ti: 88007684 task.ti: 
88007684
  [   47.616311] RIP: 0010:[]  [] 
cache_alloc.isra.20+0x646/0x670 [bcache]
  [   47.616340] RSP: 0018:880076843d10  EFLAGS: 00010246
  [   47.616352] RAX: 880079528c60 RBX: 8800796a RCX: 
05d2
  [   47.616367] RDX: 05d1 RSI:  RDI: 
00019d40
  [   47.616382] RBP: 880076843d28 R08: 88007fd19d40 R09: 
88007d001d00
  [   47.616398] R10: 880079528c60 R11: 88007b590958 R12: 

  [   47.616413] R13: 0010 R14: 88007c3c4000 R15: 
8800796a
  [   47.616428] FS:  7ff8ffa10700() GS:88007fd0() 
knlGS:
  [   47.616445] CS:  0010 DS:  ES:  CR0: 80050033
  [   47.616458] CR2: 7ff8ff4c1d30 CR3: 77f7 CR4: 
000406e0
  [   47.616476] DR0:  DR1:  DR2: 

  [   47.616491] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   47.616506] Stack:
  [   47.616511]  ea0001e880c0 88007cc28680  
880076843dd0
  [   47.616531]  c01373e3 880076843d58 811c8de5 
7fd61025
  [   47.616551]  7ff8ff4cf000 88007b590958 8800796a0008 
0009
  [   47.616570] Call Trace:
  [   47.616585]  [] register_bcache+0x2b3/0x1140 [bcache]
  [   47.616626]  [] ? page_add_file_rmap+0x25/0x60
  [   47.617074]  [] ? unlock_page+0x69/0x70
  [   47.617516]  [] kobj_attr_store+0xf/0x20
  [   47.617946]  [] sysfs_kf_write+0x37/0x40
  [   47.618353]  [] kernfs_fop_write+0x11d/0x170
  [   47.618755]  [] __vfs_write+0x37/0x110
  [   47.619149]  [] ? apparmor_file_permission+0x18/0x20
  [   47.619543]  [] ? security_file_permission+0x3d/0xc0
  [   47.619922]  [] ? percpu_down_read+0x12/0x50
  [   47.620290]  [] vfs_write+0xa9/0x1a0
  [   47.620648]  [] SyS_write+0x55/0xc0
  [   47.621021]  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [   47.621362] Code: 6a fd ff ff e9 4d fd ff ff be c0 00 40 02 4c 89 e7 e8 cf 
61 0b c1 48 85 c0 48 89 83 f0 0a 00 00 0f 85 96 fd ff ff e9 79 fd ff ff <0f> 0b 
0f 0b 0f 0b bf 40 00 00 00 e8 9a 90 09 c1 48 85 c0 48 89
  [   47.622456] RIP  [] cache_alloc.isra.20+0x646/0x670 
[bcache]
  [   47.622812]  RSP 
  [   47.623177] ---[ end trace 19bcd02731ac9be1 ]---
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate:

[Kernel-packages] [Bug 1587087] Re: OOM in guest Ubuntu with inflated balloon

2016-06-07 Thread Joseph Salisbury 
** Changed in: linux-lts-utopic (Ubuntu Trusty)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

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

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

Title:
  OOM in guest Ubuntu with inflated balloon

Status in linux-lts-utopic package in Ubuntu:
  In Progress
Status in linux-lts-utopic source package in Trusty:
  In Progress

Bug description:
  There is QEMU/KVM and a Linux OS running inside the guest.
  Inside the Linux guest a balloon consumes memory in accordance with
  commands performed on the host side in QEMU. Rapid increases of memory 
consumption
  inside the guest may end up with guest OOMs
  since memory locked by balloon couldn’t be returned to the guest OS/vm in 
time.

  The problem is addressed in mainstream Linux with the following
  patchset:

  commit 5a10b7dbf904bfe01bb9fcc6298f7df09eed77d5
  Author: Raushaniya Maksudova 
  Date: Mon Nov 10 09:36:29 2014 +1030
  virtio_balloon: free some memory from balloon on OOM

  Excessive virtio_balloon inflation can cause invocation of OOM-killer,
  when Linux is under severe memory pressure. Various mechanisms are
  responsible for correct virtio_balloon memory management. Nevertheless
  it is often the case that these control tools does not have enough time
  to react on fast changing memory load. As a result OS runs out of memory
  and invokes OOM-killer. The balancing of memory by use of the virtio
  balloon should not cause the termination of processes while there are
  pages in the balloon. Now there is no way for virtio balloon driver to
  free some memory at the last moment before some process will be get
  killed by OOM-killer.

  This does not provide a security breach as balloon itself is running
  inside guest OS and is working in the cooperation with the host. Thus
  some improvements from guest side should be considered as normal.

  To solve the problem, introduce a virtio_balloon callback which is
  expected to be called from the oom notifier call chain in out_of_memory()
  function. If virtio balloon could release some memory, it will make
  the system to return and retry the allocation that forced the out of
  memory killer to run.

  Allocate virtio feature bit for this: it is not set by default,
  the the guest will not deflate virtio balloon on OOM without explicit
  permission from host.

  Signed-off-by: Raushaniya Maksudova 
  Signed-off-by: Denis V. Lunev 
  Acked-by: Michael S. Tsirkin 
  Signed-off-by: Rusty Russell 

  commit 1fd9c67203af91977bf3b964ff3744cf74fc6f3f
  Author: Raushaniya Maksudova 
  Date: Mon Nov 10 09:35:29 2014 +1030

  virtio_balloon: return the amount of freed memory from
  leak_balloon()

  This value would be useful in the next patch to provide the amount of
  the freed memory for OOM killer.

  Signed-off-by: Raushaniya Maksudova 
  Signed-off-by: Denis V. Lunev 
  CC: Rusty Russell 
  CC: Michael S. Tsirkin 
  Signed-off-by: Rusty Russell 

  The problem is present in Ubuntu 14.10

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

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

[Kernel-packages] [Bug 1586630] Re: Wireless card QCA6164 crashes when booting linux

2016-06-07 Thread Joseph Salisbury 
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7-rc1 kernel[0].

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

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

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


Thanks in advance.

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

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

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

** Package changed: linux-firmware (Ubuntu) => linux (Ubuntu)

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

Title:
  Wireless card QCA6164 crashes when booting linux

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been trying to get my Qualcomm Atheros QCA6164 (168:0041 rev20)
  to work with diffrent firmwares without success. I've been testing
  Kalle Valos and atondvals firmware with no luck. Kalle Valos firmware
  enables wifi over 2,4GHz only, and not on every router for me. Last
  night I tried the new linux-firmwaren from:

  "http://mirrors.kernel.org/ubuntu/pool/main/l/linux-firmware/linux-
  firmware_1.157_all.deb"

  That didn't work either.

  I did install it, rebooted only to see the WiFi icon flash, so I tried
  "systemctl restart NetworkManager.service" just to see the WiFiicon
  falsh again and then the networkmanager crashed compleatly. so I ran
  the command again to get it back up but still no WiFi.

  Here is the dmesg for the ath10k

  
  [   16.553380] ath10k_pci :02:00.0: pci irq msi-x interrupts 8 irq_mode 0 
reset_mode 0
  [   17.034061] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/cal-pci-:02:00.0.bin failed with error -2
  [   17.617966] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/QCA6174/hw2.1/board-2.bin failed with error -2
  [   18.904246] ath10k_pci :02:00.0: firmware crashed! (uuid 
760b80fd-a2fb-4e90-a668-21cdeedd1d2b)
  [   18.904257] ath10k_pci :02:00.0: qca6164 hw2.1 (0x0501, 0x003405ff 
sub 17aa:3545) fw WLAN.RM.1.1-00141 fwapi 5 bdapi 1 htt-ver 0.0 wmi-op 4 htt-op 
3 cal otp max-sta 32 raw 0 hwcrypto 1 features ignore-otp,no-4addr-pad
  [   18.904261] ath10k_pci :02:00.0: debug 0 debugfs 1 tracing 1 dfs 0 
testmode 0
  [   18.905365] ath10k_pci :02:00.0: firmware register dump:
  [   18.905369] ath10k_pci :02:00.0: [00]: 0x0501 0x15B3 
0x000A012D 0x00955B31
  [   18.905373] ath10k_pci :02:00.0: [04]: 0x000A012D 0x00060330 
0x0016 0x83785006
  [   18.905376] ath10k_pci :02:00.0: [08]: 0x 0x0040 
0x00400600 0x0001
  [   18.905379] ath10k_pci :02:00.0: [12]: 0x0009 0x 
0x00931C61 0x00931C7D
  [   18.905382] ath10k_pci :02:00.0: [16]: 0x0096BDBC 0x009287BD 
0x 0x
  [   18.905385] ath10k_pci :02:00.0: [20]: 0x400A012D 0x0040E2B0 
0x00955A00 0x00404590
  [   18.905387] ath10k_pci :02:00.0: [24]: 0x809287D9 0x0040E310 
0x7A5087F8 0xC00A012D
  [   18.905390] ath10k_pci :02:00.0: [28]: 0x809288D7 0x0040E340 
0x 0xFFF08040
  [   18.905393] ath10k_pci :02:00.0: [32]: 0x809290FE 0x0040E360 
0x0040 0x00400600
  [   18.905395] ath10k_pci :02:00.0: [36]: 0x80929205 0x0040E380 
0x 0x00400600
  [   18.905398] ath10k_pci :02:00.0: [40]: 0x40928024 0x0040E3B0 
0x0040D3D0 0x0040D3D0
  [   18.905401] ath10k_pci :02:00.0: [44]: 0x 0x0040E3D0 
0x009BB001 0x00040020
  [   18.905403] ath10k_pci :02:00.0: [48]: 0x00401BF0 0x0001 
0x00404B9C 0x0040
  [   18.905406] ath10k_pci :02:00.0: [52]: 0x40928024 0x0040E3B0 
0x0040D3D0 0x0040D3D0
  [   18.905409] ath10k_pci :02:00.0: [56]: 0xA373B200 0x3D61F660 
0x05620156 0x0C677F60
  [   19.902111] ath10k_pci :02:00.0: failed to receive control response 
completion, polling..
  [   20.901952] ath10k_pci :02:00.0: ctl_resp never came in (-110)
  [   20.901972] ath10k_pci :02:00.0: failed to connect to HTC: -110
  [   20.978482] ath10k_pci :02:00.0: could not init core (-110)
  [   20.978513] ath10k_pci :02:00.0: could not probe fw (-110)
  [   21.878061] ath10k_pci :02:00.0: cannot restart a device that hasn't 
been started

  
  An update for this card would be nice :) I'll gladly help testing it and see 
if you provide instructions.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May 28 13:42:37 2016
  Dependencies:

  InstallationDate: Installed on 2016-05-24 (3 days ago)

[Kernel-packages] [Bug 1574102] Re: Regression (constant vibration of device) in xpad driver in Ubuntu 16.04

2016-06-07 Thread Joseph Salisbury 
I built a Xenial test kernel with a cherry-pick of commit 4efc6939a.
This test kernel can be downloaded from:

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

Can you test this kernel and see if it resolves this bug?

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

Title:
  Regression (constant vibration of device) in xpad driver in Ubuntu
  16.04

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

Bug description:
  Since upgrading to 16.04, I cannot launch Saints Row 2 or 3 from Steam
  without constant vibration from my Xbox360 controller. The symptoms
  are the same as outlined in https://github.com/paroj/xpad/issues/27.
  (I believe that github user submits xpad patches to upstream.) If I
  compile the f23507b version from that git repo, the problem resolves.
  This was not an issue on 15.10.

  Fix commit:
  https://github.com/paroj/xpad/commit/ef9e5b156c4b0042a75897697a792e7b1c5fde4b

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neil   2398 F pulseaudio
   /dev/snd/controlC2:  neil   2398 F pulseaudio
   /dev/snd/controlC0:  neil   2398 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 23 20:48:46 2016
  InstallationDate: Installed on 2015-10-23 (183 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: MSI MS-7721
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=UUID=a3f3cb16-7fb4-411c-9649-b40f12c5ff51 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V30.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-E35 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV30.6:bd12/15/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA55M-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0:
  dmi.product.name: MS-7721
  dmi.product.version: 6.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1574498] Re: Add support to thinkpad keyboard backlight

2016-06-07 Thread Joseph Salisbury 
** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => Medium

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

Title:
  Add support to thinkpad keyboard backlight

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

Bug description:
  Please backport this patch [1] to Ubuntu kernel (mostly Xenial, as I
  guess Yakety will include it): it adds support to keyboard backlight
  in new thinkpads, exposing the sysnode that UPower (and unity/gnome
  settings daemon) needs to control it.

  [1]
  
https://github.com/torvalds/linux/commit/bb28f3d51ff5e1be541d057708011cc1efe6fae9

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

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

[Kernel-packages] [Bug 1567237] Re: Kernel 3.19.0-58 freezes Ubuntu 14.04 on Dell XPS 15 9530

2016-06-07 Thread V B 
Hi Christopher,

I tried the kernel v4.7-rc2-yakkety and the freezing still happened with
the same message in the log before freezing:

Jun  7 10:28:52 my-ubuntu avahi-daemon[826]: Invalid response packet from host 
fe80::8eae:4cff:feff:1bf2.
Jun  7 11:29:42 my-ubuntu avahi-daemon[826]: Invalid response packet from host 
fe80::6a5b:35ff:febd:7254.
Jun  7 11:45:15 my-ubuntu compiz: pam_ecryptfs: seteuid error
Jun  7 11:51:40 my-ubuntu avahi-daemon[826]: Invalid response packet from host 
192.168.24.110.
Jun  7 11:55:52 my-ubuntu kernel: [101154.754902] [drm] HPD interrupt storm 
detected on connector HDMI-A-1: switching from hotplug detection to polling

By the way, I have a colleague who runs on the same laptop model as mine
Arch Linux with 4.4.5 kernel and he does not get this problem.

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

Title:
  Kernel 3.19.0-58 freezes Ubuntu 14.04 on Dell XPS 15 9530

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The latest security patch for  3.19.0 for Ubuntu 14.04 started
  freezing my laptop (Dell Inc. XPS 15 9530). All the patches before
  this one for the kernel 3.19.0 for Ubuntu 14.04 were OK. From log, the
  last message before freezing was "kernel: ...[drm] HPD interrupt storm
  detected on connector HDMI-A-1: switching from hotplug detection to
  polling", as you can see below:

  Apr 6 14:46:17 xxx-ubuntu dbus[1001]: [system] Activating service 
name='org.freedesktop.hostname1' (using servicehelper)
  Apr 6 14:46:17 xxx-ubuntu dbus[1001]: [system] Successfully activated service 
'org.freedesktop.hostname1'
  Apr 6 14:46:17 xxx-ubuntu kernel: [ 945.147481] systemd-hostnamed[11982]: 
Warning: nss-myhostname is not installed. Changing the local hostname might 
make it unresolveable. Plea
  se install nss-myhostname!
  Apr 6 14:50:36 xxx-ubuntu sudo: pam_ecryptfs: pam_sm_authenticate: /home/xxx 
is already mounted
  Apr 6 15:00:01 xxx-ubuntu CRON[12829]: (root) CMD (if [ -x 
/usr/sbin/backupninja ]; then /usr/sbin/backupninja; fi)
  Apr 6 15:02:29 xxx-ubuntu kernel: [ 1916.954839] sound hdaudioC0D0: HDMI: ELD 
buf size is 0, force 128
  Apr 6 15:02:29 xxx-ubuntu kernel: [ 1916.954877] sound hdaudioC0D0: HDMI: 
invalid ELD data byte 0
  Apr 6 15:07:35 xxx-ubuntu kernel: [ .796696] [drm] HPD interrupt storm 
detected on connector HDMI-A-1: switching from hotplug detection to polling

  This is the same symptom as described in the bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552333, which is
  a bug raised for 4.2 kernel running on Ubuntu 14.04 using the same
  laptop and the same Ubuntu installation as for this bug.

  At the moment I switched back to kernel 3.19.0-51 that does not cause this 
problem, but the possibility that from now on all future security patches for 
3.19.0 might freeze my laptop sounds very bad.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  valentinbrasov   3187 F pulseaudio
   /dev/snd/controlC2:  valentinbrasov   3187 F pulseaudio
   /dev/snd/controlC0:  valentinbrasov   3187 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-28 (192 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. XPS 15 9530
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-51-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro cgroup_enable=memory swapaccount=1 quiet 
splash crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-51.58~14.04.1-generic 3.19.8-ckt13
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-51-generic N/A
   linux-backports-modules-3.19.0-51-generic  N/A
   linux-firmware 1.127.20
  Tags:  trusty
  Uname: Linux 3.19.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/30/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: XPS 15 9530
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd07/30/2015:svnDellInc.:pnXPS159530:pvrA09:rvnDellInc.:rnXPS159530:rvrA09:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 15 9530
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1425699] Re: kernel panic on IBM Power8 PPC MAAS ephemeral image

2016-06-07 Thread Stefan Bader 
** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1425699

Title:
  kernel panic on IBM Power8 PPC MAAS ephemeral image

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Confirmed

Bug description:
  The kernel running on the 14.04 ephemeral image for MAAS when
  commissioning an IBM Power8 PPC server causes a periodic kernel panic.

  This happens intermittently and cannot be forcefully reproduced.

  The kernel version on the image is 3.13.0-27.50-generic according to
  the boot process.

  Attached is the boot process log with the kernel panics.

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

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

[Kernel-packages] [Bug 1579190] Re: Key 5 automatically pressed on some Logitech wireless keyboards

2016-06-07 Thread Trapper 
U1604-MATE:~$ uname -a
Linux U1604-MATE 4.4.0-22-generic #40+lp1579190 SMP Fri Jun 3 15:50:59 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

I have been running the patched kernel for a couple of days now. The
555's have totally ceased. I was experiencing the 5's frequently
daily prior to the patch but I realize the problem often vanishes for
periods of time. I will test for another week or so and also will inform
you promptly if I have a 555's event prior to 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/1579190

Title:
  Key 5 automatically pressed on some Logitech wireless keyboards

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

Bug description:
  I have a K520 Logitech keyboard and sometimes something starts to keep 
pressing key 5.
  It mostly happens when I leave the computer alone for some time, but 
sometimes also just during regular usage.

  It seems that this is a Linux specific issue as no one is complaining
  about this issue under Windows, but a couple of people are complaining
  for different versions of Ubuntu.

  It is always 5 and WladyXX3740 claims on the Logitech forum that:
  "happens on Ubuntu 15.10 and 16.04, does not happen on Ubuntu 15.04, probably 
kernel related."

  Here is where most of the people are complaining:
  
https://forums.logitech.com/t5/Keyboards-and-Keyboard-Mice/Ubuntu-15-10-and-K520-key-5-automatically-pressed-resulting-in/td-p/1488639

  I discovered that this is related to my Logitech keyboard by running this 
command:
  xinput test-xi2 --root

  Here is the device list:
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech K520   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ Logitech M310/M310t id=11   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint Stick   id=15   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint TouchPadid=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HDid=12   [slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=16   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=17   [slave  
keyboard (3)]

  And some extract from the output when this happens:
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags:
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 12 (PropertyEvent)
   property: 308 'Synaptics Off'
   changed: modified
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
     

[Kernel-packages] [Bug 1587091] Re: Extended statistics from balloon for proper memory management

2016-06-07 Thread Joseph Salisbury 
** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

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

Title:
  Extended statistics from balloon for proper memory management

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  There is QEMU/KVM and a Linux OS running inside the guest. 
  Inside the Linux guest a balloon consumes memory in accordance with 
  commands performed on the host side in QEMU and reports some statistics 
through memstat structure.
  For the Linux guest reported “free” value doesn’t describe the guest memory 
pressure at all.
  The provided patch set in Linux kernel extends the stat with available field.

  The problem is addressed in mainstream Linux with the following
  patchset:

  commit
  5057dcd0f1aaad57e07e728ba20a99e205c6b9de
  Author: Igor Redko 
  Date: Thu Mar 17 15:09:34 2016 -0700
  virtio_balloon: export 'available' memory to balloon statistics

  Add a new field, VIRTIO_BALLOON_S_AVAIL, to virtio_balloon memory
  statistics protocol, corresponding to 'Available' in /proc/meminfo.

  It indicates to the hypervisor how big the balloon can be inflated
  without pushing the guest system to swap.

  Signed-off-by: Igor Redko 
  Signed-off-by: Denis V. Lunev 
  Reviewed-by: Roman Kagan 
  Cc: Michael S. Tsirkin 
  Signed-off-by: Andrew Morton 
  Signed-off-by: Linus Torvalds 

  
  commit d02bd27bd33dd7e8d22594cd568b81be0cb584cd
  Author: Igor Redko 
  Date: Thu Mar 17 15:09:34 2016 -0700
  mm/page_alloc.c: calculate 'available' memory in a separate function

  Add a new field, VIRTIO_BALLOON_S_AVAIL, to virtio_balloon memory
  statistics protocol, corresponding to 'Available' in /proc/meminfo.

  It indicates to the hypervisor how big the balloon can be inflated
  without pushing the guest system to swap.  This metric would be very
  useful in VM orchestration software to improve memory management of
  different VMs under overcommit.

  This patch (of 2):

  Factor out calculation of the available memory counter into a separate
  exportable function, in order to be able to use it in other parts of the
  kernel.

  In particular, it appears a relevant metric to report to the hypervisor
  via virtio-balloon statistics interface (in a followup patch).

  Signed-off-by: Igor Redko 
  Signed-off-by: Denis V. Lunev 
  Reviewed-by: Roman Kagan 
  Cc: Michael S. Tsirkin 
  Signed-off-by: Andrew Morton 
  Signed-off-by: Linus Torvalds 

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

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

[Kernel-packages] [Bug 1584533] Re: Lenovo X220 unable to wlan after resume from sleep

2016-06-07 Thread Rudolf Leitgeb 
PS: Just marked this bug "Status confirmed" as per your request.

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

Title:
  Lenovo X220 unable to wlan after resume from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded to Ubuntu 16.04, and now whenever I wake up my laptop
  from sleep (hibernate doesn't work due to encrypted home directory), I
  am unable to connect to any wlan network. After a hot reboot or cold
  start everything is back to normal.

  Network manager would allow me to select already known wlan networks
  through "connect to hidden network", however, it would not allow me to
  establish the actual connection (connect button never becomes active).

  I will attach four files to this bug report:

  1. dmesg-pastreboot: dmesg after a hot reboot
  2. dmesg-pastsleep: dmesg after wakeup from sleep
  3. syslog-pastreboot: syslog snippet from timeframe after reboot
  4. syslog-pastsleep: syslog snippet from timeframe after wakeup from sleep

  Please let me know, if you need any further data or info.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rudolf 2944 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May 22 22:31:10 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-05-24 (1825 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MachineType: LENOVO 429135G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=080f751d-bbec-44b2-bd86-f4db52f4dddf ro quiet splash 
i915.semaphores=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-05-18 (4 days ago)
  dmi.bios.date: 04/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET42WW (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 429135G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET42WW(1.12):bd04/01/2011:svnLENOVO:pn429135G:pvrThinkPadX220:rvnLENOVO:rn429135G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 429135G
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1584533] Re: Lenovo X220 unable to wlan after resume from sleep

2016-06-07 Thread Rudolf Leitgeb 
Dear Christopher, thanks for your feedback. Following your suggestion I
upgraded to the latest BIOS version provided by Lenovo, here is the
output from this 'sudo dmidecode -s bios-version && sudo dmidecode -s
bios-release-date' line:

8DET70WW (1.40 )
05/14/2015

Sadly, there was no improvement on the bug, I still get situations where
my laptop won't connect top WLAN and will refuse any attempts to force
it to short of a reboot.

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

Title:
  Lenovo X220 unable to wlan after resume from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded to Ubuntu 16.04, and now whenever I wake up my laptop
  from sleep (hibernate doesn't work due to encrypted home directory), I
  am unable to connect to any wlan network. After a hot reboot or cold
  start everything is back to normal.

  Network manager would allow me to select already known wlan networks
  through "connect to hidden network", however, it would not allow me to
  establish the actual connection (connect button never becomes active).

  I will attach four files to this bug report:

  1. dmesg-pastreboot: dmesg after a hot reboot
  2. dmesg-pastsleep: dmesg after wakeup from sleep
  3. syslog-pastreboot: syslog snippet from timeframe after reboot
  4. syslog-pastsleep: syslog snippet from timeframe after wakeup from sleep

  Please let me know, if you need any further data or info.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rudolf 2944 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May 22 22:31:10 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-05-24 (1825 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MachineType: LENOVO 429135G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=080f751d-bbec-44b2-bd86-f4db52f4dddf ro quiet splash 
i915.semaphores=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-05-18 (4 days ago)
  dmi.bios.date: 04/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET42WW (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 429135G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET42WW(1.12):bd04/01/2011:svnLENOVO:pn429135G:pvrThinkPadX220:rvnLENOVO:rn429135G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 429135G
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1587089] Re: Hide "ballooned" memory from /proc in guest Ubuntu

2016-06-07 Thread Joseph Salisbury 
** Changed in: linux (Ubuntu Wily)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

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

Title:
  Hide "ballooned" memory from /proc in guest Ubuntu

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

Bug description:
  There is QEMU/KVM and a Linux guest running inside the guest. The amount
  of memory available for guest could be adjusted by balloon for better
  host scalability. The problem that this change is visible for end-user
  actually using the guest. This could (potentially) result in lawsuite
  from the end-user to hosting provides. 

  The problem is addressed in mainstream Linux with the following patch
  set:

  commit 997e120843e82609c8d99a9d5714e6cf91e14cbe
  Author: Denis V. Lunev 
  Date:   Thu Aug 20 00:49:49 2015 +0300
  virtio_balloon: do not change memory amount visible via /proc/meminfo
  
  Balloon device is frequently used as a mean of cooperative memory control
  in between guest and host to manage memory overcommitment. This is the
  typical case for any hosting workload when KVM guest is provided for
  end-user.
  
  Though there is a problem in this setup. The end-user and hosting provider
  have signed SLA agreement in which some amount of memory is guaranted for
  the guest. The good thing is that this memory will be given to the guest
  when the guest will really need it (f.e. with OOM in guest and with
  VIRTIO_BALLOON_F_DEFLATE_ON_OOM configuration flag set). The bad thing
  is that end-user does not know this.
  
  Balloon by default reduce the amount of memory exposed to the end-user
  each time when the page is stolen from guest or returned back by using
  adjust_managed_page_count and thus /proc/meminfo shows reduced amount
  of memory.
  
  Fortunately the solution is simple, we should just avoid to call
  adjust_managed_page_count with VIRTIO_BALLOON_F_DEFLATE_ON_OOM set.
  
  Signed-off-by: Denis V. Lunev 
  CC: Michael S. Tsirkin 
  Signed-off-by: Michael S. Tsirkin 

  
  commit b4d34037329f46ed818d3b0a6e1e23b9c8721f79
  Author: Denis V. Lunev 
  Date:   Thu Aug 20 00:49:48 2015 +0300
  virtio_ballon: change stub of release_pages_by_pfn
  
  and rename it to release_pages_balloon. The function originally takes
  arrays of pfns and now it takes pointer to struct virtio_ballon.
  This change is necessary to conditionally call adjust_managed_page_count
  in the next patch.
  
  Signed-off-by: Denis V. Lunev 
  CC: Michael S. Tsirkin 
  Signed-off-by: Michael S. Tsirkin 

  The issue affects ubuntu_server_14.0, ubuntu_server_15.04

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

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

[Kernel-packages] [Bug 1584052] Re: btrfs: file write crashes with false ENOSPC during snapshot creation since kernel 4.4 - fix available

2016-06-07 Thread Joseph Salisbury 
** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  btrfs: file write crashes with false ENOSPC during snapshot creation
  since kernel 4.4 - fix available

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

Bug description:
  Kernel 4.4 introduced a btrfs bug where a process writing a file while
  a snapshot creation is underway will receive a false ENOSPC error (No
  space left on device), even while there is plenty of free space on the
  file system. On systems where snapshots are created frequently, this
  leads to frequent database crashes (here with MySQL):

  2016-05-19T21:00:01.862106Z 0 [Warning] InnoDB: Retry attempts for writing 
partial data failed.
  2016-05-19T21:00:01.862133Z 0 [ERROR] InnoDB: Write to file ./ibdata1failed 
at offset 1048576, 16384 bytes should have been written, only 0 were written. 
Operating system error number 28. Check that your OS a
  nd file system support files of this size. Check also that the disk is not 
full or a disk quota exceeded.
  2016-05-19T21:00:01.862143Z 0 [ERROR] InnoDB: Error number 28 means 'No space 
left on device'

  The problem is well known: 
http://www.spinics.net/lists/linux-btrfs/msg52672.html
  A patch is available: https://patchwork.kernel.org/patch/7967161/
  The patch has been committed to the Linux Kernel source tree on Feb 18, 2016: 
https://github.com/torvalds/linux/commits/master/fs/btrfs/file.c

  Creating snapshots for undo and backup purposes without interrupting
  database operations is a central aspect of btrfs usage. This bug
  breaks server operations and should be fixed in the xenial kernel.

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

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

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

2016-06-07 Thread bugproxy 
--- Comment From cdead...@us.ibm.com 2016-06-07 08:23 EDT---
===END=== 
State: Verify by: cde00 on 31 May 2016 03:43:19 

== Comment: #1 - Application Cdeadmin  - 2016-03-21
15:55:11 == State: Verify by: cde00 on 31 May 2016 04:07:26 

 State: Verify by: byrneadw on 01 June 2016 11:03:58 

I loaded the test packages and can now successfully run HTX, I am not
seeing EEH errors anymore but I do still see these "FLOGI failure
Status:x3/x103 TMO:x14" errors.

2) from #1 execute ssh root@rcx2c360 (password is PASSW0RD)
 State: Verify by: byrneadw on 01 June 2016 11:07:41 

I loaded the test packages and can now successfully run HTX, I am not seeing 
EEH errors anymore but I do still see these "FLOGI failure Status:x3/x103 
TMO:x14" errors.
I see a comment earlier that suggests it is normal ( update #31 from Guilherme 
).

I'm wondering if this is another event to add to our ignore list. In
addition to the comment from Guilherme I can see a very similar event
already in our ignore list due to feedback we received on SW315535 -
event in that case was "FLOGI failure Status:x3/x103 TMO:x4". I'm not
sure what the difference between TMO:x4 vs TMO:x14 is

Is it ok to add "FLOGI failure Status:x3/x103 TMO:x14" events to our
ignore list also or is more debug required ?

root@rcx2c360:/tmp# dmesg -T --level=alert,crit,err
[Wed Jun  1 13:26:03 2016] lpfc :01:00.0: 0:1303 Link Up Event x1 received 
Data: x1 x0 x80 x0 x0 x0 0
[Wed Jun  1 13:26:03 2016] lpfc :01:00.0: 0:(0):2858 FLOGI failure 
Status:x3/x103 TMO:x14 Data x1800 x0
[Wed Jun  1 13:26:03 2016] lpfc :01:00.0: 0:(0):0100 FLOGI failure 
Status:x3/x103 TMO:x14
[Wed Jun  1 13:26:04 2016] lpfc :01:00.1: 1:(0):2858 FLOGI failure 
Status:x3/x103 TMO:x14 Data x1800 x0
[Wed Jun  1 13:26:04 2016] lpfc :01:00.1: 1:(0):0100 FLOGI failure 
Status:x3/x103 TMO:x14

===>> If required, access to system:
1) Telnet rchd08e0.rchland.ibm.com ( login with userid=dlth1025, 
password=tim2fish )
2) from #1 execute ssh root@rcx2c360 (password is PASSW0RD)

 State: Verify by: byrneadw on 02 June 2016 17:11:41 

considering TMO:x4 and TMO:x14 are timeout values it suggests to me this
is the same error we hit before with SW315535. The root cause of
SW315535 was the mfg usage of wrap plugs on the Fibre ports for the
purpose of running HTX. It resulted in the FLOGI message because a port
cannot login to itself.

The TMO values must have changed with Ubuntu 16.04 or new drivers as you
mentioned above. This is the first system with a Bluefin running with
16.04 we've had. In the past all our systems with Bluefin were running
in Habanero boxes with Ubuntu 14.04.03

In SW315535 Dan Eisenhauer commented :
"That "error" message means the link came up, so I am conjecturing that there 
is a wrap   plug installed,  The FLOGI failed messages would be expected in 
that case since a port cannot login to itself.  So, all those messages are 
expected and indicate that a wrap plug is installed and the adapters are 
functioning.  Those can all be ignored."

I removed the wrap plugs on our Garrison system and was able to boot many times 
without hitting this error. I think that matches the results of SW315535.
I'll confirm with our HTX guy that we need to continue using these wraps for 
HTX. If we do need them I can ignore this message per Dan's analysis. I can 
change the current entry in our ignore list so that the regex doesn't include 
the TMO value as that might change and catch us out again.

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

Title:
  STC840.20:Alpine:alp7fp1:Ubuntu 16.04, BlueFin (SAN) EEH 6 times
  during boot then disabled SRC BA188002:b0314a_1612.840

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

Bug description:
  == Comment: #0 - Application Cdeadmin  -
  2016-03-21 15:55:09 ==

  
  == Comment: #1 - Application Cdeadmin  - 2016-03-21 
15:55:11 ==
   State: Open by: mlfield on 21 March 2016 14:45:01 

  ==Automatic entries==
  Contact: LittleField, Michael *CONTRACTOR*
  Backup: Thirukumaran V T (thirukuma...@in.ibm.com), Deepti Umarani 
(deeptiumar...@in.ibm.com), Brian M. Carpenter(c...@us.ibm.com)

  = sys_capture v5.24 === 2016-03-21_14-25-41 ===

  |
  ||
  |System Hardware Information:
  |  NODE /Sys-0/Node-0, U78C7.001.1AQH383-P2
  | FSP  /Sys-0/Node-0/FSP-0, FSP-2 DD 1.0, U78C7.001.1AQH383-P1-C5
  |PSI  /Sys-0/Node-0/FSP-0/PSI-0
  |PSI  /Sys-0/Node-0/FSP-0/PSI-1
  | MEMBUF /Sys-0/Node-0/Membuf-12, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C11

[Kernel-packages] [Bug 1574102] Re: Regression (constant vibration of device) in xpad driver in Ubuntu 16.04

2016-06-07 Thread Joseph Salisbury 
** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  Regression (constant vibration of device) in xpad driver in Ubuntu
  16.04

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

Bug description:
  Since upgrading to 16.04, I cannot launch Saints Row 2 or 3 from Steam
  without constant vibration from my Xbox360 controller. The symptoms
  are the same as outlined in https://github.com/paroj/xpad/issues/27.
  (I believe that github user submits xpad patches to upstream.) If I
  compile the f23507b version from that git repo, the problem resolves.
  This was not an issue on 15.10.

  Fix commit:
  https://github.com/paroj/xpad/commit/ef9e5b156c4b0042a75897697a792e7b1c5fde4b

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neil   2398 F pulseaudio
   /dev/snd/controlC2:  neil   2398 F pulseaudio
   /dev/snd/controlC0:  neil   2398 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 23 20:48:46 2016
  InstallationDate: Installed on 2015-10-23 (183 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: MSI MS-7721
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=UUID=a3f3cb16-7fb4-411c-9649-b40f12c5ff51 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V30.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-E35 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV30.6:bd12/15/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA55M-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0:
  dmi.product.name: MS-7721
  dmi.product.version: 6.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1582858] Re: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled

2016-06-07 Thread xormar 
@penalvch
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1582858/comments/19

Which of the upstream kernels at http://kernel.ubuntu.com/~kernel-
ppa/mainline/?C=N;O=D should I test to find the last bad/first good one?
There is no v4.4.N-xenial kernel, so I don't really know where to start
and what to test. There are almost 40 kernels between v4.4-wily and
v4.6-yakkety ...

Then there's the problem that the server is sitting in a data center and
I have to be on site to en-/disable the iommu on each boot.

This also makes the bisecting very tedious, so I have no idea when I
will find the time to do it.

One more question: To setup the build environment, the requird packages
are all installed by apt-get build-dep linux-image-$(uname -r), or do I
need anything else?

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

Title:
  kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7
  if IOMMU is enabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a HP Proliant DL165 G7 I upgraded from 14.04.3 LTS to 16.04 LTS (I
  know, not supported).

  After reboot, the new kernel was loaded by GRUB, but failed to find
  the disks installed in the system (setup working for almost 2 years,
  standard HP setup with the SATA controller in AHCI mode and AHCI
  enabled during BIOS). It then dropped to a shell in initramfs, after
  hundreds (thousands?) of identical errors:

  [...] AMD-Vi: Event Logged [IO_PAGE_FAULT] device=xxx adress=yyy
  flags=0x...

  and the final error messages:

  ata3: softreset failed (1st FIS failed)
  ata4: softreset failed (1st FIS failed)
  ata3: limiting SATA link speed to 1.5 Gbps
  ata3: softreset failed (1st FIS failed)
  ata4: limiting SATA link speed to 1.5 Gbps
  ata4: softreset failed (1st FIS failed)
  ata3: reset failed, giving up
  ata4: reset failed, giving up

  The system disks are on ata1 and ata2, though.

  
  I tried booting the system from different other 16.04 boot media 
(ubuntu-16.04-server-amd64.iso, ubuntu-16.04-desktop-amd64.iso) into a rescue 
system. I also got the 
  [...] AMD-Vi: Event Logged ... messages. When the rescue shell was running, 
the system disks were also not detected, the installer I started as an 
experiment only offered the (USB disk) boot medium itself as installation 
target. The desktop installer and kernel then crashed with error messages about 
squashfs (sorry, didn't record those).

  Without any change, the same system boots without issues from a 14.04
  boot image, all disks present. Also, the 16.04 system boots fine if
  the old 3.13.0-86 kernel is selected in the GRUB menu.

  After some fiddling around, I turned off the IOMMU in the server's
  BIOS (under PCiExpress) - and all went back to normal, without any
  change on the installed system. Kernel 4.4.0-22-generic now boots just
  fine from the LVM-Root.

  So this is WORKSFORME now, but maybe somebody should look into it. I do 
believe that Proliants are quite common out there. If needed, I'll provide more 
info if possible - but currently I wouldn't know what.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 17 18:50 seq
   crw-rw 1 root audio 116, 33 May 17 18:50 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d46c7c15-9d36-4d87-930d-e43d447e8855
  InstallationDate: Installed on 2012-12-22 (1244 days ago)
  InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 
(20121017.2)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL165 G7
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/vg0-root ro net.ifnames=0 rootfstype=ext4
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2014-05-25 (725 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/27/2012
  dmi.bios.vendor: HP
  dmi.bios.version: O37
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrO37:bd07/27/2012:svnHP:pnProLiantDL165G7:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL165 G7
  dmi.sys.vendor: HP

To manage

[Kernel-packages] [Bug 1564664] Re: Peripheral Devices (keyboard and mouse) login delay

2016-06-07 Thread APolihron 
** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu-mate/+bug/1564664/+attachment/4678926/+files/syslog

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

Title:
  Peripheral Devices (keyboard and mouse) login delay

Status in ubuntu-mate:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  As a desktop setup i have a laptop+monitor+keyboard and mouse (usb).
  When i get the login screen i need to wait for like 10 sec for the laptop to 
take some impute from my Peripheral Devices (username+pass)
  Dont know if this is a kernel or an os Bug!
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apolitech   1478 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=de942971-6876-4da2-aff5-fda144aa02ba
  InstallationDate: Installed on 2016-05-28 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. K56CA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=5cdaf4a2-adc1-4e74-a34c-f0dfa50f37b0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-22-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/13/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K56CA.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K56CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK56CA.208:bd11/13/2012:svnASUSTeKCOMPUTERINC.:pnK56CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK56CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K56CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1564664/+subscriptions

-- 
Mailing list: https://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 1567781] Re: unable to handle kernel NULL pointer dereference at 00000134

2016-06-07 Thread hjl 
On Tue, Jun 07, 2016 at 03:57:55AM -, Christopher M. Penalver wrote:
> hjl, could you please test the latest mainline kernel (4.7-rc2) and
> advise to the results?
> 
Chris,
I have installed the 4.7rc2 kernel like 4.6rc6 before but
unfortunately the new kernel ist not started, the grub menu has the
4.7rc2 entry but does not offer it during start of the system.

regards
hjl

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

Title:
  unable to handle kernel NULL pointer dereference at 0134

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Problem is found in dmesg output:
  [   11.660671] BUG: unable to handle kernel NULL pointer dereference at 
0134
  [   11.660688] IP: [] mutex_lock+0x12/0x30
  [   11.660706] *pdpt = 33ee5001 *pde = 
  [   11.660714] Oops: 0002 [#1] SMP
  [   11.660723] Modules linked in: nfsd auth_rpcgss nfs_acl lockd parport_pc 
grace ppdev lp sunrpc parport autofs4 hid_generic hid_cherry pata_acpi usbhid 
hid psmouse gma500_gfx i2c_algo_bit r8169 drm_kms_helper drm sdhci_pci pata_sch 
sdhci mii video
  [   11.660772] CPU: 1 PID: 242 Comm: plymouthd Not tainted 4.2.0-35-generic 
#40-Ubuntu
  [   11.660779] Hardware name: CompuLab CM-iAM/SBC-FITPC2i/CM-iAM/SBC-FITPC2i, 
BIOS NAPA0001.86C..D.1009141059 09/14/2010
  [   11.660785] task: f5cf08c0 ti: f2364000 task.ti: f2364000
  [   11.660792] EIP: 0060:[] EFLAGS: 00010286 CPU: 1
  [   11.660798] EIP is at mutex_lock+0x12/0x30
  [   11.660804] EAX: 0134 EBX: 0134 ECX:  EDX: 8000
  [   11.660810] ESI:  EDI:  EBP: f2365ea8 ESP: f2365ea4
  [   11.660815]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   11.660820] CR0: 80050033 CR2: 0134 CR3: 31a1d540 CR4: 06f0
  [   11.660824] Stack:
  [   11.660828]  f19f93a0 f2365ec0 f8586171 f326dea0 f1ad7000  
f1a0a400 f2365ec8
  [   11.660842]  f858621f f2365edc f845ff47 f1a0a400 f1a0a400 f1a0a400 
f2365eec f84b6019
  [   11.660856]  f2365f04 c11b2de4 f2365f04 f856a78a f74d59d0  
 f1a0a400
  [   11.660869] Call Trace:
  [   11.660935]  [] __drm_modeset_lock_all+0x91/0x130 [drm]
  [   11.660986]  [] drm_modeset_lock_all+0xf/0x30 [drm]
  [   11.661018]  [] 
drm_fb_helper_restore_fbdev_mode_unlocked+0x17/0x50 [drm_kms_helper]
  [   11.661048]  [] psb_driver_lastclose+0x19/0x50 [gma500_gfx]
  [   11.661060]  [] ? kfree+0x134/0x140
  [   11.661110]  [] drm_lastclose+0x2a/0x140 [drm]
  [   11.661159]  [] drm_release+0x29f/0x490 [drm]
  [   11.661170]  [] __fput+0xcf/0x210
  [   11.661179]  [] fput+0xd/0x10
  [   11.661189]  [] task_work_run+0x7f/0xa0
  [   11.661200]  [] do_notify_resume+0x75/0x80
  [   11.661209]  [] work_notifysig+0x16/0x1b
  [   11.661215] Code: 00 00 c3 8d b6 00 00 00 00 31 c0 5d c3 8d b6 00 00 00 00 
8d bf 00 00 00 00 55 89 e5 53 3e 8d 74 26 00 89 c3 e8 60 ef ff ff 89 d8  ff 
08 79 05 e8 74 07 00 00 64 a1 c8 c0 bf c1 89 43 10 5b 5d
  [   11.661311] EIP: [] mutex_lock+0x12/0x30 SS:ESP 0068:f2365ea4
  [   11.661323] CR2: 0134
  [   11.661332] ---[ end trace 3bb80835d39a3e44 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-35-generic 4.2.0-35.40
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Apr  8 08:21:26 2016
  HibernationDevice: RESUME=UUID=fda9b258-61a9-4bc5-974e-738538cee628
  InstallationDate: Installed on 2013-07-09 (1003 days ago)
  InstallationMedia: Lubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
  MachineType: CompuLab CM-iAM/SBC-FITPC2i
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic 
root=UUID=41b7698f-f3fa-4940-8e13-9378c5021e90 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-35-generic N/A
   linux-backports-modules-4.2.0-35-generic  N/A
   linux-firmware1.149.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-12-23 (106 days ago)
  dmi.bios.date: 09/14/2010
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: NAPA0001.86C..D.1009141059
  dmi.board.name: CM-iAM/SBC-FITPC2i
  dmi.board.vendor: Intel Corporation
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: OEM
  dmi.chassis.version: N/A
  dmi.modalias:

[Kernel-packages] [Bug 1584479] Re: [MSI GP72 6QE Leopard Pro] Touchpad not detected on 16.04

2016-06-07 Thread Sam 
Re,

With the last kernel (4.7-rc2), I have more and more trouble :
- virtualboxdkms can't build 
(https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1589934)
- I use gnome-shell and all animations (ie starting session, menu to close 
session, ...) are disabled (like lags with vnc or teamviewer)
- without "acpi=off" option, I can't go to session page ; with logs, I can find 
:
Jun  7 13:34:48 MSI-I7 kernel: [0.628367] pinctrl core: initialized pinctrl 
subsystem
Jun  7 13:34:48 MSI-I7 kernel: [0.628509] RTC time: 11:34:41, date: 06/07/16
Jun  7 13:34:48 MSI-I7 kernel: [0.629350] NET: Registered protocol family 16
Jun  7 13:34:48 MSI-I7 kernel: [0.638456] cpuidle: using governor ladder
Jun  7 13:34:48 MSI-I7 kernel: [0.654445] cpuidle: using governor menu
-->>> Jun  7 13:34:48 MSI-I7 kernel: [0.654450] PCCT header not found.
-->>> Jun  7 13:34:48 MSI-I7 kernel: [0.654522] ACPI FADT declares the 
system doesn't support PCIe ASPM, so disable it
Jun  7 13:34:48 MSI-I7 kernel: [0.654524] ACPI: bus type PCI registered
Jun  7 13:34:48 MSI-I7 kernel: [0.654525] acpiphp: ACPI Hot Plug PCI 
Controller Driver version: 0.5
Jun  7 13:34:48 MSI-I7 kernel: [0.654585] PCI: MMCONFIG for domain  
[bus 00-ff] at [mem 0xe000-0xefff] (base 0xe000)
Jun  7 13:34:48 MSI-I7 kernel: [0.654587] PCI: MMCONFIG at [mem 
0xe000-0xefff] reserved in E820
Jun  7 13:34:48 MSI-I7 kernel: [0.654595] PCI: Using configuration type 1 
for base access
Jun  7 13:34:48 MSI-I7 kernel: [0.670561] HugeTLB registered 1 GB page 
size, pre-allocated 0 pages
Jun  7 13:34:48 MSI-I7 kernel: [0.670562] HugeTLB registered 2 MB page 
size, pre-allocated 0 pages
Jun  7 13:34:48 MSI-I7 kernel: [0.670758] ACPI: Added _OSI(Module Device)
Jun  7 13:34:48 MSI-I7 kernel: [0.670759] ACPI: Added _OSI(Processor Device)
Jun  7 13:34:48 MSI-I7 kernel: [0.670760] ACPI: Added _OSI(3.0 _SCP 
Extensions)
Jun  7 13:34:48 MSI-I7 kernel: [0.670761] ACPI: Added _OSI(Processor 
Aggregator Device)
Jun  7 13:34:48 MSI-I7 kernel: [0.670763] ACPI: Added _OSI(Linux)
Jun  7 13:34:48 MSI-I7 kernel: [0.670765] ACPI : EC: EC description table 
is found, configuring boot EC
Jun  7 13:34:48 MSI-I7 kernel: [0.670766] ACPI : EC: EC started
Jun  7 13:34:48 MSI-I7 kernel: [0.690017] ACPI: Executed 21 blocks of 
module-level executable AML code
Jun  7 13:34:48 MSI-I7 kernel: [0.698739] ACPI: Executed 3 blocks of 
module-level executable AML code
Jun  7 13:34:48 MSI-I7 kernel: [0.701150] ACPI: 10 ACPI AML tables 
successfully acquired and loaded
Jun  7 13:34:48 MSI-I7 kernel: [0.701152] 
-->>> Jun  7 13:34:48 MSI-I7 kernel: [0.881045] ACPI: [Firmware Bug]: BIOS 
_OSI(Linux) query honored via cmdline


In the MSI website, near the BIOS update, I see firmware update but only for 
Win$$ ;-(  So, I think I need to update after install a Win$$. This process 
take some time (I need my computer to work).


Thanks

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

Title:
  [MSI GP72 6QE Leopard Pro] Touchpad not detected on 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  I just install Ubuntu 16.04 on my new MSI laptop G72 6QE.
  My touchpad doesn't work and recognize at all.

  I try :
  - Fn+F3 to activate my touchpad
  - xinput list and is not listed
  - xev and nothing append (no signal)
  - cat /proc/bus/input/devices ddoesn't display touchpad (only HDMI, mic, 
headphone, external mouse and keyboard)
  - I don't know if there is a link, but some buttons of my keyboard don't work 
(like Fn+arrows to manage sound and luminosity) :
  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input0
  U: Uniq=
  H: Handlers=sysrq kbd event0 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=60070290 8380207af040d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  
  Thanks
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1305 F pulseaudio
moi1668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9649bbed-2d32-42cd-a446-43abaa9ab1f3
  InstallationDate: Installed on 2016-05-20 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Micro-Star International Co., Ltd. GP72 6QE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic 
root=UUID=80432220-0bdf-49f0-a145-0c015ad36c2a ro rootflags=subvol=@ acpi=off 
acpi_osi=!

[Kernel-packages] [Bug 1565864] Re: Hardware-specific: Fan is running at full speed on resume

2016-06-07 Thread raxp 
Nope, still same results

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

Title:
  Hardware-specific: Fan is running at full speed on resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug is related to Asus 1025C laptop.
  Steps to reproduce:

  1) Boot into Ubuntu
  2) run pm-suspend
  3) Wake up the laptop

  After a few seconds the CPU fan spins up to max speed and it doesn't slow 
down until reboot/poweroff.
  Hibernation can also fix this, so, fan runs at normal speed.
  It is not a PWM fan, so, I guess, I can't control it via /sys.

  Output of "sensors" before suspend:
  acpitz-virtual-0
  Adapter: Virtual device
  temp1:+55.0°C  (crit = +255.0°C)

  after:
  acpitz-virtual-0
  Adapter: Virtual device
  temp1:+0.0°C  (crit = +255.0°C)

  I've had a Linux Mint 17 before Ubuntu 15.10. No issues were in Mint. Before 
Mint, I've used a Kubuntu 14.04, 14.10, no issues either.
  I've tried to compile old versions of linux kernel (from the official git 
repo) and I noticed, that 3.16 kernel was the latest, where fan works properly. 
3.17-rc1 breaks it.

  According to git commit history, 3.17 kernel have many commits related
  to ACPI/PM fixes.

  My guess is that kernel doesn't restore thermal sensor device from
  sleep properly since 3.17.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-34-generic 4.2.0-34.39
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raxp   1809 F pulseaudio
  CurrentDesktop: MATE
  Date: Mon Apr  4 17:17:13 2016
  HibernationDevice: RESUME=UUID=31cbf4f8-c9b4-4025-b1fd-d5f474861585
  InstallationDate: Installed on 2016-03-16 (19 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release i386 (20151021)
  MachineType: ASUSTeK COMPUTER INC. 1025C
  ProcFB: 0 psbdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic 
root=UUID=98d65d26-361a-4e60-80e4-7b63d31d1ec6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-34-generic N/A
   linux-backports-modules-4.2.0-34-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1025C.1001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 1025C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1025C.1001:bd04/16/2012:svnASUSTeKCOMPUTERINC.:pn1025C:pvrx.x:rvnASUSTeKCOMPUTERINC.:rn1025C:rvrx.xx:cvnASUSTeKCOMPUTERINC.:ct10:cvrx.x:
  dmi.product.name: 1025C
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1575250] Re: system takes exactly five minutes to wake from suspend

2016-06-07 Thread Alistair Buxton 
Sure, just give me access to a build server where I can build the
kernels for bisection.

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

Title:
  system takes exactly five minutes to wake from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To reproduce:

  1. Close laptop lid.
  2. Wait a couple of minutes.
  3. Open laptop lid.

  Result: the screen remains powered off and the system will not respond
  in any way. Pressing keys does nothing. Pressing the power button does
  nothing. There is no disk activity but the power light is lit. After
  exactly five minutes (to the second) the system resumes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  al 1892 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 26 16:46:08 2016
  HibernationDevice: RESUME=UUID=8623f57e-2fc2-4a9a-bd35-73f33e1aeb59
  InstallationDate: Installed on 2016-04-21 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20040M18
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=0f83fbb5-4903-4610-9f32-1ab22c935bb0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 24CN61WW
  dmi.board.name: Caucasus2
  dmi.board.vendor: LENOVO
  dmi.board.version: Rev 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: Rev 1.0
  dmi.modalias: 
dmi:bvnLENOVO:bvr24CN61WW:bd08/11/2010:svnLENOVO:pn20040M18:pvrLenovoIdeapadS10-3t:rvnLENOVO:rnCaucasus2:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0:
  dmi.product.name: 20040M18
  dmi.product.version: Lenovo Ideapad S10-3t
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1589379] Re: System frozen after resume, on Ubuntu 16.04 kernel 4.4.0-22

2016-06-07 Thread Christopher M. Penalver 
bastien, as per the release notes from
http://h20564.www2.hp.com/hpsc/swd/public/readIndex?sp4ts.oid=7834518=8=4192
an update to your computer's buggy, insecure, and outdated BIOS is
available (1.11). When you update to this following
https://help.ubuntu.com/community/BIOSUpdate does this improve the
situation?

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: needs-bisect

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

Title:
  System frozen after resume, on Ubuntu 16.04 kernel 4.4.0-22

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Problem on HP probook 450, with Radeon R7 M260/M265.
  The last kernel on which resume works is 4.4.3-040403-generic.
  I have the problem on all kernels above, including v4.6-rc7-wily.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  Annotation: This occurred during a previous suspend, and prevented the system 
from resuming properly.
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bastien2164 F pulseaudio
  Date: Mon Jun  6 07:50:40 2016
  DuplicateSignature: suspend/resume:HP HP ProBook 450 G3:N78 Ver. 01.06
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=1888eb9c-89d7-4478-b4bc-1ce90d714377
  InstallationDate: Installed on 2016-05-05 (31 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  InterpreterPath: /usr/bin/python3.5
  MachineType: HP HP ProBook 450 G3
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=b919e8bc-92b0-4fcc-b9d3-0d8f38803a2b ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  Title: [HP HP ProBook 450 G3] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/18/2015
  dmi.bios.vendor: HP
  dmi.bios.version: N78 Ver. 01.06
  dmi.board.name: 8101
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.20
  dmi.chassis.asset.tag: 5CD6080WDD
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN78Ver.01.06:bd12/18/2015:svnHP:pnHPProBook450G3:pvr:rvnHP:rn8101:rvrKBCVersion16.20:cvnHP:ct10:cvr:
  dmi.product.name: HP ProBook 450 G3
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1585765] Re: GPU driver problem with i915 driver

2016-06-07 Thread Christopher M. Penalver 
monochromec, to clarify, 4.4.2 kernel from where precisely?

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

Title:
  GPU driver problem with i915 driver

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  First observed on freedesktop.org:
  https://bugs.freedesktop.org/show_bug.cgi?id=94002

  Steps to reproduce:

  1) Suspend machine
  2) Wake it back up
  3) X11 crashes and takes E17 with it.

  Environment:

  - Kernel: 4.4.0-22-generic (stock)
  - E17
  - Otherwise: stock 16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  root   9443 F pommed
christoph  13343 F pulseaudio
  Date: Wed May 25 21:12:14 2016
  HibernationDevice: RESUME=UUID=b3b2afbf-edea-40c5-9506-44b7f0cbf4d2
  InstallationDate: Installed on 2014-04-26 (760 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  MachineType: Apple Inc. MacBookPro8,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \boot\vmlinuz-4.4.0-22-generic ro irqpoll 
root=UUID=6a0139c1-488b-49e1-adee-a520c44dd9ab 
initrd=boot\initrd.img-4.4.0-22-generic
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (33 days ago)
  dmi.bios.date: 10/26/15
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP81.88Z.0047.B2C.1510261540
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-94245B3640C91C81
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro8,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-94245B3640C91C81
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B2C.1510261540:bd10/26/15:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:
  dmi.product.name: MacBookPro8,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/1585765/+subscriptions

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

[Kernel-packages] [Bug 1453812] Re: System freeze when using LibreOffice Writer

2016-06-07 Thread Christopher M. Penalver 
yurx cherio, 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/1453812

Title:
  System freeze when using LibreOffice Writer

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  LibreOffice Writer is freezing the system after a few minutes (Ubuntu
  15.04, libreoffice-writer 4.4.2-0ubuntu1): the only possible action is
  moving the mouse pointer on the screen. Impossible to connect to a tty
  session to kill Xorg. A physical reboot is necessary. Note that I used
  LibreOffice Calc without problem.

  The problem has been encountered also under Fedora 21:
  http://forums.fedora-fr.org/viewtopic.php?id=63428

  WORKAROUND: Use nvidia-304-updates or 340.76.

  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.360
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroRelease: Ubuntu 15.04
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation G96GL [Quadro FX 580] [10de:0659] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: NVIDIA Corporation Device [10de:063a]
  LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Hewlett-Packard HP Z400 Workstation
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr 
keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Tags:  vivid ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-15-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/06/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G3 v03.07
  dmi.board.asset.tag: CZC0195Y06
  dmi.board.name: 0B4Ch
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: D
  dmi.chassis.asset.tag: CZC0195Y06
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G3v03.07:bd04/06/2010:svnHewlett-Packard:pnHPZ400Workstation:pvr:rvnHewlett-Packard:rn0B4Ch:rvrD:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Z400 Workstation
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Wed May 20 08:19:58 2015
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.1-0ubuntu3

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

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

[Kernel-packages] [Bug 1579410] Re: Cannot suspend HP ProLiant SE316M1R2

2016-06-07 Thread Christopher M. Penalver 
Vincas Dargis:
>"An now how cant it help solving this issue?"

Provide the results of testing 4.7-rc2.

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

Title:
  Cannot suspend HP ProLiant SE316M1R2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  pm-suspend does not work on HP ProLiant SE316M1R2 system.

  I am not sure if hardware actually supports that though, but there is
  kernel crash (see syslog.txt attached with Call Trace) which maybe is
  the cause.

  Monitor goes off for few seconds but after that system resumes and
  works as before.

  Also, some interesting lines:

  May  7 20:58:23 tomashp-server kernel: [ 4374.025981] pci_legacy_suspend(): 
hpsa_suspend+0x0/0x10 [hpsa] returns -38
  May  7 20:58:23 tomashp-server kernel: [ 4374.025986] dpm_run_callback(): 
pci_pm_freeze+0x0/0xe0 returns -38
  May  7 20:58:23 tomashp-server kernel: [ 4374.025987] PM: Device :06:00.0 
failed to freeze async: error -38s2disks

  These lines also appears when using s2disk.

  s2ram gives:

  KMS graphics driver is in use, skipping quirks.
  s2ram_do: Invalid argument

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.21.22
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Sat May  7 20:55:52 2016
  HibernationDevice: RESUME=UUID=2f75ed7f-85b4-4d1f-abd5-04d88f7c8be3
  InstallationDate: Installed on 2015-10-12 (208 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  IwConfig:
   eth0  no wireless extensions.

   eth1  no wireless extensions.

   lono wireless extensions.
  MachineType: HP ProLiant SE316M1R2
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=4d4fc552-1b5c-42b8-8829-9249646d798c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (15 days ago)
  dmi.bios.date: 07/02/2013
  dmi.bios.vendor: HP
  dmi.bios.version: R02
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrR02:bd07/02/2013:svnHP:pnProLiantSE316M1R2:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant SE316M1R2
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1585210] Re: Unstable Wifi Intel 7265

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

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

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

Title:
  Unstable Wifi Intel 7265

Status in linux package in Ubuntu:
  Invalid

Bug description:
  With some routers, my wifi connection drops and restarts with the
  following error:

  May 23 20:12:00 neftali kernel: [ 1262.463055] iwlwifi :02:00.0: Queue 16 
stuck for 1 ms.
  May 23 20:12:00 neftali kernel: [ 1262.463066] iwlwifi :02:00.0: Current 
SW read_ptr 244 write_ptr 24
  May 23 20:12:00 neftali kernel: [ 1262.463107] iwl data: : 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00  
  May 23 20:12:00 neftali kernel: [ 1262.463131] iwlwifi :02:00.0: FH 
TRBs(0) = 0x
  May 23 20:12:00 neftali kernel: [ 1262.463152] iwlwifi :02:00.0: FH 
TRBs(1) = 0xc0110003
  May 23 20:12:00 neftali kernel: [ 1262.463173] iwlwifi :02:00.0: FH 
TRBs(2) = 0x
  May 23 20:12:00 neftali kernel: [ 1262.463193] iwlwifi :02:00.0: FH 
TRBs(3) = 0x80300017
  May 23 20:12:00 neftali kernel: [ 1262.463206] iwlwifi :02:00.0: FH 
TRBs(4) = 0x
  May 23 20:12:00 neftali kernel: [ 1262.463231] iwlwifi :02:00.0: FH 
TRBs(5) = 0x
  May 23 20:12:00 neftali kernel: [ 1262.463252] iwlwifi :02:00.0: FH 
TRBs(6) = 0x
  May 23 20:12:00 neftali kernel: [ 1262.463273] iwlwifi :02:00.0: FH 
TRBs(7) = 0x00709006
  May 23 20:12:00 neftali kernel: [ 1262.463331] iwlwifi :02:00.0: Q 0 is 
active and mapped to fifo 3 ra_tid 0x [24,24]
  May 23 20:12:00 neftali kernel: [ 1262.463394] iwlwifi :02:00.0: Q 1 is 
active and mapped to fifo 2 ra_tid 0x [0,0]
  May 23 20:12:00 neftali kernel: [ 1262.463456] iwlwifi :02:00.0: Q 2 is 
active and mapped to fifo 1 ra_tid 0x [50,50]
  May 23 20:12:00 neftali kernel: [ 1262.463518] iwlwifi :02:00.0: Q 3 is 
active and mapped to fifo 0 ra_tid 0x [0,0]
  May 23 20:12:00 neftali kernel: [ 1262.463580] iwlwifi :02:00.0: Q 4 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  May 23 20:12:00 neftali kernel: [ 1262.463642] iwlwifi :02:00.0: Q 5 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  May 23 20:12:00 neftali kernel: [ 1262.463705] iwlwifi :02:00.0: Q 6 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  May 23 20:12:00 neftali kernel: [ 1262.463767] iwlwifi :02:00.0: Q 7 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  May 23 20:12:00 neftali kernel: [ 1262.463829] iwlwifi :02:00.0: Q 8 is 
active and mapped to fifo 3 ra_tid 0x [0,0]
  May 23 20:12:00 neftali kernel: [ 1262.463891] iwlwifi :02:00.0: Q 9 is 
active and mapped to fifo 7 ra_tid 0x [7,7]
  May 23 20:12:00 neftali kernel: [ 1262.463974] iwlwifi :02:00.0: Q 10 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  May 23 20:12:00 neftali kernel: [ 1262.464036] iwlwifi :02:00.0: Q 11 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  May 23 20:12:00 neftali kernel: [ 1262.464098] iwlwifi :02:00.0: Q 12 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  May 23 20:12:00 neftali kernel: [ 1262.464160] iwlwifi :02:00.0: Q 13 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  May 23 20:12:00 neftali kernel: [ 1262.464222] iwlwifi :02:00.0: Q 14 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  May 23 20:12:00 neftali kernel: [ 1262.464284] iwlwifi :02:00.0: Q 15 is 
active and mapped to fifo 5 ra_tid 0x [0,0]
  May 23 20:12:00 neftali kernel: [ 1262.464346] iwlwifi :02:00.0: Q 16 is 
active and mapped to fifo 1 ra_tid 0x000f [244,24]
  May 23 20:12:00 neftali kernel: [ 1262.464408] iwlwifi :02:00.0: Q 17 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  May 23 20:12:00 neftali kernel: [ 1262.464470] iwlwifi :02:00.0: Q 18 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  May 23 20:12:00 neftali kernel: [ 1262.464532] iwlwifi :02:00.0: Q 19 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  May 23 20:12:00 neftali kernel: [ 1262.464594] iwlwifi :02:00.0: Q 20 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  May 23 20:12:00 neftali kernel: [ 1262.464656] iwlwifi :02:00.0: Q 21 is 
inactive and mapped to

[Kernel-packages] [Bug 1575437] Re: Asus ZenBook UX501VW frequently hangs during boot under Ubuntu 16.04

2016-06-07 Thread Christopher M. Penalver 
Adric Norris, to clarify, does using the WORKAROUND nouveau.modeset=0
also work in the default Ubuntu repository kernel?

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

Title:
  Asus ZenBook UX501VW frequently hangs during boot under Ubuntu 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A fresh install of Ubuntu Gnome 16.04 on an Asus ZenBook UX501VW hangs
  during boot, approximately 80% to 90% of the time... occasionally it
  manages to complete the startup for no discrenable reason, at which
  point the fan will run at full speed nonstop (very loud) until the
  machine is powered down. Due to the information from
  , I installed the wily 4.3.5 kernel (replacing 4.4.0)
  from ,
  which appears to work perfectly... no bootup hangs or odd fan
  behaviour

  The hang occurs shortly after providing the disk decryption key (I
  opted for full-disk encryption during installation). The issue occurs
  frequently when booting Ubuntu Gnome from a flash drive using "try
  before installation" mode, however, so I'm confident that it's not
  actually encryption related.

  I am *not* using any proprietary drivers (no nvidia, etc.).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adric  1574 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Apr 26 19:19:26 2016
  HibernationDevice: RESUME=UUID=74c52e77-74c8-49d1-843b-23584516bd07
  InstallationDate: Installed on 2016-04-26 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: ASUSTeK COMPUTER INC. N501VW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.206:bd02/03/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1062077] Re: [HP TouchSmart tm2-2010eg] Linux hangs with: "[drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting"

2016-06-07 Thread Christopher M. Penalver 
Samarjit Adhikari, 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/1062077

Title:
  [HP TouchSmart tm2-2010eg] Linux hangs with: "[drm:atom_op_jump]
  *ERROR* atombios stuck in loop for more than 5secs aborting"

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Symptom: Linux isn't displaying changes after switching to tty1 and back to 
Unity. Steps to reproduce:
  1. Starting up to Unity
  2. Switch to tty1 (Strg + Alt + F1)
  3. Switching back to Unity

  or resuming the system from suspend leads to the same isssue.This
  method isn't as reliable as the method stated above.

  What happens: The screen freezes. Magic Keys [Alt + Print + S/U/B] are
  working thou (so linux-kernel is responding?!) I can't switch to tty1
  either. The system becomes responding again after ~2min. Switching VTs
  is possible afterwards but leads to the same bug again.

  What is expected: Showing up a responding Unity.

  WORKAROUND: My radeon is switched off using:
  echo"OFF">/sys/kernel/debug/vgaswitcheroo/switch 
  By turning "ON" the graphics card the above stated problem doesn't appear.

  A kern.log:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1062077/+attachment/3374796/+files/kern.log

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-17-generic 3.5.0-17.26
  ProcVersionSignature: Ubuntu 3.5.0-17.26-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  octavian   2405 F pulseaudio
  Date: Fri Oct  5 09:07:44 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
  MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=2e9be59f-1f91-4313-bfac-3babbffc5c00 ro quiet splash pcie_aspm=force 
i915.i915_enable_rc6=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware1.94
  SourcePackage: linux
  UpgradeStatus: Upgraded to quantal on 2012-09-14 (20 days ago)
  dmi.bios.date: 07/30/2010
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.12
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1486
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 83.1A
  dmi.chassis.asset.tag: CNU0250216
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.12:bd07/30/2010:svnHewlett-Packard:pnHPTouchSmarttm2NotebookPC:pvr048920252A2000122:rvnHewlett-Packard:rn1486:rvr83.1A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP TouchSmart tm2 Notebook PC
  dmi.product.version: 048920252A2000122
  dmi.sys.vendor: Hewlett-Packard
  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  DistUpgraded: 2013-02-07 06:43:51,807 DEBUG enabling apt cron job
  DistroCodename: raring
  DistroRelease: Ubuntu 13.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.1.22, 3.5.0-23-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-4-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:1486]
   Advanced Micro Devices [AMD] nee ATI Manhattan [Mobility Radeon HD 5400 
Series] [1002:68e0] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2012-12-04 (64 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC
  MarkForUpload: True
  Package: xorg 1:7.7+1ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-4-generic 
root=UUID=b78f0013-4cb2-4ad2-9c13-9d884b091f3a ro
  ProcVersionSignature: Ubuntu 3.8.0-4.9-generic 3.8.0-rc6
  Tags:  raring running-unity ubuntu regression reproducible compiz-0.9
  Uname: Linux 3.8.0-4-generic x86_64
  UpgradeStatus: Upgraded to raring on 2013-02-07 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/30/2010
  dmi.bios.vendor: Insyde

[Kernel-packages] [Bug 1579282] Re: Remote Desktop error when connect to the Ubuntu LTS 16.04

2016-06-07 Thread Christopher M. Penalver 
Jason, I setup xrdp via:
https://help.ubuntu.com/community/xrdp

However, as xrdp as implemented doesn't actually contain any glue to connect 
the client to the x session, I use x11vnc as discussed in:
https://help.ubuntu.com/community/VNC/Servers

with a slight modification to the systemd ExecStart:
ExecStart=/usr/bin/x11vnc -auth guess -cursor_drag -forever -xkb -loop -repeat 
-rfbauth /home/username/.vnc/passwd -rfbport 5900 -shared

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

Title:
  Remote Desktop error when connect to the Ubuntu LTS 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Using the windows remote desktop to connect to the Ubuntu LTS 16.04,
  the session failed.

  The .xsession-errors log as followings,

  #cat .xsession-errors
  Xsession: X session started for  at Fri May  6 17:52:57 PDT 2016
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
    Major opcode of failed request:  109 (X_ChangeHosts)
    Value in failed request:  0x5
    Serial number of failed request:  6
    Current serial number in output stream:  8
  localuser:ubuntu being added to access control list
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
    Major opcode of failed request:  109 (X_ChangeHosts)
    Value in failed request:  0x5
    Serial number of failed request:  6
    Current serial number in output stream:  8
  /etc/xrdp/startwm.sh: 3: [: x: unexpected operator

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

  ##lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04 LTS
  Release:16.04
  Codename:   xenial
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=16c28cbc-e675-4e08-9672-32b766cdd90a
  InstallationDate: Installed on 2015-09-08 (241 days ago)
  InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  MachineType: HP ProLiant DL360 Gen9
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=1036285c-b89e-4d97-b5a5-199699b2651c ro
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-05 (1 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/03/2014
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd11/03/2014:svnHP:pnProLiantDL360Gen9:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL360 Gen9
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1581799] Re: radeon driver hangs : nothing else that static effect on display

2016-06-07 Thread Christopher M. Penalver 
magowiz, it wouldn't hurt to have a test of 15.10 with the radeon driver
to see if this is a regression.

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

Title:
  radeon driver hangs : nothing else that static effect on display

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  since upgrade from ubuntu 15.10 to 16.04 I was unable to use mine videocard 
due to drop support of fglrx driver (that was working) and due to radeon 
opensource driver not working with my VGA.

  Mine video card:
  $ lspci -nn | grep VGA
  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Sumo [Radeon HD 6410D] [1002:9645]

  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  I'll attach further files (dmesg.log , version.log, lspci-vnvn.log) .
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   magowiz4930 F...m pulseaudio
   /dev/snd/pcmC0D0p:   magowiz4930 F...m pulseaudio
   /dev/snd/controlC0:  magowiz4930 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=472405e9-ecbe-44ee-9931-9eedcc0a759a
  InstallationDate: Installed on 2012-01-03 (1615 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=acd61f09-2fc9-4a54-bf0b-23f0a297d2e4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-26 (40 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  _MarkForUpload: True
  dmi.bios.date: 12/09/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1003
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F1A55-M LE
  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.:bvr1003:bd12/09/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF1A55-MLE: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/1581799/+subscriptions

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

[Kernel-packages] [Bug 1535470] Re: Backlight brightness keys not working

2016-06-07 Thread Christopher M. Penalver 
dhenry, 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.

** Tags removed: needs-upstream-testing-4.6-rc1
** Tags added: needs-upstream-testing-4.7-rc2

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

Title:
  Backlight brightness keys not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Originally described in bug 1533221. This is a new bug to track this
  additional issue separately.

  The above bug has h/w info attached etc. This is a new skylake
  chipset.

  Backlight function keys are not working. I have tried various
  combinations of:

  acpi_osi=Linux acpi_backlight=native
  acpi_osi=Linux acpi_backlight=vendor
  acpi_osi=! acpi_backlight=vendor
  etc, etc

  with no luck.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian2218 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=df036c01-8f22-4d8f-ad55-6add4f99f5f4
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 5986:066d Acer, Inc 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65_P67RGRERA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-0-generic 
root=UUID=2077d068-d7ee-4407-89e1-7d2b884173de ro acpi_osi=Linux 
acpi_backlight=native drm.debug=14
  ProcVersionSignature: Ubuntu 4.4.0-0.12-generic 4.4.0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-0-generic N/A
   linux-backports-modules-4.4.0-0-generic  N/A
   linux-firmware   1.155
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.4.0-0-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.10
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_P67RGRERA
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.10:bd11/20/2015:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P65_P67RGRERA
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Kernel-packages] [Bug 1582858] Re: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled

2016-06-07 Thread Christopher M. Penalver 
Daniel, 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/1582858

Title:
  kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7
  if IOMMU is enabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a HP Proliant DL165 G7 I upgraded from 14.04.3 LTS to 16.04 LTS (I
  know, not supported).

  After reboot, the new kernel was loaded by GRUB, but failed to find
  the disks installed in the system (setup working for almost 2 years,
  standard HP setup with the SATA controller in AHCI mode and AHCI
  enabled during BIOS). It then dropped to a shell in initramfs, after
  hundreds (thousands?) of identical errors:

  [...] AMD-Vi: Event Logged [IO_PAGE_FAULT] device=xxx adress=yyy
  flags=0x...

  and the final error messages:

  ata3: softreset failed (1st FIS failed)
  ata4: softreset failed (1st FIS failed)
  ata3: limiting SATA link speed to 1.5 Gbps
  ata3: softreset failed (1st FIS failed)
  ata4: limiting SATA link speed to 1.5 Gbps
  ata4: softreset failed (1st FIS failed)
  ata3: reset failed, giving up
  ata4: reset failed, giving up

  The system disks are on ata1 and ata2, though.

  
  I tried booting the system from different other 16.04 boot media 
(ubuntu-16.04-server-amd64.iso, ubuntu-16.04-desktop-amd64.iso) into a rescue 
system. I also got the 
  [...] AMD-Vi: Event Logged ... messages. When the rescue shell was running, 
the system disks were also not detected, the installer I started as an 
experiment only offered the (USB disk) boot medium itself as installation 
target. The desktop installer and kernel then crashed with error messages about 
squashfs (sorry, didn't record those).

  Without any change, the same system boots without issues from a 14.04
  boot image, all disks present. Also, the 16.04 system boots fine if
  the old 3.13.0-86 kernel is selected in the GRUB menu.

  After some fiddling around, I turned off the IOMMU in the server's
  BIOS (under PCiExpress) - and all went back to normal, without any
  change on the installed system. Kernel 4.4.0-22-generic now boots just
  fine from the LVM-Root.

  So this is WORKSFORME now, but maybe somebody should look into it. I do 
believe that Proliants are quite common out there. If needed, I'll provide more 
info if possible - but currently I wouldn't know what.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 17 18:50 seq
   crw-rw 1 root audio 116, 33 May 17 18:50 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d46c7c15-9d36-4d87-930d-e43d447e8855
  InstallationDate: Installed on 2012-12-22 (1244 days ago)
  InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 
(20121017.2)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL165 G7
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/vg0-root ro net.ifnames=0 rootfstype=ext4
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2014-05-25 (725 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/27/2012
  dmi.bios.vendor: HP
  dmi.bios.version: O37
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrO37:bd07/27/2012:svnHP:pnProLiantDL165G7:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL165 G7
  dmi.sys.vendor: HP

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

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

<    1   2   3   >