[Kernel-packages] [Bug 1631714] [NEW] Cougar 200K keyboard not working properly with Gigabyte H97-HD3 motherboard

2016-10-09 Thread Denis Volkov 
Public bug reported:

the issue looks to be similar to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1446897

Ubuntu 16.04
Gigabyte H97-HD3
Cougar 200k

ALT, CTRL and SHIFT on both left and right and Windows Key returns keycode 50 
(keysym 0xffe1, Shift_L).
CAPS returns keycode 66 (keysym 0xffe3, Control_L). 


temporary resolved by

hg clone https://bitbucket.org/Swoogan/aziokbd
cd aziokbd
sudo ./install.sh

however, after the next reboot doesn't work again until you add
'usbhid.quirks=0x0c45:0x7603:0x4' to grub

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash
usbhid.quirks=0x0c45:0x7603:0x4"

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-38-generic 4.4.0-38.57
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  amdenis1518 F pulseaudio
 /dev/snd/controlC0:  amdenis1518 F pulseaudio
 /dev/snd/controlC1:  amdenis1518 F pulseaudio
CurrentDesktop: Unity
Date: Sun Oct  9 15:04:15 2016
HibernationDevice: RESUME=UUID=cd301db2-32c4-4a82-982c-7c5df848b04c
InstallationDate: Installed on 2016-10-08 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IwConfig:
 lono wireless extensions.
 
 enp3s0no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. H97-HD3
ProcFB:
 0 EFI VGA
 1 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=6611906d-258c-4ddd-9b16-7884ac082f78 ro quiet splash 
usbhid.quirks=0x0c45:0x7603:0x4 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-38-generic N/A
 linux-backports-modules-4.4.0-38-generic  N/A
 linux-firmware1.157.3
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F8
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H97-HD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF8:bd09/18/2015:svnGigabyteTechnologyCo.,Ltd.:pnH97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: H97-HD3
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug xenial

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

Title:
  Cougar 200K keyboard not working properly with Gigabyte H97-HD3
  motherboard

Status in linux package in Ubuntu:
  New

Bug description:
  the issue looks to be similar to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1446897

  Ubuntu 16.04
  Gigabyte H97-HD3
  Cougar 200k

  ALT, CTRL and SHIFT on both left and right and Windows Key returns keycode 50 
(keysym 0xffe1, Shift_L).
  CAPS returns keycode 66 (keysym 0xffe3, Control_L). 

  
  temporary resolved by

  hg clone https://bitbucket.org/Swoogan/aziokbd
  cd aziokbd
  sudo ./install.sh

  however, after the next reboot doesn't work again until you add
  'usbhid.quirks=0x0c45:0x7603:0x4' to grub

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash
  usbhid.quirks=0x0c45:0x7603:0x4"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  amdenis1518 F pulseaudio
   /dev/snd/controlC0:  amdenis1518 F pulseaudio
   /dev/snd/controlC1:  amdenis1518 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Oct  9 15:04:15 2016
  HibernationDevice: RESUME=UUID=cd301db2-32c4-4a82-982c-7c5df848b04c
  InstallationDate: Installed on 2016-10-08 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. H97-HD3
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=6611906d-258c-4ddd-9b16-7884ac082f78 ro quiet splash 
usbhid.quirks=0x0c45:0x7603:0x4 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A

[Kernel-packages] [Bug 1629197] Re: Suspend not working

2016-10-09 Thread Slither 
I've executed all the commands below and then attempted to create the
resume trace this command as per the instructions :

sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

As expected my system froze. Display stilled showed my X11 session with
browser and terminal open but the computer was completely unresponsive.
I tried pressing the power button yet still no response. The computer
was stuck in that limbo state again.

I had to press the physical restart button and boot into ubuntu again. I
then executed:

sudo su && dmesg > dmesg.cat

See attached file.


Instructions executed prior to sleep and dmesg commands above:


While booted into the latest non-daily mainline kernel, execute at a terminal:

sudo su
echo freezer > /sys/power/pm_test
exit

Please attach to your report the resume trace mentioned below.

While booted into the latest non-daily mainline kernel, execute at a
terminal:

sudo su
echo devices > /sys/power/pm_test
exit

Please attach to your report the resume trace mentioned below.

While booted into the latest non-daily mainline kernel, execute at a
terminal:

sudo su
echo platform > /sys/power/pm_test
exit

Please attach to your report the resume trace mentioned below.

While booted into the latest non-daily mainline kernel, execute at a
terminal:

sudo su
echo processors > /sys/power/pm_test
exit

Please attach to your report the resume trace mentioned below.

While booted into the latest non-daily mainline kernel, execute at a
terminal:

sudo su
echo core > /sys/power/pm_test
exit

Please attach to your report the resume trace mentioned below.

While booted into the latest non-daily mainline kernel, execute at a
terminal:

sudo su
echo none > /sys/power/pm_test
exit

Please attach to your report the resume trace mentioned below.

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629197/+attachment/4757920/+files/dmesg.txt

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

Title:
  Suspend not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm running a fresh installation of 16.04 running the latest updates.

  When I `pm-suspend` the computer remains powered on but is completely
  unresponsive. There is no signal going to my monitor and I can't enter
  a tty shell or ctrl+alt+del to restart. I'm forced to press the the
  physical reset button. This happens every time I perform a suspend.

  I can shutdown and reboot at the moment. I really wish DSDT loading
  was still available, I could have attempted to fix this myself with a
  patched bios (if a bung ACPI call is the culprit).

  Thanks in advance,

  Stephen

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Fri Sep 30 16:48:54 2016
  HibernationDevice: RESUME=UUID=94b7cd61-7e7a-41a7-a8ec-e3b9b7e2eb87
  InstallationDate: Installed on 2016-05-18 (134 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=48e60eed-d92a-4a36-86dd-0c839f9a63d0 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-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-I
  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:

[Kernel-packages] [Bug 1629197] Re: Suspend not working

2016-10-09 Thread Slither 
While booted into the latest non-daily mainline kernel, execute at a
terminal:

cat /proc/acpi/wakeup > wakeup

See attached file.

** Attachment added: "wakeup"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629197/+attachment/4757918/+files/wakeup

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

Title:
  Suspend not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm running a fresh installation of 16.04 running the latest updates.

  When I `pm-suspend` the computer remains powered on but is completely
  unresponsive. There is no signal going to my monitor and I can't enter
  a tty shell or ctrl+alt+del to restart. I'm forced to press the the
  physical reset button. This happens every time I perform a suspend.

  I can shutdown and reboot at the moment. I really wish DSDT loading
  was still available, I could have attempted to fix this myself with a
  patched bios (if a bung ACPI call is the culprit).

  Thanks in advance,

  Stephen

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Fri Sep 30 16:48:54 2016
  HibernationDevice: RESUME=UUID=94b7cd61-7e7a-41a7-a8ec-e3b9b7e2eb87
  InstallationDate: Installed on 2016-05-18 (134 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=48e60eed-d92a-4a36-86dd-0c839f9a63d0 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-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-I
  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.:bvr1001:bd02/01/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-I: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/1629197/+subscriptions

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

[Kernel-packages] [Bug 1629197] Re: Suspend not working

2016-10-09 Thread Slither 
In answer to the first 3 questions:

1. Which part of the process does the issue occur with, the suspend to
ram, or resuming from? Instantly after suspend from gui or terminal is
issued.

2. Please advise how you suspended specifically. For example:

Executing at a terminal pm-suspend
Clicking the word Suspend in the GUI.

3. Please advise how you resumed specifically. For example:

I used to be able to resume by either the power button or or wake on
usb via my MCE IR receiver.

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

Title:
  Suspend not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm running a fresh installation of 16.04 running the latest updates.

  When I `pm-suspend` the computer remains powered on but is completely
  unresponsive. There is no signal going to my monitor and I can't enter
  a tty shell or ctrl+alt+del to restart. I'm forced to press the the
  physical reset button. This happens every time I perform a suspend.

  I can shutdown and reboot at the moment. I really wish DSDT loading
  was still available, I could have attempted to fix this myself with a
  patched bios (if a bung ACPI call is the culprit).

  Thanks in advance,

  Stephen

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Fri Sep 30 16:48:54 2016
  HibernationDevice: RESUME=UUID=94b7cd61-7e7a-41a7-a8ec-e3b9b7e2eb87
  InstallationDate: Installed on 2016-05-18 (134 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=48e60eed-d92a-4a36-86dd-0c839f9a63d0 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-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-I
  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.:bvr1001:bd02/01/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-I: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/1629197/+subscriptions

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

[Kernel-packages] [Bug 1629197] Re: Suspend not working

2016-10-09 Thread Slither 
Please provide the output of the following terminal command:

cat /sys/kernel/debug/suspend_stats

See attached file

** Attachment added: "suspend_stats"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629197/+attachment/4757919/+files/suspend_stats

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

Title:
  Suspend not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm running a fresh installation of 16.04 running the latest updates.

  When I `pm-suspend` the computer remains powered on but is completely
  unresponsive. There is no signal going to my monitor and I can't enter
  a tty shell or ctrl+alt+del to restart. I'm forced to press the the
  physical reset button. This happens every time I perform a suspend.

  I can shutdown and reboot at the moment. I really wish DSDT loading
  was still available, I could have attempted to fix this myself with a
  patched bios (if a bung ACPI call is the culprit).

  Thanks in advance,

  Stephen

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Fri Sep 30 16:48:54 2016
  HibernationDevice: RESUME=UUID=94b7cd61-7e7a-41a7-a8ec-e3b9b7e2eb87
  InstallationDate: Installed on 2016-05-18 (134 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=48e60eed-d92a-4a36-86dd-0c839f9a63d0 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-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-I
  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.:bvr1001:bd02/01/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-I: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/1629197/+subscriptions

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

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

2016-10-09 Thread Brad Figg 
This change was made by a bot.

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

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

Title:
  Cougar 200K keyboard not working properly with Gigabyte H97-HD3
  motherboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  the issue looks to be similar to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1446897

  Ubuntu 16.04
  Gigabyte H97-HD3
  Cougar 200k

  ALT, CTRL and SHIFT on both left and right and Windows Key returns keycode 50 
(keysym 0xffe1, Shift_L).
  CAPS returns keycode 66 (keysym 0xffe3, Control_L). 

  
  temporary resolved by

  hg clone https://bitbucket.org/Swoogan/aziokbd
  cd aziokbd
  sudo ./install.sh

  however, after the next reboot doesn't work again until you add
  'usbhid.quirks=0x0c45:0x7603:0x4' to grub

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash
  usbhid.quirks=0x0c45:0x7603:0x4"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  amdenis1518 F pulseaudio
   /dev/snd/controlC0:  amdenis1518 F pulseaudio
   /dev/snd/controlC1:  amdenis1518 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Oct  9 15:04:15 2016
  HibernationDevice: RESUME=UUID=cd301db2-32c4-4a82-982c-7c5df848b04c
  InstallationDate: Installed on 2016-10-08 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. H97-HD3
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=6611906d-258c-4ddd-9b16-7884ac082f78 ro quiet splash 
usbhid.quirks=0x0c45:0x7603:0x4 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F8
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H97-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF8:bd09/18/2015:svnGigabyteTechnologyCo.,Ltd.:pnH97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: H97-HD3
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1629197] Re: Suspend not working

2016-10-09 Thread Christopher M. Penalver 
Slither, the article has been updated to better reflect what is
requested. To advise, one is to attach a resume trace after each of
those steps, not just run all the commands requested and then provide
one dmesg at the end.

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

Title:
  Suspend not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm running a fresh installation of 16.04 running the latest updates.

  When I `pm-suspend` the computer remains powered on but is completely
  unresponsive. There is no signal going to my monitor and I can't enter
  a tty shell or ctrl+alt+del to restart. I'm forced to press the the
  physical reset button. This happens every time I perform a suspend.

  I can shutdown and reboot at the moment. I really wish DSDT loading
  was still available, I could have attempted to fix this myself with a
  patched bios (if a bung ACPI call is the culprit).

  Thanks in advance,

  Stephen

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Fri Sep 30 16:48:54 2016
  HibernationDevice: RESUME=UUID=94b7cd61-7e7a-41a7-a8ec-e3b9b7e2eb87
  InstallationDate: Installed on 2016-05-18 (134 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=48e60eed-d92a-4a36-86dd-0c839f9a63d0 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-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-I
  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.:bvr1001:bd02/01/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-I: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/1629197/+subscriptions

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

[Kernel-packages] [Bug 1294087] Re: [LENOVO 20266] hibernate/resume failure

2016-10-09 Thread madbiologist 
Yuv - we don't want you to test the latest Trusty mainline kernel.  I'm
not sure there is even such a thing.  We want you to test the latest
mainline kernel, without any trusty/utopic suffix (currently 4.8.1).
This is because the most useful action is to test the most recent kernel
version.  However, you have different hardware than the original
reporter, so it is unlikely that you are experiencing the exact same
issue.  I would recommend that you run ubuntu-bug to file a new bug
report.

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

Title:
  [LENOVO 20266] hibernate/resume failure

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Lenovo Yoga 2 Pro does not come back from sleep.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-17-generic 3.13.0-17.37
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  Annotation: This occured during a previous hibernate and prevented it from 
resuming properly.
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeanmartina   2039 F pulseaudio
   /dev/snd/controlC0:  jeanmartina   2039 F pulseaudio
  Date: Tue Mar 18 08:59:28 2014
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  InstallationDate: Installed on 2014-03-12 (5 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140309)
  InterpreterPath: /usr/bin/python3.4
  MachineType: LENOVO 20266
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-17-generic.efi.signed 
root=UUID=edbaa033-c440-4e73-8460-2239177e36b4 ro 
resume=/dev/disk/by-uuid/edbaa033-c440-4e73-8460-2239177e36b4 quiet 
acpi_backlight=vendor splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-17-generic N/A
   linux-backports-modules-3.13.0-17-generic  N/A
   linux-firmware 1.126
  SourcePackage: linux
  Title: [LENOVO 20266] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1446897] Re: Cougar 200K keyboard not working properly with Gigabyte GA-970A-DS3 motherboard

2016-10-09 Thread Christopher M. Penalver 
Denis Volkov (paralloid), 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.

** Attachment removed: "hardinfo_report.html"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1446897/+attachment/4757852/+files/hardinfo_report.html

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

Title:
  Cougar 200K keyboard not working properly with Gigabyte GA-970A-DS3
  motherboard

Status in linux package in Ubuntu:
  Expired

Bug description:
  Keyboard working properly on Intel laptops  and during the boot
  sequence (ie I can use CTRL+ALT+DEL before linux boots).

  Once in linux ALT, CTRL and SHIFT on both left and right and Windows Key 
returns keycode 50 (keysym 0xffe1, Shift_L).
  CAPS returns  keycode 66 (keysym 0xffe3, Control_L).

  Tried various IOMMU combinations as the mobo has some issues with
  Linux and IOMMU.

  Collected logs are with IOMMU enabled in BIOS and 'iommu=allowed
  amd_iommu=on iommu=pt iommu=1' passed to grub.

  ---
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  marius  926 F pulseaudio
   /dev/snd/controlC0:  marius  926 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2014-11-27 (180 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic 
root=UUID=31a3dcd3-ac94-410f-a92f-f1042e507430 ro amd_iommu=on iommu=pt quiet 
splash nomdmonddf nomdmonisw crashkernel=384M-:128M
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-18-generic N/A
   linux-backports-modules-3.19.0-18-generic  N/A
   linux-firmware 1.143.1
  RfKill:

  Tags:  vivid
  Uname: Linux 3.19.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip docker fax fuse games libvirtd 
lpadmin mlocate netdev plugdev powerdev sambashare scanner sudo users video
  _MarkForUpload: True
  dmi.bios.date: 10/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FEg
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFEg:bd10/07/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1294087] Re: [LENOVO 20266] hibernate/resume failure

2016-10-09 Thread madbiologist 
Jean Martina - can you please update to the latest BIOS available from
http://support.lenovo.com/au/en/products/Laptops-and-netbooks/Yoga-
Series/Yoga-2-Pro-
Lenovo?tabName=Downloads=Mast:SubNav:Support:Drivers%20and%20Software|Drivers%20and%20Software=false
and let us know if the issue is fixed?

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

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

Title:
  [LENOVO 20266] hibernate/resume failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Lenovo Yoga 2 Pro does not come back from sleep.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-17-generic 3.13.0-17.37
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  Annotation: This occured during a previous hibernate and prevented it from 
resuming properly.
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeanmartina   2039 F pulseaudio
   /dev/snd/controlC0:  jeanmartina   2039 F pulseaudio
  Date: Tue Mar 18 08:59:28 2014
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  InstallationDate: Installed on 2014-03-12 (5 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140309)
  InterpreterPath: /usr/bin/python3.4
  MachineType: LENOVO 20266
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-17-generic.efi.signed 
root=UUID=edbaa033-c440-4e73-8460-2239177e36b4 ro 
resume=/dev/disk/by-uuid/edbaa033-c440-4e73-8460-2239177e36b4 quiet 
acpi_backlight=vendor splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-17-generic N/A
   linux-backports-modules-3.13.0-17-generic  N/A
   linux-firmware 1.126
  SourcePackage: linux
  Title: [LENOVO 20266] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1602371] Re: Touchpad incorrectly detected as PS/2 mouse in 'HP Pavillion 340G1' after Ubuntu 12.04 upgrade to 14.04.

2016-10-09 Thread Daniel Ojeda 
I get the same message when I boot with that 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/1602371

Title:
  Touchpad incorrectly detected as PS/2 mouse in 'HP Pavillion 340G1'
  after Ubuntu 12.04 upgrade to 14.04.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm currently using Linux 4.2.0-38-generic Kernel.

  
  I adjunct in a .txt the outputs for 
  -dmesg
  -cat /proc/bus/input/devices 

  Regards

  Daniel Ojeda
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  do 3758 F pulseaudio
   /dev/snd/controlC0:  do 3758 F pulseaudio
  CurrentDesktop: Unity
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-yuanli-precise-amd64-20131009-1
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=93204dde-91fd-41de-b63a-8c49d4903331
  InstallationDate: Installed on 2015-07-13 (365 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20131009-06:05
  MachineType: Hewlett-Packard HP 340 G1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-38-generic 
root=UUID=8fb79e40-a483-431f-ae1f-b6430988c9fd ro quiet splash i8042.reset 
i8042.nomux i8042.nopnp i8042.noloop vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-38.45~14.04.1-generic 4.2.8-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-38-generic N/A
   linux-backports-modules-4.2.0-38-generic  N/A
   linux-firmware1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 4.2.0-38-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-07-13 (364 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 06/12/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.12
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 21B7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 46.0B
  dmi.chassis.asset.tag: 5CG4471R2Q
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.12:bd06/12/2014:svnHewlett-Packard:pnHP340G1:pvr099810167:rvnHewlett-Packard:rn21B7:rvrKBCVersion46.0B:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 340 G1
  dmi.product.version: 099810167
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1434136] Re: HP Pavilion 13-b208tu fails to boot with F.26-F.34 BIOS, PSOD

2016-10-09 Thread Christopher M. Penalver 
** Summary changed:

- HP Pavilion 13-b208tu fails to boot with F.26 bios, PSOD
+ HP Pavilion 13-b208tu fails to boot with F.26-F.34 BIOS, PSOD

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

Title:
  HP Pavilion 13-b208tu fails to boot with F.26-F.34 BIOS, PSOD

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While trying to fix Bug #1432659, I updated the HP Pavilion 13-b208tu bios to 
the latest available on the HP website (F.26):
  
http://support.hp.com/us-en/drivers/selfservice/HP-Pavilion-13-b200-Notebook-PC-series/7527795/model/7597682

  After the update, the laptop no longer boots Ubuntu 14.10 or Ubuntu
  15.04 (Ubuntu 15.04 from the hard drive, Ubuntu 14.10 using a LiveCD).
  The grub menu is available and works, the kernel loads, the initrd
  step works, and then it hangs hard and requires power cycling.

  The required information for a kernel bug report can be found in Bug
  #1432659, from the original shipped F.23 bios. I obviously can't
  attach information with the F.26 bios loaded.

  I can confirm that the bios update worked, and I have repeated it
  twice. HP diagnostics give the system a green light, and I can boot to
  FreeDOS as normal. I'll leave the system unbootable with the F.26 bios
  for a while in case someone can help me diagnose further from grub.

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

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

[Kernel-packages] [Bug 1631678] Re: Build in display doesn't show a screen

2016-10-09 Thread Yoshiaki Ono 
apport information

** Tags added: apport-collected xenial

** Description changed:

  I'm using UX21A Asus Zenbook Prime.
  
  When I connected HDMI socket to an external display and turn on the
  laptop, Ubuntu didn't show build in display even it said display was
  recognized and activated. It happened on Ubuntu 16.04 and Linux Mint 18
  Mint even when they were started as Live USB booting.
  
  When I switched off the build in display and reactivate it through
  Display Setting GUI, it started showing. But with xrandr command, it
  didn't.
  
  I unplugged HDMI and turn on the laptop and plug HDMI again after
  confirmed the BIOS Logo, the problem didn't show up.
  
  The situation I confirmed on several environment were all the same.
  
  It suppose to be caused by a problem which the laptop considers the
  external display as primary one.
  
  So currently, I unplug the HDMI when I start it up.
  
  I also asked in askubuntu.com but it doesn't seem I could get the
  feedback. This is my first bug repport and please be kind.
  
  sudo lspci -vnvn > lspci-vnvn.log
  returns 
  Ubuntu 4.4.0-38.57-generic 4.4.19
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.1
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  zenbook1475 F pulseaudio
+ CurrentDesktop: X-Cinnamon
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=51f4543d-f960-4aea-8840-72631c112329
+ InstallationDate: Installed on 2016-10-05 (4 days ago)
+ InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64(20160426.1)
+ MachineType: ASUSTeK COMPUTER INC. UX21A
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=cce15b3a-8ba8-40d2-a621-c8b542bb3484 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-38-generic N/A
+  linux-backports-modules-4.4.0-38-generic  N/A
+  linux-firmware1.157.3
+ Tags:  xenial
+ Uname: Linux 4.4.0-38-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/14/2012
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: UX21A.216
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: UX21A
+ 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.:bvrUX21A.216:bd11/14/2012:svnASUSTeKCOMPUTERINC.:pnUX21A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX21A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
+ dmi.product.name: UX21A
+ dmi.product.version: 1.0
+ dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1631678/+attachment/4758084/+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/1631678

Title:
  Build in display doesn't show a screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using UX21A Asus Zenbook Prime.

  When I connected HDMI socket to an external display and turn on the
  laptop, Ubuntu didn't show build in display even it said display was
  recognized and activated. It happened on Ubuntu 16.04 and Linux Mint
  18 Mint even when they were started as Live USB booting.

  When I switched off the build in display and reactivate it through
  Display Setting GUI, it started showing. But with xrandr command, it
  didn't.

  I unplugged HDMI and turn on the laptop and plug HDMI again after
  confirmed the BIOS Logo, the problem didn't show up.

  The situation I confirmed on several environment were all the same.

  It suppose to be caused by a problem which the laptop considers the
  external display as primary one.

  So currently, I unplug the HDMI when I start it up.

  I also asked in askubuntu.com but it doesn't seem I could get the
  feedback. This is my first bug repport and please be kind.

  sudo lspci -vnvn > lspci-vnvn.log
  returns 
  Ubuntu 4.4.0-38.57-generic 4.4.19
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zenbook1475 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=51f4543d-f960-4aea-8840-72631c112329
  InstallationDate: Installed on 2016-10-05 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64(20160426.1)
  MachineType: ASUSTeK COMPUTER INC. UX21A
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed

[Kernel-packages] [Bug 1631678] ProcEnviron.txt

2016-10-09 Thread Yoshiaki Ono 
apport information

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

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

Title:
  Build in display doesn't show a screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using UX21A Asus Zenbook Prime.

  When I connected HDMI socket to an external display and turn on the
  laptop, Ubuntu didn't show build in display even it said display was
  recognized and activated. It happened on Ubuntu 16.04 and Linux Mint
  18 Mint even when they were started as Live USB booting.

  When I switched off the build in display and reactivate it through
  Display Setting GUI, it started showing. But with xrandr command, it
  didn't.

  I unplugged HDMI and turn on the laptop and plug HDMI again after
  confirmed the BIOS Logo, the problem didn't show up.

  The situation I confirmed on several environment were all the same.

  It suppose to be caused by a problem which the laptop considers the
  external display as primary one.

  So currently, I unplug the HDMI when I start it up.

  I also asked in askubuntu.com but it doesn't seem I could get the
  feedback. This is my first bug repport and please be kind.

  sudo lspci -vnvn > lspci-vnvn.log
  returns 
  Ubuntu 4.4.0-38.57-generic 4.4.19
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zenbook1475 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=51f4543d-f960-4aea-8840-72631c112329
  InstallationDate: Installed on 2016-10-05 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64(20160426.1)
  MachineType: ASUSTeK COMPUTER INC. UX21A
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=cce15b3a-8ba8-40d2-a621-c8b542bb3484 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-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/14/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX21A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX21A
  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.:bvrUX21A.216:bd11/14/2012:svnASUSTeKCOMPUTERINC.:pnUX21A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX21A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX21A
  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/1631678/+subscriptions

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

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

2016-10-09 Thread Yoshiaki Ono 
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1631678/+attachment/4758086/+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/1631678

Title:
  Build in display doesn't show a screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using UX21A Asus Zenbook Prime.

  When I connected HDMI socket to an external display and turn on the
  laptop, Ubuntu didn't show build in display even it said display was
  recognized and activated. It happened on Ubuntu 16.04 and Linux Mint
  18 Mint even when they were started as Live USB booting.

  When I switched off the build in display and reactivate it through
  Display Setting GUI, it started showing. But with xrandr command, it
  didn't.

  I unplugged HDMI and turn on the laptop and plug HDMI again after
  confirmed the BIOS Logo, the problem didn't show up.

  The situation I confirmed on several environment were all the same.

  It suppose to be caused by a problem which the laptop considers the
  external display as primary one.

  So currently, I unplug the HDMI when I start it up.

  I also asked in askubuntu.com but it doesn't seem I could get the
  feedback. This is my first bug repport and please be kind.

  sudo lspci -vnvn > lspci-vnvn.log
  returns 
  Ubuntu 4.4.0-38.57-generic 4.4.19
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zenbook1475 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=51f4543d-f960-4aea-8840-72631c112329
  InstallationDate: Installed on 2016-10-05 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64(20160426.1)
  MachineType: ASUSTeK COMPUTER INC. UX21A
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=cce15b3a-8ba8-40d2-a621-c8b542bb3484 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-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/14/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX21A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX21A
  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.:bvrUX21A.216:bd11/14/2012:svnASUSTeKCOMPUTERINC.:pnUX21A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX21A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX21A
  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/1631678/+subscriptions

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

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

2016-10-09 Thread Yoshiaki Ono 
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1631678/+attachment/4758090/+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/1631678

Title:
  Build in display doesn't show a screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using UX21A Asus Zenbook Prime.

  When I connected HDMI socket to an external display and turn on the
  laptop, Ubuntu didn't show build in display even it said display was
  recognized and activated. It happened on Ubuntu 16.04 and Linux Mint
  18 Mint even when they were started as Live USB booting.

  When I switched off the build in display and reactivate it through
  Display Setting GUI, it started showing. But with xrandr command, it
  didn't.

  I unplugged HDMI and turn on the laptop and plug HDMI again after
  confirmed the BIOS Logo, the problem didn't show up.

  The situation I confirmed on several environment were all the same.

  It suppose to be caused by a problem which the laptop considers the
  external display as primary one.

  So currently, I unplug the HDMI when I start it up.

  I also asked in askubuntu.com but it doesn't seem I could get the
  feedback. This is my first bug repport and please be kind.

  sudo lspci -vnvn > lspci-vnvn.log
  returns 
  Ubuntu 4.4.0-38.57-generic 4.4.19
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zenbook1475 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=51f4543d-f960-4aea-8840-72631c112329
  InstallationDate: Installed on 2016-10-05 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64(20160426.1)
  MachineType: ASUSTeK COMPUTER INC. UX21A
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=cce15b3a-8ba8-40d2-a621-c8b542bb3484 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-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/14/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX21A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX21A
  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.:bvrUX21A.216:bd11/14/2012:svnASUSTeKCOMPUTERINC.:pnUX21A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX21A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX21A
  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/1631678/+subscriptions

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

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

2016-10-09 Thread Yoshiaki Ono 
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1631678/+attachment/4758089/+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/1631678

Title:
  Build in display doesn't show a screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using UX21A Asus Zenbook Prime.

  When I connected HDMI socket to an external display and turn on the
  laptop, Ubuntu didn't show build in display even it said display was
  recognized and activated. It happened on Ubuntu 16.04 and Linux Mint
  18 Mint even when they were started as Live USB booting.

  When I switched off the build in display and reactivate it through
  Display Setting GUI, it started showing. But with xrandr command, it
  didn't.

  I unplugged HDMI and turn on the laptop and plug HDMI again after
  confirmed the BIOS Logo, the problem didn't show up.

  The situation I confirmed on several environment were all the same.

  It suppose to be caused by a problem which the laptop considers the
  external display as primary one.

  So currently, I unplug the HDMI when I start it up.

  I also asked in askubuntu.com but it doesn't seem I could get the
  feedback. This is my first bug repport and please be kind.

  sudo lspci -vnvn > lspci-vnvn.log
  returns 
  Ubuntu 4.4.0-38.57-generic 4.4.19
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zenbook1475 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=51f4543d-f960-4aea-8840-72631c112329
  InstallationDate: Installed on 2016-10-05 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64(20160426.1)
  MachineType: ASUSTeK COMPUTER INC. UX21A
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=cce15b3a-8ba8-40d2-a621-c8b542bb3484 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-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/14/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX21A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX21A
  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.:bvrUX21A.216:bd11/14/2012:svnASUSTeKCOMPUTERINC.:pnUX21A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX21A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX21A
  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/1631678/+subscriptions

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

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

2016-10-09 Thread Yoshiaki Ono 
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1631678/+attachment/4758091/+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/1631678

Title:
  Build in display doesn't show a screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using UX21A Asus Zenbook Prime.

  When I connected HDMI socket to an external display and turn on the
  laptop, Ubuntu didn't show build in display even it said display was
  recognized and activated. It happened on Ubuntu 16.04 and Linux Mint
  18 Mint even when they were started as Live USB booting.

  When I switched off the build in display and reactivate it through
  Display Setting GUI, it started showing. But with xrandr command, it
  didn't.

  I unplugged HDMI and turn on the laptop and plug HDMI again after
  confirmed the BIOS Logo, the problem didn't show up.

  The situation I confirmed on several environment were all the same.

  It suppose to be caused by a problem which the laptop considers the
  external display as primary one.

  So currently, I unplug the HDMI when I start it up.

  I also asked in askubuntu.com but it doesn't seem I could get the
  feedback. This is my first bug repport and please be kind.

  sudo lspci -vnvn > lspci-vnvn.log
  returns 
  Ubuntu 4.4.0-38.57-generic 4.4.19
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zenbook1475 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=51f4543d-f960-4aea-8840-72631c112329
  InstallationDate: Installed on 2016-10-05 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64(20160426.1)
  MachineType: ASUSTeK COMPUTER INC. UX21A
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=cce15b3a-8ba8-40d2-a621-c8b542bb3484 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-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/14/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX21A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX21A
  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.:bvrUX21A.216:bd11/14/2012:svnASUSTeKCOMPUTERINC.:pnUX21A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX21A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX21A
  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/1631678/+subscriptions

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

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

2016-10-09 Thread Yoshiaki Ono 
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1631678/+attachment/4758085/+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/1631678

Title:
  Build in display doesn't show a screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using UX21A Asus Zenbook Prime.

  When I connected HDMI socket to an external display and turn on the
  laptop, Ubuntu didn't show build in display even it said display was
  recognized and activated. It happened on Ubuntu 16.04 and Linux Mint
  18 Mint even when they were started as Live USB booting.

  When I switched off the build in display and reactivate it through
  Display Setting GUI, it started showing. But with xrandr command, it
  didn't.

  I unplugged HDMI and turn on the laptop and plug HDMI again after
  confirmed the BIOS Logo, the problem didn't show up.

  The situation I confirmed on several environment were all the same.

  It suppose to be caused by a problem which the laptop considers the
  external display as primary one.

  So currently, I unplug the HDMI when I start it up.

  I also asked in askubuntu.com but it doesn't seem I could get the
  feedback. This is my first bug repport and please be kind.

  sudo lspci -vnvn > lspci-vnvn.log
  returns 
  Ubuntu 4.4.0-38.57-generic 4.4.19
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zenbook1475 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=51f4543d-f960-4aea-8840-72631c112329
  InstallationDate: Installed on 2016-10-05 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64(20160426.1)
  MachineType: ASUSTeK COMPUTER INC. UX21A
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=cce15b3a-8ba8-40d2-a621-c8b542bb3484 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-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/14/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX21A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX21A
  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.:bvrUX21A.216:bd11/14/2012:svnASUSTeKCOMPUTERINC.:pnUX21A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX21A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX21A
  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/1631678/+subscriptions

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

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

2016-10-09 Thread Yoshiaki Ono 
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1631678/+attachment/4758093/+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/1631678

Title:
  Build in display doesn't show a screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using UX21A Asus Zenbook Prime.

  When I connected HDMI socket to an external display and turn on the
  laptop, Ubuntu didn't show build in display even it said display was
  recognized and activated. It happened on Ubuntu 16.04 and Linux Mint
  18 Mint even when they were started as Live USB booting.

  When I switched off the build in display and reactivate it through
  Display Setting GUI, it started showing. But with xrandr command, it
  didn't.

  I unplugged HDMI and turn on the laptop and plug HDMI again after
  confirmed the BIOS Logo, the problem didn't show up.

  The situation I confirmed on several environment were all the same.

  It suppose to be caused by a problem which the laptop considers the
  external display as primary one.

  So currently, I unplug the HDMI when I start it up.

  I also asked in askubuntu.com but it doesn't seem I could get the
  feedback. This is my first bug repport and please be kind.

  sudo lspci -vnvn > lspci-vnvn.log
  returns 
  Ubuntu 4.4.0-38.57-generic 4.4.19
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zenbook1475 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=51f4543d-f960-4aea-8840-72631c112329
  InstallationDate: Installed on 2016-10-05 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64(20160426.1)
  MachineType: ASUSTeK COMPUTER INC. UX21A
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=cce15b3a-8ba8-40d2-a621-c8b542bb3484 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-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/14/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX21A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX21A
  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.:bvrUX21A.216:bd11/14/2012:svnASUSTeKCOMPUTERINC.:pnUX21A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX21A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX21A
  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/1631678/+subscriptions

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

[Kernel-packages] [Bug 1631678] ProcModules.txt

2016-10-09 Thread Yoshiaki Ono 
apport information

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

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

Title:
  Build in display doesn't show a screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using UX21A Asus Zenbook Prime.

  When I connected HDMI socket to an external display and turn on the
  laptop, Ubuntu didn't show build in display even it said display was
  recognized and activated. It happened on Ubuntu 16.04 and Linux Mint
  18 Mint even when they were started as Live USB booting.

  When I switched off the build in display and reactivate it through
  Display Setting GUI, it started showing. But with xrandr command, it
  didn't.

  I unplugged HDMI and turn on the laptop and plug HDMI again after
  confirmed the BIOS Logo, the problem didn't show up.

  The situation I confirmed on several environment were all the same.

  It suppose to be caused by a problem which the laptop considers the
  external display as primary one.

  So currently, I unplug the HDMI when I start it up.

  I also asked in askubuntu.com but it doesn't seem I could get the
  feedback. This is my first bug repport and please be kind.

  sudo lspci -vnvn > lspci-vnvn.log
  returns 
  Ubuntu 4.4.0-38.57-generic 4.4.19
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zenbook1475 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=51f4543d-f960-4aea-8840-72631c112329
  InstallationDate: Installed on 2016-10-05 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64(20160426.1)
  MachineType: ASUSTeK COMPUTER INC. UX21A
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=cce15b3a-8ba8-40d2-a621-c8b542bb3484 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-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/14/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX21A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX21A
  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.:bvrUX21A.216:bd11/14/2012:svnASUSTeKCOMPUTERINC.:pnUX21A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX21A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX21A
  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/1631678/+subscriptions

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

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

2016-10-09 Thread Yoshiaki Ono 
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1631678/+attachment/4758087/+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/1631678

Title:
  Build in display doesn't show a screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using UX21A Asus Zenbook Prime.

  When I connected HDMI socket to an external display and turn on the
  laptop, Ubuntu didn't show build in display even it said display was
  recognized and activated. It happened on Ubuntu 16.04 and Linux Mint
  18 Mint even when they were started as Live USB booting.

  When I switched off the build in display and reactivate it through
  Display Setting GUI, it started showing. But with xrandr command, it
  didn't.

  I unplugged HDMI and turn on the laptop and plug HDMI again after
  confirmed the BIOS Logo, the problem didn't show up.

  The situation I confirmed on several environment were all the same.

  It suppose to be caused by a problem which the laptop considers the
  external display as primary one.

  So currently, I unplug the HDMI when I start it up.

  I also asked in askubuntu.com but it doesn't seem I could get the
  feedback. This is my first bug repport and please be kind.

  sudo lspci -vnvn > lspci-vnvn.log
  returns 
  Ubuntu 4.4.0-38.57-generic 4.4.19
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zenbook1475 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=51f4543d-f960-4aea-8840-72631c112329
  InstallationDate: Installed on 2016-10-05 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64(20160426.1)
  MachineType: ASUSTeK COMPUTER INC. UX21A
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=cce15b3a-8ba8-40d2-a621-c8b542bb3484 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-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/14/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX21A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX21A
  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.:bvrUX21A.216:bd11/14/2012:svnASUSTeKCOMPUTERINC.:pnUX21A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX21A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX21A
  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/1631678/+subscriptions

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

[Kernel-packages] [Bug 1631678] JournalErrors.txt

2016-10-09 Thread Yoshiaki Ono 
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1631678/+attachment/4758088/+files/JournalErrors.txt

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

Title:
  Build in display doesn't show a screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using UX21A Asus Zenbook Prime.

  When I connected HDMI socket to an external display and turn on the
  laptop, Ubuntu didn't show build in display even it said display was
  recognized and activated. It happened on Ubuntu 16.04 and Linux Mint
  18 Mint even when they were started as Live USB booting.

  When I switched off the build in display and reactivate it through
  Display Setting GUI, it started showing. But with xrandr command, it
  didn't.

  I unplugged HDMI and turn on the laptop and plug HDMI again after
  confirmed the BIOS Logo, the problem didn't show up.

  The situation I confirmed on several environment were all the same.

  It suppose to be caused by a problem which the laptop considers the
  external display as primary one.

  So currently, I unplug the HDMI when I start it up.

  I also asked in askubuntu.com but it doesn't seem I could get the
  feedback. This is my first bug repport and please be kind.

  sudo lspci -vnvn > lspci-vnvn.log
  returns 
  Ubuntu 4.4.0-38.57-generic 4.4.19
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zenbook1475 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=51f4543d-f960-4aea-8840-72631c112329
  InstallationDate: Installed on 2016-10-05 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64(20160426.1)
  MachineType: ASUSTeK COMPUTER INC. UX21A
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=cce15b3a-8ba8-40d2-a621-c8b542bb3484 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-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/14/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX21A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX21A
  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.:bvrUX21A.216:bd11/14/2012:svnASUSTeKCOMPUTERINC.:pnUX21A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX21A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX21A
  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/1631678/+subscriptions

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

[Kernel-packages] [Bug 1626332] Re: Ubuntu MATE 16.10 fails to boot with linux-image-4.8.0-11-generic kernel on PowerMac G5 7, 3

2016-10-09 Thread ernsteiswuerfel 
With todays daily live and "linux-image-4.8.0-21-generic
4.8.0-21.23"-kernel my G5 boots fine again into the desktop (as long as
boot-paramenter radeon.agpmode=-1 is used)!

Will mark this bug as fixed.

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

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

Title:
  Ubuntu MATE 16.10 fails to boot with linux-image-4.8.0-11-generic
  kernel on PowerMac G5 7,3

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Tried to boot todays daily Yakkety iso on my PowerMac G5 7,3 which failed:
  "Unable to find a medium containing a live file system" (see photo). Same 
problem also for Lubuntu's daily Yakkety iso.

  The same iso boots however on my PowerBook G4 5,6 + 5,8.

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

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

[Kernel-packages] [Bug 1628384] Re: f.lux not working on 4.4.0-38

2016-10-09 Thread rob 
Just tried doing a 'sudo apt-get upgrade' command, and the entries
contain:

linux-headers-4.4.0-36-generic
linux-image-4.4.0-36-generic
linux-image-extra-4.4.0-36-generic

The original log above has "linux-image-4.4.0-38-generic 4.4.0-38.57,"
so this must be the prior Kernel where f.lux was working, right?

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

Title:
  f.lux not working on 4.4.0-38

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  f.lux does not change screen brightness

  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rob1275 F pulseaudio
   /dev/snd/controlC0:  rob1275 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep 28 02:24:37 2016
  HibernationDevice: RESUME=UUID=a8eba1de-75f8-4e4b-b7b2-4ee1e7e91229
  InstallationDate: Installed on 2016-07-09 (81 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: ZOTAC ZBOX-MI520-X
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=eaa5f618-d44d-44db-9359-617ce3b92a86 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B239P202
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-MI520-X
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB239P202:bd08/13/2015:svnZOTAC:pnZBOX-MI520-X:pvrXX:rvnZOTAC:rnZBOX-MI520-X:rvrXX:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: ZBOX-MI520-X
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

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

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

[Kernel-packages] [Bug 1628384] Re: f.lux not working on 4.4.0-38

2016-10-09 Thread rob 
One more, sorry. The comment above appeared when doing 'sudo apt-get
upgrade,' and appeared below, "The following packages were automatically
installed and are no longer required:"

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

Title:
  f.lux not working on 4.4.0-38

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  f.lux does not change screen brightness

  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rob1275 F pulseaudio
   /dev/snd/controlC0:  rob1275 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep 28 02:24:37 2016
  HibernationDevice: RESUME=UUID=a8eba1de-75f8-4e4b-b7b2-4ee1e7e91229
  InstallationDate: Installed on 2016-07-09 (81 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: ZOTAC ZBOX-MI520-X
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=eaa5f618-d44d-44db-9359-617ce3b92a86 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B239P202
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-MI520-X
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB239P202:bd08/13/2015:svnZOTAC:pnZBOX-MI520-X:pvrXX:rvnZOTAC:rnZBOX-MI520-X:rvrXX:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: ZBOX-MI520-X
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

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

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

[Kernel-packages] [Bug 1617686] Re: Kernel 4.4.0-34 caused Redshift/Flux/brightness-controller etc. to stop working

2016-10-09 Thread JI Xiang 
Actually, kernel 4.4.0-41-generic from xenial-proposed works for me if
I'm using the NVIDIA graphics card, but doesn't work on Intel integrated
graphics card.

4.4.19 works on both.

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

Title:
  Kernel 4.4.0-34 caused Redshift/Flux/brightness-controller etc. to
  stop working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  As per reported by several users, such as in
  https://ubuntuforums.org/showthread.php?t=298, apps that control
  screen gamma, such as Redshift/Flux/brightness-controller, stopped
  working under the newest kernel 4.4.0-34 in Ubuntu 16.04 LTS, and
  we're not sure what caused the issue.

  Those apps are still working well on external monitors. It's just the
  internal monitor that is not responsive. Any setting just simply has
  no effect.

  It seems that all the users are using Skylake-based laptop.

  In my case, my laptop is on Skylake and GTX980M.

  Links for the individual apps mentioned above:
  - Redshift http://jonls.dk/redshift/
  - Flux https://justgetflux.com/linux.html
  - brightness-controller 
https://apps.ubuntu.com/cat/applications/brightness-controller/

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jx 4045 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=66785c85-3633-4f60-b15d-718b7b14873e
  InstallationDate: Installed on 2016-04-25 (125 days ago)
  InstallationMedia: It
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 046d:c07e Logitech, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hasee Computer CP65R
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=d940d1fe-4c2c-4de3-b82d-108083812e0e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  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.05:bd09/18/2015:svnHaseeComputer:pnCP65R:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: CP65R
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Hasee Computer

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

-- 
Mailing list: https://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 1609074] Re: Screen flicker on 16.04

2016-10-09 Thread Piotr Wieczorek 
Hi,
Apparently I was too optimistic about the issue.
I've tested both the kernel from http://kernel.ubuntu.com/~kernel-ppa/
mainline/drm-intel-nightly/current/
 and the latest mainstream 4.8.1 and unfortunately the issue is still
present in both of them

2016-09-01 18:17 GMT+02:00 Christopher M. Penalver <
christopher.m.penal...@gmail.com>:

> Piotr Wieczorek, to see if this is addressed upstream, could you please
> test http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-
> nightly/current/ and advise to the results?
>
> ** Tags removed: kernel-bug-exists-upstream-4.7 needs-upstream-testing
> ** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.
> 8-rc4
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1609074
>
> Title:
>   Screen flicker on 16.04
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   The computer running Ubuntu is being used as HTPC connected via HDMI to
> a screen projector.
>   After upgrading to 16.04, it's unusable under production kernel.
>   The screen starts flickering after a while (it's easily triggered by
> fast scrolling e.g. terminal's window). The whole screen get's filled with
> a noise, and then the projector gets disconnected for a while.
>
>   The computer runs fine on an older kernel (4.2.0-35), it's still
>   broken on the mainline kernel 4.7.0.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: linux-image-4.4.0-31-generic 4.4.0-31.50
>   ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
>   Uname: Linux 4.4.0-31-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2.1
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  pwiecz 3977 F pulseaudio
>/dev/snd/controlC1:  pwiecz 3977 F pulseaudio
>   CurrentDesktop: Unity
>   Date: Tue Aug  2 19:40:29 2016
>   InstallationDate: Installed on 2014-02-02 (912 days ago)
>   InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
> (20131016.1)
>   MachineType: Gigabyte Technology Co., Ltd. H87N-WIFI
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic
> root=UUID=98e2c9a3-1a1a-4d21-b370-79d0cde7b5f2 ro quiet splash
> vt.handoff=7
>   RelatedPackageVersions:
>linux-restricted-modules-4.4.0-31-generic N/A
>linux-backports-modules-4.4.0-31-generic  N/A
>linux-firmware1.157.2
>   SourcePackage: linux
>   UpgradeStatus: Upgraded to xenial on 2016-04-27 (97 days ago)
>   dmi.bios.date: 08/18/2015
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: F9
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: H87N-WIFI
>   dmi.board.vendor: Gigabyte Technology Co., Ltd.
>   dmi.board.version: x.x
>   dmi.chassis.asset.tag: To Be Filled By O.E.M.
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
>   dmi.chassis.version: To Be Filled By O.E.M.
>   dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd08/18/2015:
> svnGigabyteTechnologyCo.,Ltd.:pnH87N-WIFI:pvrTobefilledbyO.
> E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH87N-WIFI:rvrx.x:
> cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
>   dmi.product.name: H87N-WIFI
>   dmi.product.version: To be filled by O.E.M.
>   dmi.sys.vendor: Gigabyte Technology Co., Ltd.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1609074/+subscriptions
>

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

Title:
  Screen flicker on 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The computer running Ubuntu is being used as HTPC connected via HDMI to a 
screen projector.
  After upgrading to 16.04, it's unusable under production kernel.
  The screen starts flickering after a while (it's easily triggered by fast 
scrolling e.g. terminal's window). The whole screen get's filled with a noise, 
and then the projector gets disconnected for a while.

  The computer runs fine on an older kernel (4.2.0-35), it's still
  broken on the mainline kernel 4.7.0.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pwiecz 3977 F pulseaudio
   /dev/snd/controlC1:  pwiecz 3977 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug  2 19:40:29 2016
  InstallationDate: Installed on 2014-02-02 (912 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Gigabyte Technology Co., Ltd. H87N-WIFI
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine:

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

2016-10-09 Thread Brad Figg 
This change was made by a bot.

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

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

Title:
  Touchpad not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade from kubuntu 14.04 to 16.04 the touchpad soon stopped
  working (meaning it even worked for some hours put then stopped). Now
  it is not detected anymore. It isn't listed when typing cat
  /proc/bus/input/devices.

  sudo apt-get install xserver-xorg-input-synaptics + reboot didn't
  help.

  Following this page:
  https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo I
  assume it's related to the linux kernel and I updated my kernel to
  4.5.0-040500-generic but that didn't change anything neither.

  Laptop model: Dell XPS 13 Ubuntu edition (Intel® Core™ i7-4500U (4 Mo de 
mémoire cache, jusqu‘à 3 GHz))
  Touchpad manufacturer: Synaptics

  attached: /dmesg (I could add only one attachment!?)

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

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

[Kernel-packages] [Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

2016-10-09 Thread Eric Desrochers 
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Invalid
Status in linux-lts-xenial source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux-lts-xenial source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  Fix Released
Status in linux-lts-xenial source package in Yakkety:
  Invalid

Bug description:
  [Impact]

  At boot-time, the kernel will panic somewhere in
  'blk_mq_register_disk', a snippet of the track is below, and full
  panic dump is attached. The panic dump was collected via serial
  console, as the kernel panics so early that we cannot kdump it.

  [ 2.650512] [] blk_mq_register_disk+0xa6/0x160
  [ 2.656675] [] blk_register_queue+0xb4/0x160
  [ 2.662661] [] add_disk+0x1ce/0x490
  [ 2.667869] [] loop_add+0x1f0/0x270

  [Test Case]

  At boot-time, the kernel will panic somewhere in
  'blk_mq_register_disk', a snippet of the track is below, and full
  panic dump is attached.

  [Regression Potential]

   * Fix implemented upstream starting with v4.6-rc1

   * The fix is fairly straightfoward given the stack trace.

   * The fix is hard to verify, but user "Proton" was able to confirmed
  that upstream mainline 4.6-rc1 solve the situation and that the test
  kernel I have provided including the fix solves this particular
  problem as well.

  Confirmation by Proton :
  
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1572630/comments/23

  [Other Info]

   * https://lkml.org/lkml/2016/3/16/40
   * 
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e0e827b9
   * 
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=897bb0c7

  [Original Description]
  We discovered a pretty serious regression introduced in 4.4.0-18.

  At boot-time, the kernel will panic somewhere in
  'blk_mq_register_disk', a snippet of the track is below, and full
  panic dump is attached. The panic dump was collected via serial
  console, as the kernel panics so early that we cannot kdump it.

  [2.650512]  [] blk_mq_register_disk+0xa6/0x160
  [2.656675]  [] blk_register_queue+0xb4/0x160
  [2.662661]  [] add_disk+0x1ce/0x490
  [2.667869]  [] loop_add+0x1f0/0x270

  This seems somewhat similar to https://lkml.org/lkml/2016/3/16/40, but
  the trace is not identical.

  We discovered this issue when we were experimenting with linux-
  generic-lts-xenial from trusty-updates on a 14.04 installation. When
  we installed it, 4.4.0-15 was the current package, and it worked fine
  and provided a large amount of improvements for us. Background
  security updates installed 4.4.0-18, and this updated and grub and
  became the default kernel. On a reboot, the node panics about 2
  seconds in, resulting in a machine in a dead state. We were able to
  boot a rescue image and roll bac kto 4.4.0-15, which works nicely. We
  currently have pinning on 4.4.0-15 to prevent this problem from coming
  back, but would prefer to see the problem fixed.

  I'll attach lspci, lshw, and dmidecode for our hardware as well, but
  this is happening on pretty vanilla supermicro nodes. We are able to
  consistently reproduce it on our hardware. It is not reproducible in
  EC2, only on metal.

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

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

[Kernel-packages] [Bug 1629880] Re: Ubuntu won't launch after the Ubuntu, with Linux 4.4.0-39 generic update

2016-10-09 Thread Juhani Korhonen 
@jsalisbury Exactly.

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

Title:
  Ubuntu won't launch after the Ubuntu, with Linux 4.4.0-39 generic
  update

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

Bug description:
  I am running Linux Ubuntu 16.04 LTS, and I've discussed in a thread at
  'Ask Ubuntu: System update almost broke the system' about the Kernel
  Bug — as suggested by a local user boddhi.zazen — that I experienced
  as I was running my system updates. The problem occurs with "Ubuntu,
  with Linux 4.4.0-39 generic", although I am still able to access
  Ubuntu with the older "Ubuntu, with Linux 4.4.0-38 generic" via
  "+Advanced options for Ubuntu".

  Here's what happened:

  1. I first ran the upgrade procedures through terminal as usual: sudo apt-get 
update, sudo apt-get upgrade, sudo apt-get autoremove, and sudo apt-get 
autoremove
  2. However, I was told that "4 not upgraded", so I decided to run Software 
Updater as well, and there was indeed updates available concerning "Ubuntu 
base". I installed those successfully, and decided to proceed with restart my 
system.

  After the restart, my system doesn't start though. Instead, I receive
  the following error message:

  <-- THE BEGINNING, NOT PART OF THE ERROR MESSAGE -->
  [ 1.452270] genirq: Flags mismatch irq 0. 0080 (nvme0q0) vs. 00015a00 
(timer)
  [ 1.452551] iounmap: bad address c90001b88000
  Scanning for Btrfs filesystems
  Gave up waiting for root device. Common problems:
   - Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait for the right device?)
- Check root= (did the system wait for the right device?)
   - Missing modules (cat /proc/modules; ls /dev)
  ALERT! UUID=a5ccaf22-ffde-44c2-8c59-84a851f9fd90 does not exist. Dropping to 
shell!

  BusyBox v1.222.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs)
  <-- THE END, NOT PART OF THE ERROR MESSAGE -->

  I was able to recover my system through the "+Advanced options for
  Ubuntu", which I opened after. There I had total of nine choices,
  three options for each version. I first tried the "recovery version"
  of the latest one, but it didn't work. After that, I tried the
  "generic version" of the second latest, and — thank God — that one
  managed to recover my system! I believe the package is called linux-
  image-4.4.0-39-generic ("Ubuntu, with Linux 4.4.0-38 generic" in the
  menu")

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.16
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  Date: Mon Oct  3 16:19:33 2016
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:

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

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

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

2016-10-09 Thread Yoshiaki Ono 
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1631678/+attachment/4758097/+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/1631678

Title:
  Build in display doesn't show a screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using UX21A Asus Zenbook Prime.

  When I connected HDMI socket to an external display and turn on the
  laptop, Ubuntu didn't show build in display even it said display was
  recognized and activated. It happened on Ubuntu 16.04 and Linux Mint
  18 Mint even when they were started as Live USB booting.

  When I switched off the build in display and reactivate it through
  Display Setting GUI, it started showing. But with xrandr command, it
  didn't.

  I unplugged HDMI and turn on the laptop and plug HDMI again after
  confirmed the BIOS Logo, the problem didn't show up.

  The situation I confirmed on several environment were all the same.

  It suppose to be caused by a problem which the laptop considers the
  external display as primary one.

  So currently, I unplug the HDMI when I start it up.

  I also asked in askubuntu.com but it doesn't seem I could get the
  feedback. This is my first bug repport and please be kind.

  sudo lspci -vnvn > lspci-vnvn.log
  returns 
  Ubuntu 4.4.0-38.57-generic 4.4.19
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zenbook1475 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=51f4543d-f960-4aea-8840-72631c112329
  InstallationDate: Installed on 2016-10-05 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64(20160426.1)
  MachineType: ASUSTeK COMPUTER INC. UX21A
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=cce15b3a-8ba8-40d2-a621-c8b542bb3484 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-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/14/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX21A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX21A
  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.:bvrUX21A.216:bd11/14/2012:svnASUSTeKCOMPUTERINC.:pnUX21A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX21A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX21A
  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/1631678/+subscriptions

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

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

2016-10-09 Thread Yoshiaki Ono 
apport information

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

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

Title:
  Build in display doesn't show a screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using UX21A Asus Zenbook Prime.

  When I connected HDMI socket to an external display and turn on the
  laptop, Ubuntu didn't show build in display even it said display was
  recognized and activated. It happened on Ubuntu 16.04 and Linux Mint
  18 Mint even when they were started as Live USB booting.

  When I switched off the build in display and reactivate it through
  Display Setting GUI, it started showing. But with xrandr command, it
  didn't.

  I unplugged HDMI and turn on the laptop and plug HDMI again after
  confirmed the BIOS Logo, the problem didn't show up.

  The situation I confirmed on several environment were all the same.

  It suppose to be caused by a problem which the laptop considers the
  external display as primary one.

  So currently, I unplug the HDMI when I start it up.

  I also asked in askubuntu.com but it doesn't seem I could get the
  feedback. This is my first bug repport and please be kind.

  sudo lspci -vnvn > lspci-vnvn.log
  returns 
  Ubuntu 4.4.0-38.57-generic 4.4.19
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zenbook1475 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=51f4543d-f960-4aea-8840-72631c112329
  InstallationDate: Installed on 2016-10-05 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64(20160426.1)
  MachineType: ASUSTeK COMPUTER INC. UX21A
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=cce15b3a-8ba8-40d2-a621-c8b542bb3484 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-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/14/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX21A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX21A
  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.:bvrUX21A.216:bd11/14/2012:svnASUSTeKCOMPUTERINC.:pnUX21A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX21A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX21A
  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/1631678/+subscriptions

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

[Kernel-packages] [Bug 1631753] Re: Touchpad not detected

2016-10-09 Thread Nils 
** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1631753/+attachment/4758123/+files/lspci-vnvn.log

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

Title:
  Touchpad not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade from kubuntu 14.04 to 16.04 the touchpad soon stopped
  working (meaning it even worked for some hours put then stopped). Now
  it is not detected anymore. It isn't listed when typing cat
  /proc/bus/input/devices.

  sudo apt-get install xserver-xorg-input-synaptics + reboot didn't
  help.

  Following this page:
  https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo I
  assume it's related to the linux kernel and I updated my kernel to
  4.5.0-040500-generic but that didn't change anything neither.

  Laptop model: Dell XPS 13 Ubuntu edition (Intel® Core™ i7-4500U (4 Mo de 
mémoire cache, jusqu‘à 3 GHz))
  Touchpad manufacturer: Synaptics

  attached: /dmesg (I could add only one attachment!?)

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

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

[Kernel-packages] [Bug 1631753] Re: Touchpad not detected

2016-10-09 Thread Nils 
** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1631753/+attachment/4758124/+files/dmesg

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

Title:
  Touchpad not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade from kubuntu 14.04 to 16.04 the touchpad soon stopped
  working (meaning it even worked for some hours put then stopped). Now
  it is not detected anymore. It isn't listed when typing cat
  /proc/bus/input/devices.

  sudo apt-get install xserver-xorg-input-synaptics + reboot didn't
  help.

  Following this page:
  https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo I
  assume it's related to the linux kernel and I updated my kernel to
  4.5.0-040500-generic but that didn't change anything neither.

  Laptop model: Dell XPS 13 Ubuntu edition (Intel® Core™ i7-4500U (4 Mo de 
mémoire cache, jusqu‘à 3 GHz))
  Touchpad manufacturer: Synaptics

  attached: /dmesg (I could add only one attachment!?)

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

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

[Kernel-packages] [Bug 1631753] Re: Touchpad not detected

2016-10-09 Thread Nils 
** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1631753/+attachment/4758125/+files/Xorg.0.log

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

Title:
  Touchpad not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade from kubuntu 14.04 to 16.04 the touchpad soon stopped
  working (meaning it even worked for some hours put then stopped). Now
  it is not detected anymore. It isn't listed when typing cat
  /proc/bus/input/devices.

  sudo apt-get install xserver-xorg-input-synaptics + reboot didn't
  help.

  Following this page:
  https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo I
  assume it's related to the linux kernel and I updated my kernel to
  4.5.0-040500-generic but that didn't change anything neither.

  Laptop model: Dell XPS 13 Ubuntu edition (Intel® Core™ i7-4500U (4 Mo de 
mémoire cache, jusqu‘à 3 GHz))
  Touchpad manufacturer: Synaptics

  attached: /dmesg (I could add only one attachment!?)

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

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

[Kernel-packages] [Bug 1631678] RfKill.txt

2016-10-09 Thread Yoshiaki Ono 
apport information

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

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

Title:
  Build in display doesn't show a screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using UX21A Asus Zenbook Prime.

  When I connected HDMI socket to an external display and turn on the
  laptop, Ubuntu didn't show build in display even it said display was
  recognized and activated. It happened on Ubuntu 16.04 and Linux Mint
  18 Mint even when they were started as Live USB booting.

  When I switched off the build in display and reactivate it through
  Display Setting GUI, it started showing. But with xrandr command, it
  didn't.

  I unplugged HDMI and turn on the laptop and plug HDMI again after
  confirmed the BIOS Logo, the problem didn't show up.

  The situation I confirmed on several environment were all the same.

  It suppose to be caused by a problem which the laptop considers the
  external display as primary one.

  So currently, I unplug the HDMI when I start it up.

  I also asked in askubuntu.com but it doesn't seem I could get the
  feedback. This is my first bug repport and please be kind.

  sudo lspci -vnvn > lspci-vnvn.log
  returns 
  Ubuntu 4.4.0-38.57-generic 4.4.19
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zenbook1475 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=51f4543d-f960-4aea-8840-72631c112329
  InstallationDate: Installed on 2016-10-05 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64(20160426.1)
  MachineType: ASUSTeK COMPUTER INC. UX21A
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=cce15b3a-8ba8-40d2-a621-c8b542bb3484 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-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/14/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX21A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX21A
  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.:bvrUX21A.216:bd11/14/2012:svnASUSTeKCOMPUTERINC.:pnUX21A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX21A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX21A
  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/1631678/+subscriptions

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

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

2016-10-09 Thread Yoshiaki Ono 
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1631678/+attachment/4758095/+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/1631678

Title:
  Build in display doesn't show a screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using UX21A Asus Zenbook Prime.

  When I connected HDMI socket to an external display and turn on the
  laptop, Ubuntu didn't show build in display even it said display was
  recognized and activated. It happened on Ubuntu 16.04 and Linux Mint
  18 Mint even when they were started as Live USB booting.

  When I switched off the build in display and reactivate it through
  Display Setting GUI, it started showing. But with xrandr command, it
  didn't.

  I unplugged HDMI and turn on the laptop and plug HDMI again after
  confirmed the BIOS Logo, the problem didn't show up.

  The situation I confirmed on several environment were all the same.

  It suppose to be caused by a problem which the laptop considers the
  external display as primary one.

  So currently, I unplug the HDMI when I start it up.

  I also asked in askubuntu.com but it doesn't seem I could get the
  feedback. This is my first bug repport and please be kind.

  sudo lspci -vnvn > lspci-vnvn.log
  returns 
  Ubuntu 4.4.0-38.57-generic 4.4.19
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zenbook1475 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=51f4543d-f960-4aea-8840-72631c112329
  InstallationDate: Installed on 2016-10-05 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64(20160426.1)
  MachineType: ASUSTeK COMPUTER INC. UX21A
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=cce15b3a-8ba8-40d2-a621-c8b542bb3484 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-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/14/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX21A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX21A
  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.:bvrUX21A.216:bd11/14/2012:svnASUSTeKCOMPUTERINC.:pnUX21A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX21A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX21A
  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/1631678/+subscriptions

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

[Kernel-packages] [Bug 1434136] Re: HP Pavilion 13-b208tu fails to boot with F.26 bios, PSOD

2016-10-09 Thread Stuart Bishop 
** Tags removed: bios-outdated-f.34

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

Title:
  HP Pavilion 13-b208tu fails to boot with F.26 bios, PSOD

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While trying to fix Bug #1432659, I updated the HP Pavilion 13-b208tu bios to 
the latest available on the HP website (F.26):
  
http://support.hp.com/us-en/drivers/selfservice/HP-Pavilion-13-b200-Notebook-PC-series/7527795/model/7597682

  After the update, the laptop no longer boots Ubuntu 14.10 or Ubuntu
  15.04 (Ubuntu 15.04 from the hard drive, Ubuntu 14.10 using a LiveCD).
  The grub menu is available and works, the kernel loads, the initrd
  step works, and then it hangs hard and requires power cycling.

  The required information for a kernel bug report can be found in Bug
  #1432659, from the original shipped F.23 bios. I obviously can't
  attach information with the F.26 bios loaded.

  I can confirm that the bios update worked, and I have repeated it
  twice. HP diagnostics give the system a green light, and I can boot to
  FreeDOS as normal. I'll leave the system unbootable with the F.26 bios
  for a while in case someone can help me diagnose further from grub.

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

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

[Kernel-packages] [Bug 1631753] Re: Touchpad not detected

2016-10-09 Thread Nils 
** Attachment added: "devices"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1631753/+attachment/4758126/+files/devices

** Description changed:

- After upgrade from kubuntu 14.04 to 16.04 the touchpad soon stopped working 
(meaning it even worked for some hours put then stopped). Now it is not 
detected anymore. It isn't listed when typing cat /proc/bus/input/devices. 
- Following this page: 
https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo I assume it's 
related to the linux kernel and I updated my kernel to 4.5.0-040500-generic but 
that didn't change anything. 
-  
+ After upgrade from kubuntu 14.04 to 16.04 the touchpad soon stopped
+ working (meaning it even worked for some hours put then stopped). Now it
+ is not detected anymore. It isn't listed when typing cat
+ /proc/bus/input/devices.
+ 
+ sudo apt-get install xserver-xorg-input-synaptics + reboot didn't help.
+ 
+ Following this page:
+ https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo I assume
+ it's related to the linux kernel and I updated my kernel to
+ 4.5.0-040500-generic but that didn't change anything neither.
+ 
  Laptop model: Dell XPS 13 Ubuntu edition (Intel® Core™ i7-4500U (4 Mo de 
mémoire cache, jusqu‘à 3 GHz))
  Touchpad manufacturer: Synaptics
  
  attached: /dmesg (I could add only one attachment!?)

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

Title:
  Touchpad not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade from kubuntu 14.04 to 16.04 the touchpad soon stopped
  working (meaning it even worked for some hours put then stopped). Now
  it is not detected anymore. It isn't listed when typing cat
  /proc/bus/input/devices.

  sudo apt-get install xserver-xorg-input-synaptics + reboot didn't
  help.

  Following this page:
  https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo I
  assume it's related to the linux kernel and I updated my kernel to
  4.5.0-040500-generic but that didn't change anything neither.

  Laptop model: Dell XPS 13 Ubuntu edition (Intel® Core™ i7-4500U (4 Mo de 
mémoire cache, jusqu‘à 3 GHz))
  Touchpad manufacturer: Synaptics

  attached: /dmesg (I could add only one attachment!?)

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

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

[Kernel-packages] [Bug 1631753] [NEW] Touchpad not detected

2016-10-09 Thread Nils 
Public bug reported:

After upgrade from kubuntu 14.04 to 16.04 the touchpad soon stopped
working (meaning it even worked for some hours put then stopped). Now it
is not detected anymore. It isn't listed when typing cat
/proc/bus/input/devices.

sudo apt-get install xserver-xorg-input-synaptics + reboot didn't help.

Following this page:
https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo I assume
it's related to the linux kernel and I updated my kernel to
4.5.0-040500-generic but that didn't change anything neither.

Laptop model: Dell XPS 13 Ubuntu edition (Intel® Core™ i7-4500U (4 Mo de 
mémoire cache, jusqu‘à 3 GHz))
Touchpad manufacturer: Synaptics

attached: /dmesg (I could add only one attachment!?)

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1631753

Title:
  Touchpad not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade from kubuntu 14.04 to 16.04 the touchpad soon stopped
  working (meaning it even worked for some hours put then stopped). Now
  it is not detected anymore. It isn't listed when typing cat
  /proc/bus/input/devices.

  sudo apt-get install xserver-xorg-input-synaptics + reboot didn't
  help.

  Following this page:
  https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo I
  assume it's related to the linux kernel and I updated my kernel to
  4.5.0-040500-generic but that didn't change anything neither.

  Laptop model: Dell XPS 13 Ubuntu edition (Intel® Core™ i7-4500U (4 Mo de 
mémoire cache, jusqu‘à 3 GHz))
  Touchpad manufacturer: Synaptics

  attached: /dmesg (I could add only one attachment!?)

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

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

[Kernel-packages] [Bug 1628204] onza (amd64) - tests ran: 1, failed: 0

2016-10-09 Thread Brad Figg 
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-41.61/onza__4.4.0-41.61__2016-10-09_00-33-00/results-index.html

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

Title:
  linux: 4.4.0-41.61 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1628204/+subscriptions

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

[Kernel-packages] [Bug 1628204] onza (amd64) - tests ran: 1, failed: 0

2016-10-09 Thread Brad Figg 
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-41.61/onza__4.4.0-41.61__2016-10-09_00-33-00/results-index.html

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

Title:
  linux: 4.4.0-41.61 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1628204/+subscriptions

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

[Kernel-packages] [Bug 1434136] Re: HP Pavilion 13-b208tu fails to boot with F.26 bios, PSOD

2016-10-09 Thread Stuart Bishop 
Sorry, I don't get far enough to get any more debug information. If I
boot in recovery mode, the machine locks completely after displaying
'Loading initial ramdisk ...'. If I follow
https://wiki.ubuntu.com/DebuggingKernelBoot I don't even get that, just
a hung machine with a totally blank screen.

With the options from comment #4 I get the same screen shot as in
comment #6, except of course the kernel level is now 4.4.0-38-generic

I've also had no luck booting the yaketty daily. Same lockup.

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

Title:
  HP Pavilion 13-b208tu fails to boot with F.26 bios, PSOD

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While trying to fix Bug #1432659, I updated the HP Pavilion 13-b208tu bios to 
the latest available on the HP website (F.26):
  
http://support.hp.com/us-en/drivers/selfservice/HP-Pavilion-13-b200-Notebook-PC-series/7527795/model/7597682

  After the update, the laptop no longer boots Ubuntu 14.10 or Ubuntu
  15.04 (Ubuntu 15.04 from the hard drive, Ubuntu 14.10 using a LiveCD).
  The grub menu is available and works, the kernel loads, the initrd
  step works, and then it hangs hard and requires power cycling.

  The required information for a kernel bug report can be found in Bug
  #1432659, from the original shipped F.23 bios. I obviously can't
  attach information with the F.26 bios loaded.

  I can confirm that the bios update worked, and I have repeated it
  twice. HP diagnostics give the system a green light, and I can boot to
  FreeDOS as normal. I'll leave the system unbootable with the F.26 bios
  for a while in case someone can help me diagnose further from grub.

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

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

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

2016-10-09 Thread Albert 
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1631803/+attachment/4758428/+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/1631803

Title:
   ath9k driver randomly disconnects and can only reconnect by reloading
  the module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is the exact same bug described in Bug #407040 and Bug #404433, I
  need to reopen this as it was never fixed. I look as though network
  card is not able to reset and is causing random disconnects and
  causing the wlan interface to become unavailable, to a point where I
  need to restart my netbook to get access to the interface again. DMESG
  output:

  [  400.285672] ath: phy0: Chip reset failed
  [  400.285688] ath: phy0: Unable to reset channel, reset status -22
  [  400.285771] ath: phy0: Unable to set channel
  [  400.288009] ath: phy0: RX failed to go idle in 10 ms RXSM=0x
  [  400.288009] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x 
AR_DIAG_SW=0x DMADBG_7=0x

  
  I am running:
  Linux albert-1001PXD 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:41:41 UTC 
2016 i686 i686 i686 GNU/Linux

  
  The previous bug reports expired and I haven't found a fix online.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert 1962 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e8a3a41-aeda-4584-87a9-c9f2bffeed85
  InstallationDate: Installed on 2014-04-23 (900 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  MachineType: ASUSTeK Computer INC. 1001PXD
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=39e08d55-8a43-457f-9d95-04d0dfab085d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic i686
  UpgradeStatus: Upgraded to xenial on 2016-10-09 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1001PXD
  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.:bvr0302:bd09/20/2010:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1001PXD
  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/1631803/+subscriptions

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

[Kernel-packages] [Bug 1631803] JournalErrors.txt

2016-10-09 Thread Albert 
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1631803/+attachment/4758430/+files/JournalErrors.txt

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

Title:
   ath9k driver randomly disconnects and can only reconnect by reloading
  the module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is the exact same bug described in Bug #407040 and Bug #404433, I
  need to reopen this as it was never fixed. I look as though network
  card is not able to reset and is causing random disconnects and
  causing the wlan interface to become unavailable, to a point where I
  need to restart my netbook to get access to the interface again. DMESG
  output:

  [  400.285672] ath: phy0: Chip reset failed
  [  400.285688] ath: phy0: Unable to reset channel, reset status -22
  [  400.285771] ath: phy0: Unable to set channel
  [  400.288009] ath: phy0: RX failed to go idle in 10 ms RXSM=0x
  [  400.288009] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x 
AR_DIAG_SW=0x DMADBG_7=0x

  
  I am running:
  Linux albert-1001PXD 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:41:41 UTC 
2016 i686 i686 i686 GNU/Linux

  
  The previous bug reports expired and I haven't found a fix online.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert 1962 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e8a3a41-aeda-4584-87a9-c9f2bffeed85
  InstallationDate: Installed on 2014-04-23 (900 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  MachineType: ASUSTeK Computer INC. 1001PXD
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=39e08d55-8a43-457f-9d95-04d0dfab085d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic i686
  UpgradeStatus: Upgraded to xenial on 2016-10-09 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1001PXD
  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.:bvr0302:bd09/20/2010:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1001PXD
  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/1631803/+subscriptions

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

[Kernel-packages] [Bug 1631803] ProcModules.txt

2016-10-09 Thread Albert 
apport information

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

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

Title:
   ath9k driver randomly disconnects and can only reconnect by reloading
  the module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is the exact same bug described in Bug #407040 and Bug #404433, I
  need to reopen this as it was never fixed. I look as though network
  card is not able to reset and is causing random disconnects and
  causing the wlan interface to become unavailable, to a point where I
  need to restart my netbook to get access to the interface again. DMESG
  output:

  [  400.285672] ath: phy0: Chip reset failed
  [  400.285688] ath: phy0: Unable to reset channel, reset status -22
  [  400.285771] ath: phy0: Unable to set channel
  [  400.288009] ath: phy0: RX failed to go idle in 10 ms RXSM=0x
  [  400.288009] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x 
AR_DIAG_SW=0x DMADBG_7=0x

  
  I am running:
  Linux albert-1001PXD 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:41:41 UTC 
2016 i686 i686 i686 GNU/Linux

  
  The previous bug reports expired and I haven't found a fix online.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert 1962 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e8a3a41-aeda-4584-87a9-c9f2bffeed85
  InstallationDate: Installed on 2014-04-23 (900 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  MachineType: ASUSTeK Computer INC. 1001PXD
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=39e08d55-8a43-457f-9d95-04d0dfab085d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic i686
  UpgradeStatus: Upgraded to xenial on 2016-10-09 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1001PXD
  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.:bvr0302:bd09/20/2010:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1001PXD
  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/1631803/+subscriptions

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

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

2016-10-09 Thread Albert 
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1631803/+attachment/4758429/+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/1631803

Title:
   ath9k driver randomly disconnects and can only reconnect by reloading
  the module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is the exact same bug described in Bug #407040 and Bug #404433, I
  need to reopen this as it was never fixed. I look as though network
  card is not able to reset and is causing random disconnects and
  causing the wlan interface to become unavailable, to a point where I
  need to restart my netbook to get access to the interface again. DMESG
  output:

  [  400.285672] ath: phy0: Chip reset failed
  [  400.285688] ath: phy0: Unable to reset channel, reset status -22
  [  400.285771] ath: phy0: Unable to set channel
  [  400.288009] ath: phy0: RX failed to go idle in 10 ms RXSM=0x
  [  400.288009] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x 
AR_DIAG_SW=0x DMADBG_7=0x

  
  I am running:
  Linux albert-1001PXD 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:41:41 UTC 
2016 i686 i686 i686 GNU/Linux

  
  The previous bug reports expired and I haven't found a fix online.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert 1962 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e8a3a41-aeda-4584-87a9-c9f2bffeed85
  InstallationDate: Installed on 2014-04-23 (900 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  MachineType: ASUSTeK Computer INC. 1001PXD
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=39e08d55-8a43-457f-9d95-04d0dfab085d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic i686
  UpgradeStatus: Upgraded to xenial on 2016-10-09 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1001PXD
  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.:bvr0302:bd09/20/2010:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1001PXD
  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/1631803/+subscriptions

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

[Kernel-packages] [Bug 1631803] ProcEnviron.txt

2016-10-09 Thread Albert 
apport information

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

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

Title:
   ath9k driver randomly disconnects and can only reconnect by reloading
  the module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is the exact same bug described in Bug #407040 and Bug #404433, I
  need to reopen this as it was never fixed. I look as though network
  card is not able to reset and is causing random disconnects and
  causing the wlan interface to become unavailable, to a point where I
  need to restart my netbook to get access to the interface again. DMESG
  output:

  [  400.285672] ath: phy0: Chip reset failed
  [  400.285688] ath: phy0: Unable to reset channel, reset status -22
  [  400.285771] ath: phy0: Unable to set channel
  [  400.288009] ath: phy0: RX failed to go idle in 10 ms RXSM=0x
  [  400.288009] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x 
AR_DIAG_SW=0x DMADBG_7=0x

  
  I am running:
  Linux albert-1001PXD 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:41:41 UTC 
2016 i686 i686 i686 GNU/Linux

  
  The previous bug reports expired and I haven't found a fix online.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert 1962 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e8a3a41-aeda-4584-87a9-c9f2bffeed85
  InstallationDate: Installed on 2014-04-23 (900 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  MachineType: ASUSTeK Computer INC. 1001PXD
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=39e08d55-8a43-457f-9d95-04d0dfab085d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic i686
  UpgradeStatus: Upgraded to xenial on 2016-10-09 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1001PXD
  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.:bvr0302:bd09/20/2010:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1001PXD
  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/1631803/+subscriptions

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

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

2016-10-09 Thread Albert 
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1631803/+attachment/4758439/+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/1631803

Title:
   ath9k driver randomly disconnects and can only reconnect by reloading
  the module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is the exact same bug described in Bug #407040 and Bug #404433, I
  need to reopen this as it was never fixed. I look as though network
  card is not able to reset and is causing random disconnects and
  causing the wlan interface to become unavailable, to a point where I
  need to restart my netbook to get access to the interface again. DMESG
  output:

  [  400.285672] ath: phy0: Chip reset failed
  [  400.285688] ath: phy0: Unable to reset channel, reset status -22
  [  400.285771] ath: phy0: Unable to set channel
  [  400.288009] ath: phy0: RX failed to go idle in 10 ms RXSM=0x
  [  400.288009] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x 
AR_DIAG_SW=0x DMADBG_7=0x

  
  I am running:
  Linux albert-1001PXD 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:41:41 UTC 
2016 i686 i686 i686 GNU/Linux

  
  The previous bug reports expired and I haven't found a fix online.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert 1962 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e8a3a41-aeda-4584-87a9-c9f2bffeed85
  InstallationDate: Installed on 2014-04-23 (900 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  MachineType: ASUSTeK Computer INC. 1001PXD
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=39e08d55-8a43-457f-9d95-04d0dfab085d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic i686
  UpgradeStatus: Upgraded to xenial on 2016-10-09 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1001PXD
  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.:bvr0302:bd09/20/2010:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1001PXD
  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/1631803/+subscriptions

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

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

2016-10-09 Thread Albert 
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1631803/+attachment/4758433/+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/1631803

Title:
   ath9k driver randomly disconnects and can only reconnect by reloading
  the module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is the exact same bug described in Bug #407040 and Bug #404433, I
  need to reopen this as it was never fixed. I look as though network
  card is not able to reset and is causing random disconnects and
  causing the wlan interface to become unavailable, to a point where I
  need to restart my netbook to get access to the interface again. DMESG
  output:

  [  400.285672] ath: phy0: Chip reset failed
  [  400.285688] ath: phy0: Unable to reset channel, reset status -22
  [  400.285771] ath: phy0: Unable to set channel
  [  400.288009] ath: phy0: RX failed to go idle in 10 ms RXSM=0x
  [  400.288009] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x 
AR_DIAG_SW=0x DMADBG_7=0x

  
  I am running:
  Linux albert-1001PXD 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:41:41 UTC 
2016 i686 i686 i686 GNU/Linux

  
  The previous bug reports expired and I haven't found a fix online.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert 1962 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e8a3a41-aeda-4584-87a9-c9f2bffeed85
  InstallationDate: Installed on 2014-04-23 (900 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  MachineType: ASUSTeK Computer INC. 1001PXD
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=39e08d55-8a43-457f-9d95-04d0dfab085d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic i686
  UpgradeStatus: Upgraded to xenial on 2016-10-09 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1001PXD
  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.:bvr0302:bd09/20/2010:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1001PXD
  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/1631803/+subscriptions

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

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

2016-10-09 Thread Albert 
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1631803/+attachment/4758435/+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/1631803

Title:
   ath9k driver randomly disconnects and can only reconnect by reloading
  the module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is the exact same bug described in Bug #407040 and Bug #404433, I
  need to reopen this as it was never fixed. I look as though network
  card is not able to reset and is causing random disconnects and
  causing the wlan interface to become unavailable, to a point where I
  need to restart my netbook to get access to the interface again. DMESG
  output:

  [  400.285672] ath: phy0: Chip reset failed
  [  400.285688] ath: phy0: Unable to reset channel, reset status -22
  [  400.285771] ath: phy0: Unable to set channel
  [  400.288009] ath: phy0: RX failed to go idle in 10 ms RXSM=0x
  [  400.288009] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x 
AR_DIAG_SW=0x DMADBG_7=0x

  
  I am running:
  Linux albert-1001PXD 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:41:41 UTC 
2016 i686 i686 i686 GNU/Linux

  
  The previous bug reports expired and I haven't found a fix online.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert 1962 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e8a3a41-aeda-4584-87a9-c9f2bffeed85
  InstallationDate: Installed on 2014-04-23 (900 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  MachineType: ASUSTeK Computer INC. 1001PXD
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=39e08d55-8a43-457f-9d95-04d0dfab085d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic i686
  UpgradeStatus: Upgraded to xenial on 2016-10-09 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1001PXD
  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.:bvr0302:bd09/20/2010:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1001PXD
  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/1631803/+subscriptions

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

[Kernel-packages] [Bug 1631803] Re: ath9k driver randomly disconnects and can only reconnect by reloading the module

2016-10-09 Thread Albert 
apport information

** Tags added: apport-collected xenial

** Description changed:

  This is the exact same bug described in Bug #407040 and Bug #404433, I
  need to reopen this as it was never fixed. I look as though network card
  is not able to reset and is causing random disconnects and causing the
  wlan interface to become unavailable, to a point where I need to restart
  my netbook to get access to the interface again. DMESG output:
  
  [  400.285672] ath: phy0: Chip reset failed
  [  400.285688] ath: phy0: Unable to reset channel, reset status -22
  [  400.285771] ath: phy0: Unable to set channel
  [  400.288009] ath: phy0: RX failed to go idle in 10 ms RXSM=0x
  [  400.288009] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x 
AR_DIAG_SW=0x DMADBG_7=0x
  
  
  I am running:
  Linux albert-1001PXD 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:41:41 UTC 
2016 i686 i686 i686 GNU/Linux
  
  
  The previous bug reports expired and I haven't found a fix online.
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.1
+ Architecture: i386
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  albert 1962 F pulseaudio
+ CurrentDesktop: LXDE
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=9e8a3a41-aeda-4584-87a9-c9f2bffeed85
+ InstallationDate: Installed on 2014-04-23 (900 days ago)
+ InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
+ MachineType: ASUSTeK Computer INC. 1001PXD
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=39e08d55-8a43-457f-9d95-04d0dfab085d ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-38-generic N/A
+  linux-backports-modules-4.4.0-38-generic  N/A
+  linux-firmware1.157.3
+ Tags:  xenial
+ Uname: Linux 4.4.0-38-generic i686
+ UpgradeStatus: Upgraded to xenial on 2016-10-09 (0 days ago)
+ UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 09/20/2010
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 0302
+ dmi.board.asset.tag: To Be Filled By O.E.M.
+ dmi.board.name: 1001PXD
+ 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.:bvr0302:bd09/20/2010:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
+ dmi.product.name: 1001PXD
+ dmi.product.version: x.x
+ dmi.sys.vendor: ASUSTeK Computer INC.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1631803/+attachment/4758426/+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/1631803

Title:
   ath9k driver randomly disconnects and can only reconnect by reloading
  the module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is the exact same bug described in Bug #407040 and Bug #404433, I
  need to reopen this as it was never fixed. I look as though network
  card is not able to reset and is causing random disconnects and
  causing the wlan interface to become unavailable, to a point where I
  need to restart my netbook to get access to the interface again. DMESG
  output:

  [  400.285672] ath: phy0: Chip reset failed
  [  400.285688] ath: phy0: Unable to reset channel, reset status -22
  [  400.285771] ath: phy0: Unable to set channel
  [  400.288009] ath: phy0: RX failed to go idle in 10 ms RXSM=0x
  [  400.288009] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x 
AR_DIAG_SW=0x DMADBG_7=0x

  
  I am running:
  Linux albert-1001PXD 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:41:41 UTC 
2016 i686 i686 i686 GNU/Linux

  
  The previous bug reports expired and I haven't found a fix online.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert 1962 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e8a3a41-aeda-4584-87a9-c9f2bffeed85
  InstallationDate: Installed on 2014-04-23 (900 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  MachineType: ASUSTeK Computer INC. 1001PXD
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=39e08d55-8a43-457f-9d95-04d0dfab085d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A

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

2016-10-09 Thread Albert 
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1631803/+attachment/4758432/+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/1631803

Title:
   ath9k driver randomly disconnects and can only reconnect by reloading
  the module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is the exact same bug described in Bug #407040 and Bug #404433, I
  need to reopen this as it was never fixed. I look as though network
  card is not able to reset and is causing random disconnects and
  causing the wlan interface to become unavailable, to a point where I
  need to restart my netbook to get access to the interface again. DMESG
  output:

  [  400.285672] ath: phy0: Chip reset failed
  [  400.285688] ath: phy0: Unable to reset channel, reset status -22
  [  400.285771] ath: phy0: Unable to set channel
  [  400.288009] ath: phy0: RX failed to go idle in 10 ms RXSM=0x
  [  400.288009] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x 
AR_DIAG_SW=0x DMADBG_7=0x

  
  I am running:
  Linux albert-1001PXD 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:41:41 UTC 
2016 i686 i686 i686 GNU/Linux

  
  The previous bug reports expired and I haven't found a fix online.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert 1962 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e8a3a41-aeda-4584-87a9-c9f2bffeed85
  InstallationDate: Installed on 2014-04-23 (900 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  MachineType: ASUSTeK Computer INC. 1001PXD
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=39e08d55-8a43-457f-9d95-04d0dfab085d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic i686
  UpgradeStatus: Upgraded to xenial on 2016-10-09 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1001PXD
  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.:bvr0302:bd09/20/2010:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1001PXD
  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/1631803/+subscriptions

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

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

2016-10-09 Thread Albert 
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1631803/+attachment/4758431/+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/1631803

Title:
   ath9k driver randomly disconnects and can only reconnect by reloading
  the module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is the exact same bug described in Bug #407040 and Bug #404433, I
  need to reopen this as it was never fixed. I look as though network
  card is not able to reset and is causing random disconnects and
  causing the wlan interface to become unavailable, to a point where I
  need to restart my netbook to get access to the interface again. DMESG
  output:

  [  400.285672] ath: phy0: Chip reset failed
  [  400.285688] ath: phy0: Unable to reset channel, reset status -22
  [  400.285771] ath: phy0: Unable to set channel
  [  400.288009] ath: phy0: RX failed to go idle in 10 ms RXSM=0x
  [  400.288009] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x 
AR_DIAG_SW=0x DMADBG_7=0x

  
  I am running:
  Linux albert-1001PXD 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:41:41 UTC 
2016 i686 i686 i686 GNU/Linux

  
  The previous bug reports expired and I haven't found a fix online.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert 1962 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e8a3a41-aeda-4584-87a9-c9f2bffeed85
  InstallationDate: Installed on 2014-04-23 (900 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  MachineType: ASUSTeK Computer INC. 1001PXD
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=39e08d55-8a43-457f-9d95-04d0dfab085d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic i686
  UpgradeStatus: Upgraded to xenial on 2016-10-09 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1001PXD
  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.:bvr0302:bd09/20/2010:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1001PXD
  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/1631803/+subscriptions

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

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

2016-10-09 Thread Albert 
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1631803/+attachment/4758440/+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/1631803

Title:
   ath9k driver randomly disconnects and can only reconnect by reloading
  the module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is the exact same bug described in Bug #407040 and Bug #404433, I
  need to reopen this as it was never fixed. I look as though network
  card is not able to reset and is causing random disconnects and
  causing the wlan interface to become unavailable, to a point where I
  need to restart my netbook to get access to the interface again. DMESG
  output:

  [  400.285672] ath: phy0: Chip reset failed
  [  400.285688] ath: phy0: Unable to reset channel, reset status -22
  [  400.285771] ath: phy0: Unable to set channel
  [  400.288009] ath: phy0: RX failed to go idle in 10 ms RXSM=0x
  [  400.288009] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x 
AR_DIAG_SW=0x DMADBG_7=0x

  
  I am running:
  Linux albert-1001PXD 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:41:41 UTC 
2016 i686 i686 i686 GNU/Linux

  
  The previous bug reports expired and I haven't found a fix online.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert 1962 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e8a3a41-aeda-4584-87a9-c9f2bffeed85
  InstallationDate: Installed on 2014-04-23 (900 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  MachineType: ASUSTeK Computer INC. 1001PXD
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=39e08d55-8a43-457f-9d95-04d0dfab085d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic i686
  UpgradeStatus: Upgraded to xenial on 2016-10-09 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1001PXD
  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.:bvr0302:bd09/20/2010:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1001PXD
  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/1631803/+subscriptions

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

[Kernel-packages] [Bug 1629197] Re: Suspend not working

2016-10-09 Thread Slither 
Hi Christopher,

I'm happy to re-attempt the 6 pm-test commands again but to be clear on
how the resume trace is generated can you please confirm if the steps
below will suffice?

sudo su
echo freezer > /sys/power/pm_test
exit

sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

# at this point my machine will instantly freeze, do I wait or should I
press the reset button?

# also do I run the dmesg command below after the restart?

dmesg > dmesg.txt

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

Title:
  Suspend not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm running a fresh installation of 16.04 running the latest updates.

  When I `pm-suspend` the computer remains powered on but is completely
  unresponsive. There is no signal going to my monitor and I can't enter
  a tty shell or ctrl+alt+del to restart. I'm forced to press the the
  physical reset button. This happens every time I perform a suspend.

  I can shutdown and reboot at the moment. I really wish DSDT loading
  was still available, I could have attempted to fix this myself with a
  patched bios (if a bung ACPI call is the culprit).

  Thanks in advance,

  Stephen

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Fri Sep 30 16:48:54 2016
  HibernationDevice: RESUME=UUID=94b7cd61-7e7a-41a7-a8ec-e3b9b7e2eb87
  InstallationDate: Installed on 2016-05-18 (134 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=48e60eed-d92a-4a36-86dd-0c839f9a63d0 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-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-I
  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.:bvr1001:bd02/01/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-I: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/1629197/+subscriptions

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

[Kernel-packages] [Bug 1611552] Re: package linux-image-4.4.0-34-generic 4.4.0-34.53 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2016-10-09 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package linux-image-4.4.0-34-generic 4.4.0-34.53 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Expired

Bug description:
  This error occurred when installing the most recent round of updates.

  Running 'sudo dpkg -i /var/cache/apt/archives/linux-
  image-4.4.0-34-generic_4.4.0-34.53_amd64.deb' then 'sudo apt-get
  install -f' seemed to fix the problem.

  Perhaps the installation of the kernel was somehow interrupted?
  During installation I opened the System76 driver, but nothing else
  happened, no system crash, etc.

  (As this was generated by Apport, I'm assuming the necessary debug
  information is attached)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   sly3747 F...m pulseaudio
   /dev/snd/controlC0:  sly3747 F pulseaudio
   /dev/snd/controlC1:  sly3747 F pulseaudio
  Date: Tue Aug  9 19:09:10 2016
  DuplicateSignature:
   package:linux-image-4.4.0-34-generic:4.4.0-34.53
   Setting up linux-image-4.4.0-34-generic (4.4.0-34.53) ...
   Internal Error: Could not find image (/boot/vmlinuz-4.4.0-34-generic)
   dpkg: error processing package linux-image-4.4.0-34-generic (--configure):
subprocess installed post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=c4490ff3-1d2a-4a7b-aa3d-fbdcc9bac94c
  InstallationDate: Installed on 2016-07-06 (34 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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 0c45:6416 Microdia 
   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. Studio 1558
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/system_ssd-root ro rootflags=subvol=@ 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: grub-pc 2.02~beta2-36ubuntu3.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.4.0-34-generic 4.4.0-34.53 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 345678
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd03/30/2011:svnDellInc.:pnStudio1558:pvrA12:rvnDellInc.:rn345678:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Studio 1558
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1611675] Re: package linux-image-extra-4.4.0-21-generic 4.4.0-21.37 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127

2016-10-09 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package linux-image-extra-4.4.0-21-generic 4.4.0-21.37 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub
  exited with return code 127

Status in linux package in Ubuntu:
  Expired

Bug description:
  I cannot upgrade packages or install new packages because of this
  block

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-21-generic 4.4.0-21.37
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yudiandreanp   5143 F pulseaudio
   /dev/snd/controlC0:  yudiandreanp   5143 F pulseaudio
  Date: Wed Aug 10 16:41:00 2016
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=8f839e76-7583-4053-bf53-348bb6f7dc42
  InstallationDate: Installed on 2016-05-30 (72 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK Computer Inc. N45SF
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=dd7d5f4b-fab4-4fdc-86df-4cb86a82b762 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.1
  SourcePackage: linux
  Title: package linux-image-extra-4.4.0-21-generic 4.4.0-21.37 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with 
return code 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/19/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N45SF.223
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: N45SF
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN45SF.223:bd01/19/2012:svnASUSTeKComputerInc.:pnN45SF:pvr1.0:rvnASUSTeKComputerInc.:rnN45SF:rvr1.0:cvnASUSTeKComputerInc.:ct9:cvr1.0:
  dmi.product.name: N45SF
  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/1611675/+subscriptions

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

[Kernel-packages] [Bug 1631803] RfKill.txt

2016-10-09 Thread Albert 
apport information

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

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

Title:
   ath9k driver randomly disconnects and can only reconnect by reloading
  the module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is the exact same bug described in Bug #407040 and Bug #404433, I
  need to reopen this as it was never fixed. I look as though network
  card is not able to reset and is causing random disconnects and
  causing the wlan interface to become unavailable, to a point where I
  need to restart my netbook to get access to the interface again. DMESG
  output:

  [  400.285672] ath: phy0: Chip reset failed
  [  400.285688] ath: phy0: Unable to reset channel, reset status -22
  [  400.285771] ath: phy0: Unable to set channel
  [  400.288009] ath: phy0: RX failed to go idle in 10 ms RXSM=0x
  [  400.288009] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x 
AR_DIAG_SW=0x DMADBG_7=0x

  
  I am running:
  Linux albert-1001PXD 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:41:41 UTC 
2016 i686 i686 i686 GNU/Linux

  
  The previous bug reports expired and I haven't found a fix online.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert 1962 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e8a3a41-aeda-4584-87a9-c9f2bffeed85
  InstallationDate: Installed on 2014-04-23 (900 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  MachineType: ASUSTeK Computer INC. 1001PXD
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=39e08d55-8a43-457f-9d95-04d0dfab085d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic i686
  UpgradeStatus: Upgraded to xenial on 2016-10-09 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1001PXD
  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.:bvr0302:bd09/20/2010:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1001PXD
  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/1631803/+subscriptions

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

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

2016-10-09 Thread Albert 
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1631803/+attachment/4758437/+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/1631803

Title:
   ath9k driver randomly disconnects and can only reconnect by reloading
  the module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is the exact same bug described in Bug #407040 and Bug #404433, I
  need to reopen this as it was never fixed. I look as though network
  card is not able to reset and is causing random disconnects and
  causing the wlan interface to become unavailable, to a point where I
  need to restart my netbook to get access to the interface again. DMESG
  output:

  [  400.285672] ath: phy0: Chip reset failed
  [  400.285688] ath: phy0: Unable to reset channel, reset status -22
  [  400.285771] ath: phy0: Unable to set channel
  [  400.288009] ath: phy0: RX failed to go idle in 10 ms RXSM=0x
  [  400.288009] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x 
AR_DIAG_SW=0x DMADBG_7=0x

  
  I am running:
  Linux albert-1001PXD 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:41:41 UTC 
2016 i686 i686 i686 GNU/Linux

  
  The previous bug reports expired and I haven't found a fix online.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert 1962 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e8a3a41-aeda-4584-87a9-c9f2bffeed85
  InstallationDate: Installed on 2014-04-23 (900 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  MachineType: ASUSTeK Computer INC. 1001PXD
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=39e08d55-8a43-457f-9d95-04d0dfab085d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic i686
  UpgradeStatus: Upgraded to xenial on 2016-10-09 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1001PXD
  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.:bvr0302:bd09/20/2010:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1001PXD
  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/1631803/+subscriptions

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

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

2016-10-09 Thread Albert 
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1631803/+attachment/4758427/+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/1631803

Title:
   ath9k driver randomly disconnects and can only reconnect by reloading
  the module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is the exact same bug described in Bug #407040 and Bug #404433, I
  need to reopen this as it was never fixed. I look as though network
  card is not able to reset and is causing random disconnects and
  causing the wlan interface to become unavailable, to a point where I
  need to restart my netbook to get access to the interface again. DMESG
  output:

  [  400.285672] ath: phy0: Chip reset failed
  [  400.285688] ath: phy0: Unable to reset channel, reset status -22
  [  400.285771] ath: phy0: Unable to set channel
  [  400.288009] ath: phy0: RX failed to go idle in 10 ms RXSM=0x
  [  400.288009] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x 
AR_DIAG_SW=0x DMADBG_7=0x

  
  I am running:
  Linux albert-1001PXD 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:41:41 UTC 
2016 i686 i686 i686 GNU/Linux

  
  The previous bug reports expired and I haven't found a fix online.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert 1962 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e8a3a41-aeda-4584-87a9-c9f2bffeed85
  InstallationDate: Installed on 2014-04-23 (900 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  MachineType: ASUSTeK Computer INC. 1001PXD
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=39e08d55-8a43-457f-9d95-04d0dfab085d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic i686
  UpgradeStatus: Upgraded to xenial on 2016-10-09 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1001PXD
  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.:bvr0302:bd09/20/2010:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1001PXD
  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/1631803/+subscriptions

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

[Kernel-packages] [Bug 1602371] Re: Touchpad incorrectly detected as PS/2 mouse in 'HP Pavillion 340G1' after Ubuntu 12.04 upgrade to 14.04.

2016-10-09 Thread Christopher M. Penalver 
Daniel Ojeda, I am closing this report because the bug has been fixed in
the latest development version of Ubuntu.

This is a significant bug in Ubuntu. If you need a fix for the bug in
previous versions of Ubuntu, please perform as much as possible of the
SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

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

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

Title:
  Touchpad incorrectly detected as PS/2 mouse in 'HP Pavillion 340G1'
  after Ubuntu 12.04 upgrade to 14.04.

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I'm currently using Linux 4.2.0-38-generic Kernel.

  
  I adjunct in a .txt the outputs for 
  -dmesg
  -cat /proc/bus/input/devices 

  Regards

  Daniel Ojeda
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  do 3758 F pulseaudio
   /dev/snd/controlC0:  do 3758 F pulseaudio
  CurrentDesktop: Unity
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-yuanli-precise-amd64-20131009-1
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=93204dde-91fd-41de-b63a-8c49d4903331
  InstallationDate: Installed on 2015-07-13 (365 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20131009-06:05
  MachineType: Hewlett-Packard HP 340 G1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-38-generic 
root=UUID=8fb79e40-a483-431f-ae1f-b6430988c9fd ro quiet splash i8042.reset 
i8042.nomux i8042.nopnp i8042.noloop vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-38.45~14.04.1-generic 4.2.8-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-38-generic N/A
   linux-backports-modules-4.2.0-38-generic  N/A
   linux-firmware1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 4.2.0-38-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-07-13 (364 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 06/12/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.12
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 21B7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 46.0B
  dmi.chassis.asset.tag: 5CG4471R2Q
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.12:bd06/12/2014:svnHewlett-Packard:pnHP340G1:pvr099810167:rvnHewlett-Packard:rn21B7:rvrKBCVersion46.0B:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 340 G1
  dmi.product.version: 099810167
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1611831] Re: Can't boot from new kernel 4.4.0-34. Old kernel 4.4.0-31 is fine.

2016-10-09 Thread Christopher M. Penalver 
Ryan Budney, to keep this relevant to upstream, one would want check
for, and test the latest mainline kernel (now 4.8.1) as it is released.

Could you please advise?

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

Title:
  Can't boot from new kernel 4.4.0-34.  Old kernel 4.4.0-31 is fine.

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

Bug description:
  Greetings,

  I recently upgraded from the 4.4.0-31 to 4.4.0-34 kernel in Ubuntu
  16.04.  If I try booting from 4.4.0-34, my system freezes just after I
  enter my password to decrypt my hard-drive.  If I ask it to boot from
  4.4.0-31, everything is fine.

  My boot.log file:

lvmetad is not active yet, using direct activation during sysinit
Volume group "ubuntu-vg" not found
Cannot process volume group ubuntu-vg
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes.  This may take a while...
Found volume group "ubuntu-vg" using metadata type lvm2
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
2 logical volume(s) in volume group "ubuntu-vg" now active
  /dev/mapper/ubuntu--vg-root: recovering journal
  /dev/mapper/ubuntu--vg-root: clean, 525872/28426240 files, 91143613/113674240 
blocks

  
  It's unclear to me what is going wrong.  There appears to be no activity on 
the computer.  I let the boot sequence sit for 10 minutes (way longer than an 
average boot time) my laptop's fan is running full-tilt.  But there was no 
hard-drive activity.  

  How can I find out what's going wrong?

  I'm running Ubuntu 16.04 Linux on a Lenovo W530.  I'm not certain what other 
information would be helpful for a bug report.  I would be happy to submit 
whatever is deemed helpful. 
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rybu   4449 F pulseaudio
   /dev/snd/controlC0:  rybu   4449 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=48cdbc4a-e07f-4aa4-bb23-e2904e1cd350
  InstallationDate: Installed on 2016-04-26 (106 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 2436CTO
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETA3WW (2.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2436CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETA3WW(2.63):bd09/18/2015:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2436CTO
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1628520] Re: nvme: Missing patch in Ubuntu-4.4.0-41.61

2016-10-09 Thread bugproxy 
--- Comment From gbert...@br.ibm.com 2016-10-10 00:05 EDT---
(In reply to comment #5)
> (In reply to comment #4)
> > This is a bug against 16.04, right?
>
> yes.

Patch was applied in master-next during a rebase on the -stable kernel.

c7ebb31cd3f7 ("nvme: Call pci_disable_device on the error path.")

I'm satisfied by this.  Closing.

** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin16044

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

Title:
  nvme: Missing patch in Ubuntu-4.4.0-41.61

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

Bug description:
  == Comment: #0 - Gabriel Krisman Bertazi  - 2016-09-27 
22:59:44 ==
  Ubuntu-4.4.0-40.60 included my backport of :

  b00a726a9fd ("NVMe: Don't unmap controller registers on reset") #upstream 
commit
[ 30d6592fce71 on the Ubuntu -proposed branch]

  But missed the fix up that came later:

  81e9a969c441 ("nvme: Call pci_disable_device on the error path.") #
  4.4.y tree

  This means that we may hit an Oops if we need to go into the error
  path of  the nvme probe.

  
  Please cherry-pick this fix to your kernel.

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

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

[Kernel-packages] [Bug 1610622] Re: AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x000f address=0x00000000bec09880 flags=0x0010]

2016-10-09 Thread Boris A. Noskov 
** Changed in: linux (Ubuntu)
   Status: Expired => 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/1610622

Title:
  AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x000f
  address=0xbec09880 flags=0x0010]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   [   19.880847] xhci_hcd :02:00.0: can't setup: -110
   [   19.880915] clocksource: Switched to clocksource tsc
   [   19.880919] xhci_hcd :02:00.0: USB bus 8 deregistered
   [   19.880979] xhci_hcd :02:00.0: init :02:00.0 fail, -110
   [   19.881033] xhci_hcd: probe of :02:00.0 failed with error -110

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hitkliv1854 F pulseaudio
   /dev/snd/controlC2:  hitkliv1854 F pulseaudio
   /dev/snd/controlC0:  hitkliv1854 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Sun Aug  7 09:38:17 2016
  HibernationDevice: RESUME=UUID=4c30b323-8466-484e-bca4-99052a00ff77
  InstallationDate: Installed on 2016-08-06 (0 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=UUID=96a76e70-0ed0-478e-8558-7f0cffe4782d ro rootflags=subvol=@ quiet 
splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FC
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1611831] Re: Can't boot from new kernel 4.4.0-34. Old kernel 4.4.0-31 is fine.

2016-10-09 Thread Ryan Budney 
The bios-outdated-2.65 tag, what does this mean?   I tried clicking on
it but there's no description as far as I can tell.

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

Title:
  Can't boot from new kernel 4.4.0-34.  Old kernel 4.4.0-31 is fine.

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

Bug description:
  Greetings,

  I recently upgraded from the 4.4.0-31 to 4.4.0-34 kernel in Ubuntu
  16.04.  If I try booting from 4.4.0-34, my system freezes just after I
  enter my password to decrypt my hard-drive.  If I ask it to boot from
  4.4.0-31, everything is fine.

  My boot.log file:

lvmetad is not active yet, using direct activation during sysinit
Volume group "ubuntu-vg" not found
Cannot process volume group ubuntu-vg
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes.  This may take a while...
Found volume group "ubuntu-vg" using metadata type lvm2
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
2 logical volume(s) in volume group "ubuntu-vg" now active
  /dev/mapper/ubuntu--vg-root: recovering journal
  /dev/mapper/ubuntu--vg-root: clean, 525872/28426240 files, 91143613/113674240 
blocks

  
  It's unclear to me what is going wrong.  There appears to be no activity on 
the computer.  I let the boot sequence sit for 10 minutes (way longer than an 
average boot time) my laptop's fan is running full-tilt.  But there was no 
hard-drive activity.  

  How can I find out what's going wrong?

  I'm running Ubuntu 16.04 Linux on a Lenovo W530.  I'm not certain what other 
information would be helpful for a bug report.  I would be happy to submit 
whatever is deemed helpful. 
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rybu   4449 F pulseaudio
   /dev/snd/controlC0:  rybu   4449 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=48cdbc4a-e07f-4aa4-bb23-e2904e1cd350
  InstallationDate: Installed on 2016-04-26 (106 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 2436CTO
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETA3WW (2.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2436CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETA3WW(2.63):bd09/18/2015:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2436CTO
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO

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

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

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

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

apport-collect 1631803

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

Title:
   ath9k driver randomly disconnects and can only reconnect by reloading
  the module

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is the exact same bug described in Bug #407040 and Bug #404433, I
  need to reopen this as it was never fixed. I look as though network
  card is not able to reset and is causing random disconnects and
  causing the wlan interface to become unavailable, to a point where I
  need to restart my netbook to get access to the interface again. DMESG
  output:

  [  400.285672] ath: phy0: Chip reset failed
  [  400.285688] ath: phy0: Unable to reset channel, reset status -22
  [  400.285771] ath: phy0: Unable to set channel
  [  400.288009] ath: phy0: RX failed to go idle in 10 ms RXSM=0x
  [  400.288009] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x 
AR_DIAG_SW=0x DMADBG_7=0x

  
  I am running:
  Linux albert-1001PXD 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:41:41 UTC 
2016 i686 i686 i686 GNU/Linux

  
  The previous bug reports expired and I haven't found a fix online.

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

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

[Kernel-packages] [Bug 1631803] Re: ath9k driver randomly disconnects and can only reconnect by reloading the module

2016-10-09 Thread Paul White 
Reassigning to the kernel as per the previous two reports.

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

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

Title:
   ath9k driver randomly disconnects and can only reconnect by reloading
  the module

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is the exact same bug described in Bug #407040 and Bug #404433, I
  need to reopen this as it was never fixed. I look as though network
  card is not able to reset and is causing random disconnects and
  causing the wlan interface to become unavailable, to a point where I
  need to restart my netbook to get access to the interface again. DMESG
  output:

  [  400.285672] ath: phy0: Chip reset failed
  [  400.285688] ath: phy0: Unable to reset channel, reset status -22
  [  400.285771] ath: phy0: Unable to set channel
  [  400.288009] ath: phy0: RX failed to go idle in 10 ms RXSM=0x
  [  400.288009] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x 
AR_DIAG_SW=0x DMADBG_7=0x

  
  I am running:
  Linux albert-1001PXD 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:41:41 UTC 
2016 i686 i686 i686 GNU/Linux

  
  The previous bug reports expired and I haven't found a fix online.

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

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

[Kernel-packages] [Bug 1588632] Re: Please upgrade to zfs 0.6.5.7

2016-10-09 Thread Tamas Papp 
What is the recommended or official way to have critical fixed in the
LTS kernel?

zfs 0.6.5.7 includes critical fixes, like hole_birth fix (workaround)
which is extremely IMPORTANT.

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

Title:
  Please upgrade to zfs 0.6.5.7

Status in linux package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  Version 0.6.5.7 was released 21 ago, this is the changelog:
  https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.6.5.7

  Since Ubuntu is now shipping ZFS we can't rely on the ppa anymore to
  provide up to date packages. This point release also fixes a few minor
  bugs and supports Linux 4.6.

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

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

[Kernel-packages] [Bug 1631803] [NEW] ath9k driver randomly disconnects and can only reconnect by reloading the module

2016-10-09 Thread Launchpad Bug Tracker 
You have been subscribed to a public bug:

This is the exact same bug described in Bug #407040 and Bug #404433, I
need to reopen this as it was never fixed. I look as though network card
is not able to reset and is causing random disconnects and causing the
wlan interface to become unavailable, to a point where I need to restart
my netbook to get access to the interface again. DMESG output:

[  400.285672] ath: phy0: Chip reset failed
[  400.285688] ath: phy0: Unable to reset channel, reset status -22
[  400.285771] ath: phy0: Unable to set channel
[  400.288009] ath: phy0: RX failed to go idle in 10 ms RXSM=0x
[  400.288009] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x 
AR_DIAG_SW=0x DMADBG_7=0x


I am running:
Linux albert-1001PXD 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:41:41 UTC 
2016 i686 i686 i686 GNU/Linux


The previous bug reports expired and I haven't found a fix online.

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

-- 
 ath9k driver randomly disconnects and can only reconnect by reloading the 
module
https://bugs.launchpad.net/bugs/1631803
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 1611831] Re: Can't boot from new kernel 4.4.0-34. Old kernel 4.4.0-31 is fine.

2016-10-09 Thread Ryan Budney 
Regarding post number 18, I spoke too soon about kernel:

Linux rybu-ThinkPad-W530 4.4.16-040416-generic #201607271333 SMP Wed Jul
27 17:35:45 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

That kernel boots and I can log into Ubuntu with it, even into my
account.   But all the files in my home directory are gone.   I suspect
this is due to the directory being encrypted.

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

Title:
  Can't boot from new kernel 4.4.0-34.  Old kernel 4.4.0-31 is fine.

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

Bug description:
  Greetings,

  I recently upgraded from the 4.4.0-31 to 4.4.0-34 kernel in Ubuntu
  16.04.  If I try booting from 4.4.0-34, my system freezes just after I
  enter my password to decrypt my hard-drive.  If I ask it to boot from
  4.4.0-31, everything is fine.

  My boot.log file:

lvmetad is not active yet, using direct activation during sysinit
Volume group "ubuntu-vg" not found
Cannot process volume group ubuntu-vg
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes.  This may take a while...
Found volume group "ubuntu-vg" using metadata type lvm2
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
2 logical volume(s) in volume group "ubuntu-vg" now active
  /dev/mapper/ubuntu--vg-root: recovering journal
  /dev/mapper/ubuntu--vg-root: clean, 525872/28426240 files, 91143613/113674240 
blocks

  
  It's unclear to me what is going wrong.  There appears to be no activity on 
the computer.  I let the boot sequence sit for 10 minutes (way longer than an 
average boot time) my laptop's fan is running full-tilt.  But there was no 
hard-drive activity.  

  How can I find out what's going wrong?

  I'm running Ubuntu 16.04 Linux on a Lenovo W530.  I'm not certain what other 
information would be helpful for a bug report.  I would be happy to submit 
whatever is deemed helpful. 
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rybu   4449 F pulseaudio
   /dev/snd/controlC0:  rybu   4449 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=48cdbc4a-e07f-4aa4-bb23-e2904e1cd350
  InstallationDate: Installed on 2016-04-26 (106 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 2436CTO
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETA3WW (2.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2436CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETA3WW(2.63):bd09/18/2015:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2436CTO
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1611831] Re: Can't boot from new kernel 4.4.0-34. Old kernel 4.4.0-31 is fine.

2016-10-09 Thread Ryan Budney 
The bug is only semi-fixed upstream.  With kernels 4.4.0-36 and 38 there
is still a bug but it is different than what I originally reported.
With these two kernels, I can boot up the system and even log in, but
once I log in my home directory appears to be empty.   I imagine this is
because it remains encrypted.

I will update the status accordingly.

** Tags removed: kernel-fixed-upstream-4.4.15

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

Title:
  Can't boot from new kernel 4.4.0-34.  Old kernel 4.4.0-31 is fine.

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

Bug description:
  Greetings,

  I recently upgraded from the 4.4.0-31 to 4.4.0-34 kernel in Ubuntu
  16.04.  If I try booting from 4.4.0-34, my system freezes just after I
  enter my password to decrypt my hard-drive.  If I ask it to boot from
  4.4.0-31, everything is fine.

  My boot.log file:

lvmetad is not active yet, using direct activation during sysinit
Volume group "ubuntu-vg" not found
Cannot process volume group ubuntu-vg
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes.  This may take a while...
Found volume group "ubuntu-vg" using metadata type lvm2
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
2 logical volume(s) in volume group "ubuntu-vg" now active
  /dev/mapper/ubuntu--vg-root: recovering journal
  /dev/mapper/ubuntu--vg-root: clean, 525872/28426240 files, 91143613/113674240 
blocks

  
  It's unclear to me what is going wrong.  There appears to be no activity on 
the computer.  I let the boot sequence sit for 10 minutes (way longer than an 
average boot time) my laptop's fan is running full-tilt.  But there was no 
hard-drive activity.  

  How can I find out what's going wrong?

  I'm running Ubuntu 16.04 Linux on a Lenovo W530.  I'm not certain what other 
information would be helpful for a bug report.  I would be happy to submit 
whatever is deemed helpful. 
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rybu   4449 F pulseaudio
   /dev/snd/controlC0:  rybu   4449 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=48cdbc4a-e07f-4aa4-bb23-e2904e1cd350
  InstallationDate: Installed on 2016-04-26 (106 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 2436CTO
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETA3WW (2.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2436CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETA3WW(2.63):bd09/18/2015:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2436CTO
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1572801] Re: Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10

2016-10-09 Thread rob cain 
Just to add, too was experiencing high RAM usage & what appeared to be a
slow but steady memory leak in Unbunti 16.04 (latest). In my case, I
discovered at least part of the problem was one or more (yet to be
determined) Firefox (v49.0) plugins/add-ons. People also running Firefox
might like to retry tests using Firefox in Safe mode (all add ons
disabled), if you haven't alreay done so, see if that makes any
difference. (Also running stuff like Dropbox in the background whilst
trying to pin down a problem like this seems an inherently bad idea).

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

Title:
  Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10

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

Bug description:
  Ubuntu 16.04 64bit ISO number 20160420.1
  unity version 7.4.0+16.04.20160415-0ubuntu1
  Ubuntu 16.04 64bit ram usage has increase dramatically over Ubuntu 15.10
  Ubuntu 16.04 ram roughly 1 GB Ubuntu15.10 can be tuned to 420, 450 MB
  Ubuntu 16.04 with unity uses 1GB whereas Kubuntu 16.04 is using 420MB live usb

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr 21 01:44:22 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1920x1080+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'place', 'regex', 'resize', 'session', 'snap', 'vpswitch', 'wall', 'animation', 
'commands', 'compiztoolbox', 'copytex', 'fade', 'grid', 'imgpng', 'mousepoll', 
'move', 'scale', 'unitymtgrabhandles', 'workarounds', 'expo', 'ezoom', 
'unityshell']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2004
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2004:bd06/03/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PLUS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Apr 21 01:37:17 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Kernel-packages] [Bug 205715] cozy and homelike place

2016-10-09 Thread EdZ 
Yo!

Me and  my  family have  visited a very cozy place recently,  you may
really like  it, just  take a look at some pics  of  it


All the best, Lisa Stanley

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

Title:
  couldn't start with 2.6.24-12

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Problem found with 2.6.24-12

  IBM ThinkPad T30

  Starting in normal mode i found the following

  [50.261006] intel_rng: FWH not detected

  and in recovery mode

  [41.135147] input: TPPS/2 IBM TrackPoint as
  /devices/platform/i8047/serio1/serio2/input/input8

  I start ubuntu choosing the previous release, some clue for this
  issue.

  Thanks in advance.

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

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

[Kernel-packages] [Bug 1563229] Re: Touchpad recognised as mouse FTE1000

2016-10-09 Thread Joel M 
Same here like Onur. In addition: My model is the Asus TP200S (written
on the back of the device and Ubuntu recognized it as TP205SA.

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

Title:
  Touchpad recognised as mouse FTE1000

Status in linux package in Ubuntu:
  Triaged
Status in xinput package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Triaged
Status in xinput source package in Trusty:
  Confirmed
Status in linux source package in Wily:
  Triaged
Status in xinput source package in Wily:
  Confirmed
Status in linux source package in Xenial:
  Triaged
Status in xinput source package in Xenial:
  Confirmed

Bug description:
  In my Asus e200ha touchpad is recognized as mouse, only one click, no
  two finger click and scrolling

  Xinput say:
  FTE1000:00 0B05:0101   id=12[slave pointer (2)]

  i've tried:
  - ubuntu 14.04 with stock kernel
  - ubuntu 14.04 with 4.6rc1 kernel
  - Linux mint 17.3 with stock kernel
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: xinput 1.6.1-1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa rosa
  Uname: Linux 3.19.0-32-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/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  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/1563229/+subscriptions

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

[Kernel-packages] [Bug 1631719] Re: Intel GMA965 DRM hanging on yakkety

2016-10-09 Thread Fred Vkigg 
Attached dmesg with complete kernel errors with stack traces

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

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

Title:
  Intel GMA965 DRM hanging on yakkety

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrades to Yakkety in feature freeze with kernel 4.8.0-21-generic.

  System regularly hangs for 10 second intervals which is very noticeable in 
boot process. Cause seems to be the Intel GMA965 DRM support causing regular 
kernel warnings:
   WARNING: CPU: 0 PID: 1183 at 
/build/linux-JqzU2_/linux-4.8.0/drivers/gpu/drm/drm_irq.c:1224 
drm_wait_one_vblank+0x1b6/0x1c0 [drm]

  The problem seems to start very early in the boot process, possible
  already in GRUB, definitely when the kernel image is first started.

  Workaround:
  Boot into Ubuntu recovery mode and then resume into graphical system. In this 
case the problem does not occur.

  Disabling GRUB graphics with GRUB_TERMINAL=console does not help

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-21-generic 4.8.0-21.23
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael2377 F pulseaudio
  Date: Sun Oct  9 11:10:10 2016
  HibernationDevice: RESUME=UUID=34b8481d-d92b-4611-820b-c0c2b607f6ab
  InstallationDate: Installed on 2012-08-21 (1509 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: LENOVO 8943DNG
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-21-generic 
root=UUID=2835f778-bc9c-463b-8ee1-b337e0efe6d7 ro quiet splash vt.handoff=7
  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.8.0-21-generic N/A
   linux-backports-modules-4.8.0-21-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-08 (0 days ago)
  dmi.bios.date: 10/22/2007
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7QET27WW (1.09 )
  dmi.board.name: 8943DNG
  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:bvr7QET27WW(1.09):bd10/22/2007:svnLENOVO:pn8943DNG:pvrThinkPadR61:rvnLENOVO:rn8943DNG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 8943DNG
  dmi.product.version: ThinkPad R61
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1631719] Re: Intel GMA965 DRM hanging on yakkety

2016-10-09 Thread Fred Vkigg 
Attach Xorg.log for completeness although this does not show any
problems

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

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

Title:
  Intel GMA965 DRM hanging on yakkety

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrades to Yakkety in feature freeze with kernel 4.8.0-21-generic.

  System regularly hangs for 10 second intervals which is very noticeable in 
boot process. Cause seems to be the Intel GMA965 DRM support causing regular 
kernel warnings:
   WARNING: CPU: 0 PID: 1183 at 
/build/linux-JqzU2_/linux-4.8.0/drivers/gpu/drm/drm_irq.c:1224 
drm_wait_one_vblank+0x1b6/0x1c0 [drm]

  The problem seems to start very early in the boot process, possible
  already in GRUB, definitely when the kernel image is first started.

  Workaround:
  Boot into Ubuntu recovery mode and then resume into graphical system. In this 
case the problem does not occur.

  Disabling GRUB graphics with GRUB_TERMINAL=console does not help

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-21-generic 4.8.0-21.23
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael2377 F pulseaudio
  Date: Sun Oct  9 11:10:10 2016
  HibernationDevice: RESUME=UUID=34b8481d-d92b-4611-820b-c0c2b607f6ab
  InstallationDate: Installed on 2012-08-21 (1509 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: LENOVO 8943DNG
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-21-generic 
root=UUID=2835f778-bc9c-463b-8ee1-b337e0efe6d7 ro quiet splash vt.handoff=7
  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.8.0-21-generic N/A
   linux-backports-modules-4.8.0-21-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-08 (0 days ago)
  dmi.bios.date: 10/22/2007
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7QET27WW (1.09 )
  dmi.board.name: 8943DNG
  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:bvr7QET27WW(1.09):bd10/22/2007:svnLENOVO:pn8943DNG:pvrThinkPadR61:rvnLENOVO:rn8943DNG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 8943DNG
  dmi.product.version: ThinkPad R61
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1631719] [NEW] Intel GMA965 DRM hanging on yakkety

2016-10-09 Thread Fred Vkigg 
Public bug reported:

Upgrades to Yakkety in feature freeze with kernel 4.8.0-21-generic.

System regularly hangs for 10 second intervals which is very noticeable in boot 
process. Cause seems to be the Intel GMA965 DRM support causing regular kernel 
warnings:
 WARNING: CPU: 0 PID: 1183 at 
/build/linux-JqzU2_/linux-4.8.0/drivers/gpu/drm/drm_irq.c:1224 
drm_wait_one_vblank+0x1b6/0x1c0 [drm]

The problem seems to start very early in the boot process, possible
already in GRUB, definitely when the kernel image is first started.

Workaround:
Boot into Ubuntu recovery mode and then resume into graphical system. In this 
case the problem does not occur.

Disabling GRUB graphics with GRUB_TERMINAL=console does not help

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-21-generic 4.8.0-21.23
ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
Uname: Linux 4.8.0-21-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  michael2377 F pulseaudio
Date: Sun Oct  9 11:10:10 2016
HibernationDevice: RESUME=UUID=34b8481d-d92b-4611-820b-c0c2b607f6ab
InstallationDate: Installed on 2012-08-21 (1509 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
MachineType: LENOVO 8943DNG
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-21-generic 
root=UUID=2835f778-bc9c-463b-8ee1-b337e0efe6d7 ro quiet splash vt.handoff=7
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.8.0-21-generic N/A
 linux-backports-modules-4.8.0-21-generic  N/A
 linux-firmware1.161
SourcePackage: linux
UpgradeStatus: Upgraded to yakkety on 2016-10-08 (0 days ago)
dmi.bios.date: 10/22/2007
dmi.bios.vendor: LENOVO
dmi.bios.version: 7QET27WW (1.09 )
dmi.board.name: 8943DNG
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:bvr7QET27WW(1.09):bd10/22/2007:svnLENOVO:pn8943DNG:pvrThinkPadR61:rvnLENOVO:rn8943DNG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 8943DNG
dmi.product.version: ThinkPad R61
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Intel GMA965 DRM hanging on yakkety

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrades to Yakkety in feature freeze with kernel 4.8.0-21-generic.

  System regularly hangs for 10 second intervals which is very noticeable in 
boot process. Cause seems to be the Intel GMA965 DRM support causing regular 
kernel warnings:
   WARNING: CPU: 0 PID: 1183 at 
/build/linux-JqzU2_/linux-4.8.0/drivers/gpu/drm/drm_irq.c:1224 
drm_wait_one_vblank+0x1b6/0x1c0 [drm]

  The problem seems to start very early in the boot process, possible
  already in GRUB, definitely when the kernel image is first started.

  Workaround:
  Boot into Ubuntu recovery mode and then resume into graphical system. In this 
case the problem does not occur.

  Disabling GRUB graphics with GRUB_TERMINAL=console does not help

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-21-generic 4.8.0-21.23
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael2377 F pulseaudio
  Date: Sun Oct  9 11:10:10 2016
  HibernationDevice: RESUME=UUID=34b8481d-d92b-4611-820b-c0c2b607f6ab
  InstallationDate: Installed on 2012-08-21 (1509 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: LENOVO 8943DNG
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-21-generic 
root=UUID=2835f778-bc9c-463b-8ee1-b337e0efe6d7 ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as

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

2016-10-09 Thread Brad Figg 
This change was made by a bot.

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

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

Title:
  Intel GMA965 DRM hanging on yakkety

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrades to Yakkety in feature freeze with kernel 4.8.0-21-generic.

  System regularly hangs for 10 second intervals which is very noticeable in 
boot process. Cause seems to be the Intel GMA965 DRM support causing regular 
kernel warnings:
   WARNING: CPU: 0 PID: 1183 at 
/build/linux-JqzU2_/linux-4.8.0/drivers/gpu/drm/drm_irq.c:1224 
drm_wait_one_vblank+0x1b6/0x1c0 [drm]

  The problem seems to start very early in the boot process, possible
  already in GRUB, definitely when the kernel image is first started.

  Workaround:
  Boot into Ubuntu recovery mode and then resume into graphical system. In this 
case the problem does not occur.

  Disabling GRUB graphics with GRUB_TERMINAL=console does not help

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-21-generic 4.8.0-21.23
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael2377 F pulseaudio
  Date: Sun Oct  9 11:10:10 2016
  HibernationDevice: RESUME=UUID=34b8481d-d92b-4611-820b-c0c2b607f6ab
  InstallationDate: Installed on 2012-08-21 (1509 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: LENOVO 8943DNG
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-21-generic 
root=UUID=2835f778-bc9c-463b-8ee1-b337e0efe6d7 ro quiet splash vt.handoff=7
  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.8.0-21-generic N/A
   linux-backports-modules-4.8.0-21-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-08 (0 days ago)
  dmi.bios.date: 10/22/2007
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7QET27WW (1.09 )
  dmi.board.name: 8943DNG
  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:bvr7QET27WW(1.09):bd10/22/2007:svnLENOVO:pn8943DNG:pvrThinkPadR61:rvnLENOVO:rn8943DNG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 8943DNG
  dmi.product.version: ThinkPad R61
  dmi.sys.vendor: LENOVO

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

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