[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)

[Kai-Heng Feng]

I don't think the EXT4 issue inside VM is the same as NVMe one.

If you no longer have the issue on host machine, then the fix works.

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lz 1088 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-01-30 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Razer Blade Stealth
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1742789] Re: Xen PV Guest won't boot latest kernel- OSError: [Errno 28] No space left on device

[Michael]

Alright, I'm thinking something else is the issue, since after manually
installing 4.4.117 it also boots?

4.4.117 http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.117/

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

Title:
  Xen PV Guest won't boot latest kernel- OSError: [Errno 28] No space
  left on device

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  # lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  
  This problem is related to the latest kernel for meltdown spectre patches for 
xen pv guest and pygrub.

  This is the kernel that was attempting to be upgraded.
  linux-image-4.4.0-109-generic   4.4.0-109.132 

  
  I tried to report this issue with the following command but it failed:

  
  ubuntu-bug linux



  *** Collecting problem information



  The collected information can be sent to the developers to improve the

  application. This might take a few minutes.

  ...



  *** Problem in linux-image-4.4.0-15-generic



  The problem cannot be reported:



  This is not an official Ubuntu package. Please remove any third party
  package and try again.



  Press any key to continue...



  No pending crash reports. Try --help for more information.

  


  I have an Ubuntu 14.04 running Xen and a VM running Ubuntu 16.04 LTS
  that I'm having issues with it booting after upgrading the kernel for
  meltdown and spectre vulnerability.

  
  sudo apt-get update
  sudo apt-get upgrade
  sudo apt-get dist-upgrade
  

  Ubuntu 14.04 xen host reboot failure log:
  
  $ tailf /var/log/xen/servername.log
  Domain 24 needs to be cleaned up: destroying the domain
  Done. Rebooting now
  libxl: error: libxl_bootloader.c:628:bootloader_finished: bootloader failed - 
consult logfile /var/log/xen/bootloader.27.log
  libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: bootloader [-1] 
exited with error status 1
  libxl: error: libxl_create.c:1024:domcreate_rebuild_done: cannot (re-)build 
domain: -3
  

  
  
  cat /var/log/xen/bootloader.27.log
  Using  to parse /grub/grub.cfg
pyGRUB  version 0.6
   ┌┐
   │ Ubuntu │
   │ Ubuntu, with Linux 4.4.0-109-generic   │
   │ Ubuntu, with Linux 4.4.0-109-generic (recovery mode)   │
   │ Ubuntu, with Linux 4.4.0-108-generic   │
   │ Ubuntu, with Linux 4.4.0-108-generic (recovery mode)   │
   │ Ubuntu, with Linux 4.4.0-104-generic   │
   │ Ubuntu, with Linux 4.4.0-104-generic (recovery mode)   │
   │ Ubuntu, with Linux 4.4.0-15-generic│
   └┘
  Use the ^ and ┴ keys to select which entry is highlighted.
  Press enter to boot the selected OS, 'e' to edit the
  commands before booting, 'a' to modify the kernel arguments
  before booting, or 'c' for a command line.

  Traceback (most recent call last):
File "/usr/lib/xen-4.4/bin/pygrub", line 905, in 
  os.write(fd, ostring)
  OSError: [Errno 28] No space left on device
  

  I was able to get the vm to boot only by rapidly attempt to access the
  menu options and boot the old kernel (4.4.0-15-generic). Disk space
  and inodes seems fine on the host Ubuntu 14.04LTS and Ubuntu 16.04LTS
  Guest.

  Ubuntu 14.04 Host:
  
  root@host:/var/log/xen# df -hFilesystem  Size  Used Avail Use% Mounted on
  udev197M   12K  197M   1% /dev
  tmpfs42M  1.1M   41M   3% /run
  /dev/dm-0   104G   49G   50G  50% /
  none4.0K 0  4.0K   0% /sys/fs/cgroup
  none5.0M 0  5.0M   0% /run/lock
  none208M 0  208M   0% /run/shm
  none100M 0  100M   0% /run/user
  /dev/sda1   236M   40M  184M  18% /boot
  root@host:/var/log/xen# df -hi
  Filesystem Inodes IUsed IFree IUse% Mounted on
  udev  50K   721   49K2% /dev
  tmpfs 52K   849   52K2% /run
  /dev/dm-06.6M   86K  6.5M2% /
  none  52K 2   52K1% /sys/fs/cgroup
  none  52K 5   52K1% /run/lock
  none  52K 1   52K1% /run/shm
  none  52K 2   52K1% /run/user
  /dev/sda1 61K   298   61K1% /boot
  root@host:/var/log/xen#
  

  Ubuntu 16.04 PV Guest:
  
  root@guest:~# df -hFilesystemSize  Used Avail 
Use% Mounted on
  udev  950M 0  950M   0% /dev
  tmpfs 200M  3.1M  197M   2% /run
  /dev/mapper/guest--vg-root  47G  4.3G   40G  10% /
  tmpfs  

[Kernel-packages] [Bug 1742789] Re: Xen PV Guest won't boot latest kernel- OSError: [Errno 28] No space left on device

[Michael]

Yes, when I select 4.4.0-15 from the GRUB menu it boots.

I tested the requested upstream kernels:
4.4.6: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.6-wily/
4.4.15: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.15/
4.4.50: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.50/

All of these upstream kernels worked.

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

Title:
  Xen PV Guest won't boot latest kernel- OSError: [Errno 28] No space
  left on device

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  # lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  
  This problem is related to the latest kernel for meltdown spectre patches for 
xen pv guest and pygrub.

  This is the kernel that was attempting to be upgraded.
  linux-image-4.4.0-109-generic   4.4.0-109.132 

  
  I tried to report this issue with the following command but it failed:

  
  ubuntu-bug linux



  *** Collecting problem information



  The collected information can be sent to the developers to improve the

  application. This might take a few minutes.

  ...



  *** Problem in linux-image-4.4.0-15-generic



  The problem cannot be reported:



  This is not an official Ubuntu package. Please remove any third party
  package and try again.



  Press any key to continue...



  No pending crash reports. Try --help for more information.

  


  I have an Ubuntu 14.04 running Xen and a VM running Ubuntu 16.04 LTS
  that I'm having issues with it booting after upgrading the kernel for
  meltdown and spectre vulnerability.

  
  sudo apt-get update
  sudo apt-get upgrade
  sudo apt-get dist-upgrade
  

  Ubuntu 14.04 xen host reboot failure log:
  
  $ tailf /var/log/xen/servername.log
  Domain 24 needs to be cleaned up: destroying the domain
  Done. Rebooting now
  libxl: error: libxl_bootloader.c:628:bootloader_finished: bootloader failed - 
consult logfile /var/log/xen/bootloader.27.log
  libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: bootloader [-1] 
exited with error status 1
  libxl: error: libxl_create.c:1024:domcreate_rebuild_done: cannot (re-)build 
domain: -3
  

  
  
  cat /var/log/xen/bootloader.27.log
  Using  to parse /grub/grub.cfg
pyGRUB  version 0.6
   ┌┐
   │ Ubuntu │
   │ Ubuntu, with Linux 4.4.0-109-generic   │
   │ Ubuntu, with Linux 4.4.0-109-generic (recovery mode)   │
   │ Ubuntu, with Linux 4.4.0-108-generic   │
   │ Ubuntu, with Linux 4.4.0-108-generic (recovery mode)   │
   │ Ubuntu, with Linux 4.4.0-104-generic   │
   │ Ubuntu, with Linux 4.4.0-104-generic (recovery mode)   │
   │ Ubuntu, with Linux 4.4.0-15-generic│
   └┘
  Use the ^ and ┴ keys to select which entry is highlighted.
  Press enter to boot the selected OS, 'e' to edit the
  commands before booting, 'a' to modify the kernel arguments
  before booting, or 'c' for a command line.

  Traceback (most recent call last):
File "/usr/lib/xen-4.4/bin/pygrub", line 905, in 
  os.write(fd, ostring)
  OSError: [Errno 28] No space left on device
  

  I was able to get the vm to boot only by rapidly attempt to access the
  menu options and boot the old kernel (4.4.0-15-generic). Disk space
  and inodes seems fine on the host Ubuntu 14.04LTS and Ubuntu 16.04LTS
  Guest.

  Ubuntu 14.04 Host:
  
  root@host:/var/log/xen# df -hFilesystem  Size  Used Avail Use% Mounted on
  udev197M   12K  197M   1% /dev
  tmpfs42M  1.1M   41M   3% /run
  /dev/dm-0   104G   49G   50G  50% /
  none4.0K 0  4.0K   0% /sys/fs/cgroup
  none5.0M 0  5.0M   0% /run/lock
  none208M 0  208M   0% /run/shm
  none100M 0  100M   0% /run/user
  /dev/sda1   236M   40M  184M  18% /boot
  root@host:/var/log/xen# df -hi
  Filesystem Inodes IUsed IFree IUse% Mounted on
  udev  50K   721   49K2% /dev
  tmpfs 52K   849   52K2% /run
  /dev/dm-06.6M   86K  6.5M2% /
  none  52K 2   52K1% /sys/fs/cgroup
  none  52K 5   52K1% /run/lock
  none  52K 1   52K1% /run/shm
  none  52K 2   52K1% /run/user
  /dev/sda1 61K   298   61K1% /boot
  root@host:/var/log/xen#
  

  Ubuntu 16.04 PV Guest:
  
  root@guest:~# df -hFilesystemSize  Used Avail 
Use% Mounted on
  udev  950M 0  

[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13

[Dr. Jens Harbott]

After running for a couple of days, it seems that we are still seeing
the slow memory leak similar to what was noticed in >= 4.14 earlier with
the patched kernel. But it won't be possible for me to bisect at that
rate.

@Joseph: Getting a patched current 4.13 still would be nice, getting
instructions for how to build such a kernel would be even nicer.

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

Title:
  Servers going OOM after updating kernel from 4.10 to 4.13

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

Bug description:
  We are seeing this on multiple servers after upgrading from previous
  4.10 series HWE kernels to the new 4.13 HWE series. With the new
  kernel, free memory is continously decreasing at a high rate and the
  servers start swapping and finally OOMing services within days. With
  the 4.10 kernel, decrease of free memory is slower and stabilizes
  after a while.

  Latest kernel tested is linux-image-4.13.0-32-generic but the issue
  also affects older kernels from that series, tested back to linux-
  image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic.

  The servers are running as OpenStack controller nodes using either
  Ocata or Pike UCA plus ceph. See attached graph for the memory
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Feb  9 09:45:50 2018
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1714485] Re: Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.

[Thadeu Lima de Souza Cascardo]

Should already be fixed in bionic. If we backport the bionic package to
xenial, we will get this working as well.

Cascardo.

** Changed in: makedumpfile (Ubuntu Bionic)
   Status: In Progress => Fix Released

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

Title:
  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Zesty:
  Won't Fix
Status in makedumpfile source package in Artful:
  New
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 ==
  ---Problem Description---

  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

  ---Steps to Reproduce---

  1. Install Ubuntu 16.04.03 with / as xfs.
  2. Configure kdump.
  3. trigger crash.

  Machine hangs after below log. Attaching console log.

  [  OK  ] Reached target Network is Online.
   Starting Kernel crash dump capture service...
   Starting iSCSI initiator daemon (iscsid)...
  [   12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: 
unexpected operator
  [  OK  ] Started Kernel crash dump capture service.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).

  
  4. After manual reboot  /etc/default/kdump-tools is empty.

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

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

[Kernel-packages] [Bug 1745104] Re: ISST-LTE: KVM:UBUNTU1804: kdump is not working on UbuntuKVM guest

[Joseph Salisbury]

** Changed in: linux (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-power-systems
   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/1745104

Title:
  ISST-LTE: KVM:UBUNTU1804: kdump is not working on UbuntuKVM  guest

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

Bug description:
  == Comment: #0 - Chanh H. Nguyen  - 2018-01-23 14:55:05 
==
  root@boslcp4g5:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Bionic Beaver (development branch)"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic
  root@boslcp4g5:~# uname -r
  4.13.0-25-generic
  root@boslcp4g5:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-25-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.13.0-25-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.13.0-25-generic 
root=UUID=8a776bc5-d9e0-4a1d-9218-135f9c702e11 ro splash quiet nr_cpus=1 
systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@boslcp4g5:~# kdump-config status
  current state   : ready to kdump
  root@boslcp4g5:~# echo c > /proc/sysrq-trigger
  [  176.911191] sysrq: SysRq : This sysrq operation is disabled.
  root@boslcp4g5:~# sysctl -w kernel.sysrq=1
  kernel.sysrq = 1
  root@boslcp4g5:~# echo c > /proc/sysrq-trigger
  [  240.304466] sysrq: SysRq : Trigger a crash
  [  240.304545] Unable to handle kernel paging request for data at address 
0x
  [  240.304656] Faulting instruction address: 0xc0792f88
  [  240.304771] Oops: Kernel access of bad area, sig: 11 [#1]
  [  240.304846] SMP NR_CPUS=2048
  [  240.304848] NUMA
  [  240.304903] pSeries
  [  240.305000] Modules linked in: sctp_diag sctp libcrc32c dccp_diag dccp 
tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag netlink_diag 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache dm_service_time 
vmx_crypto crct10dif_vpmsum binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc 
scsi_dh_alua sunrpc sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq 
crc32c_vpmsum virtio_net virtio_scsi
  [  240.305776] CPU: 12 PID: 1860 Comm: bash Not tainted 4.13.0-25-generic 
#29-Ubuntu
  [  240.305886] task: c000ff904500 task.stack: c001f2d7c000
  [  240.305979] NIP: c0792f88 LR: c0793eb8 CTR: 
c0792f60
  [  240.306087] REGS: c001f2d7f9f0 TRAP: 0300   Not tainted  
(4.13.0-25-generic)
  [  240.306195] MSR: 80009033 
  [  240.306207]   CR: 2842  XER: 2004
  [  240.306338] CFAR: c0793eb4 DAR:  DSISR: 4200 
SOFTE: 1
  [  240.306338] GPR00: c0793eb8 c001f2d7fc70 c15f6200 
0063
  [  240.306338] GPR04: c001feeeade8 c001fef02068 6967676572206120 
63726173680d0a72
  [  240.306338] GPR08: 0007 0001  

  [  240.306338] GPR12: c0792f60 c7ac7e00 10180df8 
10189e30
  [  240.306338] GPR16: 10189ea8 10151210 1018bd58 
1018de48
  [  240.306338] GPR20: 28bc0268 0001 10164590 
10163bb0
  [  240.306338] GPR24: 7fffdcb37d34 7fffdcb37d30 c14fa770 
0002
  [  240.306338] GPR28: 0063 0007 c14824f4 
c14fab10
  [  240.307346] NIP [c0792f88] sysrq_handle_crash+0x28/0x30
  [  240.307474] LR [c0793eb8] __handle_sysrq+0xf8/0x2b0
  [  240.307553] Call Trace:
  [  240.307594] [c001f2d7fc70] [c0793e98] 
__handle_sysrq+0xd8/0x2b0 (unreliable)
  [  240.307715] [c001f2d7fd10] [c07946b4] 
write_sysrq_trigger+0x64/0x90
  [  240.307850] [c001f2d7fd40] [c044fb28] proc_reg_write+0x88/0xd0
  [  240.307951] [c001f2d7fd70] [c03a160c] __vfs_write+0x3c/0x70
  [  240.308049] [c001f2d7fd90] [c03a3248] vfs_write+0xd8/0x220
  [  240.308149] [c001f2d7fde0] [c03a50c8] SyS_write+0x68/0x110
  [  240.308248] [c001f2d7fe30] [c000b184] system_call+0x58/0x6c
  [  240.308340] Instruction dump:
  [ 

[Kernel-packages] [Bug 1751098] Re: Ubuntu hangs shortly after booting with kernel 4.13.0-36

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
1039796b23f7e844ed797ee3adc951a5e3c22b4b

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

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

Title:
  Ubuntu hangs shortly after booting with kernel 4.13.0-36

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

Bug description:
  After upgrading to linux 4.13.0-36 my laptop hangs shortly after
  booting, even before logging in to the desktop. It starts with the
  interface being unresponsive but the mouse cursor moving, and shortly
  after that the mouse cursor also hangs intermittently and then
  permanently.

  Linux 4.13.0-32 works fine.

  My laptop is a Dell XPS 13 9360 with an Core i5 7200u.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USUARIOORDEN DE ACCESO PID
   /dev/snd/controlC0:  nicolas2111 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 10:56:06 2018
  InstallationDate: Installed on 2018-02-02 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=452f690d-29d8-46b1-88a4-4262b6d20734 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.2
  dmi.board.name: 05HM5Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.2:bd11/21/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1751796] Re: zed process consumming 100% cpu

[Scott Moser]

Why did you mark this invalid?

If zfs 0.7.X relies on kernel > 4.13, then it seems a valid bug.
zfs-zed does not mention any dependency on a specific linux version, and even 
if it did wouldnt users be guaranteed to hit this issue after they'd upgraded 
zfs-zed and before they'd upgraded (and rebooted into) kernel?



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

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

Title:
  zed process consumming 100% cpu

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  I logged in this morning and found system kind of sluggish.
  A 'top' showed 'zed' process spinning 100% of a cpu.
  I didn't feel like worrying about it, so I simply rebooted.

  System came back up into the same state.
  Running 'strace -p 2002' shows repeated:

  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: zfs-zed 0.7.5-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 09:34:59 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (949 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.zfs.zed.d.zed-functions.sh: [deleted]

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

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

[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)

[Lucas Zanella]

Just to remember, inside the VM the error looks like this:

[26547.754916] EXT4-fs error (device sda1): htree_dirblock_to_tree:976: inode 
#31777: comm gvfsd-trash: Directory block failed checksum
[26547.756301] Aborting journal on device sda1-8.
[26547.757724] EXT4-fs (sda1): Remounting filesystem read-only
[26547.762207] EXT4-fs error (device sda1): ext4_journal_check_start:60: 
Detected aborted journal
[26631.771204] EXT4-fs error (device sda1): htree_dirblock_to_tree:976: inode 
#302034: comm gvfsd-trash: Directory block failed checksum

when outside there's no problem at all.

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 

[Kernel-packages] [Bug 1741992] Re: [18.04] kpatch - Add livepatch hook support for ppc64le

[Manoj Iyer]

** Tags removed: triage-a
** Tags added: triage-r

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

Title:
  [18.04] kpatch - Add livepatch hook support for ppc64le

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

Bug description:
  kpatch is a Linux dynamic kernel patching infrastructure which allows
  you to patch a running kernel without rebooting or restarting any
  processes. It enables sysadmins to apply critical security patches to
  the kernel immediately, without having to wait for long-running tasks
  to complete, for users to log off, or for scheduled reboot windows. It
  gives more control over uptime without sacrificing security or
  stability.

  kpatch is upstream hosted at 
  https://github.com/dynup/kpatch
  https://github.com/dynup/kpatch/releases

  Add support for livepatch infrastructure on ppc64le
  https://github.com/dynup/kpatch/pull/650

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

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

[Kernel-packages] [Bug 1714485] Re: Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.

[Manoj Iyer]

Cascardo, did you get chance to make those changes you mentioned in
comment #8 ? Please update this bug if this fix was already applied to
x/a/z releases.

** Changed in: makedumpfile (Ubuntu Zesty)
   Status: New => Won't Fix

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

Title:
  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Zesty:
  Won't Fix
Status in makedumpfile source package in Artful:
  New
Status in makedumpfile source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 ==
  ---Problem Description---

  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

  ---Steps to Reproduce---

  1. Install Ubuntu 16.04.03 with / as xfs.
  2. Configure kdump.
  3. trigger crash.

  Machine hangs after below log. Attaching console log.

  [  OK  ] Reached target Network is Online.
   Starting Kernel crash dump capture service...
   Starting iSCSI initiator daemon (iscsid)...
  [   12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: 
unexpected operator
  [  OK  ] Started Kernel crash dump capture service.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).

  
  4. After manual reboot  /etc/default/kdump-tools is empty.

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

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

[Kernel-packages] [Bug 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore

[Manoj Iyer]

IBM, could you please confirm this bug is already fixed using the
workaround mentioned here and in bug 1664545

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04.2: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

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

Bug description:
  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system
   
  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com 
   
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

   
  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

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

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

[Kernel-packages] [Bug 1704471] Re: package linux-image-4.10.0-26-lowlatency (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml


** Changed in: linux (Ubuntu)
 Assignee: Vittorio (vis2000) => (unassigned)

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

Title:
  package linux-image-4.10.0-26-lowlatency (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Non so perché si è verificato questo errore

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-26-lowlatency (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-24.28-lowlatency 4.10.15
  Uname: Linux 4.10.0-24-lowlatency i686
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vittorio   1238 F pulseaudio
   /dev/snd/controlC0:  vittorio   1238 F pulseaudio
  Date: Fri Jul 14 19:33:03 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=0e09baa8-8c43-499d-8006-7275dc5c1086
  InstallationDate: Installed on 2017-05-08 (67 days ago)
  InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release i386 
(20161012.1)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-lowlatency 
root=UUID=5395e556-416c-40c3-a8ef-6790431337c1 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~beta3-4ubuntu2.1
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.10.0-26-lowlatency (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to zesty on 2017-06-16 (28 days ago)
  dmi.bios.date: 06/08/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5G41T-M LX
  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.:bvr1101:bd06/08/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLX:rvrRevX.0x: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/1704471/+subscriptions

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

[Kernel-packages] [Bug 1708409] Re: kdump service does not start after configure/reboot

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   Status: Triaged => Incomplete

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

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  Incomplete
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  Fix Committed
Status in makedumpfile source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

  ...
  https://github.com/systemd/systemd/issues/6334

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

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

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

[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)

[Lucas Zanella]

Nope, sorry, I rebooted after copying the dmesg. I thought that since
there is  [68668.595459] EXT4-fs (nvme0n1p2): Remounting filesystem
read-only in what I copied, it was enough because there is where the
error started. Gonna cat the entire file the next time, but I'm afraid
it'll only happend if I force my CPU too much like I did (actually this
is good, because the nvme took a very long time to enter in read only
mody, it's a very good progress)

Meanwhile, I think that the average of read only errors inside the VMs
is like 0.8/day. I always test the main machine when these errors happen
and it's always fine. The only time when it gone wrong was this one that
I reported.

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help 

[Kernel-packages] [Bug 1658733] Re: Ubuntu 16.04.2KVM:kdump fails to mount root file system when noirqdistrib is missing as dump kernel parameter

[Frank Heimes]

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

** Changed in: kexec-tools (Ubuntu Zesty)
   Status: New => Invalid

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

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system when
  noirqdistrib is missing as dump kernel parameter

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  New
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Zesty:
  Invalid
Status in makedumpfile source package in Zesty:
  Invalid
Status in kexec-tools source package in Artful:
  Invalid
Status in makedumpfile source package in Artful:
  Fix Committed
Status in kexec-tools source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On Power Systems, some interrupts are missed, and dumping the crash will 
fail. Adding the noirqdistrib kernel parameter to the kdump kernel will fix 
this.

  [Test Case]
  Setting up kdump to target a virtio-scsi device on a Power System.

  [Regression Potential]
  The parameter could be interpreted differently on a different platform and 
kdump would fail. However, it has been verified that no other platform uses 
such parameter. If another parameter would have been incorrectly removed on the 
patch, kdump could fail on other systems.


  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel
  fails to mount the root file system.  This error does not occur in a
  similar guest installed to a single path device.

  Full console output of the kdump failure is attached.  These messages
  from the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.

  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest

  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  >
  > Could you please recreate the guest for further debug?

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and perform its tasks by setting

[Kernel-packages] [Bug 1635597] Re: Ubuntu:talclp1: Kdump failed with multipath disk

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   Status: Confirmed => Incomplete

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

Title:
  Ubuntu:talclp1: Kdump failed with multipath disk

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  Confirmed

Bug description:
  [Impact]
  When the target device where to dump the kernel is under a multipath 
configuration, dumping will fail, possibly leaving the system stuck in the 
kdump kernel.
  The fix is to include some scsi device handlers needed for the multipath 
setup inside the initramfs image that is used by kdump.
  All modules currently loaded in the system are included.

  [Test Case]
  Setting up kdump to target a multipath device using an appropriate storage 
that requires such scsi_dh modules and triggering a crash will demonstrate that 
kdump fails.
  After the fix, it works fine.

  [Regression Potential]
  If a bug is introduced, loading kdump might fail, and a crash will not be 
generated. A worse regression that might be considered is the system is stuck 
in such a kdump kernel and needs to be rebooted locally (and the crash file is 
not generated either). But since this is what we are trying to fix, we don't 
expect other systems to break. This didn't happen on a small (less than 1GiB of 
RAM) x86 VM, though.

  Problem  Description
  ==
  On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox.

  root@talclp1:~# echo c> /proc/sysrq-trigger
  [  132.643690] sysrq: SysRq : Trigger a crash
  [  132.643739] Unable to handle kernel paging request for data at address 
0x
  [  132.643745] Faulting instruction address: 0xc05c28f4
  [  132.643749] Oops: Kernel access of bad area, sig: 11 [#1]
  [  132.643753] SMP NR_CPUS=2048 NUMA pSeries
  [  132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos 
jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver 
dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag 
binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul 
vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq 
dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth 
crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod
  [  132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic 
#16-Ubuntu
  [  132.643824] task: c00111767080 task.stack: c000d82e
  [  132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: 
c05c28c0
  [  132.643832] REGS: c000d82e3990 TRAP: 0300   Not tainted  
(4.8.0-15-generic)
  [  132.643836] MSR: 80009033   CR: 28242422  
XER: 0001
  [  132.643848] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1
  GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063
  GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998
  GPR08: 0007 0001  0001
  GPR12: c05c28c0 c7b4b900  2200
  GPR16: 10170dc8 01002b566368 10140f58 100c7570
  GPR20:  1017dd58 10153618 1017b608
  GPR24: 3e87a294 0001 c0ebff60 0004
  GPR28: c0ec0320 0063 c0e72a90 
  [  132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50
  [  132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643914] Call Trace:
  [  132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 
(unreliable)
  [  132.643923] [c000d82e3c30] [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643928] [c000d82e3cd0] [c05c4188] 
write_sysrq_trigger+0x78/0xa0
  [  132.643935] [c000d82e3d00] [c03ad770] proc_reg_write+0xb0/0x110
  [  132.643941] [c000d82e3d50] [c030fc3c] __vfs_write+0x6c/0xe0
  [  132.643946] [c000d82e3d90] [c0311144] vfs_write+0xd4/0x240
  [  132.643950] [c000d82e3de0] [c0312e5c] SyS_write+0x6c/0x110
  [  132.643957] [c000d82e3e30] [c00095e0] system_call+0x38/0x108
  [  132.643961] Instruction dump:
  [  132.643963] 38425240 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 
3949ba60
  [  

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

[Manoj Iyer]

This should be available in Bionic now. The patch was applied to bionic
earlier this month. And, in Artful in a couple of weeks.

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

Title:
  [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when
  grouping different pmu events using perf fuzzer . (perf:)

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

Bug description:
  == SRU Justification ==
  Due to this bug, perf fuzzer resulted in crash and system goes for a reboot
  and results in a call trace shown in the bug.  It is due to grouping of 
  different PMU events, which is fixed by mainline commit 
5aa04b3eb6fca63d2e9827be656dcadc26d54e1

  Commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 is in mailine as of
  v4.15-rc5.

  
  == Fix ==
  commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11
  Author: Ravi Bangoria 
  Date:   Thu Nov 30 14:03:22 2017 +0530

  powerpc/perf: Fix oops when grouping different pmu events

  
  == Regression Potential ==
  Low.  This fix is specific to powerpc.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  ==Original Bug Description==
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-30 
03:24:47 ==
  Problem Description :
  ==
  Perf fuzzer resulted in crash and system goes for reboot and the call trace 
is shown below . It is due to grouping of different PMU events.

  Machine details :
  ==
  OS : Ubuntu 1804
  uname -r : 4.13.0-25-generic
  system : Witherspoon + DD2.1
  perf -v : perf version 4.13.13

  ltc-wspoon12 login: [78592.995848] Unable to handle kernel paging request for 
instruction fetch
  [78592.995914] Faulting instruction address: 0x
  [78592.995950] Oops: Kernel access of bad area, sig: 11 [#1]
  [78592.995982] SMP NR_CPUS=2048
  [78592.995985] NUMA
  [78592.996011] PowerNV
  [78592.996045] Modules linked in: vmx_crypto idt_89hpesx crct10dif_vpmsum 
at24 ofpart uio_pdrv_genirq uio cmdlinepart powernv_flash mtd ibmpowernv 
opal_prd ipmi_powernv ipmi_devintf ipmi_msghandler sch_fq_codel ip_tables 
x_tables autofs4 nouveau lpfc ast i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops drm mlx5_core nvmet_fc nvmet tg3 
nvme_fc nvme_fabrics ahci nvme_core libahci mlxfw devlink scsi_transport_fc
  [78592.996367] CPU: 69 PID: 6010 Comm: perf_fuzzer Tainted: GW   
4.13.0-25-generic #29-Ubuntu
  [78592.996422] task: c03f77b5b500 task.stack: c03d0b0c8000
  [78592.996462] NIP:  LR: c00e9b1c CTR: 

  [78592.996509] REGS: c03d0b0cb780 TRAP: 0400   Tainted: GW
(4.13.0-25-generic)
  [78592.996562] MSR: 900040009033 
  [78592.996588]   CR: 48002874  XER: 
  [78592.996642] CFAR: c00e9b18 SOFTE: 1
  [78592.996642] GPR00: c00eb128 c03d0b0cba00 c15f6200 

  [78592.996642] GPR04: c03d0b0cbba0 c03d0b0cbc20 0002 
c1596b10
  [78592.996642] GPR08: 0002  c1596b10 
c03fecad0028
  [78592.996642] GPR12:  c7a8d480  

  [78592.996642] GPR16:    

  [78592.996642] GPR20: 0001 c03d0b0cbc1c c03d0b0cbc24 
c03d0b0cbb98
  [78592.996642] GPR24: c03d0b0cbba0 c03d0b0cbc20 1555 
c03fefeb4ea0
  [78592.996642] GPR28: c03d0b0cbc20 0002 3000 
c03fefeb5190
  [78592.997170] NIP []   (null)
  [78592.997208] LR [c00e9b1c] power_check_constraints+0x13c/0x5a0
  [78592.997247] Call Trace:
  [78592.997267] [c03d0b0cba00] [c03d0b0cbaa0] 0xc03d0b0cbaa0 
(unreliable)
  [78592.997321] [c03d0b0cbb80] [c00eb128] 
power_pmu_event_init+0x298/0x6a0
  [78592.997373] [c03d0b0cbc70] [c029e6b4] 
perf_try_init_event+0xd4/0x120
  [78592.997424] [c03d0b0cbcb0] [c02a1038] 
perf_event_alloc.part.23+0x7b8/0xb90
  [78592.997475] [c03d0b0cbd30] [c02aa0dc] 
SyS_perf_event_open+0x69c/0xfa0
  [78592.997527] [c03d0b0cbe30] [c000b184] system_call+0x58/0x6c
  [78592.997568] Instruction dump:
  [78592.997597]        

  [78592.997664]        

  [78592.997733] ---[ end trace 57fb7542c4083583 ]---
  [78594.008780]
  [78594.008932] Sending 

[Kernel-packages] [Bug 1746988] Re: [Ubuntu 18.04 FEAT] OpenCAPI enabling

[Manoj Iyer]

** Tags removed: triage-g
** Tags added: triage-a

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

Title:
  [Ubuntu 18.04 FEAT] OpenCAPI enabling

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

Bug description:
  [FEATURE] OpenCAPI enabling

  OpenCAPI is an Open Interface Architecture that allows any
  microprocessor to attach to

*  Coherent user-level accelerators and I/O devices
*  Advanced memories accessible via read/write or user-level DMA semantics
*  Agnostic to processor architecture

  
  This is a feature to enable OpenCapi on Ubuntu 18.04. This is planned to be 
included in 4.16 and it will need to be backported to 4.15:

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

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

[Kernel-packages] [Bug 1751404] Re: cxl: patches for POWER9 support missing (CAPI)

[Manoj Iyer]

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Kernel Team (canonical-kernel-team)

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

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

Title:
  cxl: patches for POWER9 support missing (CAPI)

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

Bug description:
  The following patch, already in mainline, is missing in Ubuntu 18.04
  (kernel v4.15):

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=b1db551324f72fa14ad82ca31237a7ed418104df
  ("cxl: Add support for ASB_Notify on POWER9")

  Please integrate this patch into Ubuntu 18.04 Thanks in advance for
  your support.

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

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

[Kernel-packages] [Bug 1751796] Re: zed process consumming 100% cpu

[Colin Ian King]

** Changed in: zfs-linux (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  zed process consumming 100% cpu

Status in zfs-linux package in Ubuntu:
  Invalid

Bug description:
  I logged in this morning and found system kind of sluggish.
  A 'top' showed 'zed' process spinning 100% of a cpu.
  I didn't feel like worrying about it, so I simply rebooted.

  System came back up into the same state.
  Running 'strace -p 2002' shows repeated:

  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: zfs-zed 0.7.5-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 09:34:59 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (949 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.zfs.zed.d.zed-functions.sh: [deleted]

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

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

[Kernel-packages] [Bug 1291969] Re: No usb on resume from suspend

[Kai-Heng Feng]

@Tarek

It's a pretty bad workaround. Please file a new bug so we can check full
dmesg.

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

Title:
  No usb on resume from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My XPS13 running 14.04 sometimes loses its USB ports after resume from
  suspend. When this happens the entire bus seems dead - both external
  ports do not work, and internal USB devices (webcam, touchscreen) are
  also non-functional. Furthermore lsusb shows no devices attached.
  Rebooting or performing another suspend/resume cycle will clear the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-17-generic 3.13.0-17.37
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  steve  2868 F pulseaudio
   /dev/snd/controlC0:  steve  2868 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 13 08:36:46 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=79084358-087f-4cee-a0be-e2f78361873f
  InstallationDate: Installed on 2013-12-02 (100 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  Lsusb:
   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: Dell Inc. XPS13 9333
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic 
root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-17-generic N/A
   linux-backports-modules-3.13.0-17-generic  N/A
   linux-firmware 1.126
  RfKill:
   1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-02-12 (28 days ago)
  dmi.bios.date: 11/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)

[Kai-Heng Feng]

Do you have full dmesg in comment #75? Do you see any NVMe error?

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lz 1088 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-01-30 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Razer Blade Stealth
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 

[Kernel-packages] [Bug 1744791] Re: [Ubuntu18.04] linux-image-4.13.0-25-generic-dbgsym is not available in repo which is required for crash analysis of vmcore

[Andrew Cloke]

After providing a reference to the requested debug symbols, awaiting
information as to whether this issue is reproducible with the latest
Ubuntu kernel.

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

Title:
  [Ubuntu18.04] linux-image-4.13.0-25-generic-dbgsym is not available in
  repo which is required for crash analysis of vmcore

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

Bug description:
  ---Problem Description---
  No debug kernel deb packages available for 4.13.0-25-generic kernel [Ubuntu 
18.04 ]
  Unable to analyze vmcore generated via crash. 

  ---uname output---
  Linux spoon2 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:15:55 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8335-GTC 
   
  ---Steps to Reproduce---
  Install 18.04 ppc64el
  upgrade kernel to 4.13.0-25-generic or 4.13.0-17-generic
  try configuring debug repo
  https://wiki.ubuntu.com/Kernel/CrashdumpRecipe
  http://ddebs.ubuntu.com/pool/main/l/linux/
  sudo tee /etc/apt/sources.list.d/ddebs.list << EOF
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)  main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-security main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-updates  main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-proposed main restricted 
universe multiverse
  EOF

  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys ECDCAD72428D7C01
  sudo apt-get update
  sudo apt-get install linux-image-$(uname -r)-dbgsym

  Warning /!\ Be aware that those packages are huge! (~600 MB)

  When installed, the debug kernel can be found under
  /usr/lib/debug/boot/ and crash is started by:

  crash  

  Crash command to analyze vmcore will not work as kernel debuginfo deb package 
is not found in repo . 
  root@spoon2:~# sudo apt-get install linux-image-$(uname -r)-dbgsym
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package linux-image-4.13.0-25-generic-dbgsym
  E: Couldn't find any package by glob 'linux-image-4.13.0-25-generic-dbgsym'
  E: Couldn't find any package by regex 'linux-image-4.13.0-25-generic-dbgsym'
  root@spoon2:~# 
   
  I was also not able to find this debug symbol for 18.04 kernel. I understand 
that the current 18.04 kernel is old and was removed from the archive. Is it 
correct?

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

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

[Kernel-packages] [Bug 1745104] Re: ISST-LTE: KVM:UBUNTU1804: kdump is not working on UbuntuKVM guest

[Frank Heimes]

** Changed in: ubuntu-power-systems
   Status: In Progress => Fix Committed

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

Title:
  ISST-LTE: KVM:UBUNTU1804: kdump is not working on UbuntuKVM  guest

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

Bug description:
  == Comment: #0 - Chanh H. Nguyen  - 2018-01-23 14:55:05 
==
  root@boslcp4g5:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Bionic Beaver (development branch)"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic
  root@boslcp4g5:~# uname -r
  4.13.0-25-generic
  root@boslcp4g5:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-25-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.13.0-25-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.13.0-25-generic 
root=UUID=8a776bc5-d9e0-4a1d-9218-135f9c702e11 ro splash quiet nr_cpus=1 
systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@boslcp4g5:~# kdump-config status
  current state   : ready to kdump
  root@boslcp4g5:~# echo c > /proc/sysrq-trigger
  [  176.911191] sysrq: SysRq : This sysrq operation is disabled.
  root@boslcp4g5:~# sysctl -w kernel.sysrq=1
  kernel.sysrq = 1
  root@boslcp4g5:~# echo c > /proc/sysrq-trigger
  [  240.304466] sysrq: SysRq : Trigger a crash
  [  240.304545] Unable to handle kernel paging request for data at address 
0x
  [  240.304656] Faulting instruction address: 0xc0792f88
  [  240.304771] Oops: Kernel access of bad area, sig: 11 [#1]
  [  240.304846] SMP NR_CPUS=2048
  [  240.304848] NUMA
  [  240.304903] pSeries
  [  240.305000] Modules linked in: sctp_diag sctp libcrc32c dccp_diag dccp 
tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag netlink_diag 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache dm_service_time 
vmx_crypto crct10dif_vpmsum binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc 
scsi_dh_alua sunrpc sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq 
crc32c_vpmsum virtio_net virtio_scsi
  [  240.305776] CPU: 12 PID: 1860 Comm: bash Not tainted 4.13.0-25-generic 
#29-Ubuntu
  [  240.305886] task: c000ff904500 task.stack: c001f2d7c000
  [  240.305979] NIP: c0792f88 LR: c0793eb8 CTR: 
c0792f60
  [  240.306087] REGS: c001f2d7f9f0 TRAP: 0300   Not tainted  
(4.13.0-25-generic)
  [  240.306195] MSR: 80009033 
  [  240.306207]   CR: 2842  XER: 2004
  [  240.306338] CFAR: c0793eb4 DAR:  DSISR: 4200 
SOFTE: 1
  [  240.306338] GPR00: c0793eb8 c001f2d7fc70 c15f6200 
0063
  [  240.306338] GPR04: c001feeeade8 c001fef02068 6967676572206120 
63726173680d0a72
  [  240.306338] GPR08: 0007 0001  

  [  240.306338] GPR12: c0792f60 c7ac7e00 10180df8 
10189e30
  [  240.306338] GPR16: 10189ea8 10151210 1018bd58 
1018de48
  [  240.306338] GPR20: 28bc0268 0001 10164590 
10163bb0
  [  240.306338] GPR24: 7fffdcb37d34 7fffdcb37d30 c14fa770 
0002
  [  240.306338] GPR28: 0063 0007 c14824f4 
c14fab10
  [  240.307346] NIP [c0792f88] sysrq_handle_crash+0x28/0x30
  [  240.307474] LR [c0793eb8] __handle_sysrq+0xf8/0x2b0
  [  240.307553] Call Trace:
  [  240.307594] [c001f2d7fc70] [c0793e98] 
__handle_sysrq+0xd8/0x2b0 (unreliable)
  [  240.307715] [c001f2d7fd10] [c07946b4] 
write_sysrq_trigger+0x64/0x90
  [  240.307850] [c001f2d7fd40] [c044fb28] proc_reg_write+0x88/0xd0
  [  240.307951] [c001f2d7fd70] [c03a160c] __vfs_write+0x3c/0x70
  [  240.308049] [c001f2d7fd90] [c03a3248] vfs_write+0xd8/0x220
  [  240.308149] [c001f2d7fde0] [c03a50c8] SyS_write+0x68/0x110
  [  240.308248] [c001f2d7fe30] [c000b184] system_call+0x58/0x6c
  [  240.308340] Instruction dump:
  [  240.308400] 4bfff9f1 4bfffe50 3c4c00e6 384232a0 7c0802a6 6000 3921 

[Kernel-packages] [Bug 1749040] Re: KPTI-enabled kernel fails to boot on Cavium ThunderX CRB

[Manoj Iyer]

Test results from D05 Hisilicon board.

** Attachment added: "D05 HiSilicon"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5063513/+files/submission_2018-02-26T14.58.17.996524.html

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

Title:
  KPTI-enabled kernel fails to boot on Cavium ThunderX CRB

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

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

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

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

[Kernel-packages] [Bug 1751798] Re: linux: -proposed tracker

[Brad Figg]

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

** Changed in: kernel-sru-workflow/prepare-package-ports-meta
   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/1751798

Title:
  linux:  -proposed tracker

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

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

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

  backports: bug 1751799 (linux-azure), bug 1751801 (linux-azure-edge), bug 
1751802 (linux-gcp), bug 1751803 (linux-hwe), bug 1751805 (linux-oem)
  derivatives: bug 1751807 (linux-raspi2)

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

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

[Kernel-packages] [Bug 1680349] Re: Ubuntu 17.04: Kdump fails to capture dump on Firestone NV when machine crashes while running stress-ng.

[Andrew Cloke]

** Tags removed: triage-r
** Tags added: triage-g

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

Title:
  Ubuntu 17.04: Kdump fails to capture dump on Firestone NV when machine
  crashes while running stress-ng.

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

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-03-10 02:43:10 ==
  ---Problem Description---

  Ubuntu 17.04: Kdump fails to capture dump on Firestone NV when machine
  crashes while running stress-ng. Machine hangs.

  ---Steps to Reproduce---

  1. Configure kdump.
  2. Install stress-ng
  # apt-get install stress-ng
  3. Run stress-ng
  # stress-ng - a 0

  
  Logs:
  
  root@ltc-firep3:~# kdump-config load
  Modified cmdline:root=UUID=8b0d5b99-6087-4f40-82ea-375c83a4c139 ro quiet 
splash irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0 elfcorehdr=155200K 
   * loaded kdump kernel
  root@ltc-firep3:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.10.0-11-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.10.0-11-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=8b0d5b99-6087-4f40-82ea-375c83a4c139 ro quiet splash 
irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img 
/var/lib/kdump/vmlinuz
  root@ltc-firep3:~# stress-ng -a 0
  stress-ng: info:  [3900] defaulting to a 86400 second run per stressor
  stress-ng: info:  [3900] dispatching hogs: 160 af-alg, 160 affinity, 160 aio, 
160 aiol, 160 apparmor, 160 atomic, 160 bigheap, 160 brk, 160 bsearch, 160 
cache, 160 cap, 160 chdir, 160 chmod, 160 chown, 160 chroot, 160 clock, 160 
clone, 160 context, 160 copy-file, 160 cpu, 160 cpu-online, 160 crypt, 160 
daemon, 160 dccp, 160 dentry, 160 dir, 160 dirdeep, 160 dnotify, 160 dup, 160 
epoll, 160 eventfd, 160 exec, 160 fallocate, 160 fanotify, 160 fault, 160 
fcntl, 160 fiemap, 160 fifo, 160 filename, 160 flock, 160 fork, 160 fp-error, 
160 fstat, 160 full, 160 futex, 160 get, 160 getdent, 160 getrandom, 160 
handle, 160 hdd, 160 heapsort, 160 hsearch, 160 icache, 160 icmp-flood, 160 
inotify, 160 io, 160 iomix, 160 ioprio, 160 itimer, 160 kcmp, 160 key, 160 
kill, 160 klog, 160 lease, 160 link, 160 locka, 160 lockbus, 160 lockf, 160 
lockofd, 160 longjmp, 160 lsearch, 160 madvise, 160 malloc, 160 matrix, 160 
membarrier, 160 memcpy, 160 memfd, 160 mergesort, 160 mincore, 160 mknod, 160 
mlock, 160 mmap, 160 mmapfork, 160 mmapmany, 160 mq, 160 mremap, 160 msg, 160 
msync, 160 netlink-proc, 160 nice, 160 nop, 160 null, 160 numa, 160 oom-pipe, 
160 opcode, 160 open, 160 personality, 160 pipe, 160 poll, 160 procfs, 160 
pthread, 160 ptrace, 160 pty, 160 qsort, 160 quota, 160 rdrand, 160 readahead, 
160 remap, 160 rename, 160 resources, 160 rlimit, 160 rmap, 160 rtc, 160 
schedpolicy, 160 sctp, 160 seal, 160 seccomp, 160 seek, 160 sem, 160 sem-sysv, 
160 sendfile, 160 shm, 160 shm-sysv, 160 sigfd, 160 sigfpe, 160 sigpending, 160 
sigq, 160 sigsegv, 160 sigsuspend, 160 sleep, 160 sock, 160 sockfd, 160 
sockpair, 160 spawn, 160 splice, 160 stack, 160 stackmmap, 160 str, 160 stream, 
160 switch, 160 symlink, 160 sync-file, 160 sysfs, 160 sysinfo, 160 tee, 160 
timer, 160 timerfd, 160 tlb-shootdown, 160 tmpfs, 160 tsc, 160 tsearch, 160 
udp, 160 udp-flood, 160 unshare, 160 urandom, 160 userfaultfd, 160 utime, 160 
vecmath, 160 vfork, 160 vforkmany, 160 vm, 160 vm-rw, 160 vm-splice, 160 wait, 
160 wcs, 160 xattr, 160 yield, 160 zero, 160 zlib, 160 zombie
  stress-ng: info:  [3900] cache allocate: using built-in defaults as unable to 
determine cache details
  stress-ng: info:  [3900] cache allocate: default cache size: 2048K
  stress-ng: info:  [3907] stress-ng-atomic: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: info:  [3955] stress-ng-exec: running as root, won't run test.
  stress-ng: info:  [3999] stress-ng-icache: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: info:  [4040] stress-ng-lockbus: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: info:  [4313] stress-ng-numa: system has 2 of a maximum 256 memory 
NUMA nodes
  stress-ng: info:  [4455] stress-ng-rdrand: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: fail:  [4558] stress-ng-rtc: ioctl RTC_ALRM_READ failed, errno=22 
(Invalid argument)
  stress-ng: fail:  [4017] stress-ng-key: keyctl KEYCTL_DESCRIBE failed, 
errno=127 (Key has expired)

[Kernel-packages] [Bug 1692538] Re: Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   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/1692538

Title:
  Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA

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

Bug description:
  
  == SRU Justification ==
  Commit 66aa0678ef is request to fix four issues with the ibmveth driver.
  The issues are as follows:
  - Issue 1: ibmveth doesn't support largesend and checksum offload features 
when configured as "Trunk".
  - Issue 2: SYN packet drops seen at destination VM. When the packet
  originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to IO
  server's inbound Trunk ibmveth, on validating "checksum good" bits in ibmveth
  receive routine, SKB's ip_summed field is set with CHECKSUM_UNNECESSARY flag.
  - Issue 3: First packet of a TCP connection will be dropped, if there is
  no OVS flow cached in datapath.
  - Issue 4: ibmveth driver doesn't have support for SKB's with frag_list.

  The details for the fixes to these issues are described in the commits
  git log.



  == Comment: #0 - BRYANT G. LY  - 2017-05-22 08:40:16 ==
  ---Problem Description---

   - Issue 1: ibmveth doesn't support largesend and checksum offload features
     when configured as "Trunk". Driver has explicit checks to prevent
     enabling these offloads.

   - Issue 2: SYN packet drops seen at destination VM. When the packet
     originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to
     IO server's inbound Trunk ibmveth, on validating "checksum good" bits
     in ibmveth receive routine, SKB's ip_summed field is set with
     CHECKSUM_UNNECESSARY flag. This packet is then bridged by OVS (or Linux
     Bridge) and delivered to outbound Trunk ibmveth. At this point the
     outbound ibmveth transmit routine will not set "no checksum" and
     "checksum good" bits in transmit buffer descriptor, as it does so only
     when the ip_summed field is CHECKSUM_PARTIAL. When this packet gets
     delivered to destination VM, TCP layer receives the packet with checksum
     value of 0 and with no checksum related flags in ip_summed field. This
     leads to packet drops. So, TCP connections never goes through fine.

   - Issue 3: First packet of a TCP connection will be dropped, if there is
     no OVS flow cached in datapath. OVS while trying to identify the flow,
     computes the checksum. The computed checksum will be invalid at the
     receiving end, as ibmveth transmit routine zeroes out the pseudo
     checksum value in the packet. This leads to packet drop.

   - Issue 4: ibmveth driver doesn't have support for SKB's with frag_list.
     When Physical NIC has GRO enabled and when OVS bridges these packets,
     OVS vport send code will end up calling dev_queue_xmit, which in turn
     calls validate_xmit_skb.
     In validate_xmit_skb routine, the larger packets will get segmented into
     MSS sized segments, if SKB has a frag_list and if the driver to which
     they are delivered to doesn't support NETIF_F_FRAGLIST feature.

  Contact Information = Bryant G. Ly/b...@us.ibm.com

  ---uname output---
  4.8.0-51.54

  Machine Type = p8

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   Increases performance greatly

  The patch has been accepted upstream:
  https://patchwork.ozlabs.org/patch/764533/

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

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

[Kernel-packages] [Bug 1681909] Re: Ubuntu 17.04: dump is not captured in remote host when kdump over ssh is configured on firestone.

[Andrew Cloke]

>From comment #8 and #10, is there any result from the PowerIO team's
investigation into the NIC and related KDUMP_NET_WAIT_TIME config
option?

** Changed in: ubuntu-power-systems
   Status: Triaged => Incomplete

** Tags removed: triage-r
** Tags added: triage-g

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

Title:
  Ubuntu 17.04: dump is not captured in remote host when kdump over ssh
  is configured on firestone.

Status in The Ubuntu-power-systems project:
  Incomplete
Status in makedumpfile package in Ubuntu:
  New

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH  - 2017-03-07 
05:00:29 ==
  ---Problem Description---

  Ubuntu 17.04: dump is not captured in remote host when kdump over ssh
  is configured on firestone.

  ---Steps to Reproduce---

  1. Configure kdump.
  2. Check whether kdump is operational using ?# kdump-config show?.
  3. Install ?kernel-debuginfo? and ?kernel-debuginfo-common? rpms.
  4. Setup password less ssh connection, generate rsa key.
  # ssh-keygen -t rsa
  5. verify id_rsa and id_rsa.pub are created under /root/.ssh/
  6. Edit /etc/default/kdump-tools and add below entries.
  SSH="ubuntu@9.114.15.239"
  SSH_KEY=/root/.ssh/id_rsa
  7. Propagate RSA key.
  # kdump-config propagate
  8. Restart kdump service.
  # kdump-config load
  9. Trigger Crash using below commands.
  # echo "1" > /proc/sys/kernel/sysrq
  # echo "c" > /proc/sysrq-trigger
  10. Verify dump is available in remote server in configured path.

  Machine details
  ===

  $ ipmitool -I lanplus -H  9.47.70.3 -U ADMIN -P admin sol activate

  $ ssh ubuntu@9.47.70.29

  PW: shriya101

  
  Attaching logs

  == Comment: #1 - PAVITHRA R. PRAKASH  -
  2017-03-07 05:01:42 ==

  
  == Comment: #5 - PAVITHRA R. PRAKASH  - 2017-03-07 
23:19:46 ==
  Hi, 

  Attaching the logs.

  Network info:

  root@ltc-firep3:~# hwinfo --network
  36: None 00.0: 10700 Loopback   
[Created at net.126]
Unique ID: ZsBS.GQNx7L4uPNA
SysFS ID: /class/net/lo
Hardware Class: network interface
Model: "Loopback network interface"
Device File: lo
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown

  37: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: 2lHw.ndpeucax6V1
Parent ID: mIXc.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f2
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.2
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f2
HW Address: 98:be:94:03:18:4a
Permanent HW Address: 98:be:94:03:18:4a
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #15 (Ethernet controller)

  38: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: 7Onn.ndpeucax6V1
Parent ID: sx0U.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f0
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.0
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f0
HW Address: 98:be:94:03:18:48
Permanent HW Address: 98:be:94:03:18:48
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #16 (Ethernet controller)

  39: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: VwX_.ndpeucax6V1
Parent ID: DUng.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f3
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.3
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f3
HW Address: 98:be:94:03:18:4b
Permanent HW Address: 98:be:94:03:18:4b
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #25 (Ethernet controller)

  40: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: bZ1s.ndpeucax6V1
Parent ID: J7HY.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f1
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.1
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f1
HW Address: 98:be:94:03:18:49
Permanent HW Address: 98:be:94:03:18:49
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #4 (Ethernet controller)
  root@ltc-firep3:~# 


  Thanks,
  Pavithra

  == Comment: #6 - PAVITHRA R. PRAKASH  -
  2017-03-07 23:20:47 ==

  
  == Comment: #7 - 

[Kernel-packages] [Bug 1751796] Re: zed process consumming 100% cpu

[Scott Moser]

sorry for not being clear above.  I had dpkg-diverted that update-grub,
so my dist-upgrade and then reboot put me back into an older kernel.

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

Title:
  zed process consumming 100% cpu

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  I logged in this morning and found system kind of sluggish.
  A 'top' showed 'zed' process spinning 100% of a cpu.
  I didn't feel like worrying about it, so I simply rebooted.

  System came back up into the same state.
  Running 'strace -p 2002' shows repeated:

  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: zfs-zed 0.7.5-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 09:34:59 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (949 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.zfs.zed.d.zed-functions.sh: [deleted]

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

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

[Kernel-packages] [Bug 1751796] Re: zed process consumming 100% cpu

[Scott Moser]

Colin, thanks for quick response.
rebooting into 4.15 did in resolve the issue.

I woudln't have stumbled on it at all except at some point i had dpkg-diverted 
 /etc/kernel/postinst.d/zz-update-grub
so dist-upgrades didn't fix it.

fwiw, I was booted into vmlinuz-4.13.0-32-generic when I found the
problem.

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

Title:
  zed process consumming 100% cpu

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  I logged in this morning and found system kind of sluggish.
  A 'top' showed 'zed' process spinning 100% of a cpu.
  I didn't feel like worrying about it, so I simply rebooted.

  System came back up into the same state.
  Running 'strace -p 2002' shows repeated:

  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: zfs-zed 0.7.5-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 09:34:59 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (949 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.zfs.zed.d.zed-functions.sh: [deleted]

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

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

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

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2018-02-26 09:41 EDT---
We would  like getting the kvm_stat version as it will appear in kernel 4.17?

Specifically, we'd be interested in the following commits (already
queued for 4.17 in the kvm maintainer's tree at
https://git.kernel.org/pub/scm/virt/kvm/kvm.git/log/?h=queue):

faa312a543283c717342cd332b5b9247bd305dce   tools/kvm_stat: simplify the sortkey 
function
006f1548ac13d67d21865416a0f4e8062df1a85f   tools/kvm_stat: use a namedtuple for 
storing the values
0eb578009a1d530a11846d7c4733a5db04730884   tools/kvm_stat: use a more pythonic 
way to iterate over dictionaries
369d5a85bb782ecf63c5bae9686c7e6104eea991   tools/kvm_stat: avoid 'is' for 
equality checks
3df33a0f34a3883b6696bff8cc8fcda3c7444a62   tools/kvm_stat: fix crash when 
filtering out all non-child trace events
1cd8bfb1ed9962be6d80d5020508922aa93653ac   tools/kvm_stat: print error on 
invalid regex
1fd6a708c8438403dee17eb411cf81ffba13cf43   tools/kvm_stat: fix debugfs handling
c0e8c21eae616ed8703c1b4b01046a1578ee875c   tools/kvm_stat: mark private methods 
as such
516f1190a1e0cce12128a6446e6438745c8de62a   tools/kvm_stat: eliminate extra 
guest/pid selection dialog
18e8f4100ef14f924514fbd91eb67bd5fa5396b7   tools/kvm_stat: separate drilldown 
and fields filtering
df72ecfc790fa01de1c41f836ff51d12f9c40318   tools/kvm_stat: group child events 
indented after parent
6789af030a462708f937137e05eb12ea009fb348   tools/kvm_stat: print 'Total' line 
for multiple events only

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

Title:
  [18.04 FEAT] Add kvm_stat from kernel tree

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Improves RAS characterics of systems running KVM by providing kvm_stat script:
  https://github.com/torvalds/linux/tree/master/tools/kvm/kvm_stat

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

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

[Kernel-packages] [Bug 1751796] Re: zed process consumming 100% cpu

[Colin Ian King]

This is most probably because you are using ZFS 0.7.x user space tools
with a kernel that has ZFS 0.6.5.x drivers. Please install the latest
Bionic 4.15 kernel and see if that fixes the issue.

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

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

** Changed in: zfs-linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  zed process consumming 100% cpu

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  I logged in this morning and found system kind of sluggish.
  A 'top' showed 'zed' process spinning 100% of a cpu.
  I didn't feel like worrying about it, so I simply rebooted.

  System came back up into the same state.
  Running 'strace -p 2002' shows repeated:

  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: zfs-zed 0.7.5-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 09:34:59 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (949 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.zfs.zed.d.zed-functions.sh: [deleted]

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

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

[Kernel-packages] [Bug 1744791] Re: [Ubuntu18.04] linux-image-4.13.0-25-generic-dbgsym is not available in repo which is required for crash analysis of vmcore

[Frank Heimes]

** Changed in: ubuntu-power-systems
   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/1744791

Title:
  [Ubuntu18.04] linux-image-4.13.0-25-generic-dbgsym is not available in
  repo which is required for crash analysis of vmcore

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

Bug description:
  ---Problem Description---
  No debug kernel deb packages available for 4.13.0-25-generic kernel [Ubuntu 
18.04 ]
  Unable to analyze vmcore generated via crash. 

  ---uname output---
  Linux spoon2 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:15:55 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8335-GTC 
   
  ---Steps to Reproduce---
  Install 18.04 ppc64el
  upgrade kernel to 4.13.0-25-generic or 4.13.0-17-generic
  try configuring debug repo
  https://wiki.ubuntu.com/Kernel/CrashdumpRecipe
  http://ddebs.ubuntu.com/pool/main/l/linux/
  sudo tee /etc/apt/sources.list.d/ddebs.list << EOF
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)  main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-security main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-updates  main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-proposed main restricted 
universe multiverse
  EOF

  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys ECDCAD72428D7C01
  sudo apt-get update
  sudo apt-get install linux-image-$(uname -r)-dbgsym

  Warning /!\ Be aware that those packages are huge! (~600 MB)

  When installed, the debug kernel can be found under
  /usr/lib/debug/boot/ and crash is started by:

  crash  

  Crash command to analyze vmcore will not work as kernel debuginfo deb package 
is not found in repo . 
  root@spoon2:~# sudo apt-get install linux-image-$(uname -r)-dbgsym
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package linux-image-4.13.0-25-generic-dbgsym
  E: Couldn't find any package by glob 'linux-image-4.13.0-25-generic-dbgsym'
  E: Couldn't find any package by regex 'linux-image-4.13.0-25-generic-dbgsym'
  root@spoon2:~# 
   
  I was also not able to find this debug symbol for 18.04 kernel. I understand 
that the current 18.04 kernel is old and was removed from the archive. Is it 
correct?

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

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

[Kernel-packages] [Bug 1735713] Re: Ubuntu16.04.03: Kernel Oops on targetcli

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   Status: Incomplete => Invalid

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

Title:
  Ubuntu16.04.03: Kernel Oops on targetcli

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

Bug description:
  == Comment: #0 - RAHUL CHANDRAKAR  - 2017-12-01 03:26:31 
==
  ---Problem Description---
  Error while running targetcli command on Ubuntu 16.04
   
  ---uname output---
  Linux alpvm2nova 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:23:01 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8408-44E 
   
  ---System Hang---
   gpfs is stuck because of this
   
  ---Debugger---
  A debugger is not configured
   
  Contact Information = rahch...@in.ibm.com 
   
  Stack trace output:
   [Fri Dec  1 03:05:12 2017] Unable to handle kernel paging request for data 
at address 0x010d0688
  [Fri Dec  1 03:05:12 2017] Faulting instruction address: 0xd7570a30
  [Fri Dec  1 03:05:12 2017] Oops: Kernel access of bad area, sig: 11 [#2]
  [Fri Dec  1 03:05:12 2017] SMP NR_CPUS=2048 NUMA pSeries
  [Fri Dec  1 03:05:12 2017] Modules linked in: hvcs(OE) hvcserver rpadlpar_io 
rpaphp xt_tcpudp xt_nat target_core_pscsi(OE) target_core_file(OE) 
target_core_iblock(OE) target_core_user(OE) uio iscsi_target_mod(OE) mmfs26(OE) 
mmfslinux(OE) tracedev(OE) dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag 
af_packet_diag netlink_diag openvswitch binfmt_misc pseries_rng ibmvmc(OE) 
vmx_crypto rtc_generic xt_conntrack nf_nat_ftp nf_conntrack_ftp 
nf_conntrack_netlink nfnetlink nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_conntrack_ipv6 nf_defrag_ipv6 nbd br_netfilter bridge ib_iser rdma_cm iw_cm 
ib_cm ib_sa ib_mad ib_core ib_addr vhost_net vhost macvtap macvlan iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi ip_vs libcrc32c iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_mangle iptable_filter
  [Fri Dec  1 03:05:12 2017]  ipt_REJECT nf_reject_ipv4 ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_nat nf_conntrack ip_tables ip6table_filter ip6_tables 
ebtables x_tables dm_snapshot dm_bufio 8021q garp mrp stp llc autofs4 
dm_round_robin ses enclosure scsi_transport_sas be2net ibmvscsis(OE) 
target_core_mod(OE) configfs(OE) ibmveth(OE) lpfc vxlan ip6_udp_tunnel 
udp_tunnel scsi_transport_fc ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua 
dm_multipath
  [Fri Dec  1 03:05:12 2017] CPU: 13 PID: 178523 Comm: targetcli Tainted: G 
 D W  OE   4.4.0-98-generic #121-Ubuntu
  [Fri Dec  1 03:05:12 2017] task: c007d399cf60 ti: c007e4a84000 
task.ti: c007e4a84000
  [Fri Dec  1 03:05:12 2017] NIP: d7570a30 LR: d75709c4 CTR: 
c016e220
  [Fri Dec  1 03:05:12 2017] REGS: c007e4a87820 TRAP: 0300   Tainted: G 
 D W  OE(4.4.0-98-generic)
  [Fri Dec  1 03:05:12 2017] MSR: 80009033   CR: 
4248  XER: 
  [Fri Dec  1 03:05:12 2017] CFAR: c0008468 DAR: 010d0688 
DSISR: 4000 SOFTE: 1 
 GPR00: d75709c4 c007e4a87aa0 
d757fdf8 0001 
 GPR04: 0240 c007e8739b10 
0001  
 GPR08: 010d0680 d7f61d50 
d757fdf8 d75765f0 
 GPR12: c016e220 cfb47b80 
3fffc86beb50  
 GPR16:  103b7d00 
  
 GPR20: c007d5379aa0 c004d39b5280 
 0024 
 GPR24: c007e8739b00 c004d39b5280 
d7570910 c00516f61d00 
 GPR28: c00518b7e488 c007a6367810 
c007e8739b00 d7f6db50 
  [Fri Dec  1 03:05:12 2017] NIP [d7570a30] 
configfs_open_file+0x120/0x260 [configfs]
  [Fri Dec  1 03:05:12 2017] LR [d75709c4] 
configfs_open_file+0xb4/0x260 [configfs]
  [Fri Dec  1 03:05:12 2017] Call Trace:
  [Fri Dec  1 03:05:12 2017] [c007e4a87aa0] [d75709c4] 
configfs_open_file+0xb4/0x260 [configfs] (unreliable)
  [Fri Dec  1 03:05:12 2017] [c007e4a87af0] [c02e2d40] 
do_dentry_open+0x2c0/0x460
  [Fri Dec  1 03:05:12 2017] [c007e4a87b50] [c02fb388] 
do_last+0x178/0xff0
  [Fri Dec  1 03:05:12 2017] [c007e4a87c10] [c02fc41c] 
path_openat+0xcc/0x3c0
  [Fri Dec  1 03:05:12 2017] [c007e4a87c90] [c02fe33c] 
do_filp_open+0xfc/0x170
  [Fri Dec  1 03:05:12 2017] [c007e4a87db0] [c02e4b30] 
do_sys_open+0x1c0/0x3b0
  [Fri Dec  1 03:05:12 2017] [c007e4a87e30] [c0009204] 
system_call+0x38/0xb4
  [Fri Dec  1 03:05:12 

[Kernel-packages] [Bug 1751798] Re: linux: -proposed tracker

[Kleber Sacilotto de Souza]

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ backports: bug 1751799 (linux-azure), bug 1751801 (linux-azure-edge), bug 
1751802 (linux-gcp), bug 1751803 (linux-hwe), bug 1751805 (linux-oem)
+ derivatives: bug 1751807 (linux-raspi2)

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

Title:
  linux:  -proposed tracker

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

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

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

  backports: bug 1751799 (linux-azure), bug 1751801 (linux-azure-edge), bug 
1751802 (linux-gcp), bug 1751803 (linux-hwe), bug 1751805 (linux-oem)
  derivatives: bug 1751807 (linux-raspi2)

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

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

[Kernel-packages] [Bug 1680349] Re: Ubuntu 17.04: Kdump fails to capture dump on Firestone NV when machine crashes while running stress-ng.

[Andrew Cloke]

This issue was originally raised with 17.04 which is no longer
supported. Could you confirm this is fixed with the Xenial HWE kernel or
the Artful release?


** Changed in: ubuntu-power-systems
   Status: Triaged => 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/1680349

Title:
  Ubuntu 17.04: Kdump fails to capture dump on Firestone NV when machine
  crashes while running stress-ng.

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

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-03-10 02:43:10 ==
  ---Problem Description---

  Ubuntu 17.04: Kdump fails to capture dump on Firestone NV when machine
  crashes while running stress-ng. Machine hangs.

  ---Steps to Reproduce---

  1. Configure kdump.
  2. Install stress-ng
  # apt-get install stress-ng
  3. Run stress-ng
  # stress-ng - a 0

  
  Logs:
  
  root@ltc-firep3:~# kdump-config load
  Modified cmdline:root=UUID=8b0d5b99-6087-4f40-82ea-375c83a4c139 ro quiet 
splash irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0 elfcorehdr=155200K 
   * loaded kdump kernel
  root@ltc-firep3:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.10.0-11-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.10.0-11-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=8b0d5b99-6087-4f40-82ea-375c83a4c139 ro quiet splash 
irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img 
/var/lib/kdump/vmlinuz
  root@ltc-firep3:~# stress-ng -a 0
  stress-ng: info:  [3900] defaulting to a 86400 second run per stressor
  stress-ng: info:  [3900] dispatching hogs: 160 af-alg, 160 affinity, 160 aio, 
160 aiol, 160 apparmor, 160 atomic, 160 bigheap, 160 brk, 160 bsearch, 160 
cache, 160 cap, 160 chdir, 160 chmod, 160 chown, 160 chroot, 160 clock, 160 
clone, 160 context, 160 copy-file, 160 cpu, 160 cpu-online, 160 crypt, 160 
daemon, 160 dccp, 160 dentry, 160 dir, 160 dirdeep, 160 dnotify, 160 dup, 160 
epoll, 160 eventfd, 160 exec, 160 fallocate, 160 fanotify, 160 fault, 160 
fcntl, 160 fiemap, 160 fifo, 160 filename, 160 flock, 160 fork, 160 fp-error, 
160 fstat, 160 full, 160 futex, 160 get, 160 getdent, 160 getrandom, 160 
handle, 160 hdd, 160 heapsort, 160 hsearch, 160 icache, 160 icmp-flood, 160 
inotify, 160 io, 160 iomix, 160 ioprio, 160 itimer, 160 kcmp, 160 key, 160 
kill, 160 klog, 160 lease, 160 link, 160 locka, 160 lockbus, 160 lockf, 160 
lockofd, 160 longjmp, 160 lsearch, 160 madvise, 160 malloc, 160 matrix, 160 
membarrier, 160 memcpy, 160 memfd, 160 mergesort, 160 mincore, 160 mknod, 160 
mlock, 160 mmap, 160 mmapfork, 160 mmapmany, 160 mq, 160 mremap, 160 msg, 160 
msync, 160 netlink-proc, 160 nice, 160 nop, 160 null, 160 numa, 160 oom-pipe, 
160 opcode, 160 open, 160 personality, 160 pipe, 160 poll, 160 procfs, 160 
pthread, 160 ptrace, 160 pty, 160 qsort, 160 quota, 160 rdrand, 160 readahead, 
160 remap, 160 rename, 160 resources, 160 rlimit, 160 rmap, 160 rtc, 160 
schedpolicy, 160 sctp, 160 seal, 160 seccomp, 160 seek, 160 sem, 160 sem-sysv, 
160 sendfile, 160 shm, 160 shm-sysv, 160 sigfd, 160 sigfpe, 160 sigpending, 160 
sigq, 160 sigsegv, 160 sigsuspend, 160 sleep, 160 sock, 160 sockfd, 160 
sockpair, 160 spawn, 160 splice, 160 stack, 160 stackmmap, 160 str, 160 stream, 
160 switch, 160 symlink, 160 sync-file, 160 sysfs, 160 sysinfo, 160 tee, 160 
timer, 160 timerfd, 160 tlb-shootdown, 160 tmpfs, 160 tsc, 160 tsearch, 160 
udp, 160 udp-flood, 160 unshare, 160 urandom, 160 userfaultfd, 160 utime, 160 
vecmath, 160 vfork, 160 vforkmany, 160 vm, 160 vm-rw, 160 vm-splice, 160 wait, 
160 wcs, 160 xattr, 160 yield, 160 zero, 160 zlib, 160 zombie
  stress-ng: info:  [3900] cache allocate: using built-in defaults as unable to 
determine cache details
  stress-ng: info:  [3900] cache allocate: default cache size: 2048K
  stress-ng: info:  [3907] stress-ng-atomic: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: info:  [3955] stress-ng-exec: running as root, won't run test.
  stress-ng: info:  [3999] stress-ng-icache: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: info:  [4040] stress-ng-lockbus: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: info:  [4313] stress-ng-numa: system has 2 of a maximum 256 memory 
NUMA nodes
  stress-ng: info:  [4455] stress-ng-rdrand: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: fail:  

[Kernel-packages] [Bug 1751796] [NEW] zed process consumming 100% cpu

[Scott Moser]

Public bug reported:

I logged in this morning and found system kind of sluggish.
A 'top' showed 'zed' process spinning 100% of a cpu.
I didn't feel like worrying about it, so I simply rebooted.

System came back up into the same state.
Running 'strace -p 2002' shows repeated:

ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: zfs-zed 0.7.5-1ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 26 09:34:59 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (949 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.zfs.zed.d.zed-functions.sh: [deleted]

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


** Tags: amd64 apport-bug bionic

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

Title:
  zed process consumming 100% cpu

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  I logged in this morning and found system kind of sluggish.
  A 'top' showed 'zed' process spinning 100% of a cpu.
  I didn't feel like worrying about it, so I simply rebooted.

  System came back up into the same state.
  Running 'strace -p 2002' shows repeated:

  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: zfs-zed 0.7.5-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 09:34:59 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (949 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.zfs.zed.d.zed-functions.sh: [deleted]

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

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

[Kernel-packages] [Bug 1751337] Re: BCM5719/tg3 loses connectivity due to missing heartbeats between fw and driver

[Manoj Iyer]

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

** Changed in: ubuntu-power-systems
   Status: New => Triaged

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Kernel Team (canonical-kernel-team)

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

Title:
  BCM5719/tg3 loses connectivity due to missing heartbeats between fw
  and driver

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

Bug description:
  User reported several nodes lost connectivity in several situations,
  for instance during the netboot, in which a flood of arp traffic
  happens due to multiple simultaneous boot across the cluster.

  No stack trace or message is seen, the device just stop receiving
  packets.

  In our attempts to reproduce the issue BCM5719 lost connectivity,
  always only under a heavy arp storm, in the follow situations:

  - changing MTU
  - interface configuration (with ifconfig or ip tool) 
  - netboot

  In order to fix the issue we need to include the upstream patches:

  1 - 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=748a240c5
  which reads: "tg3: Fix rx hang on MTU change with 5717/5719 "

  2 - 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=506b0a395
  which reads: "tg3: APE heartbeat changes"

  Considering that 18.04 is planned to use linux 4.15 we will need to
  backport only the second patch.

  I'll submit it to the ml and post here a reference.

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

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

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

[bugproxy]

--- Comment From cdead...@us.ibm.com 2018-02-26 09:32 EDT---
Paul confirm this is the same issue as #942 seen by Dac.

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

Title:
  Boston-LC:bos009:Ubuntu18.04: No /dev/disk/by-path link created for
  Samsung PM1725a NVMe 1.6TB and .8 TB disk drives

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

Bug description:
  == Comment: #1 - Application Cdeadmin 
  BMC/PNOR:
  =

  Firmware Revision : 00.37 IP address : 009.003.020.216
  Firmware Build Time : 20171201BMC MAC address : 0c:c4:7a:f4:4d:60
  PNOR Build Time : 20180117
  CPLD Version : B2.91.00

  
  Ubuntu 18.04:
  =

  
  root@bos1u1p1:~# uname -a
  Linux bos1u1p1 4.15.0-041500rc9-generic #201801212130 SMP Mon Jan 22 03:36:42 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  
  root@bos1u1p1:~# ls -l /dev/disk/by-path
  total 0
  lrwxrwxrwx 1 root root  9 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:0:0 -> 
../../sda
  lrwxrwxrwx 1 root root 10 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:0:0-part1 -> 
../../sda1
  lrwxrwxrwx 1 root root 10 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:0:0-part2 -> 
../../sda2
  lrwxrwxrwx 1 root root  9 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:1:0 -> 
../../sdb
  lrwxrwxrwx 1 root root  9 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:2:0 -> 
../../sdc
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218452-lun-0 -> ../../sdd
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218452-lun-1 -> ../../sde
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218452-lun-2 -> ../../sdf
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218452-lun-3 -> ../../sdg
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218453-lun-0 -> ../../sdh
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218453-lun-1 -> ../../sdi
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218453-lun-2 -> ../../sdj
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218453-lun-3 -> ../../sdk
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218452-lun-0 -> ../../sdl
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218452-lun-1 -> ../../sdm
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218452-lun-2 -> ../../sdn
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218452-lun-3 -> ../../sdo
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218453-lun-0 -> ../../sdp
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218453-lun-1 -> ../../sdq
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218453-lun-2 -> ../../sdr
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218453-lun-3 -> ../../sds
  root@bos1u1p1:~# 

  
  Problem Description:
  =
  - I setup my Boston LC system to run with Ubuntu 18.04

  - I tried to test out Samsung PM1725a NVMe 1.6TB and .8 TB disk drives
  on Boston LC system.

  - The disk drive plugged good into the system. However, after boot the
  system did not see the disk.

  - I tried with both Samsung PM1725a NVMe 1.6TB and with .8TB disk
  drives and none of them show up.

  - This disk type plan to supporte in Boston LC system so if the system
  does not recognize it then it is an issue.

  - I checked with Joe W. my team lead and he told me to open github
  issue for further investigation.

  
  root@bos1u1p1:~# ls -l /dev/disk/by-path
  total 0
  lrwxrwxrwx 1 root root  9 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:0:0 -> 
../../sda
  lrwxrwxrwx 1 root root 10 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:0:0-part1 -> 
../../sda1
  lrwxrwxrwx 1 root root 10 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:0:0-part2 -> 
../../sda2
  lrwxrwxrwx 1 root root  9 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:1:0 -> 
../../sdb
  lrwxrwxrwx 1 root root  9 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:2:0 -> 
../../sdc

  - If the disk is recognized then it will be
  pci-0003:01:00.0-scsi-0:2:3:0 -> ../../sdd but it's not.

  
  == Comment: #2 - Application Cdeadmin 
  --- Comment From dacng 2018-01-25 11:13:00 EDT ---
  You need to install NMVE HBA in your machine

  == Comment: #3 - Application Cdeadmin 
  --- Comment From nguyenp1 2018-01-26 15:35:40 EDT ---
  - I have NVME HBA adapter installed in the system and 2 Samsung PM1725a NVMe 
1.6TB and .8 TB disk drives  in the system.  The adapter and nvme drives show 
correctly.

  - However, the "ls -l /dev/disk/by-path" command did not show any nvme 
drives.  So it's new issue with 
  Ubuntu 18.04.  Without the PCI path the nvme disks can not be assigned to KVM 
guest.

  
  root@bos1u1p1:/dev/disk/by-path# ls 

[Kernel-packages] [Bug 1751798] [NEW] linux: -proposed tracker

[Kleber Sacilotto de Souza]

Public bug reported:

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

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-lbm
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-ports-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Artful)
 Importance: Medium
 Status: Confirmed


** Tags: artful kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.02.01-4 kernel-sru-master-kernel

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

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

** Tags added: artful

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-lbm
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-ports-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: 

[Kernel-packages] [Bug 1751497] Re: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2

[Seth Forshee]

The missing firmware seems to be something which can be extracted from
nvidia binary drivers but is not distributed via an open source license,
therefore we cannot distribute the firmware in linux-firmware.

https://nouveau.freedesktop.org/wiki/VideoAcceleration/

However, the feature connected to this firmware seems to be video decode
acceleration so I don't see any reason to think that the gdm3 crashes
are connected to these missing firmware messages.

Anyway, setting the linux-firmware task to "won't fix" as there's
nothing we can do about it.

** Changed in: linux-firmware (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Bionic daily build - nouveau: Direct firmware load for
  nouveau/nve7_fuc084  failed with error -2

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Won't Fix

Bug description:
  [  136.559610] nouveau :01:00.0: Direct firmware load for
  nouveau/nve7_fuc084 failed with error -2


  Hello, 
  from time to time I find this annoying messages in dmesg in various Ubuntu 
versions (I believe since 16.04 or 16.10 up until now, including Bionic Beaver 
daily build). From time to time, the gdm3 crashes. The current HW/SW setup will 
be described below. I cannot replicate the situation, but it happens. See the 
excerpt from dmesg output below. 

  
   [9.386558] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
  [9.399079] input: HDA NVidia HDMI/DP,pcm=3 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input12
  [9.399134] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input13
  [9.399208] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input14
  [9.399274] input: HDA NVidia HDMI/DP,pcm=9 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input15
  [   12.312741] r8169 :03:00.0 enp3s0: link up
  [   12.312748] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
  [   13.439863] rfkill: input handler disabled
  [   15.125569] nf_conntrack: default automatic helper assignment has been 
turned off for security reasons and CT-based  firewall rule not found. Use the 
iptables CT target to attach helpers instead.
  [  136.559610] nouveau :01:00.0: Direct firmware load for 
nouveau/nve7_fuc084 failed with error -2
  [  136.559618] nouveau :01:00.0: Direct firmware load for 
nouveau/nve7_fuc084d failed with error -2
  [  136.559619] nouveau :01:00.0: msvld: unable to load firmware data
  [  136.559622] nouveau :01:00.0: msvld: init failed, -19
  [ 1376.746130] lp: driver loaded but no devices found
  [ 1376.756790] st: Version 20160209, fixed bufsize 32768, s/g segs 256
  [ 1381.398605] do_IRQ: 1.37 No irq handler for vector
  rr

  HW setup: 
  Asrock Extreme 6 Z97
  Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz, 3563 MHz
  nVidia GK107 [GeForce GT 640]

  SW setup: 
  Linux bionic 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  root@bionic:~# lsmod | grep nouveau
  nouveau  1716224  5
  i2c_algo_bit   16384  1 nouveau
  ttm   106496  1 nouveau
  drm_kms_helper167936  1 nouveau
  mxm_wmi16384  1 nouveau
  drm   401408  8 nouveau,ttm,drm_kms_helper
  wmi24576  2 mxm_wmi,nouveau
  video  40960  1 nouveau

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

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

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

[bugproxy]

--- Comment From naveed...@in.ibm.com 2018-02-26 08:18 EDT---
(In reply to comment #24)
> Hi.
>
> As of now, the package is only ready for bionic, so this would need to be
> tested on bionic. Also, there is a problem on some of the KPTI kernels that
> includes 4.13 and 4.4 (but not the current 4.15 on bionic). This problem
> requires a package that is now on my ppa, no you will need to install
> makedumpfile from that.
>
> As this patch would be required for any xenial backport, I am requesting
> that you test it on bionic right now, with 4.13 kernel. Otherwise, I can't
> push something that is not tested on real ppc64el hardware to xenial. Can
> you do that?
>
> Thank you very much.
> Cascardo.

Thank you Cascardo for the reply,

We tested in couple of systems with 512GB RAM and we are able to use
your makedumpfile to dump the vmcore on  4.13.0-32-generic kernel on
Bionic.

==console log===

# dpkg -s makedumpfile
Package: makedumpfile
Status: install ok installed
Priority: optional
Section: devel
Installed-Size: 493
Maintainer: Louis Bouchard 
Architecture: ppc64el
Version: 1:1.6.3-1ubuntu1
Replaces: kdump-tools (<< 1.3.4-1~)
Depends: libc6 (>= 2.17), libdw1 (>= 0.143), libelf1 (>= 0.142), liblzo2-2, 
zlib1g (>= 1:1.2.0), perl:any
Recommends: crash, kexec-tools
Description: VMcore extraction tool
This program is used to extract a subset of the memory available either
via /dev/mem or /proc/vmcore (for crashdumps). It is used to get memory
images without extra unneeded information (zero pages, userspace programs,
etc).

Starting Kernel crash dump capture service...
[   26.303566] kdump-tools[1369]: Starting kdump-tools:  * running makedumpfile 
-c -d 31 /proc/vmcore /var/crash/201802260805/dump-incomplete
Copying data  : [100.0 %] |   eta: 
0s
[   57.183844] kdump-tools[1369]: The dumpfile is saved to 
/var/crash/201802260805/dump-incomplete.
[   57.183934] kdump-tools[1369]: makedumpfile Completed.
[   57.194154] kdump-tools[1369]:  * kdump-tools: saved vmcore in 
/var/crash/201802260805
[   60.095854] kdump-tools[1369]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201802260805/dmesg.201802260805
[   60.135142] kdump-tools[1369]: The dmesg log is saved to 
/var/crash/201802260805/dmesg.201802260805.
[   60.135301] kdump-tools[1369]: makedumpfile Completed.
[   60.135439] kdump-tools[1369]:  * kdump-tools: saved dmesg content in 
/var/crash/201802260805
[   60.446625] kdump-tools[1369]: Mon, 26 Feb 2018 08:06:14 -0500
[   60.736484] kdump-tools[1369]: Rebooting.
===

Can you point this makedumpfile over web link which we can wget to
install it on 16.04.4 (reason we are asking this is, we will be doing
hardware certifications and kdump test will fail on 16.04.4)

We request for your comment on inclusion of this version makedumpfile on
16.04.4 after we test it.

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

Title:
  update makedumpfile tool version to v1.6.3

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  New upstream kernel versions, as those in linux-hwe package, require a newer 
makedumpfile to be supported. Otherwise, all copies fallback to copying the 
entire memory.

  [Test case]
  kdump-tools has been installed, system rebooted, then crash trigerred and 
verified that a small dump file was present on /var/crash/. Tested on amd64 and 
ppc64le.

  [Regression potential]
  Many other bug fixes have been included in the latest version of the package. 
The changes are supposed to fix these bugs, and have been tested as well. 
However, as the total of changes is not trivial, there is impact of regression 
that has been minimized by the tests done. Regression potential of not 
supporting older kernels has been tested with the kernels shipped on xenial and 
artful as well.


  
  

  == Comment: #0 - Hari Krishna Bathini  - 2018-01-30 
10:46:53 ==
  ---Problem Description---
  update makedumpfile to latest version v1.6.3 that officially supports
  up to kernel version 4.14.8. Since makedumpfile is inherently backward 
compatible,
  this would not break existing functionality..

  Contact Information = hbath...@in.ibm.com

  ---uname output---
  na

  Machine Type = na

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   makedumpfile reports ""The kernel version is not supported" while generating 
vmcore
  Also, there is a possibility of bogus address translations in makedumpfile 
tool with
  missing upstream patches. Can't be so sure without an exhaustive testing. 
Instead,
  it would be a good idea to go with the version which officially supports the 
kernel
  version 

[Kernel-packages] [Bug 1751718] Re: Unable to create Xenial KVM with uvtool on Cavium ThunderX ARM64 system

[Robie Basak]

It's not an issue for _uvtool itself_ until the hardware is enabled and
functional in libvirt directly, and the specific Ubuntu image you need
(Xenial) works against libvirt in the Ubuntu release you need. So please
leave the bug status for uvtool Incomplete until that is done.

> What detail I could provide?

You're in the wrong place here. I suggest you follow this up internally
within Canonical to find an engineer who can work on it for you.

** Changed in: uvtool
   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/1751718

Title:
  Unable to create Xenial KVM with uvtool on Cavium ThunderX ARM64
  system

Status in uvtool:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With a Cavium ThunderX system deployed with Bionic, if you try to create a 
Xenial KVM, this tool will failed with:
uvt-kvm: error: timed out waiting for dnsmasq lease for 52:54:00:32:a2:f7

  Steps:
sudo uvt-simplestreams-libvirt sync release=xenial arch=arm64
sudo uvt-kvm create kvm-test release=xenial arch=arm64
sudo uvt-kvm wait bjf-test --insecure

  Note that it works with release=artful.

  
  With a Cavium ThunderX system deployed with Artful, the behaviour is 
different, this tool will failed with the KVM creation no matter if you're 
trying with Xenial or Artful:
uvt-kvm: error: libvirt: unsupported configuration: ACPI requires UEFI on 
this architecture

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: User Name 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 26 03:32 seq
   crw-rw 1 root audio 116, 33 Feb 26 03:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: arm64
  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:
  CurrentDmesg:
   
  Date: Mon Feb 26 06:20:28 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 EFI VGA
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=ddcb8b36-6267-4392-a1f9-74d9203b742e ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.171
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
  dmi.product.family: Default string
  dmi.product.name: ThunderX CRB
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cavium

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

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

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

[bugproxy]

--- Comment From maur...@br.ibm.com 2018-02-26 07:39 EDT---
FYI I've submitted the patch to the mail list: 
https://lists.ubuntu.com/archives/kernel-team/2018-February/090372.html

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

Title:
  BCM5719/tg3 loses connectivity due to missing heartbeats between fw
  and driver

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

Bug description:
  User reported several nodes lost connectivity in several situations,
  for instance during the netboot, in which a flood of arp traffic
  happens due to multiple simultaneous boot across the cluster.

  No stack trace or message is seen, the device just stop receiving
  packets.

  In our attempts to reproduce the issue BCM5719 lost connectivity,
  always only under a heavy arp storm, in the follow situations:

  - changing MTU
  - interface configuration (with ifconfig or ip tool) 
  - netboot

  In order to fix the issue we need to include the upstream patches:

  1 - 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=748a240c5
  which reads: "tg3: Fix rx hang on MTU change with 5717/5719 "

  2 - 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=506b0a395
  which reads: "tg3: APE heartbeat changes"

  Considering that 18.04 is planned to use linux 4.15 we will need to
  backport only the second patch.

  I'll submit it to the ml and post here a reference.

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

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

[Kernel-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)

[Alberto Milone]

It seems like the kernel and the nvidia driver weren't built using the
same compiler.

Please, either ssh into your machine, or press CTRL+ALT+F2 and do the
following:

1) Make sure security updates are enabled, and update your system ("apt-
cache policy gcc-5" should report 5.4.0-6ubuntu1~16.04.9 on Xenial)

2) Make sure no driver from NVIDIA's website is installed. If it is,
please uninstall it first.

3) When gcc-5 is updated, re-install the nvidia package from the archive:
sudo apt-get install --reinstall nvidia-384 (or nvidia-340)

4) Restart your computer.

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04)

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  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.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  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: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Kernel-packages] [Bug 1748638] Re: System freezing

[Ondrej Manhal]

So i first tried to change from Wayland to Xorg session and it looks
like it helped. No more freezing now.

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

Title:
  System freezing

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  System completely freezes quite frequently, not responding to any
  action nor key combination. I have to long press the power button to
  reboot the system or remove the battery.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ondra  1891 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Feb 10 15:56:56 2018
  HibernationDevice: RESUME=UUID=5e25406d-d414-dbcf-2b96-f5139433cc2b
  InstallationDate: Installed on 2017-12-26 (45 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 20F1001YMC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=871d7486-df77-4e2e-a7d2-47938e1b1773 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2018-01-12 (28 days ago)
  dmi.bios.date: 11/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1HET70W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20F1001YMC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1HET70W(1.34):bd11/13/2017:svnLENOVO:pn20F1001YMC:pvrThinkPadL560:rvnLENOVO:rn20F1001YMC:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L560
  dmi.product.name: 20F1001YMC
  dmi.product.version: ThinkPad L560
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1746174] Re: Error in CPU frequency reporting when nominal and min pstates are same (cpufreq)

[Dimitri John Ledkov]

The bug is in progress, thus the fix for this issues is not yet available for 
testing.
When it is available, there will be a comment on this bug report, calling for 
testing and listing exact version number of the kernel which includes the fix.

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

Title:
  Error in CPU frequency reporting when nominal and min pstates are same
  (cpufreq)

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

Bug description:
  
  == SRU Justification ==
  Commit 09ca4c9b5958 introduced a bug in v4.8-rc2.  The bug is that
  an error happens in CPU frequency reporting when nominal and min pstates
  are the same (cpufreq).  Commit 3fa4680b8 fixes this issue.

  Commit 3fa4680b8 is in mailine as of v4.16-rc1 and has been cc'd to
  upstream stable.

  == Fix ==
  commit 3fa4680b860bf48b437d6a2c039789c4abe202ae
  Author: Shilpasri G Bhat 
  Date:   Fri Jan 12 12:43:53 2018 +0530

  cpufreq: powernv: Dont assume distinct pstate values for nominal
  and pmin

  == Regression Potential ==
  Low.  This commit been cc'd to upstream stable, so it has had additional 
  upstream review.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  
  == Comment: #0 - Shilpasri G. Bhat
  +++ This bug was initially created as a clone of Bug #163527 +++

  ---Problem Description---
  Error in CPU frequency reporting when nominal and min pstates are same

  The patch for this issue is accepted to linux-next as

  3fa4680b860bf48b437d6a2c039789c4abe202ae
  cpufreq: powernv: Dont assume distinct pstate values for nominal and pmin

  Some OpenPOWER boxes can have same pstate values for nominal and
  pmin pstates. In these boxes the current code will not initialize
  'powernv_pstate_info.min' variable and result in erroneous CPU
  frequency reporting. This patch fixes this problem.

  Fixes: 09ca4c9b5958 (cpufreq: powernv: Replacing pstate_id with frequency 
table index)
  Reported-by: Alvin Wang 
  Signed-off-by: Shilpasri G Bhat 
  Acked-by: Viresh Kumar 
  Cc: 4.8+  # 4.8+
  Signed-off-by: Rafael J. Wysocki 

  https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-
  pm.git/commit/drivers/cpufreq/powernv-cpufreq.c?h=linux-
  next=3fa4680b860bf48b437d6a2c039789c4abe202ae

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

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

[Kernel-packages] [Bug 1746299] Re: update makedumpfile tool version to v1.6.3

[Thadeu Lima de Souza Cascardo]

Hi.

As of now, the package is only ready for bionic, so this would need to
be tested on bionic. Also, there is a problem on some of the KPTI
kernels that includes 4.13 and 4.4 (but not the current 4.15 on bionic).
This problem requires a package that is now on my ppa, no you will need
to install makedumpfile from that.

As this patch would be required for any xenial backport, I am requesting
that you test it on bionic right now, with 4.13 kernel. Otherwise, I
can't push something that is not tested on real ppc64el hardware to
xenial. Can you do that?

Thank you very much.
Cascardo.

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

Title:
  update makedumpfile tool version to v1.6.3

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  New upstream kernel versions, as those in linux-hwe package, require a newer 
makedumpfile to be supported. Otherwise, all copies fallback to copying the 
entire memory.

  [Test case]
  kdump-tools has been installed, system rebooted, then crash trigerred and 
verified that a small dump file was present on /var/crash/. Tested on amd64 and 
ppc64le.

  [Regression potential]
  Many other bug fixes have been included in the latest version of the package. 
The changes are supposed to fix these bugs, and have been tested as well. 
However, as the total of changes is not trivial, there is impact of regression 
that has been minimized by the tests done. Regression potential of not 
supporting older kernels has been tested with the kernels shipped on xenial and 
artful as well.


  
  

  == Comment: #0 - Hari Krishna Bathini  - 2018-01-30 
10:46:53 ==
  ---Problem Description---
  update makedumpfile to latest version v1.6.3 that officially supports
  up to kernel version 4.14.8. Since makedumpfile is inherently backward 
compatible,
  this would not break existing functionality..

  Contact Information = hbath...@in.ibm.com

  ---uname output---
  na

  Machine Type = na

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   makedumpfile reports ""The kernel version is not supported" while generating 
vmcore
  Also, there is a possibility of bogus address translations in makedumpfile 
tool with
  missing upstream patches. Can't be so sure without an exhaustive testing. 
Instead,
  it would be a good idea to go with the version which officially supports the 
kernel
  version in question.

  Userspace tool common name: makedumpfile

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: makedumpfile

  Userspace tool obtained from project website:  na

  *Additional Instructions for hbath...@in.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #1 - Hari Krishna Bathini  - 2018-01-30 
10:49:13 ==
  With kernel version updated to 4.13.0, please update makedumpfile tool
  version to 1.6.3 which officially supports up to kernel version 4.14.8 [1].

  Thanks
  Hari

  [1]
  http://lists.infradead.org/pipermail/kexec/2018-January/019853.html

  This needs to be tagged for both 16.04.4 & 18.04 releases

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

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

[Kernel-packages] [Bug 1751718] Re: Unable to create Xenial KVM with uvtool on Cavium ThunderX ARM64 system

[Po-Hsu Lin]

Hi Robie,

I am not sure which case applies, we use uvtool for the KVM smoke test for SRU 
regression-tests on all the kernels.
It a bit wired that this is working for Artful image but not with the Xenial 
image.
What detail I could provide?

Thanks

** Changed in: uvtool
   Status: Incomplete => New

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

Title:
  Unable to create Xenial KVM with uvtool on Cavium ThunderX ARM64
  system

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

Bug description:
  With a Cavium ThunderX system deployed with Bionic, if you try to create a 
Xenial KVM, this tool will failed with:
uvt-kvm: error: timed out waiting for dnsmasq lease for 52:54:00:32:a2:f7

  Steps:
sudo uvt-simplestreams-libvirt sync release=xenial arch=arm64
sudo uvt-kvm create kvm-test release=xenial arch=arm64
sudo uvt-kvm wait bjf-test --insecure

  Note that it works with release=artful.

  
  With a Cavium ThunderX system deployed with Artful, the behaviour is 
different, this tool will failed with the KVM creation no matter if you're 
trying with Xenial or Artful:
uvt-kvm: error: libvirt: unsupported configuration: ACPI requires UEFI on 
this architecture

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: User Name 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 26 03:32 seq
   crw-rw 1 root audio 116, 33 Feb 26 03:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: arm64
  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:
  CurrentDmesg:
   
  Date: Mon Feb 26 06:20:28 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 EFI VGA
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=ddcb8b36-6267-4392-a1f9-74d9203b742e ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.171
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
  dmi.product.family: Default string
  dmi.product.name: ThunderX CRB
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cavium

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

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

[Kernel-packages] [Bug 1750379] Re: Distortion Realtek ALC887

[fleamour]

I have installed a PCI soundcard & it demonstrates same behavior. With
amplification off, volume at 100%.

Turning sound down seems to cure, but obviously this is not loud
enough!?!

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

Title:
  Distortion Realtek ALC887

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Sounds can distort even when not amplified. Amplification worked well
  for years before recent PulseAudio update. The audio is Realtek ALC887
  under an IntelG41 Chipset with GA-G41M-Combo main board;

  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  I am seeking to engage upstream for April LTS release. Windows have
  abandoned this esoteric hardware! Please Ubuntu! Keep a C2D user
  going!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fleamour   1049 F pulseaudio
   /dev/snd/controlC2:  fleamour   1049 F pulseaudio
   /dev/snd/controlC0:  fleamour   1049 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 19 13:54:33 2018
  InstallationDate: Installed on 2018-02-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FB
  dmi.board.name: G41M-Combo
  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.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41M-Combo
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

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

[bugproxy]

--- Comment From shriy...@in.ibm.com 2018-02-26 06:09 EDT---
Hi ,
Can you please let us know in which build the fix is available ?

I am able to see issue on :

root@ltc-boston27:~# dmesg | grep freq
[0.00] time_init: decrementer frequency = 512.00 MHz
[0.00] time_init: processor frequency   = 2134.00 MHz
[2.159457] powernv-cpufreq: cpufreq pstate min 98 nominal 98 max 0
[2.159459] powernv-cpufreq: Workload Optimized Frequency is enabled in the 
platform
[2.164178] powernv-cpufreq: pstate 97 is out of bound

ubuntu@ltc-boston27:~$ uname -a
Linux ltc-boston27 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:21:52 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux

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

Title:
  Error in CPU frequency reporting when nominal and min pstates are same
  (cpufreq)

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

Bug description:
  
  == SRU Justification ==
  Commit 09ca4c9b5958 introduced a bug in v4.8-rc2.  The bug is that
  an error happens in CPU frequency reporting when nominal and min pstates
  are the same (cpufreq).  Commit 3fa4680b8 fixes this issue.

  Commit 3fa4680b8 is in mailine as of v4.16-rc1 and has been cc'd to
  upstream stable.

  == Fix ==
  commit 3fa4680b860bf48b437d6a2c039789c4abe202ae
  Author: Shilpasri G Bhat 
  Date:   Fri Jan 12 12:43:53 2018 +0530

  cpufreq: powernv: Dont assume distinct pstate values for nominal
  and pmin

  == Regression Potential ==
  Low.  This commit been cc'd to upstream stable, so it has had additional 
  upstream review.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  
  == Comment: #0 - Shilpasri G. Bhat
  +++ This bug was initially created as a clone of Bug #163527 +++

  ---Problem Description---
  Error in CPU frequency reporting when nominal and min pstates are same

  The patch for this issue is accepted to linux-next as

  3fa4680b860bf48b437d6a2c039789c4abe202ae
  cpufreq: powernv: Dont assume distinct pstate values for nominal and pmin

  Some OpenPOWER boxes can have same pstate values for nominal and
  pmin pstates. In these boxes the current code will not initialize
  'powernv_pstate_info.min' variable and result in erroneous CPU
  frequency reporting. This patch fixes this problem.

  Fixes: 09ca4c9b5958 (cpufreq: powernv: Replacing pstate_id with frequency 
table index)
  Reported-by: Alvin Wang 
  Signed-off-by: Shilpasri G Bhat 
  Acked-by: Viresh Kumar 
  Cc: 4.8+  # 4.8+
  Signed-off-by: Rafael J. Wysocki 

  https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-
  pm.git/commit/drivers/cpufreq/powernv-cpufreq.c?h=linux-
  next=3fa4680b860bf48b437d6a2c039789c4abe202ae

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

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

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

[bugproxy]

--- Comment From naveed...@in.ibm.com 2018-02-26 06:02 EDT---
(In reply to comment #21)
> Tested 1:1.5.9-5ubuntu0.6  on 4.13.0-36-generic 16.04.4 .
> Makedumpfile fails s/while/during/ kdump and kdump falls back to cp.
>
> # dpkg -s makedumpfile
> Package: makedumpfile
> Status: install ok installed
> Priority: optional
> Section: devel
> Installed-Size: 425
> Maintainer: Ubuntu Developers 
> Architecture: ppc64el
> Version: 1:1.5.9-5ubuntu0.6
> Replaces: kdump-tools (<< 1.3.4-1~)
> Depends: libc6 (>= 2.17), libdw1 (>= 0.143), libelf1 (>= 0.142), liblzo2-2,
> zlib1g (>= 1:1.2.0), perl
> Recommends: crash, kexec-tools
> Description: VMcore extraction tool
>  This program is used to extract a subset of the memory available either
>  via /dev/mem or /proc/vmcore (for crashdumps). It is used to get memory
>  images without extra unneeded information (zero pages, userspace programs,
>  etc).
> Original-Maintainer: Louis Bouchard 

===console log===
27.528264] kdump-tools[2637]: Starting kdump-tools:  * running makedumpfile -c 
-d 31 /proc/vmcore /var/crash/201802260113/dump-incomplete
Checking for memory holes  : [100.0 %] |/usr/sbin/kdump-config: line 
595:  2714 Segmentation fault  makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
[   27.648216] kdump-tools[2637]:  * kdump-tools: makedumpfile failed, falling 
back to 'cp'
[   94.724887] kdump-tools[2637]:  * kdump-tools: saved vmcore in 
/var/crash/201802260113
[   95.548243] kdump-tools[2637]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201802260113/dmesg.201802260113
[   95.662597] kdump-tools[2637]: The kernel version is not supported.
[   95.663151] kdump-tools[2637]: The makedumpfile operation may be incomplete.
[   95.663574] kdump-tools[2637]: The dmesg log is saved to 
/var/crash/201802260113/dmesg.201802260113.
[   95.663992] kdump-tools[2637]: makedumpfile Completed.
[   95.664296] kdump-tools[2637]:  * kdump-tools: saved dmesg content in 
/var/crash/201802260113
[   95.749509] kdump-tools[2637]: Mon, 26 Feb 2018 01:14:41 -0600
[   95.812644] kdump-tools[2637]: Rebooting.

# ls -lhrt /var/crash/201802260113/
total 4.9G
-r 1 root root 253G Feb 26 01:14 vmcore.201802260113
-rw--- 1 root root 103K Feb 26 01:14 dmesg.201802260113

vmcore size is of RAM size, makedumpfile was failure on 16.04.4

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

Title:
  update makedumpfile tool version to v1.6.3

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  New upstream kernel versions, as those in linux-hwe package, require a newer 
makedumpfile to be supported. Otherwise, all copies fallback to copying the 
entire memory.

  [Test case]
  kdump-tools has been installed, system rebooted, then crash trigerred and 
verified that a small dump file was present on /var/crash/. Tested on amd64 and 
ppc64le.

  [Regression potential]
  Many other bug fixes have been included in the latest version of the package. 
The changes are supposed to fix these bugs, and have been tested as well. 
However, as the total of changes is not trivial, there is impact of regression 
that has been minimized by the tests done. Regression potential of not 
supporting older kernels has been tested with the kernels shipped on xenial and 
artful as well.


  
  

  == Comment: #0 - Hari Krishna Bathini  - 2018-01-30 
10:46:53 ==
  ---Problem Description---
  update makedumpfile to latest version v1.6.3 that officially supports
  up to kernel version 4.14.8. Since makedumpfile is inherently backward 
compatible,
  this would not break existing functionality..

  Contact Information = hbath...@in.ibm.com

  ---uname output---
  na

  Machine Type = na

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   makedumpfile reports ""The kernel version is not supported" while generating 
vmcore
  Also, there is a possibility of bogus address translations in makedumpfile 
tool with
  missing upstream patches. Can't be so sure without an exhaustive testing. 
Instead,
  it would be a good idea to go with the version which officially supports the 
kernel
  version in question.

  Userspace tool common name: makedumpfile

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: makedumpfile

  Userspace tool obtained from project website:  na

  *Additional Instructions for hbath...@in.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #1 - Hari Krishna Bathini  - 2018-01-30 
10:49:13 ==
  With kernel version updated to 4.13.0, please update makedumpfile tool
  version to 1.6.3 which 

[Kernel-packages] [Bug 1751718] Re: Unable to create Xenial KVM with uvtool on Cavium ThunderX ARM64 system

[Robie Basak]

Thank you for filing this report.

uvtool is just a wrapper for libvirt. Either we need libvirt support
first, or this is a wishlist item for uvtool to support some customised
libvirt configuration on this particular hardware, in which case please
provide details.

** Changed in: uvtool
   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/1751718

Title:
  Unable to create Xenial KVM with uvtool on Cavium ThunderX ARM64
  system

Status in uvtool:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With a Cavium ThunderX system deployed with Bionic, if you try to create a 
Xenial KVM, this tool will failed with:
uvt-kvm: error: timed out waiting for dnsmasq lease for 52:54:00:32:a2:f7

  Steps:
sudo uvt-simplestreams-libvirt sync release=xenial arch=arm64
sudo uvt-kvm create kvm-test release=xenial arch=arm64
sudo uvt-kvm wait bjf-test --insecure

  Note that it works with release=artful.

  
  With a Cavium ThunderX system deployed with Artful, the behaviour is 
different, this tool will failed with the KVM creation no matter if you're 
trying with Xenial or Artful:
uvt-kvm: error: libvirt: unsupported configuration: ACPI requires UEFI on 
this architecture

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: User Name 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 26 03:32 seq
   crw-rw 1 root audio 116, 33 Feb 26 03:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: arm64
  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:
  CurrentDmesg:
   
  Date: Mon Feb 26 06:20:28 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 EFI VGA
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=ddcb8b36-6267-4392-a1f9-74d9203b742e ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.171
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
  dmi.product.family: Default string
  dmi.product.name: ThunderX CRB
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cavium

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

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

[Kernel-packages] [Bug 1643455] Re: Bluetooth does not work but WiFi does on Intel 7265 with both Ubuntu 16.04 and 16.10

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  Bluetooth does not work but WiFi does on Intel 7265 with both Ubuntu
  16.04 and 16.10

Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  On an Acer V3-574-7481 with built-in stock Intel 7265 wireless
  hardware, WiFi works perfectly but Bluetooth does not. The System
  Settings applet reports "No Bluetooth adapters found" and the option
  to enable Bluetooth is grayed out. However, Bluetooth hardware is
  reported by "dmesg" and a firmware patch file is applied automatically
  during boot.

  *Bluetooth works on this same machine booted into Windows 10.* The
  machine is dual-boot from separate partitions.

  # uname -a
  Linux galois-l 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:03:13 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  # head -6 /etc/os-release 
  NAME="Ubuntu"
  VERSION="16.10 (Yakkety Yak)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.10"
  VERSION_ID="16.10"

  # rfkill list
  1: acer-wireless: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  2: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no

  # lspci -knn | grep -A3 Net
  03:00.0 Network controller [0280]: Intel Corporation Wireless 7265 
[8086:095a] (rev 59)
  Subsystem: Intel Corporation Dual Band Wireless-AC 7265 [8086:5010]
  Kernel driver in use: iwlwifi
  Kernel modules: iwlwifi

  # lsusb
  Bus 001 Device 002: ID 8087:8001 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 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
  Bus 002 Device 003: ID 04f2:b526 Chicony Electronics Co., Ltd 
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  # hcitool dev
  Devices:

  # hcitool scan
  Device is not available: No such device

  # dmesg | grep -i bluetooth
  [   26.310459] Bluetooth: Core ver 2.21
  [   26.310476] Bluetooth: HCI device and connection manager initialized
  [   26.310478] Bluetooth: HCI socket layer initialized
  [   26.310480] Bluetooth: L2CAP socket layer initialized
  [   26.310483] Bluetooth: SCO socket layer initialized
  [   26.514833] Bluetooth: hci0: read Intel version: 370810011003110e00
  [   26.794565] Bluetooth: hci0: Intel Bluetooth firmware file: 
intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
  [   26.987853] Bluetooth: hci0: Intel Bluetooth firmware patch completed and 
activated
  [   39.604402] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   39.604404] Bluetooth: BNEP filters: protocol multicast
  [   39.604407] Bluetooth: BNEP socket layer initialized

  # locate ibt-hw
  /lib/firmware/intel/ibt-hw-37.7.10-fw-1.0.1.2d.d.bseq
  /lib/firmware/intel/ibt-hw-37.7.10-fw-1.0.2.3.d.bseq
  /lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq
  /lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
  /lib/firmware/intel/ibt-hw-37.7.bseq
  /lib/firmware/intel/ibt-hw-37.8.10-fw-1.10.2.27.d.bseq
  /lib/firmware/intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
  /lib/firmware/intel/ibt-hw-37.8.10-fw-22.50.19.14.f.bseq
  /lib/firmware/intel/ibt-hw-37.8.bseq

  # dpkg -S /lib/firmware/intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
  linux-firmware: /lib/firmware/intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq

  # dpkg -s linux-firmware | grep Version
  Version: 1.161

  This behavior was identical first under Ubuntu 16.04 and then under 16.10 
after upgrade. Command and response examples above are under 16.10 after 
upgrade.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Dependencies:
   
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2016-09-20 (293 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: linux-firmware 1.164.1
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (86 days ago)
  UserGroups: adm audio cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1509839] Re: segfault on start of live session in kactivitymanager / libqt5sql

[Colin Ian King]

** Changed in: linux (Ubuntu)
 Assignee: Colin Ian King (colin-king) => (unassigned)

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

Title:
  segfault on start of live session in kactivitymanager / libqt5sql

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've installed 15.10 Wily Werewolf to my USB stick via usb-creator and 
restart the laptop
  on boot, I'm asked for the language and if I want to install or try a live 
session
  I select try life session, the dialog disappears and the machine is frozen

  Next try:
  boot to selection dialog
  switch to console crtl+alt+F1 (takes a moment)
  issue alt+syreq+1 and alt+sysreq+t ... both answer "operation is disabled"
  switch back to X ctrl+alt+F7 & click try live session
  immediately switch back to console ctrl+alt+F1
  watchdog detects hard lockup a few seconds later
  see attached screenshot

  reproduced also in beta1 of wily werewolf ... a month ago I imagine
  the beta was still starting, as for bug #1492840. But I've reformated
  the stick meanwhile and cannot really guarantee, that I didn't confuse
  the multiple ISO's I tried in short time.

  version information:
  kernel 4.2.0-16-generic #19-Ubuntu (4.1.0-3-generic #3-Ubuntu)
  libqt5sql.so 5.4.2 (both)
  currently running Kubuntu 15.04 on the same hardware
  --- 
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kubuntu3331 F pulseaudio
   /dev/snd/controlC0:  kubuntu3331 F pulseaudio
  CasperVersion: 1.365
  DistroRelease: Ubuntu 15.10
  LiveMediaBuild: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Micro-Star International Co., Ltd. GE70 2OC\2OD\2OE
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1757IMS.520
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1757
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1757IMS.520:bd11/06/2014:svnMicro-StarInternationalCo.,Ltd.:pnGE702OC\2OD\2OE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1757:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GE70 2OC\2OD\2OE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Kernel-packages] [Bug 1647511] Re: During kernel upgrade, /usr/sbin/dkms falsely reports that initrd.img won't be created

[guysoft]

Getting this in Ubuntu 17.10 kernel 4.13.0-36-generic

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

Title:
  During kernel upgrade, /usr/sbin/dkms falsely reports that initrd.img
  won't be created

Status in DKMS:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in dkms package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu release
  ==

  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  Version of package
  ==

  dkms:
Installed: 2.2.0.3-2ubuntu11.3
Candidate: 2.2.0.3-2ubuntu11.3
Version table:
   *** 2.2.0.3-2ubuntu11.3 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages
  100 /var/lib/dpkg/status
   2.2.0.3-2ubuntu11 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages

  The problem
  ===

  When setting up `linux-image-4.4.0-53-generic`, the following warning
  appears three times:

  : Unable to find an initial ram disk that I know how to handle.
  Will not try to make an initrd.

  However, when setting up `linux-image-extra-4.4.0-53-generic`, the
  following message appears:

  update-initramfs: Generating /boot/initrd.img-4.4.0-53-generic

  The text "Unable to find an initial ram disk" appears in
  `/usr/sbin/dkms`, though it may appear elsewhere.

  What should happen
  ==

  The warning message should not appear.

  Messages when setting up the two packages
  =

  Setting up linux-image-4.4.0-53-generic (4.4.0-53.74) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-53-generic 
/boot/vmlinuz-4.4.0-53-generic
  run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-53-generic 
/boot/vmlinuz-4.4.0-53-generic
  : Unable to find an initial ram disk that I know how to handle.
  Will not try to make an initrd.
  : Unable to find an initial ram disk that I know how to handle.
  Will not try to make an initrd.
  : Unable to find an initial ram disk that I know how to handle.
  Will not try to make an initrd.
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-53-generic 
/boot/vmlinuz-4.4.0-53-generic
  update-initramfs: Generating /boot/initrd.img-4.4.0-53-generic
  run-parts: executing /etc/kernel/postinst.d/pm-utils 4.4.0-53-generic 
/boot/vmlinuz-4.4.0-53-generic
  run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 
4.4.0-53-generic /boot/vmlinuz-4.4.0-53-generic
  run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-53-generic 
/boot/vmlinuz-4.4.0-53-generic
  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-53-generic 
/boot/vmlinuz-4.4.0-53-generic
  Generating grub configuration file ...
  Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
  Found linux image: /boot/vmlinuz-4.4.0-53-generic
  Found initrd image: /boot/initrd.img-4.4.0-53-generic
  Found linux image: /boot/vmlinuz-4.4.0-51-generic
  Found initrd image: /boot/initrd.img-4.4.0-51-generic
  Found linux image: /boot/vmlinuz-4.4.0-47-generic
  Found initrd image: /boot/initrd.img-4.4.0-47-generic
  Adding boot menu entry for EFI firmware configuration
  done
  Setting up linux-image-extra-4.4.0-53-generic (4.4.0-53.74) ...
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-53-generic 
/boot/vmlinuz-4.4.0-53-generic
  run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-53-generic 
/boot/vmlinuz-4.4.0-53-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-53-generic 
/boot/vmlinuz-4.4.0-53-generic
  update-initramfs: Generating /boot/initrd.img-4.4.0-53-generic
  run-parts: executing /etc/kernel/postinst.d/pm-utils 4.4.0-53-generic 
/boot/vmlinuz-4.4.0-53-generic
  run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 
4.4.0-53-generic /boot/vmlinuz-4.4.0-53-generic
  run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-53-generic 
/boot/vmlinuz-4.4.0-53-generic
  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-53-generic 
/boot/vmlinuz-4.4.0-53-generic
  Generating grub configuration file ...
  Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
  Found linux image: /boot/vmlinuz-4.4.0-53-generic
  Found initrd image: /boot/initrd.img-4.4.0-53-generic
  Found linux image: /boot/vmlinuz-4.4.0-51-generic
  Found initrd image: /boot/initrd.img-4.4.0-51-generic
  Found linux image: /boot/vmlinuz-4.4.0-47-generic
  Found initrd image: /boot/initrd.img-4.4.0-47-generic
  

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Ubuntu cannot find or detect network adapters

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It's only on 4.15.0-10 kernel. 
  When I'm boot on 4.13.0-32 `ifconfig` or `ip a` detect wlan0 and eth0, but 
when I'm load 4.15.0-10 kernel `ifconfig` or `ip a` detects only lo.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rich   3980 F pulseaudio
  Date: Mon Feb 26 11:48:04 2018
  InstallationDate: Installed on 2009-11-30 (3009 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  MachineType: Dell Inc. Inspiron 1501
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=a776fd27-d39a-4d60-86e4-ebdef517688e ro text vesafb.invalid=1 
nosplash=1 vesafb.invalid=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.171
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-02-01 (24 days ago)
  dmi.bios.date: 12/07/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.3
  dmi.board.name: 0UW744
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.3:bd12/07/2007:svnDellInc.:pnInspiron1501:pvrNotSpecified:rvnDellInc.:rn0UW744:rvr:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 1501
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1751732] [NEW] Ubuntu cannot find or detect network adapters

[Pavel-II]

Public bug reported:

It's only on 4.15.0-10 kernel. 
When I'm boot on 4.13.0-32 `ifconfig` or `ip a` detect wlan0 and eth0, but when 
I'm load 4.15.0-10 kernel `ifconfig` or `ip a` detects only lo.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-10-generic 4.15.0-10.11
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  rich   3980 F pulseaudio
Date: Mon Feb 26 11:48:04 2018
InstallationDate: Installed on 2009-11-30 (3009 days ago)
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
MachineType: Dell Inc. Inspiron 1501
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=a776fd27-d39a-4d60-86e4-ebdef517688e ro text vesafb.invalid=1 
nosplash=1 vesafb.invalid=1
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-32-generic N/A
 linux-backports-modules-4.13.0-32-generic  N/A
 linux-firmware 1.171
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-02-01 (24 days ago)
dmi.bios.date: 12/07/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.6.3
dmi.board.name: 0UW744
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.3:bd12/07/2007:svnDellInc.:pnInspiron1501:pvrNotSpecified:rvnDellInc.:rn0UW744:rvr:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 1501
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug 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/1751732

Title:
  Ubuntu cannot find or detect network adapters

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It's only on 4.15.0-10 kernel. 
  When I'm boot on 4.13.0-32 `ifconfig` or `ip a` detect wlan0 and eth0, but 
when I'm load 4.15.0-10 kernel `ifconfig` or `ip a` detects only lo.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rich   3980 F pulseaudio
  Date: Mon Feb 26 11:48:04 2018
  InstallationDate: Installed on 2009-11-30 (3009 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  MachineType: Dell Inc. Inspiron 1501
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=a776fd27-d39a-4d60-86e4-ebdef517688e ro text vesafb.invalid=1 
nosplash=1 vesafb.invalid=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.171
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-02-01 (24 days ago)
  dmi.bios.date: 12/07/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.3
  dmi.board.name: 0UW744
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.3:bd12/07/2007:svnDellInc.:pnInspiron1501:pvrNotSpecified:rvnDellInc.:rn0UW744:rvr:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 1501
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1745081] Re: Add support for Realtek WiFi device [10ec:b822]

[erik ecoologic]

Hi @hui.wang,

I do have this wifi and it's not working,
I'm happy to help the debugging

$ lspci -nnk | grep 0280
03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. Device 
[10ec:b822]
$ uname -r
4.13.0-36-generic
$ apport-collect 1745081
Gtk-Message: GtkDialog mapped without a transient parent. This is 
discouraged.
dpkg-query: no packages found matching linux


Well, I guess you'll find all you need from the report I'm sending with 
apport-collect.

Thank you very much!

Thank you very much

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

Title:
   Add support for Realtek WiFi device [10ec:b822]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Triaged

Bug description:
  05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 
[10ec:b822]
Subsystem: Lenovo Device [17aa:b023]
Flags: fast devsel, IRQ 255
I/O ports at c000 [disabled] [size=256]
Memory at f200 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-b8-22-01
Capabilities: [158] Latency Tolerance Reporting
Capabilities: [160] L1 PM Substates

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

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

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

[erik ecoologic]

apport information

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

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

Title:
   Add support for Realtek WiFi device [10ec:b822]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Triaged

Bug description:
  05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 
[10ec:b822]
Subsystem: Lenovo Device [17aa:b023]
Flags: fast devsel, IRQ 255
I/O ports at c000 [disabled] [size=256]
Memory at f200 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-b8-22-01
Capabilities: [158] Latency Tolerance Reporting
Capabilities: [160] L1 PM Substates

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

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

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

[erik ecoologic]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1745081/+attachment/5063329/+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/1745081

Title:
   Add support for Realtek WiFi device [10ec:b822]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Triaged

Bug description:
  05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 
[10ec:b822]
Subsystem: Lenovo Device [17aa:b023]
Flags: fast devsel, IRQ 255
I/O ports at c000 [disabled] [size=256]
Memory at f200 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-b8-22-01
Capabilities: [158] Latency Tolerance Reporting
Capabilities: [160] L1 PM Substates

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

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

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

[erik ecoologic]

apport information

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

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

Title:
   Add support for Realtek WiFi device [10ec:b822]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Triaged

Bug description:
  05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 
[10ec:b822]
Subsystem: Lenovo Device [17aa:b023]
Flags: fast devsel, IRQ 255
I/O ports at c000 [disabled] [size=256]
Memory at f200 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-b8-22-01
Capabilities: [158] Latency Tolerance Reporting
Capabilities: [160] L1 PM Substates

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

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

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

[erik ecoologic]

apport information

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

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

Title:
   Add support for Realtek WiFi device [10ec:b822]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Triaged

Bug description:
  05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 
[10ec:b822]
Subsystem: Lenovo Device [17aa:b023]
Flags: fast devsel, IRQ 255
I/O ports at c000 [disabled] [size=256]
Memory at f200 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-b8-22-01
Capabilities: [158] Latency Tolerance Reporting
Capabilities: [160] L1 PM Substates

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

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

[Kernel-packages] [Bug 1745081] JournalErrors.txt

[erik ecoologic]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1745081/+attachment/5063320/+files/JournalErrors.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/1745081

Title:
   Add support for Realtek WiFi device [10ec:b822]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Triaged

Bug description:
  05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 
[10ec:b822]
Subsystem: Lenovo Device [17aa:b023]
Flags: fast devsel, IRQ 255
I/O ports at c000 [disabled] [size=256]
Memory at f200 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-b8-22-01
Capabilities: [158] Latency Tolerance Reporting
Capabilities: [160] L1 PM Substates

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

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

[Kernel-packages] [Bug 1745081] Re: Add support for Realtek WiFi device [10ec:b822]

[erik ecoologic]

ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ecoologic   1261 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 17.10
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=8702bcee-298c-4f62-949c-79932b378863
InstallationDate: Installed on 2018-02-25 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
IwConfig:
 enp2s0no wireless extensions.
 
 lono wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 13d3:3526 IMC Networks 
 Bus 001 Device 002: ID 04f2:b52b Chicony Electronics Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X705UDR
Package: linux-oem
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=061ff5cb-4898-4808-98b2-c5d75594f3fd ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-36-generic N/A
 linux-backports-modules-4.13.0-36-generic  N/A
 linux-firmware 1.169.3
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags:  wayland-session artful
Uname: Linux 4.13.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 08/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X705UDR.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X705UDR
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.:bvrX705UDR.300:bd08/29/2017:svnASUSTeKCOMPUTERINC.:pnX705UDR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX705UDR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X705UDR
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.


** Tags added: apport-collected artful 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/1745081

Title:
   Add support for Realtek WiFi device [10ec:b822]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Triaged

Bug description:
  05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 
[10ec:b822]
Subsystem: Lenovo Device [17aa:b023]
Flags: fast devsel, IRQ 255
I/O ports at c000 [disabled] [size=256]
Memory at f200 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-b8-22-01
Capabilities: [158] Latency Tolerance Reporting
Capabilities: [160] L1 PM Substates

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

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

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

[erik ecoologic]

apport information

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

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

Title:
   Add support for Realtek WiFi device [10ec:b822]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Triaged

Bug description:
  05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 
[10ec:b822]
Subsystem: Lenovo Device [17aa:b023]
Flags: fast devsel, IRQ 255
I/O ports at c000 [disabled] [size=256]
Memory at f200 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-b8-22-01
Capabilities: [158] Latency Tolerance Reporting
Capabilities: [160] L1 PM Substates

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

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

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

[erik ecoologic]

apport information

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

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

Title:
   Add support for Realtek WiFi device [10ec:b822]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Triaged

Bug description:
  05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 
[10ec:b822]
Subsystem: Lenovo Device [17aa:b023]
Flags: fast devsel, IRQ 255
I/O ports at c000 [disabled] [size=256]
Memory at f200 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-b8-22-01
Capabilities: [158] Latency Tolerance Reporting
Capabilities: [160] L1 PM Substates

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

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

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

[erik ecoologic]

apport information

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

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

Title:
   Add support for Realtek WiFi device [10ec:b822]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Triaged

Bug description:
  05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 
[10ec:b822]
Subsystem: Lenovo Device [17aa:b023]
Flags: fast devsel, IRQ 255
I/O ports at c000 [disabled] [size=256]
Memory at f200 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-b8-22-01
Capabilities: [158] Latency Tolerance Reporting
Capabilities: [160] L1 PM Substates

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

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

[Kernel-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)

[Paul Lieverse]

Had the same issue on 14.04 with HWE kernel.

Last Friday morning I got offered the -116 kernel - which broke the
nvidia driver module, forcing me to revert back to the -112 kernel.

Only today (not checked during the weekend) I got offered the compiler
update, from 4.8.4-2ubuntu1~14.04.3 to 4.8.4-2ubuntu1~14.04.4.

Didn't re-install the -116 kernel yet, but given other people's
experiences I trust that should now go fine.

However, it does show that there seems to be some dependency or
distribution issue between this kernel and the required compiler
version, offering the kernel update before the compiler update was
available, and not holding off the kernel update if the compiler update
isn't in place yet.

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04)

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  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.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  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: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

-- 
Mailing list: 

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

[erik ecoologic]

apport information

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

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

Title:
   Add support for Realtek WiFi device [10ec:b822]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Triaged

Bug description:
  05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 
[10ec:b822]
Subsystem: Lenovo Device [17aa:b023]
Flags: fast devsel, IRQ 255
I/O ports at c000 [disabled] [size=256]
Memory at f200 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-b8-22-01
Capabilities: [158] Latency Tolerance Reporting
Capabilities: [160] L1 PM Substates

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

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

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

[erik ecoologic]

apport information

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

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

Title:
   Add support for Realtek WiFi device [10ec:b822]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Triaged

Bug description:
  05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 
[10ec:b822]
Subsystem: Lenovo Device [17aa:b023]
Flags: fast devsel, IRQ 255
I/O ports at c000 [disabled] [size=256]
Memory at f200 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-b8-22-01
Capabilities: [158] Latency Tolerance Reporting
Capabilities: [160] L1 PM Substates

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

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

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

[erik ecoologic]

apport information

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

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

Title:
   Add support for Realtek WiFi device [10ec:b822]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Triaged

Bug description:
  05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 
[10ec:b822]
Subsystem: Lenovo Device [17aa:b023]
Flags: fast devsel, IRQ 255
I/O ports at c000 [disabled] [size=256]
Memory at f200 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-b8-22-01
Capabilities: [158] Latency Tolerance Reporting
Capabilities: [160] L1 PM Substates

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

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

[Kernel-packages] [Bug 1745081] AlsaInfo.txt

[erik ecoologic]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1745081/+attachment/5063317/+files/AlsaInfo.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/1745081

Title:
   Add support for Realtek WiFi device [10ec:b822]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Triaged

Bug description:
  05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 
[10ec:b822]
Subsystem: Lenovo Device [17aa:b023]
Flags: fast devsel, IRQ 255
I/O ports at c000 [disabled] [size=256]
Memory at f200 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-b8-22-01
Capabilities: [158] Latency Tolerance Reporting
Capabilities: [160] L1 PM Substates

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

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

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

[erik ecoologic]

apport information

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

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

Title:
   Add support for Realtek WiFi device [10ec:b822]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Triaged

Bug description:
  05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 
[10ec:b822]
Subsystem: Lenovo Device [17aa:b023]
Flags: fast devsel, IRQ 255
I/O ports at c000 [disabled] [size=256]
Memory at f200 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-b8-22-01
Capabilities: [158] Latency Tolerance Reporting
Capabilities: [160] L1 PM Substates

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

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

[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13

[Vivien GUEANT]

I have a significant memory leak after upgrading from previous 4.10
series HWE kernels to the new 4.13 HWE series for Ubuntu 16.04 server
with Ethernet controller Intel X710 for 10GbE SFP+

# dmesg | grep i40e
[1.625565] i40e: Intel(R) Ethernet Connection XL710 Network Driver - 
version 2.1.14-k
[1.625565] i40e: Copyright (c) 2013 - 2014 Intel Corporation.
[1.688509] i40e :02:00.0: fw 5.40.47690 api 1.5 nvm 5.40 0x80002d35 
18.0.17
[1.959126] i40e :02:00.0: MAC address: 3c:fd:fe:1a:1d:e0
[2.060021] i40e :02:00.0: PCI-Express: Speed 8.0GT/s Width x4
[2.060091] i40e :02:00.0: PCI-Express bandwidth available for this 
device may be insufficient for optimal performance.
[2.060096] i40e :02:00.0: Please move the device to a different PCI-e 
link with more lanes and/or higher transfer rate.
[2.085931] i40e :02:00.0: Features: PF-id[0] VFs: 64 VSIs: 66 QP: 8 RSS 
FD_ATR FD_SB NTUPLE DCB VxLAN Geneve PTP VEPA
[2.140793] i40e :02:00.1: fw 5.40.47690 api 1.5 nvm 5.40 0x80002d35 
18.0.17
[2.422817] i40e :02:00.1: MAC address: 3c:fd:fe:1a:1d:e2
[2.442684] i40e :02:00.1: PCI-Express: Speed 8.0GT/s Width x4
[2.442696] i40e :02:00.1: PCI-Express bandwidth available for this 
device may be insufficient for optimal performance.
[2.442715] i40e :02:00.1: Please move the device to a different PCI-e 
link with more lanes and/or higher transfer rate.
[2.443043] i40e :02:00.1: Features: PF-id[1] VFs: 64 VSIs: 66 QP: 8 RSS 
FD_ATR FD_SB NTUPLE DCB VxLAN Geneve PTP VEPA
[2.480205] i40e :02:00.0 enp2s0f0: renamed from eth1
[2.512183] i40e :02:00.1 enp2s0f1: renamed from eth0
[5.800514] i40e :02:00.0 enp2s0f0: NIC Link is Up, 10 Gbps Full Duplex, 
Flow Control: None

** Attachment added: "201802_nperf_memory-week.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408/+attachment/5063316/+files/201802_nperf_memory-week.png

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

Title:
  Servers going OOM after updating kernel from 4.10 to 4.13

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

Bug description:
  We are seeing this on multiple servers after upgrading from previous
  4.10 series HWE kernels to the new 4.13 HWE series. With the new
  kernel, free memory is continously decreasing at a high rate and the
  servers start swapping and finally OOMing services within days. With
  the 4.10 kernel, decrease of free memory is slower and stabilizes
  after a while.

  Latest kernel tested is linux-image-4.13.0-32-generic but the issue
  also affects older kernels from that series, tested back to linux-
  image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic.

  The servers are running as OpenStack controller nodes using either
  Ocata or Pike UCA plus ceph. See attached graph for the memory
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Feb  9 09:45:50 2018
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1751718

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

Title:
  Unable to create Xenial KVM with uvtool on Cavium ThunderX ARM64
  system

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

Bug description:
  With a Cavium ThunderX system deployed with Bionic, if you try to create a 
Xenial KVM, this tool will failed with:
uvt-kvm: error: timed out waiting for dnsmasq lease for 52:54:00:32:a2:f7

  Steps:
sudo uvt-simplestreams-libvirt sync release=xenial arch=arm64
sudo uvt-kvm create kvm-test release=xenial arch=arm64
sudo uvt-kvm wait bjf-test --insecure

  Note that it works with release=artful.

  
  With a Cavium ThunderX system deployed with Artful, the behaviour is 
different, this tool will failed with the KVM creation no matter if you're 
trying with Xenial or Artful:
uvt-kvm: error: libvirt: unsupported configuration: ACPI requires UEFI on 
this architecture

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: User Name 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 26 03:32 seq
   crw-rw 1 root audio 116, 33 Feb 26 03:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: arm64
  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:
  CurrentDmesg:
   
  Date: Mon Feb 26 06:20:28 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 EFI VGA
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=ddcb8b36-6267-4392-a1f9-74d9203b742e ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.171
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
  dmi.product.family: Default string
  dmi.product.name: ThunderX CRB
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cavium

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

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