[Kernel-packages] [Bug 1682041] onibi (i386) - tests ran: 4, failed: 0

2017-04-15 Thread Brad Figg
tests ran:   4, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/onibi__4.4.0-74.95__2017-04-16_05-12-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/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1683105] [NEW] Installation of DMRaid should automatically add necessary modules to /etc/initramfs-tools/modules

2017-04-15 Thread David Lee
Public bug reported:

This is related to bug 1313169, I have had a sudden bout of clarity on
the cause of the issue.

I propose this modification to the dmraid installation script as it is a
small but necessary enhancement.

When dmraid is installed, it adds all the necessary hooks to initramfs-
tools. However, it has one oversight, that the required raid modules are
not added to /etc/initramfs-tools/modules. Without these modules, dmraid
will inevitably fail to initialize the array when started since the
kernel would not be able to find the required modules in the image.

I propose that when dmraid is installed, during installation the script
would check to see if the following items are already in /etc/initramfs-
tools/modules, and append the required modules into the bottom of the
file if it's not, and then rebuild the initramfs, update grub and if
necessary reinstall grub. On uninstall of package, I propose that we
should just warn the user but leave the lines in just in case they're
using something else that also needs the modules.

The following modules should be appended to the /etc/inmitramfs-
tools/modules file:

raid0
dm_raid
raid1
raid10
raid456
async_raid6_recov
async_memcpy
async_pq
async_tx
raid6_pq
async_xor
xor
libcrc32c

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

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

** Description changed:

  This is related to bug 1313169, I have had a sudden bout of clarity on
  the cause of the issue.
  
  I propose this modification to the dmraid installation script as it is a
  small but necessary enhancement.
  
  When dmraid is installed, it adds all the necessary hooks to initramfs-
  tools. However, it has one oversight, that the required raid modules are
  not added to /etc/initramfs-tools/modules. Without these modules, dmraid
  will inevitably fail to initialize the array when started since the
  kernel would not be able to find the required modules in the image.
  
  I propose that when dmraid is installed, during installation the script
  would check to see if the following items are already in /etc/initramfs-
  tools/modules, and append the required modules into the bottom of the
  file if it's not, and then rebuild the initramfs, update grub and if
  necessary reinstall grub. On uninstall of package, I propose that we
  should just warn the user but leave the lines in just in case they're
  using something else that also needs the modules.
  
  The following modules should be appended to the /etc/inmitramfs-
  tools/modules file:
  
  raid0
  dm_raid
  raid1
  raid10
  raid456
  async_raid6_recov
  async_memcpy
  async_pq
  async_tx
  raid6_pq
+ async_xor
+ xor

** Description changed:

  This is related to bug 1313169, I have had a sudden bout of clarity on
  the cause of the issue.
  
  I propose this modification to the dmraid installation script as it is a
  small but necessary enhancement.
  
  When dmraid is installed, it adds all the necessary hooks to initramfs-
  tools. However, it has one oversight, that the required raid modules are
  not added to /etc/initramfs-tools/modules. Without these modules, dmraid
  will inevitably fail to initialize the array when started since the
  kernel would not be able to find the required modules in the image.
  
  I propose that when dmraid is installed, during installation the script
  would check to see if the following items are already in /etc/initramfs-
  tools/modules, and append the required modules into the bottom of the
  file if it's not, and then rebuild the initramfs, update grub and if
  necessary reinstall grub. On uninstall of package, I propose that we
  should just warn the user but leave the lines in just in case they're
  using something else that also needs the modules.
  
  The following modules should be appended to the /etc/inmitramfs-
  tools/modules file:
  
  raid0
  dm_raid
  raid1
  raid10
  raid456
  async_raid6_recov
  async_memcpy
  async_pq
  async_tx
  raid6_pq
  async_xor
  xor
+ libcrc32c

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

Title:
  Installation of DMRaid should automatically add necessary modules to
  /etc/initramfs-tools/modules

Status in dmraid package in Ubuntu:
  New

Bug description:
  This is related to bug 1313169, I have had a sudden bout of clarity on
  the cause of the issue.

  I propose this modification to the dmraid installation script as it is
  a small but necessary enhancement.

  When dmraid is installed, it adds all the necessary hooks to
  initramfs-tools. However, it has one oversight, that the required raid
  modules are not added to /etc/initramfs-tools/modules. Without these
  modules, dmraid will inevitably fail to initialize the array when
  started since the kernel would not be able to find the required
  modules in the image.

  I propose that when dmraid is installed, 

[Kernel-packages] [Bug 1313169] Re: Ubuntu Trusty Tahr cannot boot on RAID5 array

2017-04-15 Thread David Lee
Followed up on bug 1683105 . I've worked out the exact thing that needs
to be done.

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

Title:
  Ubuntu Trusty Tahr cannot boot on RAID5 array

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Raid array is three identical Western Digital Green series 500GB hard
  drives on an NVIDIA controller set to RAID5 for a total of 1TiB
  (931.52GB) storage.

  Installation was done using the Ubuntu LiveCD.

  Partitions on the filesystem was created beforehand using gparted. The
  partition table is set up to be GPT with a 8MB bios_grub partition, a
  256MB fat32 EFIBoot partition (not used for this setup, board does not
  support EFI and is expected to boot from the bios_grub legacy
  partition), a 4GB swap, 80GB root partition, and the rest for /home.
  Then  the installer is invoked and the partitions are set up. GRUB is
  told to install to the root of the RAID array in /dev/mapper . The
  installation went flawlessly.

  Upon reboot, GRUB loads as expected, and loads the kernel and initrd
  as expected. However, the kernel gives up on waiting for the root
  partition and drops to initramfs busybox. "dmesg|grep device" shows
  the following errors:

  device-mapper: table: 252:0: raid: unknown target type
  device-mapper: ioctl: error adding target to table

  Trying to invoke dmraid -a y results in the following error:
  ERROR: device-mapper target type "raid" is not in the kernel
  RAID set "nvidia_babddecf" was not activated.

  nvidia_babddecf is the assigned volume name by the controller.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1313169/+subscriptions

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


[Kernel-packages] [Bug 1682041] onibi (amd64) - tests ran: 34, failed: 4

2017-04-15 Thread Brad Figg
tests ran:  34, failed: 4;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/onibi__4.4.0-74.95__2017-04-16_04-11-00/results-index.html

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

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1682041] onibi (i386) - tests ran: 10, failed: 1

2017-04-15 Thread Brad Figg
tests ran:  10, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/onibi__4.4.0-74.95__2017-04-16_02-39-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/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1683091] Re: The whole system froze for something like 30 seconds, then a process got killed

2017-04-15 Thread eeheeheeh
I have already mentioned that I'm not gonna share the output of `sudo
lspci -vnvn` unless absolutely necessary to resolve this issue, so I'm
changing the bug status to 'Confirmed', as instructed by brad-figg.

If you believe that the output of `sudo lspci -vnvn` is absolutely
necessary to resolve this issue, please explain why.

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

Title:
  The whole system froze for something like 30 seconds, then a process
  got killed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgraded from xenial to zesty recently.

  I was using a Firefox instance, one which is a part of Tor Browser
  Bundled. First, the application window grayed out, then the whole
  system froze for something like 30 seconds (I tried to switch to VT1
  to no avail), then the process got killed.

  Well, not exactly killed.

  The grayed-out window is still there, `xprop | grep PID` and clicking
  on it gives:

  ```
  _NET_WM_PID(CARDINAL) = 13
  ```

  PID 13 is a child of kthreadd:

  ```
  $ ps -A | awk '$1 == "13" { print }'
     13 ?00:00:00 cpuhp/1
  ```

  And this is how the relevant part of `ps -AH` with the "killed"
  process looks like:

  ```
   5709 pts/11   00:00:00   firejail
   5710 pts/11   00:00:00 firejail
   5725 pts/11   00:00:00   bash
   5736 pts/11   00:56:49 firefox 
   5769 pts/11   00:00:24   tor
  ```

  EDIT: Launchpad doesn't preserve whitespace apparently, so I'm adding
  the output above as ps.log.

  I checked syslog and dmesg. Both of them have an interesting and
  identical message, which I add as dmesg.log.

  I also add the output of `cat /proc/version_signature` as version.log.

  I don't think `sudo lspci -vnvn` is relevant here, so I'm not gonna
  share it unless absolutely necessary.

  The crashed process will be there for something like 2 or 3 days at
  least (I don't restart my laptop often), so feel free to ask me to
  manipulate or query it somehow, if necessary.

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

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


[Kernel-packages] [Bug 1683091] Re: The whole system froze for something like 30 seconds, then a process got killed

2017-04-15 Thread eeheeheeh
I also had a similar, but maybe not identical issue today.

First, several application windows grayed out, one after another. Then
my system slowed down and after a few seconds became completely
unresponsive. Of course, I couldn't switch to VT1 too. I waited for more
than 10 minutes, but nothing changed, so I restarted the laptop.

What is unusual about the situation is that during the freeze there was
no HDD activity (the blinkenlight didn't blink even once and I didn't
hear my HDD) and the CPU apparently did almost nothing too (my laptop's
fan was completely silent).

Unfortunately, there was nothing interesting in syslog when I checked it
after the restart, and checking out dmesg after a restart wouldn't help
much too.

I never experienced anything like this when I was on xenial. On xenial,
usually, when I was running out of memory and swap, my system would
become very, but not completely unresponsive, the fan would spin like
crazy, the blinkenlight responsible for HDD activity would blink like
crazy, and of course I would be able to hear the HDD too. I would
usually switch to VT1, patiently wait until the switch actually
happened, then type a command to kill the offending process. The 2
incidents that happened to me today (after I had upgraded to zesty) were
nothing like this.

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

Title:
  The whole system froze for something like 30 seconds, then a process
  got killed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Upgraded from xenial to zesty recently.

  I was using a Firefox instance, one which is a part of Tor Browser
  Bundled. First, the application window grayed out, then the whole
  system froze for something like 30 seconds (I tried to switch to VT1
  to no avail), then the process got killed.

  Well, not exactly killed.

  The grayed-out window is still there, `xprop | grep PID` and clicking
  on it gives:

  ```
  _NET_WM_PID(CARDINAL) = 13
  ```

  PID 13 is a child of kthreadd:

  ```
  $ ps -A | awk '$1 == "13" { print }'
     13 ?00:00:00 cpuhp/1
  ```

  And this is how the relevant part of `ps -AH` with the "killed"
  process looks like:

  ```
   5709 pts/11   00:00:00   firejail
   5710 pts/11   00:00:00 firejail
   5725 pts/11   00:00:00   bash
   5736 pts/11   00:56:49 firefox 
   5769 pts/11   00:00:24   tor
  ```

  EDIT: Launchpad doesn't preserve whitespace apparently, so I'm adding
  the output above as ps.log.

  I checked syslog and dmesg. Both of them have an interesting and
  identical message, which I add as dmesg.log.

  I also add the output of `cat /proc/version_signature` as version.log.

  I don't think `sudo lspci -vnvn` is relevant here, so I'm not gonna
  share it unless absolutely necessary.

  The crashed process will be there for something like 2 or 3 days at
  least (I don't restart my laptop often), so feel free to ask me to
  manipulate or query it somehow, if necessary.

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

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


[Kernel-packages] [Bug 1682041] onibi (amd64) - tests ran: 10, failed: 1

2017-04-15 Thread Brad Figg
tests ran:  10, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/onibi__4.4.0-74.95__2017-04-16_01-06-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/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


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

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

apport-collect 1683091

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

Title:
  The whole system froze for something like 30 seconds, then a process
  got killed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Upgraded from xenial to zesty recently.

  I was using a Firefox instance, one which is a part of Tor Browser
  Bundled. First, the application window grayed out, then the whole
  system froze for something like 30 seconds (I tried to switch to VT1
  to no avail), then the process got killed.

  Well, not exactly killed.

  The grayed-out window is still there, `xprop | grep PID` and clicking
  on it gives:

  ```
  _NET_WM_PID(CARDINAL) = 13
  ```

  PID 13 is a child of kthreadd:

  ```
  $ ps -A | awk '$1 == "13" { print }'
     13 ?00:00:00 cpuhp/1
  ```

  And this is how the relevant part of `ps -AH` with the "killed"
  process looks like:

  ```
   5709 pts/11   00:00:00   firejail
   5710 pts/11   00:00:00 firejail
   5725 pts/11   00:00:00   bash
   5736 pts/11   00:56:49 firefox 
   5769 pts/11   00:00:24   tor
  ```

  EDIT: Launchpad doesn't preserve whitespace apparently, so I'm adding
  the output above as ps.log.

  I checked syslog and dmesg. Both of them have an interesting and
  identical message, which I add as dmesg.log.

  I also add the output of `cat /proc/version_signature` as version.log.

  I don't think `sudo lspci -vnvn` is relevant here, so I'm not gonna
  share it unless absolutely necessary.

  The crashed process will be there for something like 2 or 3 days at
  least (I don't restart my laptop often), so feel free to ask me to
  manipulate or query it somehow, if necessary.

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

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


[Kernel-packages] [Bug 1683091] Re: The whole system froze for something like 30 seconds, then a process got killed

2017-04-15 Thread eeheeheeh
** Description changed:

  Upgraded from xenial to zesty recently.
  
  I was using a Firefox instance, one which is a part of Tor Browser
  Bundled. First, the application window grayed out, then the whole system
  froze for something like 30 seconds (I tried to switch to VT1 to no
  avail), then the process got killed.
  
  Well, not exactly killed.
  
  The grayed-out window is still there, `xprop | grep PID` and clicking on
  it gives:
  
  ```
  _NET_WM_PID(CARDINAL) = 13
  ```
  
  PID 13 is a child of kthreadd:
  
  ```
  $ ps -A | awk '$1 == "13" { print }'
-13 ?00:00:00 cpuhp/1
+    13 ?00:00:00 cpuhp/1
  ```
  
  And this is how the relevant part of `ps -AH` with the "killed" process
  looks like:
  
  ```
-  5709 pts/11   00:00:00   firejail
-  5710 pts/11   00:00:00 firejail
-  5725 pts/11   00:00:00   bash
-  5736 pts/11   00:56:49 firefox 
-  5769 pts/11   00:00:24   tor
+  5709 pts/11   00:00:00   firejail
+  5710 pts/11   00:00:00 firejail
+  5725 pts/11   00:00:00   bash
+  5736 pts/11   00:56:49 firefox 
+  5769 pts/11   00:00:24   tor
  ```
+ 
+ EDIT: Launchpad doesn't preserve whitespace apparently, so I'm adding
+ the output above as ps.log.
  
  I checked syslog and dmesg. Both of them have an interesting and
  identical message, which I add as dmesg.log.
  
  I also add the output of `cat /proc/version_signature` as version.log.
  
  I don't think `sudo lspci -vnvn` is relevant here, so I'm not gonna
  share it unless absolutely necessary.
  
  The crashed process will be there for something like 2 or 3 days at
  least (I don't restart my laptop often), so feel free to ask me to
  manipulate or query it somehow, if necessary.

** Attachment added: "ps.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683091/+attachment/4862905/+files/ps.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/1683091

Title:
  The whole system froze for something like 30 seconds, then a process
  got killed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Upgraded from xenial to zesty recently.

  I was using a Firefox instance, one which is a part of Tor Browser
  Bundled. First, the application window grayed out, then the whole
  system froze for something like 30 seconds (I tried to switch to VT1
  to no avail), then the process got killed.

  Well, not exactly killed.

  The grayed-out window is still there, `xprop | grep PID` and clicking
  on it gives:

  ```
  _NET_WM_PID(CARDINAL) = 13
  ```

  PID 13 is a child of kthreadd:

  ```
  $ ps -A | awk '$1 == "13" { print }'
     13 ?00:00:00 cpuhp/1
  ```

  And this is how the relevant part of `ps -AH` with the "killed"
  process looks like:

  ```
   5709 pts/11   00:00:00   firejail
   5710 pts/11   00:00:00 firejail
   5725 pts/11   00:00:00   bash
   5736 pts/11   00:56:49 firefox 
   5769 pts/11   00:00:24   tor
  ```

  EDIT: Launchpad doesn't preserve whitespace apparently, so I'm adding
  the output above as ps.log.

  I checked syslog and dmesg. Both of them have an interesting and
  identical message, which I add as dmesg.log.

  I also add the output of `cat /proc/version_signature` as version.log.

  I don't think `sudo lspci -vnvn` is relevant here, so I'm not gonna
  share it unless absolutely necessary.

  The crashed process will be there for something like 2 or 3 days at
  least (I don't restart my laptop often), so feel free to ask me to
  manipulate or query it somehow, if necessary.

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

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


[Kernel-packages] [Bug 1683091] Re: The whole system froze for something like 30 seconds, then a process got killed

2017-04-15 Thread eeheeheeh
** Attachment added: "dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683091/+attachment/4862903/+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/1683091

Title:
  The whole system froze for something like 30 seconds, then a process
  got killed

Status in linux package in Ubuntu:
  New

Bug description:
  Upgraded from xenial to zesty recently.

  I was using a Firefox instance, one which is a part of Tor Browser
  Bundled. First, the application window grayed out, then the whole
  system froze for something like 30 seconds (I tried to switch to VT1
  to no avail), then the process got killed.

  Well, not exactly killed.

  The grayed-out window is still there, `xprop | grep PID` and clicking
  on it gives:

  ```
  _NET_WM_PID(CARDINAL) = 13
  ```

  PID 13 is a child of kthreadd:

  ```
  $ ps -A | awk '$1 == "13" { print }'
 13 ?00:00:00 cpuhp/1
  ```

  And this is how the relevant part of `ps -AH` with the "killed"
  process looks like:

  ```
   5709 pts/11   00:00:00   firejail
   5710 pts/11   00:00:00 firejail
   5725 pts/11   00:00:00   bash
   5736 pts/11   00:56:49 firefox 
   5769 pts/11   00:00:24   tor
  ```

  I checked syslog and dmesg. Both of them have an interesting and
  identical message, which I add as dmesg.log.

  I also add the output of `cat /proc/version_signature` as version.log.

  I don't think `sudo lspci -vnvn` is relevant here, so I'm not gonna
  share it unless absolutely necessary.

  The crashed process will be there for something like 2 or 3 days at
  least (I don't restart my laptop often), so feel free to ask me to
  manipulate or query it somehow, if necessary.

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

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


[Kernel-packages] [Bug 1683091] Re: The whole system froze for something like 30 seconds, then a process got killed

2017-04-15 Thread eeheeheeh
** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683091/+attachment/4862904/+files/version.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/1683091

Title:
  The whole system froze for something like 30 seconds, then a process
  got killed

Status in linux package in Ubuntu:
  New

Bug description:
  Upgraded from xenial to zesty recently.

  I was using a Firefox instance, one which is a part of Tor Browser
  Bundled. First, the application window grayed out, then the whole
  system froze for something like 30 seconds (I tried to switch to VT1
  to no avail), then the process got killed.

  Well, not exactly killed.

  The grayed-out window is still there, `xprop | grep PID` and clicking
  on it gives:

  ```
  _NET_WM_PID(CARDINAL) = 13
  ```

  PID 13 is a child of kthreadd:

  ```
  $ ps -A | awk '$1 == "13" { print }'
 13 ?00:00:00 cpuhp/1
  ```

  And this is how the relevant part of `ps -AH` with the "killed"
  process looks like:

  ```
   5709 pts/11   00:00:00   firejail
   5710 pts/11   00:00:00 firejail
   5725 pts/11   00:00:00   bash
   5736 pts/11   00:56:49 firefox 
   5769 pts/11   00:00:24   tor
  ```

  I checked syslog and dmesg. Both of them have an interesting and
  identical message, which I add as dmesg.log.

  I also add the output of `cat /proc/version_signature` as version.log.

  I don't think `sudo lspci -vnvn` is relevant here, so I'm not gonna
  share it unless absolutely necessary.

  The crashed process will be there for something like 2 or 3 days at
  least (I don't restart my laptop often), so feel free to ask me to
  manipulate or query it somehow, if necessary.

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

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


[Kernel-packages] [Bug 1683091] [NEW] The whole system froze for something like 30 seconds, then a process got killed

2017-04-15 Thread eeheeheeh
Public bug reported:

Upgraded from xenial to zesty recently.

I was using a Firefox instance, one which is a part of Tor Browser
Bundled. First, the application window grayed out, then the whole system
froze for something like 30 seconds (I tried to switch to VT1 to no
avail), then the process got killed.

Well, not exactly killed.

The grayed-out window is still there, `xprop | grep PID` and clicking on
it gives:

```
_NET_WM_PID(CARDINAL) = 13
```

PID 13 is a child of kthreadd:

```
$ ps -A | awk '$1 == "13" { print }'
   13 ?00:00:00 cpuhp/1
```

And this is how the relevant part of `ps -AH` with the "killed" process
looks like:

```
 5709 pts/11   00:00:00   firejail
 5710 pts/11   00:00:00 firejail
 5725 pts/11   00:00:00   bash
 5736 pts/11   00:56:49 firefox 
 5769 pts/11   00:00:24   tor
```

I checked syslog and dmesg. Both of them have an interesting and
identical message, which I add as dmesg.log.

I also add the output of `cat /proc/version_signature` as version.log.

I don't think `sudo lspci -vnvn` is relevant here, so I'm not gonna
share it unless absolutely necessary.

The crashed process will be there for something like 2 or 3 days at
least (I don't restart my laptop often), so feel free to ask me to
manipulate or query it somehow, if necessary.

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

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

Title:
  The whole system froze for something like 30 seconds, then a process
  got killed

Status in linux package in Ubuntu:
  New

Bug description:
  Upgraded from xenial to zesty recently.

  I was using a Firefox instance, one which is a part of Tor Browser
  Bundled. First, the application window grayed out, then the whole
  system froze for something like 30 seconds (I tried to switch to VT1
  to no avail), then the process got killed.

  Well, not exactly killed.

  The grayed-out window is still there, `xprop | grep PID` and clicking
  on it gives:

  ```
  _NET_WM_PID(CARDINAL) = 13
  ```

  PID 13 is a child of kthreadd:

  ```
  $ ps -A | awk '$1 == "13" { print }'
 13 ?00:00:00 cpuhp/1
  ```

  And this is how the relevant part of `ps -AH` with the "killed"
  process looks like:

  ```
   5709 pts/11   00:00:00   firejail
   5710 pts/11   00:00:00 firejail
   5725 pts/11   00:00:00   bash
   5736 pts/11   00:56:49 firefox 
   5769 pts/11   00:00:24   tor
  ```

  I checked syslog and dmesg. Both of them have an interesting and
  identical message, which I add as dmesg.log.

  I also add the output of `cat /proc/version_signature` as version.log.

  I don't think `sudo lspci -vnvn` is relevant here, so I'm not gonna
  share it unless absolutely necessary.

  The crashed process will be there for something like 2 or 3 days at
  least (I don't restart my laptop often), so feel free to ask me to
  manipulate or query it somehow, if necessary.

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

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


[Kernel-packages] [Bug 1682041] onibi (i386) - tests ran: 7, failed: 0

2017-04-15 Thread Brad Figg
tests ran:   7, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/onibi__4.4.0-74.95__2017-04-15_23-50-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/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1682744] Re: Connecting to wifi 5GHz network causes iwlwifi firmware/driver error. Intel Wireless 7260

2017-04-15 Thread Piotr Dąbrowski
Related: https://bugzilla.kernel.org/show_bug.cgi?id=195299

** Bug watch added: Linux Kernel Bug Tracker #195299
   http://bugzilla.kernel.org/195299

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

Title:
  Connecting to wifi 5GHz network causes iwlwifi firmware/driver error.
  Intel Wireless 7260

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Only happens when connecting to 5GHz network, 2.5 GHz work fine.
  Network controller: Intel Corporation Wireless 7260 (rev 6b)

  iwlwifi :02:00.0: loaded firmware version 17.459231.0 op_mode
  iwlmvm

  
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4289] device 
(wlan0): Activation: starting connection 'NewHibernia5' 
(104460fe-9e5b-4a8c-8735-cfe48dec488e)
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4290] audit: 
op="connection-activate" uuid="104460fe-9e5b-4a8c-8735-cfe48dec488e" 
name="NewHibernia5" pid=7054 uid=1000 result="success"
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4291] device 
(wlan0): state change: disconnected -> prepare (reason 'none') [30 40 0]
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4293] 
manager: NetworkManager state is now CONNECTING
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4339] device 
(wlan0): set-hw-addr: set-cloned MAC address to E8:2A:EA:D4:16:6F (permanent)
  апр 14 10:32:34 liasus kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not 
ready
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4381] device 
(wlan0): state change: prepare -> config (reason 'none') [40 50 0]
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4383] device 
(wlan0): Activation: (wifi) access point 'NewHibernia5' has security, but 
secrets are required.
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4384] device 
(wlan0): state change: config -> need-auth (reason 'none') [50 60 0]
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4433] device 
(wlan0): state change: need-auth -> prepare (reason 'none') [60 40 0]
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4438] device 
(wlan0): state change: prepare -> config (reason 'none') [40 50 0]
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4450] device 
(wlan0): Activation: (wifi) connection 'NewHibernia5' has security, and secrets 
exist.  No new secrets needed.
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4451] 
Config: added 'ssid' value 'NewHibernia5'
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4451] 
Config: added 'scan_ssid' value '1'
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4452] 
Config: added 'key_mgmt' value 'WPA-PSK'
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4452] 
Config: added 'auth_alg' value 'OPEN'
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4452] 
Config: added 'psk' value ''
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4654] 
sup-iface[0x55900cef86c0,wlan0]: config: set interface ap_scan to 1
  апр 14 10:32:34 liasus wpa_supplicant[1923]: wlan0: SME: Trying to 
authenticate with e4:8d:8c:61:7d:04 (SSID='NewHibernia5' freq=5280 MHz)
  апр 14 10:32:34 liasus kernel: wlan0: authenticate with e4:8d:8c:61:7d:04
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: Microcode SW error 
detected.  Restarting 0x200.
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR values:
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: (2nd byte of 
CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:
CSR_HW_IF_CONFIG_REG: 0X40489204
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:  
CSR_INT_COALESCING: 0X8000ff40
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: 
CSR_INT: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:
CSR_INT_MASK: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:   
CSR_FH_INT_STATUS: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: 
CSR_GPIO_IN: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:   
CSR_RESET: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:
CSR_GP_CNTRL: 0X080403cd
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:  
CSR_HW_REV: 0X0144
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:  
CSR_EEPROM_REG: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:   
CSR_EEPROM_GP: 0X8000
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:  
CSR_OTP_GP_REG: 0X803a
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: 
CSR_GIO_REG: 0X001f0042
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: 

[Kernel-packages] [Bug 1682744] Re: Connecting to wifi 5GHz network causes iwlwifi firmware/driver error. Intel Wireless 7260

2017-04-15 Thread Piotr Dąbrowski
Connecting to 5GHz network also causes driver error on Intel(R) Dual
Band Wireless AC 7265, REV=0x210 (on Asus UX305FA). It seems like only
Ubuntu 17.04 is affected. I've tried the same on Ubuntu 16.10, Ubuntu
16.04 and Windows 10 - the problem does not occur on any of these.

I can upload more info if needed (but I could use some help on how to
gather it).

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

Title:
  Connecting to wifi 5GHz network causes iwlwifi firmware/driver error.
  Intel Wireless 7260

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Only happens when connecting to 5GHz network, 2.5 GHz work fine.
  Network controller: Intel Corporation Wireless 7260 (rev 6b)

  iwlwifi :02:00.0: loaded firmware version 17.459231.0 op_mode
  iwlmvm

  
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4289] device 
(wlan0): Activation: starting connection 'NewHibernia5' 
(104460fe-9e5b-4a8c-8735-cfe48dec488e)
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4290] audit: 
op="connection-activate" uuid="104460fe-9e5b-4a8c-8735-cfe48dec488e" 
name="NewHibernia5" pid=7054 uid=1000 result="success"
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4291] device 
(wlan0): state change: disconnected -> prepare (reason 'none') [30 40 0]
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4293] 
manager: NetworkManager state is now CONNECTING
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4339] device 
(wlan0): set-hw-addr: set-cloned MAC address to E8:2A:EA:D4:16:6F (permanent)
  апр 14 10:32:34 liasus kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not 
ready
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4381] device 
(wlan0): state change: prepare -> config (reason 'none') [40 50 0]
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4383] device 
(wlan0): Activation: (wifi) access point 'NewHibernia5' has security, but 
secrets are required.
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4384] device 
(wlan0): state change: config -> need-auth (reason 'none') [50 60 0]
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4433] device 
(wlan0): state change: need-auth -> prepare (reason 'none') [60 40 0]
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4438] device 
(wlan0): state change: prepare -> config (reason 'none') [40 50 0]
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4450] device 
(wlan0): Activation: (wifi) connection 'NewHibernia5' has security, and secrets 
exist.  No new secrets needed.
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4451] 
Config: added 'ssid' value 'NewHibernia5'
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4451] 
Config: added 'scan_ssid' value '1'
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4452] 
Config: added 'key_mgmt' value 'WPA-PSK'
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4452] 
Config: added 'auth_alg' value 'OPEN'
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4452] 
Config: added 'psk' value ''
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4654] 
sup-iface[0x55900cef86c0,wlan0]: config: set interface ap_scan to 1
  апр 14 10:32:34 liasus wpa_supplicant[1923]: wlan0: SME: Trying to 
authenticate with e4:8d:8c:61:7d:04 (SSID='NewHibernia5' freq=5280 MHz)
  апр 14 10:32:34 liasus kernel: wlan0: authenticate with e4:8d:8c:61:7d:04
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: Microcode SW error 
detected.  Restarting 0x200.
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR values:
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: (2nd byte of 
CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:
CSR_HW_IF_CONFIG_REG: 0X40489204
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:  
CSR_INT_COALESCING: 0X8000ff40
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: 
CSR_INT: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:
CSR_INT_MASK: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:   
CSR_FH_INT_STATUS: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: 
CSR_GPIO_IN: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:   
CSR_RESET: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:
CSR_GP_CNTRL: 0X080403cd
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:  
CSR_HW_REV: 0X0144
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:  
CSR_EEPROM_REG: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:   
CSR_EEPROM_GP: 0X8000
  апр 14 10:32:34 liasus kernel: iwlwifi 

[Kernel-packages] [Bug 1297286] Re: Wireless connection keeps disconnecting

2017-04-15 Thread gabybosetti
ALso in Ubuntu 17

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

Title:
  Wireless connection keeps disconnecting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have a wireless access point that is at most 2 meters away. It keeps
  disconnecting with no apparent reason. I read somewhere that setting a
  static ip should help with the problem, but the problem seems pretty
  persistent.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-19.39-lowlatency 3.13.6
  Uname: Linux 3.13.0-19-lowlatency x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 25 15:20:15 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-03-20 (5 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140319)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.245  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-03-23T16:50:07.398742
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   NETGEAR   74dc69be-e44f-4e15-a614-6c284d83d16b   
802-11-wireless   1395737193   Tue 25 Mar 2014 10:46:33 AM EETyes   
no /org/freedesktop/NetworkManager/Settings/2
   Wired connection 17ac79166-e72e-455b-ad9e-34574ee5d94e   
802-3-ethernet1395571025   Sun 23 Mar 2014 12:37:05 PM EETyes   
no /org/freedesktop/NetworkManager/Settings/1
   Egy Cloud 05f6b118-d332-4196-a7b0-810bba89bbf7   
802-11-wireless   1395753542   Tue 25 Mar 2014 03:19:02 PM EETyes   
no /org/freedesktop/NetworkManager/Settings/0
   AndroidAP 46037856-999f-4b3b-878d-13243f4ae958   
802-11-wireless   1395592043   Sun 23 Mar 2014 06:27:23 PM EETyes   
no /org/freedesktop/NetworkManager/Settings/3
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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


[Kernel-packages] [Bug 1682041] onibi (amd64) - tests ran: 20, failed: 0

2017-04-15 Thread Brad Figg
tests ran:  20, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/onibi__4.4.0-74.95__2017-04-15_22-30-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/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1682744] Re: Connecting to wifi 5GHz network causes iwlwifi firmware/driver error. Intel Wireless 7260

2017-04-15 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Connecting to wifi 5GHz network causes iwlwifi firmware/driver error.
  Intel Wireless 7260

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Only happens when connecting to 5GHz network, 2.5 GHz work fine.
  Network controller: Intel Corporation Wireless 7260 (rev 6b)

  iwlwifi :02:00.0: loaded firmware version 17.459231.0 op_mode
  iwlmvm

  
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4289] device 
(wlan0): Activation: starting connection 'NewHibernia5' 
(104460fe-9e5b-4a8c-8735-cfe48dec488e)
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4290] audit: 
op="connection-activate" uuid="104460fe-9e5b-4a8c-8735-cfe48dec488e" 
name="NewHibernia5" pid=7054 uid=1000 result="success"
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4291] device 
(wlan0): state change: disconnected -> prepare (reason 'none') [30 40 0]
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4293] 
manager: NetworkManager state is now CONNECTING
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4339] device 
(wlan0): set-hw-addr: set-cloned MAC address to E8:2A:EA:D4:16:6F (permanent)
  апр 14 10:32:34 liasus kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not 
ready
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4381] device 
(wlan0): state change: prepare -> config (reason 'none') [40 50 0]
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4383] device 
(wlan0): Activation: (wifi) access point 'NewHibernia5' has security, but 
secrets are required.
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4384] device 
(wlan0): state change: config -> need-auth (reason 'none') [50 60 0]
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4433] device 
(wlan0): state change: need-auth -> prepare (reason 'none') [60 40 0]
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4438] device 
(wlan0): state change: prepare -> config (reason 'none') [40 50 0]
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4450] device 
(wlan0): Activation: (wifi) connection 'NewHibernia5' has security, and secrets 
exist.  No new secrets needed.
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4451] 
Config: added 'ssid' value 'NewHibernia5'
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4451] 
Config: added 'scan_ssid' value '1'
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4452] 
Config: added 'key_mgmt' value 'WPA-PSK'
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4452] 
Config: added 'auth_alg' value 'OPEN'
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4452] 
Config: added 'psk' value ''
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4654] 
sup-iface[0x55900cef86c0,wlan0]: config: set interface ap_scan to 1
  апр 14 10:32:34 liasus wpa_supplicant[1923]: wlan0: SME: Trying to 
authenticate with e4:8d:8c:61:7d:04 (SSID='NewHibernia5' freq=5280 MHz)
  апр 14 10:32:34 liasus kernel: wlan0: authenticate with e4:8d:8c:61:7d:04
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: Microcode SW error 
detected.  Restarting 0x200.
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR values:
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: (2nd byte of 
CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:
CSR_HW_IF_CONFIG_REG: 0X40489204
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:  
CSR_INT_COALESCING: 0X8000ff40
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: 
CSR_INT: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:
CSR_INT_MASK: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:   
CSR_FH_INT_STATUS: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: 
CSR_GPIO_IN: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:   
CSR_RESET: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:
CSR_GP_CNTRL: 0X080403cd
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:  
CSR_HW_REV: 0X0144
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:  
CSR_EEPROM_REG: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:   
CSR_EEPROM_GP: 0X8000
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:  
CSR_OTP_GP_REG: 0X803a
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: 
CSR_GIO_REG: 0X001f0042
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:

[Kernel-packages] [Bug 1682041] onibi (i386) - tests ran: 1, failed: 0

2017-04-15 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/onibi__4.4.0-74.95__2017-04-15_22-04-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/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


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

2017-04-15 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/onibi__4.4.0-74.95__2017-04-15_21-36-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/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1682041] onibi (amd64) - tests ran: 64, failed: 0

2017-04-15 Thread Brad Figg
tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/onibi__4.4.0-74.95__2017-04-15_20-12-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/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1597961] Re: [Acer Aspire E5-573] Qualcomm Atheros Bluetooth 4.0 not working on [Ubuntu 16.04

2017-04-15 Thread Jordi Sayol
No news on it.

I fixed it replacing the "Qualcomm Atheros QCWB335 [168c:0036]" with the
"Qualcomm Atheros AR5B22 [168c:001c]". This one works like a charm out
of the box on Ubuntu 16.04LTS 64-bit.

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

Title:
  [Acer Aspire E5-573] Qualcomm Atheros Bluetooth 4.0 not working on
  [Ubuntu 16.04

Status in linux package in Ubuntu:
  Expired

Bug description:
  While using Windows with my Acer Aspire E5-573, I'm able to use the Bluetooth:
  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter [168c:0036] (rev 01)
Subsystem: Lite-On Communications Inc QCA9565 / AR9565 Wireless Network 
Adapter [11ad:0803]

  I've installed Ubuntu 16.04 in dual boot. While using Ubuntu, the
  Bluetooth adapter is the only piece of hardware that does not work.

  $ dmesg | grep -i bluetooth
  [   20.905534] Bluetooth: Core ver 2.21
  [   20.905548] Bluetooth: HCI device and connection manager initialized
  [   20.905551] Bluetooth: HCI socket layer initialized
  [   20.905553] Bluetooth: L2CAP socket layer initialized
  [   20.905557] Bluetooth: SCO socket layer initialized
  [   21.477624] Bluetooth: Can't change to loading configuration err
  [   21.477654] Bluetooth: Loading patch file failed
  [  124.347977] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [  124.347980] Bluetooth: BNEP filters: protocol multicast
  [  124.347985] Bluetooth: BNEP socket layer initialized

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vinicius   1913 F pulseaudio
   /dev/snd/controlC1:  vinicius   1913 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jun 30 22:27:24 2016
  HibernationDevice: RESUME=UUID=8ab51bc9-dd7d-4e30-9c74-696b6bb851ef
  InstallationDate: Installed on 2016-06-23 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Acer Aspire E5-573
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=216c2bbc-7194-46dc-929e-2a02be497343 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.37
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.37:bd02/16/2016:svnAcer:pnAspireE5-573:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-573
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1597961] Re: [Acer Aspire E5-573] Qualcomm Atheros Bluetooth 4.0 not working on [Ubuntu 16.04

2017-04-15 Thread Amjad Ali
Is there any update on this bug? I still can't use Bluetooth on my
laptop.

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

Title:
  [Acer Aspire E5-573] Qualcomm Atheros Bluetooth 4.0 not working on
  [Ubuntu 16.04

Status in linux package in Ubuntu:
  Expired

Bug description:
  While using Windows with my Acer Aspire E5-573, I'm able to use the Bluetooth:
  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter [168c:0036] (rev 01)
Subsystem: Lite-On Communications Inc QCA9565 / AR9565 Wireless Network 
Adapter [11ad:0803]

  I've installed Ubuntu 16.04 in dual boot. While using Ubuntu, the
  Bluetooth adapter is the only piece of hardware that does not work.

  $ dmesg | grep -i bluetooth
  [   20.905534] Bluetooth: Core ver 2.21
  [   20.905548] Bluetooth: HCI device and connection manager initialized
  [   20.905551] Bluetooth: HCI socket layer initialized
  [   20.905553] Bluetooth: L2CAP socket layer initialized
  [   20.905557] Bluetooth: SCO socket layer initialized
  [   21.477624] Bluetooth: Can't change to loading configuration err
  [   21.477654] Bluetooth: Loading patch file failed
  [  124.347977] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [  124.347980] Bluetooth: BNEP filters: protocol multicast
  [  124.347985] Bluetooth: BNEP socket layer initialized

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vinicius   1913 F pulseaudio
   /dev/snd/controlC1:  vinicius   1913 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jun 30 22:27:24 2016
  HibernationDevice: RESUME=UUID=8ab51bc9-dd7d-4e30-9c74-696b6bb851ef
  InstallationDate: Installed on 2016-06-23 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Acer Aspire E5-573
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=216c2bbc-7194-46dc-929e-2a02be497343 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.37
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.37:bd02/16/2016:svnAcer:pnAspireE5-573:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-573
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 403911] Re: bluez-simple-agent missing

2017-04-15 Thread Anthony Godshall
still an issue as of 16.10

root@tony-Satellite-S55t-C:~/ixxat# grep . /etc/issue
Ubuntu 16.10 \n \l

what's the problem here?  why is it dropped?

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

Title:
  bluez-simple-agent missing

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: bluez

  What else is there to say?

  Relevant to at least Intrepid and Jaunty, possibly many more.

  bluez-simple-agent is 3 kB in size, and a very important tool for
  binding (inserting PIN), when not using bluez-gnome (maybe one is
  limited to console only), or when bluez-gnome decides to use a random
  PIN (https://bugs.launchpad.net/ubuntu/+source/bluez-
  gnome/+bug/284994)

  It's a part of bluez package, so... was there a GOOD reason to drop it
  in the first place?

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

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


[Kernel-packages] [Bug 1676747] Re: Enable lspcon on i915

2017-04-15 Thread Kai-Heng Feng
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-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/1676747

Title:
  Enable lspcon on i915

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

Bug description:
  Some new machine comes with both HDMI and DP (not DP over TB), in this
  case, lspcon support is required to make HDMI work.

  The patch series cover letter has  more information:
  https://patchwork.freedesktop.org/series/4756/

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

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


[Kernel-packages] [Bug 1682041] onibi (amd64) - tests ran: 2, failed: 0

2017-04-15 Thread Brad Figg
tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/onibi__4.4.0-74.95__2017-04-15_19-17-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/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

2017-04-15 Thread Don Cady
4.8.0-48.51 -proposed works also. No regression this time.

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

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

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

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
  Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
  Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'
  Feb 21 07:17:03 orin kernel: [  190.637211] usbcore: registered new interface 
driver rtl8192cu
  Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status...
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7780] device 
(wlan0): driver supports Access Point (AP) mode
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7798] manager: 
(wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/4)
  Feb 21 07:17:03 orin kernel: [  190.648972] usbcore: registered new interface 
driver rtl8xxxu
  Feb 21 

[Kernel-packages] [Bug 1682041] onibi (i386) - tests ran: 141, failed: 0

2017-04-15 Thread Brad Figg
tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/onibi__4.4.0-74.95__2017-04-15_18-00-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/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool

2017-04-15 Thread Wei Sun
same issue. Annoying

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

Title:
  Dell Inspiron 7559 fans do not shut off once started, even when cool

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to
  be an issue with the fan control. When I first boot up the machine the
  fans are off. However, after the laptop warms up under normal usage,
  the fans kick on and then never shut off again.  Even when the CPU
  cools down to below 35c, the fans will continue to run.

  If I suspend the the laptop, and then immediately wake it up again
  then fans are once again off, until it warms up again.  So
  essentially, once the fans start they don't seem to ever shut off.

  Fans seem to work normally under Windows 10.  They turn on as needed,
  and then turn off once the laptop cools down.

  I've tried the various BIOS updates that Dell has released, without
  success. I am currently running Dell's latest BIOS for this laptop
  (v1.1.8)

  Below is the output of lm-sensors showing the fans running when the
  CPU is at a cool 35c

  dell_smm-virtual-0
  Adapter: Virtual device
  Processor Fan: 1925 RPM
  Processor Fan: 2143 RPM
  CPU:+35.0°C  
  GPU: +1.0°C  
  SODIMM: +49.0°C

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bob1709 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jul 13 19:18:45 2016
  HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77
  InstallationDate: Installed on 2016-07-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Inspiron 7559
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/17/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.8
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.1.8
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1682041] onibi (amd64) - tests ran: 141, failed: 0

2017-04-15 Thread Brad Figg
tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/onibi__4.4.0-74.95__2017-04-15_16-35-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/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1682704] Re: nvme controller is down will reset (regression in zesty on XPS laptop)

2017-04-15 Thread Shantanu Goel
This looks like a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 but someone
else should confirm.

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

Title:
  nvme controller is down will reset (regression in zesty on XPS laptop)

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  I've just upgraded a Dell XPS 15" (9550, early 2016 model) with a
  Samsung NVME drive. Machine was stable under Kubuntu 16.10 with the
  same drive. After the upgrade to Zesty I've now seen 3 hard lockups
  (machine loses root fs) with the following message printed:

  nvme controller is down will reset

  there are also messages printed to the virtual console reporting
  failure to write to the underlying disk from the home-directory encfs.

  Linux tass 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

  Ubuntu 17.04 (Kubuntu)

  dmesg about nvme:
  [1.748864] nvme nvme0: pci function :04:00.0
  [1.864553]  nvme0n1: p1 p2 p3 p4 p5 p6
  [2.961181] EXT4-fs (nvme0n1p6): mounted filesystem with ordered data 
mode. Opts: (null)
  [4.172546] EXT4-fs (nvme0n1p6): re-mounted. Opts: errors=remount-ro

  NVME cli shows 57 errors in the error-log, all seeming to be invalid
  field or invalid namespace. Not sure if that's since boot or since
  machine creation.

  Smartctrl shows...
  smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.10.0-19-generic] (local build)
  Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF INFORMATION SECTION ===
  Model Number:   PM951 NVMe SAMSUNG 512GB
  Serial Number:  S29PNXAH142328
  Firmware Version:   BXV77D0Q
  PCI Vendor/Subsystem ID:0x144d
  IEEE OUI Identifier:0x002538
  Controller ID:  1
  Number of Namespaces:   1
  Namespace 1 Size/Capacity:  512,110,190,592 [512 GB]
  Namespace 1 Utilization:365,503,283,200 [365 GB]
  Namespace 1 Formatted LBA Size: 512
  Local Time is:  Thu Apr 13 23:21:32 2017 EDT
  Firmware Updates (0x06):3 Slots
  Optional Admin Commands (0x0017):   Security Format Frmw_DL *Other*
  Optional NVM Commands (0x001f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
  Maximum Data Transfer Size: 32 Pages

  Supported Power States
  St Op Max   Active Idle   RL RT WL WT  Ent_Lat  Ex_Lat
   0 + 6.00W   --0  0  0  05   5
   1 + 4.20W   --1  1  1  1   30  30
   2 + 3.10W   --2  2  2  2  100 100
   3 -   0.0700W   --3  3  3  3  5005000
   4 -   0.0050W   --4  4  4  4 2000   22000

  Supported LBA Sizes (NSID 0x1)
  Id Fmt  Data  Metadt  Rel_Perf
   0 + 512   0 0

  === START OF SMART DATA SECTION ===
  SMART overall-health self-assessment test result: PASSED

  SMART/Health Information (NVMe Log 0x02, NSID 0x)
  Critical Warning:   0x00
  Temperature:35 Celsius
  Available Spare:100%
  Available Spare Threshold:  50%
  Percentage Used:0%
  Data Units Read:2,724,346 [1.39 TB]
  Data Units Written: 6,568,756 [3.36 TB]
  Host Read Commands: 52,921,997
  Host Write Commands:157,530,880
  Controller Busy Time:   1,349
  Power Cycles:   831
  Power On Hours: 5,358
  Unsafe Shutdowns:   46
  Media and Data Integrity Errors:0
  Error Information Log Entries:  57

  Error Information (NVMe Log 0x01, max 64 entries)
  Num   ErrCount  SQId   CmdId  Status  PELoc  LBA  NSIDVS
0 57 0  0x0004  0x4016  0x0000 1 -
1 56 0  0x0004  0x4016  0x0000 1 -
2 55 0  0x0004  0x4016  0x0000 1 -
3 54 0  0x0004  0x4016  0x0000 1 -
4 53 0  0x0004  0x4016  0x0000 1 -
5 52 0  0x0004  0x4016  0x0000 1 -
6 51 0  0x0004  0x4016  0x0000 1 -
7 50 0  0x0004  0x4016  0x0000 1 -
8 49 0  0x001f  0x4004  0x0000 0 -
9 48 0  0x001e  0x4004  0x0000 0 -
   10 47 0  0x001f  0x4004  0x0000 0 -
   11 46 0  0x001e  0x4004  0x0000 0 -
   12 45 0  0x001f  0x4004  0x0000 0 -
   13 44 0  0x001e  0x4004  0x0000 0 -

[Kernel-packages] [Bug 1682041] onibi (i386) - tests ran: 19, failed: 0

2017-04-15 Thread Brad Figg
tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/onibi__4.4.0-74.95__2017-04-15_15-20-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/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1670508] Re: CIFS: Enable encryption for SMB3

2017-04-15 Thread Pavel Shilovsky
Successfully tested the patched kernel for Xenial with xfstests and
cthon test suites.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.2 LTS
Release:16.04
Codename:   xenial

$ uname -a
Linux ubuntu-vm 4.4.0-71-generic #92~lp1670508 SMP Fri Mar 24 19:02:19 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  CIFS: Enable encryption for SMB3

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  Fix Released

Bug description:
  There has been work upstream to enable encryption support for SMB3
  connections. This is a particularly valuable (and commonly requested)
  feature with the Azure Files service as encryption is required to
  connect to an Azure Files storage share from on-prem or from a
  different Azure region.

  The relevant commits are as follows:

  CIFS: Fix possible use after free in demultiplex thread
  Commit 61cfac6f267dabcf2740a7ec8a0295833b28b5f5

  CIFS: Allow to switch on encryption with seal mount option
  Commit ae6f8dd4d0c87bfb72da9d9b56342adf53e69c31

  CIFS: Add capability to decrypt big read responses
  Commit c42a6abe3012832a68a371dabe17c2ced97e62ad

  CIFS: Decrypt and process small encrypted packets
  Commit 4326ed2f6a16ae9d33e4209b540dc9a371aba840

  CIFS: Add copy into pages callback for a read operation
  Commit d70b9104b1ca586f73aaf59426756cec3325a40e

  CIFS: Add mid handle callback
  Commit 9b7c18a2d4b798963ea80f6769701dcc4c24b55e

  CIFS: Add transform header handling callbacks
  Commit 9bb17e0916a03ab901fb684e874d77a1e96b3d1e

  CIFS: Encrypt SMB3 requests before sending
  Commit 026e93dc0a3eefb0be060bcb9ecd8d7a7fd5c398

  CIFS: Enable encryption during session setup phase
  Commit cabfb3680f78981d26c078a26e5c748531257ebb

  CIFS: Add capability to transform requests before sending
  Commit 7fb8986e7449d0a5cebd84d059927afa423fbf85

  CIFS: Separate RFC1001 length processing for SMB2 read
  Commit b8f57ee8aad414a3122bff72d7968a94baacb9b6

  CIFS: Separate SMB2 sync header processing
  Commit cb200bd6264a80c04e09e8635fa4f3901cabdaef

  CIFS: Send RFC1001 length in a separate iov
  Commit 738f9de5cdb9175c19d24cfdf90b4543fc3b47bf

  CIFS: Make send_cancel take rqst as argument
  Commit fb2036d817584df42504910fe104f68517e8990e

  CIFS: Make SendReceive2() takes resp iov
  Commit da502f7df03d2d0b416775f92ae022f3f82bedd5

  CIFS: Separate SMB2 header structure
  Commit 31473fc4f9653b73750d3792ffce6a6e1bdf0da7

  cifs: Add soft dependencies
  Commit b9be76d585d48cb25af8db0d35e1ef9030fbe13a

  cifs: Only select the required crypto modules
  Commit 3692304bba6164be3810afd41b84ecb0e1e41db1

  cifs: Simplify SMB2 and SMB311 dependencies
  Commit c1ecea87471bbb614f8121e00e5787f363140365

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

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


[Kernel-packages] [Bug 1682041] onibi (amd64) - tests ran: 19, failed: 1

2017-04-15 Thread Brad Figg
tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/onibi__4.4.0-74.95__2017-04-15_14-05-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/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1633839] Re: No symbol table. Press any key to continue

2017-04-15 Thread Paul Matthijsse
*** This bug is a duplicate of bug 1620678 ***
https://bugs.launchpad.net/bugs/1620678

My root partition is on /dev/sdb.
So changing the above command into 

sudo grub-install /dev/sdb
sudo update-grub
sudo reboot

did the trick.

By the way, fresh install of Xubuntu 17.04 on reformatted partition.
This bug stems from upgrading Xubuntu 16.04 to 16.10 and it apparently
survived the formatting process.

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

Title:
  No symbol table. Press any key to continue

Status in grub2 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.10. shows "error: no symbol table. Press any key to
  continue..." after Kernel boot and before login screen. After pressing
  a key or waiting a few seconds, the boot process continues and login
  screen appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-22-generic 4.8.0-22.24
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:     7722 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Oct 16 13:25:22 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=9d3bac9d-90f6-4fb6-ba39-e08ea2c3aa19
  InstallationDate: Installed on 2013-10-28 (1083 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 23255B2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=3b21f524-fe80-4ab0-8b84-c03e44abcd8b ro elevator=deadline
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (0 days ago)
  dmi.bios.date: 03/03/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA6WW (2.66 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23255B2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: CS023589
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:pn23255B2:pvrThinkPadX230:rvnLENOVO:rn23255B2:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 23255B2
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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


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

2017-04-15 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/1682230

Title:
  Wifi usb stick and cordless keyboard and mouse freeze system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  For kernels 4.4, using a usb wifi dongle (0bda:8178 Realtek Semiconductor 
Corp. RTL8192CU 802.11n WLAN Adapter) and a cordless mouse/keyboard (1d57:fa20 
Xenta ) freeze the system.
  With 4.8.0-36 kernel, all is fine. 
  With update 4.8.0-46, the system freeze.

  lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alain  1671 F pulseaudio
   /dev/snd/controlC0:  alain  1671 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8185182f-9ef4-421b-afca-6589e86759dc
  InstallationDate: Installed on 2017-04-09 (3 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=4d6d30b5-6ba4-4b58-b88f-62b2ea234e34 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 01/19/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: F2A78M-HD2
  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:bd01/19/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-HD2: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/1682230/+subscriptions

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


[Kernel-packages] [Bug 1682230] Re: Wifi usb stick and cordless keyboard and mouse freeze system

2017-04-15 Thread Alain Le Dilosquer
** Changed in: linux (Ubuntu)
   Status: Incomplete => New

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

Title:
  Wifi usb stick and cordless keyboard and mouse freeze system

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,
  For kernels 4.4, using a usb wifi dongle (0bda:8178 Realtek Semiconductor 
Corp. RTL8192CU 802.11n WLAN Adapter) and a cordless mouse/keyboard (1d57:fa20 
Xenta ) freeze the system.
  With 4.8.0-36 kernel, all is fine. 
  With update 4.8.0-46, the system freeze.

  lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alain  1671 F pulseaudio
   /dev/snd/controlC0:  alain  1671 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8185182f-9ef4-421b-afca-6589e86759dc
  InstallationDate: Installed on 2017-04-09 (3 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=4d6d30b5-6ba4-4b58-b88f-62b2ea234e34 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 01/19/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: F2A78M-HD2
  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:bd01/19/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-HD2: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/1682230/+subscriptions

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


[Kernel-packages] [Bug 1682892] Re: failed command: READ FPDMA QUEUED

2017-04-15 Thread xenus
Kernel param set but still seeing the issue:

Apr 15 10:08:58 mark-linux kernel: [3.467285] ata3.00: FORCE: horkage 
modified (noncq)
Apr 15 10:08:58 mark-linux kernel: [3.467531] ata3.00: ATA-9: 
ST2000DX001-1CM164, CC43, max UDMA/133
Apr 15 10:08:58 mark-linux kernel: [3.467532] ata3.00: 3907029168 sectors, 
multi 0: LBA48 NCQ (not used)
Apr 15 10:08:58 mark-linux kernel: [3.500871] ata3.00: configured for 
UDMA/133
Apr 15 10:08:58 mark-linux kernel: [3.501102] scsi 2:0:0:0: Direct-Access   
  ATA  ST2000DX001-1CM1 CC43 PQ: 0 ANSI: 5


Apr 15 12:37:06 mark-linux kernel: [ 8937.088290] ata3.00: exception Emask 0x0 
SAct 0x0 SErr 0x0 action 0x6
Apr 15 12:37:06 mark-linux kernel: [ 8937.088297] ata3.00: irq_stat 0x4001
Apr 15 12:37:06 mark-linux kernel: [ 8937.088302] ata3.00: failed command: READ 
DMA EXT
Apr 15 12:37:06 mark-linux kernel: [ 8937.088311] ata3.00: cmd 
25/00:08:16:af:10/00:00:30:00:00/e0 tag 18 dma 4096 in
Apr 15 12:37:06 mark-linux kernel: [ 8937.088311]  res 
51/84:00:16:af:10/00:00:30:00:00/00 Emask 0x10 (ATA bus error)
Apr 15 12:37:06 mark-linux kernel: [ 8937.088316] ata3.00: status: { DRDY ERR }
Apr 15 12:37:06 mark-linux kernel: [ 8937.088319] ata3.00: error: { ICRC ABRT }
Apr 15 12:37:06 mark-linux kernel: [ 8937.088324] ata3: hard resetting link
Apr 15 12:37:07 mark-linux kernel: [ 8937.564284] ata3: SATA link up 6.0 Gbps 
(SStatus 133 SControl 300)
Apr 15 12:37:07 mark-linux kernel: [ 8937.644128] ata3.00: configured for 
UDMA/133
Apr 15 12:37:07 mark-linux kernel: [ 8937.644282] ata3: EH complete
Apr 15 13:42:24 mark-linux kernel: [12854.761799] ata3.00: exception Emask 0x0 
SAct 0x0 SErr 0x0 action 0x6 frozen
Apr 15 13:42:24 mark-linux kernel: [12854.761814] ata3.00: failed command: 
WRITE DMA EXT
Apr 15 13:42:24 mark-linux kernel: [12854.761830] ata3.00: cmd 
35/00:b8:07:e0:58/00:00:71:00:00/e0 tag 15 dma 94208 out
Apr 15 13:42:24 mark-linux kernel: [12854.761830]  res 
40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
Apr 15 13:42:24 mark-linux kernel: [12854.761839] ata3.00: status: { DRDY }
Apr 15 13:42:24 mark-linux kernel: [12854.761848] ata3: hard resetting link
Apr 15 13:42:34 mark-linux kernel: [12864.762972] ata3: softreset failed (1st 
FIS failed)
Apr 15 13:42:34 mark-linux kernel: [12864.762986] ata3: hard resetting link
Apr 15 13:42:44 mark-linux kernel: [12874.762852] ata3: softreset failed (1st 
FIS failed)
Apr 15 13:42:44 mark-linux kernel: [12874.762866] ata3: hard resetting link
Apr 15 13:43:19 mark-linux kernel: [12909.763715] ata3: softreset failed (1st 
FIS failed)
Apr 15 13:43:19 mark-linux kernel: [12909.763730] ata3: limiting SATA link 
speed to 3.0 Gbps
Apr 15 13:43:19 mark-linux kernel: [12909.763734] ata3: hard resetting link
Apr 15 13:43:24 mark-linux kernel: [12914.979066] ata3: SATA link up 3.0 Gbps 
(SStatus 123 SControl 320)
Apr 15 13:43:24 mark-linux kernel: [12914.979073] ata3.00: link online but 
device misclassified
Apr 15 13:43:29 mark-linux kernel: [12920.031161] ata3.00: qc timeout (cmd 0xec)
Apr 15 13:43:29 mark-linux kernel: [12920.031174] ata3.00: failed to IDENTIFY 
(I/O error, err_mask=0x4)
Apr 15 13:43:29 mark-linux kernel: [12920.031178] ata3.00: revalidation failed 
(errno=-5)
Apr 15 13:43:29 mark-linux kernel: [12920.031191] ata3: hard resetting link
Apr 15 13:43:39 mark-linux kernel: [12930.031937] ata3: softreset failed (1st 
FIS failed)
Apr 15 13:43:39 mark-linux kernel: [12930.031951] ata3: hard resetting link
Apr 15 13:43:49 mark-linux kernel: [12940.032465] ata3: softreset failed (1st 
FIS failed)
Apr 15 13:43:49 mark-linux kernel: [12940.032479] ata3: hard resetting link
Apr 15 13:44:24 mark-linux kernel: [12975.033296] ata3: softreset failed (1st 
FIS failed)
Apr 15 13:44:24 mark-linux kernel: [12975.033311] ata3: limiting SATA link 
speed to 1.5 Gbps
Apr 15 13:44:24 mark-linux kernel: [12975.033315] ata3: hard resetting link
Apr 15 13:44:29 mark-linux kernel: [12980.244430] ata3: SATA link up 1.5 Gbps 
(SStatus 113 SControl 310)
Apr 15 13:44:29 mark-linux kernel: [12980.244437] ata3.00: link online but 
device misclassified
Apr 15 13:44:40 mark-linux kernel: [12990.432579] ata3.00: qc timeout (cmd 0xec)
Apr 15 13:44:40 mark-linux kernel: [12990.432591] ata3.00: failed to IDENTIFY 
(I/O error, err_mask=0x4)
Apr 15 13:44:40 mark-linux kernel: [12990.432595] ata3.00: revalidation failed 
(errno=-5)
Apr 15 13:44:40 mark-linux kernel: [12990.432610] ata3: hard resetting link
Apr 15 13:44:50 mark-linux kernel: [13000.433388] ata3: softreset failed (1st 
FIS failed)
Apr 15 13:44:50 mark-linux kernel: [13000.433402] ata3: hard resetting link
Apr 15 13:45:00 mark-linux kernel: [13010.433808] ata3: softreset failed (1st 
FIS failed)
Apr 15 13:45:00 mark-linux kernel: [13010.433823] ata3: hard resetting link
Apr 15 13:45:11 mark-linux kernel: [13022.309318] ata3: SATA link up 1.5 Gbps 
(SStatus 113 SControl 310)
Apr 15 13:45:12 mark-linux kernel: [13022.449662] ata3.00: configured 

[Kernel-packages] [Bug 1682041] onibi (i386) - tests ran: 4, failed: 1

2017-04-15 Thread Brad Figg
tests ran:   4, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/onibi__4.4.0-74.95__2017-04-15_12-12-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/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1539843] Re: External microphone does not work

2017-04-15 Thread Mikhail Paulyshka
Upstream bugreport: https://bugzilla.kernel.org/show_bug.cgi?id=195437

** Bug watch added: Linux Kernel Bug Tracker #195437
   http://bugzilla.kernel.org/195437

** Summary changed:

- External microphone does not work
+ Asus N551/N751: external microphone does not work

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

Title:
  Asus N551/N751: external microphone does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asus N551JM
  In this laptop is combined jack for microphone and headphone. I use headset 
A4Tech Bloody G500 that nice work in Windows. But in KUBUNTU 15.10 and ubuntu 
14.04/15.10 they do not work (work only as headphone). System don't see that i 
connected headset and in pavucontrol i see only embeded in laptop microphone.
  http://www.alsa-project.org/db/?f=bcf71e457acf21a40799621a85a53e5817f829f9
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mogost 1348 F pulseaudio
   /dev/snd/controlC1:  mogost 1348 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=d1115de1-e4fd-4119-8d26-79091505b000
  InstallationDate: Installed on 2016-01-30 (0 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: ASUSTeK COMPUTER INC. N551JM
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_EN.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic.efi.signed 
root=UUID=b7b85f18-8c88-4443-8a59-2b3a93642c97 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-generic N/A
   linux-backports-modules-4.2.0-25-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N551JM.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N551JM
  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.:bvrN551JM.204:bd10/06/2014:svnASUSTeKCOMPUTERINC.:pnN551JM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N551JM
  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/1539843/+subscriptions

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


[Kernel-packages] [Bug 1675473] Re: Tablet pressure sensitivy doesn't xork for non-wacom tablet since the 16.04

2017-04-15 Thread Imerion
Indeed, it works again in Ubuntu 17.04! Nice!

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

Title:
  Tablet pressure sensitivy doesn't xork for non-wacom tablet since the
  16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am unable to work with Ubuntu and Blender since one year, because
  since the 16.04 my Huion Tablet (GT-220 screen tablet) doesn't detect
  the pressure sensitivity and it worked before.

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

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


[Kernel-packages] [Bug 1658345] Re: Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10

2017-04-15 Thread Keary Parinis
Hey Just Bob. It may help if you indicate that the bug affects you in
the section above. May also help if you send Ubuntu bug info via apport.
Hopefully, we can raise the profile on this bug and get it fixed. Thx.

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

Title:
  Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 16.10 on my Lenovo Ideapad Flex 4 laptop. Ubuntu does not 
recognize the touchpad (it does recognize the touch screen nicely though). When 
I run xinput -list, I do not see the touchpad. I dual boot with Windows 10, 
which recognizes the touchpad from Elantech. I searched online for days and I 
found Elantech drivers for Ubuntu 14.04, however, I was unable to load older 
versions of Ubuntu on my laptop. Do you expect to support the Elantech touchpad 
in future updates? I attached a screen shot of my xinput -list output. Please 
let me know if you require any additional information. Thank you.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  keary  2345 F pulseaudio
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=dbfec3b4-a8be-406e-9f39-5258c004c656
  InstallationDate: Installed on 2017-01-18 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57fc Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80U3
  Package: linux (not installed)
  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-34-generic.efi.signed 
root=UUID=5be7438e-36fd-4960-a4cd-2371715adfa2 ro quiet splash i8042.kbdreset=1 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  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-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.8.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2MCN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Sofia-F
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J91204WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad FLEX 4-1130
  dmi.modalias: 
dmi:bvnLENOVO:bvr2MCN24WW:bd11/01/2016:svnLENOVO:pn80U3:pvrLenovoideapadFLEX4-1130:rvnLENOVO:rnSofia-F:rvrSDK0J91204WIN:cvnLENOVO:ct10:cvrLenovoideapadFLEX4-1130:
  dmi.product.name: 80U3
  dmi.product.version: Lenovo ideapad FLEX 4-1130
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1539843] Re: External microphone does not work

2017-04-15 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

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

Title:
  External microphone does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asus N551JM
  In this laptop is combined jack for microphone and headphone. I use headset 
A4Tech Bloody G500 that nice work in Windows. But in KUBUNTU 15.10 and ubuntu 
14.04/15.10 they do not work (work only as headphone). System don't see that i 
connected headset and in pavucontrol i see only embeded in laptop microphone.
  http://www.alsa-project.org/db/?f=bcf71e457acf21a40799621a85a53e5817f829f9
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mogost 1348 F pulseaudio
   /dev/snd/controlC1:  mogost 1348 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=d1115de1-e4fd-4119-8d26-79091505b000
  InstallationDate: Installed on 2016-01-30 (0 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: ASUSTeK COMPUTER INC. N551JM
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_EN.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic.efi.signed 
root=UUID=b7b85f18-8c88-4443-8a59-2b3a93642c97 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-generic N/A
   linux-backports-modules-4.2.0-25-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N551JM.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N551JM
  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.:bvrN551JM.204:bd10/06/2014:svnASUSTeKCOMPUTERINC.:pnN551JM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N551JM
  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/1539843/+subscriptions

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


[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

2017-04-15 Thread Gabi Dumi
I got it to work too on my Gigabyte AB350M Gaming 3 + Ryzen 1700 +nvidia 750.
Installed Ubuntu Mate 16.04.01 (that was on kernel 4.4.0) - this worked 
reasonably well, some errors popped up from time to time (eg. USB 3.0 stick was 
unmounting then auto-remounting from time to time, also compiling the kernel I 
got a seg fault from cc - don't know if it's related).
I downloaded the zesty kernel and used the instructions above to configure 
(disabled AMD GPIO pin control as mentioned above) compile and install 4.10.0. 
Compilation went ok (except the seg fault I mentioned and some packages I had 
to manually install) all 16 threads where at 60-70% when compiling.
Now I'm running 4.10.0-19 with seemingly no problems, everything seems to work 
including nvidia drivers  375.39, sound through hdmi, network, usb. No errors 
yet.
I'm not a linux expert by any means so there might still be problems I haven't 
discovered.

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

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1682041] onibi (amd64) - tests ran: 34, failed: 4

2017-04-15 Thread Brad Figg
tests ran:  34, failed: 4;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/onibi__4.4.0-74.95__2017-04-15_11-10-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/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1682041] rumford (amd64) - tests ran: 64, failed: 0

2017-04-15 Thread Brad Figg
tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/rumford__4.4.0-74.95__2017-04-15_11-02-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/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1680735] gonzo (i386) - tests ran: 141, failed: 0

2017-04-15 Thread Brad Figg
tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164~precise1-generic/gonzo__3.13.0-117.164~precise1__2017-04-15_10-36-00/results-index.html

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

Title:
  linux-lts-trusty: 3.13.0-117.164~precise1 -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:
  Confirmed
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the  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 --
  kernel-stable-master-bug: 1680733
  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/1680735/+subscriptions

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


[Kernel-packages] [Bug 1682041] onibi (i386) - tests ran: 10, failed: 1

2017-04-15 Thread Brad Figg
tests ran:  10, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/onibi__4.4.0-74.95__2017-04-15_09-38-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/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1539843] Re: External microphone does not work

2017-04-15 Thread Mikhail Paulyshka
Proposed patch for Linux Kernel (diff from 4.10.0-19)

** Patch added: "Fix ASUS N551JM headset microphone detection"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1539843/+attachment/4862527/+files/asus-n551jm-headset-fix.diff

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

Title:
  External microphone does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asus N551JM
  In this laptop is combined jack for microphone and headphone. I use headset 
A4Tech Bloody G500 that nice work in Windows. But in KUBUNTU 15.10 and ubuntu 
14.04/15.10 they do not work (work only as headphone). System don't see that i 
connected headset and in pavucontrol i see only embeded in laptop microphone.
  http://www.alsa-project.org/db/?f=bcf71e457acf21a40799621a85a53e5817f829f9
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mogost 1348 F pulseaudio
   /dev/snd/controlC1:  mogost 1348 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=d1115de1-e4fd-4119-8d26-79091505b000
  InstallationDate: Installed on 2016-01-30 (0 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: ASUSTeK COMPUTER INC. N551JM
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_EN.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic.efi.signed 
root=UUID=b7b85f18-8c88-4443-8a59-2b3a93642c97 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-generic N/A
   linux-backports-modules-4.2.0-25-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N551JM.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N551JM
  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.:bvrN551JM.204:bd10/06/2014:svnASUSTeKCOMPUTERINC.:pnN551JM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N551JM
  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/1539843/+subscriptions

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


[Kernel-packages] [Bug 1682041] rumford (amd64) - tests ran: 2, failed: 0

2017-04-15 Thread Brad Figg
tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/rumford__4.4.0-74.95__2017-04-15_10-27-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/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1680735] gonzo (amd64) - tests ran: 141, failed: 0

2017-04-15 Thread Brad Figg
tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164~precise1-generic/gonzo__3.13.0-117.164~precise1__2017-04-15_09-28-00/results-index.html

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

Title:
  linux-lts-trusty: 3.13.0-117.164~precise1 -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:
  Confirmed
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the  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 --
  kernel-stable-master-bug: 1680733
  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/1680735/+subscriptions

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


[Kernel-packages] [Bug 1682041] rumford (amd64) - tests ran: 141, failed: 0

2017-04-15 Thread Brad Figg
tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/rumford__4.4.0-74.95__2017-04-15_09-15-00/results-index.html

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

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1682999] Re: Ubuntu crashes on Intel j4205 Apollo Lake

2017-04-15 Thread Wojciech Pietruszewski
** Tags added: apollo-lake

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

Title:
  Ubuntu crashes on Intel j4205 Apollo Lake

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 17.04 on ASRock j4205-ITX with BIOS v1.20. ASRock
  states that this platform is supported by Ubuntu 16.10 but after
  installation it kept freezing after few minuts. There was no trace of
  error in dmesg nor in any log. Not even a crashdump. After
  installation of Ubuntu 17.04 I was able to see an error:

  Apr 14 20:40:12 server kernel: BUG: unable to handle kernel paging request at 
af7b244c32d0
  Apr 14 20:40:12 server kernel: IP: xfsaild+0x12f/0x750 [xfs]
  Apr 14 20:40:12 server kernel: PGD 0 
  Apr 14 20:40:13 server kernel: 
  Apr 14 20:40:13 server kernel: Oops:  [#1] SMP
  Apr 14 20:40:13 server kernel: Modules linked in: intel_rapl 
intel_telemetry_pltdrv intel_pmc_ipc intel_punit_ipc intel_telemetry_core 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
intel_rapl_perf mei_me mei shpchp
  Apr 14 20:40:13 server kernel:  glue_helper ahci i2c_hid cryptd mii libahci 
drm hid video fjes pinctrl_broxton pinctrl_intel
  Apr 14 20:40:13 server kernel: CPU: 1 PID: 402 Comm: xfsaild/md1 Not tainted 
4.10.0-19-generic #21-Ubuntu
  Apr 14 20:40:13 server kernel: Hardware name: To Be Filled By O.E.M. To Be 
Filled By O.E.M./J4205-ITX, BIOS P1.20 12/16/2016
  Apr 14 20:40:13 server kernel: task: 8f7b24718000 task.stack: 
ba8581edc000
  Apr 14 20:40:13 server kernel: RIP: 0010:xfsaild+0x12f/0x750 [xfs]
  Apr 14 20:40:13 server kernel: RSP: 0018:ba8581edfe50 EFLAGS: 00010246
  Apr 14 20:40:13 server kernel: RAX:  RBX: 8f7b24718000 
RCX: 
  Apr 14 20:40:13 server kernel: RDX: 8000 RSI: 0246 
RDI: 0246
  Apr 14 20:40:13 server kernel: RBP: ba8581edfef8 R08:  
R09: 
  Apr 14 20:40:13 server kernel: R10: 08eb R11: 0920 
R12: b1499b24
  Apr 14 20:40:13 server kernel: R13: af7b244c3280 R14: 8f7b280bf5a0 
R15: 8f7b24309000
  Apr 14 20:40:13 server kernel: FS:  () 
GS:8f7b3fc8() knlGS:
  Apr 14 20:40:13 server kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Apr 14 20:40:13 server kernel: CR2: af7b244c32d0 CR3: 000237c09000 
CR4: 003406e0
  Apr 14 20:40:13 server kernel: Call Trace:
  Apr 14 20:40:13 server kernel:  kthread+0x101/0x140
  Apr 14 20:40:13 server kernel:  ? xfs_trans_ail_cursor_first+0x90/0x90 [xfs]
  Apr 14 20:40:13 server kernel:  ? kthread_create_on_node+0x60/0x60
  Apr 14 20:40:13 server kernel:  ret_from_fork+0x2c/0x40
  Apr 14 20:40:13 server kernel: Code: f0 49 c7 c4 24 9b 49 b1 85 c0 0f 85 05 
05 00 00 48 c7 43 08 00 00 00 00 e8 1f 96 3e f0 8b 05 ed 40 db f0 85 c0 0f 85 
1b 05 00 00 <41> 8b 45 50 4d 8b 75 00 85 c0 74 60 49 83 7d 48 00 75 59 49 8d 
  Apr 14 20:40:13 server kernel: RIP: xfsaild+0x12f/0x750 [xfs] RSP: 
ba8581edfe50
  Apr 14 20:40:13 server kernel: CR2: af7b244c32d0
  Apr 14 20:40:13 server kernel: ---[ end trace a03641228bdafba1 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 14 21:31 seq
   crw-rw 1 root audio 116, 33 Apr 14 21:31 timer
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.10.0-19-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Sat Apr 15 09:16:45 2017
  HibernationDevice: RESUME=UUID=2b9241db-ccc7-4811-8812-ff375b7adcc2
  InstallationDate: Installed on 2017-04-13 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic 
root=UUID=42129163-ff0a-40df-a4c2-9918862de656 ro console=tty0 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   

[Kernel-packages] [Bug 1680735] gonzo (i386) - tests ran: 2, failed: 0

2017-04-15 Thread Brad Figg
tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164~precise1-generic/gonzo__3.13.0-117.164~precise1__2017-04-15_09-08-00/results-index.html

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

Title:
  linux-lts-trusty: 3.13.0-117.164~precise1 -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:
  Confirmed
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the  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 --
  kernel-stable-master-bug: 1680733
  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/1680735/+subscriptions

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


[Kernel-packages] [Bug 1682041] onibi (amd64) - tests ran: 10, failed: 1

2017-04-15 Thread Brad Figg
tests ran:  10, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/onibi__4.4.0-74.95__2017-04-15_08-06-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/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1680735] gonzo (amd64) - tests ran: 2, failed: 0

2017-04-15 Thread Brad Figg
tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164~precise1-generic/gonzo__3.13.0-117.164~precise1__2017-04-15_08-47-00/results-index.html

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

Title:
  linux-lts-trusty: 3.13.0-117.164~precise1 -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:
  Confirmed
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the  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 --
  kernel-stable-master-bug: 1680733
  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/1680735/+subscriptions

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


[Kernel-packages] [Bug 1682041] rumford (amd64) - tests ran: 19, failed: 0

2017-04-15 Thread Brad Figg
tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/rumford__4.4.0-74.95__2017-04-15_07-53-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/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1680735] gonzo (i386) - tests ran: 1, failed: 0

2017-04-15 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164~precise1-generic/gonzo__3.13.0-117.164~precise1__2017-04-15_08-29-00/results-index.html

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

Title:
  linux-lts-trusty: 3.13.0-117.164~precise1 -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:
  Confirmed
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the  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 --
  kernel-stable-master-bug: 1680733
  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/1680735/+subscriptions

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


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

2017-04-15 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164~precise1-generic/gonzo__3.13.0-117.164~precise1__2017-04-15_08-08-00/results-index.html

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

Title:
  linux-lts-trusty: 3.13.0-117.164~precise1 -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:
  Confirmed
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the  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 --
  kernel-stable-master-bug: 1680733
  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/1680735/+subscriptions

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


[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive

2017-04-15 Thread Kai-Heng Feng
Yes, can you try 6000 again? 3000 doesn't make it enters to PS3. My bad.

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

Title:
  APST quirk needed for Samsung 512GB NVMe drive

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  APST support just landed in the latest Zesty kernel (4.10.0-14.16) as
  part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602.
  That patch has a quirk for certain 256GB Samsung drives found in Dell
  laptops that do not behave well when APST is enabled. I am
  experiencing the same symptoms with the same model laptop except with
  a 512GB Samsung. Prior to manually disabling APST the drive would die
  and system would go down in flames with I/O errors within 20 to 40
  minutes of boot.

  $ sudo nvme list
  Node SN   Model   
 Namespace Usage  Format   FW Rev  
    
 - -- 
 
  /dev/nvme0n1   ** PM951 NVMe SAMSUNG 512GB
 1 500.20  GB / 512.11  GB512   B +  0 B   BXV76D0Q

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ajclayton   3305 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Mar 31 09:42:38 2017
  InstallationDate: Installed on 2012-09-08 (1665 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic 
root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt 
nouveau.modeset=0 log_buf_len=20M
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1682041] onibi (i386) - tests ran: 7, failed: 0

2017-04-15 Thread Brad Figg
tests ran:   7, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/onibi__4.4.0-74.95__2017-04-15_06-50-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/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive

2017-04-15 Thread André Düwel
Hi, I have set "nvme_core.default_ps_max_latency_us=3000" now for over a
day now and its working, too. No issues until now.

@Kai-Heng Feng: do you need any other testing?

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

Title:
  APST quirk needed for Samsung 512GB NVMe drive

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  APST support just landed in the latest Zesty kernel (4.10.0-14.16) as
  part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602.
  That patch has a quirk for certain 256GB Samsung drives found in Dell
  laptops that do not behave well when APST is enabled. I am
  experiencing the same symptoms with the same model laptop except with
  a 512GB Samsung. Prior to manually disabling APST the drive would die
  and system would go down in flames with I/O errors within 20 to 40
  minutes of boot.

  $ sudo nvme list
  Node SN   Model   
 Namespace Usage  Format   FW Rev  
    
 - -- 
 
  /dev/nvme0n1   ** PM951 NVMe SAMSUNG 512GB
 1 500.20  GB / 512.11  GB512   B +  0 B   BXV76D0Q

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ajclayton   3305 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Mar 31 09:42:38 2017
  InstallationDate: Installed on 2012-09-08 (1665 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic 
root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt 
nouveau.modeset=0 log_buf_len=20M
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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


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

2017-04-15 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/1682999

Title:
  Ubuntu crashes on Intel j4205 Apollo Lake

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 17.04 on ASRock j4205-ITX with BIOS v1.20. ASRock
  states that this platform is supported by Ubuntu 16.10 but after
  installation it kept freezing after few minuts. There was no trace of
  error in dmesg nor in any log. Not even a crashdump. After
  installation of Ubuntu 17.04 I was able to see an error:

  Apr 14 20:40:12 server kernel: BUG: unable to handle kernel paging request at 
af7b244c32d0
  Apr 14 20:40:12 server kernel: IP: xfsaild+0x12f/0x750 [xfs]
  Apr 14 20:40:12 server kernel: PGD 0 
  Apr 14 20:40:13 server kernel: 
  Apr 14 20:40:13 server kernel: Oops:  [#1] SMP
  Apr 14 20:40:13 server kernel: Modules linked in: intel_rapl 
intel_telemetry_pltdrv intel_pmc_ipc intel_punit_ipc intel_telemetry_core 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
intel_rapl_perf mei_me mei shpchp
  Apr 14 20:40:13 server kernel:  glue_helper ahci i2c_hid cryptd mii libahci 
drm hid video fjes pinctrl_broxton pinctrl_intel
  Apr 14 20:40:13 server kernel: CPU: 1 PID: 402 Comm: xfsaild/md1 Not tainted 
4.10.0-19-generic #21-Ubuntu
  Apr 14 20:40:13 server kernel: Hardware name: To Be Filled By O.E.M. To Be 
Filled By O.E.M./J4205-ITX, BIOS P1.20 12/16/2016
  Apr 14 20:40:13 server kernel: task: 8f7b24718000 task.stack: 
ba8581edc000
  Apr 14 20:40:13 server kernel: RIP: 0010:xfsaild+0x12f/0x750 [xfs]
  Apr 14 20:40:13 server kernel: RSP: 0018:ba8581edfe50 EFLAGS: 00010246
  Apr 14 20:40:13 server kernel: RAX:  RBX: 8f7b24718000 
RCX: 
  Apr 14 20:40:13 server kernel: RDX: 8000 RSI: 0246 
RDI: 0246
  Apr 14 20:40:13 server kernel: RBP: ba8581edfef8 R08:  
R09: 
  Apr 14 20:40:13 server kernel: R10: 08eb R11: 0920 
R12: b1499b24
  Apr 14 20:40:13 server kernel: R13: af7b244c3280 R14: 8f7b280bf5a0 
R15: 8f7b24309000
  Apr 14 20:40:13 server kernel: FS:  () 
GS:8f7b3fc8() knlGS:
  Apr 14 20:40:13 server kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Apr 14 20:40:13 server kernel: CR2: af7b244c32d0 CR3: 000237c09000 
CR4: 003406e0
  Apr 14 20:40:13 server kernel: Call Trace:
  Apr 14 20:40:13 server kernel:  kthread+0x101/0x140
  Apr 14 20:40:13 server kernel:  ? xfs_trans_ail_cursor_first+0x90/0x90 [xfs]
  Apr 14 20:40:13 server kernel:  ? kthread_create_on_node+0x60/0x60
  Apr 14 20:40:13 server kernel:  ret_from_fork+0x2c/0x40
  Apr 14 20:40:13 server kernel: Code: f0 49 c7 c4 24 9b 49 b1 85 c0 0f 85 05 
05 00 00 48 c7 43 08 00 00 00 00 e8 1f 96 3e f0 8b 05 ed 40 db f0 85 c0 0f 85 
1b 05 00 00 <41> 8b 45 50 4d 8b 75 00 85 c0 74 60 49 83 7d 48 00 75 59 49 8d 
  Apr 14 20:40:13 server kernel: RIP: xfsaild+0x12f/0x750 [xfs] RSP: 
ba8581edfe50
  Apr 14 20:40:13 server kernel: CR2: af7b244c32d0
  Apr 14 20:40:13 server kernel: ---[ end trace a03641228bdafba1 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 14 21:31 seq
   crw-rw 1 root audio 116, 33 Apr 14 21:31 timer
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.10.0-19-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Sat Apr 15 09:16:45 2017
  HibernationDevice: RESUME=UUID=2b9241db-ccc7-4811-8812-ff375b7adcc2
  InstallationDate: Installed on 2017-04-13 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic 
root=UUID=42129163-ff0a-40df-a4c2-9918862de656 ro console=tty0 console=ttyS0
  

[Kernel-packages] [Bug 1682999] [NEW] Ubuntu crashes on Intel j4205 Apollo Lake

2017-04-15 Thread Wojciech Pietruszewski
Public bug reported:

I'm using Ubuntu 17.04 on ASRock j4205-ITX with BIOS v1.20. ASRock
states that this platform is supported by Ubuntu 16.10 but after
installation it kept freezing after few minuts. There was no trace of
error in dmesg nor in any log. Not even a crashdump. After installation
of Ubuntu 17.04 I was able to see an error:

Apr 14 20:40:12 server kernel: BUG: unable to handle kernel paging request at 
af7b244c32d0
Apr 14 20:40:12 server kernel: IP: xfsaild+0x12f/0x750 [xfs]
Apr 14 20:40:12 server kernel: PGD 0 
Apr 14 20:40:13 server kernel: 
Apr 14 20:40:13 server kernel: Oops:  [#1] SMP
Apr 14 20:40:13 server kernel: Modules linked in: intel_rapl 
intel_telemetry_pltdrv intel_pmc_ipc intel_punit_ipc intel_telemetry_core 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
intel_rapl_perf mei_me mei shpchp
Apr 14 20:40:13 server kernel:  glue_helper ahci i2c_hid cryptd mii libahci drm 
hid video fjes pinctrl_broxton pinctrl_intel
Apr 14 20:40:13 server kernel: CPU: 1 PID: 402 Comm: xfsaild/md1 Not tainted 
4.10.0-19-generic #21-Ubuntu
Apr 14 20:40:13 server kernel: Hardware name: To Be Filled By O.E.M. To Be 
Filled By O.E.M./J4205-ITX, BIOS P1.20 12/16/2016
Apr 14 20:40:13 server kernel: task: 8f7b24718000 task.stack: 
ba8581edc000
Apr 14 20:40:13 server kernel: RIP: 0010:xfsaild+0x12f/0x750 [xfs]
Apr 14 20:40:13 server kernel: RSP: 0018:ba8581edfe50 EFLAGS: 00010246
Apr 14 20:40:13 server kernel: RAX:  RBX: 8f7b24718000 RCX: 

Apr 14 20:40:13 server kernel: RDX: 8000 RSI: 0246 RDI: 
0246
Apr 14 20:40:13 server kernel: RBP: ba8581edfef8 R08:  R09: 

Apr 14 20:40:13 server kernel: R10: 08eb R11: 0920 R12: 
b1499b24
Apr 14 20:40:13 server kernel: R13: af7b244c3280 R14: 8f7b280bf5a0 R15: 
8f7b24309000
Apr 14 20:40:13 server kernel: FS:  () 
GS:8f7b3fc8() knlGS:
Apr 14 20:40:13 server kernel: CS:  0010 DS:  ES:  CR0: 80050033
Apr 14 20:40:13 server kernel: CR2: af7b244c32d0 CR3: 000237c09000 CR4: 
003406e0
Apr 14 20:40:13 server kernel: Call Trace:
Apr 14 20:40:13 server kernel:  kthread+0x101/0x140
Apr 14 20:40:13 server kernel:  ? xfs_trans_ail_cursor_first+0x90/0x90 [xfs]
Apr 14 20:40:13 server kernel:  ? kthread_create_on_node+0x60/0x60
Apr 14 20:40:13 server kernel:  ret_from_fork+0x2c/0x40
Apr 14 20:40:13 server kernel: Code: f0 49 c7 c4 24 9b 49 b1 85 c0 0f 85 05 05 
00 00 48 c7 43 08 00 00 00 00 e8 1f 96 3e f0 8b 05 ed 40 db f0 85 c0 0f 85 1b 
05 00 00 <41> 8b 45 50 4d 8b 75 00 85 c0 74 60 49 83 7d 48 00 75 59 49 8d 
Apr 14 20:40:13 server kernel: RIP: xfsaild+0x12f/0x750 [xfs] RSP: 
ba8581edfe50
Apr 14 20:40:13 server kernel: CR2: af7b244c32d0
Apr 14 20:40:13 server kernel: ---[ end trace a03641228bdafba1 ]---

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-19-generic 4.10.0-19.21
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Apr 14 21:31 seq
 crw-rw 1 root audio 116, 33 Apr 14 21:31 timer
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.10.0-19-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Sat Apr 15 09:16:45 2017
HibernationDevice: RESUME=UUID=2b9241db-ccc7-4811-8812-ff375b7adcc2
InstallationDate: Installed on 2017-04-13 (1 days ago)
InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
PciMultimedia:
 
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic 
root=UUID=42129163-ff0a-40df-a4c2-9918862de656 ro console=tty0 console=ttyS0
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-19-generic N/A
 linux-backports-modules-4.10.0-19-generic  N/A
 linux-firmware 1.164
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/16/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.20
dmi.board.name: J4205-ITX
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.

[Kernel-packages] [Bug 1608526] Re: Asus N551JM screen brightness keys fn+F5/F6 don't work unless using kernel parameter acpi_osi=

2017-04-15 Thread Vincas Dargis
** Changed in: linux (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Asus N551JM screen brightness keys fn+F5/F6 don't work unless using
  kernel parameter acpi_osi=

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Keyboard combination fn+F5/F6 keys doesn't decrease/increase the
  screen brightness.

  WORKAROUND: Add kernel parameter:
  acpi_osi=

  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_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vincas 4675 F pulseaudio
   /dev/snd/controlC0:  vincas 4675 F pulseaudio
  Date: Mon Aug  1 16:20:41 2016
  HibernationDevice: RESUME=UUID=8c5322e6-f871-4abf-b1e0-61b84f0aa4b4
  InstallationDate: Installed on 2015-06-25 (402 days ago)
  InstallationMedia: Kubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150219.1)
  MachineType: ASUSTeK COMPUTER INC. N551JM
  ProcEnviron:
   LANGUAGE=
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=lt_LT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=e2407f5a-3411-4b70-a245-7c128267680f ro quiet splash acpi_osi= 
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.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-07-30 (1 days ago)
  dmi.bios.date: 10/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N551JM.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N551JM
  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.:bvrN551JM.204:bd10/06/2014:svnASUSTeKCOMPUTERINC.:pnN551JM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N551JM
  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/1608526/+subscriptions

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


[Kernel-packages] [Bug 1682041] rumford (amd64) - tests ran: 34, failed: 3

2017-04-15 Thread Brad Figg
tests ran:  34, failed: 3;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/rumford__4.4.0-74.95__2017-04-15_06-15-00/results-index.html

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

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1682041] onibi (amd64) - tests ran: 20, failed: 0

2017-04-15 Thread Brad Figg
tests ran:  20, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/onibi__4.4.0-74.95__2017-04-15_05-29-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/1682041

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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