from:"Joseph Salisbury"

[Kernel-packages] [Bug 1798110] Re: xenial: virtio-scsi: CPU soft lockup due to loop in virtscsi_target_destroy()

2018-10-16 Thread Joseph Salisbury

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

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

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

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

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

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

Title:
  xenial: virtio-scsi: CPU soft lockup due to loop in
  virtscsi_target_destroy()

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

Bug description:
  [Impact]

   * Detaching virtio-scsi disk in Xenial guest can cause
     CPU soft lockup in guest (and take 100% CPU in host).

   * It may prevent further progress on other tasks that
     depend on resources locked earlier in the SCSI target
     removal stack, and/or impact other SCSI functionality.

   * The fix resolves a corner case in the requests counter
     in the virtio SCSI target, which impacts a downstream
     (SAUCE) patch in the virtio-scsi target removal handler
     that depends on the requests counter value to be zero.

  [Test Case]

   * See LP #1798110 (this bug)'s comment #3 (too long for
     this section -- synthetic case with GDB+QEMU) and
     comment #4 (organic test case in cloud instance).

  [Regression Potential]

   * It seem low -- this only affects the SCSI command requeue
     path with regards to the reference counter, which is only
     used with real chance of problems in our downstream patch
     (which is now passing this testcase).

   * The other less serious issue would be decrementing it to
     a negative / < 0 value, which is not possible with this
     driver logic (see commit message), because the reqs counter
     is always incremented before calling virtscsi_queuecommand(),
     where this decrement operation is inserted.

  [Original Description]

  A customer reported a CPU soft lockup on Trusty HWE kernel from Xenial
  when detaching a virtio-scsi drive, and provided a crashdump that shows
  2 things:

  1) The soft locked up CPU is waiting for another CPU to finish something,
  and that does not happen because the other CPU is infinitely looping in
  virtscsi_target_destroy().

  2) The loop happens because the 'tgt->reqs' counter is non-zero, and that
  probably happened due to a missing decrement in SCSI command requeue path,
  exercised when the virtio ring is full.

  The reported problem itself happens because of a downstream/SAUCE patch,
  coupled with the problem of the missing decrement for the reqs counter.

  Introducing a decrement in the SCSI command requeue path resolves the
  problem, verified synthetically with QEMU+GDB and with test-case/loop
  provided by the customer as problem reproducer.

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

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

[Kernel-packages] [Bug 1798127] Re: CPU Soft Lockups when stress-ng stack stressor runs with M.2 NVMe as root FS

2018-10-16 Thread Joseph Salisbury

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc8


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

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

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

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

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

** Tags added: kernel-da-key

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

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

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

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

Title:
  CPU Soft Lockups when stress-ng stack stressor runs with M.2 NVMe as
  root FS

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

Bug description:
  This was reported by a hardware partner.  The system set up is a
  server with 512GB RAM and an M.2 NVMe drive as the root
  filesystem/boot device.

  Per the customer, when running the certification Memory Stress test
  (utilizing several stress-ng stressors run in sequence) the system
  freezes with CPU Soft Lockup errors appearing on console whe the
  "stack" stressor is run.

  Tester has tried with 2.5” SATA (1TB), 2.5” NVMe (800GB), and M.2 NVMe
  (1.9TB).

  So far, this only seems to affect the 4.15 kernel.  The tester has
  tried using the 2.5" SATA SSD as the RootFS/Boot device and the tests
  pass on all attempts.  It is ONLY when using the M.2 NVMe as the root
  / boot device that the tests cause a lockup.  The tester is re-trying
  now with the 2.5" NVMe device to see if this only occurs with the M.2
  NVMe.

  The tester has tried this on the following while using the M.2 NVMe as the 
rootFS/Boot device:
  Test run #1 – 16.04.5 at kernel 4.15; Result: Failed stress-ng memory on 
stack stressor
  Test run #2 – 18.04.1 at kernel 4.15; Result: Failed stress-ng memory on 
stack stressor
  Test run #3 – 16.04.5 at kernel 4.4; Result: Passed stress-ng memory test

  
  The stress-ng command invoked at the time the soft lockups occur is this:

  'stress-ng -k --aggressive --verify --timeout 300 --stack 0'

  This can be reproduced by running the memory_stress_ng test script
  from the cert suite:

  sudo /usr/lib/plainbox-provider-certification-
  server/bin/memory_stress_ng

  It may be more easily reproducible running the stack stressor alone,
  or the whole memory stress script without dealing with Checkbox.

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

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

[Kernel-packages] [Bug 1798165] Re: Vulkan applications cause permanent memory leak with Intel GPU

2018-10-16 Thread Joseph Salisbury

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

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

** Also affects: linux (Ubuntu Bionic)
   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/1798165

Title:
  Vulkan applications cause permanent memory leak with Intel GPU

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

Bug description:
  Vulkan applications, as Dota 2 and DXVK games cause a memory leak
  where memory is never freed and can cause a system crash if the
  applications are used for long enough. Certain applications can make
  the leak be as high as 10 MB/minute.

  Details about this bug can be seen at
  https://github.com/doitsujin/dxvk/issues/632 and
  https://bugs.freedesktop.org/show_bug.cgi?id=107899

  This bug was fixed in 4.19-rc6 and was backported to 4.14 and 4.18.
  The particular commit is:

  commit a2cef7d049f07995406b403605119a54881daf15
  Author: Jason Ekstrand 
  Date:   Wed Sep 26 02:17:03 2018 -0500

  drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set
  
  commit 337fe9f5c1e7de1f391c6a692531379d2aa2ee11 upstream.
  
  We attempt to get fences earlier in the hopes that everything will
  already have fences and no callbacks will be needed.  If we do succeed
  in getting a fence, getting one a second time will result in a duplicate
  ref with no unref.  This is causing memory leaks in Vulkan applications
  that create a lot of fences; playing for a few hours can, apparently,
  bring down the system.
  
  Cc: sta...@vger.kernel.org
  Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107899
  Reviewed-by: Chris Wilson 
  Signed-off-by: Jason Ekstrand 
  Signed-off-by: Sean Paul 
  Link: 
https://patchwork.freedesktop.org/patch/msgid/20180926071703.15257-1-jason.ekstr...@intel.com
  Signed-off-by: Greg Kroah-Hartman 

  
  On Ubuntu 18.04 with 4.15.0-36 it appears in slabtop as: 
https://i.imgur.com/qMAvuwl.png

  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:  usuario4655 F pulseaudio
   /dev/snd/seq:usuario4640 F timidity
  CurrentDesktop: XFCE
  Date: Tue Oct 16 14:16:54 2018
  HibernationDevice: RESUME=UUID=0946602f-3ca2-4379-9012-7a5171928de7
  InstallationDate: Installed on 2017-06-13 (489 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 
kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 intel_iommu=on iommu=pt 
i915.enable_gvt=1 i915.fastboot=1 
resume=UUID=0946602f-3ca2-4379-9012-7a5171928de7 mtrr_gran_size=2M 
mtrr_chunk_size=64M cgroup_enable=memory swapaccount=1 zswap.enabled=1 
log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10
  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: Upgraded to bionic on 2017-10-20 (361 days ago)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1798160] Re: Wrong screen refresh AOC G2260VWQ6

2018-10-16 Thread Joseph Salisbury

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc8

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

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

Title:
  Wrong screen refresh AOC G2260VWQ6

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.04
  Screen: AOC G2260VWQ6 FreeSync
  GPU: Radeon R9 380 2GB
  Cable: HDMI

  The monitor supports 75Hz refresh. The system misidentifies the
  monitor. There is no 75Hz option. It's only 60Hz. Under Windows 7
  there was the same problem. The monitor drivers from the AOC website
  solved the problem.

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

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

[Kernel-packages] [Bug 1792580] Re: Mounting SOFS SMB shares fails

2018-10-16 Thread Joseph Salisbury

That is actually good news.  That means the backport of commit
b327a717e50698039 is good.  It also means we are missing a commit in
v4.16-rc1 from Bionic.

Can you confirm v4.16-rc1 does not exhibit the bug:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/

If it is good, I can perform a "Reverse" bisect to identify the missing
commit.

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

Title:
  Mounting SOFS SMB shares fails

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

Bug description:
  Ubuntu 18.04.1 LTS 4.15.0-33.36-generic
  cifs-utils 2:6.8-1

  Mounting scale-out SMB shares is failing.

  mount -t cifs -o 
credentials=/tmp/creds,domain=cbs.com,uid=114,gid=119,vers=3.0,_netdev,nodfs 
//s2dscaleout.cbs.com/glance-images /tmp/test_mount
  mount error(5): Input/output error
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

  What works:
  * mounting the share from a 16.04 host
  * mounting standalone smb3 shares

  Relevant error from the log (full logs attached separately):
  Sep 14 11:12:05 r07-u13 kernel: Status code returned 0xc0c9 
STATUS_NETWORK_NAME_DELETED
  Sep 14 11:12:05 r07-u13 kernel: 
/build/linux-81MBYC/linux-4.15.0/fs/cifs/smb2maperror.c: Mapping SMB2 status 
code 0xc0c9 to POSIX err -5

  Share server os: Windows Server 2016 10.0.14393
  PS C:\Users\jujuadmin> get-smbshare glance-images | fl *

  ShareState: Online
  AvailabilityType  : ScaleOut
  ShareType : FileSystemDirectory
  FolderEnumerationMode : Unrestricted
  CachingMode   : Manual
  SmbInstance   : Default
  CATimeout : 0
  ConcurrentUserLimit   : 0
  ContinuouslyAvailable : True
  CurrentUsers  : 2
  Description   :
  EncryptData   : False
  Name  : glance-images
  Path  : C:\ClusterStorage\Volume1\GLANCE-IMAGES
  Scoped: True
  ScopeName : S2DSCALEOUT
  ShadowCopy: False
  Special   : False
  Temporary : False
  Volume: \\?\Volume{5faf880d-d308-4058-9ec2-d19d48089495}\
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep  7 16:51 seq
   crw-rw 1 root audio 116, 33 Sep  7 16:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R710
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=ba74e4cf-9634-4049-abd8-0ed721836a41 ro
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-33-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: False
  dmi.bios.date: 07/23/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 6.4.0
  dmi.board.name: 0YDJK3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A14
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr6.4.0:bd07/23/2013:svnDellInc.:pnPowerEdgeR710:pvr:rvnDellInc.:rn0YDJK3:rvrA14:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R710
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

2018-10-16 Thread Joseph Salisbury

** Description changed:

-
== SRU Justification ==
IBM is requesting these commits in bionic and cosmic. These commits
- also rely on commit 7acf50e4efa6, which was SRU'd in bug 1792102. The
- first patch, commit 2bf1071a8d50, was backported by IBM themself.
+ also rely on commit 7acf50e4efa6, which was SRU'd in bug 1792102.

Description of bug:
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.

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.

-
== Fixes ==
- 2bf1071a8d50 ("powerpc/64s: Remove POWER9 DD1 support")
bd0dbb73e013 ("powerpc/mm/books3s: Add new pte bit to mark pte temporarily
invalid.")
f08d08f3db55 ("powerpc/mm/radix: Only need the Nest MMU workaround for R ->
RW transition")
-

== Regression Potential ==
Low. Limited to powerpc.

== Test Case ==
A test kernel was built with these patches and tested by IBM.
IBM states the test kernel resolved the bug.
-

-- 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?

--
You 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
Status in linux source package in Cosmic:
In Progress

Bug description:
== SRU Justification ==
IBM is requesting these commits in bionic and cosmic. These commits
also rely on commit 7acf50e4efa6, which was SRU'd in bug 1792102.

[Kernel-packages] [Bug 1797963] Re: not able to unwind the stack from within __kernel_clock_gettime in the Linux vDSO

2018-10-16 Thread Joseph Salisbury

SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-October/096068.html

** Description changed:

- Description
+ == SRU Justification ==
+ IBM is requesting this commit in Bionic and Cosmic.  They report that they
+ are not able to unwind the stack from within __kernel_clock_gettime in the
+ Linux vDSO on Summit. This affects both DDT and MAP (via GDB and libunwind).
+ The issue is more serious than may first appear as the function appears to
+ be called somewhat often by the CUDA runtime, and can defer to a syscall
+ making it relatively time consuming (making it more likely to be encountered).
+ 
+ This commit is currently still in linux-next.
+ 
+ == Fix ==
+ 56d20861c027 ("powerpc/vdso: Correct call frame information") linux-next
+ 
+ == Regression Potential ==
+ Low.  Limited to powerpc.
+ 
+ 
+ 
+ 
+ 
+ 
+ Original Bug Description
  
  We're not able to unwind the stack from within __kernel_clock_gettime in
  the Linux vDSO on Summit. This affects both DDT and MAP (via GDB and
  libunwind). The issue is more serious than may first appear as the
  function appears to be called somewhat often by the CUDA runtime, and
  can defer to a syscall making it relatively time consuming (making it
  more likely to be encountered).
  
  To reproduce:
  
  Compile $CUDA_DIR/samples/0_Simple/matrixMul (attached is a small patch
  to modify the Makefile to compile outside of the samples directory)
  
  Run the following GDB commands:
- user@deb3qwsp1:/usr/local/cuda-10.0/samples/0_Simple/matrixMul$ gdb 
./matrixMul 
+ user@deb3qwsp1:/usr/local/cuda-10.0/samples/0_Simple/matrixMul$ gdb 
./matrixMul
  GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
  Copyright (C) 2018 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-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ./matrixMul...(no debugging symbols found)...done.
  (gdb) break main
  Breakpoint 1 at 0x8284
  (gdb) run
- Starting program: /usr/local/cuda-10.0/samples/0_Simple/matrixMul/matrixMul 
+ Starting program: /usr/local/cuda-10.0/samples/0_Simple/matrixMul/matrixMul
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library 
"/lib/powerpc64le-linux-gnu/libthread_db.so.1".
  
  Breakpoint 1, 0x00018284 in main ()
  (gdb) break *(__kernel_clock_gettime+144)
  Breakpoint 2 at 0x77f805e4: file 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S, 
line 127.
  (gdb) continue
  Continuing.
  [Matrix Multiply Using CUDA] - Starting...
  
  Breakpoint 2, __kernel_clock_gettime () at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:127
  127   
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S: No 
such file or directory.
  (gdb) bt
  #0  __kernel_clock_gettime () at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:127
  #1  0x77b8f530 in ?? () from /lib/powerpc64le-linux-gnu/libc.so.6
  #2  0x76b81118 in ?? () from 
/usr/lib/powerpc64le-linux-gnu/libcuda.so.1
  #3  0x76a69c70 in ?? () from 
/usr/lib/powerpc64le-linux-gnu/libcuda.so.1
  #4  0x76bf0ba0 in cuInit () from 
/usr/lib/powerpc64le-linux-gnu/libcuda.so.1
  #5  0x00010003ca50 in cudart::__loadDriverInternalUtil() ()
  #6  0x77f05274 in __pthread_once_slow (
- once_control=0x1000c00f0 
, 
- init_routine=0x10003c950 ) at 
pthread_once.c:116
+ once_control=0x1000c00f0 
,
+ init_routine=0x10003c950 ) at 
pthread_once.c:116
  #7  0x00010008ea88 in cudart::cuosOnce(int*, void (*)()) ()
  #8  0x0001000410a8 in cudart::globalState::initializeDriver() ()
  #9  0x00010005ec90 in cudaGetDeviceCount ()
  #10 0x00019930 in gpuGetMaxGflopsDeviceId() ()
  #11 0x00019bf4 in findCudaDevice(int, char const**) ()
  #12 0x0001836c in main ()
  (gdb) step
  128   in 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S
  (gdb) bt
  #0  __kernel_clock_gettime () at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:128
  #1  0x in ?? ()
- (gdb) 
+ (gdb)
  
- 
- Note: __kernel_clock_gettime+144 is currently the point in the function at 
which the syscall made, and is liable to change if updated. It corresponds to 
the "sc" instruction here:

[Kernel-packages] [Bug 1797963] Re: not able to unwind the stack from within __kernel_clock_gettime in the Linux vDSO

2018-10-15 Thread Joseph Salisbury

I built a test kernel with linux-next commit 56d20861c027.  The test kernel can 
be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1797963

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

Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the 
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the 
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.

Thanks in advance!

** Also affects: linux (Ubuntu Cosmic)
   Importance: High
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: New

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

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

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

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

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

** Changed in: linux (Ubuntu Cosmic)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph 
Salisbury (jsalisbury)

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

Title:
  not able to unwind the stack from within __kernel_clock_gettime in the
  Linux vDSO

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

Bug description:
  Description

  We're not able to unwind the stack from within __kernel_clock_gettime
  in the Linux vDSO on Summit. This affects both DDT and MAP (via GDB
  and libunwind). The issue is more serious than may first appear as the
  function appears to be called somewhat often by the CUDA runtime, and
  can defer to a syscall making it relatively time consuming (making it
  more likely to be encountered).

  To reproduce:

  Compile $CUDA_DIR/samples/0_Simple/matrixMul (attached is a small
  patch to modify the Makefile to compile outside of the samples
  directory)

  Run the following GDB commands:
  user@deb3qwsp1:/usr/local/cuda-10.0/samples/0_Simple/matrixMul$ gdb 
./matrixMul 
  GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
  Copyright (C) 2018 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
  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-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  <http://www.gnu.org/software/gdb/bugs/>.
  Find the GDB manual and other documentation resources online at:
  <http://www.gnu.org/software/gdb/documentation/>.
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ./matrixMul...(no debugging symbols found)...done.
  (gdb) break main
  Breakpoint 1 at 0x8284
  (gdb) run
  Starting program: /usr/local/cuda-10.0/samples/0_Simple/matrixMul/matrixMul 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library 
"/lib/powerpc64le-linux-gnu/libthread_db.so.1".

  Breakpoint 1, 0x00018284 in main ()
  (gdb) break *(__kernel_clock_gettime+144)
  Breakpoint 2 at 0x77f805e4: file 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S, 
line 127.
  (gdb) continue
  Continuing.
  [Matrix Multiply Using CUDA] - Starting...

  Breakpoint 2, __kernel_clock_gettime () at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:127
  127   
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S: No 
such file or directory.
  (gdb) bt
  #0  __kernel_clock_gettime () at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:127
  #1  0x77b8f530 in ?? () from /lib/powerpc64le-linux-gnu/libc.so.6
  #2  0x76b81118 in ?? () from 
/usr/lib/powerpc64le-linux-gnu/libcuda.so.1
  #3  0x76a69c70 in ?? () from 
/usr/lib/powerpc64le-linux-gnu/libcuda.so.1
  #4  0x76bf0ba0 in cuInit () from 
/usr/lib/powerpc64le-linux-gnu/libcuda.so.1
  #5  0x00010003ca50 in cudart::__loadDriverInternalUtil() ()
  #6  0x77f05274 in __pthread_once_slow (
  once_control=0x1000c00f0 
, 
  init_routine=0x10003c950 ) at 
pthread_once.c:116
  #7  0x00010008ea88 in cudart::cuosOnce(int*, void (*)()) ()
  #8  0x0001000410a8 in cudart::globalState::initializeDriver() ()
  #9  0x00010005ec90 in cudaGetDeviceCount ()

[Kernel-packages] [Bug 1797963] Re: not able to unwind the stack from within __kernel_clock_gettime in the Linux vDSO

2018-10-15 Thread Joseph Salisbury

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

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

Title:
  not able to unwind the stack from within __kernel_clock_gettime in the
  Linux vDSO

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Description

  We're not able to unwind the stack from within __kernel_clock_gettime
  in the Linux vDSO on Summit. This affects both DDT and MAP (via GDB
  and libunwind). The issue is more serious than may first appear as the
  function appears to be called somewhat often by the CUDA runtime, and
  can defer to a syscall making it relatively time consuming (making it
  more likely to be encountered).

  To reproduce:

  Compile $CUDA_DIR/samples/0_Simple/matrixMul (attached is a small
  patch to modify the Makefile to compile outside of the samples
  directory)

  Run the following GDB commands:
  user@deb3qwsp1:/usr/local/cuda-10.0/samples/0_Simple/matrixMul$ gdb 
./matrixMul 
  GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
  Copyright (C) 2018 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-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ./matrixMul...(no debugging symbols found)...done.
  (gdb) break main
  Breakpoint 1 at 0x8284
  (gdb) run
  Starting program: /usr/local/cuda-10.0/samples/0_Simple/matrixMul/matrixMul 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library 
"/lib/powerpc64le-linux-gnu/libthread_db.so.1".

  Breakpoint 1, 0x00018284 in main ()
  (gdb) break *(__kernel_clock_gettime+144)
  Breakpoint 2 at 0x77f805e4: file 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S, 
line 127.
  (gdb) continue
  Continuing.
  [Matrix Multiply Using CUDA] - Starting...

  Breakpoint 2, __kernel_clock_gettime () at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:127
  127   
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S: No 
such file or directory.
  (gdb) bt
  #0  __kernel_clock_gettime () at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:127
  #1  0x77b8f530 in ?? () from /lib/powerpc64le-linux-gnu/libc.so.6
  #2  0x76b81118 in ?? () from 
/usr/lib/powerpc64le-linux-gnu/libcuda.so.1
  #3  0x76a69c70 in ?? () from 
/usr/lib/powerpc64le-linux-gnu/libcuda.so.1
  #4  0x76bf0ba0 in cuInit () from 
/usr/lib/powerpc64le-linux-gnu/libcuda.so.1
  #5  0x00010003ca50 in cudart::__loadDriverInternalUtil() ()
  #6  0x77f05274 in __pthread_once_slow (
  once_control=0x1000c00f0 
, 
  init_routine=0x10003c950 ) at 
pthread_once.c:116
  #7  0x00010008ea88 in cudart::cuosOnce(int*, void (*)()) ()
  #8  0x0001000410a8 in cudart::globalState::initializeDriver() ()
  #9  0x00010005ec90 in cudaGetDeviceCount ()
  #10 0x00019930 in gpuGetMaxGflopsDeviceId() ()
  #11 0x00019bf4 in findCudaDevice(int, char const**) ()
  #12 0x0001836c in main ()
  (gdb) step
  128   in 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S
  (gdb) bt
  #0  __kernel_clock_gettime () at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:128
  #1  0x in ?? ()
  (gdb) 

  
  Note: __kernel_clock_gettime+144 is currently the point in the function at 
which the syscall made, and is liable to change if updated. It corresponds to 
the "sc" instruction here: 
https://gitlab.com/TeeFirefly/linux-kernel/blob/7408b38cfdf9b0c6c3bda97402c75bd27ef69a85/arch/powerpc/kernel/vdso64/gettimeofday.S#L127
 and can be rediscovered if needed by disassembling the function.

  Note that a backtrace can be collected before entering the syscall,
  but not during. The inability to unwind also prevents GDB from being
  able to "finish" (step out of) the function:

  (gdb) finish
  Run till exit from #0  __kernel_clock_gettime ()
  at 
/build/linux-ZIBxfV/linux-4.15.0/arch/powerpc/kernel/vdso64/gettimeofday.S:128
  Warning:
  Cannot insert breakpoint 0.
  Cannot access memory at address 0x0

  Command aborted.
  (gdb)

  
  The cause of the issue is a lack of Call Frame Information (CFI) in the 
syscall code path, and so a

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

2018-10-15 Thread Joseph Salisbury

I built another test kernel, without commit 2bf1071a8d5. This test
kernel has the three commit:

7acf50e4efa6 ("Revert "powerpc/powernv: Increase memory block size to 1GB on
radix"")
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.")

The test kernel can be downloaded from:
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

Bug description:

== SRU Justification ==
IBM is requesting these commits in bionic and cosmic. These commits
also rely on commit 7acf50e4efa6, which was SRU'd in bug 1792102. The
first patch, commit 2bf1071a8d50, was backported by IBM themself.

== Fixes ==
2bf1071a8d50 ("powerpc/64s: Remove POWER9 DD1 support")
bd0dbb73e013 ("powerpc/mm/books3s: Add new pte bit to mark pte temporarily
invalid.")
f08d08f3db55 ("powerpc/mm/radix: Only need the Nest MMU workaround for R ->
RW transition")

== Regression Potential ==
Low. Limited to powerpc.

== Test Case ==
A test kernel was built with these patches and tested by IBM.
IBM states the test kernel resolved the bug.

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 1797802] Re: Erratic behavior of intel pstate CPU frequency control

2018-10-15 Thread Joseph Salisbury

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

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

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

Title:
  Erratic behavior of intel pstate CPU frequency control

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I noticed that sometimes my Ubuntu 18.10 system feels sluggish. The
  other times everything works fine. I don't know what triggers this
  weird state. Suspend / resume? Maybe.

  At first I thought this was maybe just a "perception issue", but then
  when the sluggishness happened again, I fired up i7z and it looks that
  CPU frequency almost never got over ~1600 MHz, But my CPU is perfectly
  capable of going up to 4000 MHz!

  I tried to fix it by setting 
  echo 80 > /sys/devices/system/cpu/intel_pstate/min_perf_pct
  echo 80 > /sys/devices/system/cpu/intel_pstate/max_perf_pct

  I hoped I would force the CPU into almost max performance state this
  way. And indeed, once I ran these commands, i7z showed steady 3100+
  MHz on all cores.

  Then something weird happened - when I run some mild load on the CPU,
  like just starting the IDE, during the startup the frequency **
  dropped back to about 800-1600 MHz ** and returned to 3100 MHz after
  the load was gone (IDE loaded).

  The CPU core temperatures shown by sensors / i7z are ok and typically
  at about 40-50 C when this slowdown happens, so this doesn't look like
  thermal throttling.

  Any ideas?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pkolaczk   3281 F pulseaudio
   /dev/snd/pcmC0D0c:   pkolaczk   3281 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 22:16:50 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=4836842e-0116-43c4-98b4-7a56427f81f1
  InstallationDate: Installed on 2017-04-12 (549 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Precision 5520
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=7f76b1f0-8fef-41cc-86a2-99e554cb4d40 ro acpi_rev_override quiet 
splash iwlwifi.power_save=1 crashkernel=384M-:128M crashkernel=384M-:128M 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 06X96V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd07/24/2018:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.product.sku: 07BF
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1797772] Re: ideapad_laptop disables WiFi/BT radios on Lenovo Y530

2018-10-15 Thread Joseph Salisbury

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc8


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

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

** Tags added: cosmic kernel-da-key

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

Title:
  ideapad_laptop disables WiFi/BT radios on Lenovo Y530

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been working with a user that has a Lenovo Legion Y530-15ICH
  where booting Ubuntu 18.10 (kernel 4.18.0-8) results in the radios
  being disabled by the platform driver "ideapad-laptop".

  Unloading or blacklisting the module solves the issue but disables
  other platform ACPI interfaces:

  $ sudo tee /etc/modprobe.d/ideapad.conf <<< "blacklist ideapad_laptop"

  The system has the most recent firmware:

  [0.00] DMI: LENOVO 81FV/LNVNB161216, BIOS 8JCN44WW 08/13/2018

  The wifi device is:

  00:14.3 Network controller [0280]: Intel Corporation Wireless-AC 9560 
[Jefferson Peak] [8086:a370] (rev 10)
   Subsystem: Intel Corporation Wireless-AC 9560 [Jefferson Peak] [8086:0034]
   Kernel driver in use: iwlwifi

  We investigated the issue extensively and built the module with
  additional logic without solving the issue. It is well-known that some
  Lenovo models do not have a separate hardware radio kill switch (this
  model uses hot-keys Fn + F7 for 'Airplane mode') and need to use a DMI
  match to disable the rfkill logic.

  We used dmidecode to get the correct Version string:

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: LENOVO
   Product Name: 81FV
   Version: Lenovo Legion Y530-15ICH
   Serial Number: PF18CD10
   UUID: A44F71C1-5E3D-11E8-9379-8C16458E3F9D
   Wake-up Type: Power Switch
   SKU Number: LENOVO_MT_81FV_BU_idea_FM_Legion Y530-15ICH
   Family: Legion Y530-15ICH

  and added it to no_hw_rfkill_list[]:

  {
  .ident = "Lenovo Legion Y530-15ICH",
  .matches = {
  DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
  DMI_MATCH(DMI_PRODUCT_VERSION, "Lenovo Legion Y530-15ICH"),
  },
  },

  However, rfkill was still listing the platform devices "ideapad_wlan"
  and "ideapad_bluetooth":

  0: ideapad_wlan: Wireless LAN
   Soft blocked: no
   Hard blocked: yes
  1: ideapad_bluetooth: Bluetooth
   Soft blocked: yes
   Hard blocked: yes
  3: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no
  4: hci0: Bluetooth
   Soft blocked: yes
   Hard blocked: no

  /sys/class/rfkill/rfkill0/hard=1
  /sys/class/rfkill/rfkill0/index=0
  /sys/class/rfkill/rfkill0/name=ideapad_wlan
  /sys/class/rfkill/rfkill0/persistent=1
  /sys/class/rfkill/rfkill0/soft=0
  /sys/class/rfkill/rfkill0/state=2
  /sys/class/rfkill/rfkill0/type=wlan
  /sys/class/rfkill/rfkill0/uevent=RFKILL_NAME=ideapad_wlan RFKILL_TYPE=wlan 
RFKILL_STATE=2
  /sys/class/rfkill/rfkill1/hard=1
  /sys/class/rfkill/rfkill1/index=1
  /sys/class/rfkill/rfkill1/name=ideapad_bluetooth
  /sys/class/rfkill/rfkill1/persistent=1
  /sys/class/rfkill/rfkill1/soft=1
  /sys/class/rfkill/rfkill1/state=2
  /sys/class/rfkill/rfkill1/type=bluetooth
  /sys/class/rfkill/rfkill1/uevent=RFKILL_NAME=ideapad_bluetooth 
RFKILL_TYPE=bluetooth RFKILL_STATE=2
  /sys/class/rfkill/rfkill3/hard=0
  /sys/class/rfkill/rfkill3/index=3
  /sys/class/rfkill/rfkill3/name=phy0
  /sys/class/rfkill/rfkill3/persistent=0
  /sys/class/rfkill/rfkill3/soft=0
  /sys/class/rfkill/rfkill3/state=1
  /sys/class/rfkill/rfkill3/type=wlan
  /sys/class/rfkill/rfkill3/uevent=RFKILL_NAME=phy0 RFKILL_TYPE=wlan 
RFKILL_STATE=1
  /sys/class/rfkill/rfkill4/hard=0
  /sys/class/rfkill/rfkill4/index=4
  /sys/class/rfkill/rfkill4/name=hci0
  /sys/class/rfkill/rfkill4/persistent=0
  /sys/class/rfkill/rfkill4/soft=1
  /sys/class/rfkill/rfkill4/state=0
  /sys/class/rfkill/rfkill4/type=bluetooth
  /sys/class/rfkill/rfkill4/uevent=RFKILL_NAME=hci0 RFKILL_TYPE=bluetooth 
RFKILL_STATE=0

  We then added printk(KERN_NOTICE ... in the module's
  platform_driver.probe function ideapad_acpi_add() both at entry and
  later to report the DMI and status of the hardware switch control
  flag:

  diff -u 
/home/all/SourceCode/linux/linux/drivers/platform/x86/ideapad-laptop.c 
./ideapad-laptop.c
  ---

[Kernel-packages] [Bug 1797670] Re: upgrading to 16.04 bug

2018-10-15 Thread Joseph Salisbury

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"


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

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

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

Title:
  upgrading to 16.04 bug

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  lsb_release -rd
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  apt-cache policy pkgname
  N: Unable to locate package pkgname

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-53-generic 3.13.0-53.87
  ProcVersionSignature: Ubuntu 3.13.0-53.87-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  taktak 2369 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Oct 13 05:57:00 2018
  HibernationDevice: RESUME=UUID=e21c4184-fae7-45c6-bc5b-b10babb22ea3
  InstallationDate: Installed on 2012-12-06 (2136 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Vostro 1015
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=1f09aafa-4f9a-489b-9b7a-96d0efa55993 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-53-generic N/A
   linux-backports-modules-3.13.0-53-generic  N/A
   linux-firmware 1.127.11
  SourcePackage: linux
  StagingDrivers: keucr
  UpgradeStatus: Upgraded to trusty on 2018-10-13 (0 days ago)
  WifiSyslog:
   Oct 13 05:52:19 Takostro kernel: [  657.752075] ERROR @wl_dev_intvar_get : 
error (-1)
   Oct 13 05:52:19 Takostro kernel: [  657.752081] ERROR 
@wl_cfg80211_get_tx_power : error (-1)
  dmi.bios.date: 09/17/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 047MWF
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd09/17/2009:svnDellInc.:pnVostro1015:pvr:rvnDellInc.:rn047MWF:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Vostro 1015
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1797669] Re: tc filter add after delete get error "No space left on device"

2018-10-15 Thread Joseph Salisbury

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc8


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

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

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

Title:
  tc filter add after delete get error "No space left on device"

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  tc filter seems still leak with ubuntu kernel 4.15.0-36-generic,
  it can be reproduced with the following steps.

  ```
  tc qdisc add dev eth0 ingress
  tc filter add dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip 
dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1
  tc filter add dev eth0 ingress protocol ip prio 1 handle 800::2 u32 match ip 
dst 192.168.5.46/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1
  tc filter del dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip 
dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1
  tc filter add dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip 
dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1
  ```

  the last command will get this error
  ```
  RTNETLINK answers: No space left on device
  We have an error talking to the kernel
  ```

  upstream 4.15(eol) also have this issue, but 4.16.2 fixed, and ubuntu 
4.15.0-36 already patched upstream 4.16.2 fix patch.
  however this issue still exist, I think the difference between 4.15 and 4.16 
caused this issue.
  please kindly help check it.
  Thanks.

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

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

[Kernel-packages] [Bug 1797628] Re: System hangs during boot at "Started configure plugged in printer"

2018-10-15 Thread Joseph Salisbury

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc8


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

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

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

Title:
  System hangs during boot at "Started configure plugged in printer"

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  System: Lenovo T430s with HP OfficeJet Pro 8600 attached via usb hub

  Followed general bug reporting instructions (including
  https://wiki.ubuntu.com/Bugs/FindRightPackage). This may be kernel
  related, not xorg.

  What I tried: rebooting
  What I expected: to see the login screen
  What happened: booting hangs

  Rebooted using 'E' option in grub to remove splash and quiet. Saw
  system hang at "Started configure plugged in printer"

  When I unplug the USB hub (to which the printer is connected), I can
  reboot and login fine then reinsert USB hub.

  After this "fix," I can reboot fine without unplugging anything. This
  bug appears to happen right after a system update (running Software
  Updater and there are kernel bits to update).

  This is new behaviour; I had the same system setup running and booting
  fine under 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12
  Uname: Linux 4.18.0-9-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 12 15:48:22 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fb]
  InstallationDate: Installed on 2018-10-02 (10 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  MachineType: LENOVO 2356CU8
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-9-generic 
root=UUID=e307efee-e562-4d24-9632-4a97a84073ee ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/22/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ET91WW (2.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2356CU8
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 529944
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG7ET91WW(2.51):bd01/22/2013:svnLENOVO:pn2356CU8:pvrThinkPadT430s:rvnLENOVO:rn2356CU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430s
  dmi.product.name: 2356CU8
  dmi.product.sku: LENOVO_MT_2356
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Kernel-packages] [Bug 1797759] Re: screen goes blank when mate loads - unable to see the login screen

2018-10-15 Thread Joseph Salisbury

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc8


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

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

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

Title:
  screen goes blank when mate loads - unable to see the login screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After a clean install of Ubuntu Mate 18.04.1 LTS 64bit on my laptop HP 
Elitebook 2540p Intel Core i7 CPU 640 @ 2.13GHz x 4 the screen goes blank 
before the login screen appears.
  Kernel Linux 4.15.0-36-generic x86_64.
  It was fine using Ubuntu Mate 16.x.
  I have found by booting to save mode and select boot from HDD everything 
works except the font is a bit large and some screens go off the bottom of the 
screen and I can't view this part of the screen.
  When checking software & updates there are no additional drivers loaded.
  The monitor preferences show monitor is known, resolution is 1280 x 800, 
refresh rates is 0 hz. None of this info can be changed.
  I have run the software update 3-4 times hoping that it would right itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Mon Oct 15 00:25:10 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:7008]
  InstallationDate: Installed on 2018-09-01 (43 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Hewlett-Packard HP EliteBook 2540p
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcEnviron:
   LANGUAGE=en_NZ:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--mate--vg-root ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CSU Ver. F.50
  dmi.board.name: 7008
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 38.34
  dmi.chassis.asset.tag: SGH038PG56
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CSUVer.F.50:bd07/08/2014:svnHewlett-Packard:pnHPEliteBook2540p:pvr:rvnHewlett-Packard:rn7008:rvrKBCVersion38.34:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 2540p
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  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/1797759/+subscriptions

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

[Kernel-packages] [Bug 1797805] Re: After Update to Ubuntu 18.04.1 LTS Libre Base wont open database

2018-10-15 Thread Joseph Salisbury

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

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

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

Title:
  After Update to Ubuntu 18.04.1 LTS Libre Base wont open database

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Hi!

  A few days ago I updaet my System to Ubuntu 18.04.1 LTS.

  Today I found out that I can't open my Libre Base Adress-Database
  anymore.

  1) I start Libre Base.(German Version)
  2) The "Datenank-Assistent" asks me what I want to do. I continue by choosing 
to open my Adress-Database.
  3) The Libre Base Main Window apperas with my Database. At the left side are 
die Options "Tables", "Queries", "Forms" and "Reports". "Forms" is active. 
  4) I choose the only form stored with this database.
  5) Libre-Base crashes and takes all Instances of Libre Writer, etc. with it.
  6) I restart Libre Base. It wants to repair the broken Database. It does so 
succesfully.
  7) Continue with 3)

  My PC:
  CPU: Intel Celeron(r) CPU G1820 @ 2.70GHz x 2
   Grafik: Intel Haswell Desktop x86/MMX/SSE2
  RAM: 7.8 GB
Gnome: 3.28.2
  OS-TYpe: 32-bit
Disks: 1.1 TB

  libreoffice-base:
Installiert:   1:6.0.6-0ubuntu0.18.04.1
Installationskandidat: 1:6.0.6-0ubuntu0.18.04.1
Versionstabelle:
   *** 1:6.0.6-0ubuntu0.18.04.1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/universe i386 
Packages
  100 /var/lib/dpkg/status
   1:6.0.3-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/universe i386 Packages

  
  Best regard

  Wannabe

  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 i686
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  arne   2313 F pulseaudio
   /dev/snd/controlC0:  arne   2313 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 23:20:38 2018
  HibernationDevice: RESUME=UUID=47b31bba-205c-4d51-9e19-dcde4056d0cb
  InstallationDate: Installed on 2014-03-01 (1688 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=UUID=df276a8e-3485-4b48-b073-ebcb6e030df1 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
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-10-10 (4 days ago)
  dmi.bios.date: 12/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0701
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0701:bd12/03/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1797828] Re: Kernel Panic at reboot or shutdown

2018-10-15 Thread Joseph Salisbury

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

** Tags added: kernel-da-key

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

Title:
  Kernel Panic at reboot or shutdown

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I recive a kernel panel error sometimes when i reboot or shutdown my laptop.
   cat /proc/version_signature > version.log
  Ubuntu 4.15.0-36.39-generic 4.15.18

  ---

  [7.644992] [ cut here ]
  [7.644993] sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:1a.7/usb1/1-2/1-2:1.0/media0'
  [7.645012] WARNING: CPU: 1 PID: 302 at 
/build/linux-39dmni/linux-4.15.0/fs/sysfs/dir.c:31 sysfs_warn_dup+0x56/0x70
  [7.645013] Modules linked in: nvidia_uvm(POE) uvcvideo(+) 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 bnep videobuf2_core videodev 
media snd_hda_codec_hdmi snd_hda_codec_idt snd_hda_codec_generic snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep kvm_intel kvm irqbypass snd_pcm 
snd_seq_midi snd_seq_midi_event serio_raw pcmcia snd_rawmidi arc4 iwl3945 
snd_seq iwlegacy snd_seq_device btusb nvidia(POE) btrtl snd_timer btbcm btintel 
mac80211 bluetooth lpc_ich ecdh_generic input_leds yenta_socket pcmcia_rsrc 
tifm_7xx1 pcmcia_core joydev tifm_core snd cfg80211 soundcore drm shpchp 
ip6t_REJECT nf_reject_ipv6 sony_laptop nf_log_ipv6 xt_hl ip6t_rt mac_hid 
nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 
nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 
nf_defrag_ipv4
  [7.645066]  xt_conntrack ip6table_filter ip6_tables 
nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat sch_fq_codel 
nf_conntrack_ftp nf_conntrack libcrc32c coretemp parport_pc iptable_filter 
ppdev lp parport ip_tables x_tables autofs4 uas usb_storage hid_generic usbhid 
hid psmouse ahci libahci firewire_ohci firewire_core pata_acpi crc_itu_t sky2 
video [last unloaded: videobuf2_memops]
  [7.645092] CPU: 1 PID: 302 Comm: systemd-udevd Tainted: P   OE
4.15.0-36-generic #39-Ubuntu
  [7.645093] Hardware name: Sony Corporation VGN-SZ61MN_B/VAIO  
  , BIOS R0122S5 04/04/2008
  [7.645096] RIP: 0010:sysfs_warn_dup+0x56/0x70
  [7.645097] RSP: 0018:ad0d40c0b850 EFLAGS: 00010286
  [7.645099] RAX:  RBX: 94d035d5b000 RCX: 
0006
  [7.645100] RDX: 0007 RSI: 0086 RDI: 
94d03fd16490
  [7.645101] RBP: ad0d40c0b868 R08: 0001 R09: 
03ba
  [7.645102] R10: 0001 R11:  R12: 
94d038909dd8
  [7.645103] R13: 94d0301ff088 R14: 94d038b0f810 R15: 
94d03003c840
  [7.645105] FS:  7f1e1a9b1680() GS:94d03fd0() 
knlGS:
  [7.645107] CS:  0010 DS:  ES:  CR0: 80050033
  [7.645108] CR2: 0210baa8 CR3: 0001340f4000 CR4: 
06e0
  [7.645109] Call Trace:
  [7.645114]  sysfs_create_dir_ns+0x77/0x90
  [7.645118]  kobject_add_internal+0xac/0x2b0
  [7.645119]  kobject_add+0x71/0xd0
  [7.645123]  ? device_private_init+0x23/0x70
  [7.645124]  device_add+0x12c/0x680
  [7.645129]  cdev_device_add+0x4e/0x80
  [7.645130]  ? cdev_init+0x55/0x60
  [7.645136]  media_devnode_register+0xe7/0x180 [media]
  [7.645139]  __media_device_register+0x77/0x110 [media]
  [7.645148]  uvc_probe+0x96f/0xed0 [uvcvideo]
  [7.645150]  ? kernfs_activate+0x78/0x80
  [7.645152]  ? kernfs_add_one+0xe4/0x130
  [7.645155]  usb_probe_interface+0x129/0x300
  [7.645159]  ? uvc_parse_standard_control+0x1400/0x1400 [uvcvideo]
  [7.645161]  ? usb_probe_interface+0x129/0x300
  [7.645163]  driver_probe_device+0x31e/0x490
  [7.645165]  __driver_attach+0xa7/0xf0
  [7.645167]  ? driver_probe_device+0x490/0x490
  [7.645169]  bus_for_each_dev+0x70/0xc0
  [7.645171]  driver_attach+0x1e/0x20
  [7.645172]  bus_add_driver+0x1c7/0x270
  [7.645174]  driver_register+0x60/0xe0
  [7.645176]  usb_register_driver+0x81/0x150
  [7.645178]  ? 0xc151a000
  [7.645179]  ? 0xc151a000
  [7.645183]  uvc_init+0x29/0x1000 [uvcvideo]
  [7.645186]  do_one_initcall+0x52/0x19f
  [7.645189]  ? __vunmap+0x81/0xb0
  [7.645191]  ? _cond_resched+0x19/0x40
  [7.645193]  ? kmem_cache_alloc_trace+0xa6/0x1b0
  [7.645196]  ? do_init_module+0x27/0x209
  [7.645198]  do_init_module+0x5f/0x209
  [7.645200]  load_module+0x191e/0x1f10
  [7.645203]  ? ima_post_read_file+0x96/0xa0
  [7.645206]  SYSC_finit_module+0xfc/0x120
  [7.645208]  ? SYSC_finit_module+0xfc/0x120
  [7.645210]  SyS_finit_module+0xe/0x10
  [7.645212]  do_syscall_64+0x73/0x130
  [7.645214]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [7.645215] RIP:

[Kernel-packages] [Bug 1797867] Re: Fn keys doesn't work completely.I can only use it to control voulume

2018-10-15 Thread Joseph Salisbury

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc8


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

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

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

Title:
  Fn keys doesn't work completely.I can only use it to control voulume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I ran `acpi_listen`.It doesn't output anything when I press a fn key that is 
not F1/F2/F3 (voulume)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  blurhy 2761 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-10 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc.
   Bus 001 Device 003: ID 13d3:5666 IMC Networks
   Bus 001 Device 002: ID 8087:0a2b Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. FX503VD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX503VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX503VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: FX
  dmi.product.name: FX503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  ---

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

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

[Kernel-packages] [Bug 1797881] Re: Display goes blank soon after boot on dell xps13 on linux-image-4.18.0-10-generic

2018-10-15 Thread Joseph Salisbury

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

** Tags added: kernel-da-key

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

Title:
  Display goes blank soon after boot on dell xps13 on linux-
  image-4.18.0-10-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Display goes blank soon after boot on dell xps13 with linux-
  image-4.18.0-10-generic.

  linux-image-4.18.0-7-generic working fine.

  dmesg outputs:
  [drm:intel_dp_start_link_train [i915]] *ERROR* [CONNECTOR:71:eDP-1] Link 
Training failed at link rate = 54, lane count = 4

  probably related to https://patchwork.kernel.org/patch/10633295/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  baz2265 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct 15 14:25:35 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=/dev/mapper/cryptswap1
  InstallationDate: Installed on 2018-03-01 (227 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=/dev/mapper/system-root ro quiet splash crashkernel=384M-:128M vt.handoff=1
  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: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.9.0
  dmi.board.name: 02PG84
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.9.0:bd07/09/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.product.sku: 082A
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1792580] Re: Mounting SOFS SMB shares fails

2018-10-15 Thread Joseph Salisbury

To see if we are missing commits in Bionic, I built a mainline kernel
that was reset to v4.15 and had a pick of commit b327a717e50698039.

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

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

Title:
  Mounting SOFS SMB shares fails

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

Bug description:
  Ubuntu 18.04.1 LTS 4.15.0-33.36-generic
  cifs-utils 2:6.8-1

  Mounting scale-out SMB shares is failing.

  mount -t cifs -o 
credentials=/tmp/creds,domain=cbs.com,uid=114,gid=119,vers=3.0,_netdev,nodfs 
//s2dscaleout.cbs.com/glance-images /tmp/test_mount
  mount error(5): Input/output error
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

  What works:
  * mounting the share from a 16.04 host
  * mounting standalone smb3 shares

  Relevant error from the log (full logs attached separately):
  Sep 14 11:12:05 r07-u13 kernel: Status code returned 0xc0c9 
STATUS_NETWORK_NAME_DELETED
  Sep 14 11:12:05 r07-u13 kernel: 
/build/linux-81MBYC/linux-4.15.0/fs/cifs/smb2maperror.c: Mapping SMB2 status 
code 0xc0c9 to POSIX err -5

  Share server os: Windows Server 2016 10.0.14393
  PS C:\Users\jujuadmin> get-smbshare glance-images | fl *

  ShareState: Online
  AvailabilityType  : ScaleOut
  ShareType : FileSystemDirectory
  FolderEnumerationMode : Unrestricted
  CachingMode   : Manual
  SmbInstance   : Default
  CATimeout : 0
  ConcurrentUserLimit   : 0
  ContinuouslyAvailable : True
  CurrentUsers  : 2
  Description   :
  EncryptData   : False
  Name  : glance-images
  Path  : C:\ClusterStorage\Volume1\GLANCE-IMAGES
  Scoped: True
  ScopeName : S2DSCALEOUT
  ShadowCopy: False
  Special   : False
  Temporary : False
  Volume: \\?\Volume{5faf880d-d308-4058-9ec2-d19d48089495}\
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep  7 16:51 seq
   crw-rw 1 root audio 116, 33 Sep  7 16:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R710
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=ba74e4cf-9634-4049-abd8-0ed721836a41 ro
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-33-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: False
  dmi.bios.date: 07/23/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 6.4.0
  dmi.board.name: 0YDJK3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A14
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr6.4.0:bd07/23/2013:svnDellInc.:pnPowerEdgeR710:pvr:rvnDellInc.:rn0YDJK3:rvrA14:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R710
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1797862] Re: Cannot turn off keyboard backlight

2018-10-15 Thread Joseph Salisbury

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc8


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

** Tags added: kernel-da-key

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

Title:
  Cannot turn off keyboard backlight

Status in linux package in Ubuntu:
  Incomplete
Status in upower package in Ubuntu:
  Incomplete

Bug description:
  /sys/class/leds $ ls
  asus-wireless::airplane  input10::capslock  input10::compose  input10::kana  
input10::numlock  input10::scrolllock  input4::capslock  input4::numlock  
input4::scrolllock  phy0-led

  
  There isn't any asus kbd backlight folder. `xset led off` doesn't work for me.
  And I can only use fn to control volume (f1/f2/f3).

  The leds kills my battery

  
  $ sudo dmidecode -t 1; lsb_release -a

  # dmidecode 3.1
  Getting SMBIOS data from sysfs.
  SMBIOS 3.0.0 present.

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: FX503VD
   Version: 1.0
   Serial Number: H9NRCX00M803374
   UUID: 524E3948-5843-3030-4D38-30373441
   Wake-up Type: Power Switch
   SKU Number:
   Family: FX

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu Cosmic Cuttlefish (development branch)
  Release: 18.10
  Codename: cosmic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 15 17:13:35 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-10-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1b90]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:1b90]
  InstallationDate: Installed on 2018-10-10 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc. 
   Bus 001 Device 003: ID 13d3:5666 IMC Networks 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. FX503VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX503VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX503VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: FX
  dmi.product.name: FX503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A

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

2018-10-15 Thread Joseph Salisbury

I rebuilt the kernel, so they should be there now:
http://kernel.ubuntu.com/~jsalisbury/lp1752961

-- 
You 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 1797837] Re: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence

2018-10-15 Thread Joseph Salisbury

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc8

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

** Tags added: needs-bisect

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

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:
  Incomplete

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/1797837/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-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

2018-10-15 Thread Joseph Salisbury

I built the next test kernel, up to the following commit:
1da9a586a2ed78d0b5fab4c0cc0473b873e48346

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

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1794067] Re: Bug in selinux on ubuntu 16.04 with kernel 4.15.0-34

2018-10-15 Thread Joseph Salisbury

There are a bunch of LSM stacking changes in 4.15.0-16 that may be the
cause.

I built a test kernel with commit f14e289850b3 as the tip. The test kernel can 
be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1794067

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

Title:
  Bug in selinux on ubuntu 16.04 with kernel 4.15.0-34

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

Bug description:
  Hello, just found a bug in selinux.

  Whats going wrong:

  Copy a link with "-a" option while selinux is on.

  steps to reproduce:

  ~$ mkdir -p a/b
  ~$ ln -s b a/c
  ~$ cp -a a b
  cp: failed to restore the default file creation context: Invalid argument

  Results of my investigation:

  The "cp" of coreutils is calling "setfscreatecon (NULL)" to restore
  the default file creation context (coreutils-8.30/src/copy.c:1771) as
  it is stated in the selinux api
  (/libselinux/include/selinux/selinux.h:71).

  As we see in the result of strace below, the kernel returns an -1 on
  try to restore the default file creation context. So in my opinion is
  the bug has to be in the selinux_setprocattr method in the
  security/selinux/hooks.c file.

  Part of "strace cp -a a b"

  lgetxattr("a/c", "security.selinux", "system_u:object_r:user_home_dir_t:s0", 
255) = 37
  readlink("a/c", "b", 2) = 1
  symlink("b", "b/a/c") = 0
  open("/proc/self/task/2136/attr/fscreate", O_RDWR|O_CLOEXEC) = 3
  write(3, NULL, 0) = -1 EINVAL (Invalid argument)
  close(3) = 0
  open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=2995, ...}) = 0
  read(3, "# Locale name alias data base.\n#"..., 4096) = 2995
  read(3, "", 4096) = 0
  close(3)

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

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

[Kernel-packages] [Bug 1792134] Re: Upgrading to 4.15.0-33 caused the system to fail to boot

2018-10-15 Thread Joseph Salisbury

Would it be possible for you to test the proposed kernel and post back if it 
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to 
enable and use -proposed. 

Thank you in advance!

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

Title:
  Upgrading to 4.15.0-33 caused the system to fail to boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A routine upgrade upgraded the kernel to 4.15.0-34 upon which the
  machine would not boot and instead booted to initramfs. Attempts to
  boot into recovery mode resulted in the error "Warning failed to
  connect to lvmetad. Falling back to device scanning."

  Reverting to 4.15.0-33 allowed me to boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  connor 4127 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 12 12:30:06 2018
  HibernationDevice: RESUME=UUID=af5bdbd9-e688-4d55-a263-0d649f9b59d4
  InstallationDate: Installed on 2018-07-23 (51 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20HNS1KE00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset
  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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/20/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET52W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HNS1KE00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET52W(1.30):bd03/20/2018:svnLENOVO:pn20HNS1KE00:pvrThinkPadX270:rvnLENOVO:rn20HNS1KE00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X270
  dmi.product.name: 20HNS1KE00
  dmi.product.version: ThinkPad X270
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-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

2018-10-15 Thread Joseph Salisbury

In regards to commit 2bf1071a8d509:

The SRU team would not like to see such a large portion of code getting
removed after release. One never knows whether there really was nothing
that did not still make use of some parts.

I believe 2bf1071a8d5 is needed as a prereq for f08d08f3db5545. Do you
think 2bf1071a8d5 will be required to resolve this bug? I can
investigate as well to see if f08d08f3db5545 can be backported to not
require 2bf1071a8d5.