[Kernel-packages] [Bug 1797314] [NEW] fscache: bad refcounting in fscache_op_complete leads to OOPS

[Daniel Axtens]

Public bug reported:

SRU Justification
-

[Impact]

A kernel BUG is sometimes observed when using fscache:
[4740718.880898] FS-Cache:
[4740718.880920] FS-Cache: Assertion failed
[4740718.880934] FS-Cache: 0 > 0 is false
[4740718.881001] [ cut here ]
[4740718.881017] kernel BUG at 
/usr/src/linux-4.4.0/fs/fscache/operation.c:449!
[4740718.881040] invalid opcode:  [#1] SMP

[4740718.892659] Call Trace:
[4740718.893506]  [] cachefiles_read_copier+0x3a9/0x410 
[cachefiles]
[4740718.894374]  [] fscache_op_work_func+0x22/0x50 
[fscache]
[4740718.895180]  [] process_one_work+0x150/0x3f0
[4740718.895966]  [] worker_thread+0x11a/0x470
[4740718.896753]  [] ? __schedule+0x359/0x980
[4740718.897783]  [] ? rescuer_thread+0x310/0x310
[4740718.898581]  [] kthread+0xd6/0xf0
[4740718.899469]  [] ? kthread_park+0x60/0x60
[4740718.900477]  [] ret_from_fork+0x3f/0x70
[4740718.901514]  [] ? kthread_park+0x60/0x60

[Problem]

In include/fscache-cache.h, fscache_retrieval_complete reads, in part:

atomic_sub(n_pages, &op->n_pages);
if (atomic_read(&op->n_pages) <= 0)
fscache_op_complete(&op->op, true);

The code is using atomic_sub followed by an atomic_read. This causes two
threads doing a decrement of pages to race with each other seeing the
op->refcount <= 0 at same time, and end up calling fscache_op_complete
in both the threads leading to the OOPS.

[Fix]
The fix is trivial to use atomic_sub_return instead of two calls.

[Testcase]
The user has tested the patch successfully on their fscache/cachefiles setup.

[Regression Potential]
Limited to fscache. Small, comprehensible change.

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

** Description changed:

  SRU Justification
  -
  
  [Impact]
  
  A kernel BUG is sometimes observed when using fscache:
+ [4740718.880898] FS-Cache:
+ [4740718.880920] FS-Cache: Assertion failed
+ [4740718.880934] FS-Cache: 0 > 0 is false
+ [4740718.881001] [ cut here ]
+ [4740718.881017] kernel BUG at 
/usr/src/linux-4.4.0/fs/fscache/operation.c:449!
+ [4740718.881040] invalid opcode:  [#1] SMP
+ 
+ [4740718.892659] Call Trace:
+ [4740718.893506]  [] cachefiles_read_copier+0x3a9/0x410 
[cachefiles]
+ [4740718.894374]  [] fscache_op_work_func+0x22/0x50 
[fscache]
+ [4740718.895180]  [] process_one_work+0x150/0x3f0
+ [4740718.895966]  [] worker_thread+0x11a/0x470
+ [4740718.896753]  [] ? __schedule+0x359/0x980
+ [4740718.897783]  [] ? rescuer_thread+0x310/0x310
+ [4740718.898581]  [] kthread+0xd6/0xf0
+ [4740718.899469]  [] ? kthread_park+0x60/0x60
+ [4740718.900477]  [] ret_from_fork+0x3f/0x70
+ [4740718.901514]  [] ? kthread_park+0x60/0x60
  
- Jun 25 11:32:08  kernel: [4740718.880898] FS-Cache:
- Jun 25 11:32:08  kernel: [4740718.880920] FS-Cache: Assertion failed
- Jun 25 11:32:08  kernel: [4740718.880934] FS-Cache: 0 > 0 is false
- Jun 25 11:32:08  kernel: [4740718.881001] [ cut here 
]
- Jun 25 11:32:08  kernel: [4740718.881017] kernel BUG at 
/usr/src/linux-4.4.0/fs/fscache/operation.c:449!
- Jun 25 11:32:08  kernel: [4740718.881040] invalid opcode:  [#1] SMP
- ...
- Jun 25 11:32:08  kernel: [4740718.892659] Call Trace:
- Jun 25 11:32:08  kernel: [4740718.893506]  [] 
cachefiles_read_copier+0x3a9/0x410 [cachefiles]
- Jun 25 11:32:08  kernel: [4740718.894374]  [] 
fscache_op_work_func+0x22/0x50 [fscache]
- Jun 25 11:32:08  kernel: [4740718.895180]  [] 
process_one_work+0x150/0x3f0
- Jun 25 11:32:08  kernel: [4740718.895966]  [] 
worker_thread+0x11a/0x470
- Jun 25 11:32:08  kernel: [4740718.896753]  [] ? 
__schedule+0x359/0x980
- Jun 25 11:32:08  kernel: [4740718.897783]  [] ? 
rescuer_thread+0x310/0x310
- Jun 25 11:32:08  kernel: [4740718.898581]  [] 
kthread+0xd6/0xf0
- Jun 25 11:32:08  kernel: [4740718.899469]  [] ? 
kthread_park+0x60/0x60
- Jun 25 11:32:08  kernel: [4740718.900477]  [] 
ret_from_fork+0x3f/0x70
- Jun 25 11:32:08  kernel: [4740718.901514]  [] ? 
kthread_park+0x60/0x60
- 
  [Problem]
  
  In include/fscache-cache.h, fscache_retrieval_complete reads, in part:
  
- atomic_sub(n_pages, &op->n_pages);
- if (atomic_read(&op->n_pages) <= 0)
- fscache_op_complete(&op->op, true);
- 
- The code is using atomic_sub followed by an atomic_read. This causes two 
threads doing a decrement of pages to race with each other seeing the 
op->refcount <= 0 at same time,
- and end up calling fscache_op_complete in both the threads leading to the 
OOPS.
- 
+ atomic_sub(n_pages, &op->n_pages);
+ if (atomic_read(&op->n_pages) <= 0)
+ fscache_op_complete(&op->op, true);
+ 
+ The code is using atom

[Kernel-packages] [Bug 1783140] Re: KVM live migration fails

[ Christian Ehrhardt ]

Yes both are known to be flaky - thanks!

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

Title:
  KVM live migration fails

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Fix Released
Status in qemu source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Backport fix from the 2.6.2 stable branch to the qemu 2.5 in Xenial

   * Newer guests might use virtio attributes that are clobbered on 
 migration with the old qemu code.

  [Test Case]

   * Setup two Xenial hosts on ppc64el

   * Create a guest that has a rather new kernel (>=4.14) I'd recommend 
 Bionic

   * Migrate that guest from Host1 to Host2

  [Regression Potential]

   * The modification could affect virtio handling in other cases in a non 
 expected way, but mostly related to migrations. So the expected 
 regression would be issues to migrate properly.
 I verified plenty of migrations in regression testing and we had
 this very code in the Yakkety release as we picked 2.6.1 stable release 
 back then. Due to that it is actually pretty well tested and should not 
 really regress anything out in the wild.

  [Other Info]
   
   * So far this only triggers on the confused endian marshalling on 
 ppc64el, but in theory a different case could trigger it on x86 just as 
 much.

  ---

  Environment:
  2 POWER8 with Ubuntu 16.04.4 LTS as KVM hypervisor.
  1 KVM guest with Ubuntu 18.04 LTS. Virtual disk for the guest is a qcow2 file 
on an NFS share, accessible from both hypervisors, so live migration is 
possible and works for all other guests (SLES, RHEL, Ubunutu 16.04),
  Live migratino of Ubuntu 18.04 guest fails on ppc, while the same test on an 
x86_64 environment suceeds.

  root@pkvm2:~# virsh migrate --persistent --live p8lnxtst4 
qemu+ssh://pkvm1/system
  error: internal error: early end of file from monitor, possible problem: 
2018-07-23T11:12:25.586385Z qemu-system-ppc64: VQ 0 size 0x100 Guest index 
0x38aa inconsistent with Host index 0xa980: delta 0x8f2a
  2018-07-23T11:12:25.586434Z qemu-system-ppc64: error while loading state for 
instance 0x0 of device 'pci@8002000:01.0/virtio-net'
  2018-07-23T11:12:25.587246Z qemu-system-ppc64: load of migration failed: 
Operation not permitted

  root@pkvm2:~# uname -a
  Linux pkvm2 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:51:21 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux

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

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

[Kernel-packages] [Bug 1759961] Re: Update to bluez 5.50

[Daniel van Vugt]

Chanho,

Yes we can do that, and the patch [1] appears to be compatible with
5.48. However, please start by logging a new bug describing the problem
you are facing. Just run this command on the affected machine to open
the new bug:

  ubuntu-bug bluez


[1] https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=b916c9dec

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

Title:
  Update to bluez 5.50

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  From upstream:
  http://www.bluez.org/release-of-bluez-5-49/

  Release of BlueZ 5.49

  This is mostly a bug fix release, with fixes to features such as
  AVCTP, OBEX, GATT and Mesh. There are however some notable new
  features also, such as improved heartbeat management support in
  meshctl as well as a new experimental ConnectDevice D-Bus method on
  the Adapter interface, which can be used for quick device object
  creation for testing purpose or when information about the device has
  been received over some Out-of-Band channel.

  Upstream changelog:
  https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog

  ver 5.49:
Fix issue with configuring discoverable advertising flag.
Fix issue with bearer selection and single mode controllers.
Fix issue with Connect and ConnectProfile returning in progress.
Fix issue with missing Paired property change when not bonded.
Fix issue with storage for controllers without public address.
Fix issue with handling AVCTP disconnecting the channel queue.
Fix issue with not clearing connectable setting on power off.
Fix issue with creating multiple mgmt socket instances.
Fix issue with GATT server and BR/EDR only devices.
Fix issue with InterfaceAdded event ordering.
Add support for generic ConnectDevice method call.
Add support for Mesh heartbeat client functionality.

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

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

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

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1797304

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

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

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

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

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

Title:
  Keyboard backlight sysfs sometimes is missing on Dell laptops

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  When the keyboard backlight sysfs is missing, userspace does not know
  the current keyboard backlight brightness.

  [Fix]
  There's a loading order race condition, between the dell-smbios and its
  backends, dell-smbios-{smm,wmi}. 
  Build them as one module can solve the issue.

  The last patch is what we want, but pulls the entire series as a
  whole.

  [Test]
  The backlight sysfs always exists with the patch. Userspace now knows
  the current keyboard backlight brightness.

  [Regression Potential]
  Low. No functional change, as it simply links the modules together.
  Limits to Dell machines.

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

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

[Kernel-packages] [Bug 1795292] Re: ELAN469D touch pad not working

[Jake Jensen]

Kernel 4.19.0-rc7
Laptop is a Lenovo IdeaPad 330S-15ARR. Same issue as everyone else. 

Attempting to install various ALPS drivers doesn't work, nor does the
i8042.reset workaround.

Patching elan_i2c_core to add the 469D entry also failed.

Notes: noapic is required for the laptop to load into 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/1795292

Title:
  ELAN469D touch pad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on
  this Lenovo Ideapad 330S-15ARR laptop.  The touch pad doesn't work in
  either.

  Some possibly relevant info from dmesg:
  i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy 
regulator
  i2c_designware AMDI0010:01: controller timed out

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xorbit 2086 F pulseaudio
   /dev/snd/pcmC1D0p:   xorbit 2086 F...m pulseaudio
   /dev/snd/controlC0:  xorbit 2086 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Sep 30 23:14:26 2018
  InstallationDate: Installed on 2018-09-20 (10 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 81FB
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 
rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 
elan_i2c.dyndbg=+p
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago)
  dmi.bios.date: 06/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WCN22WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330S-15ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR:
  dmi.product.family: ideapad 330S-15ARR
  dmi.product.name: 81FB
  dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR
  dmi.product.version: Lenovo ideapad 330S-15ARR
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-20 (13 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  cosmic
  Uname: Linux 4.19.0-041900rc6-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1784152] Re: i2c_hid_get_input floods system logs

[Ascaris]

Niel, it's still happening on my system as of now (October 10, 2018),
using latest Ubuntu kernel.  Did you change the touchpad to basic mode
by any chance?

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

Title:
  i2c_hid_get_input floods system logs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.15.0-29.31-generic 4.15.18

  After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system
  logs are flooded whenever I move the cursor with my touchpad.

  It looks like this:
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  etc...

  This problem did not occur on the previous kernel version so there
  must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file.
  This seems to be fixed in a recent commit here:
  
https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c

  I am currently running the older kernel version but would still like
  to be up to date without this flooding happening.

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

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

[Kernel-packages] [Bug 1797304] [NEW] Keyboard backlight sysfs sometimes is missing on Dell laptops

[Kai-Heng Feng]

Public bug reported:

[Impact]
When the keyboard backlight sysfs is missing, userspace does not know
the current keyboard backlight brightness.

[Fix]
There's a loading order race condition, between the dell-smbios and its
backends, dell-smbios-{smm,wmi}. 
Build them as one module can solve the issue.

The last patch is what we want, but pulls the entire series as a whole.

[Test]
The backlight sysfs always exists with the patch. Userspace now knows
the current keyboard backlight brightness.

[Regression Potential]
Low. No functional change, as it simply links the modules together.
Limits to Dell machines.

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

Title:
  Keyboard backlight sysfs sometimes is missing on Dell laptops

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  When the keyboard backlight sysfs is missing, userspace does not know
  the current keyboard backlight brightness.

  [Fix]
  There's a loading order race condition, between the dell-smbios and its
  backends, dell-smbios-{smm,wmi}. 
  Build them as one module can solve the issue.

  The last patch is what we want, but pulls the entire series as a
  whole.

  [Test]
  The backlight sysfs always exists with the patch. Userspace now knows
  the current keyboard backlight brightness.

  [Regression Potential]
  Low. No functional change, as it simply links the modules together.
  Limits to Dell machines.

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

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

[Kernel-packages] [Bug 1759961] Re: Update to bluez 5.50

[Chanho Park]

Hi all,

I've encountered Heart rate profile connection error of bluez-5.48 in
Bionic. It can be resolved in bluez 5.49 version from below commit.

- Fix issue with Connect and ConnectProfile returning in progress.

Do you have a plan to upgrade the bluez version to 5.50 for Bionic as
well? If not, could you pick the patch for Ubuntu bionic's bluez
version. If you want to create a ticket for this release, I can make it.

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

Title:
  Update to bluez 5.50

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  From upstream:
  http://www.bluez.org/release-of-bluez-5-49/

  Release of BlueZ 5.49

  This is mostly a bug fix release, with fixes to features such as
  AVCTP, OBEX, GATT and Mesh. There are however some notable new
  features also, such as improved heartbeat management support in
  meshctl as well as a new experimental ConnectDevice D-Bus method on
  the Adapter interface, which can be used for quick device object
  creation for testing purpose or when information about the device has
  been received over some Out-of-Band channel.

  Upstream changelog:
  https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog

  ver 5.49:
Fix issue with configuring discoverable advertising flag.
Fix issue with bearer selection and single mode controllers.
Fix issue with Connect and ConnectProfile returning in progress.
Fix issue with missing Paired property change when not bonded.
Fix issue with storage for controllers without public address.
Fix issue with handling AVCTP disconnecting the channel queue.
Fix issue with not clearing connectable setting on power off.
Fix issue with creating multiple mgmt socket instances.
Fix issue with GATT server and BR/EDR only devices.
Fix issue with InterfaceAdded event ordering.
Add support for generic ConnectDevice method call.
Add support for Mesh heartbeat client functionality.

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

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

[Kernel-packages] [Bug 1730321] Re: Ubuntu VM is not detecting the disks connected to Availa beach (LSI/Avago) in Pass Thru mode

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Ubuntu VM is not detecting the disks connected to Availa beach
  (LSI/Avago)  in Pass Thru mode

Status in linux package in Ubuntu:
  Expired
Status in xubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  Below is my setup details:
   
  C240 M4 24HDD server with AVB card (FW 24.12.1-0048) and Boot SSDs.
  Installed ESXi 6.0U1b in the boot SSD in AHCI mode.
  Updated the latest ESXi Native driver on this. (VMWare-Native-6.610.17.00)
  Created a VM and Installed Ubuntu 14.04.04.
  AVB card has one RAID1 VD, one JBOD and all other UG drives.
  Assigned the AVB controller as a Pass thorugh to ESXi host.
  Added AVB controller as a Pass through device to the Ubuntu VM.
  Updated the /etc/vmware/passthru.map file with the device ID and vendor ID of 
AVB card.
  Updated the Ubuntu VM with the latest MR driver 06.810

  I want to run some IOs to the disks connected to the AVB card from Ubuntu VM. 
But I am unable to see the disks from the VM.
  I am seeing so many call traces in the console related to megaraid_sas and 
see the attached screenshots of the same.

  Avago is able to reproduce the issue in their lab and see the attached
  email thread on this discussion.

  Note : The same scenario is working fine with Ubuntu 12.x series
  VM's.This issue is occurring both Ubuntu 14.x.x and 16.x.x series
  guest operating systems.

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

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

[Kernel-packages] [Bug 1797002] Re: all my bluetooth headsets skips terribly after todays update

[Daniel van Vugt]

The change could also be a coincidence and environmental, like:

 * a new 2.4GHz wifi network or device was recently introduced nearby,
degrading Bluetooth signal quality.

 * a new Bluetooth device was introduced nearby, degrading the signal
quality of audio.

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

Title:
  all my bluetooth headsets skips terribly after todays update

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  all my bluetooth headsets skips terribly after today's system update.
  it is heavy noticeable even on audio setting test form.
  it work just fine today before i applied updates.

  even reinstall ubuntu from scratch - didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  9 18:40:44 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-10-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.66
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1968
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 93.52
  dmi.chassis.asset.tag: 5CG32907G7
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 088510305B0610100
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:17:29:62:BE:6A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:16831 acl:64 sco:0 events:1798 errors:0
TX bytes:688571 acl:2399 sco:0 commands:125 errors:0

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

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

[Kernel-packages] [Bug 1797031] Re: Touchscreen/stylus always reports 1% battery [patch]

[Kai-Heng Feng]

Upstream maintainers are busy, so it's quite normal. Please be patient.

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

Title:
  Touchscreen/stylus always reports 1% battery [patch]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell 5379 with a touchscreen that always reports 1% battery
  with the stylus. This pops up a low battery notification the first
  time I use the stylus after booting. The attached patch tells the
  kernel to ignore the battery on this particular device, since it
  appears to not report information correctly anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  trent  1734 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  9 22:42:47 2018
  HibernationDevice: RESUME=UUID=aef6a948-4599-4581-99a2-44b7944d2d58
  InstallationDate: Installed on 2018-05-10 (153 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:2361 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0025 Intel Corp. 
   Bus 001 Device 002: ID 0bda:5696 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5379
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 05G60G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1796353] Re: linux-kvm: 4.18.0-1003.3 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Fix Released

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

Title:
  linux-kvm: 4.18.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1797002] Re: all my bluetooth headsets skips terribly after todays update

[Daniel van Vugt]

Thanks Ivan. It appears your bluez and pulseaudio packages last updated
on 2018-07-25, so they won't be the cause of any recent regressions.

I think this kernel upgrade on 2018-10-09 might be what changed:
linux-generic:amd64 (4.15.0.29.31 --> 4.15.0.36.38)

Please try downgrading your kernel, like to version 4.14:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/


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

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

Title:
  all my bluetooth headsets skips terribly after todays update

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  all my bluetooth headsets skips terribly after today's system update.
  it is heavy noticeable even on audio setting test form.
  it work just fine today before i applied updates.

  even reinstall ubuntu from scratch - didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  9 18:40:44 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-10-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.66
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1968
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 93.52
  dmi.chassis.asset.tag: 5CG32907G7
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 088510305B0610100
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:17:29:62:BE:6A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:16831 acl:64 sco:0 events:1798 errors:0
TX bytes:688571 acl:2399 sco:0 commands:125 errors:0

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

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

[Kernel-packages] [Bug 1797296] Re: nouveau lockup

[Brad Figg]

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

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

Title:
  nouveau lockup

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Oct 10 11:38:30 sun kernel: [17891.545097] nouveau :03:00.0: fifo: 
SCHED_ERROR 0a [CTXSW_TIMEOUT]
  Oct 10 11:38:30 sun kernel: [17891.545109] nouveau :03:00.0: fifo: 
runlist 0: scheduled for recovery
  Oct 10 11:38:30 sun kernel: [17891.545118] nouveau :03:00.0: fifo: 
channel 12: killed
  Oct 10 11:38:30 sun kernel: [17891.545125] nouveau :03:00.0: fifo: engine 
0: scheduled for recovery
  Oct 10 11:38:30 sun kernel: [17891.545563] nouveau :03:00.0: 
systemd-logind[944]: channel 12 killed!
  Oct 10 11:42:24 sun kernel: [18125.788110] INFO: task kworker/u32:0:14726 
blocked for more than 120 seconds.
  Oct 10 11:42:24 sun kernel: [18125.788114]   Tainted: GW 
4.18.0-8-generic #9-Ubuntu
  Oct 10 11:42:24 sun kernel: [18125.788115] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Oct 10 11:42:24 sun kernel: [18125.788117] kworker/u32:0   D0 14726  
2 0x8000
  Oct 10 11:42:24 sun kernel: [18125.788154] Workqueue: events_unbound 
nv50_disp_atomic_commit_work [nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788155] Call Trace:
  Oct 10 11:42:24 sun kernel: [18125.788161]  __schedule+0x29e/0x840
  Oct 10 11:42:24 sun kernel: [18125.788178]  ? nvkm_ioctl_ntfy_get+0x5c/0x80 
[nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788180]  schedule+0x2c/0x80
  Oct 10 11:42:24 sun kernel: [18125.788181]  schedule_timeout+0x258/0x360
  Oct 10 11:42:24 sun kernel: [18125.788197]  ? nvif_object_ioctl+0x47/0x50 
[nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788220]  ? nouveau_bo_rd32+0x2a/0x30 
[nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788242]  ? nv84_fence_read+0x2c/0x30 
[nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788263]  ? 
nouveau_fence_no_signaling+0x2a/0x90 [nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788266]  dma_fence_default_wait+0x1fc/0x260
  Oct 10 11:42:24 sun kernel: [18125.788267]  ? dma_fence_release+0xa0/0xa0
  Oct 10 11:42:24 sun kernel: [18125.788269]  dma_fence_wait_timeout+0x3e/0xf0
  Oct 10 11:42:24 sun kernel: [18125.788275]  
drm_atomic_helper_wait_for_fences+0x3f/0xc0 [drm_kms_helper]
  Oct 10 11:42:24 sun kernel: [18125.788309]  
nv50_disp_atomic_commit_tail+0x78/0x860 [nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788311]  ? __switch_to_asm+0x40/0x70
  Oct 10 11:42:24 sun kernel: [18125.788312]  ? __switch_to_asm+0x34/0x70
  Oct 10 11:42:24 sun kernel: [18125.788333]  
nv50_disp_atomic_commit_work+0x12/0x20 [nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788335]  process_one_work+0x20f/0x3c0
  Oct 10 11:42:24 sun kernel: [18125.788337]  worker_thread+0x34/0x400
  Oct 10 11:42:24 sun kernel: [18125.788339]  kthread+0x120/0x140
  Oct 10 11:42:24 sun kernel: [18125.788340]  ? 
pwq_unbound_release_workfn+0xd0/0xd0
  Oct 10 11:42:24 sun kernel: [18125.788341]  ? kthread_bind+0x40/0x40
  Oct 10 11:42:24 sun kernel: [18125.788343]  ret_from_fork+0x35/0x40
  Oct 10 11:44:25 sun kernel: [18246.620114] INFO: task kworker/u32:0:14726 
blocked for more than 120 seconds.
  Oct 10 11:44:25 sun kernel: [18246.620117]   Tainted: GW 
4.18.0-8-generic #9-Ubuntu
  Oct 10 11:44:25 sun kernel: [18246.620118] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Oct 10 11:44:25 sun kernel: [18246.620120] kworker/u32:0   D0 14726  
2 0x8000
  Oct 10 11:44:25 sun kernel: [18246.620156] Workqueue: events_unbound 
nv50_disp_atomic_commit_work [nouveau]
  Oct 10 11:44:25 sun kernel: [18246.620157] Call Trace:
  Oct 10 11:44:25 sun kernel: [18246.620163]  __schedule+0x29e/0x840
  Oct 10 11:44:25 sun kernel: [18246.620180]  ? nvkm_ioctl_ntfy_get+0x5c/0x80 
[nouveau]
  Oct 10 11:44:25 sun kernel: [18246.620181]  schedule+0x2c/0x80
  Oct 10 11:44:25 sun kernel: [18246.620183]  schedule_timeout+0x258/0x360
  Oct 10 11:44:25 sun kernel: [18246.620197]  ? nvif_object_ioctl+0x47/0x50 
[nouveau]
  Oct 10 11:44:25 sun kernel: [18246.620221]  ? nouveau_bo_rd32+0x2a/0x30 
[nouveau]
  Oct 10 11:44:25 sun kernel: [18246.620242]  ? nv84_fence_read+0x2c/0x30 
[nouveau]
  Oct 10 11:44:25 sun kernel: [18246.620263]  ? 
nouveau_fence_no_signaling+0x2a/0x90 [nouveau]
  Oct 10 11:44:25 sun kernel: [18246.620265]  dma_fence_default_wait+0x1fc/0x260
  Oct 10 11:44:25 sun kernel: [18246.620267]  ? dma_fence_release+0xa0/0xa0
  Oct 10 11:44:25 sun kernel: [18246.620268]  dma_fence_wait_timeout+0x3e/0xf0
  Oct 10 11:44:25 sun kernel: [18246.620274]  
drm_atomic_helper_wait_for_fences+0x3f/0xc0 [drm_kms_helper]
  Oct 10 11:44:25 sun kernel: [18246.620296]  
nv50_disp_atomic_commit_tail+0x78/0x860 [nouveau]
  Oct 10 11:44:25 sun kernel: [18246.620297]  ? __switch_to_asm+0x40/0x70
  Oct 10 11:44:2

[Kernel-packages] [Bug 1797031] Re: Touchscreen/stylus always reports 1% battery [patch]

[Trent Gamblin]

I've posted it to the linux-input list a few times but was ignored, so I
tried here.

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

Title:
  Touchscreen/stylus always reports 1% battery [patch]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell 5379 with a touchscreen that always reports 1% battery
  with the stylus. This pops up a low battery notification the first
  time I use the stylus after booting. The attached patch tells the
  kernel to ignore the battery on this particular device, since it
  appears to not report information correctly anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  trent  1734 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  9 22:42:47 2018
  HibernationDevice: RESUME=UUID=aef6a948-4599-4581-99a2-44b7944d2d58
  InstallationDate: Installed on 2018-05-10 (153 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:2361 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0025 Intel Corp. 
   Bus 001 Device 002: ID 0bda:5696 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5379
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 05G60G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.sys.vendor: Dell Inc.

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

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

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

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1797296

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

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

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

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

** Tags added: cosmic

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

Title:
  nouveau lockup

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Oct 10 11:38:30 sun kernel: [17891.545097] nouveau :03:00.0: fifo: 
SCHED_ERROR 0a [CTXSW_TIMEOUT]
  Oct 10 11:38:30 sun kernel: [17891.545109] nouveau :03:00.0: fifo: 
runlist 0: scheduled for recovery
  Oct 10 11:38:30 sun kernel: [17891.545118] nouveau :03:00.0: fifo: 
channel 12: killed
  Oct 10 11:38:30 sun kernel: [17891.545125] nouveau :03:00.0: fifo: engine 
0: scheduled for recovery
  Oct 10 11:38:30 sun kernel: [17891.545563] nouveau :03:00.0: 
systemd-logind[944]: channel 12 killed!
  Oct 10 11:42:24 sun kernel: [18125.788110] INFO: task kworker/u32:0:14726 
blocked for more than 120 seconds.
  Oct 10 11:42:24 sun kernel: [18125.788114]   Tainted: GW 
4.18.0-8-generic #9-Ubuntu
  Oct 10 11:42:24 sun kernel: [18125.788115] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Oct 10 11:42:24 sun kernel: [18125.788117] kworker/u32:0   D0 14726  
2 0x8000
  Oct 10 11:42:24 sun kernel: [18125.788154] Workqueue: events_unbound 
nv50_disp_atomic_commit_work [nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788155] Call Trace:
  Oct 10 11:42:24 sun kernel: [18125.788161]  __schedule+0x29e/0x840
  Oct 10 11:42:24 sun kernel: [18125.788178]  ? nvkm_ioctl_ntfy_get+0x5c/0x80 
[nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788180]  schedule+0x2c/0x80
  Oct 10 11:42:24 sun kernel: [18125.788181]  schedule_timeout+0x258/0x360
  Oct 10 11:42:24 sun kernel: [18125.788197]  ? nvif_object_ioctl+0x47/0x50 
[nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788220]  ? nouveau_bo_rd32+0x2a/0x30 
[nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788242]  ? nv84_fence_read+0x2c/0x30 
[nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788263]  ? 
nouveau_fence_no_signaling+0x2a/0x90 [nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788266]  dma_fence_default_wait+0x1fc/0x260
  Oct 10 11:42:24 sun kernel: [18125.788267]  ? dma_fence_release+0xa0/0xa0
  Oct 10 11:42:24 sun kernel: [18125.788269]  dma_fence_wait_timeout+0x3e/0xf0
  Oct 10 11:42:24 sun kernel: [18125.788275]  
drm_atomic_helper_wait_for_fences+0x3f/0xc0 [drm_kms_helper]
  Oct 10 11:42:24 sun kernel: [18125.788309]  
nv50_disp_atomic_commit_tail+0x78/0x860 [nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788311]  ? __switch_to_asm+0x40/0x70
  Oct 10 11:42:24 sun kernel: [18125.788312]  ? __switch_to_asm+0x34/0x70
  Oct 10 11:42:24 sun kernel: [18125.788333]  
nv50_disp_atomic_commit_work+0x12/0x20 [nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788335]  process_one_work+0x20f/0x3c0
  Oct 10 11:42:24 sun kernel: [18125.788337]  worker_thread+0x34/0x400
  Oct 10 11:42:24 sun kernel: [18125.788339]  kthread+0x120/0x140
  Oct 10 11:42:24 sun kernel: [18125.788340]  ? 
pwq_unbound_release_workfn+0xd0/0xd0
  Oct 10 11:42:24 sun kernel: [18125.788341]  ? kthread_bind+0x40/0x40
  Oct 10 11:42:24 sun kernel: [18125.788343]  ret_from_fork+0x35/0x40
  Oct 10 11:44:25 sun kernel: [18246.620114] INFO: task kworker/u32:0:14726 
blocked for more than 120 seconds.
  Oct 10 11:44:25 sun kernel: [18246.620117]   Tainted: GW 
4.18.0-8-generic #9-Ubuntu
  Oct 10 11:44:25 sun kernel: [18246.620118] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Oct 10 11:44:25 sun kernel: [18246.620120] kworker/u32:0   D0 14726  
2 0x8000
  Oct 10 11:44:25 sun kernel: [18246.620156] Workqueue: events_unbound 
nv50_disp_atomic_commit_work [nouveau]
  Oct 10 11:44:25 sun kernel: [18246.620157] Call Trace:
  Oct 10 11:44:25 sun kernel: [18246.620163]  __schedule+0x29e/0x840
  Oct 10 11:44:25 sun kernel: [18246.620180]  ? nvkm_ioctl_ntfy_get+0x5c/0x80 
[nouveau]
  Oct 10 11:44:25 sun kernel: [18246.620181]  schedule+0x2c/0x80
  Oct 10 11:44:25 sun kernel: [18246.620183]  schedule_timeout+0x258/0x360
  Oct 10 11:44:25 sun kernel: [18246.620197]  ? nvif_object_ioctl+0x47/0x50 
[nouveau]
  Oct 10 11:44:25 sun kernel: [18246.620221]  ? nouveau_bo_rd32+0x2a/0x30 
[nouveau]
  Oct 10 11:44:25 sun kernel: [18246.620242]  ? nv84_fence_read+0x2c/0x30 
[nouveau]
  Oct 10 11:44:25 sun kernel: [18246.620263]  ? 
nouveau_fence_

[Kernel-packages] [Bug 1797292] Re: The front MIC can't work on the Lenovo M715

[Hui Wang]

** Description changed:

- Steps:
- 1. Installed system and log in.
- 2. Plug microphone into microphone jack
- 3. Try to record voice from mic
- 4. Unplug in microphone, plug a headset into headset jack
- 5. Try to record voice from mic of headset.
+ [Impact]
+ On the machine of Lenovo M715, there are 2 audio jacks on the front panel,
+ one of them is microphone jack. When we plug a micrphone into it, the system
+ can't detect this microphone and can't record sound via this microphone too.
  
- Actual result:
- Nothing can be recorded by jacks.
+ 
+ [Fix]
+ Apply the quirk of ALC294_FIXUP_LENOVO_MIC_LOCATION, the alsa driver will
+ assign a different name to this audio jack, then pulseaudio can handle this
+ jack and everything works well.
+ 
+ 
+ [Test Case]
+ plug a microphone to this jack and record sound, system can detect the
+ microphone and can record sound.
+ 
+ [Regression Potential]
+ Very low, this pin configuration is specific to the machine of
+ M715 so far, will not affect other machines.

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

Title:
  The front MIC can't work on the Lenovo M715

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

Bug description:
  [Impact]
  On the machine of Lenovo M715, there are 2 audio jacks on the front panel,
  one of them is microphone jack. When we plug a micrphone into it, the system
  can't detect this microphone and can't record sound via this microphone too.

  
  [Fix]
  Apply the quirk of ALC294_FIXUP_LENOVO_MIC_LOCATION, the alsa driver will
  assign a different name to this audio jack, then pulseaudio can handle this
  jack and everything works well.

  
  [Test Case]
  plug a microphone to this jack and record sound, system can detect the
  microphone and can record sound.

  [Regression Potential]
  Very low, this pin configuration is specific to the machine of
  M715 so far, will not affect other machines.

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

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

[Kernel-packages] [Bug 1797296] [NEW] nouveau lockup

[Brad Figg]

Public bug reported:

Oct 10 11:38:30 sun kernel: [17891.545097] nouveau :03:00.0: fifo: 
SCHED_ERROR 0a [CTXSW_TIMEOUT]
Oct 10 11:38:30 sun kernel: [17891.545109] nouveau :03:00.0: fifo: runlist 
0: scheduled for recovery
Oct 10 11:38:30 sun kernel: [17891.545118] nouveau :03:00.0: fifo: channel 
12: killed
Oct 10 11:38:30 sun kernel: [17891.545125] nouveau :03:00.0: fifo: engine 
0: scheduled for recovery
Oct 10 11:38:30 sun kernel: [17891.545563] nouveau :03:00.0: 
systemd-logind[944]: channel 12 killed!
Oct 10 11:42:24 sun kernel: [18125.788110] INFO: task kworker/u32:0:14726 
blocked for more than 120 seconds.
Oct 10 11:42:24 sun kernel: [18125.788114]   Tainted: GW 
4.18.0-8-generic #9-Ubuntu
Oct 10 11:42:24 sun kernel: [18125.788115] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Oct 10 11:42:24 sun kernel: [18125.788117] kworker/u32:0   D0 14726  2 
0x8000
Oct 10 11:42:24 sun kernel: [18125.788154] Workqueue: events_unbound 
nv50_disp_atomic_commit_work [nouveau]
Oct 10 11:42:24 sun kernel: [18125.788155] Call Trace:
Oct 10 11:42:24 sun kernel: [18125.788161]  __schedule+0x29e/0x840
Oct 10 11:42:24 sun kernel: [18125.788178]  ? nvkm_ioctl_ntfy_get+0x5c/0x80 
[nouveau]
Oct 10 11:42:24 sun kernel: [18125.788180]  schedule+0x2c/0x80
Oct 10 11:42:24 sun kernel: [18125.788181]  schedule_timeout+0x258/0x360
Oct 10 11:42:24 sun kernel: [18125.788197]  ? nvif_object_ioctl+0x47/0x50 
[nouveau]
Oct 10 11:42:24 sun kernel: [18125.788220]  ? nouveau_bo_rd32+0x2a/0x30 
[nouveau]
Oct 10 11:42:24 sun kernel: [18125.788242]  ? nv84_fence_read+0x2c/0x30 
[nouveau]
Oct 10 11:42:24 sun kernel: [18125.788263]  ? 
nouveau_fence_no_signaling+0x2a/0x90 [nouveau]
Oct 10 11:42:24 sun kernel: [18125.788266]  dma_fence_default_wait+0x1fc/0x260
Oct 10 11:42:24 sun kernel: [18125.788267]  ? dma_fence_release+0xa0/0xa0
Oct 10 11:42:24 sun kernel: [18125.788269]  dma_fence_wait_timeout+0x3e/0xf0
Oct 10 11:42:24 sun kernel: [18125.788275]  
drm_atomic_helper_wait_for_fences+0x3f/0xc0 [drm_kms_helper]
Oct 10 11:42:24 sun kernel: [18125.788309]  
nv50_disp_atomic_commit_tail+0x78/0x860 [nouveau]
Oct 10 11:42:24 sun kernel: [18125.788311]  ? __switch_to_asm+0x40/0x70
Oct 10 11:42:24 sun kernel: [18125.788312]  ? __switch_to_asm+0x34/0x70
Oct 10 11:42:24 sun kernel: [18125.788333]  
nv50_disp_atomic_commit_work+0x12/0x20 [nouveau]
Oct 10 11:42:24 sun kernel: [18125.788335]  process_one_work+0x20f/0x3c0
Oct 10 11:42:24 sun kernel: [18125.788337]  worker_thread+0x34/0x400
Oct 10 11:42:24 sun kernel: [18125.788339]  kthread+0x120/0x140
Oct 10 11:42:24 sun kernel: [18125.788340]  ? 
pwq_unbound_release_workfn+0xd0/0xd0
Oct 10 11:42:24 sun kernel: [18125.788341]  ? kthread_bind+0x40/0x40
Oct 10 11:42:24 sun kernel: [18125.788343]  ret_from_fork+0x35/0x40
Oct 10 11:44:25 sun kernel: [18246.620114] INFO: task kworker/u32:0:14726 
blocked for more than 120 seconds.
Oct 10 11:44:25 sun kernel: [18246.620117]   Tainted: GW 
4.18.0-8-generic #9-Ubuntu
Oct 10 11:44:25 sun kernel: [18246.620118] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Oct 10 11:44:25 sun kernel: [18246.620120] kworker/u32:0   D0 14726  2 
0x8000
Oct 10 11:44:25 sun kernel: [18246.620156] Workqueue: events_unbound 
nv50_disp_atomic_commit_work [nouveau]
Oct 10 11:44:25 sun kernel: [18246.620157] Call Trace:
Oct 10 11:44:25 sun kernel: [18246.620163]  __schedule+0x29e/0x840
Oct 10 11:44:25 sun kernel: [18246.620180]  ? nvkm_ioctl_ntfy_get+0x5c/0x80 
[nouveau]
Oct 10 11:44:25 sun kernel: [18246.620181]  schedule+0x2c/0x80
Oct 10 11:44:25 sun kernel: [18246.620183]  schedule_timeout+0x258/0x360
Oct 10 11:44:25 sun kernel: [18246.620197]  ? nvif_object_ioctl+0x47/0x50 
[nouveau]
Oct 10 11:44:25 sun kernel: [18246.620221]  ? nouveau_bo_rd32+0x2a/0x30 
[nouveau]
Oct 10 11:44:25 sun kernel: [18246.620242]  ? nv84_fence_read+0x2c/0x30 
[nouveau]
Oct 10 11:44:25 sun kernel: [18246.620263]  ? 
nouveau_fence_no_signaling+0x2a/0x90 [nouveau]
Oct 10 11:44:25 sun kernel: [18246.620265]  dma_fence_default_wait+0x1fc/0x260
Oct 10 11:44:25 sun kernel: [18246.620267]  ? dma_fence_release+0xa0/0xa0
Oct 10 11:44:25 sun kernel: [18246.620268]  dma_fence_wait_timeout+0x3e/0xf0
Oct 10 11:44:25 sun kernel: [18246.620274]  
drm_atomic_helper_wait_for_fences+0x3f/0xc0 [drm_kms_helper]
Oct 10 11:44:25 sun kernel: [18246.620296]  
nv50_disp_atomic_commit_tail+0x78/0x860 [nouveau]
Oct 10 11:44:25 sun kernel: [18246.620297]  ? __switch_to_asm+0x40/0x70
Oct 10 11:44:25 sun kernel: [18246.620299]  ? __switch_to_asm+0x34/0x70
Oct 10 11:44:25 sun kernel: [18246.620320]  
nv50_disp_atomic_commit_work+0x12/0x20 [nouveau]
Oct 10 11:44:25 sun kernel: [18246.620322]  process_one_work+0x20f/0x3c0
Oct 10 11:44:25 sun kernel: [18246.620324]  worker_thread+0x34/0x400
Oct 10 11:44:25 sun kernel: [18246.620326]  kthread+0x120/0x140
Oct 10 11:44:25 sun kernel: [18246.620327]  ? 
pw

[Kernel-packages] [Bug 1797296] Re: nouveau lockup

[Brad Figg]

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797296/+attachment/5199769/+files/syslog

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

Title:
  nouveau lockup

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Oct 10 11:38:30 sun kernel: [17891.545097] nouveau :03:00.0: fifo: 
SCHED_ERROR 0a [CTXSW_TIMEOUT]
  Oct 10 11:38:30 sun kernel: [17891.545109] nouveau :03:00.0: fifo: 
runlist 0: scheduled for recovery
  Oct 10 11:38:30 sun kernel: [17891.545118] nouveau :03:00.0: fifo: 
channel 12: killed
  Oct 10 11:38:30 sun kernel: [17891.545125] nouveau :03:00.0: fifo: engine 
0: scheduled for recovery
  Oct 10 11:38:30 sun kernel: [17891.545563] nouveau :03:00.0: 
systemd-logind[944]: channel 12 killed!
  Oct 10 11:42:24 sun kernel: [18125.788110] INFO: task kworker/u32:0:14726 
blocked for more than 120 seconds.
  Oct 10 11:42:24 sun kernel: [18125.788114]   Tainted: GW 
4.18.0-8-generic #9-Ubuntu
  Oct 10 11:42:24 sun kernel: [18125.788115] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Oct 10 11:42:24 sun kernel: [18125.788117] kworker/u32:0   D0 14726  
2 0x8000
  Oct 10 11:42:24 sun kernel: [18125.788154] Workqueue: events_unbound 
nv50_disp_atomic_commit_work [nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788155] Call Trace:
  Oct 10 11:42:24 sun kernel: [18125.788161]  __schedule+0x29e/0x840
  Oct 10 11:42:24 sun kernel: [18125.788178]  ? nvkm_ioctl_ntfy_get+0x5c/0x80 
[nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788180]  schedule+0x2c/0x80
  Oct 10 11:42:24 sun kernel: [18125.788181]  schedule_timeout+0x258/0x360
  Oct 10 11:42:24 sun kernel: [18125.788197]  ? nvif_object_ioctl+0x47/0x50 
[nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788220]  ? nouveau_bo_rd32+0x2a/0x30 
[nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788242]  ? nv84_fence_read+0x2c/0x30 
[nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788263]  ? 
nouveau_fence_no_signaling+0x2a/0x90 [nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788266]  dma_fence_default_wait+0x1fc/0x260
  Oct 10 11:42:24 sun kernel: [18125.788267]  ? dma_fence_release+0xa0/0xa0
  Oct 10 11:42:24 sun kernel: [18125.788269]  dma_fence_wait_timeout+0x3e/0xf0
  Oct 10 11:42:24 sun kernel: [18125.788275]  
drm_atomic_helper_wait_for_fences+0x3f/0xc0 [drm_kms_helper]
  Oct 10 11:42:24 sun kernel: [18125.788309]  
nv50_disp_atomic_commit_tail+0x78/0x860 [nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788311]  ? __switch_to_asm+0x40/0x70
  Oct 10 11:42:24 sun kernel: [18125.788312]  ? __switch_to_asm+0x34/0x70
  Oct 10 11:42:24 sun kernel: [18125.788333]  
nv50_disp_atomic_commit_work+0x12/0x20 [nouveau]
  Oct 10 11:42:24 sun kernel: [18125.788335]  process_one_work+0x20f/0x3c0
  Oct 10 11:42:24 sun kernel: [18125.788337]  worker_thread+0x34/0x400
  Oct 10 11:42:24 sun kernel: [18125.788339]  kthread+0x120/0x140
  Oct 10 11:42:24 sun kernel: [18125.788340]  ? 
pwq_unbound_release_workfn+0xd0/0xd0
  Oct 10 11:42:24 sun kernel: [18125.788341]  ? kthread_bind+0x40/0x40
  Oct 10 11:42:24 sun kernel: [18125.788343]  ret_from_fork+0x35/0x40
  Oct 10 11:44:25 sun kernel: [18246.620114] INFO: task kworker/u32:0:14726 
blocked for more than 120 seconds.
  Oct 10 11:44:25 sun kernel: [18246.620117]   Tainted: GW 
4.18.0-8-generic #9-Ubuntu
  Oct 10 11:44:25 sun kernel: [18246.620118] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Oct 10 11:44:25 sun kernel: [18246.620120] kworker/u32:0   D0 14726  
2 0x8000
  Oct 10 11:44:25 sun kernel: [18246.620156] Workqueue: events_unbound 
nv50_disp_atomic_commit_work [nouveau]
  Oct 10 11:44:25 sun kernel: [18246.620157] Call Trace:
  Oct 10 11:44:25 sun kernel: [18246.620163]  __schedule+0x29e/0x840
  Oct 10 11:44:25 sun kernel: [18246.620180]  ? nvkm_ioctl_ntfy_get+0x5c/0x80 
[nouveau]
  Oct 10 11:44:25 sun kernel: [18246.620181]  schedule+0x2c/0x80
  Oct 10 11:44:25 sun kernel: [18246.620183]  schedule_timeout+0x258/0x360
  Oct 10 11:44:25 sun kernel: [18246.620197]  ? nvif_object_ioctl+0x47/0x50 
[nouveau]
  Oct 10 11:44:25 sun kernel: [18246.620221]  ? nouveau_bo_rd32+0x2a/0x30 
[nouveau]
  Oct 10 11:44:25 sun kernel: [18246.620242]  ? nv84_fence_read+0x2c/0x30 
[nouveau]
  Oct 10 11:44:25 sun kernel: [18246.620263]  ? 
nouveau_fence_no_signaling+0x2a/0x90 [nouveau]
  Oct 10 11:44:25 sun kernel: [18246.620265]  dma_fence_default_wait+0x1fc/0x260
  Oct 10 11:44:25 sun kernel: [18246.620267]  ? dma_fence_release+0xa0/0xa0
  Oct 10 11:44:25 sun kernel: [18246.620268]  dma_fence_wait_timeout+0x3e/0xf0
  Oct 10 11:44:25 sun kernel: [18246.620274]  
drm_atomic_helper_wait_for_fences+0x3f/0xc0 [drm_kms_helper]
  Oct 10 11:44:25 sun kernel: [18246.620296]  
nv50_disp_atomic_commit_tail+0x78/0x860 [nouveau]
  Oct 10 11:44:25 sun ker

[Kernel-packages] [Bug 1797002] Re: all my bluetooth headsets skips terribly after todays update

[Ivan]

and dpkg.log

but again, it doesn't work even with fresh installation over formatted
partition, can try it again tomorrow

** Attachment added: "dpkg.log"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+attachment/5199768/+files/dpkg.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/1797002

Title:
  all my bluetooth headsets skips terribly after todays update

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  all my bluetooth headsets skips terribly after today's system update.
  it is heavy noticeable even on audio setting test form.
  it work just fine today before i applied updates.

  even reinstall ubuntu from scratch - didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  9 18:40:44 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-10-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.66
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1968
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 93.52
  dmi.chassis.asset.tag: 5CG32907G7
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 088510305B0610100
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:17:29:62:BE:6A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:16831 acl:64 sco:0 events:1798 errors:0
TX bytes:688571 acl:2399 sco:0 commands:125 errors:0

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

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

[Kernel-packages] [Bug 1797002] Re: all my bluetooth headsets skips terribly after todays update

[Ivan]

Here they are, bu today I've tried to update with check box pre-release
updates

** Attachment added: "history.log"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+attachment/5199767/+files/history.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/1797002

Title:
  all my bluetooth headsets skips terribly after todays update

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  all my bluetooth headsets skips terribly after today's system update.
  it is heavy noticeable even on audio setting test form.
  it work just fine today before i applied updates.

  even reinstall ubuntu from scratch - didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  9 18:40:44 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-10-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.66
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1968
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 93.52
  dmi.chassis.asset.tag: 5CG32907G7
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 088510305B0610100
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:17:29:62:BE:6A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:16831 acl:64 sco:0 events:1798 errors:0
TX bytes:688571 acl:2399 sco:0 commands:125 errors:0

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

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

[Kernel-packages] [Bug 1797080] Re: linux-gcp: 4.15.0-1023.24~16.04.1 -proposed tracker

[Brad Figg]

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

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1797061
  phase: Uploaded

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

Title:
  linux-gcp: 4.15.0-1023.24~16.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1797061
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered

[Carl Reinke]

fdea70d has the bug.

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

Title:
  With kernel 4.13 btrfs scans for devices before all devices have been
  discovered

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  See attached dmesg outputs for booting kernels 4.11.x (working) and
  4.13.x (not working).

  dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
  btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have 
been discovered by the kernel.  The btrfs RAID1 filesystem mounts, and 
everything is good.

  dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
  btrfs scans for devices after only 2 (sda, sdb) of the devices have been 
discovered by the kernel.  The btrfs RAID1 filesystem fails to mount ("failed 
to read the system array: -5").  The remaining 2 devices (sdc, sdd) are 
discovered by the kernel immediately afterward.  At the end of the log, I run 
`btrfs device scan` and mount the filesystem manually.

  Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2015-10-15 (933 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: HP ProLiant MicroServer Gen8
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@ 
rootdelay=10
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  bionic apport-hook-error
  Uname: Linux 4.15.0-20-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: HP
  dmi.bios.version: J06
  dmi.chassis.type: 7
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant MicroServer Gen8
  dmi.sys.vendor: HP

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

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

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

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1797292

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

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

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

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

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

Title:
  The front MIC can't work on the Lenovo M715

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

Bug description:
  Steps:
  1. Installed system and log in.
  2. Plug microphone into microphone jack
  3. Try to record voice from mic
  4. Unplug in microphone, plug a headset into headset jack
  5. Try to record voice from mic of headset.

  Actual result:
  Nothing can be recorded by jacks.

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

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

[Kernel-packages] [Bug 1797292] Re: The front MIC can't work on the Lenovo M715

[Hui Wang]

** Tags added: originate-from-1789803 sutton

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

Title:
  The front MIC can't work on the Lenovo M715

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

Bug description:
  Steps:
  1. Installed system and log in.
  2. Plug microphone into microphone jack
  3. Try to record voice from mic
  4. Unplug in microphone, plug a headset into headset jack
  5. Try to record voice from mic of headset.

  Actual result:
  Nothing can be recorded by jacks.

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

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

[Kernel-packages] [Bug 1797292] [NEW] The front MIC can't work on the Lenovo M715

[Hui Wang]

Public bug reported:

Steps:
1. Installed system and log in.
2. Plug microphone into microphone jack
3. Try to record voice from mic
4. Unplug in microphone, plug a headset into headset jack
5. Try to record voice from mic of headset.

Actual result:
Nothing can be recorded by jacks.

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Critical
 Assignee: Hui Wang (hui.wang)
 Status: Incomplete


** Tags: originate-from-1789803 sutton

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

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

Title:
  The front MIC can't work on the Lenovo M715

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

Bug description:
  Steps:
  1. Installed system and log in.
  2. Plug microphone into microphone jack
  3. Try to record voice from mic
  4. Unplug in microphone, plug a headset into headset jack
  5. Try to record voice from mic of headset.

  Actual result:
  Nothing can be recorded by jacks.

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

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

[Kernel-packages] [Bug 1797288] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel module failed to build

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel
  module failed to build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  I tried to install  the driver for wifi, but doesn't function, I just
  can connect to network via ethernet

  My version of ubuntu is 16.04 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-36-generic
  Date: Wed Oct 10 21:38:29 2018
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.3:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c:2358:2:
 error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2018-10-10 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.3
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1797288] [NEW] bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel module failed to build

[David Andres Zea]

Public bug reported:

I tried to install  the driver for wifi, but doesn't function, I just
can connect to network via ethernet

My version of ubuntu is 16.04 LTS

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2
ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
DKMSKernelVersion: 4.15.0-36-generic
Date: Wed Oct 10 21:38:29 2018
DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.3:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c:2358:2:
 error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
InstallationDate: Installed on 2018-10-10 (0 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.3
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.27
SourcePackage: bcmwl
Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel module 
failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: bcmwl (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 bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1797288

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel
  module failed to build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  I tried to install  the driver for wifi, but doesn't function, I just
  can connect to network via ethernet

  My version of ubuntu is 16.04 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-36-generic
  Date: Wed Oct 10 21:38:29 2018
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.3:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c:2358:2:
 error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2018-10-10 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.3
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1796553] Re: BT mouse getting reset during operation

[Kai-Heng Feng]

There's a new firmware for Intel 7260:
commit 70353356f8a01b6593ea94fd6ed6e9593fd0da1f
Author: Amit K Bag 
Date:   Wed May 16 10:52:14 2018 +0530

linux-firmware: Update firmware patch for Intel Bluetooth 7260
(B3/B4)

This patch updates the firmware patch for Intel bluetooth 7260
also known as Intel WP2 B3 and WP1 B4.

Patch Version: 87

Release Version: 20.60.0.2

Clone [1] and copy intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq to
/lib/firmware/intel/.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/

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

Title:
  BT mouse getting reset during operation

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  (note: It's unclear to me if that's a kernel regression or an issue with 
bluez)

  
  I've been using this particular combination of Bluetooth mouse ("TECKNET 
BM306") & laptop ("Dell Latitude E7240") for over a year now.

  It used to work with 18.04 and 17.10, but with 18.10 I'm encountering
  a strange disconnect behaviour:

  1) Mouse is working ok
  2) Mouse suddenly stops
  3) Disabling and enabling bluetooth on the laptop makes the mouse work again.

  when this happens, dmesg reports:

  [57812.977570] usb 1-1.3: reset full-speed USB device number 18 using
  ehci-pci

  Disabling bluetooth and enabling it again results in:

  [57833.455866] usb 1-1.3: USB disconnect, device number 18
  [57833.455948] Bluetooth: hci0: turning off Intel device LED failed (-19)
  [57836.905656] usb 1-1.3: new full-speed USB device number 19 using ehci-pci
  [57837.016248] usb 1-1.3: New USB device found, idVendor=8087, 
idProduct=07dc, bcdDevice= 0.01
  [57837.016253] usb 1-1.3: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
  [57837.030092] Bluetooth: hci0: read Intel version: 370710018002030d00
  [57837.030169] Bluetooth: hci0: Intel Bluetooth firmware file: 
intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
  [57837.251206] Bluetooth: hci0: Intel firmware patch completed and activated
  [57841.724368] hid-generic 0005:0A5C:0001.001F: unknown main item tag 0x0
  [57841.724587] input: TECKNET BM306 Mouse as 
/devices/pci:00/:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/hci0:256/0005:0A5C:0001.001F/input/input78
  [57841.724873] hid-generic 0005:0A5C:0001.001F: input,hidraw0: BLUETOOTH HID 
v1.29 Mouse [TECKNET BM306] on fc:f8:ae:45:3c:05

  $ bluetoothctl --version
  bluetoothctl: 5.50

  $ hciconfig -a
  hci0: Type: Primary  Bus: USB
BD Address: FC:F8:AE:45:3C:05  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING PSCAN 
RX bytes:52465 acl:3355 sco:0 events:222 errors:0
TX bytes:28384 acl:13 sco:0 commands:170 errors:0
Features: 0xff 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
Link policy: RSWITCH HOLD SNIFF 
Link mode: SLAVE ACCEPT 
Name: 'ChromeLinux_AA14'
Class: 0x0c010c
Service Classes: Rendering, Capturing
Device Class: Computer, Laptop
HCI Version: 4.0 (0x6)  Revision: 0x500
LMP Version: 4.0 (0x6)  Subversion: 0x500
Manufacturer: Intel Corp. (2)

  $ bluetoothctl
  Agent registered
  [TECKNET BM306]# show
  Controller FC:F8:AE:45:3C:05 (public)
Name: humbaba
Alias: ChromeLinux_AA14
Class: 0x000c010c
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: Headset   (1108--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0532
Discovering: no
  [TECKNET BM306]# devices
  Device 20:9B:A5:68:AE:67 SoundBuds Flow
  Device DC:2C:26:01:24:23 TECKNET BM306
  Device 88:71:E5:0E:6B:99 Echo-HPT
  Device 00:0B:E4:A0:A2:14 Nokia BH-103
  Device A8:96:75:8B:4F:49 Moto G5S Plus
  Device 00:02:5B:20:75:3C Trust SPK-02
  Device 88:75:98:F2:5C:9E NS9+
  Device 00:E0:4C:D5:E0:F5 SoundCore mini
  [TECKNET BM306]# info DC:2C:26:01:24:23
  Device DC:2C:26:01:24:23 (public)
Name: TECKNET BM306
Alias: TECKNET BM306
Class: 0x0580
Icon: input-mouse
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Service D

[Kernel-packages] [Bug 1797031] Re: Touchscreen/stylus always reports 1% battery [patch]

[Kai-Heng Feng]

Please upstream your patch so we can backport it to Ubuntu's kernel.

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

Title:
  Touchscreen/stylus always reports 1% battery [patch]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell 5379 with a touchscreen that always reports 1% battery
  with the stylus. This pops up a low battery notification the first
  time I use the stylus after booting. The attached patch tells the
  kernel to ignore the battery on this particular device, since it
  appears to not report information correctly anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  trent  1734 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  9 22:42:47 2018
  HibernationDevice: RESUME=UUID=aef6a948-4599-4581-99a2-44b7944d2d58
  InstallationDate: Installed on 2018-05-10 (153 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:2361 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0025 Intel Corp. 
   Bus 001 Device 002: ID 0bda:5696 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5379
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 05G60G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1797198] Re: [nvidia] After login the screen goes black

[Daniel van Vugt]

It appears the main error here is:

  (EE) NVIDIA(GPU-0): Failed to acquire modesetting permission.

which may related to bug 1795637, but probably not. It sounds like a
similar problem but in this case the bug would be in gdm3 instead of
plymouth.

As a workaround you might want to try disabling KMS and let the Nvidia
driver operate natively. To do this,

  1. Edit /etc/default/grub and add "nomodeset":
 GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"

  2. sudo update-grub

  3. Reboot

That does roughly the same thing as the recovery mode workaround.


** Package changed: gnome-shell (Ubuntu) => xorg-server (Ubuntu)

** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [nvidia] After login the screen goes black

Status in gdm3 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  When I boot Cosmic, grub is working OK and login screen is presented OK, but 
after login the screen goes black.
  When I boot in Recovery Mode" and "Resume" all is working OK and Nvidia 
driver 390 is used.
  These bugs my be related
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1770238
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1748656
  https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192

  See attachment for syslog info.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 10 20:12:32 2018
  InstallationDate: Installed on 2018-10-10 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181010.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1781879] Re: Latest ASUS trackpad doesn't work in Ubuntu

[sarath]

Yes I am also facing the same issue.

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

Title:
  Latest ASUS trackpad doesn't work in Ubuntu

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It seems there might be a new hardware variant of the elan trackpad in
  the newer ASUS machines.

  The issue is the shown here with some reasonably deep investigation.
  Is this something that I can do or am I reduced to having to find out
  a mouse if I want to use Linux?

  https://www.asus.com/us/Laptops/ASUS-TUF-Gaming-FX504/specifications/

  user@TUF-GAMING-FX504GD-FX80GD:~$ xinput
   Virtual core pointer  id=2[master pointer  (3)]
 ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
 ↳ Logitech USB Receiver id=12   [slave  pointer  (2)]
 ↳ Logitech USB Receiver id=13   [slave  pointer  (2)]
   Virtual core keyboard id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
  ↳ Power Button  id=6[slave  keyboard (3)]
  ↳ Asus Wireless Radio Control   id=7[slave  keyboard (3)]
  ↳ Video Bus id=8[slave  keyboard (3)]
  ↳ Video Bus id=9[slave  keyboard (3)]
  ↳ Power Button  id=10   [slave  keyboard (3)]
  ↳ Sleep Button  id=11   [slave  keyboard (3)]
  ↳ USB2.0 HD UVC WebCam: USB2.0 HD   id=14   [slave  keyboard (3)]
  ↳ Asus WMI hotkeys  id=15   [slave  keyboard (3)]
  ↳ AT Translated Set 2 keyboard  id=16   [slave  keyboard (3)]
  ↳ Logitech USB Receiver id=17   [slave  keyboard (3)]

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

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

[Kernel-packages] [Bug 1797002] Re: all my bluetooth headsets skips terribly after todays update

[Daniel van Vugt]

Ivan:

Please attach a copy of your:
  /var/log/apt/history.log
  /var/log/dpkg.log
So that we can see what packages changed around 10 October.

--

anlag:

Please open a new bug by running:
  ubuntu-bug pulseaudio
and also attach the same files requested above to your new bug.

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

** Changed in: bluez (Ubuntu)
   Status: Invalid => 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/1797002

Title:
  all my bluetooth headsets skips terribly after todays update

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  all my bluetooth headsets skips terribly after today's system update.
  it is heavy noticeable even on audio setting test form.
  it work just fine today before i applied updates.

  even reinstall ubuntu from scratch - didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  9 18:40:44 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-10-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.66
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1968
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 93.52
  dmi.chassis.asset.tag: 5CG32907G7
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 088510305B0610100
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:17:29:62:BE:6A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:16831 acl:64 sco:0 events:1798 errors:0
TX bytes:688571 acl:2399 sco:0 commands:125 errors:0

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

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

[Kernel-packages] [Bug 1792660] Re: nvme name floated after boot with 4.15.0 kernel

[Guo Yaowen]

hi Guilherme,
Get it! Thank you very much for your support.

Guo Yaowen

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

Title:
  nvme name floated after boot with 4.15.0 kernel

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

Bug description:
  nvme device name such as /dev/nvme?n?p? would be floated that is
  symbol link to different real ssd device after reboot in 4.15.0 kernel
  for 16.04.5 HWE and 18.04 GA-kernel. This are not found on 16.04.5 GA-
  kernel ( 4.4.0)

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

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

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

[bugproxy]

--- Comment From mranw...@us.ibm.com 2018-10-10 21:28 EDT---
Thanks, looks good!  Over an hour of runtime, the failure recreates in a minute 
or so.

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

Title:
  Signal 7 error when running GPFS tracing in cluster

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  -- Problem Description --
  GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel 
driver using vmalloc) and then writing trace records from user space threads in 
parallel.  While the SIGBUS happened, the access virtual memory address is in 
the mapped range, no overflow on access.

  Worked with Benjamin Herrenschmidt on GPFS tracing kernel driver code
  and he made a suggestion as workaround on the driver code to bypass
  the problem, and it works

  the workaround code change as below:

   - rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, PAGE_SHARED);
  + rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, 
__pgprot(pgprot_val(PAGE_SHARED)|_PAGE_DIRTY);

  As Benjamin mentioned, this is a Linux kernel bug and this is just a
  workaround. He will give the details about the kernel bug and why this
  workaround works

  The root cause is that for PTEs created by a driver at mmap time (ie,
  that aren't created dynamically at fault time), it's not legit for
  ptep_set_access_flags() to make them invalid even temporarily. A
  concurrent access while they are invalid will be unable to service the
  page fault and will cause as SIGBUS.

  Thankfully such PTEs shouldn't normally be the subject of a RO->RW
  privilege escalation.

  What happens is that the GPFS driver creates the PTEs using
  remap_pfn_range(...,PAGE_SHARED).

  PAGE_SHARED has _PAGE_ACCESSED (R) but not _PAGE_DIRTY (C) set.

  Thus on the first write, we try set C and while doing so, hit the
  above workaround, which causes the problem described earlier.

  The proposed patch will ensure we only do the Nest MMU hack when
  changing _PAGE_RW and not for normal R/C updates.

  The workaround tested by the GPFS team consists of adding _PAGE_DIRTY
  to the mapping created by remap_pfn_range() to avoid the RC update
  fault completely.

  This is fixed by these:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd0dbb73e01306a1060e56f81e5fe287be936477

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f08d08f3db55452d31ba4a37c702da6245876b96

  Since DD1 support is still in (ie,
  2bf1071a8d50928a4ae366bb3108833166c2b70c is not applied) the second
  doesn't apply cleanly.  Did you want that attached?

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

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

[Kernel-packages] [Bug 1795292] Re: ELAN469D touch pad not working

[Patrick Van Oosterwijck]

@nikola is this the same laptop?  Here are the same pieces of data from
my Lenovo Ideapad 330S-15ARR:

sudo acpidump | grep -C3 ELAN
5B10: 39 5F 48 49 44 00 A0 13 93 54 43 50 44 0A 02 A4  9_HIDTCPD...
5B20: 0D 53 59 4E 41 33 32 35 35 00 A0 13 93 54 43 50  .SYNA3255TCP
5B30: 44 0A 03 A4 0D 41 4C 50 53 31 32 31 45 00 A4 0D  DALPS121E...
5B40: 45 4C 41 4E 34 36 39 44 00 08 45 49 43 30 11 21  ELAN469D..EIC0.!
5B50: 0A 1E 8E 19 00 01 00 01 02 00 00 01 06 00 80 1A  
5B60: 06 00 15 00 5C 5F 53 42 2E 49 32 43 44 00 79 00  \_SB.I2CD.y.
5B70: 08 53 49 43 30 11 21 0A 1E 8E 19 00 01 00 01 02  .SIC0.!.

dmesg | grep i2c
[1.015986] i2c /dev entries driver
[1.662298] i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, 
using dummy regulator
[2.684046] i2c_designware AMDI0010:01: controller timed out

Oddly, the ACPI data is identical, but i2c_hid identifies yours as i2c-
ALPS121E:00 and mine as i2c-ELAN469D:00 ?

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

Title:
  ELAN469D touch pad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on
  this Lenovo Ideapad 330S-15ARR laptop.  The touch pad doesn't work in
  either.

  Some possibly relevant info from dmesg:
  i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy 
regulator
  i2c_designware AMDI0010:01: controller timed out

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xorbit 2086 F pulseaudio
   /dev/snd/pcmC1D0p:   xorbit 2086 F...m pulseaudio
   /dev/snd/controlC0:  xorbit 2086 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Sep 30 23:14:26 2018
  InstallationDate: Installed on 2018-09-20 (10 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 81FB
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 
rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 
elan_i2c.dyndbg=+p
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago)
  dmi.bios.date: 06/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WCN22WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330S-15ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR:
  dmi.product.family: ideapad 330S-15ARR
  dmi.product.name: 81FB
  dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR
  dmi.product.version: Lenovo ideapad 330S-15ARR
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-20 (13 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  cosmic
  Uname: Linux 4.19.0-041900rc6-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 713556] Re: Sharkoon Fireglider mouse is wrongly detected as a joystick

[Newell Jensen]

** Merge proposal unlinked:
   https://code.launchpad.net/~newell-jensen/maas/+git/maas/+merge/343053

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

Title:
  Sharkoon Fireglider mouse is wrongly detected as a joystick

Status in udev:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-input-evdev

  I've been programming a game in SDL and I was surprised that SDL was
  reporting that 1 joystick was connected when there were none. SDL
  provides the name as "A4Tech USB Full Speed". "ls /dev/input" shows
  one joystick connected:

  by-idevent0  event2  event4  event6  event8  micemouse1
  by-path  event1  event3  event5  event7  js0 mouse0

  lsusb shows my mouse as:

  Bus 003 Device 003: ID 09da:8090 A4 Tech Co., Ltd

  Unplugging the mouse makes /dev/input/js0 disappear.
  --- 
  Architecture: amd64
  DistroRelease: Ubuntu 10.10
  InstallationMedia: elementary 0.2 Jupiter - Release i386
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Tags: maverick
  Uname: Linux 2.6.37-02063706-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Kernel-packages] [Bug 713556] Re: Sharkoon Fireglider mouse is wrongly detected as a joystick

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~newell-jensen/maas/+git/maas/+merge/343053

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

Title:
  Sharkoon Fireglider mouse is wrongly detected as a joystick

Status in udev:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-input-evdev

  I've been programming a game in SDL and I was surprised that SDL was
  reporting that 1 joystick was connected when there were none. SDL
  provides the name as "A4Tech USB Full Speed". "ls /dev/input" shows
  one joystick connected:

  by-idevent0  event2  event4  event6  event8  micemouse1
  by-path  event1  event3  event5  event7  js0 mouse0

  lsusb shows my mouse as:

  Bus 003 Device 003: ID 09da:8090 A4 Tech Co., Ltd

  Unplugging the mouse makes /dev/input/js0 disappear.
  --- 
  Architecture: amd64
  DistroRelease: Ubuntu 10.10
  InstallationMedia: elementary 0.2 Jupiter - Release i386
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Tags: maverick
  Uname: Linux 2.6.37-02063706-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Kernel-packages] [Bug 1793430] Re: Page leaking in cachefiles_read_backing_file while vmscan is active

[Kiran Kumar Modukuri]

test log attached

** Attachment added: "test log for fscache page leak."
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793430/+attachment/5199707/+files/fscache_page_leak_test.log

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

Title:
  Page leaking in cachefiles_read_backing_file while vmscan is active

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

Bug description:
  SRU Justification
  -

  [Description]
  In a heavily loaded system where the system pagecache is nearing memory 
limits and fscache is enabled, pages can be leaked by fscache while trying read 
pages from cachefiles backend. This can happen because two applications can be 
reading same page from a single mount, two threads can be trying to read the 
backing page at same time. This results in one of the thread finding that a 
page for the backing file or netfs file is already in the radix tree. During 
the error handling cachefiles does not cleanup the reference on backing page, 
leading to page leak.
  
  [Fix]
  The fix is straightforward, to decrement the reference when error is 
encounterd.
  
  [Testing]
  A user has tested the fix using following method for 12+ hrs.
  
  1) mkdir -p /mnt/nfs ; mount -o vers=3,fsc :/export /mnt/nfs
  2) create 1 files of 2.8MB in a NFS mount.
  3) start a thread to simulate heavy VM presssure
 (while true ; do echo 3 > /proc/sys/vm/drop_caches ; sleep 1 ; done)&
  4) start multiple parallel reader for data set at same time
 find /mnt/nfs -type f | xargs -P 80 cat > /dev/null &
 find /mnt/nfs -type f | xargs -P 80 cat > /dev/null &
 find /mnt/nfs -type f | xargs -P 80 cat > /dev/null &
 ..
 ..
 find /mnt/nfs -type f | xargs -P 80 cat > /dev/null &
 find /mnt/nfs -type f | xargs -P 80 cat > /dev/null &
  5) finally check using cat /proc/fs/fscache/stats | grep -i pages ;
 free -h , cat /proc/meminfo and page-types -r -b lru
 to ensure all pages are freed.

  [Regression Potential]
  Limited to cachefiles.

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

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

[Kernel-packages] [Bug 1793430] Re: Page leaking in cachefiles_read_backing_file while vmscan is active

[Kiran Kumar Modukuri]

Yes we were able to test with 4.15.0-37-generic kernel aswell.

Your sosreport has been generated and saved in:
  /tmp/sosreport-kmodukuri.00195310-20181010154537.tar.xz

The checksum is: 8c057643e9995694678915ce550e422c

Please send this file to your support representative.

** Attachment added: "sos report after testing on 4.15.0-37-generic"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793430/+attachment/5199706/+files/sosreport-kmodukuri.00195310-20181010154537.tar.xz

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

Title:
  Page leaking in cachefiles_read_backing_file while vmscan is active

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

Bug description:
  SRU Justification
  -

  [Description]
  In a heavily loaded system where the system pagecache is nearing memory 
limits and fscache is enabled, pages can be leaked by fscache while trying read 
pages from cachefiles backend. This can happen because two applications can be 
reading same page from a single mount, two threads can be trying to read the 
backing page at same time. This results in one of the thread finding that a 
page for the backing file or netfs file is already in the radix tree. During 
the error handling cachefiles does not cleanup the reference on backing page, 
leading to page leak.
  
  [Fix]
  The fix is straightforward, to decrement the reference when error is 
encounterd.
  
  [Testing]
  A user has tested the fix using following method for 12+ hrs.
  
  1) mkdir -p /mnt/nfs ; mount -o vers=3,fsc :/export /mnt/nfs
  2) create 1 files of 2.8MB in a NFS mount.
  3) start a thread to simulate heavy VM presssure
 (while true ; do echo 3 > /proc/sys/vm/drop_caches ; sleep 1 ; done)&
  4) start multiple parallel reader for data set at same time
 find /mnt/nfs -type f | xargs -P 80 cat > /dev/null &
 find /mnt/nfs -type f | xargs -P 80 cat > /dev/null &
 find /mnt/nfs -type f | xargs -P 80 cat > /dev/null &
 ..
 ..
 find /mnt/nfs -type f | xargs -P 80 cat > /dev/null &
 find /mnt/nfs -type f | xargs -P 80 cat > /dev/null &
  5) finally check using cat /proc/fs/fscache/stats | grep -i pages ;
 free -h , cat /proc/meminfo and page-types -r -b lru
 to ensure all pages are freed.

  [Regression Potential]
  Limited to cachefiles.

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

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

[Kernel-packages] [Bug 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu

[Joseph Salisbury]

I'll check into why those are missing and should have more packages
ready shortly.

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

Title:
  [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common
  deb on Ubuntu

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  ---Problem Description---
  File libperf-jvmti.so is missing in linux-tools-common deb making it 
impossible to use perf for the JVM JITed methods
   
  ---uname output---
  inux-image-4.13.0-36-generic
   
  Machine Type = not relevant 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   File libperf-jvmti.so is missing in linux-tools-common deb provided for 
Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also 
checked if the file is available on launchpad 
(https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) 
at it's also absent there:

  gromero@ltc-wspoon3:~/download$ dpkg -c 
linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm
  gromero@ltc-wspoon3:~/download$ dpkg -c 
linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm

  I do see the file in tools/perf/jvmti dir in the source .tar.gz, but
  apparently it's no being packaged in any .deb file?

  Thanks. 
   

   
  Userspace tool common name: perf 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace tool obtained from project website:  na

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

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

[Kernel-packages] [Bug 1792195] Re: Signal 7 error when running GPFS tracing in cluster

[Joseph Salisbury]

Sorry, it looks like my copy failed.  The files should be there now.

http://kernel.ubuntu.com/~jsalisbury/lp1792195

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

Title:
  Signal 7 error when running GPFS tracing in cluster

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  -- Problem Description --
  GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel 
driver using vmalloc) and then writing trace records from user space threads in 
parallel.  While the SIGBUS happened, the access virtual memory address is in 
the mapped range, no overflow on access.

  Worked with Benjamin Herrenschmidt on GPFS tracing kernel driver code
  and he made a suggestion as workaround on the driver code to bypass
  the problem, and it works

  the workaround code change as below:

   - rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, PAGE_SHARED);
  + rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, 
__pgprot(pgprot_val(PAGE_SHARED)|_PAGE_DIRTY);

  As Benjamin mentioned, this is a Linux kernel bug and this is just a
  workaround. He will give the details about the kernel bug and why this
  workaround works

  The root cause is that for PTEs created by a driver at mmap time (ie,
  that aren't created dynamically at fault time), it's not legit for
  ptep_set_access_flags() to make them invalid even temporarily. A
  concurrent access while they are invalid will be unable to service the
  page fault and will cause as SIGBUS.

  Thankfully such PTEs shouldn't normally be the subject of a RO->RW
  privilege escalation.

  What happens is that the GPFS driver creates the PTEs using
  remap_pfn_range(...,PAGE_SHARED).

  PAGE_SHARED has _PAGE_ACCESSED (R) but not _PAGE_DIRTY (C) set.

  Thus on the first write, we try set C and while doing so, hit the
  above workaround, which causes the problem described earlier.

  The proposed patch will ensure we only do the Nest MMU hack when
  changing _PAGE_RW and not for normal R/C updates.

  The workaround tested by the GPFS team consists of adding _PAGE_DIRTY
  to the mapping created by remap_pfn_range() to avoid the RC update
  fault completely.

  This is fixed by these:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd0dbb73e01306a1060e56f81e5fe287be936477

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f08d08f3db55452d31ba4a37c702da6245876b96

  Since DD1 support is still in (ie,
  2bf1071a8d50928a4ae366bb3108833166c2b70c is not applied) the second
  doesn't apply cleanly.  Did you want that attached?

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

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

[Kernel-packages] [Bug 1796553] Re: BT mouse getting reset during operation

[Ralf Hildebrandt]

Tested:

$ uname -a
Linux humbaba 4.19.0-041900rc7-generic #201810071631 SMP Sun Oct 7 16:33:10 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

and the error is still there.

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

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

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

Title:
  BT mouse getting reset during operation

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  (note: It's unclear to me if that's a kernel regression or an issue with 
bluez)

  
  I've been using this particular combination of Bluetooth mouse ("TECKNET 
BM306") & laptop ("Dell Latitude E7240") for over a year now.

  It used to work with 18.04 and 17.10, but with 18.10 I'm encountering
  a strange disconnect behaviour:

  1) Mouse is working ok
  2) Mouse suddenly stops
  3) Disabling and enabling bluetooth on the laptop makes the mouse work again.

  when this happens, dmesg reports:

  [57812.977570] usb 1-1.3: reset full-speed USB device number 18 using
  ehci-pci

  Disabling bluetooth and enabling it again results in:

  [57833.455866] usb 1-1.3: USB disconnect, device number 18
  [57833.455948] Bluetooth: hci0: turning off Intel device LED failed (-19)
  [57836.905656] usb 1-1.3: new full-speed USB device number 19 using ehci-pci
  [57837.016248] usb 1-1.3: New USB device found, idVendor=8087, 
idProduct=07dc, bcdDevice= 0.01
  [57837.016253] usb 1-1.3: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
  [57837.030092] Bluetooth: hci0: read Intel version: 370710018002030d00
  [57837.030169] Bluetooth: hci0: Intel Bluetooth firmware file: 
intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
  [57837.251206] Bluetooth: hci0: Intel firmware patch completed and activated
  [57841.724368] hid-generic 0005:0A5C:0001.001F: unknown main item tag 0x0
  [57841.724587] input: TECKNET BM306 Mouse as 
/devices/pci:00/:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/hci0:256/0005:0A5C:0001.001F/input/input78
  [57841.724873] hid-generic 0005:0A5C:0001.001F: input,hidraw0: BLUETOOTH HID 
v1.29 Mouse [TECKNET BM306] on fc:f8:ae:45:3c:05

  $ bluetoothctl --version
  bluetoothctl: 5.50

  $ hciconfig -a
  hci0: Type: Primary  Bus: USB
BD Address: FC:F8:AE:45:3C:05  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING PSCAN 
RX bytes:52465 acl:3355 sco:0 events:222 errors:0
TX bytes:28384 acl:13 sco:0 commands:170 errors:0
Features: 0xff 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
Link policy: RSWITCH HOLD SNIFF 
Link mode: SLAVE ACCEPT 
Name: 'ChromeLinux_AA14'
Class: 0x0c010c
Service Classes: Rendering, Capturing
Device Class: Computer, Laptop
HCI Version: 4.0 (0x6)  Revision: 0x500
LMP Version: 4.0 (0x6)  Subversion: 0x500
Manufacturer: Intel Corp. (2)

  $ bluetoothctl
  Agent registered
  [TECKNET BM306]# show
  Controller FC:F8:AE:45:3C:05 (public)
Name: humbaba
Alias: ChromeLinux_AA14
Class: 0x000c010c
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: Headset   (1108--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0532
Discovering: no
  [TECKNET BM306]# devices
  Device 20:9B:A5:68:AE:67 SoundBuds Flow
  Device DC:2C:26:01:24:23 TECKNET BM306
  Device 88:71:E5:0E:6B:99 Echo-HPT
  Device 00:0B:E4:A0:A2:14 Nokia BH-103
  Device A8:96:75:8B:4F:49 Moto G5S Plus
  Device 00:02:5B:20:75:3C Trust SPK-02
  Device 88:75:98:F2:5C:9E NS9+
  Device 00:E0:4C:D5:E0:F5 SoundCore mini
  [TECKNET BM306]# info DC:2C:26:01:24:23
  Device DC:2C:26:01:24:23 (public)
Name: TECKNET BM306
Alias: TECKNET BM306
Class: 0x0580
Icon: input-mouse
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb)
UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
Modalias: usb:v0A5Cp0001d0129

  
  $ rfkill list
  2

[Kernel-packages] [Bug 1796351] Re: linux-gcp: 4.18.0-1002.3 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
  phase: Uploaded
+ kernel-phase:Promoted to proposed
+ kernel-phase-changed:Wednesday, 10. October 2018 22:07 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
- phase: Uploaded
- kernel-phase:Promoted to proposed
- kernel-phase-changed:Wednesday, 10. October 2018 22:07 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-gcp: 4.18.0-1002.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1796350] Re: linux-azure: 4.18.0-1003.3 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
  phase: Uploaded
+ kernel-phase:Promoted to proposed
+ kernel-phase-changed:Wednesday, 10. October 2018 22:07 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
- phase: Uploaded
- kernel-phase:Promoted to proposed
- kernel-phase-changed:Wednesday, 10. October 2018 22:07 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-azure: 4.18.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

[bugproxy]

--- Comment From mranw...@us.ibm.com 2018-10-10 17:49 EDT---
Commit list good, the port for 2bf1071a8d50 also included 749a027 powerpc/64s: 
Fix DT CPU features Power9 DD2.1 logic as a pre-req/additional fix.

The download directory there is empty, though, so I can't get to the
test kernel.

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

Title:
  Signal 7 error when running GPFS tracing in cluster

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  -- Problem Description --
  GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel 
driver using vmalloc) and then writing trace records from user space threads in 
parallel.  While the SIGBUS happened, the access virtual memory address is in 
the mapped range, no overflow on access.

  Worked with Benjamin Herrenschmidt on GPFS tracing kernel driver code
  and he made a suggestion as workaround on the driver code to bypass
  the problem, and it works

  the workaround code change as below:

   - rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, PAGE_SHARED);
  + rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, 
__pgprot(pgprot_val(PAGE_SHARED)|_PAGE_DIRTY);

  As Benjamin mentioned, this is a Linux kernel bug and this is just a
  workaround. He will give the details about the kernel bug and why this
  workaround works

  The root cause is that for PTEs created by a driver at mmap time (ie,
  that aren't created dynamically at fault time), it's not legit for
  ptep_set_access_flags() to make them invalid even temporarily. A
  concurrent access while they are invalid will be unable to service the
  page fault and will cause as SIGBUS.

  Thankfully such PTEs shouldn't normally be the subject of a RO->RW
  privilege escalation.

  What happens is that the GPFS driver creates the PTEs using
  remap_pfn_range(...,PAGE_SHARED).

  PAGE_SHARED has _PAGE_ACCESSED (R) but not _PAGE_DIRTY (C) set.

  Thus on the first write, we try set C and while doing so, hit the
  above workaround, which causes the problem described earlier.

  The proposed patch will ensure we only do the Nest MMU hack when
  changing _PAGE_RW and not for normal R/C updates.

  The workaround tested by the GPFS team consists of adding _PAGE_DIRTY
  to the mapping created by remap_pfn_range() to avoid the RC update
  fault completely.

  This is fixed by these:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd0dbb73e01306a1060e56f81e5fe287be936477

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f08d08f3db55452d31ba4a37c702da6245876b96

  Since DD1 support is still in (ie,
  2bf1071a8d50928a4ae366bb3108833166c2b70c is not applied) the second
  doesn't apply cleanly.  Did you want that attached?

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

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

[Kernel-packages] [Bug 1743872] Re: "0BDA:A811" - Not work 802.11ac WLAN Adapter

[Evgeny]

I have the same bug with same vendor/product id.

Is it useful, about patch under os_dep/linux/usb_intf.c, struct usb_device_id 
rtw_usb_id_tbl[].
for 0bda:a811?

At the line 320:

{USB_DEVICE(0x0BDA, 0xA811),.driver_info = RTL8821}, /* OUTLINK - Edimax
*/

This line was added 3 years ago, why doesnt work from box? May be is it
wrong patch?

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

Title:
  "0BDA:A811" - Not work 802.11ac WLAN Adapter

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Not work:
  
https://www.ebay.com/itm/600Mbps-Dual-Band-2-4G-5G-Hz-Wireless-Lan-USB-PC-WiFi-Adapter-802-11AC/352152445782

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-30-generic 4.13.0-30.33
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1752 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 17:08:45 2018
  InstallationDate: Installed on 2017-10-13 (96 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-30-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-30-generic N/A
   linux-backports-modules-4.13.0-30-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1797031] Re: Touchscreen/stylus always reports 1% battery [patch]

[Trent Gamblin]

The bug still exists in 4.19rc7.

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

Title:
  Touchscreen/stylus always reports 1% battery [patch]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell 5379 with a touchscreen that always reports 1% battery
  with the stylus. This pops up a low battery notification the first
  time I use the stylus after booting. The attached patch tells the
  kernel to ignore the battery on this particular device, since it
  appears to not report information correctly anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  trent  1734 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  9 22:42:47 2018
  HibernationDevice: RESUME=UUID=aef6a948-4599-4581-99a2-44b7944d2d58
  InstallationDate: Installed on 2018-05-10 (153 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:2361 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0025 Intel Corp. 
   Bus 001 Device 002: ID 0bda:5696 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5379
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 05G60G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1797031] Re: Touchscreen/stylus always reports 1% battery [patch]

[Trent Gamblin]

Forget to answer, this bug has existed on every kernel I've tried, which
is limited to Ubuntu 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/1797031

Title:
  Touchscreen/stylus always reports 1% battery [patch]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell 5379 with a touchscreen that always reports 1% battery
  with the stylus. This pops up a low battery notification the first
  time I use the stylus after booting. The attached patch tells the
  kernel to ignore the battery on this particular device, since it
  appears to not report information correctly anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  trent  1734 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  9 22:42:47 2018
  HibernationDevice: RESUME=UUID=aef6a948-4599-4581-99a2-44b7944d2d58
  InstallationDate: Installed on 2018-05-10 (153 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:2361 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0025 Intel Corp. 
   Bus 001 Device 002: ID 0bda:5696 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5379
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 05G60G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1743872] Re: "0BDA:A811" - Not work 802.11ac WLAN Adapter

[Evgeny]

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

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

Title:
  "0BDA:A811" - Not work 802.11ac WLAN Adapter

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Not work:
  
https://www.ebay.com/itm/600Mbps-Dual-Band-2-4G-5G-Hz-Wireless-Lan-USB-PC-WiFi-Adapter-802-11AC/352152445782

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-30-generic 4.13.0-30.33
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1752 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 17:08:45 2018
  InstallationDate: Installed on 2017-10-13 (96 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-30-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-30-generic N/A
   linux-backports-modules-4.13.0-30-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

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

[bugproxy]

--- Comment From grom...@br.ibm.com 2018-10-10 17:08 EDT---
Hi Joseph,

It looks like 'perf' binary is missing in linux-tools-common in the
pointed out packages:

root@gromero16:~/perf/lp1761379# dpkg -c 
linux-tools-common_4.15.0-34.38~lp1761379_all.deb
drwxr-xr-x root/root 0 2018-08-27 10:45 ./
drwxr-xr-x root/root 0 2018-08-27 10:45 ./usr/
drwxr-xr-x root/root 0 2018-08-27 10:45 ./usr/share/
drwxr-xr-x root/root 0 2018-08-27 10:45 ./usr/share/doc/
drwxr-xr-x root/root 0 2018-08-27 10:45 
./usr/share/doc/linux-tools-common/
-rw-r--r-- root/root133835 2018-08-27 10:45 
./usr/share/doc/linux-tools-common/changelog.Debian.gz
-rw-r--r-- root/root  1292 2018-08-27 10:45 
./usr/share/doc/linux-tools-common/copyright
root@gromero16:~/perf/lp1761379#

I also could not find it and any jvmti.so in the remaining packages.

Would you mind to check that please?

Thank you.

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

Title:
  [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common
  deb on Ubuntu

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  ---Problem Description---
  File libperf-jvmti.so is missing in linux-tools-common deb making it 
impossible to use perf for the JVM JITed methods
   
  ---uname output---
  inux-image-4.13.0-36-generic
   
  Machine Type = not relevant 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   File libperf-jvmti.so is missing in linux-tools-common deb provided for 
Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also 
checked if the file is available on launchpad 
(https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) 
at it's also absent there:

  gromero@ltc-wspoon3:~/download$ dpkg -c 
linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm
  gromero@ltc-wspoon3:~/download$ dpkg -c 
linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm

  I do see the file in tools/perf/jvmti dir in the source .tar.gz, but
  apparently it's no being packaged in any .deb file?

  Thanks. 
   

   
  Userspace tool common name: perf 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace tool obtained from project website:  na

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

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

[Kernel-packages] [Bug 1797080] Re: linux-gcp: 4.15.0-1023.24~16.04.1 -proposed tracker

[Brad Figg]

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1797061
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Wednesday, 10. October 2018 21:06 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1797061
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Wednesday, 10. October 2018 21:06 UTC
+ phase: Uploaded

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

Title:
  linux-gcp: 4.15.0-1023.24~16.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1797061
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1797065] Re: linux-kvm: 4.15.0-1025.25 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1797061
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Wednesday, 10. October 2018 21:05 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1797061
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Wednesday, 10. October 2018 21:05 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-kvm: 4.15.0-1025.25 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1797061
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1797235] [NEW] Xorg crashes when using nvidia-driver-390 with secure boot disabled

[Lee Trager]

Public bug reported:

The latest nvidia update causes X.org to crash as soon as I try to login
with gdm. I can login to Wayland for a few minutes but it then crashes
as well. While going through dmesg I saw the following. It appears that
the crash is happening because I disabled UEFI secure boot. Once I
reenabled it the system become stable and I can now use X.org or
Wayland.

Oct 10 13:48:49 ltrager-laptop kernel: PKCS#7 signature not signed with a 
trusted key
Oct 10 13:48:49 ltrager-laptop kernel: nvidia-modeset: Loading NVIDIA Kernel 
Mode Setting Driver for UNIX platforms  390.77  Tue Jul 10 22:10:46 PDT 2018
Oct 10 13:48:49 ltrager-laptop kernel: PKCS#7 signature not signed with a 
trusted key
Oct 10 13:48:49 ltrager-laptop kernel: [drm] [nvidia-drm] [GPU ID 0x0100] 
Loading driver
Oct 10 13:48:49 ltrager-laptop kernel: [drm] Initialized nvidia-drm 0.0.0 
20160202 for :01:00.0 on minor 0
Oct 10 13:48:49 ltrager-laptop kernel: PKCS#7 signature not signed with a 
trusted key
Oct 10 13:48:49 ltrager-laptop kernel: nvidia-uvm: Loaded the UVM driver in 8 
mode, major device number 239
Oct 10 13:48:49 ltrager-laptop systemd-udevd[4290]: Process 
'/sbin/create-uvm-dev-node' failed with exit code 1.

** Affects: nvidia-graphics-drivers-390 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Xorg crashes when using nvidia-driver-390 with secure boot disabled

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  The latest nvidia update causes X.org to crash as soon as I try to
  login with gdm. I can login to Wayland for a few minutes but it then
  crashes as well. While going through dmesg I saw the following. It
  appears that the crash is happening because I disabled UEFI secure
  boot. Once I reenabled it the system become stable and I can now use
  X.org or Wayland.

  Oct 10 13:48:49 ltrager-laptop kernel: PKCS#7 signature not signed with a 
trusted key
  Oct 10 13:48:49 ltrager-laptop kernel: nvidia-modeset: Loading NVIDIA Kernel 
Mode Setting Driver for UNIX platforms  390.77  Tue Jul 10 22:10:46 PDT 2018
  Oct 10 13:48:49 ltrager-laptop kernel: PKCS#7 signature not signed with a 
trusted key
  Oct 10 13:48:49 ltrager-laptop kernel: [drm] [nvidia-drm] [GPU ID 0x0100] 
Loading driver
  Oct 10 13:48:49 ltrager-laptop kernel: [drm] Initialized nvidia-drm 0.0.0 
20160202 for :01:00.0 on minor 0
  Oct 10 13:48:49 ltrager-laptop kernel: PKCS#7 signature not signed with a 
trusted key
  Oct 10 13:48:49 ltrager-laptop kernel: nvidia-uvm: Loaded the UVM driver in 8 
mode, major device number 239
  Oct 10 13:48:49 ltrager-laptop systemd-udevd[4290]: Process 
'/sbin/create-uvm-dev-node' failed with exit code 1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1797235/+subscriptions

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

[Kernel-packages] [Bug 1795598] Re: linux: 3.2.0-137.183 -proposed tracker

[Brad Figg]

** Summary changed:

- linux:  -proposed tracker
+ linux: 3.2.0-137.183 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package-lbm
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-lbm
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Brad Figg 
(brad-figg)

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Brad Figg 
(brad-figg)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Brad Figg 
(brad-figg)

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

Title:
  linux: 3.2.0-137.183 -proposed tracker

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

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

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

  backports: 
  derivatives:

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

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

[Kernel-packages] [Bug 1796918] Re: [Bionic] additional support for CPPC (V3) and documentation.

[Manoj Iyer]

No regression were found booting the Bionic kernel with the patches
applied.

== Enable CPPC control in firmware ==
CAVM_CN99xx# env set cppccontrol 1

== With stock bionic ==
ubuntu@starbuck:~$ uname -a 
Linux starbuck 4.15.0-36-generic #39-Ubuntu SMP Wed Sep 26 06:05:44 UTC 2018 
aarch64 aarch64 aarch64 GNU/Linux

ubuntu@starbuck:~$ ls -lR  /sys/devices/system/cpu/cpu1/acpi_cppc/
/sys/devices/system/cpu/cpu1/acpi_cppc/:
total 0
-r--r--r-- 1 root root 4096 Oct 10 20:02 feedback_ctrs
-r--r--r-- 1 root root 4096 Oct 10 20:02 highest_perf
-r--r--r-- 1 root root 4096 Oct 10 20:02 lowest_nonlinear_perf
-r--r--r-- 1 root root 4096 Oct 10 20:02 lowest_perf
-r--r--r-- 1 root root 4096 Oct 10 20:02 nominal_perf
-r--r--r-- 1 root root 4096 Oct 10 20:02 reference_perf
-r--r--r-- 1 root root 4096 Oct 10 20:02 wraparound_time
ubuntu@starbuck:~$ 

== Bionic kernel with patches. ==

ubuntu@starbuck:~$ uname -a 
Linux starbuck 4.15.0-37-generic #40~lp1796918+build.1 SMP Tue Oct 9 15:52:06 
UTC 2018 aarch64 aarch64 aarch64 GNU/Linux
ubuntu@starbuck:~$

ubuntu@starbuck:~$ ls -lR  /sys/devices/system/cpu/cpu1/acpi_cppc/
/sys/devices/system/cpu/cpu1/acpi_cppc/:
total 0
-r--r--r-- 1 root root 4096 Oct 10 20:14 feedback_ctrs
-r--r--r-- 1 root root 4096 Oct 10 20:14 highest_perf
-r--r--r-- 1 root root 4096 Oct 10 20:14 lowest_freq
-r--r--r-- 1 root root 4096 Oct 10 20:14 lowest_nonlinear_perf
-r--r--r-- 1 root root 4096 Oct 10 20:14 lowest_perf
-r--r--r-- 1 root root 4096 Oct 10 20:14 nominal_freq
-r--r--r-- 1 root root 4096 Oct 10 20:14 nominal_perf
-r--r--r-- 1 root root 4096 Oct 10 20:14 reference_perf
-r--r--r-- 1 root root 4096 Oct 10 20:14 wraparound_time
ubuntu@starbuck:~$ 

ubuntu@starbuck:~$ cat /sys/devices/system/cpu/cpu1/acpi_cppc/highest_perf 
250
ubuntu@starbuck:~$

ubuntu@starbuck:~$ cat /sys/devices/system/cpu/cpu1/acpi_cppc/lowest_perf 
100
ubuntu@starbuck:~$

ubuntu@starbuck:~$ cat /sys/devices/system/cpu/cpu1/acpi_cppc/feedback_ctrs
ref:1306246528 del:4074430338
ubuntu@starbuck:~$

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

Title:
  [Bionic] additional support for CPPC (V3) and documentation.

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

Bug description:
  [IMPACT]
  Add support for CPPC V3

  [FIX]
   33477d84c26b cpufreq / CPPC: Add cpuinfo_cur_freq support for CPPC
   b382bf885269 ACPI / CPPC: Document CPPC sysfs interface
   256f19d212f2 cpufreq / CPPC: Support for CPPC v3
   4773e77cdc9b ACPI / CPPC: Add support for CPPC v3
   
  [Test]

  [Regression Potential]

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

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

[Kernel-packages] [Bug 1796949] Re: [Bionic] CPPC bug fixes

[Manoj Iyer]

No regression were found booting the Bionic kernel with the patches
applied.

== Enable CPPC control in firmware ==
CAVM_CN99xx# env set cppccontrol 1

== With stock bionic ==
ubuntu@starbuck:~$ uname -a
Linux starbuck 4.15.0-36-generic #39-Ubuntu SMP Wed Sep 26 06:05:44 UTC 2018 
aarch64 aarch64 aarch64 GNU/Linux

ubuntu@starbuck:~$ ls -lR /sys/devices/system/cpu/cpu1/acpi_cppc/
/sys/devices/system/cpu/cpu1/acpi_cppc/:
total 0
-r--r--r-- 1 root root 4096 Oct 10 20:02 feedback_ctrs
-r--r--r-- 1 root root 4096 Oct 10 20:02 highest_perf
-r--r--r-- 1 root root 4096 Oct 10 20:02 lowest_nonlinear_perf
-r--r--r-- 1 root root 4096 Oct 10 20:02 lowest_perf
-r--r--r-- 1 root root 4096 Oct 10 20:02 nominal_perf
-r--r--r-- 1 root root 4096 Oct 10 20:02 reference_perf
-r--r--r-- 1 root root 4096 Oct 10 20:02 wraparound_time
ubuntu@starbuck:~$

== Bionic kernel with patches. ==

ubuntu@starbuck:~$ uname -a
Linux starbuck 4.15.0-37-generic #40~lp1796918+build.1 SMP Tue Oct 9 15:52:06 
UTC 2018 aarch64 aarch64 aarch64 GNU/Linux
ubuntu@starbuck:~$

ubuntu@starbuck:~$ ls -lR /sys/devices/system/cpu/cpu1/acpi_cppc/
/sys/devices/system/cpu/cpu1/acpi_cppc/:
total 0
-r--r--r-- 1 root root 4096 Oct 10 20:14 feedback_ctrs
-r--r--r-- 1 root root 4096 Oct 10 20:14 highest_perf
-r--r--r-- 1 root root 4096 Oct 10 20:14 lowest_freq
-r--r--r-- 1 root root 4096 Oct 10 20:14 lowest_nonlinear_perf
-r--r--r-- 1 root root 4096 Oct 10 20:14 lowest_perf
-r--r--r-- 1 root root 4096 Oct 10 20:14 nominal_freq
-r--r--r-- 1 root root 4096 Oct 10 20:14 nominal_perf
-r--r--r-- 1 root root 4096 Oct 10 20:14 reference_perf
-r--r--r-- 1 root root 4096 Oct 10 20:14 wraparound_time
ubuntu@starbuck:~$

ubuntu@starbuck:~$ cat /sys/devices/system/cpu/cpu1/acpi_cppc/highest_perf
250
ubuntu@starbuck:~$

ubuntu@starbuck:~$ cat /sys/devices/system/cpu/cpu1/acpi_cppc/lowest_perf
100
ubuntu@starbuck:~$

ubuntu@starbuck:~$ cat /sys/devices/system/cpu/cpu1/acpi_cppc/feedback_ctrs
ref:1306246528 del:4074430338
ubuntu@starbuck:~$

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

Title:
  [Bionic] CPPC bug fixes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  A number of CPPC related fixes from upstream needed for Cavium ThunderX2 
systems.

  [Fix]

  58e1c03536c9 ACPI / CPPC: Fix invalid PCC channel status errors
  6fa12d584dcb ACPI / CPPC: Check for valid PCC subspace only if PCC is used
  b8b10bc2015c cpufreq: CPPC: Don't set transition_latency
  d29abc836843 ACPI / CPPC: Update all pr_(debug/err) messages to log the 
susbspace id

  [Test]

  [Regression Potential]

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

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

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

[bugproxy]

--- Comment From mranw...@us.ibm.com 2018-10-10 16:00 EDT---
Thanks!  I'm building that too, to see if that was the issue.  But that patch 
applies with some (-2, -25) fuzz for me - I tried on master-next, too, and see 
the same.  I'm at fd01374000c8 (-36.39) and I just have the patches from this 
bug and from LP 1792102

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

Title:
  Signal 7 error when running GPFS tracing in cluster

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  -- Problem Description --
  GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel 
driver using vmalloc) and then writing trace records from user space threads in 
parallel.  While the SIGBUS happened, the access virtual memory address is in 
the mapped range, no overflow on access.

  Worked with Benjamin Herrenschmidt on GPFS tracing kernel driver code
  and he made a suggestion as workaround on the driver code to bypass
  the problem, and it works

  the workaround code change as below:

   - rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, PAGE_SHARED);
  + rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, 
__pgprot(pgprot_val(PAGE_SHARED)|_PAGE_DIRTY);

  As Benjamin mentioned, this is a Linux kernel bug and this is just a
  workaround. He will give the details about the kernel bug and why this
  workaround works

  The root cause is that for PTEs created by a driver at mmap time (ie,
  that aren't created dynamically at fault time), it's not legit for
  ptep_set_access_flags() to make them invalid even temporarily. A
  concurrent access while they are invalid will be unable to service the
  page fault and will cause as SIGBUS.

  Thankfully such PTEs shouldn't normally be the subject of a RO->RW
  privilege escalation.

  What happens is that the GPFS driver creates the PTEs using
  remap_pfn_range(...,PAGE_SHARED).

  PAGE_SHARED has _PAGE_ACCESSED (R) but not _PAGE_DIRTY (C) set.

  Thus on the first write, we try set C and while doing so, hit the
  above workaround, which causes the problem described earlier.

  The proposed patch will ensure we only do the Nest MMU hack when
  changing _PAGE_RW and not for normal R/C updates.

  The workaround tested by the GPFS team consists of adding _PAGE_DIRTY
  to the mapping created by remap_pfn_range() to avoid the RC update
  fault completely.

  This is fixed by these:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd0dbb73e01306a1060e56f81e5fe287be936477

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f08d08f3db55452d31ba4a37c702da6245876b96

  Since DD1 support is still in (ie,
  2bf1071a8d50928a4ae366bb3108833166c2b70c is not applied) the second
  doesn't apply cleanly.  Did you want that attached?

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

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

[Kernel-packages] [Bug 1796353] Re: linux-kvm: 4.18.0-1003.3 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
  phase: Uploaded
+ kernel-phase:Promoted to proposed
+ kernel-phase-changed:Wednesday, 10. October 2018 20:07 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
- phase: Uploaded
- kernel-phase:Promoted to proposed
- kernel-phase-changed:Wednesday, 10. October 2018 20:07 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-kvm: 4.18.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1792195] Re: Signal 7 error when running GPFS tracing in cluster

[Joseph Salisbury]

I built a v2 test kernel.  This test kernel now has the following four
commits:

f08d08f3db55 ("powerpc/mm/radix: Only need the Nest MMU workaround for R -> RW 
transition")
bd0dbb73e013 ("powerpc/mm/books3s: Add new pte bit to mark pte temporarily 
invalid.")
2bf1071a8d50 ("powerpc/64s: Remove POWER9 DD1 support")
7acf50e4efa6 ("Revert "powerpc/powernv: Increase memory block size to 1GB on 
radix"")

Commit 7acf50e4efa6 was requested in bug 1792102, but I added it to this
test kernel as well.


The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1792195

Can you test this kernel and see if it resolves this bug?

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

Title:
  Signal 7 error when running GPFS tracing in cluster

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  -- Problem Description --
  GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel 
driver using vmalloc) and then writing trace records from user space threads in 
parallel.  While the SIGBUS happened, the access virtual memory address is in 
the mapped range, no overflow on access.

  Worked with Benjamin Herrenschmidt on GPFS tracing kernel driver code
  and he made a suggestion as workaround on the driver code to bypass
  the problem, and it works

  the workaround code change as below:

   - rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, PAGE_SHARED);
  + rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, 
__pgprot(pgprot_val(PAGE_SHARED)|_PAGE_DIRTY);

  As Benjamin mentioned, this is a Linux kernel bug and this is just a
  workaround. He will give the details about the kernel bug and why this
  workaround works

  The root cause is that for PTEs created by a driver at mmap time (ie,
  that aren't created dynamically at fault time), it's not legit for
  ptep_set_access_flags() to make them invalid even temporarily. A
  concurrent access while they are invalid will be unable to service the
  page fault and will cause as SIGBUS.

  Thankfully such PTEs shouldn't normally be the subject of a RO->RW
  privilege escalation.

  What happens is that the GPFS driver creates the PTEs using
  remap_pfn_range(...,PAGE_SHARED).

  PAGE_SHARED has _PAGE_ACCESSED (R) but not _PAGE_DIRTY (C) set.

  Thus on the first write, we try set C and while doing so, hit the
  above workaround, which causes the problem described earlier.

  The proposed patch will ensure we only do the Nest MMU hack when
  changing _PAGE_RW and not for normal R/C updates.

  The workaround tested by the GPFS team consists of adding _PAGE_DIRTY
  to the mapping created by remap_pfn_range() to avoid the RC update
  fault completely.

  This is fixed by these:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd0dbb73e01306a1060e56f81e5fe287be936477

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f08d08f3db55452d31ba4a37c702da6245876b96

  Since DD1 support is still in (ie,
  2bf1071a8d50928a4ae366bb3108833166c2b70c is not applied) the second
  doesn't apply cleanly.  Did you want that attached?

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

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

[Kernel-packages] [Bug 1796944] Re: linux-aws: 4.18.0-1002.3 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.18.0-1002.3 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
  phase: Uploaded
+ kernel-phase:Promoted to proposed
+ kernel-phase-changed:Wednesday, 10. October 2018 20:03 UTC

** Description changed:

  This bug is for tracking the 4.18.0-1002.3 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
- phase: Uploaded
- kernel-phase:Promoted to proposed
- kernel-phase-changed:Wednesday, 10. October 2018 20:03 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-aws: 4.18.0-1002.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-aws source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1797066] Re: linux-aws: 4.15.0-1025.25 -proposed tracker

[Brad Figg]

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1797061
  phase: Uploaded

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

Title:
  linux-aws: 4.15.0-1025.25 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1797061
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1797062] Re: linux-gcp: 4.15.0-1023.24 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

Title:
  linux-gcp: 4.15.0-1023.24 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1797061
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1796351] Re: linux-gcp: 4.18.0-1002.3 -proposed tracker

[Brad Figg]

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

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

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

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

** Tags added: block-proposed-cosmic

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
  phase: Packaging
+ kernel-phase-changed:Wednesday, 10. October 2018 19:37 UTC
+ kernel-phase:Uploaded

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
- phase: Packaging
- kernel-phase-changed:Wednesday, 10. October 2018 19:37 UTC
- kernel-phase:Uploaded
+ phase: Uploaded

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

Title:
  linux-gcp: 4.18.0-1002.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1797065] Re: linux-kvm: 4.15.0-1025.25 -proposed tracker

[Łukasz Zemczak]

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux-kvm: 4.15.0-1025.25 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1797061
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1782934] Re: XPS 13 9350 black screen with kernel versions > 4.15.0-20-generic

[Oliver Rew]

I did not see it mentioned above, so I figured it was worth noting.

This black screen problem is also experienced by many Dell XPS 13 windows users.
https://www.dell.com/community/XPS/XPS-13-9350-Black-Screen/td-p/5912336

No one has yet found a real fix, but there is some speculative talk
about it relating to microcode on the Intel HD 520 Embedded Graphics. It
is pretty much agreed in that community that this first started taking
place after the 2-13-2018 release of the Intel HD 520 Graphics
Driver(15.65.4.4944). It did on my own Dell XPS 13 (9350).

https://downloadcenter.intel.com/product/88355/Intel-HD-Graphics-520

The only widely accepted fix was reverting back to the default Windows
Graphics Driver. I personally reinstalled Windows multiple times and
tried to install every past HD 520 driver to no avail. After that, I
switched to Ubuntu and it worked for a while until this bug.

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

Title:
  XPS 13 9350 black screen with kernel versions > 4.15.0-20-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With any Ubuntu variant I've tried (Ubuntu, Ubuntu Mate, Ubuntu
  Budgie), the graphical installer works correctly, but on every post-
  install login, the screen goes black at the disk decryption screen.

  The kernel version post-install is 4.14.0-29-generic (edited to add:
  this SHOULD have read '4.15.0-29-generic').

  Other things seem to be working. If I'm careful, I can enter the disk
  decryption password and tell (via sounds) that I've gotten through to
  the login screen, but the screen remains dark.

  This happens with standard or minimal installs.

  If I then try to boot with the previous kernel--4.15.0-20-generic--
  everything works flawlessly.

  The only non-standard thing about this system is that I replaced the
  onboard wireless card with an Intel Dual Band Wireless-AC 8625.

  ---

  I don't have a clue about kernel debugging, but I can provide further
  system info as needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Sat Jul 21 20:35:45 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Iris Graphics 540 [8086:1926] (rev 0a) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Iris Graphics 540 [1028:0704]
  InstallationDate: Installed on 2018-07-21 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia
   Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp.
   Bus 001 Device 002: ID 8087:0a2b Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 09JHRY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd01/16/2018:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: NULL
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1797061] Re: linux: 4.15.0-38.41 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

Title:
  linux: 4.15.0-38.41 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

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

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

  backports: bug 1797074 (linux-azure), bug 1797076 (linux-hwe), bug 1797078 
(linux-azure-edge), bug 1797080 (linux-gcp), bug 1797081 (linux-hwe-edge), bug 
1797082 (linux-azure)
  derivatives: bug 1797062 (linux-gcp), bug 1797065 (linux-kvm), bug 1797066 
(linux-aws), bug 1797067 (linux-azure), bug 1797069 (linux-oem), bug 1797073 
(linux-raspi2)
  kernel-stable-phase-changed:Wednesday, 10. October 2018 11:02 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1792195] Re: Signal 7 error when running GPFS tracing in cluster

[Joseph Salisbury]

You are correct, commit bd0dbb73e01306a1060e56f81e5fe287be936477 was not
in that test kernel.  It looks like it needs some backporing as well.
I'll do that and build a v2 test kernel.

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

Title:
  Signal 7 error when running GPFS tracing in cluster

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  -- Problem Description --
  GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel 
driver using vmalloc) and then writing trace records from user space threads in 
parallel.  While the SIGBUS happened, the access virtual memory address is in 
the mapped range, no overflow on access.

  Worked with Benjamin Herrenschmidt on GPFS tracing kernel driver code
  and he made a suggestion as workaround on the driver code to bypass
  the problem, and it works

  the workaround code change as below:

   - rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, PAGE_SHARED);
  + rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, 
__pgprot(pgprot_val(PAGE_SHARED)|_PAGE_DIRTY);

  As Benjamin mentioned, this is a Linux kernel bug and this is just a
  workaround. He will give the details about the kernel bug and why this
  workaround works

  The root cause is that for PTEs created by a driver at mmap time (ie,
  that aren't created dynamically at fault time), it's not legit for
  ptep_set_access_flags() to make them invalid even temporarily. A
  concurrent access while they are invalid will be unable to service the
  page fault and will cause as SIGBUS.

  Thankfully such PTEs shouldn't normally be the subject of a RO->RW
  privilege escalation.

  What happens is that the GPFS driver creates the PTEs using
  remap_pfn_range(...,PAGE_SHARED).

  PAGE_SHARED has _PAGE_ACCESSED (R) but not _PAGE_DIRTY (C) set.

  Thus on the first write, we try set C and while doing so, hit the
  above workaround, which causes the problem described earlier.

  The proposed patch will ensure we only do the Nest MMU hack when
  changing _PAGE_RW and not for normal R/C updates.

  The workaround tested by the GPFS team consists of adding _PAGE_DIRTY
  to the mapping created by remap_pfn_range() to avoid the RC update
  fault completely.

  This is fixed by these:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd0dbb73e01306a1060e56f81e5fe287be936477

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f08d08f3db55452d31ba4a37c702da6245876b96

  Since DD1 support is still in (ie,
  2bf1071a8d50928a4ae366bb3108833166c2b70c is not applied) the second
  doesn't apply cleanly.  Did you want that attached?

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

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

[Kernel-packages] [Bug 1797062] Re: linux-gcp: 4.15.0-1023.24 -proposed tracker

[Łukasz Zemczak]

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux-gcp: 4.15.0-1023.24 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1797061
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1783957] Re: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence

[Anquietas]

Well ? What should I understand from what you just did ?

You are no longer committed to fix this bug ?

OK, I'll report this bug 10 times over, until someone helps me.

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

Title:
  Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no
  login screen in a normal sequence

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged

Bug description:
  I have a MacBook Air laptop which is running Linux (Kubuntu 16.04.5
  LTS) with NVidia Graphics Card, KDE, Xorg, SDDM, and so on... Clean
  and natural install, no funky custom kernel or drivers or anything...

  Everything worked fine (with the 4.13.* kernel) until I've upgraded
  all my packages (which included the "wonderful" 4.15.0-29 kernel,
  which broke my system).

  Now, everytime I try to boot normally, it asks me for my disk password (I 
have an encrypted LVM) and after that, guess what ?: blank screen. The login 
screen does not appear.
  I can switch the Terminals with Ctrl+Alt+Fx, however.

  However, the same kernel, if I boot it in recovery mode and then I
  select "Resume", the login screen appears, but it lags a little bit...

  Needless to say, if I boot the older kernel (4.13), everything works
  perfectly.

  I dug up some logs and found something like "sddm-greeter"
  segmentation fault in nouveau_dri.so or something like this.

  So, it looks like the new kernel doesn't quite seem to look eye-to-eye
  with nouveau drivers...

  And no, I don't want the NVidia proprietary drivers because I get
  along just perfectly with Nouveau on other machines, and I don't want
  to reinstall nvidia drivers everytime I'm upgrading the kernel.

  And yes, I already have "haveged" installed, to provide sufficient
  entropy (I saw that the possible lack of entropy might be a problem in
  some cases)...

  If I boot in recovery mode and then select "resume", everything works.

  So, what is going on ?

  Any help would be appreciated...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Jul 27 10:40:31 2018
  InstallationDate: Installed on 2018-07-04 (22 days ago)
  InstallationMedia: Kubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1797190] Re: It can not be formatted with 'gnome-disk-utility 3.30.1' the pendrive

[Cristian Aravena Romero]

** Also affects: nautilus (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/1797190

Title:
  It can not be formatted with 'gnome-disk-utility 3.30.1'  the pendrive

Status in Linux:
  Unknown
Status in gnome-disk-utility package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  New

Bug description:
  List: linux-usb
  https://marc.info/?l=linux-usb&m=153919676204905&w=2

  ---

  https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues/104

  ---

  Hello,

  I am trying to format a pendrive of 2TB(Purchased in China for ebay).
  What I do is the following:

  1) I start the notebook with Linux 4.18.0-9
  2) I start with my GNOME session
  3) I connect the pendrive
  4) I open Nautilus
  5) The pendrive in nautilus appears as mounted
  6) In nautilus I hit a right click with the mouse to my pedrive
  7) I choose 'Format'
  8) A window opens where I can only choose between: ext4, NTFS or FAT
  9) I leave the default -> 'NTFS'
  10) Next press
  11) I change to the next window where the information of what is going to 
happen appears and I confirm the format
  12) Then I return to nautilius
  13) The pendrive appears in nautilus
  14) It can not be accessed, even though the pendrive is mounted

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-9-generic 4.18.0-9.10
  ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12
  Uname: Linux 4.18.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2162 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 10 14:30:28 2018
  InstallationDate: Installed on 2017-10-13 (362 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-9-generic N/A
   linux-backports-modules-4.18.0-9-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.sku: System SKUNumber
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1796353] Re: linux-kvm: 4.18.0-1003.3 -proposed tracker

[Brad Figg]

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

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

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

** Tags added: block-proposed-cosmic

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
+ kernel-phase:Uploaded
+ kernel-phase-changed:Wednesday, 10. October 2018 19:07 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
- kernel-phase:Uploaded
- kernel-phase-changed:Wednesday, 10. October 2018 19:07 UTC
+ phase: Uploaded

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

Title:
  linux-kvm: 4.18.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1796350] Re: linux-azure: 4.18.0-1003.3 -proposed tracker

[Brad Figg]

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

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

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

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

** Tags added: block-proposed-cosmic

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
  phase: Packaging
+ kernel-phase:Uploaded
+ kernel-phase-changed:Wednesday, 10. October 2018 19:08 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
- phase: Packaging
- kernel-phase:Uploaded
- kernel-phase-changed:Wednesday, 10. October 2018 19:08 UTC
+ phase: Uploaded

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

Title:
  linux-azure: 4.18.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1797061] Re: linux: 4.15.0-38.41 -proposed tracker

[Łukasz Zemczak]

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux: 4.15.0-38.41 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

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

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

  backports: bug 1797074 (linux-azure), bug 1797076 (linux-hwe), bug 1797078 
(linux-azure-edge), bug 1797080 (linux-gcp), bug 1797081 (linux-hwe-edge), bug 
1797082 (linux-azure)
  derivatives: bug 1797062 (linux-gcp), bug 1797065 (linux-kvm), bug 1797066 
(linux-aws), bug 1797067 (linux-azure), bug 1797069 (linux-oem), bug 1797073 
(linux-raspi2)
  kernel-stable-phase-changed:Wednesday, 10. October 2018 11:02 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1797065] Re: linux-kvm: 4.15.0-1025.25 -proposed tracker

[Brad Figg]

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

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

Title:
  linux-kvm: 4.15.0-1025.25 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1797061
  phase: Uploaded

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

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

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

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1797200

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

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

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

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

** Tags added: 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/1797200

Title:
  [Bionic] ACPI / PPTT: use ACPI ID whenever
  ACPI_PPTT_ACPI_PROCESSOR_ID_VALID is set

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Currently, we use the ACPI processor ID only for the leaf/processor nodes as 
the specification states it must match the value of the ACPI processor ID field 
in the processor’s entry in the MADT.

  However, if a PPTT structure represents a processors group, it matches a 
processor container UID in the namespace and the 
ACPI_PPTT_ACPI_PROCESSOR_ID_VALID flag indicates whether the ACPI processor ID 
is valid.
  
  Let's use UID whenever ACPI_PPTT_ACPI_PROCESSOR_ID_VALID is set to be 
consistent instead of using table offset as it's currently done for non-leaf 
nodes.
  
  Fixes: 2bd00bcd73e5 (ACPI/PPTT: Add Processor Properties Topology Table 
parsing)

  
  [Fix]
  This patch in is 4.18:
  30998033f62a ACPI / PPTT: use ACPI ID whenever 
ACPI_PPTT_ACPI_PROCESSOR_ID_VALID is set

  [Test]

  
  [Regression Potential]

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

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

[Kernel-packages] [Bug 1796944] Re: linux-aws: 4.18.0-1002.3 -proposed tracker

[Brad Figg]

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

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

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

** Tags added: block-proposed-cosmic

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the 4.18.0-1002.3 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
  phase: Packaging
+ kernel-phase:Uploaded
+ kernel-phase-changed:Wednesday, 10. October 2018 19:03 UTC

** Description changed:

  This bug is for tracking the 4.18.0-1002.3 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
- phase: Packaging
- kernel-phase:Uploaded
- kernel-phase-changed:Wednesday, 10. October 2018 19:03 UTC
+ phase: Uploaded

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

Title:
  linux-aws: 4.18.0-1002.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-aws source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
  phase: Uploaded

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

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

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

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1797202

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

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

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

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

** Tags added: 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/1797202

Title:
  [Bionic] arm64: topology: Avoid checking numa mask for scheduler MC
  selection

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  The numa mask subset check can often lead to system hang or crash during CPU 
hotplug and system suspend operation if NUMA is disabled. This is mostly 
observed on HMP systems where the CPU compute capacities are different and ends 
up in different scheduler domains. Since cpumask_of_node is returned instead 
core_sibling, the scheduler is confused with incorrect cpumasks(e.g. one CPU in 
two different sched domains at the same time) on CPU hotplug.

  [Fix]
  The following patch fixes this issue:
  e156ab71a974 arm64: topology: Avoid checking numa mask for scheduler MC 
selection

  [Test]

  [Regression Potential]

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

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

[Kernel-packages] [Bug 1746088] Re: [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel

[Andrew Cloke]

** Changed in: ubuntu-power-systems
   Status: Fix Released => Triaged

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

Title:
  [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
  4.13.0-26-generic kernel

Status in The Ubuntu-power-systems project:
  Triaged
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Fix Released
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  Triaged

Bug description:
  [Impact]
  It won't be possible to analyze dumps produced by newer kernels (hwe on 
xenial, for example).

  [Test Case]
  Tested that this version of crash can analyze both GA (4.4) and hwe (4.15) 
kernels.

  [Regression Potential]
  New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing may be desirable.


  ---Problem Description---
  Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel 
(Ubuntu 16.04.4)

  ---uname output---
  Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8001-22C

  ---Steps to Reproduce---
   This bug follow up bug of 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=163565
  The steps to create dump is as follows

  Once you generate the kdump
  use crash to analyze the vmcore and we get this error

  console logs ==

  root@ltc-briggs1:/var/crash/201801150227# ls
  dmesg.201801150227  vmcore.201801150227
  .0-26-generic vmcore.2018011502271150227# crash 
/usr/lib/debug/boot/vmlinux-4.13.

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  WARNING: cannot access vmalloc'd module memory

  crash: invalid structure member offset: thread_info_task
     FILE: task.c  LINE: 598  FUNCTION: irqstacks_init()

  [/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 =>
  100833e0

    100833e0: (undetermined)
    1017d220: OFFSET_verify+80
    1011552c: task_init+5084
    1008ade0: main_loop+336

  == Comment from Hari Krishna Bathini ==

  There are quite a few commits (all available upstream) that are needed for
  crash tool to work fine. I think the right thing to do here would be to use
  the latest crash tool version 7.2.0 to go with the kernel update. Also, the
  below commit would be needed on top of 7.2.0 crash utility:

    commit c8178eca9c74f81a7f803a58d339635cc152e8d9
    Author: Dave Anderson 
    Date:   Thu Nov 9 11:39:05 2017 -0500

  Update for support of Linux 4.14 and later PPC64 kernels where the
  hash page table geometry accomodates a larger virtual address range.
  Without the patch, the virtual-to-physical translation of user space
  virtual addresses by "vm -p", "vtop", and "rd -u" may generate an
  invalid translation or otherwise fail.
  (hbath...@linux.vnet.ibm.com)

  Similar thing holds true for makedumpfile tool..

  Thanks
  Hari

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

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

[Kernel-packages] [Bug 1797190] Re: It can not be formatted with 'gnome-disk-utility' the pendrive

[Cristian Aravena Romero]

** Description changed:

+ List: linux-usb
+ https://marc.info/?l=linux-usb&m=153919676204905&w=2
+ 
+ ---
+ 
  https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues/104
  
  ---
  
  Hello,
  
  I am trying to format a pendrive of 2TB(Purchased in China for ebay).
  What I do is the following:
  
  1) I start the notebook with Linux 4.18.0-9
  2) I start with my GNOME session
  3) I connect the pendrive
  4) I open Nautilus
  5) The pendrive in nautilus appears as mounted
  6) In nautilus I hit a right click with the mouse to my pedrive
  7) I choose 'Format'
  8) A window opens where I can only choose between: ext4, NTFS or FAT
  9) I leave the default -> 'NTFS'
  10) Next press
  11) I change to the next window where the information of what is going to 
happen appears and I confirm the format
  12) Then I return to nautilius
  13) The pendrive appears in nautilus
  14) It can not be accessed, even though the pendrive is mounted
  
  Best regards,
  --
  Cristian Aravena Romero (caravena)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-9-generic 4.18.0-9.10
  ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12
  Uname: Linux 4.18.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2162 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 10 14:30:28 2018
  InstallationDate: Installed on 2017-10-13 (362 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-9-generic N/A
   linux-backports-modules-4.18.0-9-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.sku: System SKUNumber
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

** Summary changed:

- It can not be formatted with 'gnome-disk-utility'  the pendrive
+ It can not be formatted with 'gnome-disk-utility 3.30.1'  the pendrive

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

Title:
  It can not be formatted with 'gnome-disk-utility 3.30.1'  the pendrive

Status in Linux:
  Unknown
Status in gnome-disk-utility package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  List: linux-usb
  https://marc.info/?l=linux-usb&m=153919676204905&w=2

  ---

  https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues/104

  ---

  Hello,

  I am trying to format a pendrive of 2TB(Purchased in China for ebay).
  What I do is the following:

  1) I start the notebook with Linux 4.18.0-9
  2) I start with my GNOME session
  3) I connect the pendrive
  4) I open Nautilus
  5) The pendrive in nautilus appears as mounted
  6) In nautilus I hit a right click with the mouse to my pedrive
  7) I choose 'Format'
  8) A window opens where I can only choose between: ext4, NTFS or FAT
  9) I leave the default -> 'NTFS'
  10) Next press
  11) I change to the next window where the information of what is going to 
happen appears and I confirm the format
  12) Then I return to nautilius
  13) The pendrive appears in nautilus
  14) It can not be accessed, even though the pendrive is mounted

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-9-generic 4.18.0-9.10
  ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12
  Uname: Linux 4.18.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2162 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 10 14:30:28 2018
  InstallationDate: Installed on 2017-10-13 (362 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Machine

[Kernel-packages] [Bug 1796720] Re: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460

[Daniel]

I can confirm that the problem is fixed in 4.18.13:

amdgpu-pci-6500
Adapter: PCI adapter
vddgfx:   +0.77 V  
fan1: 968 RPM
temp1:+29.0°C  (crit = +94.0°C, hyst = -273.1°C)
power1:6.11 W  (cap =  48.00 W)


** Tags added: kernel-fixed-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/1796720

Title:
  High GPU temperature after kernel 4.18.0.9.10 on AMD RX460

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Today I have received an update for Linux kernel which upgraded the
  kernel on my Ubuntu 18.10 installation to 4.18.0.9.10! Immediately
  after restart I noticed that the GPU temperature is abnormally High...

  Before Update:
  - GPU fan set to off on idle
  - GPU idle temperature: 29-32 C

  After Update:
  - GPU fan set to off on idle
  - GPU idle temperature: 47-50 C (which I have to put the fans on 50% to keep 
it on 33 C)

  I have also tried to boot from the older kernel (4.18.0.8) and
  everything is normal there!

  System spec:
  - MB: ASUS Prime x299-deluxe
  - CPU: Intel Corei7 7820x skylake-x
  - GPU: AMD RX460

  glxinfo | grep OpenGL:

  OpenGL vendor string: X.Org
  OpenGL renderer string: AMD Radeon (TM) RX 460 Graphics (POLARIS11, DRM 
3.26.0, 4.18.0-9-generic, LLVM 7.0.0)
  OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.1
  OpenGL core profile shading language version string: 4.50
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.1
  OpenGL shading language version string: 4.40
  OpenGL context flags: (none)
  OpenGL profile mask: compatibility profile
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.2.1
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
  OpenGL ES profile extensions:

  sudo cat /sys/kernel/debug/dri/0/amdgpu_pm_info:

  Clock Gating Flags Mask: 0x37bcf
   Graphics Medium Grain Clock Gating: On
   Graphics Medium Grain memory Light Sleep: On
   Graphics Coarse Grain Clock Gating: On
   Graphics Coarse Grain memory Light Sleep: On
   Graphics Coarse Grain Tree Shader Clock Gating: Off
   Graphics Coarse Grain Tree Shader Light Sleep: Off
   Graphics Command Processor Light Sleep: On
   Graphics Run List Controller Light Sleep: On
   Graphics 3D Coarse Grain Clock Gating: Off
   Graphics 3D Coarse Grain memory Light Sleep: Off
   Memory Controller Light Sleep: On
   Memory Controller Medium Grain Clock Gating: On
   System Direct Memory Access Light Sleep: Off
   System Direct Memory Access Medium Grain Clock Gating: On
   Bus Interface Medium Grain Clock Gating: Off
   Bus Interface Light Sleep: On
   Unified Video Decoder Medium Grain Clock Gating: On
   Video Compression Engine Medium Grain Clock Gating: On
   Host Data Path Light Sleep: Off
   Host Data Path Medium Grain Clock Gating: On
   Digital Right Management Medium Grain Clock Gating: Off
   Digital Right Management Light Sleep: Off
   Rom Medium Grain Clock Gating: On
   Data Fabric Medium Grain Clock Gating: Off

  GFX Clocks and Power:
   1750 MHz (MCLK)
   1212 MHz (SCLK)
   214 MHz (PSTATE_SCLK)
   300 MHz (PSTATE_MCLK)
   1081 mV (VDDGFX)
   18.65 W (average GPU)

  GPU Temperature: 39 C
  GPU Load: 0 %

  UVD: Disabled

  VCE: Disabled

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-9-generic 4.18.0-9.10
  ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12
  Uname: Linux 4.18.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  shadowfax   3078 F pulseaudio
   /dev/snd/controlC0:  shadowfax   3078 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  8 20:27:13 2018
  InstallationDate: Installed on 2018-09-26 (11 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180925.1)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-9-generic 
root=UUID=a58662c7-39e2-4f05-9da6-d63173c94d53 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-9-generic N/A
   linux-backports-modules-4.18.0-9-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1503
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X299-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3

[Kernel-packages] [Bug 1797061] Re: linux: 4.15.0-38.41 -proposed tracker

[Brad Figg]

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1797074 (linux-azure), bug 1797076 (linux-hwe), bug 1797078 
(linux-azure-edge), bug 1797080 (linux-gcp), bug 1797081 (linux-hwe-edge), bug 
1797082 (linux-azure)
  derivatives: bug 1797062 (linux-gcp), bug 1797065 (linux-kvm), bug 1797066 
(linux-aws), bug 1797067 (linux-azure), bug 1797069 (linux-oem), bug 1797073 
(linux-raspi2)
  kernel-stable-phase-changed:Wednesday, 10. October 2018 11:02 UTC
  kernel-stable-phase:Uploaded
  
  -- swm properties --
+ boot-testing-requested: true
  phase: Uploaded

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

Title:
  linux: 4.15.0-38.41 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

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

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

  backports: bug 1797074 (linux-azure), bug 1797076 (linux-hwe), bug 1797078 
(linux-azure-edge), bug 1797080 (linux-gcp), bug 1797081 (linux-hwe-edge), bug 
1797082 (linux-azure)
  derivatives: bug 1797062 (linux-gcp), bug 1797065 (linux-kvm), bug 1797066 
(linux-aws), bug 1797067 (linux-azure), bug 1797069 (linux-oem), bug 1797073 
(linux-raspi2)
  kernel-stable-phase-changed:Wednesday, 10. October 2018 11:02 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1797062] Re: linux-gcp: 4.15.0-1023.24 -proposed tracker

[Brad Figg]

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

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

Title:
  linux-gcp: 4.15.0-1023.24 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1797061
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1797202] [NEW] [Bionic] arm64: topology: Avoid checking numa mask for scheduler MC selection

[Manoj Iyer]

Public bug reported:

[Impact]
The numa mask subset check can often lead to system hang or crash during CPU 
hotplug and system suspend operation if NUMA is disabled. This is mostly 
observed on HMP systems where the CPU compute capacities are different and ends 
up in different scheduler domains. Since cpumask_of_node is returned instead 
core_sibling, the scheduler is confused with incorrect cpumasks(e.g. one CPU in 
two different sched domains at the same time) on CPU hotplug.

[Fix]
The following patch fixes this issue:
e156ab71a974 arm64: topology: Avoid checking numa mask for scheduler MC 
selection

[Test]

[Regression Potential]

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


** Tags: cavium

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

Title:
  [Bionic] arm64: topology: Avoid checking numa mask for scheduler MC
  selection

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  The numa mask subset check can often lead to system hang or crash during CPU 
hotplug and system suspend operation if NUMA is disabled. This is mostly 
observed on HMP systems where the CPU compute capacities are different and ends 
up in different scheduler domains. Since cpumask_of_node is returned instead 
core_sibling, the scheduler is confused with incorrect cpumasks(e.g. one CPU in 
two different sched domains at the same time) on CPU hotplug.

  [Fix]
  The following patch fixes this issue:
  e156ab71a974 arm64: topology: Avoid checking numa mask for scheduler MC 
selection

  [Test]

  [Regression Potential]

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

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

[Kernel-packages] [Bug 1797190] Re: It can not be formatted with 'gnome-disk-utility' the pendrive

[Cristian Aravena Romero]

** Description changed:

  https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues/104
  
  ---
  
  Hello,
  
- I am trying to format a pendrive 2TB(Purchased in China for ebay). What
- I do is the following:
+ I am trying to format a pendrive of 2TB(Purchased in China for ebay).
+ What I do is the following:
  
  1) I start the notebook with Linux 4.18.0-9
  2) I start with my GNOME session
  3) I connect the pendrive
  4) I open Nautilus
  5) The pendrive in nautilus appears as mounted
  6) In nautilus I hit a right click with the mouse to my pedrive
  7) I choose 'Format'
  8) A window opens where I can only choose between: ext4, NTFS or FAT
  9) I leave the default -> 'NTFS'
  10) Next press
  11) I change to the next window where the information of what is going to 
happen appears and I confirm the format
  12) Then I return to nautilius
  13) The pendrive appears in nautilus
  14) It can not be accessed, even though the pendrive is mounted
  
  Best regards,
  --
  Cristian Aravena Romero (caravena)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-9-generic 4.18.0-9.10
  ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12
  Uname: Linux 4.18.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2162 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 10 14:30:28 2018
  InstallationDate: Installed on 2017-10-13 (362 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-9-generic N/A
   linux-backports-modules-4.18.0-9-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.sku: System SKUNumber
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=201371
   Importance: Unknown
   Status: Unknown

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

Title:
  It can not be formatted with 'gnome-disk-utility'  the pendrive

Status in Linux:
  Unknown
Status in gnome-disk-utility package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues/104

  ---

  Hello,

  I am trying to format a pendrive of 2TB(Purchased in China for ebay).
  What I do is the following:

  1) I start the notebook with Linux 4.18.0-9
  2) I start with my GNOME session
  3) I connect the pendrive
  4) I open Nautilus
  5) The pendrive in nautilus appears as mounted
  6) In nautilus I hit a right click with the mouse to my pedrive
  7) I choose 'Format'
  8) A window opens where I can only choose between: ext4, NTFS or FAT
  9) I leave the default -> 'NTFS'
  10) Next press
  11) I change to the next window where the information of what is going to 
happen appears and I confirm the format
  12) Then I return to nautilius
  13) The pendrive appears in nautilus
  14) It can not be accessed, even though the pendrive is mounted

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-9-generic 4.18.0-9.10
  ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12
  Uname: Linux 4.18.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2162 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 10 14:30:28 2018
  InstallationDate: Installed on 2017-10-13 (362 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Machin

[Kernel-packages] [Bug 1746088] Re: [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel

[Steve Langasek]

An audit of package versions across Ubuntu releases shows that crash is
at a higher version number in xenial-updates than it is in bionic.  If
this was appropriate to SRU to xenial, then it also needs to be SRUed to
bionic so that users don't see inconsistent behavior on bionic for
upgrades vs. new installs.

** Changed in: crash (Ubuntu Bionic)
   Status: Fix Released => Triaged

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

Title:
  [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
  4.13.0-26-generic kernel

Status in The Ubuntu-power-systems project:
  Fix Released
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Fix Released
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  Triaged

Bug description:
  [Impact]
  It won't be possible to analyze dumps produced by newer kernels (hwe on 
xenial, for example).

  [Test Case]
  Tested that this version of crash can analyze both GA (4.4) and hwe (4.15) 
kernels.

  [Regression Potential]
  New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing may be desirable.


  ---Problem Description---
  Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel 
(Ubuntu 16.04.4)

  ---uname output---
  Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8001-22C

  ---Steps to Reproduce---
   This bug follow up bug of 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=163565
  The steps to create dump is as follows

  Once you generate the kdump
  use crash to analyze the vmcore and we get this error

  console logs ==

  root@ltc-briggs1:/var/crash/201801150227# ls
  dmesg.201801150227  vmcore.201801150227
  .0-26-generic vmcore.2018011502271150227# crash 
/usr/lib/debug/boot/vmlinux-4.13.

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  WARNING: cannot access vmalloc'd module memory

  crash: invalid structure member offset: thread_info_task
     FILE: task.c  LINE: 598  FUNCTION: irqstacks_init()

  [/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 =>
  100833e0

    100833e0: (undetermined)
    1017d220: OFFSET_verify+80
    1011552c: task_init+5084
    1008ade0: main_loop+336

  == Comment from Hari Krishna Bathini ==

  There are quite a few commits (all available upstream) that are needed for
  crash tool to work fine. I think the right thing to do here would be to use
  the latest crash tool version 7.2.0 to go with the kernel update. Also, the
  below commit would be needed on top of 7.2.0 crash utility:

    commit c8178eca9c74f81a7f803a58d339635cc152e8d9
    Author: Dave Anderson 
    Date:   Thu Nov 9 11:39:05 2017 -0500

  Update for support of Linux 4.14 and later PPC64 kernels where the
  hash page table geometry accomodates a larger virtual address range.
  Without the patch, the virtual-to-physical translation of user space
  virtual addresses by "vm -p", "vtop", and "rd -u" may generate an
  invalid translation or otherwise fail.
  (hbath...@linux.vnet.ibm.com)

  Similar thing holds true for makedumpfile tool..

  Thanks
  Hari

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

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

[Kernel-packages] [Bug 1797200] [NEW] [Bionic] ACPI / PPTT: use ACPI ID whenever ACPI_PPTT_ACPI_PROCESSOR_ID_VALID is set

[Manoj Iyer]

Public bug reported:

[Impact]
Currently, we use the ACPI processor ID only for the leaf/processor nodes as 
the specification states it must match the value of the ACPI processor ID field 
in the processor’s entry in the MADT.

However, if a PPTT structure represents a processors group, it matches a 
processor container UID in the namespace and the 
ACPI_PPTT_ACPI_PROCESSOR_ID_VALID flag indicates whether the ACPI processor ID 
is valid.

Let's use UID whenever ACPI_PPTT_ACPI_PROCESSOR_ID_VALID is set to be 
consistent instead of using table offset as it's currently done for non-leaf 
nodes.

Fixes: 2bd00bcd73e5 (ACPI/PPTT: Add Processor Properties Topology Table parsing)


[Fix]
This patch in is 4.18:
30998033f62a ACPI / PPTT: use ACPI ID whenever 
ACPI_PPTT_ACPI_PROCESSOR_ID_VALID is set

[Test]


[Regression Potential]

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


** Tags: cavium

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

Title:
  [Bionic] ACPI / PPTT: use ACPI ID whenever
  ACPI_PPTT_ACPI_PROCESSOR_ID_VALID is set

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  Currently, we use the ACPI processor ID only for the leaf/processor nodes as 
the specification states it must match the value of the ACPI processor ID field 
in the processor’s entry in the MADT.

  However, if a PPTT structure represents a processors group, it matches a 
processor container UID in the namespace and the 
ACPI_PPTT_ACPI_PROCESSOR_ID_VALID flag indicates whether the ACPI processor ID 
is valid.
  
  Let's use UID whenever ACPI_PPTT_ACPI_PROCESSOR_ID_VALID is set to be 
consistent instead of using table offset as it's currently done for non-leaf 
nodes.
  
  Fixes: 2bd00bcd73e5 (ACPI/PPTT: Add Processor Properties Topology Table 
parsing)

  
  [Fix]
  This patch in is 4.18:
  30998033f62a ACPI / PPTT: use ACPI ID whenever 
ACPI_PPTT_ACPI_PROCESSOR_ID_VALID is set

  [Test]

  
  [Regression Potential]

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

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

[Kernel-packages] [Bug 1797190] Re: It can not be formatted with 'gnome-disk-utility' the pendrive

[Cristian Aravena Romero]

** Attachment added: "dmesg_4.19.0-041900rc7-generic.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797190/+attachment/5199640/+files/dmesg_4.19.0-041900rc7-generic.txt

** Description changed:

  Hello,
  
- I am trying to format a pendrive. What I do is the following:
+ I am trying to format a pendrive 2TB(purchased in China). What I do is
+ the following:
  
  1) I start the notebook with Linux 4.18.0-9
  2) I start with my GNOME session
  3) I connect the pendrive
  4) I open Nautilus
  5) The pendrive in nautilus appears as mounted
  6) In nautilus I hit a right click with the mouse to my pedrive
  7) I choose 'Format'
  8) A window opens where I can only choose between: ext4, NTFS or FAT
  9) I leave the default -> 'NTFS'
  10) Next press
  11) I change to the next window where the information of what is going to 
happen appears and I confirm the format
  12) Then I return to nautilius
  13) The pendrive appears in nautilus
  14) It can not be accessed, even though the pendrive is mounted
  
  Best regards,
  --
  Cristian Aravena Romero (caravena)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-9-generic 4.18.0-9.10
  ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12
  Uname: Linux 4.18.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2162 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 10 14:30:28 2018
  InstallationDate: Installed on 2017-10-13 (362 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-9-generic N/A
   linux-backports-modules-4.18.0-9-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.sku: System SKUNumber
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

** Description changed:

  Hello,
  
- I am trying to format a pendrive 2TB(purchased in China). What I do is
- the following:
+ I am trying to format a pendrive 2TB(purchased in China for ebay). What
+ I do is the following:
  
  1) I start the notebook with Linux 4.18.0-9
  2) I start with my GNOME session
  3) I connect the pendrive
  4) I open Nautilus
  5) The pendrive in nautilus appears as mounted
  6) In nautilus I hit a right click with the mouse to my pedrive
  7) I choose 'Format'
  8) A window opens where I can only choose between: ext4, NTFS or FAT
  9) I leave the default -> 'NTFS'
  10) Next press
  11) I change to the next window where the information of what is going to 
happen appears and I confirm the format
  12) Then I return to nautilius
  13) The pendrive appears in nautilus
  14) It can not be accessed, even though the pendrive is mounted
  
  Best regards,
  --
  Cristian Aravena Romero (caravena)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-9-generic 4.18.0-9.10
  ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12
  Uname: Linux 4.18.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2162 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 10 14:30:28 2018
  InstallationDate: Installed on 2017-10-13 (362 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-9-generic N/A
   linux-backports-modules-4.18.0-9-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bio

[Kernel-packages] [Bug 1797190] Re: It can not be formatted with 'gnome-disk-utility' the pendrive

[Cristian Aravena Romero]

https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues/104
--
Cristian Aravena Romero (caravena)

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

Title:
  It can not be formatted with 'gnome-disk-utility'  the pendrive

Status in Linux:
  Unknown
Status in gnome-disk-utility package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues/104

  ---

  Hello,

  I am trying to format a pendrive of 2TB(Purchased in China for ebay).
  What I do is the following:

  1) I start the notebook with Linux 4.18.0-9
  2) I start with my GNOME session
  3) I connect the pendrive
  4) I open Nautilus
  5) The pendrive in nautilus appears as mounted
  6) In nautilus I hit a right click with the mouse to my pedrive
  7) I choose 'Format'
  8) A window opens where I can only choose between: ext4, NTFS or FAT
  9) I leave the default -> 'NTFS'
  10) Next press
  11) I change to the next window where the information of what is going to 
happen appears and I confirm the format
  12) Then I return to nautilius
  13) The pendrive appears in nautilus
  14) It can not be accessed, even though the pendrive is mounted

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-9-generic 4.18.0-9.10
  ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12
  Uname: Linux 4.18.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2162 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 10 14:30:28 2018
  InstallationDate: Installed on 2017-10-13 (362 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-9-generic N/A
   linux-backports-modules-4.18.0-9-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.sku: System SKUNumber
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic

[Heribert Heckhoff]

The Kernel
(4.17.0-041700rc2-generic_4.17.0-041700rc2.201810101258_amd64) posted in
comment #46 just works great with ant_sel=1 . Signal level is as good as
with 4.15.0-32-generic.

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

Title:
  rtl8723be wifi does not work under linux-modules-
  extra-4.15.0-33-generic

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

Bug description:
  When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with
  kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK.

  Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any
  wifi networks and thus there is no connection. Changing the antenna
  setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either;
  as a workaround an external wifi device (Gigaset USB Adapter 108)
  works.

  The expectation is that wifi through rtl8723be will still work under 
4.15.0-33.36 as it did previously.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  al 1234 F pulseaudio
   /dev/snd/controlC0:  al 1234 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-05-27 (89 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Hewlett-Packard HP Notebook
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.02
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8137
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 99.02
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1797190] Re: It can not be formatted with 'gnome-disk-utility' to pendrive

[Cristian Aravena Romero]

** Description changed:

  Hello,
  
  I am trying to format a pendrive. What I do is the following:
  
  1) I start the notebook with Linux 4.18.0-9
- 2) Join my GNOME session
+ 2) I start with my GNOME session
  3) I connect the pendrive
  4) I open Nautilus
  5) The pendrive in nautilus appears as mounted
  6) In nautilus I hit a right click with the mouse to my pedrive
  7) I choose 'Format'
  8) A window opens where I can only choose between: ext4, NTFS or FAT
  9) I leave the default -> 'NTFS'
  10) Next press
  11) I change to the next window where the information of what is going to 
happen appears and I confirm the format
  12) Then I return to nautilius
  13) The pendrive appears in nautilus
  14) It can not be entered, even though the pendrive is mounted
  
  Best regards,
  --
  Cristian Aravena Romero (caravena)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-9-generic 4.18.0-9.10
  ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12
  Uname: Linux 4.18.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2162 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 10 14:30:28 2018
  InstallationDate: Installed on 2017-10-13 (362 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-9-generic N/A
   linux-backports-modules-4.18.0-9-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.sku: System SKUNumber
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

** Description changed:

  Hello,
  
  I am trying to format a pendrive. What I do is the following:
  
  1) I start the notebook with Linux 4.18.0-9
  2) I start with my GNOME session
  3) I connect the pendrive
  4) I open Nautilus
  5) The pendrive in nautilus appears as mounted
  6) In nautilus I hit a right click with the mouse to my pedrive
  7) I choose 'Format'
  8) A window opens where I can only choose between: ext4, NTFS or FAT
  9) I leave the default -> 'NTFS'
  10) Next press
  11) I change to the next window where the information of what is going to 
happen appears and I confirm the format
  12) Then I return to nautilius
  13) The pendrive appears in nautilus
- 14) It can not be entered, even though the pendrive is mounted
+ 14) It can not be accessed, even though the unit is mounted
  
  Best regards,
  --
  Cristian Aravena Romero (caravena)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-9-generic 4.18.0-9.10
  ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12
  Uname: Linux 4.18.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2162 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 10 14:30:28 2018
  InstallationDate: Installed on 2017-10-13 (362 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-9-generic N/A
   linux-backports-modules-4.18.0-9-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dm

[Kernel-packages] [Bug 1783140] Re: KVM live migration fails

[Launchpad Bug Tracker]

This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.32

---
qemu (1:2.5+dfsg-5ubuntu10.32) xenial; urgency=medium

  * fix migration of new guests on ppc64el (LP: #1783140)
Fixed by backporting two patches from the 2.6.x stable branch
- d/p/ubuntu/lp-1783140-virtio-set-low-features-early-on-load.patch
- d/p/ubuntu/lp-1783140-Revert-virtio-net-unbreak-self-announcement.patch

 -- Christian Ehrhardt   Tue, 11 Sep
2018 15:00:19 +0200

** Changed in: qemu (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  KVM live migration fails

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Fix Released
Status in qemu source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Backport fix from the 2.6.2 stable branch to the qemu 2.5 in Xenial

   * Newer guests might use virtio attributes that are clobbered on 
 migration with the old qemu code.

  [Test Case]

   * Setup two Xenial hosts on ppc64el

   * Create a guest that has a rather new kernel (>=4.14) I'd recommend 
 Bionic

   * Migrate that guest from Host1 to Host2

  [Regression Potential]

   * The modification could affect virtio handling in other cases in a non 
 expected way, but mostly related to migrations. So the expected 
 regression would be issues to migrate properly.
 I verified plenty of migrations in regression testing and we had
 this very code in the Yakkety release as we picked 2.6.1 stable release 
 back then. Due to that it is actually pretty well tested and should not 
 really regress anything out in the wild.

  [Other Info]
   
   * So far this only triggers on the confused endian marshalling on 
 ppc64el, but in theory a different case could trigger it on x86 just as 
 much.

  ---

  Environment:
  2 POWER8 with Ubuntu 16.04.4 LTS as KVM hypervisor.
  1 KVM guest with Ubuntu 18.04 LTS. Virtual disk for the guest is a qcow2 file 
on an NFS share, accessible from both hypervisors, so live migration is 
possible and works for all other guests (SLES, RHEL, Ubunutu 16.04),
  Live migratino of Ubuntu 18.04 guest fails on ppc, while the same test on an 
x86_64 environment suceeds.

  root@pkvm2:~# virsh migrate --persistent --live p8lnxtst4 
qemu+ssh://pkvm1/system
  error: internal error: early end of file from monitor, possible problem: 
2018-07-23T11:12:25.586385Z qemu-system-ppc64: VQ 0 size 0x100 Guest index 
0x38aa inconsistent with Host index 0xa980: delta 0x8f2a
  2018-07-23T11:12:25.586434Z qemu-system-ppc64: error while loading state for 
instance 0x0 of device 'pci@8002000:01.0/virtio-net'
  2018-07-23T11:12:25.587246Z qemu-system-ppc64: load of migration failed: 
Operation not permitted

  root@pkvm2:~# uname -a
  Linux pkvm2 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:51:21 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux

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

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

[Kernel-packages] [Bug 1797190] [NEW] It can not be formatted with 'gnome-disk-utility' to pendrive

[Cristian Aravena Romero]

Public bug reported:

Hello,

I am trying to format a pendrive. What I do is the following:

1) I start the notebook with Linux 4.18.0-9
2) I start with my GNOME session
3) I connect the pendrive
4) I open Nautilus
5) The pendrive in nautilus appears as mounted
6) In nautilus I hit a right click with the mouse to my pedrive
7) I choose 'Format'
8) A window opens where I can only choose between: ext4, NTFS or FAT
9) I leave the default -> 'NTFS'
10) Next press
11) I change to the next window where the information of what is going to 
happen appears and I confirm the format
12) Then I return to nautilius
13) The pendrive appears in nautilus
14) It can not be accessed, even though the pendrive is mounted

Best regards,
--
Cristian Aravena Romero (caravena)

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-9-generic 4.18.0-9.10
ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12
Uname: Linux 4.18.0-9-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caravena   2162 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 10 14:30:28 2018
InstallationDate: Installed on 2017-10-13 (362 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-9-generic N/A
 linux-backports-modules-4.18.0-9-generic  N/A
 linux-firmware1.175
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.family: ChiefRiver System
dmi.product.name: 530U3C/530U4C
dmi.product.sku: System SKUNumber
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

** Affects: gnome-disk-utility (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug cosmic package-from-proposed wayland-session

** Summary changed:

- It can not be formatted with 'gnome-disk-utility 3.30.1' and access with 
'nautilus 3.26.4' to pendrive
+ It can not be formatted with 'gnome-disk-utility' and access with 'nautilus' 
to pendrive

** Also affects: gnome-disk-utility (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- It can not be formatted with 'gnome-disk-utility' and access with 'nautilus' 
to pendrive
+ It can not be formatted with 'gnome-disk-utility'  to pendrive

** Description changed:

  Hello,
  
  I am trying to format a pendrive. What I do is the following:
  
  1) I start the notebook with Linux 4.18.0-9
  2) Join my GNOME session
  3) I connect the pendrive
  4) I open Nautilus
  5) The pendrive in nautilus appears as mounted
  6) In nautilus I hit a right click with the mouse to my pedrive
  7) I choose 'Format'
  8) A window opens where I can only choose between: ext4, NTFS or FAT
  9) I leave the default -> 'NTFS'
  10) Next press
  11) I change to the next window where the information of what is going to 
happen appears and I confirm the format
  12) Then I return to nautilius
  13) The pendrive appears in nautilus
- 14) It can not be entered, even though the unit is mounted
+ 14) It can not be entered, even though the pendrive is mounted
  
  Best regards,
  --
  Cristian Aravena Romero (caravena)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-9-generic 4.18.0-9.10
  ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12
  Uname: Linux 4.18.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  caravena   2162 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  caravena   2162 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 10 14:30:28 2018
  InstallationDate: Installed on 2017-10-13 (362 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-9-generic 
root=UUID=707d0f89-4b1

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  It can not be formatted with 'gnome-disk-utility'  to pendrive

Status in gnome-disk-utility package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I am trying to format a pendrive. What I do is the following:

  1) I start the notebook with Linux 4.18.0-9
  2) I start with my GNOME session
  3) I connect the pendrive
  4) I open Nautilus
  5) The pendrive in nautilus appears as mounted
  6) In nautilus I hit a right click with the mouse to my pedrive
  7) I choose 'Format'
  8) A window opens where I can only choose between: ext4, NTFS or FAT
  9) I leave the default -> 'NTFS'
  10) Next press
  11) I change to the next window where the information of what is going to 
happen appears and I confirm the format
  12) Then I return to nautilius
  13) The pendrive appears in nautilus
  14) It can not be accessed, even though the pendrive is mounted

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-9-generic 4.18.0-9.10
  ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12
  Uname: Linux 4.18.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2162 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 10 14:30:28 2018
  InstallationDate: Installed on 2017-10-13 (362 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-9-generic N/A
   linux-backports-modules-4.18.0-9-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.sku: System SKUNumber
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1797190/+subscriptions

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

[Kernel-packages] [Bug 1783140] Re: KVM live migration fails

[Robie Basak]

I see the following autopkgtest failures:

Regression in autopkgtest for open-iscsi (amd64): test log
Regression in autopkgtest for ubuntu-image (amd64): test log

However looking at the history the particular tests failing seem to be
flaky and unrelated to this SRU, and all the others continue to pass.

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

Title:
  KVM live migration fails

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Fix Released
Status in qemu source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Backport fix from the 2.6.2 stable branch to the qemu 2.5 in Xenial

   * Newer guests might use virtio attributes that are clobbered on 
 migration with the old qemu code.

  [Test Case]

   * Setup two Xenial hosts on ppc64el

   * Create a guest that has a rather new kernel (>=4.14) I'd recommend 
 Bionic

   * Migrate that guest from Host1 to Host2

  [Regression Potential]

   * The modification could affect virtio handling in other cases in a non 
 expected way, but mostly related to migrations. So the expected 
 regression would be issues to migrate properly.
 I verified plenty of migrations in regression testing and we had
 this very code in the Yakkety release as we picked 2.6.1 stable release 
 back then. Due to that it is actually pretty well tested and should not 
 really regress anything out in the wild.

  [Other Info]
   
   * So far this only triggers on the confused endian marshalling on 
 ppc64el, but in theory a different case could trigger it on x86 just as 
 much.

  ---

  Environment:
  2 POWER8 with Ubuntu 16.04.4 LTS as KVM hypervisor.
  1 KVM guest with Ubuntu 18.04 LTS. Virtual disk for the guest is a qcow2 file 
on an NFS share, accessible from both hypervisors, so live migration is 
possible and works for all other guests (SLES, RHEL, Ubunutu 16.04),
  Live migratino of Ubuntu 18.04 guest fails on ppc, while the same test on an 
x86_64 environment suceeds.

  root@pkvm2:~# virsh migrate --persistent --live p8lnxtst4 
qemu+ssh://pkvm1/system
  error: internal error: early end of file from monitor, possible problem: 
2018-07-23T11:12:25.586385Z qemu-system-ppc64: VQ 0 size 0x100 Guest index 
0x38aa inconsistent with Host index 0xa980: delta 0x8f2a
  2018-07-23T11:12:25.586434Z qemu-system-ppc64: error while loading state for 
instance 0x0 of device 'pci@8002000:01.0/virtio-net'
  2018-07-23T11:12:25.587246Z qemu-system-ppc64: load of migration failed: 
Operation not permitted

  root@pkvm2:~# uname -a
  Linux pkvm2 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:51:21 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux

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

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

[Kernel-packages] [Bug 1783140] Update Released

[Robie Basak]

The verification of the Stable Release Update for qemu has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  KVM live migration fails

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Fix Released
Status in qemu source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Backport fix from the 2.6.2 stable branch to the qemu 2.5 in Xenial

   * Newer guests might use virtio attributes that are clobbered on 
 migration with the old qemu code.

  [Test Case]

   * Setup two Xenial hosts on ppc64el

   * Create a guest that has a rather new kernel (>=4.14) I'd recommend 
 Bionic

   * Migrate that guest from Host1 to Host2

  [Regression Potential]

   * The modification could affect virtio handling in other cases in a non 
 expected way, but mostly related to migrations. So the expected 
 regression would be issues to migrate properly.
 I verified plenty of migrations in regression testing and we had
 this very code in the Yakkety release as we picked 2.6.1 stable release 
 back then. Due to that it is actually pretty well tested and should not 
 really regress anything out in the wild.

  [Other Info]
   
   * So far this only triggers on the confused endian marshalling on 
 ppc64el, but in theory a different case could trigger it on x86 just as 
 much.

  ---

  Environment:
  2 POWER8 with Ubuntu 16.04.4 LTS as KVM hypervisor.
  1 KVM guest with Ubuntu 18.04 LTS. Virtual disk for the guest is a qcow2 file 
on an NFS share, accessible from both hypervisors, so live migration is 
possible and works for all other guests (SLES, RHEL, Ubunutu 16.04),
  Live migratino of Ubuntu 18.04 guest fails on ppc, while the same test on an 
x86_64 environment suceeds.

  root@pkvm2:~# virsh migrate --persistent --live p8lnxtst4 
qemu+ssh://pkvm1/system
  error: internal error: early end of file from monitor, possible problem: 
2018-07-23T11:12:25.586385Z qemu-system-ppc64: VQ 0 size 0x100 Guest index 
0x38aa inconsistent with Host index 0xa980: delta 0x8f2a
  2018-07-23T11:12:25.586434Z qemu-system-ppc64: error while loading state for 
instance 0x0 of device 'pci@8002000:01.0/virtio-net'
  2018-07-23T11:12:25.587246Z qemu-system-ppc64: load of migration failed: 
Operation not permitted

  root@pkvm2:~# uname -a
  Linux pkvm2 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:51:21 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux

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

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

[Kernel-packages] [Bug 1793430] Re: Page leaking in cachefiles_read_backing_file while vmscan is active

[Kiran Kumar Modukuri]

All tests passed from Nvidia testing for fscache.

Your sosreport has been generated and saved in:
  /tmp/sosreport-tid1870983.00195310-20181009172638.tar.xz

The checksum is: 2f7b671685cf8116920efb63e6397fe2



** Attachment added: "sosreport-tid1870983.00195310-20181009172638.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793430/+attachment/5199600/+files/sosreport-tid1870983.00195310-20181009172638.tar.xz

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

Title:
  Page leaking in cachefiles_read_backing_file while vmscan is active

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

Bug description:
  SRU Justification
  -

  [Description]
  In a heavily loaded system where the system pagecache is nearing memory 
limits and fscache is enabled, pages can be leaked by fscache while trying read 
pages from cachefiles backend. This can happen because two applications can be 
reading same page from a single mount, two threads can be trying to read the 
backing page at same time. This results in one of the thread finding that a 
page for the backing file or netfs file is already in the radix tree. During 
the error handling cachefiles does not cleanup the reference on backing page, 
leading to page leak.
  
  [Fix]
  The fix is straightforward, to decrement the reference when error is 
encounterd.
  
  [Testing]
  A user has tested the fix using following method for 12+ hrs.
  
  1) mkdir -p /mnt/nfs ; mount -o vers=3,fsc :/export /mnt/nfs
  2) create 1 files of 2.8MB in a NFS mount.
  3) start a thread to simulate heavy VM presssure
 (while true ; do echo 3 > /proc/sys/vm/drop_caches ; sleep 1 ; done)&
  4) start multiple parallel reader for data set at same time
 find /mnt/nfs -type f | xargs -P 80 cat > /dev/null &
 find /mnt/nfs -type f | xargs -P 80 cat > /dev/null &
 find /mnt/nfs -type f | xargs -P 80 cat > /dev/null &
 ..
 ..
 find /mnt/nfs -type f | xargs -P 80 cat > /dev/null &
 find /mnt/nfs -type f | xargs -P 80 cat > /dev/null &
  5) finally check using cat /proc/fs/fscache/stats | grep -i pages ;
 free -h , cat /proc/meminfo and page-types -r -b lru
 to ensure all pages are freed.

  [Regression Potential]
  Limited to cachefiles.

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

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

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

[bugproxy]

--- Comment From mranw...@us.ibm.com 2018-10-10 13:30 EDT---
I gave that a try and still saw the problem:
Linux version 4.15.0-36-generic (jsalisbury@kathleen) (gcc version 7.3.0 
(Ubuntu 7.3.0-16ubuntu3)) #40~lp1792195 SMP Wed Oct 10 13:19:58 UTC 2018

Does that also include bd0dbb73e01306a1060e56f81e5fe287be936477?

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

Title:
  Signal 7 error when running GPFS tracing in cluster

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  -- Problem Description --
  GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel 
driver using vmalloc) and then writing trace records from user space threads in 
parallel.  While the SIGBUS happened, the access virtual memory address is in 
the mapped range, no overflow on access.

  Worked with Benjamin Herrenschmidt on GPFS tracing kernel driver code
  and he made a suggestion as workaround on the driver code to bypass
  the problem, and it works

  the workaround code change as below:

   - rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, PAGE_SHARED);
  + rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, 
__pgprot(pgprot_val(PAGE_SHARED)|_PAGE_DIRTY);

  As Benjamin mentioned, this is a Linux kernel bug and this is just a
  workaround. He will give the details about the kernel bug and why this
  workaround works

  The root cause is that for PTEs created by a driver at mmap time (ie,
  that aren't created dynamically at fault time), it's not legit for
  ptep_set_access_flags() to make them invalid even temporarily. A
  concurrent access while they are invalid will be unable to service the
  page fault and will cause as SIGBUS.

  Thankfully such PTEs shouldn't normally be the subject of a RO->RW
  privilege escalation.

  What happens is that the GPFS driver creates the PTEs using
  remap_pfn_range(...,PAGE_SHARED).

  PAGE_SHARED has _PAGE_ACCESSED (R) but not _PAGE_DIRTY (C) set.

  Thus on the first write, we try set C and while doing so, hit the
  above workaround, which causes the problem described earlier.

  The proposed patch will ensure we only do the Nest MMU hack when
  changing _PAGE_RW and not for normal R/C updates.

  The workaround tested by the GPFS team consists of adding _PAGE_DIRTY
  to the mapping created by remap_pfn_range() to avoid the RC update
  fault completely.

  This is fixed by these:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd0dbb73e01306a1060e56f81e5fe287be936477

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f08d08f3db55452d31ba4a37c702da6245876b96

  Since DD1 support is still in (ie,
  2bf1071a8d50928a4ae366bb3108833166c2b70c is not applied) the second
  doesn't apply cleanly.  Did you want that attached?

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

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

[Kernel-packages] [Bug 1797062] Re: linux-gcp: 4.15.0-1023.24 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1797061
  phase: Uploaded

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

Title:
  linux-gcp: 4.15.0-1023.24 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1797061
  phase: Uploaded

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  PC is unbearably slow

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Everything on my machine is running abnormally, unbearably slow - From
  opening an application from either my GUI (GNOME) to BASH. Simple
  tasks like checking for an update to opening a web browser is just
  god-aweful slow, yet it behaves just fine booting up from the HDD and
  running benchmarks.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_4_15_0_34_37_generic_44
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeb1786 F pulseaudio
   /dev/snd/controlC0:  jeb1786 F pulseaudio
   /dev/snd/controlC2:  jeb1786 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 10 12:09:11 2018
  InstallationDate: Installed on 2018-08-17 (54 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: BIOSTAR Group A880G+
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=a967adb1-1600-455b-8704-e2bf5de5081d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-generic N/A
   linux-backports-modules-4.15.0-34-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080016
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: A880G+
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: A880G+
  dmi.sys.vendor: BIOSTAR Group

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

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