[Kernel-packages] [Bug 1824641] Re: [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or 148 or 150 (but 4.4.0-143 works)

2019-06-22 Thread Tony Pursell
Another update to 4.4.0-151, still the same, screen still blank after
booting, 143 still works.

** Summary changed:

- [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or 
148 or 150 (but 4.4.0-143 works)
+ [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or 
148 or 150 or 151 (but 4.4.0-143 works)

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

Title:
  [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or
  146 or 148 or 150 or 151 (but 4.4.0-143 works)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual
  core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot
  this kernel everything is blank.  Just a black screen.  If I change to
  a terminal using Ctrl Alt F4 it is still a black screen but I can
  carefully type in my user name and password and then the shutdown
  command and it shuts down

  Using Advanced options in grub neither the upstart or the recovery
  option work.  The screen is still black.  The recovery option does,
  however, display the boot sequence before going black.

  I can boot the previous kernel 4.4.0-143 and all is OK.

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

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


[Kernel-packages] [Bug 1824641] Re: [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or 148 or 150 (but 4.4.0-143 works)

2019-06-06 Thread Tony Pursell
Another update to 4.4.0-150, still the same, screen still blank after
booting,

** Summary changed:

- [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or 
148 (but 4.4.0-143 works)
+ [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or 
148 or 150 (but 4.4.0-143 works)

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

Title:
  [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or
  146 or 148 or 150 (but 4.4.0-143 works)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual
  core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot
  this kernel everything is blank.  Just a black screen.  If I change to
  a terminal using Ctrl Alt F4 it is still a black screen but I can
  carefully type in my user name and password and then the shutdown
  command and it shuts down

  Using Advanced options in grub neither the upstart or the recovery
  option work.  The screen is still black.  The recovery option does,
  however, display the boot sequence before going black.

  I can boot the previous kernel 4.4.0-143 and all is OK.

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

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


[Kernel-packages] [Bug 1824641] Re: [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 (but 4.4.0-143 works)

2019-05-18 Thread Tony Pursell
Another update to 4.4.0-148, still the same, screen still blank after
booting,

** Summary changed:

- [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 
(but 4.4.0-143 works)
+ [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or 
148 (but 4.4.0-143 works)

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

Title:
  [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or
  146 or 148 (but 4.4.0-143 works)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual
  core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot
  this kernel everything is blank.  Just a black screen.  If I change to
  a terminal using Ctrl Alt F4 it is still a black screen but I can
  carefully type in my user name and password and then the shutdown
  command and it shuts down

  Using Advanced options in grub neither the upstart or the recovery
  option work.  The screen is still black.  The recovery option does,
  however, display the boot sequence before going black.

  I can boot the previous kernel 4.4.0-143 and all is OK.

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

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


[Kernel-packages] [Bug 1824641] Re: [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 (but 4.4.0-143 works)

2019-04-24 Thread Tony Pursell
** Summary changed:

- [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 (but 
4.4.0-143 works)
+ [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 
(but 4.4.0-143 works)

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

Title:
  [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or
  146 (but 4.4.0-143 works)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual
  core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot
  this kernel everything is blank.  Just a black screen.  If I change to
  a terminal using Ctrl Alt F4 it is still a black screen but I can
  carefully type in my user name and password and then the shutdown
  command and it shuts down

  Using Advanced options in grub neither the upstart or the recovery
  option work.  The screen is still black.  The recovery option does,
  however, display the boot sequence before going black.

  I can boot the previous kernel 4.4.0-143 and all is OK.

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

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


[Kernel-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

2019-04-24 Thread Tony den Haan
Updated Ubuntu-18.04 LTS, rebooted and problem is gone.

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

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in console-setup source package in Bionic:
  Confirmed
Status in kbd source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Confirmed
Status in console-setup source package in Cosmic:
  Confirmed
Status in kbd source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Confirmed
Status in console-setup source package in Disco:
  In Progress
Status in kbd source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Confirmed
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Confirmed
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Confirmed

Bug description:
  
  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY
  
  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
 $ sudo kbd_mode
 The keyboard is in some unknown mode
 $ sudo kbd_mode
 The keyboard is in raw (scancode) mode
 $

   * Install or reinstall kbd-configuration

 $ sudo apt install --reinstall keyboard-configuration 
 ...
 Setting up keyboard-configuration (1.178ubuntu11) ...
 Your console font configuration will be updated the next time your system
 boots. If you want to update it now, run 'setupcon' from a virtual console.
 ...

   * With the fixed package you should see the note above and the kbd
  mode must stay the same:

 $ sudo kbd_mode
 The keyboard is in raw (scancode) mode
 $

   * The unfixed package sets the kbd mode to unicode:

 $  sudo kbd_mode
 The keyboard is in Unicode (UTF-8) mode
 $

  [Regression Potential]

   * The change may break debian-installer changing the keyboard mode, this 
should also be tested.
   * In general changing the postinst script may make the package unable to 
install, but this is tested in generic environment and the change to the 
postinst script is very small.

  [Original Bug Text]
  WORKAROUND:

  sudo kbd_mode -s

  ORIGINAL DESCRIPTION:

  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions

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


[Kernel-packages] [Bug 1824641] Re: [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 (but 4.4.0-143 works)

2019-04-23 Thread Tony Pursell
An update with 4.4.0-146 has been installed and there is no fix in it.
The screen is still blank.

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

Title:
  [regression] Atom N550: Blank screen after booting kernel 4.4.0-145
  (but 4.4.0-143 works)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual
  core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot
  this kernel everything is blank.  Just a black screen.  If I change to
  a terminal using Ctrl Alt F4 it is still a black screen but I can
  carefully type in my user name and password and then the shutdown
  command and it shuts down

  Using Advanced options in grub neither the upstart or the recovery
  option work.  The screen is still black.  The recovery option does,
  however, display the boot sequence before going black.

  I can boot the previous kernel 4.4.0-143 and all is OK.

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

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


[Kernel-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

2019-04-20 Thread Tony den Haan
It's back! Me too on Ubuntu 18.04.2 LTS.
Maybe it was package keyboard-configuration_1.178ubuntu2.8_all.deb?

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

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in console-setup source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  New
Status in console-setup source package in Cosmic:
  New
Status in linux source package in Cosmic:
  New
Status in xorg-server source package in Cosmic:
  New
Status in console-setup source package in Disco:
  In Progress
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Confirmed
Status in console-setup source package in Eoan:
  New
Status in linux source package in Eoan:
  New
Status in xorg-server source package in Eoan:
  New

Bug description:
  WORKAROUND:

  sudo kbd_mode -s

  ORIGINAL DESCRIPTION:

  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions

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


[Kernel-packages] [Bug 1824641] Re: Blank screen after booting 4.4.0-145

2019-04-15 Thread Tony Pursell
Attached is Xorg log for the boot of 4.4.0-145

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

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

Title:
  Blank screen after booting 4.4.0-145

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual
  core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot
  this kernel everything is blank.  Just a black screen.  If I change to
  a terminal using Ctrl Alt F4 it is still a black screen but I can
  carefully type in my user name and password and then the shutdown
  command and it shuts down

  Using Advanced options in grub neither the upstart or the recovery
  option work.  The screen is still black.  The recovery option does,
  however, display the boot sequence before going black.

  I can boot the previous kernel 4.4.0-143 and all is OK.

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

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


[Kernel-packages] [Bug 1824641] Re: Blank screen after booting 4.4.0-145

2019-04-15 Thread Tony Pursell
Attached is a syslog for the boot of 4.4.0-145 from start up to shut
down in the way described above.

** Attachment added: "Syslog from boot of 4.4.0-145"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+attachment/5255939/+files/syslog4.4.0-145

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

Title:
  Blank screen after booting 4.4.0-145

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual
  core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot
  this kernel everything is blank.  Just a black screen.  If I change to
  a terminal using Ctrl Alt F4 it is still a black screen but I can
  carefully type in my user name and password and then the shutdown
  command and it shuts down

  Using Advanced options in grub neither the upstart or the recovery
  option work.  The screen is still black.  The recovery option does,
  however, display the boot sequence before going black.

  I can boot the previous kernel 4.4.0-143 and all is OK.

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

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


[Kernel-packages] [Bug 1824641] Re: Blank screen after booting 4.4.0-145

2019-04-14 Thread Tony Pursell
Sorry I cannot collect log files for the kernel giving the bug.  If I
can collect any useful information using the kernel that does work,
please let me know

** Changed in: mutter (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Blank screen after booting 4.4.0-145

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual
  core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot
  this kernel everything is blank.  Just a black screen.  If I change to
  a terminal using Ctrl Alt F4 it is still a black screen but I can
  carefully type in my user name and password and then the shutdown
  command and it shuts down

  Using Advanced options in grub neither the upstart or the recovery
  option work.  The screen is still black.  The recovery option does,
  however, display the boot sequence before going black.

  I can boot the previous kernel 4.4.0-143 and all is OK.

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

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


[Kernel-packages] [Bug 1824641] Re: Blank screen after booting 4.4.0-145

2019-04-13 Thread Tony Pursell
Sorry I cannot collect log files for the kernel giving the bug.  If I
can collect any useful information using the kernel that does work,
please let me know

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

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

Title:
  Blank screen after booting 4.4.0-145

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual
  core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot
  this kernel everything is blank.  Just a black screen.  If I change to
  a terminal using Ctrl Alt F4 it is still a black screen but I can
  carefully type in my user name and password and then the shutdown
  command and it shuts down

  Using Advanced options in grub neither the upstart or the recovery
  option work.  The screen is still black.  The recovery option does,
  however, display the boot sequence before going black.

  I can boot the previous kernel 4.4.0-143 and all is OK.

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

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


[Kernel-packages] [Bug 1824641] Re: Blank screen after booting 4.4.0-145

2019-04-13 Thread Tony Pursell
Please not that Launchpad has automatically assigned this bug to mutter,
but mutter is not installed on the notebook in question, so I have added
linux

** Also 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/1824641

Title:
  Blank screen after booting 4.4.0-145

Status in linux package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual
  core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot
  this kernel everything is blank.  Just a black screen.  If I change to
  a terminal using Ctrl Alt F4 it is still a black screen but I can
  carefully type in my user name and password and then the shutdown
  command and it shuts down

  Using Advanced options in grub neither the upstart or the recovery
  option work.  The screen is still black.  The recovery option does,
  however, display the boot sequence before going black.

  I can boot the previous kernel 4.4.0-143 and all is OK.

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

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


[Kernel-packages] [Bug 1762672] Re: TPM intermittently fails after cold-boot

2019-03-28 Thread Tony Espy
I just ran an additional five cycles of the testing described in my
previous comment with no failures.

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

Title:
  TPM intermittently fails after cold-boot

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

Bug description:
  [Impact]
  On an 18.04 LTS system with a TPM, the TPM will fail intermittently on cold 
boots. The problem seems to be that the TPM gets into a state where the partial 
self-test doesn't return TPM_RC_SUCCESS (meaning all tests have run to 
completion), but instead returns TPM_RC_TESTING (meaning some tests are still 
running in the background). A reboot can sometimes restore TPM functionality.

  This bug was originally reported on a Dell XPS 13, but has also
  recently been reported on a Dell Edge Gateway 3000.

  The bug has been confirmed to be fixed in the current development
  release (19.04/Cosmic).

  [Test Case]
  Cold boot a Dell XPS 13 or Dell Edge Gateway 3000 running 18.04 LTS Desktop 
or Server and grep for the following error log message:

  "tpm tpm0: A TPM error (2314) occurred continue selftest"

  Any attempts at using the TPM via tpm2-tss libraries or tpm2-tools
  should produce errors.

  As this bug is due to a race condition, ideally this test case would
  be run multiple times (20+ cold boots).

  Once the patch is installed the following error message may still be
  present in the syslog, however attempts to use the TPM should work:

  "tpm tpm0: A TPM error (2314) occurred attempting the self test"

  [Regression Potential]
  The chance of regression is low, as this patch was written by a well 
respected kernel developer with deep TPM experience. The patch is also being 
cherry-picked from the upstream stable and LTS kernels, and as mentioned, has 
already landed in Disco.

  [Original Description]
  After updating a Dell XPS 13 to 18.04 LTS, the TPM started to intermittently 
fail on cold boot. The following log messages could be observed in syslog:

  [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4)
   [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.895424] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest
   [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest
   [3.423100] tpm tpm0: TPM self test failed
   [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19)

  Discussion https://lkml.org/lkml/2017/12/6/284

  Fix
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6

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

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


[Kernel-packages] [Bug 1762672] Re: TPM intermittently fails after cold-boot

2019-03-28 Thread Tony Espy
Tested the latest OEM kernel from -proposed on a Dell Edge Gateway 3000
running Ubuntu Server 18.04 LTS:

# rmadison linux-image-oem | grep bionic-proposed
 linux-image-oem | 4.15.0.1035.40 | bionic-proposed | amd64

# dpkg -l | grep linux-image-oem
ii  linux-image-oem   4.15.0.1035.40
  amd64OEM Linux kernel image

Cold booted (x5) the system and instead of seeing "TPM error
(2314)...selftest" messages, I see the following (expected) messages:

Mar 28 18:35:01 1K5JB02 kernel: ACPI: TPM2 0x76D537C8 34 (v03 Tpm2Tabl 
0001 AMI )
Mar 28 18:35:01 1K5JB02 kernel: tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, 
rev-id 4)
Mar 28 18:35:01 1K5JB02 kernel: tpm tpm0: A TPM error (2314) occurred 
attempting the self test

Verified that the TPM is operational by running tpm2_listpcrs (version
3.1.3 built from source) using the in-kernel resource manager:

admin@1K5JB02:~$ sudo -i
root@1K5JB02:~# export LD_LIBRARY_PATH=/usr/local/lib/:$LD_LIBRARY_PATH
root@1K5JB02:~# export TPM2TOOLS_TCTI_NAME=device 
TPM2TOOLS_DEVICE_FILE=/dev/tpmrm0
root@1K5JB02:~# tpm2_startup --clear
root@1K5JB02:~# tpm2_listpcrs 

Bank/Algorithm: TPM_ALG_SHA1(0x0004)
PCR_00: 51 3f 1d 55 df 26 29 a2 42 ac 0b bf ae 7d 76 54 ef 91 24 d3
.
.
.


** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  TPM intermittently fails after cold-boot

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

Bug description:
  [Impact]
  On an 18.04 LTS system with a TPM, the TPM will fail intermittently on cold 
boots. The problem seems to be that the TPM gets into a state where the partial 
self-test doesn't return TPM_RC_SUCCESS (meaning all tests have run to 
completion), but instead returns TPM_RC_TESTING (meaning some tests are still 
running in the background). A reboot can sometimes restore TPM functionality.

  This bug was originally reported on a Dell XPS 13, but has also
  recently been reported on a Dell Edge Gateway 3000.

  The bug has been confirmed to be fixed in the current development
  release (19.04/Cosmic).

  [Test Case]
  Cold boot a Dell XPS 13 or Dell Edge Gateway 3000 running 18.04 LTS Desktop 
or Server and grep for the following error log message:

  "tpm tpm0: A TPM error (2314) occurred continue selftest"

  Any attempts at using the TPM via tpm2-tss libraries or tpm2-tools
  should produce errors.

  As this bug is due to a race condition, ideally this test case would
  be run multiple times (20+ cold boots).

  Once the patch is installed the following error message may still be
  present in the syslog, however attempts to use the TPM should work:

  "tpm tpm0: A TPM error (2314) occurred attempting the self test"

  [Regression Potential]
  The chance of regression is low, as this patch was written by a well 
respected kernel developer with deep TPM experience. The patch is also being 
cherry-picked from the upstream stable and LTS kernels, and as mentioned, has 
already landed in Disco.

  [Original Description]
  After updating a Dell XPS 13 to 18.04 LTS, the TPM started to intermittently 
fail on cold boot. The following log messages could be observed in syslog:

  [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4)
   [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.895424] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest
   [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest
   [3.423100] tpm tpm0: TPM self test failed
   [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19)

  Discussion https://lkml.org/lkml/2017/12/6/284

  Fix
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6

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

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


[Kernel-packages] [Bug 1762672] Re: TPM intermittently fails after cold-boot

2019-02-25 Thread Tony Espy
@Tyler

So it looks like we landed this just in time for the new SRU cycle,
which means we're looking at a tentative release to proposed on Mar 25.
Does that sound right? If so, I may check with Anthony to see if there's
a possibility that linux-oem could possibly re-spin and release
earlier...

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

Title:
  TPM intermittently fails after cold-boot

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

Bug description:
  [Impact]
  On an 18.04 LTS system with a TPM, the TPM will fail intermittently on cold 
boots. The problem seems to be that the TPM gets into a state where the partial 
self-test doesn't return TPM_RC_SUCCESS (meaning all tests have run to 
completion), but instead returns TPM_RC_TESTING (meaning some tests are still 
running in the background). A reboot can sometimes restore TPM functionality.

  This bug was originally reported on a Dell XPS 13, but has also
  recently been reported on a Dell Edge Gateway 3000.

  The bug has been confirmed to be fixed in the current development
  release (19.04/Cosmic).

  [Test Case]
  Cold boot a Dell XPS 13 or Dell Edge Gateway 3000 running 18.04 LTS Desktop 
or Server and grep for the following error log message:

  "tpm tpm0: A TPM error (2314) occurred continue selftest"

  Any attempts at using the TPM via tpm2-tss libraries or tpm2-tools
  should produce errors.

  As this bug is due to a race condition, ideally this test case would
  be run multiple times (20+ cold boots).

  Once the patch is installed the following error message may still be
  present in the syslog, however attempts to use the TPM should work:

  "tpm tpm0: A TPM error (2314) occurred attempting the self test"

  [Regression Potential]
  The chance of regression is low, as this patch was written by a well 
respected kernel developer with deep TPM experience. The patch is also being 
cherry-picked from the upstream stable and LTS kernels, and as mentioned, has 
already landed in Disco.

  [Original Description]
  After updating a Dell XPS 13 to 18.04 LTS, the TPM started to intermittently 
fail on cold boot. The following log messages could be observed in syslog:

  [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4)
   [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.895424] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest
   [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest
   [3.423100] tpm tpm0: TPM self test failed
   [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19)

  Discussion https://lkml.org/lkml/2017/12/6/284

  Fix
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6

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

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


[Kernel-packages] [Bug 1762672] Re: TPM intermittently fails after cold-boot

2019-02-22 Thread Tony Espy
@Khaled

Just curious as to why this is now FixCommitted? Has Tyler's back-port
landed in git for the next OEM and/or mainline kernel SRU release?

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

Title:
  TPM intermittently fails after cold-boot

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

Bug description:
  [Impact]
  On an 18.04 LTS system with a TPM, the TPM will fail intermittently on cold 
boots. The problem seems to be that the TPM gets into a state where the partial 
self-test doesn't return TPM_RC_SUCCESS (meaning all tests have run to 
completion), but instead returns TPM_RC_TESTING (meaning some tests are still 
running in the background). A reboot can sometimes restore TPM functionality.

  This bug was originally reported on a Dell XPS 13, but has also
  recently been reported on a Dell Edge Gateway 3000.

  The bug has been confirmed to be fixed in the current development
  release (19.04/Cosmic).

  [Test Case]
  Cold boot a Dell XPS 13 or Dell Edge Gateway 3000 running 18.04 LTS Desktop 
or Server and grep for the following error log message:

  "tpm tpm0: A TPM error (2314) occurred continue selftest"

  Any attempts at using the TPM via tpm2-tss libraries or tpm2-tools
  should produce errors.

  As this bug is due to a race condition, ideally this test case would
  be run multiple times (20+ cold boots).

  Once the patch is installed the following error message may still be
  present in the syslog, however attempts to use the TPM should work:

  "tpm tpm0: A TPM error (2314) occurred attempting the self test"

  [Regression Potential]
  The chance of regression is low, as this patch was written by a well 
respected kernel developer with deep TPM experience. The patch is also being 
cherry-picked from the upstream stable and LTS kernels, and as mentioned, has 
already landed in Disco.

  [Original Description]
  After updating a Dell XPS 13 to 18.04 LTS, the TPM started to intermittently 
fail on cold boot. The following log messages could be observed in syslog:

  [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4)
   [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.895424] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest
   [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest
   [3.423100] tpm tpm0: TPM self test failed
   [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19)

  Discussion https://lkml.org/lkml/2017/12/6/284

  Fix
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6

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

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


[Kernel-packages] [Bug 1762672] Re: TPM intermittently fails after cold-boot

2019-02-21 Thread Tony Espy
** Description changed:

-  [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4)
-  [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest
-  [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest
-  [0.895424] tpm tpm0: A TPM error (2314) occurred continue selftest
-  [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest
-  [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest
-  [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest
-  [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest
-  [3.423100] tpm tpm0: TPM self test failed
-  [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19)
+ [Impact]
+ On an 18.04 LTS system with a TPM, the TPM will fail intermittently on cold 
boots. The problem seems to be that the TPM gets into a state where the partial 
self-test doesn't return TPM_RC_SUCCESS (meaning all tests have run to 
completion), but instead returns TPM_RC_TESTING (meaning some tests are still 
running in the background). A reboot can sometimes restore TPM functionality.
+ 
+ This bug was originally reported on a Dell XPS 13, but has also recently
+ been reported on a Dell Edge Gateway 3000.
+ 
+ The bug has been confirmed to be fixed in the current development
+ release (19.04/Cosmic).
+ 
+ [Test Case]
+ Cold boot a Dell XPS 13 or Dell Edge Gateway 3000 running 18.04 LTS Desktop 
or Server and grep for the following error log message:
+ 
+ "tpm tpm0: A TPM error (2314) occurred continue selftest"
+ 
+ Any attempts at using the TPM via tpm2-tss libraries or tpm2-tools
+ should produce errors.
+ 
+ As this bug is due to a race condition, ideally this test case would be
+ run multiple times (20+ cold boots).
+ 
+ Once the patch is installed the following error message may still be
+ present in the syslog, however attempts to use the TPM should work:
+ 
+ "tpm tpm0: A TPM error (2314) occurred attempting the self test"
+ 
+ [Regression Potential]
+ The chance of regression is low, as this patch was written by a well 
respected kernel developer with deep TPM experience. The patch is also being 
cherry-picked from the upstream stable and LTS kernels, and as mentioned, has 
already landed in Disco.
+ 
+ [Original Description]
+ After updating a Dell XPS 13 to 18.04 LTS, the TPM started to intermittently 
fail on cold boot. The following log messages could be observed in syslog:
+ 
+ [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4)
+  [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest
+  [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest
+  [0.895424] tpm tpm0: A TPM error (2314) occurred continue selftest
+  [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest
+  [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest
+  [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest
+  [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest
+  [3.423100] tpm tpm0: TPM self test failed
+  [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19)
  
  Discussion https://lkml.org/lkml/2017/12/6/284
  
  Fix
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 18.04
- Package: linux-image-generic 4.15.0.13.14
- ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
- Uname: Linux 4.15.0-13-generic x86_64
- ApportVersion: 2.20.9-0ubuntu2
- Architecture: amd64
- AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  baz2268 F pulseaudio
- CurrentDesktop: XFCE
- Date: Tue Apr 10 11:41:57 2018
- EcryptfsInUse: Yes
- HibernationDevice: RESUME=/dev/mapper/cryptswap1
- InstallationDate: Installed on 2018-03-01 (39 days ago)
- InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
- MachineType: Dell Inc. XPS 13 9360
- ProcFB: 0 inteldrmfb
- ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=/dev/mapper/system-root ro quiet splash crashkernel=384M-:128M vt.handoff=1
- RelatedPackageVersions:
-  linux-restricted-modules-4.15.0-13-generic N/A
-  linux-backports-modules-4.15.0-13-generic  N/A
-  linux-firmware 1.173
- SourcePackage: linux
- UpgradeStatus: No upgrade log present (probably fresh install)
- dmi.bios.date: 01/25/2018
- dmi.bios.vendor: Dell Inc.
- dmi.bios.version: 2.5.1
- dmi.board.name: 02PG84
- dmi.board.vendor: Dell Inc.
- dmi.board.version: A00
- dmi.chassis.type: 9
- dmi.chassis.vendor: Dell Inc.
- dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.1:bd01/25/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr:
- dmi.product.family: XPS
- dmi.product.name: XPS 13 9360
- dmi.sys.vendor: Dell Inc.

-- 
You received this bug notification because you are a member of 

[Kernel-packages] [Bug 1762672] Re: TPM intermittently fails after cold-boot

2019-02-21 Thread Tony Espy
** Summary changed:

- TPM on Dell XPS 13 stopped working after upgrade to 18.04
+ TPM intermittently fails after cold-boot

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

Title:
  TPM intermittently fails after cold-boot

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress

Bug description:
   [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4)
   [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.895424] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest
   [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest
   [3.423100] tpm tpm0: TPM self test failed
   [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19)

  Discussion https://lkml.org/lkml/2017/12/6/284

  Fix
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-generic 4.15.0.13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  baz2268 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Apr 10 11:41:57 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=/dev/mapper/cryptswap1
  InstallationDate: Installed on 2018-03-01 (39 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=/dev/mapper/system-root ro quiet splash crashkernel=384M-:128M vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.1
  dmi.board.name: 02PG84
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.1:bd01/25/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1762672] Re: TPM on Dell XPS 13 stopped working after upgrade to 18.04

2019-02-20 Thread Tony Espy
I've run 10 cold boots on the gateway mentioned in my previous comment,
and in each case after issuing a tpm2_startup clear command, I've been
able to query the NVLIST of the TPM. So the back-ported patch appears to
be working as advertised.

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

Title:
  TPM on Dell XPS 13 stopped working after upgrade to 18.04

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress

Bug description:
   [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4)
   [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.895424] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest
   [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest
   [3.423100] tpm tpm0: TPM self test failed
   [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19)

  Discussion https://lkml.org/lkml/2017/12/6/284

  Fix
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-generic 4.15.0.13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  baz2268 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Apr 10 11:41:57 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=/dev/mapper/cryptswap1
  InstallationDate: Installed on 2018-03-01 (39 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=/dev/mapper/system-root ro quiet splash crashkernel=384M-:128M vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.1
  dmi.board.name: 02PG84
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.1:bd01/25/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1762672] Re: TPM on Dell XPS 13 stopped working after upgrade to 18.04

2019-02-20 Thread Tony Espy
@Tyler I've tested your kernel on a Dell Edge Gateway 3000 which was
showing the same TPM selftest log messages as originally described in
this bug. When cold-booted with your kernel I only see the following
messages now:

14:57:44 [0.00] ACPI: TPM2 0x76D537C8 34 (v03 Tpm2Tabl 0001 
AMI  )
14:57:44 [2.703384] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4)
14:57:44 [2.714914] tpm tpm0: A TPM error (2314) occurred attempting the self 
test

I was able to verify that the TPM is operational by running the
following tpm2-tools commands:

$ sudo tpm2_startup -T device --clear
$ tpm2_nvlist
(produces valid output)

Note - in this case, the system is using the in-kernel resource manager,
which it appears doesn't initialize the TPM, hence the need for using
tpm2_startup to initialize the TPM. The version of tpm2-tools used is
2.1.0.

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

Title:
  TPM on Dell XPS 13 stopped working after upgrade to 18.04

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress

Bug description:
   [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4)
   [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.895424] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest
   [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest
   [3.423100] tpm tpm0: TPM self test failed
   [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19)

  Discussion https://lkml.org/lkml/2017/12/6/284

  Fix
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-generic 4.15.0.13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  baz2268 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Apr 10 11:41:57 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=/dev/mapper/cryptswap1
  InstallationDate: Installed on 2018-03-01 (39 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=/dev/mapper/system-root ro quiet splash crashkernel=384M-:128M vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.1
  dmi.board.name: 02PG84
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.1:bd01/25/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1814628] Re: divide error: 0000 with Ubuntu 18.04

2019-02-08 Thread Tony
We are running MAAS here and that server is one that was deployed a
month ago approximately.

1a)
[0.00] Linux version 4.15.0-45-generic (buildd@lgw01-amd64-031) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 
2019 (Ubuntu 4.15.0-45.48-generic 4.15.18)
[0.00] Command line: 
BOOT_IMAGE=ubuntu/amd64/generic/bionic/daily/boot-kernel nomodeset ro 
root=squash:http://10.223.0.5:5248/images/ubuntu/amd64/generic/bionic/daily/squashfs
 ip=finer-panda:BOOTIF ip6=off overlayroot=tmpfs 
overlayroot_cfgdisk=disabled cc:{'datasource_list': ['MAAS']}end_cc 
cloud-config-url=http://10.223.0.5:5240/MAAS/metadata/latest/by-id/yx6d6w/?op=get_preseed
 apparmor=0 log_host=10.223.0.5 log_port=514 --- elevator=noop console=tty1 
console=ttyS0,115200 initrd=ubuntu/amd64/generic/bionic/daily/boot-initrd 
BOOTIF=01-f4-e9-d4-b6-5d-70

1b) Last check for them was a couple of months ago
1c) iDRAC says no.
2a) Say what? I tried starting it up and I got the shell appearing in the 
console. Then it just shut itself down again before I had time to react to log 
in. Could be a MAAS thing shutting it down?
2b) And what's that?
2c) Don't see any failures. First it boots up:
Ubuntu 18.04.1 LTS finer-panda ttyS0

finer-panda login: [   50.049021] cloud-init[2188]: Cloud-init v. 
18.4-0ubuntu1~18.04.1 running 'modules:config' at Fri, 08 Feb 2019 07:21:19 
+. Up 48.36 seconds.
[   51.015952] cloud-init[2270]: Powering node off.
ci-info: no authorized ssh keys fingerprints found for user ubuntu.


Then promptly after that:
[   51.169438] cloud-init[2270]: Cloud-init v. 18.4-0ubuntu1~18.04.1 running 
'modules:final' at Fri, 08 Feb 2019 07:21:22 +. Up 50.67 seconds.
[   51.169580] cloud-init[2270]: ci-info: no authorized ssh keys fingerprints 
found for user ubuntu.
[   51.169694] cloud-init[2270]: Cloud-init v. 18.4-0ubuntu1~18.04.1 finished 
at Fri, 08 Feb 2019 07:21:23 +. Datasource DataSourceMAAS 
[http://10.223.0.5:5240/MAs
 Stopping Authorization Manager...
[  OK  ] Stopped target Timers.
[  OK  ] Stopped Daily apt upgrade and clean activ Stopping Accounts 
Service...
[  OK  ] Stopped target Host and Network Name Lookups.
 Stopping Read required files in advance...
 Stopping OpenBSD Secure Shell server...
 Stopping LVM2 PV scan on device 8:2...
[  OK  ] Unmounted /var/lib/lxcfs.
etc..

2d) This is the host running the dozens of virtual machines popping up
and shut down daily. Until this day and all the 32 exactly identical
hosts are still up and running...and have been for a month.

I'll try to dig out the info what causes it to shut down instead of
staying up.

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

Title:
  divide error:  with Ubuntu 18.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Got a host running lots of virtual machines crashing today with the
  following terminal output (if that's to any help):

  [3430458.298979] divide error:  [#1] SMP PTI
  [3430458.304484] Modules linked in: cpuid vhost_net vhost tap 
nf_conntrack_ipv6 nf_defrag_ipv6 xt_physdev br_netfilter ip_set nfnetlink 
kvm_intel kvm irqbypass rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace 
sunrpc cachefiles fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
bridge ebtable_filter ebtables ip6table_filter ip6_tables devlink 
iptable_filter 8021q garp mrp stp llc bonding ipmi_ssif intel_rapl sb_edac 
x86_pkg_temp_thermal intel_powerclamp coretemp dcdbas intel_cstate 
intel_rapl_perf ipmi_si mei_me ipmi_devintf lpc_ich mei shpchp ipmi_msghandler 
acpi_power_meter mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi
  [3430458.389747]  scsi_transport_iscsi ip_tables x_tables autofs4 btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq raid1 raid0 multipath linear crct10dif_pclmul mgag200 
crc32_pclmul i2c_algo_bit ghash_clmulni_intel ttm pcbc mxm_wmi drm_kms_helper 
bnx2x aesni_intel syscopyarea sysfillrect aes_x86_64 sysimgblt fb_sys_fops 
crypto_simd glue_helper ptp cryptd drm pps_core ahci mdio libahci libcrc32c wmi 
[last unloaded: irqbypass]
  [3430458.440756] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.15.0-43-generic 
#46-Ubuntu
  [3430458.450411] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.7.1 
01/26/2018
  [3430458.460008] RIP: 0010:update_group_capacity+0x19d/0x1f0
  [3430458.467098] RSP: 0018:91043ec03bd8 EFLAGS: 00010247
  [3430458.474207] RAX: 006314d6 RBX: 0001 RCX: 
024d
  [3430458.483490] RDX:  RSI:  RDI: 
00022880
  [3430458.492769] RBP: 91043ec03c00 R08: 

[Kernel-packages] [Bug 1814628] Re: divide error: 0000 with Ubuntu 18.04

2019-02-05 Thread Tony
The host was inaccessible as it crashed.

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

Title:
  divide error:  with Ubuntu 18.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Got a host running lots of virtual machines crashing today with the
  following terminal output (if that's to any help):

  [3430458.298979] divide error:  [#1] SMP PTI
  [3430458.304484] Modules linked in: cpuid vhost_net vhost tap 
nf_conntrack_ipv6 nf_defrag_ipv6 xt_physdev br_netfilter ip_set nfnetlink 
kvm_intel kvm irqbypass rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace 
sunrpc cachefiles fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
bridge ebtable_filter ebtables ip6table_filter ip6_tables devlink 
iptable_filter 8021q garp mrp stp llc bonding ipmi_ssif intel_rapl sb_edac 
x86_pkg_temp_thermal intel_powerclamp coretemp dcdbas intel_cstate 
intel_rapl_perf ipmi_si mei_me ipmi_devintf lpc_ich mei shpchp ipmi_msghandler 
acpi_power_meter mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi
  [3430458.389747]  scsi_transport_iscsi ip_tables x_tables autofs4 btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq raid1 raid0 multipath linear crct10dif_pclmul mgag200 
crc32_pclmul i2c_algo_bit ghash_clmulni_intel ttm pcbc mxm_wmi drm_kms_helper 
bnx2x aesni_intel syscopyarea sysfillrect aes_x86_64 sysimgblt fb_sys_fops 
crypto_simd glue_helper ptp cryptd drm pps_core ahci mdio libahci libcrc32c wmi 
[last unloaded: irqbypass]
  [3430458.440756] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.15.0-43-generic 
#46-Ubuntu
  [3430458.450411] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.7.1 
01/26/2018
  [3430458.460008] RIP: 0010:update_group_capacity+0x19d/0x1f0
  [3430458.467098] RSP: 0018:91043ec03bd8 EFLAGS: 00010247
  [3430458.474207] RAX: 006314d6 RBX: 0001 RCX: 
024d
  [3430458.483490] RDX:  RSI:  RDI: 
00022880
  [3430458.492769] RBP: 91043ec03c00 R08: 9104376dc940 R09: 
1dcd6500
  [3430458.502071] R10: 91043ec0 R11: 0001 R12: 
910437625000
  [3430458.511391] R13: 9104376dc940 R14:  R15: 
91043ec03c30
  [3430458.520724] FS:  () GS:91043ec0() 
knlGS:
  [3430458.531161] CS:  0010 DS:  ES:  CR0: 80050033
  [3430458.538994] CR2: 00010960b008 CR3: 003f8300a002 CR4: 
003626e0
  [3430458.548416] DR0:  DR1:  DR2: 

  [3430458.557858] DR3:  DR6: fffe0ff0 DR7: 
0400
  [3430458.567298] Call Trace:
  [3430458.571507]  
  [3430458.575253]  find_busiest_group+0xff/0x9c0
  [3430458.581327]  load_balance+0x164/0x9c0
  [3430458.586928]  ? sched_clock+0x9/0x10
  [3430458.592347]  ? sched_clock_cpu+0x11/0xb0
  [3430458.598249]  rebalance_domains+0x245/0x2d0
  [3430458.604372]  run_rebalance_domains+0x139/0x1f0
  [3430458.610901]  __do_softirq+0xe4/0x2bb
  [3430458.616459]  irq_exit+0xb8/0xc0
  [3430458.621538]  scheduler_ipi+0xea/0x130
  [3430458.627201]  smp_reschedule_interrupt+0x39/0xe0
  [3430458.633860]  reschedule_interrupt+0x84/0x90
  [3430458.640138]  
  [3430458.644096] RIP: 0010:cpuidle_enter_state+0xa7/0x2f0
  [3430458.651289] RSP: 0018:a90100107e68 EFLAGS: 0246 ORIG_RAX: 
ff02
  [3430458.661431] RAX: 91043ec22880 RBX: 000c2ffbd05252a7 RCX: 
001f
  [3430458.671114] RDX: 000c2ffbd05252a7 RSI: ff1e5f04e459 RDI: 

  [3430458.680819] RBP: a90100107ea8 R08:  R09: 
0d17
  [3430458.690557] R10: a90100107e38 R11: 0eca R12: 
c900ff401f58
  [3430458.700303] R13: 0004 R14: 9bb71d18 R15: 

  [3430458.710075]  ? cpuidle_enter_state+0x97/0x2f0
  [3430458.716723]  cpuidle_enter+0x17/0x20
  [3430458.722455]  call_cpuidle+0x23/0x40
  [3430458.728041]  do_idle+0x18c/0x1f0
  [3430458.733312]  cpu_startup_entry+0x73/0x80
  [3430458.739293]  start_secondary+0x1ab/0x200
  [3430458.745229]  secondary_startup_64+0xa5/0xb0
  [3430458.751415] Code: 34 10 48 8b 96 38 0a 00 00 48 8b 86 30 0a 00 00 48 8b 
b6 a0 09 00 00 49 d1 e9 48 29 d6 ba 00 00 00 00 48 0f 48 f2 31 d2 44 01 ce <48> 
f7 f6 48 3d ff 03 00 00 77 0c ba 00 04 00 00 48 29 c2 48 0f
  [3430458.775397] RIP: update_group_capacity+0x19d/0x1f0 RSP: 91043ec03bd8
  [3430458.784442] ---[ end trace c1ae6368b9740f8a ]---
  [3430458.866540] Kernel panic - not syncing: Fatal exception in interrupt
  [3430458.866591] Kernel Offset: 0x1960 from 0x8100 

[Kernel-packages] [Bug 1814628] [NEW] divide error: 0000 with Ubuntu 18.04

2019-02-04 Thread Tony
Public bug reported:

Got a host running lots of virtual machines crashing today with the
following terminal output (if that's to any help):

[3430458.298979] divide error:  [#1] SMP PTI
[3430458.304484] Modules linked in: cpuid vhost_net vhost tap nf_conntrack_ipv6 
nf_defrag_ipv6 xt_physdev br_netfilter ip_set nfnetlink kvm_intel kvm irqbypass 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc cachefiles fscache 
xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack 
ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge ebtable_filter ebtables 
ip6table_filter ip6_tables devlink iptable_filter 8021q garp mrp stp llc 
bonding ipmi_ssif intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp 
coretemp dcdbas intel_cstate intel_rapl_perf ipmi_si mei_me ipmi_devintf 
lpc_ich mei shpchp ipmi_msghandler acpi_power_meter mac_hid sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi
[3430458.389747]  scsi_transport_iscsi ip_tables x_tables autofs4 btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq raid1 raid0 multipath linear crct10dif_pclmul mgag200 
crc32_pclmul i2c_algo_bit ghash_clmulni_intel ttm pcbc mxm_wmi drm_kms_helper 
bnx2x aesni_intel syscopyarea sysfillrect aes_x86_64 sysimgblt fb_sys_fops 
crypto_simd glue_helper ptp cryptd drm pps_core ahci mdio libahci libcrc32c wmi 
[last unloaded: irqbypass]
[3430458.440756] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.15.0-43-generic 
#46-Ubuntu
[3430458.450411] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.7.1 
01/26/2018
[3430458.460008] RIP: 0010:update_group_capacity+0x19d/0x1f0
[3430458.467098] RSP: 0018:91043ec03bd8 EFLAGS: 00010247
[3430458.474207] RAX: 006314d6 RBX: 0001 RCX: 
024d
[3430458.483490] RDX:  RSI:  RDI: 
00022880
[3430458.492769] RBP: 91043ec03c00 R08: 9104376dc940 R09: 
1dcd6500
[3430458.502071] R10: 91043ec0 R11: 0001 R12: 
910437625000
[3430458.511391] R13: 9104376dc940 R14:  R15: 
91043ec03c30
[3430458.520724] FS:  () GS:91043ec0() 
knlGS:
[3430458.531161] CS:  0010 DS:  ES:  CR0: 80050033
[3430458.538994] CR2: 00010960b008 CR3: 003f8300a002 CR4: 
003626e0
[3430458.548416] DR0:  DR1:  DR2: 

[3430458.557858] DR3:  DR6: fffe0ff0 DR7: 
0400
[3430458.567298] Call Trace:
[3430458.571507]  
[3430458.575253]  find_busiest_group+0xff/0x9c0
[3430458.581327]  load_balance+0x164/0x9c0
[3430458.586928]  ? sched_clock+0x9/0x10
[3430458.592347]  ? sched_clock_cpu+0x11/0xb0
[3430458.598249]  rebalance_domains+0x245/0x2d0
[3430458.604372]  run_rebalance_domains+0x139/0x1f0
[3430458.610901]  __do_softirq+0xe4/0x2bb
[3430458.616459]  irq_exit+0xb8/0xc0
[3430458.621538]  scheduler_ipi+0xea/0x130
[3430458.627201]  smp_reschedule_interrupt+0x39/0xe0
[3430458.633860]  reschedule_interrupt+0x84/0x90
[3430458.640138]  
[3430458.644096] RIP: 0010:cpuidle_enter_state+0xa7/0x2f0
[3430458.651289] RSP: 0018:a90100107e68 EFLAGS: 0246 ORIG_RAX: 
ff02
[3430458.661431] RAX: 91043ec22880 RBX: 000c2ffbd05252a7 RCX: 
001f
[3430458.671114] RDX: 000c2ffbd05252a7 RSI: ff1e5f04e459 RDI: 

[3430458.680819] RBP: a90100107ea8 R08:  R09: 
0d17
[3430458.690557] R10: a90100107e38 R11: 0eca R12: 
c900ff401f58
[3430458.700303] R13: 0004 R14: 9bb71d18 R15: 

[3430458.710075]  ? cpuidle_enter_state+0x97/0x2f0
[3430458.716723]  cpuidle_enter+0x17/0x20
[3430458.722455]  call_cpuidle+0x23/0x40
[3430458.728041]  do_idle+0x18c/0x1f0
[3430458.733312]  cpu_startup_entry+0x73/0x80
[3430458.739293]  start_secondary+0x1ab/0x200
[3430458.745229]  secondary_startup_64+0xa5/0xb0
[3430458.751415] Code: 34 10 48 8b 96 38 0a 00 00 48 8b 86 30 0a 00 00 48 8b b6 
a0 09 00 00 49 d1 e9 48 29 d6 ba 00 00 00 00 48 0f 48 f2 31 d2 44 01 ce <48> f7 
f6 48 3d ff 03 00 00 77 0c ba 00 04 00 00 48 29 c2 48 0f
[3430458.775397] RIP: update_group_capacity+0x19d/0x1f0 RSP: 91043ec03bd8
[3430458.784442] ---[ end trace c1ae6368b9740f8a ]---
[3430458.866540] Kernel panic - not syncing: Fatal exception in interrupt
[3430458.866591] Kernel Offset: 0x1960 from 0x8100 (relocation 
range: 0x8000-0xbfff)
[3430458.954898] ---[ end Kernel panic - not syncing: Fatal exception in 
interrupt

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

Title:
  divide error: 

[Kernel-packages] [Bug 1800859] Re: Fail to suspend properly in Ubuntu 18.10 (Also occurred in 18.04)

2018-11-08 Thread Tony Corbett
4 days of running the 4.13 kernel and every time I close the lid on this
laptop it's suspending and resuming without fail as it should.

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

Title:
  Fail to suspend properly in Ubuntu 18.10 (Also occurred in 18.04)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.

  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12

  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee0  Data: 
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] #19
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
PRICtl: Enable+ Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 0020, Page Request Allocation: 
0020
Capabilities: [2d0 v1] Process Address Space ID (PASID)
PASIDCap: 

[Kernel-packages] [Bug 1800859] Re: Fail to suspend properly in Ubuntu 18.10 (Also occurred in 18.04)

2018-11-06 Thread Tony Corbett
Yes, it suspends and resumes just fine on 4.13.16.

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

Title:
  Fail to suspend properly in Ubuntu 18.10 (Also occurred in 18.04)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.

  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12

  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee0  Data: 
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] #19
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
PRICtl: Enable+ Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 0020, Page Request Allocation: 
0020
Capabilities: [2d0 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID Width: 10
PASIDCtl: Enable+ Exec- Priv-
  

[Kernel-packages] [Bug 1800859] Re: Fail to suspend properly in Ubuntu 18.10 (Also occurred in 18.04)

2018-11-05 Thread Tony Corbett
It seems to be behaving on 4.13.16-041316-generic (but I've not been
about over the weekend to test a great deal!)  Will keep an eye on it
and report back this evening.

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

Title:
  Fail to suspend properly in Ubuntu 18.10 (Also occurred in 18.04)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.

  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12

  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee0  Data: 
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] #19
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
PRICtl: Enable+ Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 0020, Page Request Allocation: 
0020
Capabilities: [2d0 v1] Process Address Space ID 

[Kernel-packages] [Bug 1800859] Re: Fail to suspend properly in Ubuntu 18.10 (Also occurred in 18.04)

2018-11-01 Thread Tony Corbett
And just for completeness, another failure on 4.18.0-10-generic ...

Nov  1 13:27:49 g0wfv kernel: [ 4547.133172] atkbd serio0: Unknown key pressed 
(translated set 2, code 0xd8 on isa0060/serio0).
Nov  1 13:27:49 g0wfv kernel: [ 4547.133179] atkbd serio0: Use 'setkeycodes 
e058 ' to make it known.
Nov  1 13:27:49 g0wfv kernel: [ 4547.142204] atkbd serio0: Unknown key released 
(translated set 2, code 0xd8 on isa0060/serio0).
Nov  1 13:27:49 g0wfv kernel: [ 4547.142210] atkbd serio0: Use 'setkeycodes 
e058 ' to make it known.
Nov  1 13:27:49 g0wfv kernel: [ 4547.387163] wlo1: deauthenticating from 
c0:ff:d4:71:dd:c8 by local choice (Reason: 3=DEAUTH_LEAVING)
Nov  1 13:27:53 g0wfv kernel: [ 4551.104328] PM: suspend entry (deep)
Nov  1 14:25:43 g0wfv kernel: [0.00] Linux version 4.18.0-10-generic 
(buildd@lgw01-amd64-060) (gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)) #11-Ubuntu 
SMP Thu Oct 11 15:13:55 UTC 2018 (Ubuntu 4.18.0-10.11-generic 4.18.12)

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

Title:
  Fail to suspend properly in Ubuntu 18.10 (Also occurred in 18.04)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.

  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12

  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not 

[Kernel-packages] [Bug 1800859] Re: Fail to wake from suspend in Ubuntu 18.10

2018-11-01 Thread Tony Corbett
Another failure to suspend on 4.19 (booted into 4.18 on restart) ...

Nov  1 10:42:56 g0wfv kernel: [ 4694.900806] atkbd serio0: Unknown key pressed 
(translated set 2, code 0xd8 on isa0060/serio0).
Nov  1 10:42:56 g0wfv kernel: [ 4694.900852] atkbd serio0: Use 'setkeycodes 
e058 ' to make it known.
Nov  1 10:42:56 g0wfv kernel: [ 4694.909888] atkbd serio0: Unknown key released 
(translated set 2, code 0xd8 on isa0060/serio0).
Nov  1 10:42:56 g0wfv kernel: [ 4694.909892] atkbd serio0: Use 'setkeycodes 
e058 ' to make it known.
Nov  1 10:42:56 g0wfv kernel: [ 4695.122164] wlo1: deauthenticating from 
c0:ff:d4:71:dd:c8 by local choice (Reason: 3=DEAUTH_LEAVING)
Nov  1 10:43:00 g0wfv kernel: [ 4699.048317] PM: suspend entry (deep)
Nov  1 12:13:08 g0wfv kernel: [0.00] Linux version 4.18.0-10-generic 
(buildd@lgw01-amd64-060) (gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)) #11-Ubuntu 
SMP Thu Oct 11 15:13:55 UTC 2018 (Ubuntu 4.18.0-10.11-generic 4.18.12)


** Summary changed:

- Fail to wake from suspend in Ubuntu 18.10
+ Fail to suspend properly in Ubuntu 18.10 (Also occurred in 18.04)

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

Title:
  Fail to suspend properly in Ubuntu 18.10 (Also occurred in 18.04)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.

  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12

  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- 

[Kernel-packages] [Bug 1800859] Re: Fail to wake from suspend in Ubuntu 18.10

2018-11-01 Thread Tony Corbett
The above failure was exactly what I was originally experiencing in
18.04 with 4.15.0-38-generic; The only way to recover is to power off
and back on.

The AMDGPU failure seems to be another (sporadic) issue - it's the first
time I've seen it fail this way ...

More watching and testing required!

** Tags added: kernel-bug-exists-upstream

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

Title:
  Fail to wake from suspend in Ubuntu 18.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.

  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12

  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee0  Data: 
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] #19
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
   

[Kernel-packages] [Bug 1800859] Re: Fail to wake from suspend in Ubuntu 18.10

2018-11-01 Thread Tony Corbett
This one failed to suspend properly on 14.9 ...

Nov  1 08:30:24 g0wfv kernel: [  282.955728] atkbd serio0: Unknown key pressed 
(translated set 2, code 0xd8 on isa0060/serio0).
Nov  1 08:30:24 g0wfv kernel: [  282.955736] atkbd serio0: Use 'setkeycodes 
e058 ' to make it known.
Nov  1 08:30:24 g0wfv kernel: [  282.964593] atkbd serio0: Unknown key released 
(translated set 2, code 0xd8 on isa0060/serio0).
Nov  1 08:30:24 g0wfv kernel: [  282.964600] atkbd serio0: Use 'setkeycodes 
e058 ' to make it known.
Nov  1 08:30:24 g0wfv kernel: [  283.290474] wlo1: deauthenticating from 
c0:ff:d4:71:dd:c8 by local choice (Reason: 3=DEAUTH_LEAVING)
Nov  1 08:30:28 g0wfv kernel: [  287.130650] PM: suspend entry (deep)
Nov  1 09:13:18 g0wfv kernel: [0.00] Linux version 
4.19.0-041900-generic (kernel@tangerine) (gcc version 8.2.0 (Ubuntu 
8.2.0-7ubuntu1)) #201810221809 SMP Mon Oct 22 22:11:45 UTC 2018

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

Title:
  Fail to wake from suspend in Ubuntu 18.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.

  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12

  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 

[Kernel-packages] [Bug 1800859] Re: Fail to wake from suspend in Ubuntu 18.10

2018-11-01 Thread Tony Corbett
That would be a good idea  (silly me!)

Booted into 14.9 ... just testing as we speak!

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

Title:
  Fail to wake from suspend in Ubuntu 18.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.

  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12

  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee0  Data: 
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] #19
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
PRICtl: Enable+ Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 0020, Page Request Allocation: 
0020
Capabilities: [2d0 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID Width: 10
PASIDCtl: Enable+ 

[Kernel-packages] [Bug 1800859] Re: Fail to wake from suspend in Ubuntu 18.10

2018-10-31 Thread Tony Corbett
Unable to boot 4.19 upstream kernel (invalid signature)

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

Title:
  Fail to wake from suspend in Ubuntu 18.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.

  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12

  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee0  Data: 
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] #19
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
PRICtl: Enable+ Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 0020, Page Request Allocation: 
0020
Capabilities: [2d0 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID Width: 10
PASIDCtl: Enable+ Exec- Priv-
Kernel driver in 

[Kernel-packages] [Bug 1800859] Re: Fail to wake from suspend in Ubuntu 18.10

2018-10-31 Thread Tony Corbett
Failed wake after suspend ...

Oct 31 15:55:08 g0wfv kernel: [ 3212.930714] atkbd serio0: Unknown key pressed 
(translated set 2, code 0xd8 on isa0060/serio0).
Oct 31 15:55:08 g0wfv kernel: [ 3212.930721] atkbd serio0: Use 'setkeycodes 
e058 ' to make it known.
Oct 31 15:55:08 g0wfv kernel: [ 3212.940557] atkbd serio0: Unknown key released 
(translated set 2, code 0xd8 on isa0060/serio0).
Oct 31 15:55:08 g0wfv kernel: [ 3212.940564] atkbd serio0: Use 'setkeycodes 
e058 ' to make it known.
Oct 31 15:55:09 g0wfv kernel: [ 3213.238559] wlo1: deauthenticating from 
c0:ff:d4:71:dd:c8 by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 31 15:55:12 g0wfv kernel: [ 3216.833285] PM: suspend entry (deep)
Oct 31 18:04:32 g0wfv kernel: [ 3216.833293] PM: Syncing filesystems ... done.
Oct 31 18:04:32 g0wfv kernel: [ 3217.556685] Freezing user space processes ... 
(elapsed 0.003 seconds) done.
Oct 31 18:04:32 g0wfv kernel: [ 3217.560474] OOM killer disabled.
Oct 31 18:04:32 g0wfv kernel: [ 3217.560476] Freezing remaining freezable tasks 
... (elapsed 0.002 seconds) done.
Oct 31 18:04:32 g0wfv kernel: [ 3217.562636] Suspending console(s) (use 
no_console_suspend to debug)
Oct 31 18:04:32 g0wfv kernel: [ 3217.583712] sd 0:0:0:0: [sda] Synchronizing 
SCSI cache
Oct 31 18:04:32 g0wfv kernel: [ 3217.791855] sd 0:0:0:0: [sda] Stopping disk
Oct 31 18:04:32 g0wfv kernel: [ 3218.954069] ACPI: EC: interrupt blocked
Oct 31 18:04:32 g0wfv kernel: [ 3218.974774] snd_hda_intel :00:09.2: 
Refused to change power state, currently in D0
Oct 31 18:04:32 g0wfv kernel: [ 3218.994804] ACPI: Preparing to enter system 
sleep state S3
Oct 31 18:04:32 g0wfv kernel: [ 3219.002312] ACPI: EC: event blocked
Oct 31 18:04:32 g0wfv kernel: [ 3219.002314] ACPI: EC: EC stopped
Oct 31 18:04:32 g0wfv kernel: [ 3219.002315] PM: Saving platform NVS memory
Oct 31 18:04:32 g0wfv kernel: [ 3219.002397] Disabling non-boot CPUs ...
Oct 31 18:04:32 g0wfv kernel: [ 3219.016440] smpboot: CPU 1 is now offline
Oct 31 18:04:32 g0wfv kernel: [ 3219.040670] smpboot: CPU 2 is now offline
Oct 31 18:04:32 g0wfv kernel: [ 3219.072570] smpboot: CPU 3 is now offline
Oct 31 18:04:32 g0wfv kernel: [ 3219.075473] ACPI: Low-level resume complete
Oct 31 18:04:32 g0wfv kernel: [ 3219.075557] ACPI: EC: EC started
Oct 31 18:04:32 g0wfv kernel: [ 3219.075558] PM: Restoring platform NVS memory
Oct 31 18:04:32 g0wfv kernel: [ 3219.075659] LVT offset 0 assigned for vector 
0x400
Oct 31 18:04:32 g0wfv kernel: [ 3219.075942] Enabling non-boot CPUs ...
Oct 31 18:04:32 g0wfv kernel: [ 3219.076051] x86: Booting SMP configuration:
Oct 31 18:04:32 g0wfv kernel: [ 3219.076052] smpboot: Booting Node 0 Processor 
1 APIC 0x11
Oct 31 18:04:32 g0wfv kernel: [ 3219.078382]  cache: parent cpu1 should not be 
sleeping
Oct 31 18:04:32 g0wfv kernel: [ 3219.078473] microcode: CPU1: 
patch_level=0x06006115
Oct 31 18:04:32 g0wfv kernel: [ 3219.078630] CPU1 is up
Oct 31 18:04:32 g0wfv kernel: [ 3219.078664] smpboot: Booting Node 0 Processor 
2 APIC 0x12
Oct 31 18:04:32 g0wfv kernel: [ 3219.081154]  cache: parent cpu2 should not be 
sleeping
Oct 31 18:04:32 g0wfv kernel: [ 3219.081262] microcode: CPU2: 
patch_level=0x06006115
Oct 31 18:04:32 g0wfv kernel: [ 3219.081655] CPU2 is up
Oct 31 18:04:32 g0wfv kernel: [ 3219.081721] smpboot: Booting Node 0 Processor 
3 APIC 0x13
Oct 31 18:04:32 g0wfv kernel: [ 3219.084110]  cache: parent cpu3 should not be 
sleeping
Oct 31 18:04:32 g0wfv kernel: [ 3219.084209] microcode: CPU3: 
patch_level=0x06006115
Oct 31 18:04:32 g0wfv kernel: [ 3219.084643] CPU3 is up
Oct 31 18:04:32 g0wfv kernel: [ 3219.085315] ACPI: Waking up from system sleep 
state S3
Oct 31 18:04:32 g0wfv kernel: [ 3219.112587] ACPI: EC: interrupt unblocked
Oct 31 18:04:32 g0wfv kernel: [ 3219.158205] ACPI: EC: event unblocked
Oct 31 18:04:32 g0wfv kernel: [ 3219.158986] [drm] PCIE GART of 1024M enabled 
(table at 0x00F4).
Oct 31 18:04:32 g0wfv kernel: [ 3219.159425] sd 0:0:0:0: [sda] Starting disk
Oct 31 18:04:32 g0wfv kernel: [ 3219.191933] [drm] UVD initialized successfully.
Oct 31 18:04:32 g0wfv kernel: [ 3219.391445] [drm] VCE initialized successfully.
Oct 31 18:04:32 g0wfv kernel: [ 3219.392666] r8169 :01:00.0 enp1s0: link 
down
Oct 31 18:04:32 g0wfv kernel: [ 3219.392717] amdgpu :00:01.0: AMD-Vi: Event 
logged [IO_PAGE_FAULT domain=0x address=0x0001f1cf4040 flags=0x0050]
Oct 31 18:04:32 g0wfv kernel: [ 3219.392720] amdgpu :00:01.0: AMD-Vi: Event 
logged [IO_PAGE_FAULT domain=0x address=0x0001f175c560 flags=0x0070]
Oct 31 18:04:32 g0wfv kernel: [ 3219.392722] amdgpu :00:01.0: AMD-Vi: Event 
logged [IO_PAGE_FAULT domain=0x address=0x0001f175c570 flags=0x0070]
Oct 31 18:04:32 g0wfv kernel: [ 3219.392725] amdgpu :00:01.0: AMD-Vi: Event 
logged [IO_PAGE_FAULT domain=0x address=0x0001f175c570 flags=0x0070]
Oct 31 18:04:32 g0wfv kernel: [ 3219.415471] usb 1-1.4: reset full-speed USB 
device number 3 using ehci-pci
Oct 31 18:04:32 g0wfv kernel: [ 

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

2018-10-31 Thread Tony Corbett
apport information

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

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

Title:
  Fail to wake from suspend in Ubuntu 18.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.

  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12

  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee0  Data: 
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] #19
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
PRICtl: Enable+ Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 0020, Page Request Allocation: 
0020
Capabilities: [2d0 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, 

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

2018-10-31 Thread Tony Corbett
apport information

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

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

Title:
  Fail to wake from suspend in Ubuntu 18.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.

  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12

  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee0  Data: 
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] #19
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
PRICtl: Enable+ Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 0020, Page Request Allocation: 
0020
Capabilities: [2d0 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max 

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

2018-10-31 Thread Tony Corbett
apport information

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

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

Title:
  Fail to wake from suspend in Ubuntu 18.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.

  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12

  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee0  Data: 
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] #19
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
PRICtl: Enable+ Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 0020, Page Request Allocation: 
0020
Capabilities: [2d0 v1] Process Address Space ID (PASID)
PASIDCap: Exec- 

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

2018-10-31 Thread Tony Corbett
apport information

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

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

Title:
  Fail to wake from suspend in Ubuntu 18.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.

  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12

  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee0  Data: 
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] #19
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
PRICtl: Enable+ Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 0020, Page Request Allocation: 
0020
Capabilities: [2d0 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID 

[Kernel-packages] [Bug 1800859] Re: Fail to wake from suspend in Ubuntu 18.10

2018-10-31 Thread Tony Corbett
I'm waiting for it to fail again before posting more info.  Once it does
I will try the upstream kernel.

But to answer the question, this was happening in 18.04 (kernel version
4.15.0-38-generic) prior to upgrade, and has failed once since upgrade
to 18.10 earlier this afternoon. (But as luck would have it, it won't
fail on demand for me now!)

Last time I can remember this particular system resuming from suspend
reliably was probably just prior to install of 18.04 from new -
previously it was running 18.04 upgraded from 17.10 (and earlier!)

I'll keep an eye on it and report back.  Annoyingly, for now though, it
seems to be resuming OK!

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

Title:
  Fail to wake from suspend in Ubuntu 18.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.

  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12

  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee0  Data: 
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] #19

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

2018-10-31 Thread Tony Corbett
apport information

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

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

Title:
  Fail to wake from suspend in Ubuntu 18.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.

  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12

  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee0  Data: 
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] #19
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
PRICtl: Enable+ Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 0020, Page Request Allocation: 
0020
Capabilities: [2d0 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, 

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

2018-10-31 Thread Tony Corbett
apport information

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

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

Title:
  Fail to wake from suspend in Ubuntu 18.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.

  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12

  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee0  Data: 
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] #19
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
PRICtl: Enable+ Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 0020, Page Request Allocation: 
0020
Capabilities: [2d0 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID 

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

2018-10-31 Thread Tony Corbett
apport information

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

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

Title:
  Fail to wake from suspend in Ubuntu 18.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.

  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12

  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee0  Data: 
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] #19
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
PRICtl: Enable+ Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 0020, Page Request Allocation: 
0020
Capabilities: [2d0 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, 

[Kernel-packages] [Bug 1800859] ProcCpuinfoMinimal.txt

2018-10-31 Thread Tony Corbett
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1800859/+attachment/5207570/+files/ProcCpuinfoMinimal.txt

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

Title:
  Fail to wake from suspend in Ubuntu 18.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.

  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12

  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee0  Data: 
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] #19
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
PRICtl: Enable+ Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 0020, Page Request Allocation: 
0020
Capabilities: [2d0 v1] Process Address Space ID (PASID)
PASIDCap: 

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

2018-10-31 Thread Tony Corbett
apport information

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

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

Title:
  Fail to wake from suspend in Ubuntu 18.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.

  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12

  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee0  Data: 
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] #19
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
PRICtl: Enable+ Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 0020, Page Request Allocation: 
0020
Capabilities: [2d0 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, 

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

2018-10-31 Thread Tony Corbett
apport information

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

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

Title:
  Fail to wake from suspend in Ubuntu 18.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.

  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12

  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee0  Data: 
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] #19
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
PRICtl: Enable+ Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 0020, Page Request Allocation: 
0020
Capabilities: [2d0 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max 

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

2018-10-31 Thread Tony Corbett
apport information

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

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

Title:
  Fail to wake from suspend in Ubuntu 18.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.

  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12

  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee0  Data: 
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] #19
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
PRICtl: Enable+ Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 0020, Page Request Allocation: 
0020
Capabilities: [2d0 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID 

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

2018-10-31 Thread Tony Corbett
apport information

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

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

Title:
  Fail to wake from suspend in Ubuntu 18.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.

  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12

  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee0  Data: 
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] #19
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
PRICtl: Enable+ Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 0020, Page Request Allocation: 
0020
Capabilities: [2d0 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID 

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

2018-10-31 Thread Tony Corbett
apport information

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

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

Title:
  Fail to wake from suspend in Ubuntu 18.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.

  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12

  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee0  Data: 
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] #19
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
PRICtl: Enable+ Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 0020, Page Request Allocation: 
0020
Capabilities: [2d0 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID 

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

2018-10-31 Thread Tony Corbett
apport information

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

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

Title:
  Fail to wake from suspend in Ubuntu 18.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.

  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12

  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee0  Data: 
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] #19
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
PRICtl: Enable+ Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 0020, Page Request Allocation: 
0020
Capabilities: [2d0 v1] Process Address Space ID (PASID)
PASIDCap: Exec- 

[Kernel-packages] [Bug 1800859] Re: Fail to wake from suspend in Ubuntu 18.10

2018-10-31 Thread Tony Corbett
apport information

** Tags added: apport-collected

** Description changed:

  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.
  
  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...
  
  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10
  
  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12
  
  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov
  
  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+
  
  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee0  Data: 
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] #19
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
PRICtl: Enable+ Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 0020, Page Request Allocation: 
0020
Capabilities: [2d0 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID Width: 10
PASIDCtl: Enable+ Exec- Priv-
Kernel driver in use: amdgpu
Kernel modules: amdgpu
  
  00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Kabini 
HDMI/DP Audio [1002:9840]
Subsystem: Hewlett-Packard Company Kabini HDMI/DP Audio [103c:81f9]
Control: I/O+ 

[Kernel-packages] [Bug 1800859] Re: Fail to wake from suspend in Ubuntu 18.10

2018-10-31 Thread Tony Corbett
/var/log/kern.log (Correct suspend)
---

Oct 31 14:49:13 g0wfv kernel: [ 1526.582399] atkbd serio0: Unknown key pressed 
(translated set 2, code 0xd8 on isa0060/serio0).
Oct 31 14:49:13 g0wfv kernel: [ 1526.582406] atkbd serio0: Use 'setkeycodes 
e058 ' to make it known.
Oct 31 14:49:13 g0wfv kernel: [ 1526.591522] atkbd serio0: Unknown key released 
(translated set 2, code 0xd8 on isa0060/serio0).
Oct 31 14:49:13 g0wfv kernel: [ 1526.591529] atkbd serio0: Use 'setkeycodes 
e058 ' to make it known.
Oct 31 14:49:13 g0wfv kernel: [ 1526.929334] wlo1: deauthenticating from 
c0:ff:d4:71:dd:c8 by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 31 14:49:17 g0wfv kernel: [ 1530.941539] PM: suspend entry (deep)
Oct 31 14:49:17 g0wfv kernel: [ 1530.941544] PM: Syncing filesystems ... done.
Oct 31 14:49:23 g0wfv kernel: [ 1531.403144] Freezing user space processes ... 
(elapsed 0.003 seconds) done.
Oct 31 14:49:23 g0wfv kernel: [ 1531.406255] OOM killer disabled.
Oct 31 14:49:23 g0wfv kernel: [ 1531.406256] Freezing remaining freezable tasks 
... (elapsed 0.001 seconds) done.
Oct 31 14:49:23 g0wfv kernel: [ 1531.408315] Suspending console(s) (use 
no_console_suspend to debug)
Oct 31 14:49:23 g0wfv kernel: [ 1531.425977] sd 0:0:0:0: [sda] Synchronizing 
SCSI cache
Oct 31 14:49:23 g0wfv kernel: [ 1531.607574] sd 0:0:0:0: [sda] Stopping disk
Oct 31 14:49:23 g0wfv kernel: [ 1532.762024] ACPI: EC: interrupt blocked
Oct 31 14:49:23 g0wfv kernel: [ 1532.781877] pci_raw_set_power_state: 31 
callbacks suppressed
Oct 31 14:49:23 g0wfv kernel: [ 1532.781885] snd_hda_intel :00:09.2: 
Refused to change power state, currently in D0
Oct 31 14:49:23 g0wfv kernel: [ 1532.801924] ACPI: Preparing to enter system 
sleep state S3
Oct 31 14:49:23 g0wfv kernel: [ 1532.810201] ACPI: EC: event blocked
Oct 31 14:49:23 g0wfv kernel: [ 1532.810203] ACPI: EC: EC stopped
Oct 31 14:49:23 g0wfv kernel: [ 1532.810204] PM: Saving platform NVS memory
Oct 31 14:49:23 g0wfv kernel: [ 1532.810283] Disabling non-boot CPUs ...
Oct 31 14:49:23 g0wfv kernel: [ 1532.826448] IRQ 37: no longer affine to CPU1
Oct 31 14:49:23 g0wfv kernel: [ 1532.827561] smpboot: CPU 1 is now offline
Oct 31 14:49:23 g0wfv kernel: [ 1532.850783] IRQ 35: no longer affine to CPU2
Oct 31 14:49:23 g0wfv kernel: [ 1532.851832] smpboot: CPU 2 is now offline
Oct 31 14:49:23 g0wfv kernel: [ 1532.882702] IRQ 18: no longer affine to CPU3
Oct 31 14:49:23 g0wfv kernel: [ 1532.882725] IRQ 28: no longer affine to CPU3
Oct 31 14:49:23 g0wfv kernel: [ 1532.882731] IRQ 29: no longer affine to CPU3
Oct 31 14:49:23 g0wfv kernel: [ 1532.882740] IRQ 33: no longer affine to CPU3
Oct 31 14:49:23 g0wfv kernel: [ 1532.883787] smpboot: CPU 3 is now offline
Oct 31 14:49:23 g0wfv kernel: [ 1532.888683] ACPI: Low-level resume complete
Oct 31 14:49:23 g0wfv kernel: [ 1532.888725] ACPI: EC: EC started
Oct 31 14:49:23 g0wfv kernel: [ 1532.888726] PM: Restoring platform NVS memory
Oct 31 14:49:23 g0wfv kernel: [ 1532.26] LVT offset 0 assigned for vector 
0x400
Oct 31 14:49:23 g0wfv kernel: [ 1532.889090] Enabling non-boot CPUs ...
Oct 31 14:49:23 g0wfv kernel: [ 1532.889171] x86: Booting SMP configuration:
Oct 31 14:49:23 g0wfv kernel: [ 1532.889172] smpboot: Booting Node 0 Processor 
1 APIC 0x11
Oct 31 14:49:23 g0wfv kernel: [ 1532.891503]  cache: parent cpu1 should not be 
sleeping
Oct 31 14:49:23 g0wfv kernel: [ 1532.891594] microcode: CPU1: 
patch_level=0x06006115
Oct 31 14:49:23 g0wfv kernel: [ 1532.891750] CPU1 is up
Oct 31 14:49:23 g0wfv kernel: [ 1532.891813] smpboot: Booting Node 0 Processor 
2 APIC 0x12
Oct 31 14:49:23 g0wfv kernel: [ 1532.894309]  cache: parent cpu2 should not be 
sleeping
Oct 31 14:49:23 g0wfv kernel: [ 1532.894431] microcode: CPU2: 
patch_level=0x06006115
Oct 31 14:49:23 g0wfv kernel: [ 1532.894666] CPU2 is up
Oct 31 14:49:23 g0wfv kernel: [ 1532.894686] smpboot: Booting Node 0 Processor 
3 APIC 0x13
Oct 31 14:49:23 g0wfv kernel: [ 1532.897085]  cache: parent cpu3 should not be 
sleeping
Oct 31 14:49:23 g0wfv kernel: [ 1532.897192] microcode: CPU3: 
patch_level=0x06006115
Oct 31 14:49:23 g0wfv kernel: [ 1532.897635] CPU3 is up
Oct 31 14:49:23 g0wfv kernel: [ 1532.898310] ACPI: Waking up from system sleep 
state S3
Oct 31 14:49:23 g0wfv kernel: [ 1532.925268] ACPI: EC: interrupt unblocked
Oct 31 14:49:23 g0wfv kernel: [ 1532.965438] ACPI: EC: event unblocked
Oct 31 14:49:23 g0wfv kernel: [ 1532.966134] [drm] PCIE GART of 1024M enabled 
(table at 0x00F4).
Oct 31 14:49:23 g0wfv kernel: [ 1532.966918] sd 0:0:0:0: [sda] Starting disk
Oct 31 14:49:23 g0wfv kernel: [ 1532.998225] [drm] UVD initialized successfully.
Oct 31 14:49:23 g0wfv kernel: [ 1533.198643] [drm] VCE initialized successfully.
Oct 31 14:49:23 g0wfv kernel: [ 1533.200161] r8169 :01:00.0 enp1s0: link 
down
Oct 31 14:49:23 g0wfv kernel: [ 1533.222588] usb 1-1.4: reset full-speed USB 
device number 3 using ehci-pci
Oct 31 14:49:23 g0wfv kernel: [ 1533.770442] ata2: SATA 

[Kernel-packages] [Bug 1800859] [NEW] Fail to wake from suspend in Ubuntu 18.10

2018-10-31 Thread Tony Corbett
Public bug reported:

This has all the hallmarks of Bug #1774950 excepting that no amount of
kernel reversion seems to solve the problem.

System sporadically works fine, but mostly fails to suspend properly
according to /var/log/kern.log ...

$ lsb_release -rd
Description:Ubuntu 18.10
Release:18.10

$ cat /proc/version_signature 
Ubuntu 4.18.0-10.11-generic 4.18.12

$ lscpu
Architecture:x86_64
CPU op-mode(s):  32-bit, 64-bit
Byte Order:  Little Endian
CPU(s):  4
On-line CPU(s) list: 0-3
Thread(s) per core:  2
Core(s) per socket:  2
Socket(s):   1
NUMA node(s):1
Vendor ID:   AuthenticAMD
CPU family:  21
Model:   101
Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
Stepping:1
CPU MHz: 1582.715
CPU max MHz: 2500.
CPU min MHz: 1300.
BogoMIPS:4990.76
Virtualisation:  AMD-V
L1d cache:   32K
L1i cache:   96K
L2 cache:1024K
NUMA node0 CPU(s):   0-3
Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

$ sudo lspci -vnvn 
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee0  Data: 
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] #19
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
PRICtl: Enable+ Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 0020, Page Request Allocation: 
0020
Capabilities: [2d0 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID Width: 10
PASIDCtl: Enable+ Exec- Priv-
Kernel driver in use: amdgpu
Kernel modules: amdgpu

00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Kabini 
HDMI/DP Audio [1002:9840]
Subsystem: Hewlett-Packard Company Kabini HDMI/DP Audio [103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- 

[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)

2018-10-29 Thread Tony Corbett
Bug still present in 4.15.0-38-generic on HP Notebook - 15-ba047na.

$ uname -r
4.15.0-38-generic

$ lscpu
Architecture:x86_64
CPU op-mode(s):  32-bit, 64-bit
Byte Order:  Little Endian
CPU(s):  4
On-line CPU(s) list: 0-3
Thread(s) per core:  2
Core(s) per socket:  2
Socket(s):   1
NUMA node(s):1
Vendor ID:   AuthenticAMD
CPU family:  21
Model:   101
Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
Stepping:1
CPU MHz: 1583.409
CPU max MHz: 2500.
CPU min MHz: 1300.
BogoMIPS:4990.78
Virtualisation:  AMD-V
L1d cache:   32K
L1i cache:   96K
L2 cache:1024K
NUMA node0 CPU(s):   0-3
Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

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

Title:
  Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and
  Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  Systems with acpi-lpss can't do S3/S4 on Bionic.

  [Test]
  Users confirmed these patches work for them.

  [Fix]
  Commit a192aa923b66a (ACPI / LPSS: Consolidate runtime PM and system
  sleep handling) applies quirks for both runtime and system suspend.
  This causes problems for some systems, so avoid using quirks on S3 and
  S4.

  [Regression Potential]
  Low. These patches are in upstream stable, and it brings back driver's
  old behavior.

  ===Original Bug Report===
  I have installed Kubuntu 18.04 on 3 different machines (my friend's and my 
own) with no suspend problems but my HP Pavilion 11 x360 does not suspend.

  It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse,
  Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu
  18.04.

  I have also tried suspend using a live USB of 18.04 on this machine
  and it fails in the same way, so does not appear to be caused by any
  additional programs that I had installed.

  By installing an older kernel (4.14) on Kubuntu 18.04 the suspend
  function works as expected.

  Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the
  suspend failure that freezes the machine and requires a hard reset.

  Correct behaviour is -

  Screen goes blank, fan goes off, power LED flashes to show machine is
  in suspend. Pressing power button triggers 'resume' function.

  What happens -

  Screen goes blank, fan stays on, power LED stays on. Machine stays in
  this state and does not respond to any keyboard interaction, mouse
  movement or power button presses.

  Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response.

  The only way to use the machine is to shut down by holding down the
  power button.

  Checking the logs suggests that the machine believes it is in suspend
  mode sleep [deep] when it isn't.

  Having to hard reset to get any response means that the kernel logs
  say no more than sleep [deep]

  pm-suspend also results in the same problems with kernels 4.15 and
  4.16, but works fine with 4.14.

  It is curious that a machine that suspends fine on an earlier 4.14
  kernel no longer works with 4.15 and above, whilst 3 other machines
  (including one with pretty similar hardware) do not exhibit this
  problem.

  There are only a handful of questions about it on the forums but at
  least 3 other people have the same problem:

  https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on-
  resuming-from-suspend

  https://askubuntu.com/questions/1041369/after-upgrading-
  from-17-10-ubuntu-18-04-wont-sleep-suspend

  I am attempting to round up anyone else with the same issue and point
  them to this bug report.

  My laptop is HP Pavilion x360 11-n013na
  Matalaks is Acer Aspire ES1-511
  collisionTwo has XPS 9560

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

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

[Kernel-packages] [Bug 1753430] Re: virtualbox-guest-utils.service not starting

2018-04-11 Thread Tony Middleton
Just did a fresh upgrade of Ubuntu Mate from Xenial to Bionic.  The
guest packages were installed on the Xenial system prior to upgrade.
During the upgrade the guest packages were upgraded, NOT removed.

However, on the upgraded system the virtualbox-guest-utils.service was
NOT started but could be started manually.

Thus the original bug reported on this number still applies, although
all the other issues found on the way seem to have been addressed.

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

Title:
  virtualbox-guest-utils.service not starting

Status in dkms package in Ubuntu:
  Fix Released

Bug description:
  I am trialing various flavours of Ubuntu in Virtualbox virtual
  machines - Xubuntu, Lubuntu, Ubuntu and Ubuntu Mate.  All version
  18.04, running on Kubuntu 17.10 host.  All set up identically as far
  as I can tell, with virtualbox-guest-dkms, virtualbox-guest-utils and
  virtualbox-guest-x11 installed in each guest.

  All work fine except that shared folders does not work in 2 of the
  VMs.  It works in Xubuntu, Ubuntu but not in Lubuntu and Ubuntu Mate.
  On investigation it appears that the virtualbox-guest-utils.service is
  not started automatically on the two versions not working.  If I start
  it manually everything is OK.

  Here is the status - 
  systemctl status virtualbox-guest-utils.service 
  ● virtualbox-guest-utils.service - Virtualbox guest utils
 Loaded: loaded (/lib/systemd/system/virtualbox-guest-utils.service; 
enabled; vendor preset: enabled)
 Active: inactive (dead)

  Looking in journalctl there are no messages showing that the service
  tried to start and failed.  There is nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: virtualbox-guest-utils 5.2.8-dfsg-2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic i686
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Mon Mar  5 09:53:02 2018
  InstallationDate: Installed on 2012-10-23 (1958 days ago)
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: virtualbox
  UpgradeStatus: Upgraded to bionic on 2018-03-04 (0 days ago)

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

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


[Kernel-packages] [Bug 1756337] Re: kernel bug at fscache/operation.c

2018-04-06 Thread Tony
Due to https://bugs.launchpad.net/ubuntu/+source/apport/+bug/997020 I
switched this to 'Confirmed'.

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

Title:
  kernel bug at fscache/operation.c

Status in MAAS:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  MAAS deployed Ubuntu 16.04 LTS hosts began suffering from either

  [577275.774627] FS-Cache:
  [577275.777530] FS-Cache: Assertion failed
  [577275.781945] FS-Cache: 6 == 5 is false
  [577275.786304] [ cut here ]
  [577275.791662] kernel BUG at 
/build/linux-Fk60NP/linux-4.10.0/fs/fscache/operation.c:494!
  [577275.800740] invalid opcode:  [#1] SMP
  [577275.805415] Modules linked in: vhost_net vhost macvtap macvlan 
nf_conntrack_ipv6 nf_defrag_ipv6 xt_physdev br_netfilter ip_set nfnetlink 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc cachefiles fscache $
  [577275.885578]  ib_core configfs iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipa$
  [577275.925771] CPU: 52 PID: 39395 Comm: kworker/u161:1 Not tainted 
4.10.0-19-generic #21-Ubuntu
  [577275.940896] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.6.0 
10/31/2017

  
  or

  [126530.552030] FS-Cache:
  [126530.554868] FS-Cache: Assertion failed
  [126530.559250] FS-Cache: 1 > 0 is false
  [126530.563472] [ cut here ]
  [126530.568822] kernel BUG at 
/build/linux-Fk60NP/linux-4.10.0/fs/fscache/operation.c:68!
  [126530.577792] invalid opcode:  [#1] SMP
  [126530.582464] Modules linked in: vhost_net vhost macvtap macvlan 
nf_conntrack_ipv6 nf_defrag_ipv6 xt_physdev br_netfilter ip_set nfnetlink 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc cachefiles fscache $
  [126530.662615]  libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul $
  [126530.700165] CPU: 6 PID: 13971 Comm: CPU 1/KVM Not tainted 
4.10.0-19-generic #21-Ubuntu
  [126530.709227] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.7.1 
01/26/2018

  Possible solution here: https://patchwork.kernel.org/patch/10234815/

  Using MAAS: MAAS version: 2.2.2 (6099-g8751f91-0ubuntu1~16.04.1)

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

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


[Kernel-packages] [Bug 1753430] Re: virtualbox-guest-utils.service not starting

2018-03-21 Thread Tony Middleton
Regarding the original service not starting problem.

If I do a clean 18.04 install everything works OK. (Apart from Lubuntu
where I couldn't get the installer to work.)

If I do a clean 17.10 install without the guest packages because of bug
#1683043, upgrade to 18.04, install dpkg-dev, install the guest packages
everything works.

If I do a clean 16.04 install, add the guest packages, upgrade to 18.04
during which the guest packages are removed,  re add the guest packages
then Kubuntu, Ubuntu, Xubuntu work.  For Lubuntu and Ubuntu Mate the
virtualbox-guest-utils.service does not start automatically but can be
started manually.  This situation is a bit artificial as the packages
shouldn't be removed during the upgrade.

I suggest we revisit this problem when the upgrade package removal
problem is resolved.

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

Title:
  virtualbox-guest-utils.service not starting

Status in dkms package in Ubuntu:
  Fix Released

Bug description:
  I am trialing various flavours of Ubuntu in Virtualbox virtual
  machines - Xubuntu, Lubuntu, Ubuntu and Ubuntu Mate.  All version
  18.04, running on Kubuntu 17.10 host.  All set up identically as far
  as I can tell, with virtualbox-guest-dkms, virtualbox-guest-utils and
  virtualbox-guest-x11 installed in each guest.

  All work fine except that shared folders does not work in 2 of the
  VMs.  It works in Xubuntu, Ubuntu but not in Lubuntu and Ubuntu Mate.
  On investigation it appears that the virtualbox-guest-utils.service is
  not started automatically on the two versions not working.  If I start
  it manually everything is OK.

  Here is the status - 
  systemctl status virtualbox-guest-utils.service 
  ● virtualbox-guest-utils.service - Virtualbox guest utils
 Loaded: loaded (/lib/systemd/system/virtualbox-guest-utils.service; 
enabled; vendor preset: enabled)
 Active: inactive (dead)

  Looking in journalctl there are no messages showing that the service
  tried to start and failed.  There is nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: virtualbox-guest-utils 5.2.8-dfsg-2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic i686
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Mon Mar  5 09:53:02 2018
  InstallationDate: Installed on 2012-10-23 (1958 days ago)
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: virtualbox
  UpgradeStatus: Upgraded to bionic on 2018-03-04 (0 days ago)

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

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


[Kernel-packages] [Bug 1753430] Re: virtualbox-guest-utils.service not starting

2018-03-21 Thread Tony Middleton
Had a look at your PPA and realised that you had got hwe versions of the
guest packages as well as virtualbox-hwe.

So,  added your PPA to 16.04 Kubuntu guest and tried to upgrade to
18.04.  However do-release-upgrade disabled the entry before it
upgraded.  In that case I don't know how to test this.

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

Title:
  virtualbox-guest-utils.service not starting

Status in dkms package in Ubuntu:
  Fix Released

Bug description:
  I am trialing various flavours of Ubuntu in Virtualbox virtual
  machines - Xubuntu, Lubuntu, Ubuntu and Ubuntu Mate.  All version
  18.04, running on Kubuntu 17.10 host.  All set up identically as far
  as I can tell, with virtualbox-guest-dkms, virtualbox-guest-utils and
  virtualbox-guest-x11 installed in each guest.

  All work fine except that shared folders does not work in 2 of the
  VMs.  It works in Xubuntu, Ubuntu but not in Lubuntu and Ubuntu Mate.
  On investigation it appears that the virtualbox-guest-utils.service is
  not started automatically on the two versions not working.  If I start
  it manually everything is OK.

  Here is the status - 
  systemctl status virtualbox-guest-utils.service 
  ● virtualbox-guest-utils.service - Virtualbox guest utils
 Loaded: loaded (/lib/systemd/system/virtualbox-guest-utils.service; 
enabled; vendor preset: enabled)
 Active: inactive (dead)

  Looking in journalctl there are no messages showing that the service
  tried to start and failed.  There is nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: virtualbox-guest-utils 5.2.8-dfsg-2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic i686
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Mon Mar  5 09:53:02 2018
  InstallationDate: Installed on 2012-10-23 (1958 days ago)
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: virtualbox
  UpgradeStatus: Upgraded to bionic on 2018-03-04 (0 days ago)

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

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


[Kernel-packages] [Bug 1753430] Re: virtualbox-guest-utils.service not starting

2018-03-20 Thread Tony Middleton
I thought virtualbox-hwe was a host package.  My problem was when
upgrading guest systems.

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

Title:
  virtualbox-guest-utils.service not starting

Status in dkms package in Ubuntu:
  Fix Released

Bug description:
  I am trialing various flavours of Ubuntu in Virtualbox virtual
  machines - Xubuntu, Lubuntu, Ubuntu and Ubuntu Mate.  All version
  18.04, running on Kubuntu 17.10 host.  All set up identically as far
  as I can tell, with virtualbox-guest-dkms, virtualbox-guest-utils and
  virtualbox-guest-x11 installed in each guest.

  All work fine except that shared folders does not work in 2 of the
  VMs.  It works in Xubuntu, Ubuntu but not in Lubuntu and Ubuntu Mate.
  On investigation it appears that the virtualbox-guest-utils.service is
  not started automatically on the two versions not working.  If I start
  it manually everything is OK.

  Here is the status - 
  systemctl status virtualbox-guest-utils.service 
  ● virtualbox-guest-utils.service - Virtualbox guest utils
 Loaded: loaded (/lib/systemd/system/virtualbox-guest-utils.service; 
enabled; vendor preset: enabled)
 Active: inactive (dead)

  Looking in journalctl there are no messages showing that the service
  tried to start and failed.  There is nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: virtualbox-guest-utils 5.2.8-dfsg-2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic i686
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Mon Mar  5 09:53:02 2018
  InstallationDate: Installed on 2012-10-23 (1958 days ago)
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: virtualbox
  UpgradeStatus: Upgraded to bionic on 2018-03-04 (0 days ago)

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

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


[Kernel-packages] [Bug 1753430] Re: virtualbox-guest-utils.service not starting

2018-03-19 Thread Tony Middleton
Slightly confused by this response and the move to "Fix released".

The fix referred to fixes the compilation error.  However there are two
other problems - the service not starting even when the module compiled
and the packages being uninstalled during the upgrade.  Do I need to
raise those as new bugs?

You ask for an upgrade log.  Please can you clarify which log you need.

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

Title:
  virtualbox-guest-utils.service not starting

Status in dkms package in Ubuntu:
  Fix Released

Bug description:
  I am trialing various flavours of Ubuntu in Virtualbox virtual
  machines - Xubuntu, Lubuntu, Ubuntu and Ubuntu Mate.  All version
  18.04, running on Kubuntu 17.10 host.  All set up identically as far
  as I can tell, with virtualbox-guest-dkms, virtualbox-guest-utils and
  virtualbox-guest-x11 installed in each guest.

  All work fine except that shared folders does not work in 2 of the
  VMs.  It works in Xubuntu, Ubuntu but not in Lubuntu and Ubuntu Mate.
  On investigation it appears that the virtualbox-guest-utils.service is
  not started automatically on the two versions not working.  If I start
  it manually everything is OK.

  Here is the status - 
  systemctl status virtualbox-guest-utils.service 
  ● virtualbox-guest-utils.service - Virtualbox guest utils
 Loaded: loaded (/lib/systemd/system/virtualbox-guest-utils.service; 
enabled; vendor preset: enabled)
 Active: inactive (dead)

  Looking in journalctl there are no messages showing that the service
  tried to start and failed.  There is nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: virtualbox-guest-utils 5.2.8-dfsg-2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic i686
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Mon Mar  5 09:53:02 2018
  InstallationDate: Installed on 2012-10-23 (1958 days ago)
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: virtualbox
  UpgradeStatus: Upgraded to bionic on 2018-03-04 (0 days ago)

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

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


Re: [Kernel-packages] [Bug 1729244] Re: package linux-image-extra-4.4.0-98-generic 4.4.0-98.121 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before a

2017-11-01 Thread Tony Travis
On 01/11/17 14:29, Joseph Salisbury wrote:
> You may need to run the following from a terminal:
> 
> sudo apt-get install -f
> sudo apt-get clean
> sudo apt-get update
> 
> Then re-install the package or updates.
> 
> If that does not resolve your issue, please mark the bug as "Confirmed"

Hi, Joseph.

OK, that fixed the problem.

Thanks,

  Tony.

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

-- 
Minke Informatics Limited, Registered in Scotland - Company No. SC419028
Registered Office: 3 Donview, Bridge of Alford, AB33 8QJ, Scotland (UK)
tel. +44(0)19755 63548http://minke-informatics.co.uk
mob. +44(0)7985 078324mailto:tony.tra...@minke-informatics.co.uk

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

Title:
  package linux-image-extra-4.4.0-98-generic 4.4.0-98.121 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting a removal

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Attempting to install with nVidia GTX1060 graphics card

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-98-generic 4.4.0-98.121
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   linux-image-extra-4.4.0-98-generic: Purge
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  manager2337 F pulseaudio
  Date: Wed Nov  1 01:01:21 2017
  DpkgTerminalLog:
   dpkg: error processing package linux-image-extra-4.4.0-98-generic (--purge):
package is in a very bad inconsistent state; you should
reinstall it before attempting a removal
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  HibernationDevice: RESUME=UUID=a907603a-3713-4675-a0a6-27553415946e
  MachineType: empty empty
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic 
root=UUID=aad3d69b-99bb-47af-a94c-f6dd4926450f ro bootdegraded=y
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.14
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-extra-4.4.0-98-generic 4.4.0-98.121 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 'V1.06   '
  dmi.board.asset.tag: empty
  dmi.board.name: S3992-E
  dmi.board.vendor: TYAN Computer Corporation
  dmi.board.version: empty
  dmi.chassis.asset.tag: empty
  dmi.chassis.type: 3
  dmi.chassis.vendor: empty
  dmi.chassis.version: empty
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr'V1.06':bd06/09/2009:svnempty:pnempty:pvrempty:rvnTYANComputerCorporation:rnS3992-E:rvrempty:cvnempty:ct3:cvrempty:
  dmi.product.name: empty
  dmi.product.version: empty
  dmi.sys.vendor: empty

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

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


[Kernel-packages] [Bug 1729244] [NEW] package linux-image-extra-4.4.0-98-generic 4.4.0-98.121 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before at

2017-11-01 Thread Tony Travis
Public bug reported:

Attempting to install with nVidia GTX1060 graphics card

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.4.0-98-generic 4.4.0-98.121
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
AptOrdering:
 linux-image-extra-4.4.0-98-generic: Purge
 NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  manager2337 F pulseaudio
Date: Wed Nov  1 01:01:21 2017
DpkgTerminalLog:
 dpkg: error processing package linux-image-extra-4.4.0-98-generic (--purge):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting a removal
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
HibernationDevice: RESUME=UUID=a907603a-3713-4675-a0a6-27553415946e
MachineType: empty empty
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic 
root=UUID=aad3d69b-99bb-47af-a94c-f6dd4926450f ro bootdegraded=y
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.14
RfKill:
 
SourcePackage: linux
Title: package linux-image-extra-4.4.0-98-generic 4.4.0-98.121 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/09/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 'V1.06   '
dmi.board.asset.tag: empty
dmi.board.name: S3992-E
dmi.board.vendor: TYAN Computer Corporation
dmi.board.version: empty
dmi.chassis.asset.tag: empty
dmi.chassis.type: 3
dmi.chassis.vendor: empty
dmi.chassis.version: empty
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr'V1.06':bd06/09/2009:svnempty:pnempty:pvrempty:rvnTYANComputerCorporation:rnS3992-E:rvrempty:cvnempty:ct3:cvrempty:
dmi.product.name: empty
dmi.product.version: empty
dmi.sys.vendor: empty

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


** Tags: amd64 apport-package xenial

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

Title:
  package linux-image-extra-4.4.0-98-generic 4.4.0-98.121 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting a removal

Status in linux package in Ubuntu:
  New

Bug description:
  Attempting to install with nVidia GTX1060 graphics card

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-98-generic 4.4.0-98.121
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   linux-image-extra-4.4.0-98-generic: Purge
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  manager2337 F pulseaudio
  Date: Wed Nov  1 01:01:21 2017
  DpkgTerminalLog:
   dpkg: error processing package linux-image-extra-4.4.0-98-generic (--purge):
package is in a very bad inconsistent state; you should
reinstall it before attempting a removal
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  HibernationDevice: RESUME=UUID=a907603a-3713-4675-a0a6-27553415946e
  MachineType: empty empty
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic 
root=UUID=aad3d69b-99bb-47af-a94c-f6dd4926450f ro bootdegraded=y
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.14
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-extra-4.4.0-98-generic 4.4.0-98.121 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 'V1.06   '
  dmi.board.asset.tag: empty
  dmi.board.name: S3992-E
  dmi.board.vendor: TYAN Computer Corporation
  dmi.board.version: empty
  dmi.chassis.asset.tag: empty
  dmi.chassis.type: 3
  dmi.chassis.vendor: empty
  dmi.chassis.version: empty
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr'V1.06':bd06/09/2009:svnempty:pnempty:pvrempty:rvnTYANComputerCorporation:rnS3992-E:rvrempty:cvnempty:ct3:cvrempty:
  dmi.product.name: empty
  dmi.product.version: empty
  dmi.sys.vendor: empty

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

-- 
Mailing 

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

2017-06-13 Thread Tony Brobston
buzuk56's solution worked for me. I'm using Ryzen 5 1500X with Gigabyte
GA-AB350-gaming-3.

Thanks! So glad to have Ubuntu on this machine.

-- 
You 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:
  Unknown
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  Gigabyte AM4 boards users cannot boot Ubuntu successfully.
  Commit linux-gpio/fixes babdc22b0ccf4ef5a3075ce6e4afc26b7a279faf 
"pinctrl/amd: Use regular interrupt instead of chained" can fix the issue. 

  [Test Case]
  All Gigabyte AM4 boards can reproduce the issue.
  With the patch, the issue is resolved, per comment #170.

  [Regression Potential] 
  Regression Potential is low. It limits to rather new AMD platform which has 
pinctrl-amd. 
  As the commit log says, use chained interrupt is not a good idea. Use regular 
interrupt is the correct way.

  I also test the patch on an AMD laptop, where its touchpad depends on
  pinctrl-amd. No regression found.

  Original bug report:
  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/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 1536721] Re: System freezes

2016-11-16 Thread Tony Pursell
After upgrade to 16.10, this problem is back but the freezes do not
occur as frequently as they did in 16.04 before my 'fix'

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

Title:
  System freezes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My system frequently freezes.  The screen is still displayed but no
  input is accepted from mouse or keyboard.  The only action available
  is to switch off and re-start.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 21 16:47:04 2016
  DistUpgraded: 2015-10-28 10:41:28,942 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: wily
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:368d]
  InstallationDate: Installed on 2015-06-21 (214 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 90BX0018UK
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic.efi.signed 
root=UUID=2e321d15-1961-4c45-b1ce-7662ab1eee40 ro quiet splash vt.handoff=7
  SourcePackage: compiz
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-28 (85 days ago)
  dmi.bios.date: 08/29/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: O07KT44AUS
  dmi.board.name: Aptio CRB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993 WIN
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrO07KT44AUS:bd08/29/2014:svnLENOVO:pn90BX0018UK:pvrLenovoE50-00:rvnLENOVO:rnAptioCRB:rvrSDK0F82993WIN:cvnLENOVO:ct3:cvrNone:
  dmi.product.name: 90BX0018UK
  dmi.product.version: Lenovo E50-00
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Jan 21 16:19:27 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 780 
   vendor ACR
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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


[Kernel-packages] [Bug 1536721] Re: System freezes

2016-10-07 Thread Tony Pursell
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: compiz (Ubuntu)

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

Title:
  System freezes

Status in linux package in Ubuntu:
  New

Bug description:
  My system frequently freezes.  The screen is still displayed but no
  input is accepted from mouse or keyboard.  The only action available
  is to switch off and re-start.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 21 16:47:04 2016
  DistUpgraded: 2015-10-28 10:41:28,942 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: wily
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:368d]
  InstallationDate: Installed on 2015-06-21 (214 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 90BX0018UK
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic.efi.signed 
root=UUID=2e321d15-1961-4c45-b1ce-7662ab1eee40 ro quiet splash vt.handoff=7
  SourcePackage: compiz
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-28 (85 days ago)
  dmi.bios.date: 08/29/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: O07KT44AUS
  dmi.board.name: Aptio CRB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993 WIN
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrO07KT44AUS:bd08/29/2014:svnLENOVO:pn90BX0018UK:pvrLenovoE50-00:rvnLENOVO:rnAptioCRB:rvrSDK0F82993WIN:cvnLENOVO:ct3:cvrNone:
  dmi.product.name: 90BX0018UK
  dmi.product.version: Lenovo E50-00
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Jan 21 16:19:27 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 780 
   vendor ACR
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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


[Kernel-packages] [Bug 1623572] Re: Continuous messages in journal related to USB device.

2016-09-16 Thread Tony Middleton
I've only noticed this recently but I don't look in the journal often so
can't say how long the issue has been there.

I tried the 4.8 kernel.  The messages were still there but lower
frequency 2 or 3 per minute.

** Tags added: kernel-bug-exists-upstream

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

Title:
  Continuous messages in journal related to USB device.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a USB multi-card reader.  When it is plugged in I get
  continuous messages in the journal

  eg

  Sep 14 16:55:16 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
  Sep 14 16:55:16 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
  Sep 14 16:55:17 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
  Sep 14 16:55:17 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
  Sep 14 16:55:17 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
  Sep 14 16:55:23 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
  Sep 14 16:55:28 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
  Sep 14 16:55:30 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
  Sep 14 16:55:40 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
  Sep 14 16:55:47 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
  Sep 14 16:56:04 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
  Sep 14 16:56:18 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
  Sep 14 16:56:25 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
  Sep 14 16:56:35 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd

  I have no idea whether this relates to a faulty device or a system
  problem.

  Regards

  Tony

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tony   4726 F pulseaudio
   /dev/snd/controlC0:  tony   4726 F pulseaudio
  Date: Wed Sep 14 16:53:10 2016
  HibernationDevice: RESUME=UUID=925ed755-51a9-4968-ab9d-1a8c4c0cc93c
  InstallationDate: Installed on 2015-06-12 (460 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=f32dfa71-d154-4f81-9515-bef34b96bc2a ro
  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-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-05-10 (126 days ago)
  dmi.bios.date: 03/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A85X-UP4
  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.:bvrF4:bd03/13/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A85X-UP4: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/1623572/+subscriptions

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


[Kernel-packages] [Bug 1623572] [NEW] Continuous messages in journal related to USB device.

2016-09-14 Thread Tony Middleton
Public bug reported:

I have a USB multi-card reader.  When it is plugged in I get continuous
messages in the journal

eg

Sep 14 16:55:16 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
Sep 14 16:55:16 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
Sep 14 16:55:17 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
Sep 14 16:55:17 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
Sep 14 16:55:17 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
Sep 14 16:55:23 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
Sep 14 16:55:28 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
Sep 14 16:55:30 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
Sep 14 16:55:40 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
Sep 14 16:55:47 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
Sep 14 16:56:04 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
Sep 14 16:56:18 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
Sep 14 16:56:25 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
Sep 14 16:56:35 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd

I have no idea whether this relates to a faulty device or a system
problem.

Regards

Tony

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-36-generic 4.4.0-36.55
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  tony   4726 F pulseaudio
 /dev/snd/controlC0:  tony   4726 F pulseaudio
Date: Wed Sep 14 16:53:10 2016
HibernationDevice: RESUME=UUID=925ed755-51a9-4968-ab9d-1a8c4c0cc93c
InstallationDate: Installed on 2015-06-12 (460 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=f32dfa71-d154-4f81-9515-bef34b96bc2a ro
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-36-generic N/A
 linux-backports-modules-4.4.0-36-generic  N/A
 linux-firmware1.157.3
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-05-10 (126 days ago)
dmi.bios.date: 03/13/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F4
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F2A85X-UP4
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.:bvrF4:bd03/13/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A85X-UP4: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.

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


** Tags: amd64 apport-bug xenial

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

Title:
  Continuous messages in journal related to USB device.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a USB multi-card reader.  When it is plugged in I get
  continuous messages in the journal

  eg

  Sep 14 16:55:16 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
  Sep 14 16:55:16 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
  Sep 14 16:55:17 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
  Sep 14 16:55:17 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
  Sep 14 16:55:17 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
  Sep 14 16:55:23 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
  Sep 14 16:55:28 rose kernel: usb 10-1.1: reset high-speed USB device number 6 
using xhci_hcd
  Sep 14 16:55:30 rose kernel: 

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

2016-06-17 Thread Tony Espy
@Simon

Pretty sure my results reported in comment #11 were using the silo, so
5.37 doesn't resolve the problem.

I just re-tested on arale ( rc-proposed, 350 ) and still see the same
behavior on the initial connect of the headset.  Unfortunately, I can't
seem to get the headset to work at all now with the latest rc-proposed
image.

I'll retry on krillin later today.

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

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

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

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

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

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

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1527354/+subscriptions

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


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

2016-06-07 Thread tony
@jsalisbury: Yes this issue started after an upgrade and there is a red 
Triangle with an exclamation mark inside on my task bar.It tells me the update 
information is outdated... and also informs me to update manually. When I 
initiate manual update it tell me my system is up-to-date.
Kindly I also recently bought a new laptop 'Lenovo g50-70' and installed linux 
mint 17.3 and is having issues with wifi and bluetooth, I want to return it and 
get another one coz its still under warranty, can you advice me on a computer 
model that will work well with mint without issues because it seems that 
everyone with lenovo and linux have issues. Thanks in advance.

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

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

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

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

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

2016-06-05 Thread tony
Public bug reported:

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

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

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

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

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

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

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


** Tags: amd64 apport-bug trusty

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 3
  B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0002 Rev= 3.13
  S:  Manufacturer=Linux 3.13.0-87-generic ehci_hcd
  S:  Product=EHCI Host Controller

[Kernel-packages] [Bug 1559882] Re: Macbook Air resumes immediately after suspend

2016-04-18 Thread Tony
On Macbook Air 7.2 (running Mate 16.04) closing lid suspends correctly
after initial boot. Sometimes works for several cycles. Usually on
second and subsequent cycles, the machine resumes again after a few
seconds, while the lid is shut. From then on, this behaviour is
consistent and does not change. Also same problem after manually placed
into suspend from power menu.

Workaraound: Disable XHC1

For example:

echo XHC1 | sudo tee /proc/acpi/wakeup   (toggles XHC1)

This completely fixes the problem, and subsequent lid close/open works
as it should.

uname -r

4.4.0-18-generic

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

Title:
  Macbook Air resumes immediately after suspend

Status in linux-lts-vivid package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  New

Bug description:
  When closing the lid on the computer, the machine suspends. Within 5
  to 10 seconds, the machine resumes again with lid still closed.
  Opening and closing the lid again yields the same behavior again
  (suspend and resuming after a few seconds without opening the lid).
  This behaviour is the same when entering a sudo pm-suspend from the
  terminal, or using"Suspend" from the menu.

  There is one case where the behaviour described above is different.
  That is in the situation where machine is put into suspend for the
  first time after a complete reboot. In this case the machine suspends
  correctly and stays suspended as expected.

  The problem is consistent and can be reproduced as described any
  number of times.

  Disabling wi-fi (using the Broadcom 802.11 Linux STA proprietary
  driver) doesn't alter the behaviour described above.

  cat /proc/acpi/wakeup

  PEG0S3*disabled
  EC  S4*disabled  platform:PNP0C09:00
  HDEFS3*disabled  pci::00:1b.0
  RP01S3*disabled  pci::00:1c.0
  RP02S3*disabled  pci::00:1c.1
  RP03S3*disabled  pci::00:1c.2
  ARPTS4*disabled  pci::03:00.0
  RP05S3*disabled  pci::00:1c.4
  RP06S3*disabled  pci::00:1c.5
  SPITS3*disabled  platform:APP000D:00
  XHC1S3*enabled   pci::00:14.0
  ADP1S4*disabled  platform:ACPI0003:00
  LID0S4*enabled   platform:PNP0C0D:00

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

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-56-generic 3.19.0-56.62~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
  Uname: Linux 3.19.0-56-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 21 07:59:26 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-12-20 (91 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1557298] Re: [Xenial][Bluez5] Low Energy Keyboard is paired incorrectly

2016-03-24 Thread Tony Espy
I see those error messages quite frequently on touch devices running
Bluez5 as well.

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

Title:
  [Xenial][Bluez5] Low Energy Keyboard is paired incorrectly

Status in Unity Control Center:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  Failed to pair low energy(bluetooth smart, 4.0 or 4.1) devices
  correctly.

  1. bluetooth smart mouse is being listed as "all type" in bluetooth-
  wizard, however it is able to be paired and use, even repair(i'm
  mentioning this because in some circumstance low energy device can be
  only paired once, bug #1515179)

  2. bluetooth smart keyboard is unable to use after bluetooth-wizard
  says "OK". Also the passcode input is also not acting interactively
  like when pairing with bluetooth 3.0 keyboard.

  Above scenario also being verified with bluetoothctl and blueman.

  -
  More details about versions:

  Environment:
  xenial daily (20160307)
  bluez 5.37-0ubuntu5
  gnome-bluetooth 3.18.2-1ubuntu2
  blueman  2.0.3-1ubuntu1
  bluetooth controller 0cf3:e005 Atheros Communications, Inc. (hci version: 4.1)

  Tested devices:
  Designer Mouse, bluetooth smart (pairable, work, re-pair work)
  Designer Keyboard, bluetooth smart (paired, not working)
  BT3.0 keyboard, bluetooth classic (pair and work)
  BT3.0 mouse, bluetooth classic (pair and work)

  -
  In control environment with the same hardware system and devices:
  trusty 14.04.1 + dist-upgrade (stay with 3.13 kernel)
  bluez5 5.35 (ppa: https://launchpad.net/~vidplace7/+archive/ubuntu/bluez5)

  It works with all above devices but can only be pairing through
  bluetoothctl, since the older bluetooth-wizard does not understand
  bluez 5.x. Everything seems works fine, although there are a lot more
  error messages, but since this bug is more about xenial, please let me
  know if we need more information about this, I'm able to reproduce
  this trusty scenario in anytime.

  -
  Additional note:
  A little clarification, since I'm not sure how far the Bluetooth SIG is going 
to use Bluetooth Smart(Low Energy, or even Smart-Ready) to cover the 
versioning, I decided to just use what ever I saw on the product box.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 15 11:40:12 2016
  InstallationDate: Installed on 2016-03-14 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude E5550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic.efi.signed 
root=UUID=1079eca4-4293-4e51-ba0e-84f7d681cb2c ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0141B2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/18/2015:svnDellInc.:pnLatitudeE5550:pvr:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5550
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:71:CC:39:BD:22  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:862538 acl:39687 sco:0 events:2668 errors:0
TX bytes:26235 acl:904 sco:0 commands:1021 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-control-center/+bug/1557298/+subscriptions

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


[Kernel-packages] [Bug 1560094] Re: Starting bluez service is denied

2016-03-21 Thread Tony Espy
@Jamie

Thanks for the comment...   I'll work on re-vising the snapcraft.yaml
and will follow-up with zyga for details on the new snappy dbus
interface.  Hopefully it allows us to do all that the standard DBus conf
file allows.

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

Title:
  Starting bluez service is denied

Status in bluez package in Ubuntu:
  New

Bug description:
  If snappy core is updated in the background (on Raspberry Pi 2), and
  then bluez installed, starting the service is failing.

  
  Denials:

  [   45.955490] audit: type=1400 audit(1458574955.667:11): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=834 comm="c0
  [   46.197608] audit: type=1326 audit(1458574955.907:12): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=831 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.275680] audit: type=1400 audit(1458574955.987:13): apparmor="DENIED" 
operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=829 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1
  [   46.276483] audit: type=1326 audit(1458574955.987:14): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=829 comm="bluetoothd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000
  [   46.412021] audit: type=1326 audit(1458574956.123:15): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=839 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.504308] audit: type=1400 audit(1458574956.215:16): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=842 comm="c0
  [   46.520137] audit: type=1400 audit(1458574956.231:17): apparmor="DENIED" 
operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=841 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1
  [   46.520800] audit: type=1326 audit(1458574956.231:18): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=841 comm="bluetoothd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000
  [   46.625293] audit: type=1326 audit(1458574956.335:19): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=844 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.721080] audit: type=1400 audit(1458574956.431:20): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=847 comm="c2

  If trying to start bluetootctl:

  [  582.205066] audit: type=1400 audit(1458575491.915:31): apparmor="DENIED" 
operation="connect" profile="bluez5_bluetoothctl_5.37-2-armhf" 
name="/run/dbus/system_bus_socket" pid=993 comm="bluetoothctl" re0
  [bluetooth]# 

  
  ubuntu@localhost:~$ snappy list
  NameDate   Version  Developer 
  bluez5  2016-02-04 5.37-2-armhf canonical 
  canonical-pi2   2016-02-02 3.0  canonical 
  canonical-pi2-linux 2016-02-03 4.3.0-1006-3 canonical 
  ubuntu-core 2016-03-08 16.04.0-15.armhf canonical 
  ubuntu@localhost:~$ 

  ubuntu@localhost:~$ snappy info
  release: core/rolling
  architecture: armhf
  frameworks: bluez5.canonical
  apps:

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

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


[Kernel-packages] [Bug 1560094] Re: Starting bluez service is denied

2016-03-21 Thread Tony Espy
Our wrapper scripts for bluez ( bluetoothd ) and obexd are currently
copying DBus configuration files before starting the service.  This was
done as snappy had no way to allow a framework type snap such as bluez
or network-manager a way to install a DBus configuration file.


** Branch linked: lp:~bluetooth/bluez/snap-core-rolling

** Attachment added: "wrapper script from bluez5 snap"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1560094/+attachment/4606861/+files/command-bluez.wrapper

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

Title:
  Starting bluez service is denied

Status in bluez package in Ubuntu:
  New

Bug description:
  If snappy core is updated in the background (on Raspberry Pi 2), and
  then bluez installed, starting the service is failing.

  
  Denials:

  [   45.955490] audit: type=1400 audit(1458574955.667:11): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=834 comm="c0
  [   46.197608] audit: type=1326 audit(1458574955.907:12): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=831 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.275680] audit: type=1400 audit(1458574955.987:13): apparmor="DENIED" 
operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=829 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1
  [   46.276483] audit: type=1326 audit(1458574955.987:14): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=829 comm="bluetoothd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000
  [   46.412021] audit: type=1326 audit(1458574956.123:15): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=839 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.504308] audit: type=1400 audit(1458574956.215:16): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=842 comm="c0
  [   46.520137] audit: type=1400 audit(1458574956.231:17): apparmor="DENIED" 
operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=841 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1
  [   46.520800] audit: type=1326 audit(1458574956.231:18): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=841 comm="bluetoothd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000
  [   46.625293] audit: type=1326 audit(1458574956.335:19): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=844 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.721080] audit: type=1400 audit(1458574956.431:20): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=847 comm="c2

  If trying to start bluetootctl:

  [  582.205066] audit: type=1400 audit(1458575491.915:31): apparmor="DENIED" 
operation="connect" profile="bluez5_bluetoothctl_5.37-2-armhf" 
name="/run/dbus/system_bus_socket" pid=993 comm="bluetoothctl" re0
  [bluetooth]# 

  
  ubuntu@localhost:~$ snappy list
  NameDate   Version  Developer 
  bluez5  2016-02-04 5.37-2-armhf canonical 
  canonical-pi2   2016-02-02 3.0  canonical 
  canonical-pi2-linux 2016-02-03 4.3.0-1006-3 canonical 
  ubuntu-core 2016-03-08 16.04.0-15.armhf canonical 
  ubuntu@localhost:~$ 

  ubuntu@localhost:~$ snappy info
  release: core/rolling
  architecture: armhf
  frameworks: bluez5.canonical
  apps:

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

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


[Kernel-packages] [Bug 1387949] Re: power cycling Emerson EM229 headset caused phone to reboot

2016-03-11 Thread Tony Espy
@Selene

Sorry for updating the status without a comment.  I think my intention
was to get this re-tested on a current image and see if it was still
reproducible.

Looks like Simon has commented about kernel changes that may address the
original issue, so re-assigned to him.


** Changed in: bluez (Ubuntu)
 Assignee: Tony Espy (awe) => Simon Fels (morphis)

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

Title:
  power cycling Emerson EM229 headset caused phone to reboot

Status in Canonical System Image:
  Incomplete
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  While sanity testing krillin rtm image 139, I paired a bluetooth
  headset.  I made a call with it, hung up, then turned the headset off.
  I noticed this caused the BT indicator icon to invert, which is a nice
  way to indicate whether something is connected.  So, I turned the
  device back on, waited for the icon to invert, turned the device off,
  waited, and instead of inverting the icon...  the phone rebooted.

  Not sure what exactly failed here, like which component, but it's
  definitely not good when a paired headset can cause the phone to
  spontaneously reboot.

  I don't see any relevant .crash files, and all I see in syslog from
  that time is this:

  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  Activation 
(/ril_1) failed for connection '/310410695117999/context1'
  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  (/ril_1): device 
state change: failed -> disconnected (reason 'none') [120 30 0]
  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  (/ril_1): 
deactivating device (reason 'none') [0]
  Oct 30 23:43:01 ubuntu-phablet kernel: [  
747.229681][Ker_PM][request_suspend_state]wakeup (3->0) at 747214006509 
(2014-10-31 05:43:01.704759580 UTC)
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.779813]mtk-tpd: TPD wake up
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.816572]mtk-tpd: TPD wake up done
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.816593]  
mag_context_obj ok--->hwm_obj->early_suspend=0 
  Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Activating service 
name='org.freedesktop.systemd1' (using servicehelper)
  Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Successfully activated 
service 'org.freedesktop.systemd1'
  Oct 30 23:43:09 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="771" x-info="http://www.rsyslog.com;] exiting on 
signal 15.
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="785" x-info="http://www.rsyslog.com;] start
  Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is 
deprecated, consider using the 'stop' statement instead [try 
http://www.rsyslog.com/e/2307 ]
  Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is 
deprecated, consider using the 'stop' statement instead [try 
http://www.rsyslog.com/e/2307 ]
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's groupid changed to 103
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's userid changed to 100
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Booting Linux on 
physical CPU 0
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Initializing cgroup 
subsys cpu
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Linux version 3.4.67 
(root@android-barajas_1414177384) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue 
Oct 28 11:57:42 UTC 2014

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387949/+subscriptions

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


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

2016-03-08 Thread Tony Espy
Note, I forgot to mention in the previous comment that on xenial
desktop, the PIN wasn't displayed in settings.

Finally, here's the trace from my krillin, running rc-proposed/bq-
aquaris.en #270 + bluez 5.37.  Same result as the original bug
description.

** Attachment added: "btmon trace"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+attachment/4593246/+files/krillin-270.cap

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

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

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

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

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

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

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

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

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

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

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

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

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

  Device info *before* pairing attempt:

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+subscriptions

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


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

2016-03-08 Thread Tony Espy
And here's the trace for my xenial desktop running on a Thinkpad 410s.

** Attachment added: "btmon trace"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+attachment/4593245/+files/xenial-desktop.cap

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

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

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

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

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

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

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

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

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

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

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

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

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

  Device info *before* pairing attempt:

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+subscriptions

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


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

2016-03-08 Thread Tony Espy
OK, so I guess I was wrong about pairing working with my Ubuntu desktops
( both running 5.37 ), although I'm pretty sure this worked for me
before. Maybe I was running bluez 5.36 when I tested?

Here's a btmon trace of wily running bluez 5.37 on a mid '13 macair.  I
get prompted to view the PIN just like on krillin.

** Attachment added: "btmon trace"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+attachment/4593244/+files/wily-macair.cap

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

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

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

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

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

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

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

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

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

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

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

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

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

  Device info *before* pairing attempt:

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+subscriptions

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


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

2016-03-08 Thread Tony Espy
@Simon

Re: comment #6, when I paired the keyboard with my Ubuntu laptops,
neither prompted me at all; the keyboard silently paired and was usable.

That said, I'll re-test this afternoon and get you the HCI dump from the
phone.

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

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

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

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

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

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

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

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

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

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

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

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

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

  Device info *before* pairing attempt:

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+subscriptions

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


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

2016-03-07 Thread Tony Espy
** Attachment added: "dbus log from krillin"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+attachment/4591780/+files/dbus.log

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

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

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

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

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

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

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

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

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

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

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

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

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

  Device info *before* pairing attempt:

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+subscriptions

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


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

2016-03-07 Thread Tony Espy
** Description changed:

  Connecting to the latest generation Apple BT keyboard ( the one with the
  USB port & no batteries ) fails on an Ubuntu Touch device, as when you
  press the "Connect" button on the device page, a dialog titled
  "Bluetooth Pairing Request" is displayed, with the following text:
  
  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX
  
  The dialog has "Cancel" and "Confirm PIN" buttons.
  
  The keyboard has no display on which a PIN could be displayed.
  
  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.
  
  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.
  
  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.
  
  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found that
  this requires power cycling the keyboard to clear and cause the PIN
  dialog to be displayed again.
+ 
+ [bluetooth]# show
+ Controller B8:64:91:48:2B:1E
+   Name: Aquaris E4.5 Ubuntu Edition
+   Alias: Aquaris E4.5 Ubuntu Edition
+   Class: 0x1c020c
+   Powered: yes
+   Discoverable: no
+   Pairable: yes
+   UUID: Headset AG(1112--1000-8000-00805f9b34fb)
+   UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
+   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
+   UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
+   UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
+   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
+   UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
+   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
+   UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
+   UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
+   Modalias: usb:v1D6Bp0246d0525
+   Discovering: no
+ 
+ [bluetooth]# devices
+ Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
+ Device DE:76:E2:04:9D:6F BB-9D6F
+ Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
+ Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
+ Device 84:38:35:67:0C:3D ubuntu-0
+ Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
+ Device 00:21:3C:A0:14:A6 Jawbone ERA
+ Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7
+ 
+ Device info *before* pairing attempt:
+ 
+ Device 04:69:F8:C2:A0:09
+   Name: tony espy’s Keyboard
+   Alias: tony espy’s Keyboard
+   Class: 0x002540
+   Icon: input-keyboard
+   Paired: no
+   Trusted: no
+   Blocked: no
+   Connected: no
+   LegacyPairing: no
+   Modalias: bluetooth:v004Cp0267d0066
+ 
+ No changes in any of the attributes after *after* the pairing attempt (
+ output of info command is the same ).

** Attachment added: "syslog from krillin w/bluez debug enabled"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+attachment/4591778/+files/syslog

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

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

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

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

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

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

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

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

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

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

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

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

2016-03-07 Thread Tony Espy
Re-tested on krillin ( rc-proposed/bq-aquaris.en / 270 ), this time with
bluez 5.37 installed from the silo.

@Simon, how could this not be a system settings app failure?  As I
pointed out in my description, pairing this keyboard works fine with
every other device I tried, including two Ubuntu desktop systems.

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

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

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

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

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

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

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

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

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

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

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

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

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

  Device info *before* pairing attempt:

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+subscriptions

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


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

2016-03-07 Thread Tony Espy
** Attachment added: "system settings log from krillin"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+attachment/4591779/+files/application-legacy-ubuntu-system-settings-.log

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

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

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

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

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

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

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

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

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

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

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

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

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

  Device info *before* pairing attempt:

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+subscriptions

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


[Kernel-packages] [Bug 1387949] Re: power cycling Emerson EM229 headset caused phone to reboot

2016-03-03 Thread Tony Espy
** Changed in: bluez (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: canonical-devices-system-image
   Status: Confirmed => Incomplete

** Changed in: bluez (Ubuntu)
 Assignee: (unassigned) => Selene Scriven (toykeeper)

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

Title:
  power cycling Emerson EM229 headset caused phone to reboot

Status in Canonical System Image:
  Incomplete
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  While sanity testing krillin rtm image 139, I paired a bluetooth
  headset.  I made a call with it, hung up, then turned the headset off.
  I noticed this caused the BT indicator icon to invert, which is a nice
  way to indicate whether something is connected.  So, I turned the
  device back on, waited for the icon to invert, turned the device off,
  waited, and instead of inverting the icon...  the phone rebooted.

  Not sure what exactly failed here, like which component, but it's
  definitely not good when a paired headset can cause the phone to
  spontaneously reboot.

  I don't see any relevant .crash files, and all I see in syslog from
  that time is this:

  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  Activation 
(/ril_1) failed for connection '/310410695117999/context1'
  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  (/ril_1): device 
state change: failed -> disconnected (reason 'none') [120 30 0]
  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  (/ril_1): 
deactivating device (reason 'none') [0]
  Oct 30 23:43:01 ubuntu-phablet kernel: [  
747.229681][Ker_PM][request_suspend_state]wakeup (3->0) at 747214006509 
(2014-10-31 05:43:01.704759580 UTC)
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.779813]mtk-tpd: TPD wake up
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.816572]mtk-tpd: TPD wake up done
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.816593]  
mag_context_obj ok--->hwm_obj->early_suspend=0 
  Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Activating service 
name='org.freedesktop.systemd1' (using servicehelper)
  Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Successfully activated 
service 'org.freedesktop.systemd1'
  Oct 30 23:43:09 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="771" x-info="http://www.rsyslog.com;] exiting on 
signal 15.
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="785" x-info="http://www.rsyslog.com;] start
  Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is 
deprecated, consider using the 'stop' statement instead [try 
http://www.rsyslog.com/e/2307 ]
  Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is 
deprecated, consider using the 'stop' statement instead [try 
http://www.rsyslog.com/e/2307 ]
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's groupid changed to 103
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's userid changed to 100
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Booting Linux on 
physical CPU 0
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Initializing cgroup 
subsys cpu
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Linux version 3.4.67 
(root@android-barajas_1414177384) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue 
Oct 28 11:57:42 UTC 2014

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387949/+subscriptions

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


[Kernel-packages] [Bug 1531925] Re: Can't connect Logitech Living Room Keyboard [LE]

2016-03-01 Thread Tony Espy
Added a task for ubuntu-system-settings as LE devices aren't considered
at all by Bluetooth settings.

** Description changed:

  Cannot connect a Logitech Illuminated Living Room keyboard to a device
  running bluez5.  There are two versions of the keyboard, a unifying
  receiver version, and a Bluetooth version.  The latter has a BT symbol
  on the 'del' key.  To put the BT version in pairing mode, power on the
  keyboard, then briefly hold the FN and 'del' key together and release.
  A green LED at the top right of the keyboard should start flashing
  quickly.
  
  Once in pairing mode, the device will become visible on desktop using
  the BT settings UI, however it's *never* shown in the UI on a device
  running the latest Touch ( OTA9.1+ ).  Note, this includes devices
  running a silo version of bluez 5.37, including both arale and krillin.
  On both devices, the keyboard *is* viewable using bluetoothctl.
  
+ It should be noted that LE keyboard support on touch should be a
+ considered a missing feature.
+ 
  Here's the reported attributes of the device from my macair running
  15.10 + bluez 5.37:
  
  Device DF:08:A9:A0:13:93
-   Name: K830
-   Alias: K830
-   Appearance: 0x03c1
-   Icon: input-keyboard
-   Paired: yes
-   Trusted: no
-   Blocked: no
-   Connected: yes
-   LegacyPairing: no
-   UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb)
-   UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
-   UUID: Device Information  (180a--1000-8000-00805f9b34fb)
-   UUID: Battery Service (180f--1000-8000-00805f9b34fb)
-   UUID: Human Interface Device (1812--1000-8000-00805f9b34fb)
-   UUID: Vendor specific   (0001--1000-8000-011f246d)
-   Modalias: usb:v046DpB335d0010
+   Name: K830
+   Alias: K830
+   Appearance: 0x03c1
+   Icon: input-keyboard
+   Paired: yes
+   Trusted: no
+   Blocked: no
+   Connected: yes
+   LegacyPairing: no
+   UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb)
+   UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
+   UUID: Device Information  (180a--1000-8000-00805f9b34fb)
+   UUID: Battery Service (180f--1000-8000-00805f9b34fb)
+   UUID: Human Interface Device (1812--1000-8000-00805f9b34fb)
+   UUID: Vendor specific   (0001--1000-8000-011f246d)
+   Modalias: usb:v046DpB335d0010
  
  From bluetoothctl on both my laptop and my desktop, I'm able to pair,
  trust and connect the device, and info reflects these changes, however
  the device never actually connects, it's LED remains blinking fast, and
  the keyboard cannot be used.
  
  Note, before pairing, I issued the command 'agent KeyboardOnly' and
  'default-agent'.

** Also affects: ubuntu-system-settings (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Can't connect Logitech Living Room Keyboard [LE]

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

Bug description:
  Cannot connect a Logitech Illuminated Living Room keyboard to a device
  running bluez5.  There are two versions of the keyboard, a unifying
  receiver version, and a Bluetooth version.  The latter has a BT symbol
  on the 'del' key.  To put the BT version in pairing mode, power on the
  keyboard, then briefly hold the FN and 'del' key together and release.
  A green LED at the top right of the keyboard should start flashing
  quickly.

  Once in pairing mode, the device will become visible on desktop using
  the BT settings UI, however it's *never* shown in the UI on a device
  running the latest Touch ( OTA9.1+ ).  Note, this includes devices
  running a silo version of bluez 5.37, including both arale and
  krillin.  On both devices, the keyboard *is* viewable using
  bluetoothctl.

  It should be noted that LE keyboard support on touch should be a
  considered a missing feature.

  Here's the reported attributes of the device from my macair running
  15.10 + bluez 5.37:

  Device DF:08:A9:A0:13:93
    Name: K830
    Alias: K830
    Appearance: 0x03c1
    Icon: input-keyboard
    Paired: yes
    Trusted: no
    Blocked: no
    Connected: yes
    LegacyPairing: no
    UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb)
    UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
    UUID: Device Information  (180a--1000-8000-00805f9b34fb)
    UUID: Battery Service (180f--1000-8000-00805f9b34fb)
    UUID: Human Interface Device (1812--1000-8000-00805f9b34fb)
    UUID: Vendor specific   (0001--1000-8000-011f246d)
    Modalias: usb:v046DpB335d0010

  From bluetoothctl on both my laptop and my desktop, I'm able to pair,
  trust and connect the 

[Kernel-packages] [Bug 1531925] Re: Can't connect Logitech Living Room Keyboard [LE]

2016-03-01 Thread Tony Espy
** Description changed:

- Trying to pair this device and bluetoothd crashed on my Wily laptop and
- the N4 running latest proposed
+ Cannot connect a Logitech Illuminated Living Room keyboard to a device
+ running bluez5.  There are two versions of the keyboard, a unifying
+ receiver version, and a Bluetooth version.  The latter has a BT symbol
+ on the 'del' key.  To put the BT version in pairing mode, power on the
+ keyboard, then briefly hold the FN and 'del' key together and release.
+ A green LED at the top right of the keyboard should start flashing
+ quickly.
  
- build number: 107
- device name: mako
- channel: ubuntu-touch/rc-proposed/ubuntu-pd
- last update: 2016-01-07 11:30:20
- version version: 107
- version ubuntu: 20160107
- version device: 20150911
- version custom: 20150929-2-vivid
+ Once in pairing mode, the device will become visible on desktop using
+ the BT settings UI, however it's *never* shown in the UI on a device
+ running the latest Touch ( OTA9.1+ ).  Note, this includes devices
+ running a silo version of bluez 5.37, including both arale and krillin.
+ On both devices, the keyboard *is* viewable using bluetoothctl.
  
- The device is a Logitech Illuminated Living Room keyboard K830 (
- Bluetooth Smart version; !Unifying version ) with an integrated
- trackpad.
+ Here's the reported attributes of the device from my macair running
+ 15.10 + bluez 5.37:
  
- Device DF:08:A9:A0:13:91
-  Name: K830
-  Alias: K830
-  Appearance: 0x03c1
-  Icon: input-keyboard
-  Paired: no
-  Trusted: no
-  Blocked: no
-  Connected: no
-  LegacyPairing: no
-  UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
-  RSSI: -43
+ Device DF:08:A9:A0:13:93
+   Name: K830
+   Alias: K830
+   Appearance: 0x03c1
+   Icon: input-keyboard
+   Paired: yes
+   Trusted: no
+   Blocked: no
+   Connected: yes
+   LegacyPairing: no
+   UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb)
+   UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
+   UUID: Device Information  (180a--1000-8000-00805f9b34fb)
+   UUID: Battery Service (180f--1000-8000-00805f9b34fb)
+   UUID: Human Interface Device (1812--1000-8000-00805f9b34fb)
+   UUID: Vendor specific   (0001--1000-8000-011f246d)
+   Modalias: usb:v046DpB335d0010
  
- The device would come and go in the devices list from bluetoothctl
- A manual scan would bring it back
- I then tried to manually pair and it failed with
- Failed to pair: org.freedesktop.DBus.Error.NoReply
+ From bluetoothctl on both my laptop and my desktop, I'm able to pair,
+ trust and connect the device, and info reflects these changes, however
+ the device never actually connects, it's LED remains blinking fast, and
+ the keyboard cannot be used.
  
- On the latop dmesg reports
- [357895.395029] traps: bluetoothd[790] general protection ip:56419e2c0306 
sp:7ffefd2b6760 error:0 in bluetoothd[56419e217000+105000]
+ Note, before pairing, I issued the command 'agent KeyboardOnly' and
+ 'default-agent'.

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

Title:
  Can't connect Logitech Living Room Keyboard [LE]

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Cannot connect a Logitech Illuminated Living Room keyboard to a device
  running bluez5.  There are two versions of the keyboard, a unifying
  receiver version, and a Bluetooth version.  The latter has a BT symbol
  on the 'del' key.  To put the BT version in pairing mode, power on the
  keyboard, then briefly hold the FN and 'del' key together and release.
  A green LED at the top right of the keyboard should start flashing
  quickly.

  Once in pairing mode, the device will become visible on desktop using
  the BT settings UI, however it's *never* shown in the UI on a device
  running the latest Touch ( OTA9.1+ ).  Note, this includes devices
  running a silo version of bluez 5.37, including both arale and
  krillin.  On both devices, the keyboard *is* viewable using
  bluetoothctl.

  Here's the reported attributes of the device from my macair running
  15.10 + bluez 5.37:

  Device DF:08:A9:A0:13:93
Name: K830
Alias: K830
Appearance: 0x03c1
Icon: input-keyboard
Paired: yes
Trusted: no
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: Device Information  (180a--1000-8000-00805f9b34fb)
UUID: Battery Service (180f--1000-8000-00805f9b34fb)
UUID: Human Interface Device (1812--1000-8000-00805f9b34fb)
UUID: Vendor specific   (0001--1000-8000-011f246d)
 

[Kernel-packages] [Bug 1531925] Re: Can't connect Logitech Living Room Keyboard [LE]

2016-03-01 Thread Tony Espy
** Summary changed:

- bluetoothd crash with BTLE keyboard
+ Can't connect Logitech Living Room Keyboard [LE]

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

Title:
  Can't connect Logitech Living Room Keyboard [LE]

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Trying to pair this device and bluetoothd crashed on my Wily laptop
  and the N4 running latest proposed

  build number: 107
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu-pd
  last update: 2016-01-07 11:30:20
  version version: 107
  version ubuntu: 20160107
  version device: 20150911
  version custom: 20150929-2-vivid

  The device is a Logitech Illuminated Living Room keyboard K830 (
  Bluetooth Smart version; !Unifying version ) with an integrated
  trackpad.

  Device DF:08:A9:A0:13:91
   Name: K830
   Alias: K830
   Appearance: 0x03c1
   Icon: input-keyboard
   Paired: no
   Trusted: no
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
   RSSI: -43

  The device would come and go in the devices list from bluetoothctl
  A manual scan would bring it back
  I then tried to manually pair and it failed with
  Failed to pair: org.freedesktop.DBus.Error.NoReply

  On the latop dmesg reports
  [357895.395029] traps: bluetoothd[790] general protection ip:56419e2c0306 
sp:7ffefd2b6760 error:0 in bluetoothd[56419e217000+105000]

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

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


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

2016-03-01 Thread Tony Espy
Note, it turns out that if the headset initiates the connection, then
the HFP features work.  It's only when the connection is initiated from
the phone ( ie. when first pairing the device ) that the HFP features
fail.

To reproduce easily:

1. Goto to settings & forget the device if previously paired
2. Pair the device
3. Make a phone call
4. Try to end the call from the headset

** Summary changed:

- [Jawbone ERA] HFP features not working with Bluez5
+ [Jawbone ERA] HFP features not working with Bluez5 when phone initiates 
connection

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

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

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

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

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

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

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1527354/+subscriptions

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


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

2016-02-29 Thread Tony Espy
Re-tested on arale ( rc-proposed - 258 ) with bluez 5.37 ( from silo 39
) and I'm able to terminate a call from the headset.

Re-tested on krillin ( rc-proposed - 419 ) with bluez 5.37 ( same silo )
and I'm also able to terminate the call from the headset.

Note - I also installed pulseaudio from silo 47, which fixes a
regression in rc-proposed on arale and krillin.

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

Title:
  [Jawbone ERA] HFP features not working with Bluez5

Status in bluez package in Ubuntu:
  New

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

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

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

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

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

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

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

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

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

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


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

2016-02-29 Thread Tony Espy
** Branch linked: lp:~bluetooth/bluez/new-rel-5-37-plus-touch-xenial-
sync

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

Title:
  [Jawbone ERA] HFP features not working with Bluez5

Status in bluez package in Ubuntu:
  New

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

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

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

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

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

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

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

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

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

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


[Kernel-packages] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience

2016-01-28 Thread Tony Espy
@Uranicus

Right now I think we have enough information.   We'll let you know if we
need more...

Hopefully we can get this squared away for OTA10.

Thanks for your patience...

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

Title:
  IN CAR: Battery levels not shared via bluetooth for in car experience

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress
Status in ofono package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu RTM:
  Confirmed

Bug description:
  STEPS:
  Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 
2013 in my instance)

  1. Connect the DUT to the car
  2. On the display panel the battery always shows full

  EXPECTED:
  I expect to see the actual level of the battery on the device

  ACTUAL:
  The display always shows the battery at 100% I assume the default if no info 
is available.

  VERSIONS:
  current build number: 71
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-28 18:01:08
  version version: 71
  version ubuntu: 20150728
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  MODIFICATIONS:
  Installation of silo19 for in car bt fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+subscriptions

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


[Kernel-packages] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience

2016-01-28 Thread Tony Espy
Based on comment #8 and discussion with the product team, I've changed
the ofono tasks back to 'Confirmed' as it seems there's more work to do.


** Changed in: ofono (Ubuntu)
   Status: In Progress => Confirmed

** Changed in: ofono (Ubuntu RTM)
   Status: In Progress => Confirmed

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

Title:
  IN CAR: Battery levels not shared via bluetooth for in car experience

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress
Status in ofono package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu RTM:
  Confirmed

Bug description:
  STEPS:
  Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 
2013 in my instance)

  1. Connect the DUT to the car
  2. On the display panel the battery always shows full

  EXPECTED:
  I expect to see the actual level of the battery on the device

  ACTUAL:
  The display always shows the battery at 100% I assume the default if no info 
is available.

  VERSIONS:
  current build number: 71
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-28 18:01:08
  version version: 71
  version ubuntu: 20150728
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  MODIFICATIONS:
  Installation of silo19 for in car bt fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+subscriptions

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


[Kernel-packages] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience

2016-01-28 Thread Tony Espy
** Changed in: ofono (Ubuntu RTM)
   Status: Fix Released => In Progress

** Changed in: ofono (Ubuntu)
   Status: Fix Released => In Progress

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

Title:
  IN CAR: Battery levels not shared via bluetooth for in car experience

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress
Status in ofono package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu RTM:
  Confirmed

Bug description:
  STEPS:
  Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 
2013 in my instance)

  1. Connect the DUT to the car
  2. On the display panel the battery always shows full

  EXPECTED:
  I expect to see the actual level of the battery on the device

  ACTUAL:
  The display always shows the battery at 100% I assume the default if no info 
is available.

  VERSIONS:
  current build number: 71
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-28 18:01:08
  version version: 71
  version ubuntu: 20150728
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  MODIFICATIONS:
  Installation of silo19 for in car bt fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+subscriptions

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


[Kernel-packages] [Bug 1531925] Re: bluetoothd crash with BTLE keyboard

2016-01-25 Thread Tony Espy
** Changed in: bluez (Ubuntu)
   Status: New => Incomplete

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

Title:
  bluetoothd crash with BTLE keyboard

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Trying to pair this device and bluetoothd crashed on my Wily laptop
  and the N4 running latest proposed

  build number: 107
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu-pd
  last update: 2016-01-07 11:30:20
  version version: 107
  version ubuntu: 20160107
  version device: 20150911
  version custom: 20150929-2-vivid

  
  The device is a Logitech keyboard with an integrated trackpad.

  Device DF:08:A9:A0:13:91
   Name: K830
   Alias: K830
   Appearance: 0x03c1
   Icon: input-keyboard
   Paired: no
   Trusted: no
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
   RSSI: -43

  The device would come and go in the devices list from bluetoothctl
  A manual scan would bring it back
  I then tried to manually pair and it failed with
  Failed to pair: org.freedesktop.DBus.Error.NoReply

  On the latop dmesg reports
  [357895.395029] traps: bluetoothd[790] general protection ip:56419e2c0306 
sp:7ffefd2b6760 error:0 in bluetoothd[56419e217000+105000]

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

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


[Kernel-packages] [Bug 1531925] Re: bluetoothd crash with BTLE keyboard

2016-01-25 Thread Tony Espy
** Description changed:

  Trying to pair this device and bluetoothd crashed on my Wily laptop and
  the N4 running latest proposed
  
  build number: 107
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu-pd
  last update: 2016-01-07 11:30:20
  version version: 107
  version ubuntu: 20160107
  version device: 20150911
  version custom: 20150929-2-vivid
  
- 
- The device is a Logitech keyboard with an integrated trackpad.
+ The device is a Logitech Illuminated Living Room keyboard K830 (
+ Bluetooth Smart version; !Unifying version ) with an integrated
+ trackpad.
  
  Device DF:08:A9:A0:13:91
   Name: K830
   Alias: K830
   Appearance: 0x03c1
   Icon: input-keyboard
   Paired: no
   Trusted: no
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
   RSSI: -43
  
  The device would come and go in the devices list from bluetoothctl
  A manual scan would bring it back
  I then tried to manually pair and it failed with
  Failed to pair: org.freedesktop.DBus.Error.NoReply
  
  On the latop dmesg reports
  [357895.395029] traps: bluetoothd[790] general protection ip:56419e2c0306 
sp:7ffefd2b6760 error:0 in bluetoothd[56419e217000+105000]

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

Title:
  bluetoothd crash with BTLE keyboard

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Trying to pair this device and bluetoothd crashed on my Wily laptop
  and the N4 running latest proposed

  build number: 107
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu-pd
  last update: 2016-01-07 11:30:20
  version version: 107
  version ubuntu: 20160107
  version device: 20150911
  version custom: 20150929-2-vivid

  The device is a Logitech Illuminated Living Room keyboard K830 (
  Bluetooth Smart version; !Unifying version ) with an integrated
  trackpad.

  Device DF:08:A9:A0:13:91
   Name: K830
   Alias: K830
   Appearance: 0x03c1
   Icon: input-keyboard
   Paired: no
   Trusted: no
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
   RSSI: -43

  The device would come and go in the devices list from bluetoothctl
  A manual scan would bring it back
  I then tried to manually pair and it failed with
  Failed to pair: org.freedesktop.DBus.Error.NoReply

  On the latop dmesg reports
  [357895.395029] traps: bluetoothd[790] general protection ip:56419e2c0306 
sp:7ffefd2b6760 error:0 in bluetoothd[56419e217000+105000]

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

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


[Kernel-packages] [Bug 1531925] Re: bluetoothd crash with BTLE keyboard

2016-01-25 Thread Tony Espy
A couple of updates...

 - I've verified that the keyboard is indeed a low-energy device.

 - I'm able to see the device on my MacAir running 15.10 + the latest
5.37 bluez packages both in the indicator, and via bluetoothctl

 - I cannot successfully pair with the device from the indicator or
bluetoothctl

 - At some point, 'bluetoothctl info' shows that the device is paired &
connected, however the keyboard BT indicator is still blinking, which
means the keyboard is still in pairing mode, and it cannot be used.

 - When I attempt to connect using gattool, I get the following error:

Attempting to connect to DF:08:A9:A0:13:92
Error: connect error: Transport endpoint is not connected (107)

I also see the following error messages in my syslog:

Jan 25 12:06:24 shrike bluetoothd[949]: Unable to register GATT service with 
handle 0x0046 for device DF:08:A9:A0:13:92
Jan 25 12:06:24 shrike bluetoothd[949]: Report Map read failed: Attribute 
requires authentication before read/write
Jan 25 12:06:24 shrike bluetoothd[949]: Protocol Mode characteristic read 
failed: Attribute requires authentication before read/write
Jan 25 12:06:24 shrike bluetoothd[949]: HID Information read failed: Attribute 
requires authentication before read/write
Jan 25 12:06:25 shrike bluetoothd[949]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write

 - I was able to use the device with my new iMac, which is running El
Capitan.  When I pair the keyboard, I'm prompted for a PIN code.

So, it looks like PIN authentication isn't being handled properly for
this keyboard.

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

Title:
  bluetoothd crash with BTLE keyboard

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Trying to pair this device and bluetoothd crashed on my Wily laptop
  and the N4 running latest proposed

  build number: 107
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu-pd
  last update: 2016-01-07 11:30:20
  version version: 107
  version ubuntu: 20160107
  version device: 20150911
  version custom: 20150929-2-vivid

  The device is a Logitech Illuminated Living Room keyboard K830 (
  Bluetooth Smart version; !Unifying version ) with an integrated
  trackpad.

  Device DF:08:A9:A0:13:91
   Name: K830
   Alias: K830
   Appearance: 0x03c1
   Icon: input-keyboard
   Paired: no
   Trusted: no
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
   RSSI: -43

  The device would come and go in the devices list from bluetoothctl
  A manual scan would bring it back
  I then tried to manually pair and it failed with
  Failed to pair: org.freedesktop.DBus.Error.NoReply

  On the latop dmesg reports
  [357895.395029] traps: bluetoothd[790] general protection ip:56419e2c0306 
sp:7ffefd2b6760 error:0 in bluetoothd[56419e217000+105000]

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

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


[Kernel-packages] [Bug 1531925] Re: bluetoothd crash with BTLE keyboard

2016-01-25 Thread Tony Espy
Also, I have yet to be able to reproduce the crash...

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

Title:
  bluetoothd crash with BTLE keyboard

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Trying to pair this device and bluetoothd crashed on my Wily laptop
  and the N4 running latest proposed

  build number: 107
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu-pd
  last update: 2016-01-07 11:30:20
  version version: 107
  version ubuntu: 20160107
  version device: 20150911
  version custom: 20150929-2-vivid

  The device is a Logitech Illuminated Living Room keyboard K830 (
  Bluetooth Smart version; !Unifying version ) with an integrated
  trackpad.

  Device DF:08:A9:A0:13:91
   Name: K830
   Alias: K830
   Appearance: 0x03c1
   Icon: input-keyboard
   Paired: no
   Trusted: no
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
   RSSI: -43

  The device would come and go in the devices list from bluetoothctl
  A manual scan would bring it back
  I then tried to manually pair and it failed with
  Failed to pair: org.freedesktop.DBus.Error.NoReply

  On the latop dmesg reports
  [357895.395029] traps: bluetoothd[790] general protection ip:56419e2c0306 
sp:7ffefd2b6760 error:0 in bluetoothd[56419e217000+105000]

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

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


[Kernel-packages] [Bug 1533716] Re: Delay of approx. 60 seconds when an outgoing call is innitiated by the IN CAR bluetooth system

2016-01-15 Thread Tony Espy
** Also affects: ofono (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ofono (Ubuntu RTM)
   Importance: Undecided
   Status: New

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

** Changed in: ofono (Ubuntu RTM)
   Status: New => In Progress

** Branch linked: lp:~morphis/ofono/ota9-suspend-fix

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

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

** Changed in: ofono (Ubuntu)
 Assignee: (unassigned) => Simon Fels (morphis)

** Changed in: ofono (Ubuntu RTM)
 Assignee: (unassigned) => Simon Fels (morphis)

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

Title:
  Delay of approx. 60 seconds when an outgoing call is innitiated by the
  IN CAR bluetooth system

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  Confirmed
Status in bluez package in Ubuntu RTM:
  Invalid
Status in ofono package in Ubuntu RTM:
  In Progress

Bug description:
  My system:

  current build number: 228
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-01-13 08:28:26
  version version: 228
  version ubuntu: 20160113
  version device: 20160108-efc96d8
  version custom: 2015--36-46-vivid

  Since several days (not weeks, so something has changed in the last
  couple days!) I have the following situation with my BQ 4.5 in my car.
  When I initiate a call from the IN CAR system (where my phone is
  connected to) I experience sometimes the normal behaviour that the
  call is directly established.

  Sometimes nothing happens. The call is not established and my in car system 
says that the attempt to carry out a call has failed (this message comes after 
approx. 15 seconds after initiation of the call).
  Then approx. 60 seconds after the initiation of the call the call is all of a 
sudden established (without any further interaction). I currently was not able 
to find a logic in this. Here my "log"-file of what I did today:

  -

  13.01.2016

  9:00 h call initiated from car, call directly established
  9:03 h call initiated from car (phone book), approx. 60 sec. delay between 
initiation and call being established
  9:06 h call initiated from car, call directly established
  9:09 h call initiated from car (phone book), approx. 60 sec. delay between 
initiation and call being established

  9:26 h New pairing between phone and car, retry

  9:30 h call initiated from car, call directly established
  9:33 h call initiated from car (phone book), approx. 60 sec. delay between 
initiation and call being established
  9:36 h call initiated from car, call directly established
  9:39 h call initiated from car (phone book), approx. 60 sec. delay between 
initiation and call being established
  9:42 h call initiated from car, call directly established
  9:45 h call initiated from car, call directly established (this time again 
via phone book)
  9:48 h call initiated from car (via voice command), approx. 60 sec. delay 
between initiation and call being established
  9:52 h call initiated from phone itself, call established and correctly 
routed via car speaker

  I have added the syslog, upstart-files to the bug report for further
  analysis.

  Uranicus

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533716/+subscriptions

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


[Kernel-packages] [Bug 1533716] Re: Delay of approx. 60 seconds when an outgoing call is innitiated by the IN CAR bluetooth system

2016-01-15 Thread Tony Espy
** Changed in: ofono (Ubuntu RTM)
   Status: In Progress => Fix Committed

** Changed in: ofono (Ubuntu RTM)
   Importance: Undecided => Critical

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

** Changed in: ofono (Ubuntu)
   Importance: High => Critical

** Changed in: ofono (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Delay of approx. 60 seconds when an outgoing call is innitiated by the
  IN CAR bluetooth system

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  Fix Committed
Status in bluez package in Ubuntu RTM:
  Invalid
Status in ofono package in Ubuntu RTM:
  Fix Committed

Bug description:
  My system:

  current build number: 228
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-01-13 08:28:26
  version version: 228
  version ubuntu: 20160113
  version device: 20160108-efc96d8
  version custom: 2015--36-46-vivid

  Since several days (not weeks, so something has changed in the last
  couple days!) I have the following situation with my BQ 4.5 in my car.
  When I initiate a call from the IN CAR system (where my phone is
  connected to) I experience sometimes the normal behaviour that the
  call is directly established.

  Sometimes nothing happens. The call is not established and my in car system 
says that the attempt to carry out a call has failed (this message comes after 
approx. 15 seconds after initiation of the call).
  Then approx. 60 seconds after the initiation of the call the call is all of a 
sudden established (without any further interaction). I currently was not able 
to find a logic in this. Here my "log"-file of what I did today:

  -

  13.01.2016

  9:00 h call initiated from car, call directly established
  9:03 h call initiated from car (phone book), approx. 60 sec. delay between 
initiation and call being established
  9:06 h call initiated from car, call directly established
  9:09 h call initiated from car (phone book), approx. 60 sec. delay between 
initiation and call being established

  9:26 h New pairing between phone and car, retry

  9:30 h call initiated from car, call directly established
  9:33 h call initiated from car (phone book), approx. 60 sec. delay between 
initiation and call being established
  9:36 h call initiated from car, call directly established
  9:39 h call initiated from car (phone book), approx. 60 sec. delay between 
initiation and call being established
  9:42 h call initiated from car, call directly established
  9:45 h call initiated from car, call directly established (this time again 
via phone book)
  9:48 h call initiated from car (via voice command), approx. 60 sec. delay 
between initiation and call being established
  9:52 h call initiated from phone itself, call established and correctly 
routed via car speaker

  I have added the syslog, upstart-files to the bug report for further
  analysis.

  Uranicus

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533716/+subscriptions

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


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

2016-01-15 Thread Tony Espy
Re-tested on krillin, rc-proposed #231.  Same result, my Jawbone only
works as a headset.  Same result on arale ( rc-proposed, #220 ).  On
mako ( rc-proposed, #331 ) I couldn't even get the headset function to
work.

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

Title:
  [Jawbone ERA] HFP features not working with Bluez5

Status in bluez package in Ubuntu:
  New

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

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

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

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

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

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

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

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

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

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


[Kernel-packages] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience

2016-01-11 Thread Tony Espy
@Matthias

So what you're saying is that you see the correct battery level
displayed in your car the first time after you connect the phone and
car, and then after you restart the car, the battery level is just shown
as full? Once this happens, does the battery level displayed ever change
or does it continually read as full after the car restart?

I recently made some improvement to the way the battery level is
monitored, however these changes have no yet landed in our proposed
images.  I'll discuss with my team and see if we can land this before
the deadline for OTA9.

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

Title:
  IN CAR: Battery levels not shared via bluetooth for in car experience

Status in Canonical System Image:
  Fix Committed
Status in bluez package in Ubuntu:
  Fix Released
Status in ofono package in Ubuntu:
  Fix Released
Status in ofono package in Ubuntu RTM:
  Fix Released

Bug description:
  STEPS:
  Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 
2013 in my instance)

  1. Connect the DUT to the car
  2. On the display panel the battery always shows full

  EXPECTED:
  I expect to see the actual level of the battery on the device

  ACTUAL:
  The display always shows the battery at 100% I assume the default if no info 
is available.

  VERSIONS:
  current build number: 71
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-28 18:01:08
  version version: 71
  version ubuntu: 20150728
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  MODIFICATIONS:
  Installation of silo19 for in car bt fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+subscriptions

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


[Kernel-packages] [Bug 1531515] Re: Bluetooth cannot be enabled on Ubuntu Touch rc-proposed Nexus 4

2016-01-06 Thread Tony Espy
I just flashed my mako to the same image as Willem ( rc-proposed/331 )
and couldn't reproduce the problem.  After a fresh flash,  I rebooted
the device multiple times with BT enabled, after each reboot, BT was
still enabled.  I rebooted ten times, and wasn't able to reproduce...

I also verified that toggling BT off and back on again works as
expected.

A quick look at the syslog shows that the bluez5 version of bluetoothd
was only started at 14:41:46 which appears to be after the final reboot
mentioned in comment #2.  The previous version of bluetoothd running on
the phone was 4.101, which was started at 12:05:44.

@Willem, what time did you flash the device?

My guess is this may have been some kind of system update hiccup.

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

Title:
  Bluetooth cannot be enabled on Ubuntu Touch rc-proposed Nexus 4

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After switching from OTA8.5 to rc-proposed (to test if my BT keyboard would 
work with that) BT cannot be turned on any more.
  I can flip the switch, but after 30s it is switched off again (probably never 
turned on).
  I am unable to discover any BT devices.

  Running bluetoothctl on the devices from the terminal and then entering 
"show" results in:
  "No default controller available"

  I switched to rc-proposed for the Nexus 4 like this:
  ubuntu-device-flash touch --channel=ubuntu-touch/rc-proposed/ubuntu

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

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


  1   2   3   >