[Kernel-packages] [Bug 1835939] Re: The 18.04 linux kernel hangs and crashes when shutting down a Windows 10 instance running under vmware

2019-07-15 Thread Seth Arnold
Thanks Scott, I've made the bug public.

There's a surprising number of crashes reported to the error tracker --
I wonder if your hardware is entirely stable? Have you run memtest86 or
memtest86+ recently? Is there anything in your smartctl output that
would indicate drive problems?

Thanks

** Information type changed from Private Security to Public Security

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

Title:
  The 18.04 linux kernel hangs and crashes when shutting down a Windows
  10 instance running under vmware

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is the second crash and the second time that I have reported this
  problem.  I apologize but I forgot to make a note of the bug number
  and can't seem to find it.

  My whoopsie number is

  
02aff7e0e154c826180cb958966df0a740c15d05305d3d9b6520f8fae51f25680fa7831afada8c542654d752a069fc813fcb29567e21d3c0f9b84d2a0147fdf3b

  I ran the "ubuntu-bug linux" command to send configuration
  information.  If I need to do something else, please let me know.

  VMware Workstation 15.1.0 build-13591040

  I have had the system hand once using Oracle's Virtual Box (i.e.
  exiting from Windows) but there was no crash.

  Let me know what other information I need to give you.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-54-generic 4.15.0-54.58
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  butler 3213 F pulseaudio
   /dev/snd/controlC1:  butler 3213 F pulseaudio
   /dev/snd/controlC0:  butler 3213 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Tue Jul  9 14:05:40 2019
  HibernationDevice: RESUME=UUID=81a753c1-bc6b-4040-8aff-c2495d989ba3
  InstallationDate: Installed on 2018-06-16 (387 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. CM6870
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=512M-:192M 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-54-generic N/A
   linux-backports-modules-4.15.0-54-generic  N/A
   linux-firmware 1.173.8
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0708
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CM6870
  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.:bvr0708:bd12/25/2012:svnASUSTeKCOMPUTERINC.:pnCM6870:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6870:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: Desktop
  dmi.product.name: CM6870
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1836476] Re: Binarypplication/x-rpm: bcmwl

2019-07-15 Thread Seth Arnold
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.

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

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

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


** Information type changed from Private Security to Public

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

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

Title:
  Binarypplication/x-rpm: bcmwl

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Binarypplication/x-rpm: bcmwl-kernel-source

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

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


[Kernel-packages] [Bug 1836982] Re: Touchpad Not Working

2019-07-18 Thread Seth Arnold
** Information type changed from Private Security to Public

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

Title:
  Touchpad Not Working

Status in linux package in Ubuntu:
  New

Bug description:
  My touchpad is not working. It cannot be a hardware issue as it is
  working when I switch to Windows. Your kind help is needed.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-54-generic 4.15.0-54.58
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ashish 3981 F...m pulseaudio
   /dev/snd/controlC0:  ashish 3981 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 18 06:37:19 2019
  HibernationDevice: RESUME=UUID=10d2974b-4ab6-4f1d-a960-50c42491bf7e
  InstallationDate: Installed on 2019-01-30 (168 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO INVALID
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic 
root=UUID=f666af41-f04f-404f-8108-5ac2993ef72e ro quiet splash acpi_osi= 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-54-generic N/A
   linux-backports-modules-4.15.0-54-generic  N/A
   linux-firmware 1.173.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K17763 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: INVALID
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN40WW:bd04/13/2018:svnLENOVO:pnINVALID:pvrINVALID:rvnLENOVO:rnINVALID:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrINVALID:
  dmi.product.family: IDEAPAD
  dmi.product.name: INVALID
  dmi.product.version: INVALID
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1743792] Re: kernel panic on ioctl(TUNSETIFF) with a dev name with '/'

2019-05-16 Thread Seth Arnold
Thanks for commenting on this issue. I'm sorry we lost track of proper
public attribution for the discovery.

Yes, you may use this CVE publicly. (And thanks for asking.)

** Information type changed from Private Security to Public Security

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

Title:
  kernel panic on ioctl(TUNSETIFF) with a dev name with '/'

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Executing the attached program with either `sudo` or `unshare -r -n` causes 
kernel panic.
  Mostly running just once is enough to hit the issue, but not 100% 
deterministic.

  [  121.718035] BUG: unable to handle kernel NULL pointer dereference at   
(null)   
  [  121.726006] IP:   (null)
  [  121.729333] PGD 0   
  [  121.729334] P4D 0   
  [  121.731445] 
  [  121.735149] Oops: 0010 [#1] SMP PTI 
  [  121.738747] Modules linked in: nf_conntrack_netlink nfnetlink xfrm_user 
xfrm_algo xt_addrtype xt_conntrack br_netfilter overlay xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 n
  f_nat nf_conntrack xt_tcpudp bridge stp llc ip6table_filter ip6_tables 
iptable_filter binfmt_misc zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) 
znvpair(PO) spl(O) ppdev input_leds mac_hid i2c_piix4 pvpanic parport_pc 
parport sb_edac serio_raw intel_rapl_perf
   ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear crct1
  0dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc  
  [  121.809474]  aesni_intel aes_x86_64 crypto_simd glue_helper cryptd psmouse 
virtio_net virtio_scsi   
  [  121.818453] CPU: 0 PID: 0 Comm: swapper/0 Tainted: P   O
4.13.0-25-generic #29-Ubuntu
  [  121.827338] Hardware name: Google Google Compute Engine/Google Compute 
Engine, BIOS Google 01/01/2011   
  [  121.836674] task: ad212480 task.stack: ad20
 
  [  121.842693] RIP: 0010:  (null)  
  [  121.846544] RSP: 0018:9e253fc03e80 EFLAGS: 00010206 
  [  121.851868] RAX:  RBX: 0100 RCX: 
0100   
  [  121.859111] RDX:  RSI:  RDI: 
   
  [  121.866438] RBP: 9e253fc03eb0 R08: fff8 R09: 
000f   
  [  121.873680] R10: 45fc5cc2 R11: 0edc6924 R12: 
9e253fc03ed0   
  [  121.880918] R13: 9e251a7ef140 R14:  R15: 
   
  [  121.888158] FS:  () GS:9e253fc0() 
knlGS:
  [  121.896377] CS:  0010 DS:  ES:  CR0: 80050033  
 
  [  121.902225] CR2:  CR3: 00035b60a003 CR4: 
001606f0   
  [  121.909463] DR0:  DR1:  DR2: 
   
  [  121.916699] DR3:  DR6: fffe0ff0 DR7: 
0400   
  [  121.923935] Call Trace: 
  [  121.926482]
  [  121.928599]  ? call_timer_fn+0x33/0x130 
  [  121.932539]  run_timer_softirq+0x40f/0x470  
  [  121.936738]  ? kvm_clock_get_cycles+0x1e/0x20   
  [  121.941195]  ? ktime_get+0x40/0xa0  
  [  121.944725]  ? native_apic_msr_write+0x2b/0x40  
  [  121.949359]  __do_softirq+0xde/0x2a5
  [  121.953040]  irq_exit+0xb6/0xc0 
  [  121.956290]  smp_apic_timer_interrupt+0x68/0x90 
  [  121.960922]  apic_timer_interrupt+0x9f/0xb0 
  [  121.965206]   
  [  121.967417] RIP: 0010:native_safe_halt+0x6/0x10 
  [  121.972058] RSP: 0018:ad203de0 EFLAGS: 0246 ORIG_RAX: 
ff10  
  [  121.979726] RAX: 0

[Kernel-packages] [Bug 1818552] Re: disable a.out support

2019-05-17 Thread Seth Arnold
Xenial:

$ grep AOUT !$
grep AOUT /boot/config-4.4.0-149-generic
# CONFIG_HAVE_AOUT is not set   

# CONFIG_IA32_AOUT is not set

Bionic:

$ grep AOUT /boot/config-4.15.0-51-generic  
  
# CONFIG_HAVE_AOUT is not set   

# CONFIG_IA32_AOUT is not set   



Sorry to say I don't have an a.out file to test with.

Thanks

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

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

Title:
  disable a.out support

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Won't Fix
Status in linux-hwe-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Won't Fix
Status in linux-hwe-edge source package in Trusty:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in linux-hwe-edge source package in Xenial:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-hwe-edge source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux-hwe-edge source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Fix Released
Status in linux-hwe-edge source package in Disco:
  Invalid

Bug description:
  Hello,

  I suggest we disable a.out support in our kernels. It's quite old,
  likely has security problems, and unlikely to have users.

  
  Here's a hand-filtered list of kernel configs that were returned from this 
list:

  grep -rl -e AOUT=m -e AOUT=y | sort -n

  I've selected what looks like the most recent kernels from among:
  precise
  trusty
  xenial
  bionic
  cosmic

  There is no disco because it's not on the kernel.ubuntu.com/kernel-
  config rsync source.

  Thanks

  precise/linux/3.2.0-126.169/i386-config.flavour.generic
  precise/linux/3.2.0-126.169/i386-config.flavour.generic-pae
  precise/linux/3.2.0-126.169/i386-config.flavour.lowlatency
  precise/linux/3.2.0-126.169/i386-config.flavour.virtual
  precise/linux/3.8.0-25.36/armel-config.flavour.omap4
  precise/linux/3.8.0-25.36/armhf-config.flavour.omap4
  precise/linux/3.8.0-25.36/i386-config.flavour.generic
  precise/linux/3.8.0-25.36/i386-config.flavour.lowlatency
  precise/linux-armadaxp/3.2.0-1687.114/i386-config.flavour.generic
  precise/linux-armadaxp/3.2.0-1687.114/i386-config.flavour.lowlatency
  precise/linux-lts-trusty/3.13.0-148.197~precise1/i386-config.flavour.generic
  
precise/linux-lts-trusty/3.13.0-148.197~precise1/i386-config.flavour.lowlatency
  precise/linux-ti-omap4/3.2.0-1504.131/i386-config.flavour.generic
  precise/linux-ti-omap4/3.2.0-1504.131/i386-config.flavour.lowlatency
  trusty/linux/3.13.0-148.197/i386-config.flavour.generic
  trusty/linux/3.13.0-148.197/i386-config.flavour.lowlatency
  trusty/linux-aws/4.4.0-1004.4/i386-config.flavour.generic
  trusty/linux-aws/4.4.0-1004.4/i386-config.flavour.lowlatency
  trusty/linux-lts-xenial/4.4.0-125.150~14.04.1/i386-config.flavour.generic
  trusty/linux-lts-xenial/4.4.0-125.150~14.04.1/i386-config.flavour.lowlatency
  xenial/linux/4.4.0-125.150/i386-config.flavour.generic
  xenial/linux/4.4.0-125.150/i386-config.flavour.lowlatency
  xenial/linux-aws/4.4.0-1055.64/i386-config.flavour.generic
  xenial/linux-aws/4.4.0-1055.64/i386-config.flavour.lowlatency
  xenial/linux-azure/4.13.0-1001.1/i386-config.flavour.generic
  xenial/linux-azure/4.13.0-1001.1/i386-config.flavour.lowlatency
  xenial/linux-euclid/4.4.0-9019.20/i386-config.flavour.generic
  xenial/linux-euclid/4.4.0-9019.20/i386-config.flavour.lowlatency
  xenial/linux-flo/3.4.0-5.19/i386-config.flavour.generic
  xenial/linux-flo/3.4.0-5.19/i386-config.flavour.lowlatency
  xenial/linux-flo/3.4.0-5.23/armhf-config.flavour.flo
  xenial/linux-gcp/4.10.0-1009.9/i386-config.flavour.generic
  xenial/linux-gcp/4.10.0-1009.9/i386-config.flavour.lowlatency
  xenial/linux-gcp/4.8.0-1002.2/i386-config.flavour.generic
  xenial/linux-gcp/4.8.0-1002.2/i386-config.flavour.lowlatency
  xenial/linux-gke/4.4.0-1034.34/i386-config.flavour.generic
  xenial/linux-gke/4.4.0-1034.34/i386-config.flavour.lowlatency
  xenial/linux-gke/4.4.0-1036.36/armhf-config.flavour.mako
  xenial/linux-goldfish/3.4.0-4.26/i386-config.flavour.generic
  xenial/linux-goldfish/3.4.0-4.26/i386-config.flavour.generic-pae
  xenial/linux-goldfish/3.4.0-4.26/i386-config.flavour.goldfish
  xenial/linux-goldfish/3.4.0-4.26/i386-config.flavour.lowlatency
  xeni

[Kernel-packages] [Bug 1830400] Re: ubuntu 19.04

2019-05-24 Thread Seth Arnold
What steps specifically do you have to do each boot?

Please run apport-collect 1830400 in order to run the automated data
collection for this bug report.

Thanks

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

Title:
  ubuntu 19.04

Status in linux package in Ubuntu:
  New

Bug description:
  ubuntu 19.04 does not load ethernet or wireless drivers on power up. I
  have to manually load ethernet drivers each time i powerup.

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

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


[Kernel-packages] [Bug 1830400] Re: ubuntu 19.04

2019-05-24 Thread Seth Arnold
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  ubuntu 19.04

Status in linux package in Ubuntu:
  New

Bug description:
  ubuntu 19.04 does not load ethernet or wireless drivers on power up. I
  have to manually load ethernet drivers each time i powerup.

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

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


Re: [Kernel-packages] [Bug 1818170] Re: xenial linux 4.4.0-143.169 ADT test failure [/proc/timer_list: Permission denied]

2019-03-19 Thread Seth Arnold
On Tue, Mar 19, 2019 at 09:46:38AM -, kenn wrote:
> I have that bug, i/o screenlet won't run because of insufficient
> permission. Will it be fixed in the 4.4.0-143 kernel?

This was an intentional change:

https://marc.info/?l=git-commits-head&m=151163650225215&w=2
https://lkml.org/lkml/2018/12/20/346

The file /proc/timer_list may be removed in the future:

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

Thanks

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

Title:
  xenial linux 4.4.0-143.169 ADT test failure [/proc/timer_list:
  Permission denied]

Status in QA Regression Testing:
  Fix Released
Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20190228_103241_6fdc6@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20190226_190740_8dbe6@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20190226_183159_8dbe6@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20190226_174407_8dbe6@/log.gz

  Test suite: ubuntu_qrt_kernel_security.test-kernel-security.py
  Test case: test_095_kernel_symbols_missing_proc_time_list

  16:57:44 ERROR| [stderr] test_095_kernel_symbols_missing_proc_time_list 
(__main__.KernelSecurityTest)
  16:57:44 ERROR| [stderr] kernel addresses in /proc/timer_list are zeroed out 
... FAIL

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

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


[Kernel-packages] [Bug 1831301] Re: sound doesn't works in both kernel. no one cards is recognize by system-

2019-05-31 Thread Seth Arnold
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

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

Title:
  sound doesn't works in both kernel. no one cards is recognize by
  system-

Status in linux package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base (not installed)
  ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Sat Jun  1 04:26:10 2019
  InstallationDate: Installed on 2019-04-03 (58 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-05-31T22:19:11.232515

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

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


[Kernel-packages] [Bug 1831490] Re: kernel is out of memory and killed during a kernel sys_write operation

2019-06-03 Thread Seth Arnold
Can you run apport-collect 1831490 on this machine to collect additional
logs and data?

Thanks

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

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

Title:
  kernel is out of memory and killed during a kernel sys_write operation

Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  This error is being reproduced on i386 arch when using the pc-kernel
  snap from beta or candidate.

  > sudo snap install test-snapd-tools
  > dmesg

  [15131.806107] audit: type=1400 audit(1559585825.240:93): 
apparmor="STATUS" operation="profile_replace" profile="unconfined" 
name="snap-update-ns.test-snapd-tools" pid=18240 comm="apparmor_parser"
  [15131.871610] vmap allocation for size 73728 failed: use vmalloc= to 
increase size.
  [15131.871614] vmalloc: allocation failure: 68481 bytes
  [15131.871616] apparmor_parser: page allocation failure: order:0, 
mode:0x24000c2
  [15131.871619] CPU: 0 PID: 18242 Comm: apparmor_parser Not tainted 
4.4.0-150-generic #176-Ubuntu
  [15131.871620] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [15131.871622]  c1b15967 5ed07e43 0286 cfee9e00 c13c12ef c1a1ce6c 
0001 cfee9e30
  [15131.871625]  c11821b6 c1a1b220 f40ba700  024000c2 cfee9e44 
c1a1ce6c cfee9e18
  [15131.871629]  5ed07e43 00010b81  cfee9e60 c11ba86f 024000c2 
 c1a1ce6c
  [15131.871632] Call Trace:
  [15131.871637]  [] dump_stack+0x58/0x79
  [15131.871640]  [] warn_alloc_failed+0xd6/0x110
  [15131.871643]  [] __vmalloc_node_range+0x1ef/0x210
  [15131.871645]  [] __vmalloc_node+0x66/0x70
  [15131.871648]  [] ? __aa_kvmalloc+0x28/0x60
  [15131.871650]  [] vmalloc+0x38/0x40
  [15131.871652]  [] ? __aa_kvmalloc+0x28/0x60
  [15131.871654]  [] __aa_kvmalloc+0x28/0x60
  [15131.871656]  [] aa_simple_write_to_buffer+0x34/0x90
  [15131.871658]  [] policy_update+0x73/0x230
  [15131.871660]  [] ? security_file_permission+0x3e/0xd0
  [15131.871662]  [] profile_replace+0x98/0xe0
  [15131.871664]  [] ? policy_update+0x230/0x230
  [15131.871666]  [] __vfs_write+0x22/0x50
  [15131.871668]  [] vfs_write+0x8c/0x1b0
  [15131.871669]  [] SyS_write+0x51/0xb0
  [15131.871672]  [] do_fast_syscall_32+0x9f/0x190
  [15131.871675]  [] sysenter_past_esp+0x3d/0x61
  [15131.871676] Mem-Info:
  [15131.871679] active_anon:16802 inactive_anon:2068 isolated_anon:0
  active_file:84472 inactive_file:25195 isolated_file:0
  unevictable:0 dirty:34 writeback:0 unstable:0
  slab_reclaimable:7222 slab_unreclaimable:14030
  mapped:8431 shmem:5785 pagetables:204 bounce:0
  free:289381 free_pcp:659 free_cma:0
  [15131.871685] DMA free:8848kB min:788kB low:984kB high:1180kB 
active_anon:636kB inactive_anon:0kB active_file:2720kB inactive_file:800kB 
unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB 
managed:15916kB mlocked:0kB dirty:0kB writeback:0kB mapped:472kB shmem:308kB 
slab_reclaimable:484kB slab_unreclaimable:424kB kernel_stack:8kB pagetables:4kB 
unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB 
writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
  [15131.871686] lowmem_reserve[]: 0 834 1942 1942
  [15131.871692] Normal free:364440kB min:42432kB low:53040kB high:63648kB 
active_anon:30164kB inactive_anon:2776kB active_file:158404kB 
inactive_file:32020kB unevictable:0kB isolated(anon):0kB isolated(file):0kB 
present:897016kB managed:862444kB mlocked:0kB dirty:116kB writeback:0kB 
mapped:11176kB shmem:6332kB slab_reclaimable:28404kB slab_unreclaimable:55696kB 
kernel_stack:1040kB pagetables:348kB unstable:0kB bounce:0kB free_pcp:1336kB 
local_pcp:676kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 
all_unreclaimable? no
  [15131.871693] lowmem_reserve[]: 0 0 8863 8863
  [15131.871698] HighMem free:784236kB min:512kB low:14600kB high:28688kB 
active_anon:36408kB inactive_anon:5496kB active_file:176764kB 
inactive_file:67960kB unevictable:0kB isolated(anon):0kB isolated(file):0kB 
present:1134472kB managed:1134472kB mlocked:0kB dirty:20kB writeback:0kB 
mapped:22076kB shmem:16500kB slab_reclaimable:0kB slab_unreclaimable:0kB 
kernel_stack:0kB pagetables:464kB unstable:0kB bounce:0kB free_pcp:1300kB 
local_pcp:680kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 
all_unreclaimable? no
  [15131.871699] lowmem_reserve[]: 0 0 0 0
  [15131.871701] DMA: 12*4kB (UME) 10*8kB (UME) 7*16kB (ME) 5*32kB (UM) 2*64kB 
(U) 3*128kB (UM) 3*256kB (UM) 4*512kB (UME) 3*1024kB (ME) 1*2048kB (M) 0*4096kB 
= 8848kB
  [15131.871711] Normal: 87*4kB (UME) 106*8kB (UME) 168*16kB (UME) 195*32kB 
(UME) 135*64kB (UME) 161*128kB (ME) 120*256kB (ME) 61*512kB (UME) 25*1024kB 
(ME) 6*2048kB (M) 55*4096kB (M) = 364492kB
  [15131.871720] HighMem: 131*4kB (UM) 835*8kB (UM

[Kernel-packages] [Bug 1862706] [NEW] segfaults, dpkg script failures

2020-02-10 Thread Seth Arnold
Public bug reported:

Hello, I had some apt install failures due to zfs segfaults during zfs
postinst scripts:

sarnold@millbarge:/var/lib$ sudo apt install -f
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  ebtables libbrlapi0.6 libenchant1c2a libgspell-1-1 libxen-4.9 libxenstore3.0 
linux-headers-5.3.0-29 linux-headers-5.3.0-29-generic 
linux-image-5.3.0-29-generic
  linux-modules-5.3.0-29-generic linux-modules-extra-5.3.0-29-generic 
linux-tools-5.3.0-29 linux-tools-5.3.0-29-generic python3-asn1crypto
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up zfsutils-linux (0.8.3-1ubuntu3) ...
zfs-import-scan.service is a disabled or a static unit, not starting it.
zfs-import-scan.service is a disabled or a static unit, not starting it.
Job for zfs-mount.service failed because the control process exited with error 
code.
See "systemctl status zfs-mount.service" and "journalctl -xe" for details.
invoke-rc.d: initscript zfs-mount, action "start" failed.
● zfs-mount.service - Mount ZFS filesystems
 Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Tue 2020-02-11 00:46:19 UTC; 5ms 
ago
   Docs: man:zfs(8)
Process: 2770075 ExecStart=/sbin/zfs mount -a (code=exited, 
status=1/FAILURE)
   Main PID: 2770075 (code=exited, status=1/FAILURE)

Feb 11 00:46:19 millbarge systemd[1]: Starting Mount ZFS filesystems...
Feb 11 00:46:19 millbarge zfs[2770075]: cannot mount '/var/lib/AccountsService':
Feb 11 00:46:19 millbarge zfs[2770075]: cannot mount 
'/var/lib/AccountsService': mount failed
Feb 11 00:46:19 millbarge systemd[1]: zfs-mount.service: Main process exited, 
code=exited, status=1/FAILURE
Feb 11 00:46:19 millbarge systemd[1]: zfs-mount.service: Failed with result 
'exit-code'.
Feb 11 00:46:19 millbarge systemd[1]: Failed to start Mount ZFS filesystems.
dpkg: error processing package zfsutils-linux (--configure):
 installed zfsutils-linux package post-installation script subprocess returned 
error exit status 1
No apport report written because the error message indicates its a followup 
error from a previous failure.

  dpkg: dependency problems prevent configuration of 
zfs-initramfs:
 zfs-initramfs depends on zfsutils-linux (>= 0.8.3-1ubuntu3); however:
  Package zfsutils-linux is not configured yet.

dpkg: error processing package zfs-initramfs (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of zfs-zed:
 zfs-zed depends on zfsutils-linux (>= 0.8.3-1ubuntu3); however:
  Package zfsutils-linux is not configured yet.

dpkg: error processing package zfs-zed (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup 
error from a previous failure.

  Errors were encountered while processing:
 zfsutils-linux
 zfs-initramfs
 zfs-zed
E: Sub-process /usr/bin/dpkg returned an error code (1)
sarnold@millbarge:/var/lib$ sudo dmesg | tail -30
[345819.461404] pci_bus :06: Allocating resources
[345819.461422] pcieport :06:01.0: bridge window [mem 
0x0010-0x000f] to [bus 08-3a] add_size 40 add_align 10
[345819.461424] pcieport :06:04.0: bridge window [mem 
0x0010-0x000f] to [bus 3c-6f] add_size 40 add_align 10
[345819.461428] pcieport :06:01.0: BAR 14: no space for [mem size 
0x0040]
[345819.461428] pcieport :06:01.0: BAR 14: failed to assign [mem size 
0x0040]
[345819.461429] pcieport :06:04.0: BAR 14: no space for [mem size 
0x0040]
[345819.461430] pcieport :06:04.0: BAR 14: failed to assign [mem size 
0x0040]
[345819.461431] pcieport :06:04.0: BAR 14: no space for [mem size 
0x0040]
[345819.461432] pcieport :06:04.0: BAR 14: failed to assign [mem size 
0x0040]
[345819.461432] pcieport :06:01.0: BAR 14: no space for [mem size 
0x0040]
[345819.461433] pcieport :06:01.0: BAR 14: failed to assign [mem size 
0x0040]
[345833.001361] show_signal_msg: 34 callbacks suppressed
[345833.001363] zfs[2653666]: segfault at 0 ip 7f2ff09bbd63 sp 
7f2fec900430 error 4 in libc-2.30.so[7f2ff094d000+178000]
[345833.001369] Code: 48 29 f2 ff 55 70 48 85 c0 7e 4c 48 8b 93 90 00 00 00 48 
01 43 10 48 83 fa ff 74 0a 48 01 d0 48 89 83 90 00 00 00 48 8b 43 08 <0f> b6 00 
48 83 c4 18 5b 5d 41 5c 41 5d 41 5e 41 5f c3 0f 1f 00 0f
[345833.001370] zfs[2653667]: segfault at 0 ip 7f2ff0aafa20 sp 
7f2fcfff7498 error 4 in

Re: [Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

2020-02-10 Thread Seth Arnold
On Mon, Feb 10, 2020 at 07:53:20AM -, Andrea Righi wrote:
> OK, so we know that it's not related to the memory cgroup subsystem.

But this is a good instinct. It does seem to happen when eg firefox or git
is in heavy memory use, not the system as a whole.

> Another reason of such unexpected swapping activity could be due to
> memory compaction code that is triggering some direct memory reclaim and
> forcing to swap out pages.
> 
> What do you have in /proc/sys/vm/swappiness? Could you try to set that
> to 0 (kernel prefers to drop file-backed pages instead of swapping out
> anonymous pages) and see if the swap out activity is still happening?

$ cat /proc/sys/vm/swappiness
60

I'll try 0.

> Moreover, we can do some more advanced tracing of the direct memory reclaim 
> code, for example:
>  $ sudo kprobe-perf -s 'p:shrink_node'
> 

This doesn't work:


# kprobe-perf -s 'p:shrink_node'
ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
# ls -l /sys/kernel/debug/tracing/available_filter_functions
ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
# find /sys/kernel/debug/tracing
/sys/kernel/debug/tracing
/sys/kernel/debug/tracing/instances
/sys/kernel/debug/tracing/trace_stat
/sys/kernel/debug/tracing/per_cpu
/sys/kernel/debug/tracing/per_cpu/cpu7
/sys/kernel/debug/tracing/per_cpu/cpu6
/sys/kernel/debug/tracing/per_cpu/cpu5
/sys/kernel/debug/tracing/per_cpu/cpu4
/sys/kernel/debug/tracing/per_cpu/cpu3
/sys/kernel/debug/tracing/per_cpu/cpu2
/sys/kernel/debug/tracing/per_cpu/cpu1
/sys/kernel/debug/tracing/per_cpu/cpu0
/sys/kernel/debug/tracing/options
#


Thanks

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

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin pl

[Kernel-packages] [Bug 1862708] [NEW] tracing doesn't work on focal

2020-02-10 Thread Seth Arnold
Public bug reported:

Hello, while investigating bug 1861359 I tried to use kprobe-perf to
troubleshoot and found that tracing doesn't work on focal:

# kprobe-perf -s 'p:shrink_node'
ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
# ls -l /sys/kernel/debug/tracing/available_filter_functions
ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
# find /sys/kernel/debug/tracing
/sys/kernel/debug/tracing
/sys/kernel/debug/tracing/instances
/sys/kernel/debug/tracing/trace_stat
/sys/kernel/debug/tracing/per_cpu
/sys/kernel/debug/tracing/per_cpu/cpu7
/sys/kernel/debug/tracing/per_cpu/cpu6
/sys/kernel/debug/tracing/per_cpu/cpu5
/sys/kernel/debug/tracing/per_cpu/cpu4
/sys/kernel/debug/tracing/per_cpu/cpu3
/sys/kernel/debug/tracing/per_cpu/cpu2
/sys/kernel/debug/tracing/per_cpu/cpu1
/sys/kernel/debug/tracing/per_cpu/cpu0
/sys/kernel/debug/tracing/options


I'm guessing this is due to lockdown:

# dmesg | grep -C2 -i lockdown
[0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
[0.00] secureboot: Secure boot enabled
[0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
[0.00] SMBIOS 3.0.0 present.
[0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
--
[0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
[0.534731] clocksource: Switched to clocksource tsc-early
[0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.534737] Could not create tracefs 'available_events' entry
[0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.534741] Could not create tracefs 'set_event' entry
[0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.534743] Could not create tracefs 'available_tracers' entry
[0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.534745] Could not create tracefs 'current_tracer' entry
[0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.534746] Could not create tracefs 'tracing_cpumask' entry
[0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.534747] Could not create tracefs 'trace_options' entry
[0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.534748] Could not create tracefs 'trace' entry
[0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.534750] Could not create tracefs 'trace_pipe' entry
[0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.534751] Could not create tracefs 'buffer_size_kb' entry
[0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.534752] Could not create tracefs 'buffer_total_size_kb' entry
[0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.534754] Could not create tracefs 'free_buffer' entry
[0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.534755] Could not create tracefs 'trace_marker' entry
[0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.534783] Could not create tracefs 'trace_marker_raw' entry
[0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.534784] Could not create tracefs 'trace_clock' entry
[0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.534785] Could not create tracefs 'tracing_on' entry
[0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.534786] Could not create tracefs 'timestamp_mode' entry
[0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.534788] Could not create tracefs 'buffer_percent' entry
[0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.534817] Could not create tracefs 'print-parent' entry
[0.534817] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.534818] Could not create tracefs 'sym-offset' entry
[0.534819] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.534819] Could not create tracefs 'sym-addr' entry
[0.534820] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.534820] Could not create tracefs 'verbose' entry
[0.534821] Lockdown: swapper/0: use of tracefs is restricted; see man 
k

Re: [Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

2020-02-10 Thread Seth Arnold
> What do you have in /proc/sys/vm/swappiness? Could you try to set that
> to 0 (kernel prefers to drop file-backed pages instead of swapping out
> anonymous pages) and see if the swap out activity is still happening?

Unfortunately, this did not solve the problem.

Setting swappiness to 0 and re-enabling my swap nearly immediately caused
the whole computer to lag whenever firefox had focus -- and swap use
jumped to 380M, despite having roughly five gigs free space.

Turning swap back off again helped immensely.

Thanks

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

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'

[Kernel-packages] [Bug 1862706] Re: segfaults, dpkg script failures

2020-02-10 Thread Seth Arnold
I didn't know that two of my datasets were not mounted:

$ zfs list -oname,canmount,mounted,mountpoint | grep 'on   no'
rpool/var/cache  on   no  /var/cache
rpool/var/lib/AccountsServiceon   no  /var/lib/AccountsService

Thanks

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

Title:
  segfaults, dpkg script failures

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Hello, I had some apt install failures due to zfs segfaults during zfs
  postinst scripts:

  sarnold@millbarge:/var/lib$ sudo apt install -f
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
ebtables libbrlapi0.6 libenchant1c2a libgspell-1-1 libxen-4.9 
libxenstore3.0 linux-headers-5.3.0-29 linux-headers-5.3.0-29-generic 
linux-image-5.3.0-29-generic
linux-modules-5.3.0-29-generic linux-modules-extra-5.3.0-29-generic 
linux-tools-5.3.0-29 linux-tools-5.3.0-29-generic python3-asn1crypto
  Use 'sudo apt autoremove' to remove them.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  3 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up zfsutils-linux (0.8.3-1ubuntu3) ...
  zfs-import-scan.service is a disabled or a static unit, not starting it.
  zfs-import-scan.service is a disabled or a static unit, not starting it.
  Job for zfs-mount.service failed because the control process exited with 
error code.
  See "systemctl status zfs-mount.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript zfs-mount, action "start" failed.
  ● zfs-mount.service - Mount ZFS filesystems
   Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-02-11 00:46:19 UTC; 
5ms ago
 Docs: man:zfs(8)
  Process: 2770075 ExecStart=/sbin/zfs mount -a (code=exited, 
status=1/FAILURE)
 Main PID: 2770075 (code=exited, status=1/FAILURE)

  Feb 11 00:46:19 millbarge systemd[1]: Starting Mount ZFS filesystems...
  Feb 11 00:46:19 millbarge zfs[2770075]: cannot mount 
'/var/lib/AccountsService':
  Feb 11 00:46:19 millbarge zfs[2770075]: cannot mount 
'/var/lib/AccountsService': mount failed
  Feb 11 00:46:19 millbarge systemd[1]: zfs-mount.service: Main process exited, 
code=exited, status=1/FAILURE
  Feb 11 00:46:19 millbarge systemd[1]: zfs-mount.service: Failed with result 
'exit-code'.
  Feb 11 00:46:19 millbarge systemd[1]: Failed to start Mount ZFS filesystems.
  dpkg: error processing package zfsutils-linux (--configure):
   installed zfsutils-linux package post-installation script subprocess 
returned error exit status 1
  No apport report written because the error message indicates its a followup 
error from a previous failure.

dpkg: dependency problems prevent configuration of 
zfs-initramfs:
   zfs-initramfs depends on zfsutils-linux (>= 0.8.3-1ubuntu3); however:
Package zfsutils-linux is not configured yet.

  dpkg: error processing package zfs-initramfs (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of zfs-zed:
   zfs-zed depends on zfsutils-linux (>= 0.8.3-1ubuntu3); however:
Package zfsutils-linux is not configured yet.

  dpkg: error processing package zfs-zed (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
error from a previous failure.

Errors were encountered while processing:
   zfsutils-linux
   zfs-initramfs
   zfs-zed
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  sarnold@millbarge:/var/lib$ sudo dmesg | tail -30
  [345819.461404] pci_bus :06: Allocating resources
  [345819.461422] pcieport :06:01.0: bridge window [mem 
0x0010-0x000f] to [bus 08-3a] add_size 40 add_align 10
  [345819.461424] pcieport :06:04.0: bridge window [mem 
0x0010-0x000f] to [bus 3c-6f] add_size 40 add_align 10
  [345819.461428] pcieport :06:01.0: BAR 14: no space for [mem size 
0x0040]
  [345819.461428] pcieport :06:01.0: BAR 14: failed to assign [mem size 
0x0040]
  [345819.461429] pcieport :06:04.0: BAR 14: no space for [mem size 
0x0040]
  [345819.461430] pcieport :06:04.0: BAR 14: failed to assign [mem size 
0x0040]
  [345819.461431] pcieport :06:04.0: BAR 14: no space for [mem size 
0x0040]
  [345819.461432] pcieport :06:04.0: BAR 14: failed to assign [mem size 
0x0040]
  [345819.461432] pcieport 

[Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

2020-02-10 Thread Seth Arnold
These are all the zpool and zfs commands on the receiver except
snapshots, renames, and destroys, associated with my Ubuntu archive
mirror rsync. (7000-ish lines of juggling 30-snapshots. I should do
something better here.)

** Attachment added: "receiver_limited_history"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861235/+attachment/5327158/+files/receiver_limited_history

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

Title:
  zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

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

Bug description:
  Same as bug 1861228 but with a newer kernel installed.

  [  790.702566] VERIFY(size != 0) failed
  [  790.702590] PANIC at range_tree.c:304:range_tree_find_impl()
  [  790.702611] Showing stack for process 28685
  [  790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P   O 
4.15.0-76-generic #86-Ubuntu
  [  790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 
2.0 12/17/2015
  [  790.702616] Call Trace:
  [  790.702626]  dump_stack+0x6d/0x8e
  [  790.702637]  spl_dumpstack+0x42/0x50 [spl]
  [  790.702640]  spl_panic+0xc8/0x110 [spl]
  [  790.702645]  ? __switch_to_asm+0x41/0x70
  [  790.702714]  ? arc_prune_task+0x1a/0x40 [zfs]
  [  790.702740]  ? dbuf_dirty+0x43d/0x850 [zfs]
  [  790.702745]  ? getrawmonotonic64+0x43/0xd0
  [  790.702746]  ? getrawmonotonic64+0x43/0xd0
  [  790.702775]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702778]  ? getrawmonotonic64+0x43/0xd0
  [  790.702805]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702807]  ? mutex_lock+0x12/0x40
  [  790.702833]  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
  [  790.702866]  range_tree_find_impl+0x88/0x90 [zfs]
  [  790.702870]  ? spl_kmem_zalloc+0xdc/0x1a0 [spl]
  [  790.702902]  range_tree_clear+0x4f/0x60 [zfs]
  [  790.702930]  dnode_free_range+0x11f/0x5a0 [zfs]
  [  790.702957]  dmu_object_free+0x53/0x90 [zfs]
  [  790.702983]  dmu_free_long_object+0x9f/0xc0 [zfs]
  [  790.703010]  receive_freeobjects.isra.12+0x7a/0x100 [zfs]
  [  790.703036]  receive_writer_thread+0x6d2/0xa60 [zfs]
  [  790.703040]  ? set_curr_task_fair+0x2b/0x60
  [  790.703043]  ? spl_kmem_free+0x33/0x40 [spl]
  [  790.703048]  ? kfree+0x165/0x180
  [  790.703073]  ? receive_free.isra.13+0xc0/0xc0 [zfs]
  [  790.703078]  thread_generic_wrapper+0x74/0x90 [spl]
  [  790.703081]  kthread+0x121/0x140
  [  790.703084]  ? __thread_exit+0x20/0x20 [spl]
  [  790.703085]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  790.703088]  ret_from_fork+0x35/0x40
  [  967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds.
  [  967.636979]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637076] txg_quiesce D0 14810  2 0x8000
  [  967.637080] Call Trace:
  [  967.637089]  __schedule+0x24e/0x880
  [  967.637092]  schedule+0x2c/0x80
  [  967.637106]  cv_wait_common+0x11e/0x140 [spl]
  [  967.637114]  ? wait_woken+0x80/0x80
  [  967.637122]  __cv_wait+0x15/0x20 [spl]
  [  967.637210]  txg_quiesce_thread+0x2cb/0x3d0 [zfs]
  [  967.637278]  ? txg_delay+0x1b0/0x1b0 [zfs]
  [  967.637286]  thread_generic_wrapper+0x74/0x90 [spl]
  [  967.637291]  kthread+0x121/0x140
  [  967.637297]  ? __thread_exit+0x20/0x20 [spl]
  [  967.637299]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  967.637304]  ret_from_fork+0x35/0x40
  [  967.637326] INFO: task zfs:28590 blocked for more than 120 seconds.
  [  967.637371]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637467] zfs D0 28590  28587 0x8080
  [  967.637470] Call Trace:
  [  967.637474]  __schedule+0x24e/0x880
  [  967.637477]  schedule+0x2c/0x80
  [  967.637486]  cv_wait_common+0x11e/0x140 [spl]
  [  967.637491]  ? wait_woken+0x80/0x80
  [  967.637498]  __cv_wait+0x15/0x20 [spl]
  [  967.637554]  dmu_recv_stream+0xa51/0xef0 [zfs]
  [  967.637630]  zfs_ioc_recv_impl+0x306/0x1100 [zfs]
  [  967.637679]  ? dbuf_read+0x34a/0x920 [zfs]
  [  967.637725]  ? dbuf_rele+0x36/0x40 [zfs]
  [  967.637728]  ? _cond_resched+0x19/0x40
  [  967.637798]  zfs_ioc_recv_new+0x33d/0x410 [zfs]
  [  967.637809]  ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl]
  [  967.637816]  ? spl_vmem_alloc+0x19/0x20 [spl]
  [  967.637828]  ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair]
  [  967.637834]  ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair]
  [  967.637840]  ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair]
  [  967.637905]  zfsdev_ioctl+0x451/0x610 [zfs]
  [  967.637913]  do_vfs_ioctl+0xa8/0x630
  [  967.637917]  ? __audit_syscall_entry+0xbc/0x110
  [  967.637924]  ? syscall_trace_enter+0x1da/0x2d0
  [  967.637927]  SyS_ioctl+0x79/0x90
  [  967.637930]  do_syscall_64+0x73/0x130
  [  967.63

[Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

2020-02-10 Thread Seth Arnold
These are just the zfs bookmark and zfs send commands from the sender.

** Attachment added: "zfs bookmark, zfs send commands"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861235/+attachment/5327157/+files/sender_limited_history

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

Title:
  zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

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

Bug description:
  Same as bug 1861228 but with a newer kernel installed.

  [  790.702566] VERIFY(size != 0) failed
  [  790.702590] PANIC at range_tree.c:304:range_tree_find_impl()
  [  790.702611] Showing stack for process 28685
  [  790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P   O 
4.15.0-76-generic #86-Ubuntu
  [  790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 
2.0 12/17/2015
  [  790.702616] Call Trace:
  [  790.702626]  dump_stack+0x6d/0x8e
  [  790.702637]  spl_dumpstack+0x42/0x50 [spl]
  [  790.702640]  spl_panic+0xc8/0x110 [spl]
  [  790.702645]  ? __switch_to_asm+0x41/0x70
  [  790.702714]  ? arc_prune_task+0x1a/0x40 [zfs]
  [  790.702740]  ? dbuf_dirty+0x43d/0x850 [zfs]
  [  790.702745]  ? getrawmonotonic64+0x43/0xd0
  [  790.702746]  ? getrawmonotonic64+0x43/0xd0
  [  790.702775]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702778]  ? getrawmonotonic64+0x43/0xd0
  [  790.702805]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702807]  ? mutex_lock+0x12/0x40
  [  790.702833]  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
  [  790.702866]  range_tree_find_impl+0x88/0x90 [zfs]
  [  790.702870]  ? spl_kmem_zalloc+0xdc/0x1a0 [spl]
  [  790.702902]  range_tree_clear+0x4f/0x60 [zfs]
  [  790.702930]  dnode_free_range+0x11f/0x5a0 [zfs]
  [  790.702957]  dmu_object_free+0x53/0x90 [zfs]
  [  790.702983]  dmu_free_long_object+0x9f/0xc0 [zfs]
  [  790.703010]  receive_freeobjects.isra.12+0x7a/0x100 [zfs]
  [  790.703036]  receive_writer_thread+0x6d2/0xa60 [zfs]
  [  790.703040]  ? set_curr_task_fair+0x2b/0x60
  [  790.703043]  ? spl_kmem_free+0x33/0x40 [spl]
  [  790.703048]  ? kfree+0x165/0x180
  [  790.703073]  ? receive_free.isra.13+0xc0/0xc0 [zfs]
  [  790.703078]  thread_generic_wrapper+0x74/0x90 [spl]
  [  790.703081]  kthread+0x121/0x140
  [  790.703084]  ? __thread_exit+0x20/0x20 [spl]
  [  790.703085]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  790.703088]  ret_from_fork+0x35/0x40
  [  967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds.
  [  967.636979]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637076] txg_quiesce D0 14810  2 0x8000
  [  967.637080] Call Trace:
  [  967.637089]  __schedule+0x24e/0x880
  [  967.637092]  schedule+0x2c/0x80
  [  967.637106]  cv_wait_common+0x11e/0x140 [spl]
  [  967.637114]  ? wait_woken+0x80/0x80
  [  967.637122]  __cv_wait+0x15/0x20 [spl]
  [  967.637210]  txg_quiesce_thread+0x2cb/0x3d0 [zfs]
  [  967.637278]  ? txg_delay+0x1b0/0x1b0 [zfs]
  [  967.637286]  thread_generic_wrapper+0x74/0x90 [spl]
  [  967.637291]  kthread+0x121/0x140
  [  967.637297]  ? __thread_exit+0x20/0x20 [spl]
  [  967.637299]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  967.637304]  ret_from_fork+0x35/0x40
  [  967.637326] INFO: task zfs:28590 blocked for more than 120 seconds.
  [  967.637371]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637467] zfs D0 28590  28587 0x8080
  [  967.637470] Call Trace:
  [  967.637474]  __schedule+0x24e/0x880
  [  967.637477]  schedule+0x2c/0x80
  [  967.637486]  cv_wait_common+0x11e/0x140 [spl]
  [  967.637491]  ? wait_woken+0x80/0x80
  [  967.637498]  __cv_wait+0x15/0x20 [spl]
  [  967.637554]  dmu_recv_stream+0xa51/0xef0 [zfs]
  [  967.637630]  zfs_ioc_recv_impl+0x306/0x1100 [zfs]
  [  967.637679]  ? dbuf_read+0x34a/0x920 [zfs]
  [  967.637725]  ? dbuf_rele+0x36/0x40 [zfs]
  [  967.637728]  ? _cond_resched+0x19/0x40
  [  967.637798]  zfs_ioc_recv_new+0x33d/0x410 [zfs]
  [  967.637809]  ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl]
  [  967.637816]  ? spl_vmem_alloc+0x19/0x20 [spl]
  [  967.637828]  ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair]
  [  967.637834]  ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair]
  [  967.637840]  ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair]
  [  967.637905]  zfsdev_ioctl+0x451/0x610 [zfs]
  [  967.637913]  do_vfs_ioctl+0xa8/0x630
  [  967.637917]  ? __audit_syscall_entry+0xbc/0x110
  [  967.637924]  ? syscall_trace_enter+0x1da/0x2d0
  [  967.637927]  SyS_ioctl+0x79/0x90
  [  967.637930]  do_syscall_64+0x73/0x130
  [  967.637935]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [  967.637938] RIP: 0033:0x7fc305a905d7
  [  967.637940] RSP: 002b:7ffc45e39618 EFLAGS: 02

[Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

2020-02-10 Thread Seth Arnold
The two machines involved are:

Receiver, bionic, probably running 4.15.0-76-generic and zfsutils-linux
0.7.5-1ubuntu16.7

Sender, focal, probably running 5.4.0-12-generic and zfsutils-linux
0.8.3-1ubuntu3


I'm using sanoid and syncoid to automate snapshot management and sending and 
receiving. The combination worked well for about a week before I got this 
failure.

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

Title:
  zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

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

Bug description:
  Same as bug 1861228 but with a newer kernel installed.

  [  790.702566] VERIFY(size != 0) failed
  [  790.702590] PANIC at range_tree.c:304:range_tree_find_impl()
  [  790.702611] Showing stack for process 28685
  [  790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P   O 
4.15.0-76-generic #86-Ubuntu
  [  790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 
2.0 12/17/2015
  [  790.702616] Call Trace:
  [  790.702626]  dump_stack+0x6d/0x8e
  [  790.702637]  spl_dumpstack+0x42/0x50 [spl]
  [  790.702640]  spl_panic+0xc8/0x110 [spl]
  [  790.702645]  ? __switch_to_asm+0x41/0x70
  [  790.702714]  ? arc_prune_task+0x1a/0x40 [zfs]
  [  790.702740]  ? dbuf_dirty+0x43d/0x850 [zfs]
  [  790.702745]  ? getrawmonotonic64+0x43/0xd0
  [  790.702746]  ? getrawmonotonic64+0x43/0xd0
  [  790.702775]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702778]  ? getrawmonotonic64+0x43/0xd0
  [  790.702805]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702807]  ? mutex_lock+0x12/0x40
  [  790.702833]  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
  [  790.702866]  range_tree_find_impl+0x88/0x90 [zfs]
  [  790.702870]  ? spl_kmem_zalloc+0xdc/0x1a0 [spl]
  [  790.702902]  range_tree_clear+0x4f/0x60 [zfs]
  [  790.702930]  dnode_free_range+0x11f/0x5a0 [zfs]
  [  790.702957]  dmu_object_free+0x53/0x90 [zfs]
  [  790.702983]  dmu_free_long_object+0x9f/0xc0 [zfs]
  [  790.703010]  receive_freeobjects.isra.12+0x7a/0x100 [zfs]
  [  790.703036]  receive_writer_thread+0x6d2/0xa60 [zfs]
  [  790.703040]  ? set_curr_task_fair+0x2b/0x60
  [  790.703043]  ? spl_kmem_free+0x33/0x40 [spl]
  [  790.703048]  ? kfree+0x165/0x180
  [  790.703073]  ? receive_free.isra.13+0xc0/0xc0 [zfs]
  [  790.703078]  thread_generic_wrapper+0x74/0x90 [spl]
  [  790.703081]  kthread+0x121/0x140
  [  790.703084]  ? __thread_exit+0x20/0x20 [spl]
  [  790.703085]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  790.703088]  ret_from_fork+0x35/0x40
  [  967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds.
  [  967.636979]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637076] txg_quiesce D0 14810  2 0x8000
  [  967.637080] Call Trace:
  [  967.637089]  __schedule+0x24e/0x880
  [  967.637092]  schedule+0x2c/0x80
  [  967.637106]  cv_wait_common+0x11e/0x140 [spl]
  [  967.637114]  ? wait_woken+0x80/0x80
  [  967.637122]  __cv_wait+0x15/0x20 [spl]
  [  967.637210]  txg_quiesce_thread+0x2cb/0x3d0 [zfs]
  [  967.637278]  ? txg_delay+0x1b0/0x1b0 [zfs]
  [  967.637286]  thread_generic_wrapper+0x74/0x90 [spl]
  [  967.637291]  kthread+0x121/0x140
  [  967.637297]  ? __thread_exit+0x20/0x20 [spl]
  [  967.637299]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  967.637304]  ret_from_fork+0x35/0x40
  [  967.637326] INFO: task zfs:28590 blocked for more than 120 seconds.
  [  967.637371]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637467] zfs D0 28590  28587 0x8080
  [  967.637470] Call Trace:
  [  967.637474]  __schedule+0x24e/0x880
  [  967.637477]  schedule+0x2c/0x80
  [  967.637486]  cv_wait_common+0x11e/0x140 [spl]
  [  967.637491]  ? wait_woken+0x80/0x80
  [  967.637498]  __cv_wait+0x15/0x20 [spl]
  [  967.637554]  dmu_recv_stream+0xa51/0xef0 [zfs]
  [  967.637630]  zfs_ioc_recv_impl+0x306/0x1100 [zfs]
  [  967.637679]  ? dbuf_read+0x34a/0x920 [zfs]
  [  967.637725]  ? dbuf_rele+0x36/0x40 [zfs]
  [  967.637728]  ? _cond_resched+0x19/0x40
  [  967.637798]  zfs_ioc_recv_new+0x33d/0x410 [zfs]
  [  967.637809]  ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl]
  [  967.637816]  ? spl_vmem_alloc+0x19/0x20 [spl]
  [  967.637828]  ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair]
  [  967.637834]  ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair]
  [  967.637840]  ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair]
  [  967.637905]  zfsdev_ioctl+0x451/0x610 [zfs]
  [  967.637913]  do_vfs_ioctl+0xa8/0x630
  [  967.637917]  ? __audit_syscall_entry+0xbc/0x110
  [  967.637924]  ? syscall_trace_enter+0x1da/0x2d0
  [  967.637927]  SyS_ioctl+0x79/0x90
  [  967.637930]  do_syscall_64+0x73/0x130
  [  967.637935]  entry_SYSCALL

[Kernel-packages] [Bug 1862708] ArecordDevices.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "ArecordDevices.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327181/+files/ArecordDevices.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/1862708

Title:
  tracing doesn't work on focal

Status in linux package in Ubuntu:
  Incomplete
Status in perf-tools-unstable package in Ubuntu:
  New

Bug description:
  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:

  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options

  
  I'm guessing this is due to lockdown:

  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534785] Could not create tracefs 'tracing_on' entry
  [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534786] Could not create tracefs 'timestamp_mode' entry
  [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534788] Could not create tracefs 'buffer_percent' entry
  [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown

[Kernel-packages] [Bug 1862708] Re: tracing doesn't work on focal

2020-02-10 Thread Seth Arnold
apport information

** Tags added: apport-collected

** Description changed:

  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:
  
  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options
  
  
  I'm guessing this is due to lockdown:
  
  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534785] Could not create tracefs 'tracing_on' entry
  [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534786] Could not create tracefs 'timestamp_mode' entry
  [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534788] Could not create tracefs 'buffer_percent' entry
  [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534817] Could not create tracefs 'print-parent' entry
  [0.534817] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534818] Could not create tracefs 'sym-offset' entry
  [0.534819] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534819] Could not create tracefs 'sym-addr' entry
  [0.534820] Lo

[Kernel-packages] [Bug 1862708] AplayDevices.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "AplayDevices.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327180/+files/AplayDevices.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/1862708

Title:
  tracing doesn't work on focal

Status in linux package in Ubuntu:
  Incomplete
Status in perf-tools-unstable package in Ubuntu:
  New

Bug description:
  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:

  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options

  
  I'm guessing this is due to lockdown:

  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534785] Could not create tracefs 'tracing_on' entry
  [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534786] Could not create tracefs 'timestamp_mode' entry
  [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534788] Could not create tracefs 'buffer_percent' entry
  [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
 

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

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1862708/+attachment/5327182/+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/1862708

Title:
  tracing doesn't work on focal

Status in linux package in Ubuntu:
  Incomplete
Status in perf-tools-unstable package in Ubuntu:
  New

Bug description:
  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:

  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options

  
  I'm guessing this is due to lockdown:

  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534785] Could not create tracefs 'tracing_on' entry
  [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534786] Could not create tracefs 'timestamp_mode' entry
  [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534788] Could not create tracefs 'buffer_percent' entry
  [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534817] C

[Kernel-packages] [Bug 1862708] Card0.Codecs.codec.0.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "Card0.Codecs.codec.0.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327184/+files/Card0.Codecs.codec.0.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/1862708

Title:
  tracing doesn't work on focal

Status in linux package in Ubuntu:
  Incomplete
Status in perf-tools-unstable package in Ubuntu:
  New

Bug description:
  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:

  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options

  
  I'm guessing this is due to lockdown:

  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534785] Could not create tracefs 'tracing_on' entry
  [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534786] Could not create tracefs 'timestamp_mode' entry
  [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534788] Could not create tracefs 'buffer_percent' entry
  [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man 
ker

[Kernel-packages] [Bug 1862708] Lsusb-v.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327191/+files/Lsusb-v.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/1862708

Title:
  tracing doesn't work on focal

Status in linux package in Ubuntu:
  Incomplete
Status in perf-tools-unstable package in Ubuntu:
  New

Bug description:
  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:

  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options

  
  I'm guessing this is due to lockdown:

  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534785] Could not create tracefs 'tracing_on' entry
  [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534786] Could not create tracefs 'timestamp_mode' entry
  [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534788] Could not create tracefs 'buffer_percent' entry
  [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.53

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

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327196/+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/1862708

Title:
  tracing doesn't work on focal

Status in linux package in Ubuntu:
  Incomplete
Status in perf-tools-unstable package in Ubuntu:
  New

Bug description:
  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:

  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options

  
  I'm guessing this is due to lockdown:

  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534785] Could not create tracefs 'tracing_on' entry
  [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534786] Could not create tracefs 'timestamp_mode' entry
  [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534788] Could not create tracefs 'buffer_percent' entry
  [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [

[Kernel-packages] [Bug 1862708] Card1.Amixer.values.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "Card1.Amixer.values.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327186/+files/Card1.Amixer.values.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/1862708

Title:
  tracing doesn't work on focal

Status in linux package in Ubuntu:
  Incomplete
Status in perf-tools-unstable package in Ubuntu:
  New

Bug description:
  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:

  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options

  
  I'm guessing this is due to lockdown:

  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534785] Could not create tracefs 'tracing_on' entry
  [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534786] Could not create tracefs 'timestamp_mode' entry
  [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534788] Could not create tracefs 'buffer_percent' entry
  [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man 
kerne

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

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327187/+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/1862708

Title:
  tracing doesn't work on focal

Status in linux package in Ubuntu:
  Incomplete
Status in perf-tools-unstable package in Ubuntu:
  New

Bug description:
  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:

  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options

  
  I'm guessing this is due to lockdown:

  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534785] Could not create tracefs 'tracing_on' entry
  [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534786] Could not create tracefs 'timestamp_mode' entry
  [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534788] Could not create tracefs 'buffer_percent' entry
  [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
 

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

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1862708/+attachment/5327188/+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/1862708

Title:
  tracing doesn't work on focal

Status in linux package in Ubuntu:
  Incomplete
Status in perf-tools-unstable package in Ubuntu:
  New

Bug description:
  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:

  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options

  
  I'm guessing this is due to lockdown:

  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534785] Could not create tracefs 'tracing_on' entry
  [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534786] Could not create tracefs 'timestamp_mode' entry
  [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534788] Could not create tracefs 'buffer_percent' entry
  [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534817]

[Kernel-packages] [Bug 1862708] Lsusb-t.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327190/+files/Lsusb-t.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/1862708

Title:
  tracing doesn't work on focal

Status in linux package in Ubuntu:
  Incomplete
Status in perf-tools-unstable package in Ubuntu:
  New

Bug description:
  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:

  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options

  
  I'm guessing this is due to lockdown:

  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534785] Could not create tracefs 'tracing_on' entry
  [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534786] Could not create tracefs 'timestamp_mode' entry
  [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534788] Could not create tracefs 'buffer_percent' entry
  [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.53

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

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1862708/+attachment/5327198/+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/1862708

Title:
  tracing doesn't work on focal

Status in linux package in Ubuntu:
  Incomplete
Status in perf-tools-unstable package in Ubuntu:
  New

Bug description:
  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:

  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options

  
  I'm guessing this is due to lockdown:

  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534785] Could not create tracefs 'tracing_on' entry
  [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534786] Could not create tracefs 'timestamp_mode' entry
  [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534788] Could not create tracefs 'buffer_percent' entry
  [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.53481

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

2020-02-10 Thread Seth Arnold
apport information

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

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

Title:
  tracing doesn't work on focal

Status in linux package in Ubuntu:
  Incomplete
Status in perf-tools-unstable package in Ubuntu:
  New

Bug description:
  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:

  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options

  
  I'm guessing this is due to lockdown:

  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534785] Could not create tracefs 'tracing_on' entry
  [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534786] Could not create tracefs 'timestamp_mode' entry
  [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534788] Could not create tracefs 'buffer_percent' entry
  [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.53481

[Kernel-packages] [Bug 1862708] PciMultimedia.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "PciMultimedia.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327192/+files/PciMultimedia.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/1862708

Title:
  tracing doesn't work on focal

Status in linux package in Ubuntu:
  Incomplete
Status in perf-tools-unstable package in Ubuntu:
  New

Bug description:
  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:

  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options

  
  I'm guessing this is due to lockdown:

  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534785] Could not create tracefs 'tracing_on' entry
  [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534786] Could not create tracefs 'timestamp_mode' entry
  [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534788] Could not create tracefs 'buffer_percent' entry
  [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7

[Kernel-packages] [Bug 1862708] Card0.Amixer.values.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "Card0.Amixer.values.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327183/+files/Card0.Amixer.values.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/1862708

Title:
  tracing doesn't work on focal

Status in linux package in Ubuntu:
  Incomplete
Status in perf-tools-unstable package in Ubuntu:
  New

Bug description:
  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:

  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options

  
  I'm guessing this is due to lockdown:

  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534785] Could not create tracefs 'tracing_on' entry
  [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534786] Could not create tracefs 'timestamp_mode' entry
  [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534788] Could not create tracefs 'buffer_percent' entry
  [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man 
kerne

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

2020-02-10 Thread Seth Arnold
apport information

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

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

Title:
  tracing doesn't work on focal

Status in linux package in Ubuntu:
  Incomplete
Status in perf-tools-unstable package in Ubuntu:
  New

Bug description:
  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:

  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options

  
  I'm guessing this is due to lockdown:

  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534785] Could not create tracefs 'tracing_on' entry
  [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534786] Could not create tracefs 'timestamp_mode' entry
  [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534788] Could not create tracefs 'buffer_percent' entry
  [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534817]

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

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327194/+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/1862708

Title:
  tracing doesn't work on focal

Status in linux package in Ubuntu:
  Incomplete
Status in perf-tools-unstable package in Ubuntu:
  New

Bug description:
  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:

  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options

  
  I'm guessing this is due to lockdown:

  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534785] Could not create tracefs 'tracing_on' entry
  [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534786] Could not create tracefs 'timestamp_mode' entry
  [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534788] Could not create tracefs 'buffer_percent' entry
  [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown

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

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327199/+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/1862708

Title:
  tracing doesn't work on focal

Status in linux package in Ubuntu:
  Incomplete
Status in perf-tools-unstable package in Ubuntu:
  New

Bug description:
  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:

  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options

  
  I'm guessing this is due to lockdown:

  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534785] Could not create tracefs 'tracing_on' entry
  [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534786] Could not create tracefs 'timestamp_mode' entry
  [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534788] Could not create tracefs 'buffer_percent' entry
  [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [  

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

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327195/+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/1862708

Title:
  tracing doesn't work on focal

Status in linux package in Ubuntu:
  Incomplete
Status in perf-tools-unstable package in Ubuntu:
  New

Bug description:
  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:

  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options

  
  I'm guessing this is due to lockdown:

  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534785] Could not create tracefs 'tracing_on' entry
  [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534786] Could not create tracefs 'timestamp_mode' entry
  [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534788] Could not create tracefs 'buffer_percent' entry
  [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [

[Kernel-packages] [Bug 1862708] Card0.Codecs.codec.2.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "Card0.Codecs.codec.2.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327185/+files/Card0.Codecs.codec.2.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/1862708

Title:
  tracing doesn't work on focal

Status in linux package in Ubuntu:
  Incomplete
Status in perf-tools-unstable package in Ubuntu:
  New

Bug description:
  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:

  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options

  
  I'm guessing this is due to lockdown:

  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534785] Could not create tracefs 'tracing_on' entry
  [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534786] Could not create tracefs 'timestamp_mode' entry
  [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534788] Could not create tracefs 'buffer_percent' entry
  [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man 
ker

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

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327193/+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/1862708

Title:
  tracing doesn't work on focal

Status in linux package in Ubuntu:
  Incomplete
Status in perf-tools-unstable package in Ubuntu:
  New

Bug description:
  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:

  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options

  
  I'm guessing this is due to lockdown:

  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534785] Could not create tracefs 'tracing_on' entry
  [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534786] Could not create tracefs 'timestamp_mode' entry
  [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534788] Could not create tracefs 'buffer_percent' entry
  [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_

[Kernel-packages] [Bug 1862708] Re: tracing doesn't work on focal

2020-02-10 Thread Seth Arnold
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  tracing doesn't work on focal

Status in linux package in Ubuntu:
  Confirmed
Status in perf-tools-unstable package in Ubuntu:
  New

Bug description:
  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:

  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options

  
  I'm guessing this is due to lockdown:

  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534785] Could not create tracefs 'tracing_on' entry
  [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534786] Could not create tracefs 'timestamp_mode' entry
  [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534788] Could not create tracefs 'buffer_percent' entry
  [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534817] Could not create tracefs 'print-parent' entry
  [0.534817] L

[Kernel-packages] [Bug 1862840] Re: [Bionic] i915 incomplete fix for CVE-2019-14615

2020-02-11 Thread Seth Arnold
Please use CVE-2020-8832 for this issue. Thanks.

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8832

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

Title:
  [Bionic] i915 incomplete fix for CVE-2019-14615

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

Bug description:
  [Impact]

  Gregory Herrero reported that the proof-of-concept for CVE-2019-14615
  indicates that the information leak is not fixed in the Bionic 4.15
  kernel as indicated by USN-4255-1:

   https://usn.ubuntu.com/4255-1/

  This only affects Ubuntu's 4.15 kernel series. Xenial (4.4), Disco
  (5.0), Eoan (5.3), and Focal (5.4) are not affected by this incomplete
  fix issue.

  I've verified this by testing each Ubuntu release with the proof-of-
  concept. I then tested vanilla 4.15 with commit bc8a76a152c5
  ("drm/i915/gen9: Clear residual context state on context switch")
  applied, which is the fix for CVE-2019-14615, and verified that the
  proof-of-concept showed that the info leak was still possible. I then
  tested vanilla 4.16 with commit bc8a76a152c5 applied to verify that
  the proof-of-concept showed that the info leak was fixed.

  After bisecting changes to the DRM subsystem as well as the i915
  driver, it looks like commit d2b4b97933f5 ("drm/i915: Record the
  default hw state after reset upon load") as well as its prerequisites
  are necessary to fully fix CVE-2019-14615 in 4.15 based kernels.

  [Test Case]

  A proof-of-concept for CVE-2019-14615 became available once the issue
  was made public. It can be found here:

   https://github.com/HE-Wenjian/iGPU-Leak

  Steps to use the proof-of-concept:

   $ git clone https://github.com/HE-Wenjian/iGPU-Leak.git

   # In one terminal
   $ cd iGPU-Leak/demo/SLM_Leak/
   $ ./run_victim.sh

   # In another terminal
   $ cd iGPU-Leak/demo/SLM_Leak/
   $ ./run_attacker.sh

   # In the terminal running run_attacker.sh, ensure that all data dumped
   # to the terminal is zeros and that there is no non-zero data. You'll
   # have to closely monitor the script for a minute or so to ensure that
   # the information leak is not possible.

  [Regression Potential]

  TODO

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

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


[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

2020-02-12 Thread Seth Arnold
$ uname -a
Linux millbarge 5.4.0-12-generic #15-Ubuntu SMP Tue Jan 21 15:12:29 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
$ grep FTRACE /boot/config-`uname -r`
CONFIG_KPROBES_ON_FTRACE=y
CONFIG_HAVE_KPROBES_ON_FTRACE=y
CONFIG_STM_SOURCE_FTRACE=m
# CONFIG_PSTORE_FTRACE is not set
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_DYNAMIC_FTRACE_WITH_REGS=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_FTRACE=y
CONFIG_FTRACE_SYSCALLS=y
CONFIG_DYNAMIC_FTRACE=y
CONFIG_DYNAMIC_FTRACE_WITH_REGS=y
CONFIG_FTRACE_MCOUNT_RECORD=y
# CONFIG_FTRACE_STARTUP_TEST is not set

$ sudo ls -l /sys/kernel/debug/tracing/available_filter_functions
ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
$ sudo kprobe-perf -s 'p:shrink_node'
ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.

Are you using secure boot?

$ dmesg | grep -i secure
[0.00] secureboot: Secure boot enabled
[0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
[0.019867] secureboot: Secure boot enabled
[0.965284] integrity: Loaded X.509 cert 'millbarge Secure Boot Module 
Signature key: effb550c01bc71fba674d2a0b19930ccde197df8'
[   72.131681] Bluetooth: hci0: Secure boot is enabled

Thanks

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

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None

[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'

2020-04-06 Thread Seth Arnold
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Public Security to Public

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

Title:
  Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. 
The test steps are as follows:
  # echo 1> / proc / sys / kernel / sysrq
  # echo c> / proc / sysrq-trigger
  The logs are as follows:

  kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 
/proc/vmcore /var/crash/202003251128/dump-incomplete
  kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0
  kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8
  kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud
  kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to 
physical address.
  kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032
  kdump-tools[646]: validate_mem_section: Can't read mem_section array.
  kdump-tools[646]: get_mem_section: Could not validate mem_section.
  kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section.
  kdump-tools[646]: makedumpfile Failed.
  kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp'

  But when I use the HWE kernel, I find that there is no such problem.
  The HEW kernel version: 5.3.0-42-generic

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

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


[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

2020-04-07 Thread Seth Arnold
Thanks Andrea, I don't think that helped. I'll attach a file with vmstat
1 output and funclatency output, along with a few notes on the testing.

Thanks

** Attachment added: "after-limiting-dirty-bytes"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861359/+attachment/5349071/+files/after-limiting-dirty-bytes

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

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed

Bug description:
  [Impact]

  High watermark boosting can cause large swap activity under certain
  memory intensive workloads, making the system very unresponsive
  (screen does not refresh, keyboard not responding, etc.).

  This large swap activity seems to be prevented disabling high
  watermark boosting.

  [Test case]

  Opening this web page in chrome seems to be a good reproducer of the
  problem:

  
https://platform.leolabs.space/visualizations/conjunction?type=conjunction&reportId=2004981040

  When this page is opened we can clearly see from 'top' (for example)
  that the used swap is going up very quickly.

  With the fix applied swap is not used at all and the system is always
  responsive.

  [Fix]

  Set vm.watermark_boost_factor to 0, disabling watermark boosting by
  default.

  [Regression potential]

  Regression potential is minimal, setting vm.watermark_boost_factor to
  0 by default restores the old kernel behavior before watermark
  boosting was introduced. In case of unexpected regressions we can
  always fix this in user-space via sysctl.

  [Original report]

  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
     Mixer name : 'Realtek ALC285'
     Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
     Controls  : 53
     Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
     Mixer name : 'USB Mixer'
     Components : 'USB17ef:306f'
     Controls  : 9
     Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No A

[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

2020-04-07 Thread Seth Arnold
I should point out that the period bursts of writes every five seconds
in my vmstat 1 output is due to zfs's flushing mechanism; by default it
flushes dirty pages every five seconds.

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

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed

Bug description:
  [Impact]

  High watermark boosting can cause large swap activity under certain
  memory intensive workloads, making the system very unresponsive
  (screen does not refresh, keyboard not responding, etc.).

  This large swap activity seems to be prevented disabling high
  watermark boosting.

  [Test case]

  Opening this web page in chrome seems to be a good reproducer of the
  problem:

  
https://platform.leolabs.space/visualizations/conjunction?type=conjunction&reportId=2004981040

  When this page is opened we can clearly see from 'top' (for example)
  that the used swap is going up very quickly.

  With the fix applied swap is not used at all and the system is always
  responsive.

  [Fix]

  Set vm.watermark_boost_factor to 0, disabling watermark boosting by
  default.

  [Regression potential]

  Regression potential is minimal, setting vm.watermark_boost_factor to
  0 by default restores the old kernel behavior before watermark
  boosting was introduced. In case of unexpected regressions we can
  always fix this in user-space via sysctl.

  [Original report]

  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
     Mixer name : 'Realtek ALC285'
     Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
     Controls  : 53
     Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
     Mixer name : 'USB Mixer'
     Components : 'USB17ef:306f'
     Controls  : 9
     Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET69W(

[Kernel-packages] [Bug 1814983] Re: zfs poor sustained read performance from ssd pool

2020-04-16 Thread Seth Arnold
Thanks Colin,

I believe that bountysource.com url is a scrape of
https://github.com/openzfs/zfs/issues/6223

I hadn't seen much of this information before.

Sadly my machine doesn't have enough memory to just keep turning up the
knobs -- the working set far exceeds the memory of my computer.

A recent archive-wide search I performed, I tried the following:

echo 126491074560 >> /sys/module/zfs/parameters/zfs_arc_max # eight gigs less 
than RAM
echo 117901139968 >> /sys/module/zfs/parameters/zfs_arc_dnode_limit # eight 
gigs less than ^^

I picked these numbers entirely at a guess. The zfs arc had previously
been 0 -- for half of ram, 64 gigabytes.

This workload seemed to run fine for longer than usual (arc_prune cpu
numbers were low, good read iops reported in zpool status output -- not
ideal indicator of actual progress, but a reasonable proxy) but
eventually the arc_prune tasks started consuming most of the CPUs, and
read iops fell to the dozens.

I haven't tried a run with silly low numbers for the arc dnode limit,
but I'm curious...

Thanks

** Bug watch added: github.com/openzfs/zfs/issues #6223
   https://github.com/openzfs/zfs/issues/6223

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

Title:
  zfs poor sustained read performance from ssd pool

Status in Native ZFS for Linux:
  Unknown
Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm seeing substantially slower read performance from an ssd pool than
  I expected.

  I have two pools on this computer; one ('fst') is four sata ssds, the
  other ('srv') is nine spinning metal drives.

  With a long-running ripgrep process on the fst pool, performance
  started out really good and grew to astonishingly good (iirc ~30kiops,
  as measured by zpool iostat -v 1). However after a few hours the
  performance has dropped to 30-40 iops. top reports an arc_reclaim and
  many arc_prune processes to be consuming most of the CPU time.

  I've included a screenshot of top, some output from zpool iostat -v 1,
  and arc_summary, with "===" to indicate the start of the next
  command's output:

  ===
  top (memory in gigabytes):

  top - 16:27:53 up 70 days, 16:03,  3 users,  load average: 35.67, 35.81, 35.58
  Tasks: 809 total,  19 running, 612 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.0 us, 58.1 sy,  0.0 ni, 39.2 id,  2.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  GiB Mem :  125.805 total,0.620 free,   96.942 used,   28.243 buff/cache
  GiB Swap:5.694 total,5.688 free,0.006 used.   27.840 avail Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   1523 root  20   00.0m   0.0m   0.0m R 100.0  0.0 290:52.26 
arc_reclaim 
   4484 root  20   00.0m   0.0m   0.0m R  56.2  0.0   1:18.79 arc_prune 
  
   6225 root  20   00.0m   0.0m   0.0m R  56.2  0.0   1:11.92 arc_prune 
  
   7601 root  20   00.0m   0.0m   0.0m S  56.2  0.0   2:50.25 arc_prune 
  
  30891 root  20   00.0m   0.0m   0.0m S  56.2  0.0   1:33.08 arc_prune 
  
   3057 root  20   00.0m   0.0m   0.0m S  55.9  0.0   9:00.95 arc_prune 
  
   3259 root  20   00.0m   0.0m   0.0m R  55.9  0.0   3:16.84 arc_prune 
  
  24008 root  20   00.0m   0.0m   0.0m S  55.9  0.0   1:55.71 arc_prune 
  
   1285 root  20   00.0m   0.0m   0.0m R  55.6  0.0   3:20.52 arc_prune 
  
   5345 root  20   00.0m   0.0m   0.0m R  55.6  0.0   1:15.99 arc_prune 
  
  30121 root  20   00.0m   0.0m   0.0m S  55.6  0.0   1:35.50 arc_prune 
  
  31192 root  20   00.0m   0.0m   0.0m S  55.6  0.0   6:17.16 arc_prune 
  
  32287 root  20   00.0m   0.0m   0.0m S  55.6  0.0   1:28.02 arc_prune 
  
  32625 root  20   00.0m   0.0m   0.0m R  55.6  0.0   1:27.34 arc_prune 
  
  22572 root  20   00.0m   0.0m   0.0m S  55.3  0.0  10:02.92 arc_prune 
  
  31989 root  20   00.0m   0.0m   0.0m R  55.3  0.0   1:28.03 arc_prune 
  
   3353 root  20   00.0m   0.0m   0.0m R  54.9  0.0   8:58.81 arc_prune 
  
  10252 root  20   00.0m   0.0m   0.0m R  54.9  0.0   2:36.37 arc_prune 
  
   1522 root  20   00.0m   0.0m   0.0m S  53.9  0.0 15

[Kernel-packages] [Bug 1814983] Re: zfs poor sustained read performance from ssd pool

2020-04-16 Thread Seth Arnold
Writing 8589934592 (eight gigs) into the zfs_arc_dnode_limit seemed to
make an improvement: the arc_prune threads would periodically spike
above 20% CPU use, but would return to 2-5% CPU use quickly; it worked
well for a long time, perhaps even hours, before all the arc_prune
threads returned to ~50% CPU use.

I tried one gigabyte for a bit but the arc_prune threads returned
quickly. Tuning this may take a bit.

Thanks for the tip.

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

Title:
  zfs poor sustained read performance from ssd pool

Status in Native ZFS for Linux:
  Unknown
Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm seeing substantially slower read performance from an ssd pool than
  I expected.

  I have two pools on this computer; one ('fst') is four sata ssds, the
  other ('srv') is nine spinning metal drives.

  With a long-running ripgrep process on the fst pool, performance
  started out really good and grew to astonishingly good (iirc ~30kiops,
  as measured by zpool iostat -v 1). However after a few hours the
  performance has dropped to 30-40 iops. top reports an arc_reclaim and
  many arc_prune processes to be consuming most of the CPU time.

  I've included a screenshot of top, some output from zpool iostat -v 1,
  and arc_summary, with "===" to indicate the start of the next
  command's output:

  ===
  top (memory in gigabytes):

  top - 16:27:53 up 70 days, 16:03,  3 users,  load average: 35.67, 35.81, 35.58
  Tasks: 809 total,  19 running, 612 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.0 us, 58.1 sy,  0.0 ni, 39.2 id,  2.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  GiB Mem :  125.805 total,0.620 free,   96.942 used,   28.243 buff/cache
  GiB Swap:5.694 total,5.688 free,0.006 used.   27.840 avail Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   1523 root  20   00.0m   0.0m   0.0m R 100.0  0.0 290:52.26 
arc_reclaim 
   4484 root  20   00.0m   0.0m   0.0m R  56.2  0.0   1:18.79 arc_prune 
  
   6225 root  20   00.0m   0.0m   0.0m R  56.2  0.0   1:11.92 arc_prune 
  
   7601 root  20   00.0m   0.0m   0.0m S  56.2  0.0   2:50.25 arc_prune 
  
  30891 root  20   00.0m   0.0m   0.0m S  56.2  0.0   1:33.08 arc_prune 
  
   3057 root  20   00.0m   0.0m   0.0m S  55.9  0.0   9:00.95 arc_prune 
  
   3259 root  20   00.0m   0.0m   0.0m R  55.9  0.0   3:16.84 arc_prune 
  
  24008 root  20   00.0m   0.0m   0.0m S  55.9  0.0   1:55.71 arc_prune 
  
   1285 root  20   00.0m   0.0m   0.0m R  55.6  0.0   3:20.52 arc_prune 
  
   5345 root  20   00.0m   0.0m   0.0m R  55.6  0.0   1:15.99 arc_prune 
  
  30121 root  20   00.0m   0.0m   0.0m S  55.6  0.0   1:35.50 arc_prune 
  
  31192 root  20   00.0m   0.0m   0.0m S  55.6  0.0   6:17.16 arc_prune 
  
  32287 root  20   00.0m   0.0m   0.0m S  55.6  0.0   1:28.02 arc_prune 
  
  32625 root  20   00.0m   0.0m   0.0m R  55.6  0.0   1:27.34 arc_prune 
  
  22572 root  20   00.0m   0.0m   0.0m S  55.3  0.0  10:02.92 arc_prune 
  
  31989 root  20   00.0m   0.0m   0.0m R  55.3  0.0   1:28.03 arc_prune 
  
   3353 root  20   00.0m   0.0m   0.0m R  54.9  0.0   8:58.81 arc_prune 
  
  10252 root  20   00.0m   0.0m   0.0m R  54.9  0.0   2:36.37 arc_prune 
  
   1522 root  20   00.0m   0.0m   0.0m S  53.9  0.0 158:42.45 arc_prune 
  
   3694 root  20   00.0m   0.0m   0.0m R  53.9  0.0   1:20.79 arc_prune 
  
  13394 root  20   00.0m   0.0m   0.0m R  53.9  0.0  10:35.78 arc_prune 
  
  24592 root  20   00.0m   0.0m   0.0m R  53.9  0.0   1:54.19 arc_prune 
  
  25859 root  20   00.0m   0.0m   0.0m S  53.9  0.0   1:51.71 arc_prune 
  
   8194 root  20   00.0m   0.0m   0.0m S  53.6  0.0   0:54.51 arc_prune 
  
  18472 root  20   00.0m   0.0m   0.0m R  53.6  0.0   2:08.73 ar

[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

2020-04-16 Thread Seth Arnold
Andrea, I've been running the v1 kernel for a day or so now:

[0.00] Linux version 5.4.0-24-generic (arighi@sita) (gcc version
9.3.0 (Ubuntu 9.3.0-10ubuntu1)) #28+lp1861359v1 SMP Wed Apr 15 14:49:33
UTC 2020 (Ubuntu 5.4.0-24.28+lp1861359v1-generic 5.4.30)

$ uptime
 02:21:45 up 1 day, 9 min, 14 users,  load average: 0.42, 0.25, 0.23

and have not seen any hangs or stalls of any sort in the ~ten hours that
I've been using it.

Normally these problems start to appear about a day into use, so it's
perhaps still early to declare success, but this is looking promising.

Even loading https://platform.leolabs.space/visualization in firefox
just causes momentary glitches in mouse movement, like 50ms kind of
range. (I know this range is pretty poor for humans to tell, but it sure
feels like less than half a second by a lot.)

Thanks

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

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed

Bug description:
  [Impact]

  High watermark boosting can cause large swap activity under certain
  memory intensive workloads, making the system very unresponsive
  (screen does not refresh, keyboard not responding, etc.).

  This large swap activity seems to be prevented disabling high
  watermark boosting.

  [Test case]

  Opening this web page in chrome seems to be a good reproducer of the
  problem:

  
https://platform.leolabs.space/visualizations/conjunction?type=conjunction&reportId=2004981040

  When this page is opened we can clearly see from 'top' (for example)
  that the used swap is going up very quickly.

  With the fix applied swap is not used at all and the system is always
  responsive.

  [Fix]

  Set vm.watermark_boost_factor to 0, disabling watermark boosting by
  default.

  [Regression potential]

  Regression potential is minimal, setting vm.watermark_boost_factor to
  0 by default restores the old kernel behavior before watermark
  boosting was introduced. In case of unexpected regressions we can
  always fix this in user-space via sysctl.

  [Original report]

  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
     Mixer name : 'Realtek ALC285'
     Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
     Controls  : 53
     Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
     Mixer name : 'USB Mixer'
     Components : 'USB17ef:306f'
     Controls  : 9
     Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-ge

[Kernel-packages] [Bug 1814983] Re: zfs poor sustained read performance from ssd pool

2020-04-17 Thread Seth Arnold
Andreas, this system is running 18.04 LTS, 0.7.5-1ubuntu16.8,
4.15.0-91-generic.

It has 128 gigs of ram; the workload is running ripgrep on an entire
unpacked Ubuntu source archive, roughly 193 million files, 3.8 TB of
data, on a single raidz1 ssd vdev.

So I have no illusions that this workload fits into the available
memory, but it's unfortunate that the best performance I've found so far
includes dropping caches every few minutes.

Thanks

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

Title:
  zfs poor sustained read performance from ssd pool

Status in Native ZFS for Linux:
  Unknown
Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm seeing substantially slower read performance from an ssd pool than
  I expected.

  I have two pools on this computer; one ('fst') is four sata ssds, the
  other ('srv') is nine spinning metal drives.

  With a long-running ripgrep process on the fst pool, performance
  started out really good and grew to astonishingly good (iirc ~30kiops,
  as measured by zpool iostat -v 1). However after a few hours the
  performance has dropped to 30-40 iops. top reports an arc_reclaim and
  many arc_prune processes to be consuming most of the CPU time.

  I've included a screenshot of top, some output from zpool iostat -v 1,
  and arc_summary, with "===" to indicate the start of the next
  command's output:

  ===
  top (memory in gigabytes):

  top - 16:27:53 up 70 days, 16:03,  3 users,  load average: 35.67, 35.81, 35.58
  Tasks: 809 total,  19 running, 612 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.0 us, 58.1 sy,  0.0 ni, 39.2 id,  2.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  GiB Mem :  125.805 total,0.620 free,   96.942 used,   28.243 buff/cache
  GiB Swap:5.694 total,5.688 free,0.006 used.   27.840 avail Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   1523 root  20   00.0m   0.0m   0.0m R 100.0  0.0 290:52.26 
arc_reclaim 
   4484 root  20   00.0m   0.0m   0.0m R  56.2  0.0   1:18.79 arc_prune 
  
   6225 root  20   00.0m   0.0m   0.0m R  56.2  0.0   1:11.92 arc_prune 
  
   7601 root  20   00.0m   0.0m   0.0m S  56.2  0.0   2:50.25 arc_prune 
  
  30891 root  20   00.0m   0.0m   0.0m S  56.2  0.0   1:33.08 arc_prune 
  
   3057 root  20   00.0m   0.0m   0.0m S  55.9  0.0   9:00.95 arc_prune 
  
   3259 root  20   00.0m   0.0m   0.0m R  55.9  0.0   3:16.84 arc_prune 
  
  24008 root  20   00.0m   0.0m   0.0m S  55.9  0.0   1:55.71 arc_prune 
  
   1285 root  20   00.0m   0.0m   0.0m R  55.6  0.0   3:20.52 arc_prune 
  
   5345 root  20   00.0m   0.0m   0.0m R  55.6  0.0   1:15.99 arc_prune 
  
  30121 root  20   00.0m   0.0m   0.0m S  55.6  0.0   1:35.50 arc_prune 
  
  31192 root  20   00.0m   0.0m   0.0m S  55.6  0.0   6:17.16 arc_prune 
  
  32287 root  20   00.0m   0.0m   0.0m S  55.6  0.0   1:28.02 arc_prune 
  
  32625 root  20   00.0m   0.0m   0.0m R  55.6  0.0   1:27.34 arc_prune 
  
  22572 root  20   00.0m   0.0m   0.0m S  55.3  0.0  10:02.92 arc_prune 
  
  31989 root  20   00.0m   0.0m   0.0m R  55.3  0.0   1:28.03 arc_prune 
  
   3353 root  20   00.0m   0.0m   0.0m R  54.9  0.0   8:58.81 arc_prune 
  
  10252 root  20   00.0m   0.0m   0.0m R  54.9  0.0   2:36.37 arc_prune 
  
   1522 root  20   00.0m   0.0m   0.0m S  53.9  0.0 158:42.45 arc_prune 
  
   3694 root  20   00.0m   0.0m   0.0m R  53.9  0.0   1:20.79 arc_prune 
  
  13394 root  20   00.0m   0.0m   0.0m R  53.9  0.0  10:35.78 arc_prune 
  
  24592 root  20   00.0m   0.0m   0.0m R  53.9  0.0   1:54.19 arc_prune 
  
  25859 root  20   00.0m   0.0m   0.0m S  53.9  0.0   1:51.71 arc_prune 
  
   8194 root  20   00.0m   0.0m   0.0m S  53.6  0.0   0:54.51 arc_prune 
  
  18472 root  20   00.0m   0.0m   0.0m R  53.6  0.0  

[Kernel-packages] [Bug 1814983] Re: zfs poor sustained read performance from ssd pool

2020-04-17 Thread Seth Arnold
Colin, thanks for the link to https://github.com/openzfs/zfs/issues/9966
; unfortunately I think that's a different problem, my meta use seems
less drastic than the github issue

arc_prune   41859269059
arc_meta_used   43590932168
arc_meta_limit  494868305920
arc_dnode_limit 44294967296
arc_meta_max479969748624
arc_meta_min416777216

It looks like there's still 14898557296 bytes available for arc_meta.

Do you know off-hand what the comment about the l2arc issue is? My l2arc
is 1TB, well above 320 gigs.

Here's where my stats are now (the system is not currently under any
real load):

$ cat /proc/spl/kstat/zfs/arcstats
13 1 0x01 96 4608 10492531405 1374854032619736
nametype data
hits46820744874
misses  4953303948
demand_data_hits41163033450
demand_data_misses  4112593263
demand_metadata_hits45398565264
demand_metadata_misses  4771209639
prefetch_data_hits  43978361
prefetch_data_misses44454061
prefetch_metadata_hits  4255167799
prefetch_metadata_misses465046985
mru_hits42596176358
mru_ghost_hits  47960783
mfu_hits43972213379
mfu_ghost_hits  437066000
deleted 4624581823
mutex_miss  466283716
access_skip 4112
evict_skip  459660318004
evict_not_enough4531586443
evict_l2_cached 4758952236544
evict_l2_eligible   46629993222656
evict_l2_ineligible 41055824726016
evict_l2_skip   44093
hash_elements   41382698
hash_elements_max   47705756
hash_collisions 4101258453
hash_chains 454374
hash_chain_max  46
p   43403412095
c   49636886736
c_min   44221281536
c_max   4126491074560
size49501317832
compressed_size 46533731328
uncompressed_size   412946349568
overhead_size   41324591616
hdr_size4125140504
data_size   45910385664
metadata_size   41947937280
dbuf_size   4313455312
dnode_size  4801582080
bonus_size  4304865408
anon_size   469632
anon_evictable_data 40
anon_evictable_metadata 40
mru_size42874187264
mru_evictable_data  42820684800
mru_evictable_metadata  411149312
mru_ghost_size  41934149120
mru_ghost_evictable_data4254414848
mru_ghost_evictable_metadata41679734272
mfu_size44984066048
mfu_evictable_data  43089700864
mfu_evictable_metadata  4293028864
mfu_ghost_size  432707072
mfu_ghost_evictable_data432707072
mfu_ghost_evictable_metadata40
l2_hits 416313870
l2_misses   4936990042
l2_feeds41342134
l2_rw_clash 41
l2_read_bytes   473933849600
l2_write_bytes  4218946362880
l2_writes_sent  445529
l2_writes_done  445529
l2_writes_error 40
l2_writes_lock_retry421
l2_evict_lock_retry 40
l2_evict_reading40
l2_evict_l1cached   40
l2_free_on_write4878
l2_abort_lowmem 4496
l2_cksum_bad40
l2_io_error 40
l2_size 4130902416896
l2_asize498157307392
l2_hdr_size 497951584
memory_throttle_count   40
memory_direct_count 4856012
memory_indirect_count   4233680
memory_all_bytes4135081009152
memory_free_bytes   4120346943488
memory_available_bytes  3118236303360
arc_no_grow 40
arc_tempreserve 40
arc_loaned_bytes40
arc_prune   41859269059
arc_meta_used   43590932168
arc_meta_limit  494868305920
arc_dnode_limit 44294967296
arc_meta_max479969748624
arc

[Kernel-packages] [Bug 1814983] Re: zfs poor sustained read performance from ssd pool

2020-04-17 Thread Seth Arnold
I forgot to mention, my l2arc is used on the second pool on this system:

$ zpool iostat -v
   capacity operations 
bandwidth 
pool alloc   free   read  write   read  
write
---  -  -  -  -  -  
-
fst  1.79T  1.84T611 52  5.51M  
 968K
  raidz1 1.79T  1.84T611 52  5.51M  
 968K
wwn-0x5002538e4095da39   -  -154 12  1.40M  
 242K
wwn-0x5002538e4095bdd6   -  -150 12  1.36M  
 242K
wwn-0x5002538e4093c6fd   -  -154 13  1.40M  
 242K
wwn-0x5002538e4095da30   -  -150 13  1.36M  
 242K
---  -  -  -  -  -  
-
srv  1.69T  6.47T 45 11  4.08M  
 624K
  mirror  576G  2.16T 15  3  1.36M  
 206K
ata-HGST_HUS724030ALA640_PN2234P8KTWJYY  -  -  5  1   464K  
68.8K
ata-HGST_HUS724030ALA640_PN2234P9G620TW  -  -  5  1   465K  
68.8K
ata-HGST_HUS724030ALA640_PN2234P9G66E2U  -  -  5  1   465K  
68.8K
  mirror  576G  2.16T 15  3  1.36M  
 209K
ata-HGST_HUS724030ALA640_PN2234P9G69TKU  -  -  5  1   465K  
69.7K
ata-HGST_HUS724030ALA640_PN2234P9G69TXU  -  -  5  1   464K  
69.7K
ata-HGST_HUS724030ALA640_PN2234P9G69U2U  -  -  5  1   464K  
69.7K
  mirror  576G  2.16T 15  3  1.36M  
 208K
ata-HGST_HUS724030ALA640_PN2234P9G6EBUU  -  -  5  1   464K  
69.3K
ata-HGST_HUS724030ALA640_PN2234P9G6ESAU  -  -  5  1   464K  
69.3K
ata-HGST_HUS724030ALA640_PN2234P9G6G70U  -  -  5  1   464K  
69.3K
logs -  -  -  -  -  
-
  nvme0n1p1   776K  19.9G  0  0  1  
1
cache-  -  -  -  -  
-
  nvme0n1p2  91.4G  1006G 11  1  52.5K  
 155K
---  -  -  -  -  -  
-

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

Title:
  zfs poor sustained read performance from ssd pool

Status in Native ZFS for Linux:
  Unknown
Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm seeing substantially slower read performance from an ssd pool than
  I expected.

  I have two pools on this computer; one ('fst') is four sata ssds, the
  other ('srv') is nine spinning metal drives.

  With a long-running ripgrep process on the fst pool, performance
  started out really good and grew to astonishingly good (iirc ~30kiops,
  as measured by zpool iostat -v 1). However after a few hours the
  performance has dropped to 30-40 iops. top reports an arc_reclaim and
  many arc_prune processes to be consuming most of the CPU time.

  I've included a screenshot of top, some output from zpool iostat -v 1,
  and arc_summary, with "===" to indicate the start of the next
  command's output:

  ===
  top (memory in gigabytes):

  top - 16:27:53 up 70 days, 16:03,  3 users,  load average: 35.67, 35.81, 35.58
  Tasks: 809 total,  19 running, 612 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.0 us, 58.1 sy,  0.0 ni, 39.2 id,  2.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  GiB Mem :  125.805 total,0.620 free,   96.942 used,   28.243 buff/cache
  GiB Swap:5.694 total,5.688 free,0.006 used.   27.840 avail Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   1523 root  20   00.0m   0.0m   0.0m R 100.0  0.0 290:52.26 
arc_reclaim 
   4484 root  20   00.0m   0.0m   0.0m R  56.2  0.0   1:18.79 arc_prune 
  
   6225 root  20   00.0m   0.0m   0.0m R  56.2  0.0   1:11.92 arc_prune 
  
   7601 root  20   00.0m   0.0m   0.0m S  56.2  0.0   2:50.25 arc_prune 
  
  30891 root  20   00.0m   0.0m   0.0m S  56.2  0.0   1:33.08 arc_prune 
  
   3057 root  20   00.0m   0.0m   0.0m S  55.9  0.0   9:00.95 arc_prune 
  
   3259 root  20   00.0m   0.0m   0.0m R  55.9  0.0   3:16.84 arc_prune 
  
  24008 root  20

[Kernel-packages] [Bug 1876697] Re: test_regression_testsuite from ubuntu_qrt_apparmor failed on Focal zVM

2020-05-06 Thread Seth Arnold
This feels related to
https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1875665 which was
filed by amd64 users.

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

Title:
  test_regression_testsuite from ubuntu_qrt_apparmor failed on Focal zVM

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

Bug description:
  Issue found on zVM "kernel04" with 5.4.0-29.33

   ==
   FAIL: test_regression_testsuite (__main__.ApparmorTestsuites)
   Run kernel regression tests 
   --
   Traceback (most recent call last):
 File "./test-apparmor.py", line 1746, in test_regression_testsuite
   self.assertEqual(expected, rc, result + report)
   AssertionError: Got exit code 2, expected 0 
   
   running aa_exec
   
   running access
   xfail: ACCESS file rx (r)
   xfail: ACCESS file rwx (r)
   xfail: ACCESS file r (wx)
   xfail: ACCESS file rx (wx)
   xfail: ACCESS file rwx (wx)
   xfail: ACCESS dir rwx (r)
   xfail: ACCESS dir r (wx)
   xfail: ACCESS dir rx (wx)
   xfail: ACCESS dir rwx (wx)
   
   running at_secure
   
   running introspect
   
   running capabilities
   (ptrace)
   (sethostname)
   (setdomainname)
   (setpriority)
   (setscheduler)
   Error: syscall_setscheduler failed. Test 'syscall_setscheduler -- 
unconfined' was expected to 'pass'. Reason for failure 'FAIL: Can't set 
SCHED_RR: Operation not permitted'
   Error: syscall_setscheduler failed. Test 'syscall_setscheduler -- all caps' 
was expected to 'pass'. Reason for failure 'FAIL: Can't set SCHED_RR: Operation 
not permitted'
 preparing apparmor_2.13.3-7ubuntu5.dsc...  done
   Error: syscall_setscheduler failed. Test 'syscall_setscheduler -- capability 
sys_nice' was expected to 'pass'. Reason for failure 'FAIL: Can't set SCHED_RR: 
Operation not permitted'
   Error: changehat_wrapper failed. Test 'syscall_setscheduler changehat -- all 
caps' was expected to 'pass'. Reason for failure 'FAIL: Can't set SCHED_RR: 
Operation not permitted'
   Error: changehat_wrapper failed. Test 'syscall_setscheduler changehat -- 
capability sys_nice' was expected to 'pass'. Reason for failure 'FAIL: Can't 
set SCHED_RR: Operation not permitted'
   (reboot)
   (chroot)
   (mlockall)
   (net_raw)

  Please find attachment for the complete test log.

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

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


[Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

2020-05-11 Thread Seth Arnold
Here's the part that looks important; the whole dmesg is in the
attachment.

Thanks

[  761.730488] dnone_free_ramge: nblks = 0, trunc = 1, len = 
18446744073709551615, blkshift = 0
[  761.730542] dnode_free_range: nblks == 0, len == 18446744073709551615
   , off=0
[  761.730543] range_tree_clear: size == 0
[  761.730605] VERIFY(size != 0) failed
[  761.730625] PANIC at range_tree.c:307:range_tree_find_impl()
[  761.730653] Showing stack for process 23913
[  761.730656] CPU: 31 PID: 23913 Comm: receive_writer Tainted: P   OE  
  4.15.0-99-generic #100-Ubuntu
[  761.730657] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 2.0 
12/17/2015
[  761.730658] Call Trace:
[  761.730668]  dump_stack+0x6d/0x8e
[  761.730679]  spl_dumpstack+0x42/0x50 [spl]
[  761.730684]  spl_panic+0xc8/0x110 [spl]
[  761.730690]  ? fbcon_cursor+0x13e/0x1c0
[  761.730695]  ? atomic_notifier_call_chain+0x1a/0x20
[  761.730700]  ? vt_console_print+0x240/0x410
[  761.730705]  ? up+0x32/0x50
[  761.730708]  ? console_unlock+0x2a1/0x560
[  761.730767]  range_tree_find_impl+0x88/0x90 [zfs]
[  761.730769]  ? printk+0x52/0x6e
[  761.730810]  range_tree_clear+0x54/0x70 [zfs]
[  761.730843]  dnode_free_range+0x15b/0x720 [zfs]
[  761.730874]  dmu_object_free+0x75/0xc0 [zfs]
[  761.730904]  dmu_free_long_object+0x9f/0xc0 [zfs]
[  761.730934]  receive_freeobjects.isra.12+0x7a/0x100 [zfs]
[  761.730963]  receive_writer_thread+0x6d2/0xa60 [zfs]
[  761.730965]  ? set_curr_task_fair+0x2b/0x60
[  761.730970]  ? spl_kmem_free+0x33/0x40 [spl]
[  761.730973]  ? kfree+0x162/0x180
[  761.731001]  ? receive_free.isra.13+0xc0/0xc0 [zfs]
[  761.731006]  thread_generic_wrapper+0x74/0x90 [spl]
[  761.731008]  kthread+0x121/0x140
[  761.731012]  ? __thread_exit+0x20/0x20 [spl]
[  761.731014]  ? kthread_create_worker_on_cpu+0x70/0x70
[  761.731018]  ret_from_fork+0x35/0x40
[  967.430681] INFO: task txg_quiesce:4049 blocked for more than 120 seconds.
[  967.430739]   Tainted: P   OE4.15.0-99-generic #100-Ubuntu
[  967.430785] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  967.430836] txg_quiesce D0  4049  2 0x8000
[  967.430840] Call Trace:
[  967.430853]  __schedule+0x24e/0x880
[  967.430858]  schedule+0x2c/0x80
[  967.430875]  cv_wait_common+0x11e/0x140 [spl]
[  967.430885]  ? wait_woken+0x80/0x80
[  967.430893]  __cv_wait+0x15/0x20 [spl]
[  967.431010]  txg_quiesce_thread+0x2cb/0x3d0 [zfs]
[  967.431078]  ? txg_delay+0x1b0/0x1b0 [zfs]
[  967.431088]  thread_generic_wrapper+0x74/0x90 [spl]
[  967.431093]  kthread+0x121/0x140
[  967.431099]  ? __thread_exit+0x20/0x20 [spl]
[  967.431102]  ? kthread_create_worker_on_cpu+0x70/0x70
[  967.431107]  ret_from_fork+0x35/0x40
[  967.431140] INFO: task zfs:23834 blocked for more than 120 seconds.
[  967.431184]   Tainted: P   OE4.15.0-99-generic #100-Ubuntu
[  967.431229] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  967.431279] zfs D0 23834  23831 0x8080
[  967.431282] Call Trace:
[  967.431286]  __schedule+0x24e/0x880
[  967.431290]  schedule+0x2c/0x80
[  967.431298]  cv_wait_common+0x11e/0x140 [spl]
[  967.431303]  ? wait_woken+0x80/0x80
[  967.431310]  __cv_wait+0x15/0x20 [spl]
[  967.431367]  dmu_recv_stream+0xa51/0xef0 [zfs]
[  967.431438]  zfs_ioc_recv_impl+0x306/0x1100 [zfs]
[  967.431487]  ? dbuf_rele+0x36/0x40 [zfs]
[  967.431555]  zfs_ioc_recv_new+0x33d/0x410 [zfs]
[  967.431564]  ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl]
[  967.431571]  ? spl_vmem_alloc+0x19/0x20 [spl]
[  967.431584]  ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair]
[  967.431590]  ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair]
[  967.431596]  ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair]
[  967.431660]  zfsdev_ioctl+0x451/0x610 [zfs]
[  967.431672]  do_vfs_ioctl+0xa8/0x630
[  967.431677]  ? __audit_syscall_entry+0xbc/0x110
[  967.431682]  ? syscall_trace_enter+0x1da/0x2d0
[  967.431685]  SyS_ioctl+0x79/0x90
[  967.431688]  do_syscall_64+0x73/0x130
[  967.431693]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[  967.431696] RIP: 0033:0x7f4c273385d7
[  967.431698] RSP: 002b:7ffed780e068 EFLAGS: 0246 ORIG_RAX: 
0010
[  967.431701] RAX: ffda RBX: 5a46 RCX: 7f4c273385d7
[  967.431702] RDX: 7ffed780e080 RSI: 5a46 RDI: 0006
[  967.431704] RBP: 7ffed780e080 R08: 7f4c2760de20 R09: 
[  967.431705] R10: 55dc5929b010 R11: 0246 R12: 7ffed78116b0
[  967.431707] R13: 0006 R14: 55dc592a2f10 R15: 000c
[  967.431722] INFO: task receive_writer:23913 blocked for more than 120 
seconds.
[  967.431771]   Tainted: P   OE4.15.0-99-generic #100-Ubuntu
[  967.431816] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  967.431867] receive_writer  D0 23913  2 0x8080
[  967.431870] Call Trace:
[  967.431874]  __schedule+0x24e/0x880
[  96

[Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

2020-05-12 Thread Seth Arnold
Thanks Colin!

[  271.628232] dnone_free_ramge: nblks = 0, trunc = 1, len = 
18446744073709551615, blkshift = 0
[  271.628297] dnode_free_range: nblks == 0, len == 18446744073709551615
   , off=0
[  271.628298] range_tree_clear: size == 0
[  271.628375] range_tree_find_impl: size == 0
[  271.628393] VERIFY(size != 0) failed
[  271.628409] PANIC at range_tree.c:168:range_tree_add()
[  271.628429] Showing stack for process 7960
[  271.628432] CPU: 26 PID: 7960 Comm: receive_writer Tainted: P   OE   
 4.15.0-99-generic #100-Ubuntu
[  271.628433] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 2.0 
12/17/2015
[  271.628433] Call Trace:
[  271.628442]  dump_stack+0x6d/0x8e
[  271.628458]  spl_dumpstack+0x42/0x50 [spl]
[  271.628462]  spl_panic+0xc8/0x110 [spl]
[  271.628468]  ? vt_console_print+0x240/0x410
[  271.628473]  ? console_unlock+0x2a1/0x560
[  271.628475]  ? vprintk_emit+0x104/0x2c0
[  271.628477]  ? vprintk_default+0x29/0x50
[  271.628479]  ? printk+0x52/0x6e
[  271.628566]  range_tree_add+0x29b/0x300 [zfs]
[  271.628600]  ? range_tree_clear+0xa4/0xb0 [zfs]
[  271.628602]  ? printk+0x52/0x6e
[  271.628635]  dnode_free_range+0x178/0x720 [zfs]
[  271.628673]  dmu_object_free+0x6d/0xc0 [zfs]
[  271.628698]  dmu_free_long_object+0x9f/0xc0 [zfs]
[  271.628723]  receive_freeobjects.isra.12+0x7a/0x100 [zfs]
[  271.628747]  receive_writer_thread+0x6d2/0xa60 [zfs]
[  271.628750]  ? set_curr_task_fair+0x2b/0x60
[  271.628753]  ? spl_kmem_free+0x33/0x40 [spl]
[  271.628757]  ? kfree+0x162/0x180
[  271.628781]  ? receive_free.isra.13+0xc0/0xc0 [zfs]
[  271.628785]  thread_generic_wrapper+0x74/0x90 [spl]
[  271.628788]  kthread+0x121/0x140
[  271.628791]  ? __thread_exit+0x20/0x20 [spl]
[  271.628792]  ? kthread_create_worker_on_cpu+0x70/0x70
[  271.628796]  ret_from_fork+0x35/0x40


** Attachment added: "dmesg-0.7.5-1ubuntu16.10~lp1861235.2"
   
https://bugs.launchpad.net/linux/+bug/1861235/+attachment/5370673/+files/dmesg-0.7.5-1ubuntu16.10~lp1861235.2

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

Title:
  zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

Status in Linux:
  New
Status in zfs-linux package in Ubuntu:
  Incomplete
Status in zfs-linux source package in Bionic:
  New

Bug description:
  Same as bug 1861228 but with a newer kernel installed.

  [  790.702566] VERIFY(size != 0) failed
  [  790.702590] PANIC at range_tree.c:304:range_tree_find_impl()
  [  790.702611] Showing stack for process 28685
  [  790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P   O 
4.15.0-76-generic #86-Ubuntu
  [  790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 
2.0 12/17/2015
  [  790.702616] Call Trace:
  [  790.702626]  dump_stack+0x6d/0x8e
  [  790.702637]  spl_dumpstack+0x42/0x50 [spl]
  [  790.702640]  spl_panic+0xc8/0x110 [spl]
  [  790.702645]  ? __switch_to_asm+0x41/0x70
  [  790.702714]  ? arc_prune_task+0x1a/0x40 [zfs]
  [  790.702740]  ? dbuf_dirty+0x43d/0x850 [zfs]
  [  790.702745]  ? getrawmonotonic64+0x43/0xd0
  [  790.702746]  ? getrawmonotonic64+0x43/0xd0
  [  790.702775]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702778]  ? getrawmonotonic64+0x43/0xd0
  [  790.702805]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702807]  ? mutex_lock+0x12/0x40
  [  790.702833]  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
  [  790.702866]  range_tree_find_impl+0x88/0x90 [zfs]
  [  790.702870]  ? spl_kmem_zalloc+0xdc/0x1a0 [spl]
  [  790.702902]  range_tree_clear+0x4f/0x60 [zfs]
  [  790.702930]  dnode_free_range+0x11f/0x5a0 [zfs]
  [  790.702957]  dmu_object_free+0x53/0x90 [zfs]
  [  790.702983]  dmu_free_long_object+0x9f/0xc0 [zfs]
  [  790.703010]  receive_freeobjects.isra.12+0x7a/0x100 [zfs]
  [  790.703036]  receive_writer_thread+0x6d2/0xa60 [zfs]
  [  790.703040]  ? set_curr_task_fair+0x2b/0x60
  [  790.703043]  ? spl_kmem_free+0x33/0x40 [spl]
  [  790.703048]  ? kfree+0x165/0x180
  [  790.703073]  ? receive_free.isra.13+0xc0/0xc0 [zfs]
  [  790.703078]  thread_generic_wrapper+0x74/0x90 [spl]
  [  790.703081]  kthread+0x121/0x140
  [  790.703084]  ? __thread_exit+0x20/0x20 [spl]
  [  790.703085]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  790.703088]  ret_from_fork+0x35/0x40
  [  967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds.
  [  967.636979]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637076] txg_quiesce D0 14810  2 0x8000
  [  967.637080] Call Trace:
  [  967.637089]  __schedule+0x24e/0x880
  [  967.637092]  schedule+0x2c/0x80
  [  967.637106]  cv_wait_common+0x11e/0x140 [spl]
  [  967.637114]  ? wait_woken+0x80/0x80
  [  967.637122]  __cv_wait+0x15/0x20 [spl]
  [  967.637210]  txg_quiesce_thread+0x2cb/0x3d0 [zfs]
  [  967.637278]  ? txg_delay+0x1b0/0x1

[Kernel-packages] [Bug 1814983] Re: zfs poor sustained read performance from ssd pool

2020-05-14 Thread Seth Arnold
Hello Colin, this looks promising for my arc_prune spinlock contention
problems:

https://github.com/openzfs/zfs/pull/10331

with some background here:

https://github.com/openzfs/zfs/issues/7559

This might have a simple ~dozen line fix! It's not yet reviewed by the
openzfs gurus but it sure *looks* plausible to me. I tried to bodge this
patch into the dkms module you gave me for my other zfs problem, but I
have no confidence in my work -- I tried to reduce the number of
arc_prune threads but failed, so I'm skeptical if I was able to change
anything anyway. (I'm finding dkms to be *very* confusing.)

Any chance I can ask you to put together a dkms with this patch? I'd
trust your work way further. :)

Thanks

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

Title:
  zfs poor sustained read performance from ssd pool

Status in Native ZFS for Linux:
  Unknown
Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm seeing substantially slower read performance from an ssd pool than
  I expected.

  I have two pools on this computer; one ('fst') is four sata ssds, the
  other ('srv') is nine spinning metal drives.

  With a long-running ripgrep process on the fst pool, performance
  started out really good and grew to astonishingly good (iirc ~30kiops,
  as measured by zpool iostat -v 1). However after a few hours the
  performance has dropped to 30-40 iops. top reports an arc_reclaim and
  many arc_prune processes to be consuming most of the CPU time.

  I've included a screenshot of top, some output from zpool iostat -v 1,
  and arc_summary, with "===" to indicate the start of the next
  command's output:

  ===
  top (memory in gigabytes):

  top - 16:27:53 up 70 days, 16:03,  3 users,  load average: 35.67, 35.81, 35.58
  Tasks: 809 total,  19 running, 612 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.0 us, 58.1 sy,  0.0 ni, 39.2 id,  2.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  GiB Mem :  125.805 total,0.620 free,   96.942 used,   28.243 buff/cache
  GiB Swap:5.694 total,5.688 free,0.006 used.   27.840 avail Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   1523 root  20   00.0m   0.0m   0.0m R 100.0  0.0 290:52.26 
arc_reclaim 
   4484 root  20   00.0m   0.0m   0.0m R  56.2  0.0   1:18.79 arc_prune 
  
   6225 root  20   00.0m   0.0m   0.0m R  56.2  0.0   1:11.92 arc_prune 
  
   7601 root  20   00.0m   0.0m   0.0m S  56.2  0.0   2:50.25 arc_prune 
  
  30891 root  20   00.0m   0.0m   0.0m S  56.2  0.0   1:33.08 arc_prune 
  
   3057 root  20   00.0m   0.0m   0.0m S  55.9  0.0   9:00.95 arc_prune 
  
   3259 root  20   00.0m   0.0m   0.0m R  55.9  0.0   3:16.84 arc_prune 
  
  24008 root  20   00.0m   0.0m   0.0m S  55.9  0.0   1:55.71 arc_prune 
  
   1285 root  20   00.0m   0.0m   0.0m R  55.6  0.0   3:20.52 arc_prune 
  
   5345 root  20   00.0m   0.0m   0.0m R  55.6  0.0   1:15.99 arc_prune 
  
  30121 root  20   00.0m   0.0m   0.0m S  55.6  0.0   1:35.50 arc_prune 
  
  31192 root  20   00.0m   0.0m   0.0m S  55.6  0.0   6:17.16 arc_prune 
  
  32287 root  20   00.0m   0.0m   0.0m S  55.6  0.0   1:28.02 arc_prune 
  
  32625 root  20   00.0m   0.0m   0.0m R  55.6  0.0   1:27.34 arc_prune 
  
  22572 root  20   00.0m   0.0m   0.0m S  55.3  0.0  10:02.92 arc_prune 
  
  31989 root  20   00.0m   0.0m   0.0m R  55.3  0.0   1:28.03 arc_prune 
  
   3353 root  20   00.0m   0.0m   0.0m R  54.9  0.0   8:58.81 arc_prune 
  
  10252 root  20   00.0m   0.0m   0.0m R  54.9  0.0   2:36.37 arc_prune 
  
   1522 root  20   00.0m   0.0m   0.0m S  53.9  0.0 158:42.45 arc_prune 
  
   3694 root  20   00.0m   0.0m   0.0m R  53.9  0.0   1:20.79 arc_prune 
  
  13394 root  20   00.0m   0.0m   0.0m R  53.9  0.0  10:35.78 arc_prune 
  
  24592 root  20   00.0m   0.0m   0.0m R  53.9  0.0   1:54.19 arc_prune 
  
  25859 root  20   00.

[Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

2020-05-15 Thread Seth Arnold
Hello Colin, trying the zfs recv operation on the .3 dkms eventually
kills my system dead. There was nothing on the console. The cursor on
the console stopped blinking; I couldn't switch VTs. My ssh sessions
were hung. ping reported destination host unreachable.

It ran for about two and a half minutes, transferred around 10 datasets or 
snapshots:
$ journalctl -b -1  | grep -c "COMMAND=/sbin/zfs receive"
10


Sadly, journalctl doesn't have the dmesg from the previous boot:

$ journalctl -b -1 -k
[...]
May 15 17:25:10 wopr kernel: ZFS: Loaded module 
v0.7.5-1ubuntu16.10~lp1861235.3, ZFS pool version 5000, ZFS filesystem version 5
May 15 17:25:15 wopr kernel:  zd32: p1
May 15 17:25:20 wopr kernel: pps pps0: new PPS source ptp0
May 15 17:25:20 wopr kernel: ixgbe :05:00.0: registered PHC device on 
enp5s0f0
May 15 17:25:20 wopr kernel: IPv6: ADDRCONF(NETDEV_UP): enp5s0f0: link is not 
ready
May 15 17:25:20 wopr kernel: new mount options do not match the existing 
superblock, will be ignored
May 15 17:25:21 wopr kernel: Process accounting resumed
May 15 17:25:24 wopr kernel: ixgbe :05:00.0 enp5s0f0: NIC Link is Up 1 
Gbps, Flow Control: None
May 15 17:25:24 wopr kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp5s0f0: link 
becomes ready
May 15 17:25:29 wopr kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 
state recovery directory
May 15 17:25:29 wopr kernel: NFSD: starting 90-second grace period (net 
f0a9)
May 15 17:25:32 wopr kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
May 15 17:25:32 wopr kernel: Ebtables v2.0 registered
May 15 17:25:33 wopr kernel: bridge: filtering via arp/ip/ip6tables is no 
longer available by default. Update your scripts to load br_netfilter if you 
need this.
May 15 17:25:33 wopr kernel: virbr0: port 1(virbr0-nic) entered blocking state
May 15 17:25:33 wopr kernel: virbr0: port 1(virbr0-nic) entered disabled state
May 15 17:25:33 wopr kernel: device virbr0-nic entered promiscuous mode
May 15 17:25:33 wopr kernel: nf_conntrack version 0.5.0 (65536 buckets, 262144 
max)
May 15 17:25:33 wopr kernel: virbr0: port 1(virbr0-nic) entered blocking state
May 15 17:25:33 wopr kernel: virbr0: port 1(virbr0-nic) entered listening state
May 15 17:25:33 wopr kernel: virbr0: port 1(virbr0-nic) entered disabled state


Thanks

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

Title:
  zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

Status in Linux:
  New
Status in zfs-linux package in Ubuntu:
  Incomplete
Status in zfs-linux source package in Bionic:
  New

Bug description:
  Same as bug 1861228 but with a newer kernel installed.

  [  790.702566] VERIFY(size != 0) failed
  [  790.702590] PANIC at range_tree.c:304:range_tree_find_impl()
  [  790.702611] Showing stack for process 28685
  [  790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P   O 
4.15.0-76-generic #86-Ubuntu
  [  790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 
2.0 12/17/2015
  [  790.702616] Call Trace:
  [  790.702626]  dump_stack+0x6d/0x8e
  [  790.702637]  spl_dumpstack+0x42/0x50 [spl]
  [  790.702640]  spl_panic+0xc8/0x110 [spl]
  [  790.702645]  ? __switch_to_asm+0x41/0x70
  [  790.702714]  ? arc_prune_task+0x1a/0x40 [zfs]
  [  790.702740]  ? dbuf_dirty+0x43d/0x850 [zfs]
  [  790.702745]  ? getrawmonotonic64+0x43/0xd0
  [  790.702746]  ? getrawmonotonic64+0x43/0xd0
  [  790.702775]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702778]  ? getrawmonotonic64+0x43/0xd0
  [  790.702805]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702807]  ? mutex_lock+0x12/0x40
  [  790.702833]  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
  [  790.702866]  range_tree_find_impl+0x88/0x90 [zfs]
  [  790.702870]  ? spl_kmem_zalloc+0xdc/0x1a0 [spl]
  [  790.702902]  range_tree_clear+0x4f/0x60 [zfs]
  [  790.702930]  dnode_free_range+0x11f/0x5a0 [zfs]
  [  790.702957]  dmu_object_free+0x53/0x90 [zfs]
  [  790.702983]  dmu_free_long_object+0x9f/0xc0 [zfs]
  [  790.703010]  receive_freeobjects.isra.12+0x7a/0x100 [zfs]
  [  790.703036]  receive_writer_thread+0x6d2/0xa60 [zfs]
  [  790.703040]  ? set_curr_task_fair+0x2b/0x60
  [  790.703043]  ? spl_kmem_free+0x33/0x40 [spl]
  [  790.703048]  ? kfree+0x165/0x180
  [  790.703073]  ? receive_free.isra.13+0xc0/0xc0 [zfs]
  [  790.703078]  thread_generic_wrapper+0x74/0x90 [spl]
  [  790.703081]  kthread+0x121/0x140
  [  790.703084]  ? __thread_exit+0x20/0x20 [spl]
  [  790.703085]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  790.703088]  ret_from_fork+0x35/0x40
  [  967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds.
  [  967.636979]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637076] txg_quiesce D0 14810  2 0x8000
  [  967.637080] Call Trace:
  [  967.637089]  __schedu

Re: [Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

2020-05-15 Thread Seth Arnold
On Sat, May 16, 2020 at 01:56:08AM -, Seth Arnold wrote:
> Sadly, journalctl doesn't have the dmesg from the previous boot:

I meant to say, journalctl's copy of dmesg from the previous boot doesn't
have the new debug output. Sorry.

Thanks

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

Title:
  zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

Status in Linux:
  New
Status in zfs-linux package in Ubuntu:
  Incomplete
Status in zfs-linux source package in Bionic:
  New

Bug description:
  Same as bug 1861228 but with a newer kernel installed.

  [  790.702566] VERIFY(size != 0) failed
  [  790.702590] PANIC at range_tree.c:304:range_tree_find_impl()
  [  790.702611] Showing stack for process 28685
  [  790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P   O 
4.15.0-76-generic #86-Ubuntu
  [  790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 
2.0 12/17/2015
  [  790.702616] Call Trace:
  [  790.702626]  dump_stack+0x6d/0x8e
  [  790.702637]  spl_dumpstack+0x42/0x50 [spl]
  [  790.702640]  spl_panic+0xc8/0x110 [spl]
  [  790.702645]  ? __switch_to_asm+0x41/0x70
  [  790.702714]  ? arc_prune_task+0x1a/0x40 [zfs]
  [  790.702740]  ? dbuf_dirty+0x43d/0x850 [zfs]
  [  790.702745]  ? getrawmonotonic64+0x43/0xd0
  [  790.702746]  ? getrawmonotonic64+0x43/0xd0
  [  790.702775]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702778]  ? getrawmonotonic64+0x43/0xd0
  [  790.702805]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702807]  ? mutex_lock+0x12/0x40
  [  790.702833]  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
  [  790.702866]  range_tree_find_impl+0x88/0x90 [zfs]
  [  790.702870]  ? spl_kmem_zalloc+0xdc/0x1a0 [spl]
  [  790.702902]  range_tree_clear+0x4f/0x60 [zfs]
  [  790.702930]  dnode_free_range+0x11f/0x5a0 [zfs]
  [  790.702957]  dmu_object_free+0x53/0x90 [zfs]
  [  790.702983]  dmu_free_long_object+0x9f/0xc0 [zfs]
  [  790.703010]  receive_freeobjects.isra.12+0x7a/0x100 [zfs]
  [  790.703036]  receive_writer_thread+0x6d2/0xa60 [zfs]
  [  790.703040]  ? set_curr_task_fair+0x2b/0x60
  [  790.703043]  ? spl_kmem_free+0x33/0x40 [spl]
  [  790.703048]  ? kfree+0x165/0x180
  [  790.703073]  ? receive_free.isra.13+0xc0/0xc0 [zfs]
  [  790.703078]  thread_generic_wrapper+0x74/0x90 [spl]
  [  790.703081]  kthread+0x121/0x140
  [  790.703084]  ? __thread_exit+0x20/0x20 [spl]
  [  790.703085]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  790.703088]  ret_from_fork+0x35/0x40
  [  967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds.
  [  967.636979]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637076] txg_quiesce D0 14810  2 0x8000
  [  967.637080] Call Trace:
  [  967.637089]  __schedule+0x24e/0x880
  [  967.637092]  schedule+0x2c/0x80
  [  967.637106]  cv_wait_common+0x11e/0x140 [spl]
  [  967.637114]  ? wait_woken+0x80/0x80
  [  967.637122]  __cv_wait+0x15/0x20 [spl]
  [  967.637210]  txg_quiesce_thread+0x2cb/0x3d0 [zfs]
  [  967.637278]  ? txg_delay+0x1b0/0x1b0 [zfs]
  [  967.637286]  thread_generic_wrapper+0x74/0x90 [spl]
  [  967.637291]  kthread+0x121/0x140
  [  967.637297]  ? __thread_exit+0x20/0x20 [spl]
  [  967.637299]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  967.637304]  ret_from_fork+0x35/0x40
  [  967.637326] INFO: task zfs:28590 blocked for more than 120 seconds.
  [  967.637371]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637467] zfs D0 28590  28587 0x8080
  [  967.637470] Call Trace:
  [  967.637474]  __schedule+0x24e/0x880
  [  967.637477]  schedule+0x2c/0x80
  [  967.637486]  cv_wait_common+0x11e/0x140 [spl]
  [  967.637491]  ? wait_woken+0x80/0x80
  [  967.637498]  __cv_wait+0x15/0x20 [spl]
  [  967.637554]  dmu_recv_stream+0xa51/0xef0 [zfs]
  [  967.637630]  zfs_ioc_recv_impl+0x306/0x1100 [zfs]
  [  967.637679]  ? dbuf_read+0x34a/0x920 [zfs]
  [  967.637725]  ? dbuf_rele+0x36/0x40 [zfs]
  [  967.637728]  ? _cond_resched+0x19/0x40
  [  967.637798]  zfs_ioc_recv_new+0x33d/0x410 [zfs]
  [  967.637809]  ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl]
  [  967.637816]  ? spl_vmem_alloc+0x19/0x20 [spl]
  [  967.637828]  ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair]
  [  967.637834]  ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair]
  [  967.637840]  ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair]
  [  967.637905]  zfsdev_ioctl+0x451/0x610 [zfs]
  [  967.637913]  do_vfs_ioctl+0xa8/0x630
  [  967.637917]  ? __audit_syscall_entry+0xbc/0x110
  [  967.637924]  ? syscall_trace_enter+0x1da/0x2d0
  [  967.637927]  SyS_ioctl+0x79/0x90
  [  967.637930]  do_syscall_64+0x73/0x130
  [  967.637935]  entry_SYSCALL_64_after_

[Kernel-packages] [Bug 1882850] Re: Touchpad not detected

2020-06-09 Thread Seth Arnold
** Information type changed from Private Security to Public

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

Title:
  Touchpad not detected

Status in linux package in Ubuntu:
  New

Bug description:
  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Ideapad extra buttons"
  P: Phys=ideapad/input0
  S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input8
  U: Uniq=
  H: Handlers=rfkill kbd event8 
  B: PROP=0
  B: EV=13
  B: KEY=81000800100c03 4430 0 2
  B: MSC=10

  I: Bus=0003 Vendor=04f2 Product=b6d9 Version=2699
  N: Name="Integrated Camera: Integrated C"
  P: Phys=usb-:00:14.0-6/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-6/3-6:1.0/input/input9
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input10
  U: Uniq=
  H: Handlers=kbd event10 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11
  U: Uniq=
  H: Handlers=event11 
  B: PROP=0
  B: EV=21
  B: SW=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12
  U: Uniq=
  H: Handlers=event12 
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13
  U: Uniq=
  H: Handlers=event13 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=7"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14
  U: Uniq=
  H: Handlers=event14 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=8"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input15
  U: Uniq=
  H: Handlers=event15 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=9"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input16
  U: Uniq=
  H: Handlers=event16 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=10"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input17
  U: Uniq=
  H: Handlers=event17 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=11"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input18
  U: Uniq=
  H: Handlers=event18 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=12"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input19
  U: Uniq=
  H: Handlers=event19 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus=0003 Vendor=3938 Product=1080 Version=0200
  N: Name="YK 2.4G Wireless Device Mouse"
  P: Phys=usb-:00:14.0-3/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/0003:3938:1080.0003/input/input20
  U: Uniq=
  H: Handlers=mouse0 event4 
  B: PROP=0
  B: EV=17
  B: KEY=1f 0 0 0 0
  B: REL=903
  B: MSC=10

  I: Bus=0003 Vendor=3938 Product=1080 Version=0200
  N: Name="YK 2.4G Wireless Device System Control"
  P: Phys=usb-:00:14.0-3/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/

[Kernel-packages] [Bug 1883086] Re: package linux-image-4.4.0-178-generic 4.4.0-178.208 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

2020-06-11 Thread Seth Arnold
** Information type changed from Private Security to Public

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

Title:
  package linux-image-4.4.0-178-generic 4.4.0-178.208 failed to
  install/upgrade: subprocess installed pre-removal script returned
  error exit status 1

Status in linux-signed package in Ubuntu:
  New

Bug description:
  Troubleshooting while switch on computer.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-178-generic 4.4.0-178.208
  ProcVersionSignature: Ubuntu 4.4.0-178.208-generic 4.4.217
  Uname: Linux 4.4.0-178-generic x86_64
  NonfreeKernelModules: btrfs xor raid6_pq hid_generic rtsx_usb_sdmmc usbhid 
rtsx_usb uas usb_storage i915_bpo intel_ips i2c_algo_bit psmouse drm_kms_helper 
syscopyarea r8169 sysfillrect sysimgblt fb_sys_fops mii ahci libahci drm wmi 
i2c_hid hid video pinctrl_sunrisepoint pinctrl_intel fjes
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: amd64
  Date: Thu Jun 11 13:01:18 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-12-17 (1272 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32ubuntu0.1
  SourcePackage: linux-signed
  Title: package linux-image-4.4.0-178-generic 4.4.0-178.208 failed to 
install/upgrade: subprocess installed pre-removal script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1310717] Re: process segfaults, hung task timeouts

2020-06-18 Thread Seth Arnold
I'm sorry, I can't recall that system very well at this point. "gmain"
is the generic name used by any application using glib's
g_get_worker_context() function to create worker threads. At this point
I can't even recall if I booted that system with X11 / lightdm or if I
had configured it to boot to multiuser only.

About the only thing I used that system for was tmux and irssi, neither
of which are using the thread name 'gmain' in Xenial, so they were
probably also not using the name in Saucy. So, it would have been
supplied by 'standard' system software, not something I chose to run
myself.

My pandaboard es killed SD cards pretty quickly, I came away with the
impression that SD cards are basically garbage not intended for 'real'
system use: segfaults and bus faults were the common symptom, and this
may have been a symptom of rubbish SD card too.

Thanks

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

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

Title:
  process segfaults, hung task timeouts

Status in linux-ti-omap4 package in Ubuntu:
  Incomplete

Bug description:
  My pandaboard ES runs irssi in a tmux session for me; irssi has died
  of segfaults twice recently, and dmesg had these warnings:

  [395523.456237] PLL GO bit not set
  [395523.456604] omapdss HDMI error: failed to power on device
  [395523.458251] [drm] Cannot find any crtc or sizes - going 1024x768
  [511971.446472] INFO: task gmain:28222 blocked for more than 120 seconds.
  [511971.446899] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [511971.447387] gmain   D c0592de8 0 28222   1414 0x0200
  [511971.447479] [] (__schedule+0x65c/0x7ec) from [] 
(schedule+0x94/0x98)
  [511971.447570] [] (schedule+0x94/0x98) from [] 
(exit_mm+0xc0/0x138)
  [511971.447601] [] (exit_mm+0xc0/0x138) from [] 
(do_exit+0x220/0x7e8)
  [511971.447662] [] (do_exit+0x220/0x7e8) from [] 
(do_group_exit+0x94/0xd0)
  [511971.447723] [] (do_group_exit+0x94/0xd0) from [] 
(get_signal_to_deliver+0x4f0/0x568)
  [511971.447784] [] (get_signal_to_deliver+0x4f0/0x568) from 
[] (do_signal+0x94/0x4ec)
  [511971.447814] [] (do_signal+0x94/0x4ec) from [] 
(do_notify_resume+0x28/0x64)
  [511971.447875] [] (do_notify_resume+0x28/0x64) from [] 
(work_pending+0x28/0x2c)
  [512091.451538] INFO: task gmain:28222 blocked for more than 120 seconds.
  [512091.451965] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [512091.452453] gmain   D c0592de8 0 28222   1414 0x0200
  [512091.452514] [] (__schedule+0x65c/0x7ec) from [] 
(schedule+0x94/0x98)
  [512091.452575] [] (schedule+0x94/0x98) from [] 
(exit_mm+0xc0/0x138)
  [512091.452606] [] (exit_mm+0xc0/0x138) from [] 
(do_exit+0x220/0x7e8)
  [512091.452667] [] (do_exit+0x220/0x7e8) from [] 
(do_group_exit+0x94/0xd0)
  [512091.452728] [] (do_group_exit+0x94/0xd0) from [] 
(get_signal_to_deliver+0x4f0/0x568)
  [512091.452789] [] (get_signal_to_deliver+0x4f0/0x568) from 
[] (do_signal+0x94/0x4ec)
  [512091.452819] [] (do_signal+0x94/0x4ec) from [] 
(do_notify_resume+0x28/0x64)
  [512091.452880] [] (do_notify_resume+0x28/0x64) from [] 
(work_pending+0x28/0x2c)
  [512211.444030] INFO: task gmain:28222 blocked for more than 120 seconds.
  [512211.444183] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.$
  [512211.444366] gmain   D c0592de8 0 28222   1414 0x0200
  [512211.27] [] (__schedule+0x65c/0x7ec) from [] 
(schedule+0x94/0x98)
  [512211.27] [] (schedule+0x94/0x98) from [] 
(exit_mm+0xc0/0x138)
  [512211.58] [] (exit_mm+0xc0/0x138) from [] 
(do_exit+0x220/0x7e8)
  [512211.58] [] (do_exit+0x220/0x7e8) from [] 
(do_group_exit+0x94/0xd0)
  [512211.88] [] (do_group_exit+0x94/0xd0) from [] 
(get_signal_to_deliver+0x4f0/0x568)
  [512211.444519] [] (get_signal_to_deliver+0x4f0/0x568) from 
[] (do_signal+0x94/0x4ec)
  [512211.444549] [] (do_signal+0x94/0x4ec) from [] 
(do_notify_resume+0x28/0x64)
  [512211.444549] [] (do_notify_resume+0x28/0x64) from [] 
(work_pending+0x28/0x2c)
  [512331.443237] INFO: task gmain:28222 blocked for more than 120 seconds.
  [512331.443389] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.$
  [512331.443511] gmain   D c0592de8 0 28222   1414 0x0200
  [512331.443542] [] (__schedule+0x65c/0x7ec) from [] 
(schedule+0x94/0x98)$
  [512331.443572] [] (schedule+0x94/0x98) from [] 
(exit_mm+0xc0/0x138)
  [512331.443572] [] (exit_mm+0xc0/0x138) from [] 
(do_exit+0x220/0x7e8)$
  [512331.443603] [] (do_exit+0x220/0x7e8) from [] 
(do_group_exit+0x94/0xd0)
  [512331.443634] [] (do_group_exit+0x94/0xd0) from [] 
(get_signal_to_deliver+0x4f0/0x568)$
  [512331.443634] [] (get_signal_to_deliver+0x4f0/0x568) from 
[] (do_signal+0x94/0x4ec)
  [512331.443664] [] (do_signal+0x94/0x4ec) from [] 
(do

[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

2020-03-25 Thread Seth Arnold
BTW, this is still happening in:

Linux millbarge 5.4.0-20-generic #24-Ubuntu SMP Mon Mar 23 20:55:46 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux

I've seen it both with firefox in trello, firefox in launchpad (typing
this comment) and doing two sequential wgets of
http://releases.ubuntu.com/18.04/ubuntu-18.04.4-desktop-amd64.iso (a 1.8
GB file).

Thanks

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

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/

[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

2020-03-25 Thread Seth Arnold
I'm adding the champagne tag to this bug to bring it to a potential
wider audience; I think we may need to take more drastic steps like
disabling swap on upgrades, not offering swap in our installers, etc.,
to try to have a better experience.

Thanks

** Tags added: champagne

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

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
   

[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

2020-03-30 Thread Seth Arnold
Sultan, thanks for the advice.

I set this watermark boost factor to zero as you suggested, and then
decided to try a stupid simple benchmark of my storage -- my swap is a
zfs dataset on nvme. zfs means it'll go slower than raw nvme block
access:

$ dd if=ubuntu-18.04.4-desktop-amd64.iso of=foo bs=$((1024*1024)) conv=fsync
2028+1 records in
2028+1 records out
2126544896 bytes (2.1 GB, 2.0 GiB) copied, 6.91399 s, 308 MB/s

And this is a sequential workload with large blocks rather than random
with pages, but it gives the flavour of the speed well enough.

Anyway, my system hung again when re-focusing firefox even after
changing the watermark boost factor to zero. It was unusable for ten or
twenty seconds. I have loads of free memory, it shouldn't be in swap:

$ free -h
  totalusedfree  shared  buff/cache   available
Mem:   15Gi11Gi   1.6Gi   643Mi   2.2Gi   2.8Gi
Swap: 2.0Gi23Mi   2.0Gi

Thanks

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

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  High watermark boosting can cause large swap activity under certain
  memory intensive workloads, making the system very unresponsive
  (screen does not refresh, keyboard not responding, etc.).

  This large swap activity seems to be prevented disabling high
  watermark boosting.

  [Test case]

  Opening this web page in chrome seems to be a good reproducer of the
  problem:

  
https://platform.leolabs.space/visualizations/conjunction?type=conjunction&reportId=2004981040

  When this page is opened we can clearly see from 'top' (for example)
  that the used swap is going up very quickly.

  With the fix applied swap is not used at all and the system is always
  responsive.

  [Fix]

  Set vm.watermark_boost_factor to 0, disabling watermark boosting by
  default.

  [Regression potential]

  Regression potential is minimal, setting vm.watermark_boost_factor to
  0 by default restores the old kernel behavior before watermark
  boosting was introduced. In case of unexpected regressions we can
  always fix this in user-space via sysctl.

  [Original report]

  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
     Mixer name : 'Realtek ALC285'
     Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
     Controls  : 53
     Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
     Mixer name : 'USB Mixer'
     Components : 'USB17ef:306f'
     Controls  : 9
     Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVer

[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

2020-04-02 Thread Seth Arnold
Sultan put together a kernel with some debugging for me:

[101616.889859] __alloc_pages_nodemask: stall of 3683ms for order-0, mask: 
0x100dca
[101616.889863] Call Trace:
[101616.889880]  __alloc_pages_nodemask+0x34f/0x3b0
[101616.889887]  alloc_pages_vma+0x7f/0x200
[101616.889893]  do_anonymous_page+0x118/0x650
[101616.889898]  __handle_mm_fault+0x760/0x7a0
[101616.889903]  handle_mm_fault+0xca/0x200
[101616.889911]  do_user_addr_fault+0x1f9/0x450
[101616.889917]  __do_page_fault+0x58/0x90
[101616.889925]  ? syscall_slow_exit_work+0x123/0x150
[101616.889930]  do_page_fault+0x2c/0xe0
[101616.889938]  page_fault+0x34/0x40
[101616.889943] RIP: 0033:0x7f0e38f80190
[101616.889949] Code: 78 04 41 bf 01 00 00 00 44 39 ef 0f 87 4f 01 00 00 41 83 
c5 01 48 ba 00 00 00 00 00 80 fa ff 44 89 ee 48 8d 0c f9 48 c1 e6 03 <48> 89 11 
48 83 c1 08 48 8b 7b 18 48 01 f7 48 39 f9 75 ed 44 89 68
[101616.889951] RSP: 002b:7ffd1b151780 EFLAGS: 00010202
[101616.889955] RAX: 7f0e27619000 RBX: 06b3e615a810 RCX: 
7f0e27634000
[101616.889958] RDX: fffa8000 RSI: 0001aff8 RDI: 
35fe
[101616.889960] RBP: 6bfd R08: 7ffd1b151820 R09: 
292d95be
[101616.889962] R10: 0011 R11: 7f0e2632d000 R12: 
7f0e3082e000
[101616.889964] R13: 35ff R14: 0001 R15: 
0001

The trigger in this case was firefox loading
https://code.launchpad.net/~ahasenack/qa-regression-testing/+git/qa-
regression-testing/+merge/381582

Recent calls to journalctl > /tmp/foo had lead to a minute-long hang
(though the mouse did make ~10ms motion every six or seven seconds),
swap growth from 1MB to 62M, but no stacktraces.

Thanks

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

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  High watermark boosting can cause large swap activity under certain
  memory intensive workloads, making the system very unresponsive
  (screen does not refresh, keyboard not responding, etc.).

  This large swap activity seems to be prevented disabling high
  watermark boosting.

  [Test case]

  Opening this web page in chrome seems to be a good reproducer of the
  problem:

  
https://platform.leolabs.space/visualizations/conjunction?type=conjunction&reportId=2004981040

  When this page is opened we can clearly see from 'top' (for example)
  that the used swap is going up very quickly.

  With the fix applied swap is not used at all and the system is always
  responsive.

  [Fix]

  Set vm.watermark_boost_factor to 0, disabling watermark boosting by
  default.

  [Regression potential]

  Regression potential is minimal, setting vm.watermark_boost_factor to
  0 by default restores the old kernel behavior before watermark
  boosting was introduced. In case of unexpected regressions we can
  always fix this in user-space via sysctl.

  [Original report]

  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
     Mixer name : 'Realtek ALC285'
     Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
     Controls  : 53
     Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
     Mixer name : 'USB Mixer'
     Components : 'USB17ef:306f'
     Controls  

[Kernel-packages] [Bug 1862708] Re: tracing doesn't work on focal

2020-04-02 Thread Seth Arnold
I'm sorry for the slow response Francis, I've been running custom kernels for:
https://bugs.launchpad.net/bugs/1861359
for a while. Thanks for the reminder.

sarnold@millbarge:~$ dmesg | grep -i lockdown
[0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
[1.009940] Lockdown: swapper/0: hibernation is restricted; see man 
kernel_lockdown.7
[   22.929952] Lockdown: systemd: /dev/mem,kmem,port is restricted; see man 
kernel_lockdown.7
[   26.152235] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
[   30.333255] Lockdown: rasdaemon: debugfs access is restricted; see man 
kernel_lockdown.7
sarnold@millbarge:~$ sudo -s
[sudo] password for sarnold: 
root@millbarge:/home/sarnold# kprobe-perf -s 'p:shrink_node'
Tracing kprobe shrink_node. Ctrl-C to end.
^C
Ending tracing...
root@millbarge:/home/sarnold# ls -l 
/sys/kernel/debug/tracing/available_filter_functions
-r--r--r-- 1 root root 0 Apr  3 02:18 
/sys/kernel/debug/tracing/available_filter_functions
root@millbarge:/home/sarnold# uname -a
Linux millbarge 5.4.0-21-generic #25-Ubuntu SMP Sat Mar 28 13:10:28 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
root@millbarge:/home/sarnold# dpkg -l 'linux*' | grep ^ii
ii  linux-base4.5ubuntu3   all  Linux image 
base package
ii  linux-firmware1.187all  Firmware 
for Linux kernel drivers
ii  linux-generic 5.4.0.21.25  amd64Complete 
Generic Linux kernel and headers
ii  linux-headers-5.4.0-185.4.0-18.22  all  Header 
files related to Linux kernel version 5.4.0
ii  linux-headers-5.4.0-18-generic5.4.0-18.22  amd64Linux 
kernel headers for version 5.4.0 on 64 bit x86 SMP
ii  linux-headers-5.4.0-205.4.0-20.24  all  Header 
files related to Linux kernel version 5.4.0
ii  linux-headers-5.4.0-20-generic5.4.0-20.24  amd64Linux 
kernel headers for version 5.4.0 on 64 bit x86 SMP
ii  linux-headers-5.4.0-215.4.0-21.25  all  Header 
files related to Linux kernel version 5.4.0
ii  linux-headers-5.4.0-21-generic5.4.0-21.25  amd64Linux 
kernel headers for version 5.4.0 on 64 bit x86 SMP
ii  linux-headers-generic 5.4.0.21.25  amd64Generic 
Linux kernel headers
ii  linux-image-5.4.0-20-generic  5.4.0-20.24  amd64Signed 
kernel image generic
ii  linux-image-5.4.0-21-generic  5.4.0-21.25  amd64Signed 
kernel image generic
ii  linux-image-generic   5.4.0.21.25  amd64Generic 
Linux kernel image
ii  linux-image-unsigned-5.4.0-18-generic 5.4.0-18.22  amd64Linux 
kernel image for version 5.4.0 on 64 bit x86 SMP
ii  linux-libc-dev:amd64  5.4.0-21.25  amd64Linux 
Kernel Headers for development
ii  linux-modules-5.4.0-18-generic5.4.0-18.22  amd64Linux 
kernel extra modules for version 5.4.0 on 64 bit x86 SMP
ii  linux-modules-5.4.0-20-generic5.4.0-20.24  amd64Linux 
kernel extra modules for version 5.4.0 on 64 bit x86 SMP
ii  linux-modules-5.4.0-21-generic5.4.0-21.25  amd64Linux 
kernel extra modules for version 5.4.0 on 64 bit x86 SMP
ii  linux-modules-extra-5.4.0-18-generic  5.4.0-18.22  amd64Linux 
kernel extra modules for version 5.4.0 on 64 bit x86 SMP
ii  linux-modules-extra-5.4.0-20-generic  5.4.0-20.24  amd64Linux 
kernel extra modules for version 5.4.0 on 64 bit x86 SMP
ii  linux-modules-extra-5.4.0-21-generic  5.4.0-21.25  amd64Linux 
kernel extra modules for version 5.4.0 on 64 bit x86 SMP
ii  linux-tools-5.4.0-18  5.4.0-18.22  amd64Linux 
kernel version specific tools for version 5.4.0-18
ii  linux-tools-5.4.0-18-generic  5.4.0-18.22  amd64Linux 
kernel version specific tools for version 5.4.0-18
ii  linux-tools-5.4.0-20  5.4.0-20.24  amd64Linux 
kernel version specific tools for version 5.4.0-20
ii  linux-tools-5.4.0-20-generic  5.4.0-20.24  amd64Linux 
kernel version specific tools for version 5.4.0-20
ii  linux-tools-5.4.0-21  5.4.0-21.25  amd64Linux 
kernel version specific tools for version 5.4.0-21
ii  linux-tools-5.4.0-21-generic  5.4.0-21.25  amd64Linux 
kernel version specific tools for version 5.4.0-21
ii  linux-tools-common5.4.0-21.25  all  Linux 
kernel version specific tools for version 5.4.0
ii  linux-tools-generic   5.4.0.21.25  amd64Generic 
Linux kernel tools
root@millbarge:/home/sarnold# man kernel_lockdown
No manual entry for kernel_lockdown
root@millbarge:/home/sarnold# 


Other tools also work now:

root@millbarge:/home/sarnold# tcpconnect-bpfcc 
Tracing connect ... Hit Ctrl-C to end
PIDCOMM IP SADDRDADDRDPORT
6781   ssh  4  192.168.0.34

[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

2020-04-03 Thread Seth Arnold
Stefan, while recent kernels seem happier than previous kernels (I think
-14 era was terrible), I don't think this problem is fixed yet:

sarnold@millbarge:/tmp$ uname -a
Linux millbarge 5.4.0-21-generic #25-Ubuntu SMP Sat Mar 28 13:10:28 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
sarnold@millbarge:/tmp$ uptime
 17:18:02 up 14:59,  8 users,  load average: 0.36, 0.27, 0.16
sarnold@millbarge:/tmp$ time journalctl > foo

real0m47.135s
user0m36.886s
sys 0m10.180s
sarnold@millbarge:/tmp$ ls -lh /tmp/foo
-rw-rw-r-- 1 sarnold sarnold 841M Apr  3 17:15 /tmp/foo
sarnold@millbarge:/tmp$ wc -l /tmp/foo
4045530 /tmp/foo


During that journalctl run, my mouse could not move for twenty seconds. I left 
an iovisor tool running to log high-latency __alloc_pages_nodemask() calls 
(identified by Sultan as a likely cause):

# funcslower-bpfcc __alloc_pages_nodemask
Tracing function calls slower than 1 ms... Ctrl+C to quit.
COMM   PIDLAT(ms) RVAL FUNC
dp_sync_taskq  716   7.72 f2d109115040 __alloc_pages_nodemask 
systemd-udevd  44671 1.59 f2d10575b800 __alloc_pages_nodemask 
git46218 4.27 f2d10500edc0 __alloc_pages_nodemask 
z_wr_iss   683   4.90 f2d101b4cf40 __alloc_pages_nodemask 
systemd-udevd  51359 4.27 f2d10ec12800 __alloc_pages_nodemask 
systemd-udevd  56585 2.48 f2d10d3b0500 __alloc_pages_nodemask 
systemd-udevd  56577 2.55 f2d106f73380 __alloc_pages_nodemask 
systemd-udevd  72552 2.09 f2d105249680 __alloc_pages_nodemask 
systemd-udevd  76964 1.53 f2d1017fd440 __alloc_pages_nodemask 
systemd-udevd  80900 3.94 f2d102675200 __alloc_pages_nodemask 
systemd-udevd  88669 2.09 f2d1015fb5c0 __alloc_pages_nodemask 
kthreadd   2 4.41 f2d10d6f96c0 __alloc_pages_nodemask 
kthreadd   2 4.65 f2d10d38c3c0 __alloc_pages_nodemask 
kthreadd   2 3.97 f2d10d3cc780 __alloc_pages_nodemask 
updatedb.mloca 1061942.44 f2d10e1c2680 __alloc_pages_nodemask 
kthreadd   2 1.20 f2d10d36ff40 __alloc_pages_nodemask 
kthreadd   2 4.13 f2d10d495940 __alloc_pages_nodemask 
kthreadd   2 6.34 f2d10d317180 __alloc_pages_nodemask 
kthreadd   2 4.76 f2d110e85000 __alloc_pages_nodemask 
systemd-udevd  1138221.51 f2d10f5c8e00 __alloc_pages_nodemask 
systemd-udevd  1138201.91 f2d10e611800 __alloc_pages_nodemask 
systemd-udevd  1220173.13 f2d10e539700 __alloc_pages_nodemask 
systemd-udevd  1411022.43 f2d104487200 __alloc_pages_nodemask 
systemd-udevd  1445654.82 f2d106b84040 __alloc_pages_nodemask 
systemd-udevd  1156  1.28 f2d102325c00 __alloc_pages_nodemask 
systemd-udevd  1524863.07 f2d101516500 __alloc_pages_nodemask 
systemd-udevd  1524854.94 f2d1015cbbc0 __alloc_pages_nodemask 
systemd-udevd  1728071.33 f2d1015f4700 __alloc_pages_nodemask 
systemd-udevd  1855034.46 f2d10d321240 __alloc_pages_nodemask 
systemd-udevd  1892445.12 f2d10e7f0b00 __alloc_pages_nodemask 
systemd-udevd  2059735.36 f2d10d4171c0 __alloc_pages_nodemask 
systemd-udevd  2101335.19 f2d10ffac340 __alloc_pages_nodemask 
systemd-udevd  2096212.95 f2d10d377fc0 __alloc_pages_nodemask 
systemd-udevd  2187682.24 f2d10526e500 __alloc_pages_nodemask 
systemd-udevd  2342611.42 f2d101814680 __alloc_pages_nodemask 
systemd-udevd  2354683.82 f2d10d2afa40 __alloc_pages_nodemask 
systemd-udevd  2368264.94 f2d10d0f8440 __alloc_pages_nodemask 
systemd-udevd  2471151.13 f2d1023ee180 __alloc_pages_nodemask 
systemd-udevd  2475731.46 f2d1015a4040 __alloc_pages_nodemask 
systemd-udevd  2712885.38 f2d10d1b3800 __alloc_pages_nodemask 
dav1d-tile 2834602.05 f2d10cdb0b80 __alloc_pages_nodemask 
dav1d-tile 2834602.80 f2d10cdb8840 __alloc_pages_nodemask 
dav1d-tile 2834602.83 f2d10cdb9200 __alloc_pages_nodemask 
RemVidParent   2834602.82 f2d10cdba200 __alloc_pages_nodemask 
dav1d-tile 2834604.11 f2d10cdbcf00 __alloc_pages_nodemask 
journalctl 2862701.71 f2d10e2668c0 __alloc_pages_nodemask 
journalctl 2862701.09 f2d10ccfac00 __alloc_pages_nodemask 
journalctl 2862701.11 f2d10cce3200 __alloc_pages_nodemask 
journalctl 2862702.96 f2d10cce7380 __alloc_pages_nodemask 
x-terminal-emu 24851 1.14 f2d1086a2a00 __alloc_pages_nodemask 
journalctl 2862701.44 f2d10ccc41c0 __alloc_pages_nodemask 
kthreadd   2 1.25 f2d110c71000 __alloc_pages_nodemask 
journalctl 2862701.05 f2d10ccb1200 __alloc_pages_nodemask 
journalctl 2862701.65 f2d10ccbd700 __alloc_pages_nodemask 
journalctl 2862703.08 f2d102229000 __alloc_pages_nodemask 
journalctl 2862701.88 f2d10cbfd0c0 __alloc_pages_nodemask 
journalctl 2862701.54 f2d109088

[Kernel-packages] [Bug 1862708] Re: tracing doesn't work on focal

2020-04-03 Thread Seth Arnold
Just to be clear, not *all* tracing tools work, but this is much better:

sarnold@millbarge:/tmp$ uname -a
Linux millbarge 5.4.0-21-generic #25-Ubuntu SMP Sat Mar 28 13:10:28 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
sarnold@millbarge:/tmp$ sudo zfsslower-bpfcc 
Traceback (most recent call last):
  File "/usr/sbin/zfsslower-bpfcc", line 265, in 
if BPF.get_kprobe_functions(b'zpl_iter'):
  File "/usr/lib/python3/dist-packages/bcc/__init__.py", line 539, in 
get_kprobe_functions
with open("%s/../kprobes/blacklist" % TRACEFS, "rb") as blacklist_f:
PermissionError: [Errno 1] Operation not permitted: 
'/sys/kernel/debug/tracing/../kprobes/blacklist'

Thanks

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

Title:
  tracing doesn't work on focal

Status in linux package in Ubuntu:
  Fix Released
Status in perf-tools-unstable package in Ubuntu:
  New

Bug description:
  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:

  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options

  
  I'm guessing this is due to lockdown:

  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of trace

[Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

2020-04-22 Thread Seth Arnold
Hello Colin, yes, this is still an open issue:

Linux wopr 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:09:48 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux


Apr 22 19:10:03 wopr zed[12576]: eid=8352 class=history_event 
pool_guid=0xB3B099B638F02EEF
Apr 22 19:10:03 wopr kernel: VERIFY(size != 0) failed
Apr 22 19:10:03 wopr kernel: PANIC at range_tree.c:304:range_tree_find_impl()
Apr 22 19:10:03 wopr kernel: Showing stack for process 12577
Apr 22 19:10:03 wopr kernel: CPU: 8 PID: 12577 Comm: receive_writer Tainted: P  
 O 4.15.0-91-generic #92-Ubuntu
Apr 22 19:10:03 wopr kernel: Hardware name: Supermicro 
SSG-6038R-E1CR16L/X10DRH-iT, BIOS 2.0 12/17/2015
Apr 22 19:10:03 wopr kernel: Call Trace:
Apr 22 19:10:03 wopr kernel:  dump_stack+0x6d/0x8e
Apr 22 19:10:03 wopr kernel:  spl_dumpstack+0x42/0x50 [spl]
Apr 22 19:10:03 wopr kernel:  spl_panic+0xc8/0x110 [spl]
Apr 22 19:10:03 wopr kernel:  ? __switch_to_asm+0x41/0x70
Apr 22 19:10:03 wopr kernel:  ? abd_iter_map+0xa/0x90 [zfs]
Apr 22 19:10:03 wopr kernel:  ? dbuf_dirty+0x43d/0x850 [zfs]
Apr 22 19:10:03 wopr kernel:  ? getrawmonotonic64+0x43/0xd0
Apr 22 19:10:03 wopr kernel:  ? getrawmonotonic64+0x43/0xd0
Apr 22 19:10:03 wopr kernel:  ? dmu_zfetch+0x49a/0x500 [zfs]
Apr 22 19:10:03 wopr kernel:  ? getrawmonotonic64+0x43/0xd0
Apr 22 19:10:03 wopr kernel:  ? dmu_zfetch+0x49a/0x500 [zfs]
Apr 22 19:10:03 wopr kernel:  ? mutex_lock+0x12/0x40
Apr 22 19:10:03 wopr kernel:  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
Apr 22 19:10:03 wopr kernel:  range_tree_find_impl+0x88/0x90 [zfs]
Apr 22 19:10:03 wopr kernel:  ? spl_kmem_zalloc+0xdc/0x1a0 [spl]
Apr 22 19:10:03 wopr kernel:  range_tree_clear+0x4f/0x60 [zfs]
Apr 22 19:10:03 wopr kernel:  dnode_free_range+0x11f/0x5a0 [zfs]
Apr 22 19:10:03 wopr kernel:  dmu_object_free+0x53/0x90 [zfs]
Apr 22 19:10:03 wopr kernel:  dmu_free_long_object+0x9f/0xc0 [zfs]
Apr 22 19:10:03 wopr kernel:  receive_freeobjects.isra.12+0x7a/0x100 [zfs]
Apr 22 19:10:03 wopr kernel:  receive_writer_thread+0x6d2/0xa60 [zfs]
Apr 22 19:10:03 wopr kernel:  ? set_curr_task_fair+0x2b/0x60
Apr 22 19:10:03 wopr kernel:  ? spl_kmem_free+0x33/0x40 [spl]
Apr 22 19:10:03 wopr kernel:  ? kfree+0x165/0x180
Apr 22 19:10:03 wopr kernel:  ? receive_free.isra.13+0xc0/0xc0 [zfs]
Apr 22 19:10:03 wopr kernel:  thread_generic_wrapper+0x74/0x90 [spl]
Apr 22 19:10:03 wopr kernel:  kthread+0x121/0x140
Apr 22 19:10:03 wopr kernel:  ? __thread_exit+0x20/0x20 [spl]
Apr 22 19:10:03 wopr kernel:  ? kthread_create_worker_on_cpu+0x70/0x70
Apr 22 19:10:03 wopr kernel:  ret_from_fork+0x35/0x40
Apr 22 19:12:56 wopr kernel: INFO: task txg_quiesce:2265 blocked for more than 
120 seconds.
Apr 22 19:12:56 wopr kernel:   Tainted: P   O 4.15.0-91-generic 
#92-Ubuntu
Apr 22 19:12:56 wopr kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
Apr 22 19:12:56 wopr kernel: txg_quiesce D0  2265  2 0x8000
Apr 22 19:12:56 wopr kernel: Call Trace:
Apr 22 19:12:56 wopr kernel:  __schedule+0x24e/0x880
Apr 22 19:12:56 wopr kernel:  schedule+0x2c/0x80
Apr 22 19:12:56 wopr kernel:  cv_wait_common+0x11e/0x140 [spl]
Apr 22 19:12:56 wopr kernel:  ? wait_woken+0x80/0x80
Apr 22 19:12:56 wopr kernel:  __cv_wait+0x15/0x20 [spl]
Apr 22 19:12:56 wopr kernel:  txg_quiesce_thread+0x2cb/0x3d0 [zfs]
Apr 22 19:12:56 wopr kernel:  ? txg_delay+0x1b0/0x1b0 [zfs]
Apr 22 19:12:56 wopr kernel:  thread_generic_wrapper+0x74/0x90 [spl]
Apr 22 19:12:56 wopr kernel:  kthread+0x121/0x140
Apr 22 19:12:56 wopr kernel:  ? __thread_exit+0x20/0x20 [spl]
Apr 22 19:12:56 wopr kernel:  ? kthread_create_worker_on_cpu+0x70/0x70
Apr 22 19:12:56 wopr kernel:  ret_from_fork+0x35/0x40
Apr 22 19:12:56 wopr kernel: INFO: task zfs:12482 blocked for more than 120 
seconds.
Apr 22 19:12:56 wopr kernel:   Tainted: P   O 4.15.0-91-generic 
#92-Ubuntu
Apr 22 19:12:56 wopr kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
Apr 22 19:12:56 wopr kernel: zfs D0 12482  12479 0x8080
Apr 22 19:12:56 wopr kernel: Call Trace:
Apr 22 19:12:56 wopr kernel:  __schedule+0x24e/0x880
Apr 22 19:12:56 wopr kernel:  schedule+0x2c/0x80
Apr 22 19:12:56 wopr kernel:  cv_wait_common+0x11e/0x140 [spl]
Apr 22 19:12:56 wopr kernel:  ? wait_woken+0x80/0x80
Apr 22 19:12:56 wopr kernel:  __cv_wait+0x15/0x20 [spl]
Apr 22 19:12:56 wopr kernel:  dmu_recv_stream+0xa51/0xef0 [zfs]
Apr 22 19:12:56 wopr kernel:  zfs_ioc_recv_impl+0x306/0x1100 [zfs]
Apr 22 19:12:56 wopr kernel:  ? dbuf_rele+0x36/0x40 [zfs]
Apr 22 19:12:56 wopr kernel:  zfs_ioc_recv_new+0x33d/0x410 [zfs]
Apr 22 19:12:56 wopr kernel:  ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl]
Apr 22 19:12:56 wopr kernel:  ? spl_vmem_alloc+0x19/0x20 [spl]
Apr 22 19:12:56 wopr kernel:  ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair]
Apr 22 19:12:56 wopr kernel:  ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair]
Apr 22 19:12:56 wopr kernel:  ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair]
Apr 22 19:12:56 wopr kernel:  zfsdev_ioctl+0x

[Kernel-packages] [Bug 1875513] Re: wifi is not showing in select networks

2020-04-27 Thread Seth Arnold
** Information type changed from Private Security to Public

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

Title:
  wifi is not showing in select networks

Status in linux package in Ubuntu:
  New

Bug description:
  i am trying to connect my mobile hotspot but it is not showing in
  select network section although my hotspot is on.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  saud   1309 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 05:41:03 2020
  InstallationDate: Installed on 2020-04-27 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: TOSHIBA Satellite C55-B
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=087e4472-46b8-4204-9cc0-e37643c7ffbf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.10:bd05/06/2014:svnTOSHIBA:pnSatelliteC55-B:pvrPSKSSV-00700JAR:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: Satellite C55-B
  dmi.product.sku: Type1Sku0
  dmi.product.version: PSKSSV-00700JAR
  dmi.sys.vendor: TOSHIBA

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

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


[Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

2020-05-28 Thread Seth Arnold
I picked the last dataset given in the command output from an earlier,
but not the most recent, comment:

$ sudo zdb - srv/backups/millbarge/rpool/var/log 529
Dataset srv/backups/millbarge/rpool/var/log [ZPL], ID 39694, cr_txg 23197757, 
554M, 274 objects, rootbp DVA[0]=<1:1d000d42000:1000> 
DVA[1]=<2:24416f4b000:1000> [L0 DMU objset] sha256 uncompressed LE contiguous 
unique double size=800L/800P birth=23437543L/23437543P fill=274 
cksum=cf5fcb2f986c768c:7cc8638aeb1a5162:9de9f236f072e16:40c6a08d90b54951

Object  lvl   iblk   dblk  dsize  dnsize  lsize   %full  type
   5290  0  0  0 512  0-nan  DSL permissions 
(K=UNKNOWN) (Z=UNKNOWN)
 0   bonus  UNKNOWN
dnode flags: USED_BYTES USERUSED_ACCOUNTED USEROBJUSED_ACCOUNTED 
SPILL_BLKPTR
dnode maxblkid: 0
UNKNOWN OBJECT TYPE
c < (1ULL << 24) >> 9 (0x7f < 0x8000)
ASSERT at ../../module/zfs/zio.c:266:zio_buf_alloc()Aborted


Thanks

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

Title:
  zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

Status in Linux:
  New
Status in zfs-linux package in Ubuntu:
  Incomplete
Status in zfs-linux source package in Bionic:
  New

Bug description:
  Same as bug 1861228 but with a newer kernel installed.

  [  790.702566] VERIFY(size != 0) failed
  [  790.702590] PANIC at range_tree.c:304:range_tree_find_impl()
  [  790.702611] Showing stack for process 28685
  [  790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P   O 
4.15.0-76-generic #86-Ubuntu
  [  790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 
2.0 12/17/2015
  [  790.702616] Call Trace:
  [  790.702626]  dump_stack+0x6d/0x8e
  [  790.702637]  spl_dumpstack+0x42/0x50 [spl]
  [  790.702640]  spl_panic+0xc8/0x110 [spl]
  [  790.702645]  ? __switch_to_asm+0x41/0x70
  [  790.702714]  ? arc_prune_task+0x1a/0x40 [zfs]
  [  790.702740]  ? dbuf_dirty+0x43d/0x850 [zfs]
  [  790.702745]  ? getrawmonotonic64+0x43/0xd0
  [  790.702746]  ? getrawmonotonic64+0x43/0xd0
  [  790.702775]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702778]  ? getrawmonotonic64+0x43/0xd0
  [  790.702805]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702807]  ? mutex_lock+0x12/0x40
  [  790.702833]  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
  [  790.702866]  range_tree_find_impl+0x88/0x90 [zfs]
  [  790.702870]  ? spl_kmem_zalloc+0xdc/0x1a0 [spl]
  [  790.702902]  range_tree_clear+0x4f/0x60 [zfs]
  [  790.702930]  dnode_free_range+0x11f/0x5a0 [zfs]
  [  790.702957]  dmu_object_free+0x53/0x90 [zfs]
  [  790.702983]  dmu_free_long_object+0x9f/0xc0 [zfs]
  [  790.703010]  receive_freeobjects.isra.12+0x7a/0x100 [zfs]
  [  790.703036]  receive_writer_thread+0x6d2/0xa60 [zfs]
  [  790.703040]  ? set_curr_task_fair+0x2b/0x60
  [  790.703043]  ? spl_kmem_free+0x33/0x40 [spl]
  [  790.703048]  ? kfree+0x165/0x180
  [  790.703073]  ? receive_free.isra.13+0xc0/0xc0 [zfs]
  [  790.703078]  thread_generic_wrapper+0x74/0x90 [spl]
  [  790.703081]  kthread+0x121/0x140
  [  790.703084]  ? __thread_exit+0x20/0x20 [spl]
  [  790.703085]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  790.703088]  ret_from_fork+0x35/0x40
  [  967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds.
  [  967.636979]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637076] txg_quiesce D0 14810  2 0x8000
  [  967.637080] Call Trace:
  [  967.637089]  __schedule+0x24e/0x880
  [  967.637092]  schedule+0x2c/0x80
  [  967.637106]  cv_wait_common+0x11e/0x140 [spl]
  [  967.637114]  ? wait_woken+0x80/0x80
  [  967.637122]  __cv_wait+0x15/0x20 [spl]
  [  967.637210]  txg_quiesce_thread+0x2cb/0x3d0 [zfs]
  [  967.637278]  ? txg_delay+0x1b0/0x1b0 [zfs]
  [  967.637286]  thread_generic_wrapper+0x74/0x90 [spl]
  [  967.637291]  kthread+0x121/0x140
  [  967.637297]  ? __thread_exit+0x20/0x20 [spl]
  [  967.637299]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  967.637304]  ret_from_fork+0x35/0x40
  [  967.637326] INFO: task zfs:28590 blocked for more than 120 seconds.
  [  967.637371]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637467] zfs D0 28590  28587 0x8080
  [  967.637470] Call Trace:
  [  967.637474]  __schedule+0x24e/0x880
  [  967.637477]  schedule+0x2c/0x80
  [  967.637486]  cv_wait_common+0x11e/0x140 [spl]
  [  967.637491]  ? wait_woken+0x80/0x80
  [  967.637498]  __cv_wait+0x15/0x20 [spl]
  [  967.637554]  dmu_recv_stream+0xa51/0xef0 [zfs]
  [  967.637630]  zfs_ioc_recv_impl+0x306/0x1100 [zfs]
  [  967.637679]  ? dbuf_read+0x34a/0x920 [zfs]
  [  967.637725]  ? dbuf_rele+0x36/0x40 [z

[Kernel-packages] [Bug 1779736] Re: umask ignored on NFSv4.2 mounts

2020-05-28 Thread Seth Arnold
The default NFSv4 acls may be a poor choice on ZOL. This keeps biting
people unexpectedly, I wonder how many people this has affected and they
never spot it?

Thanks

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

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

Title:
  umask ignored on NFSv4.2 mounts

Status in linux package in Ubuntu:
  Confirmed
Status in nfs-utils package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  New

Bug description:
  After upgrading to kernel 4.15.0-24-generic (on Ubuntu 18.04 LTS)
  NFSv4.2 mounts ignore the umask when creating files and directories.
  Files get permissions 666 and directories get 777.  Therefore, a umask
  of 000 is seemingly being forced when creating files/directories in
  NFS mounts.  Mounting with noacl does not resolve the issue.

  How to replicate:

  1. Mount an NFS share (defaults to NFSv4.2)
  2. Ensure restrictive umask: umask 022
  3. Create directory: mkdir test_dir
  4. Create file: touch test_file
  5. List: ls -l

  The result will be:
  drwxrwxrwx 2 user user 2 Jul  2 12:16 test_dir
  -rw-rw-rw- 1 user user 0 Jul  2 12:16 test_file

  while the expected result would be
  drwxr-xr-x 2 user user 2 Jul  2 12:16 test_dir
  -rw-r--r-- 1 user user 0 Jul  2 12:16 test_file

  Bug does not occur when mounting with any of:
    vers=3
    vers=4.0
    vers=4.1

  I have a suspicion this is related to: 
https://tools.ietf.org/id/draft-ietf-nfsv4-umask-03.html
  But since the server does not have ACL's enabled, and mounting with noacl 
does not resolve the issue this is unexpected behavior.

  Both server and client are running kernel 4.15.0-24-generic on Ubuntu
  18.04 LTS.  NFS package versions are:

  nfs-kernel-server 1:1.3.4-2.1ubuntu5
  nfs-common 1:1.3.4-2.1ubuntu5

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

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


[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

2020-02-18 Thread Seth Arnold
$ uname -a
Linux millbarge 5.4.0-12-generic #15-Ubuntu SMP Tue Jan 21 15:12:29 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
$ cat /proc/sys/kernel/ftrace_enabled
1
$ sudo kprobe-perf -s 'p:shrink_node'
[sudo] password for sarnold: 
ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
$ sudo kprobe-perf -F -s 'p:shrink_node'
Tracing kprobe shrink_node. Ctrl-C to end.
/usr/sbin/kprobe-perf: line 227: current_tracer: Permission denied
/usr/sbin/kprobe-perf: line 228: kprobe_events: Permission denied
ERROR: adding kprobe "p:shrink_node shrink_node".
Last 2 dmesg entries (might contain reason):
[1039094.850875] usb 1-4.4.1.3: Manufacturer: u-blox AG - www.u-blox.com
[1039094.860068] cdc_acm 1-4.4.1.3:1.0: ttyACM1: USB ACM device
Exiting.


Does the /proc/sys/kernel/ftrace_enabled output need a new bug report?

Thanks

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

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
 

[Kernel-packages] [Bug 1864272] [NEW] How to disable lockdown?

2020-02-21 Thread Seth Arnold
Public bug reported:

Hello, I tried to disable lockdown so I could debug bug 1861359.

I changed my security= kernel command line parameter to no longer
reference lockdown or integrity and yet the lockdown still applied:

sarnold@millbarge:~/Canonical/work-reports$ uname -a
Linux millbarge 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
sarnold@millbarge:~/Canonical/work-reports$ cat /proc/cmdline 
BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-14-generic root=ZFS=rpool/ROOT/ubuntu ro 
root=ZFS=rpool/ROOT/ubuntu quiet splash acpi_osi=! "acpi_osi=Windows 2015" 
security=yama,apparmor vt.handoff=1
sarnold@millbarge:~/Canonical/work-reports$ dmesg | grep -i lockdown
[0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
[0.175625] Lockdown: swapper: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.175626] Tracing disabled due to lockdown
[0.226042] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.226042] Can not register tracer wakeup due to lockdown
[0.226042] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.226042] Can not register tracer function_graph due to lockdown
[0.536927] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.536928] Tracing disabled due to lockdown
[0.536929] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.536929] Tracing disabled due to lockdown
[0.536930] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.536930] Tracing disabled due to lockdown
[0.536931] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.536932] Tracing disabled due to lockdown
[0.536934] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.536934] Tracing disabled due to lockdown
[0.536935] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.536936] Tracing disabled due to lockdown
[0.536937] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.536937] Tracing disabled due to lockdown
[0.826846] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.826847] Tracing disabled due to lockdown
[0.826849] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.826849] Can not register tracer mmiotrace due to lockdown
[0.826851] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.826851] Can not register tracer blk due to lockdown
[0.955352] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
[0.955353] Can not register tracer hwlat due to lockdown
[1.005959] Lockdown: swapper/0: hibernation is restricted; see man 
kernel_lockdown.7
[   18.886284] Lockdown: systemd: /dev/mem,kmem,port is restricted; see man 
kernel_lockdown.7
[   21.314470] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
[   48.022857] Lockdown: opensnoop-bpfcc: unsafe use of perf is restricted; see 
man kernel_lockdown.7
[   48.022862] Lockdown: opensnoop-bpfcc: use of kprobes is restricted; see man 
kernel_lockdown.7


Thanks

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-14-generic 5.4.0-14.17
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
Date: Sat Feb 22 05:06:38 2020
ProcEnviron:
 TERM=rxvt-unicode-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-5.4
UpgradeStatus: Upgraded to focal on 2020-01-24 (28 days ago)

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


** Tags: amd64 apport-bug focal

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

Title:
  How to disable lockdown?

Status in linux-signed-5.4 package in Ubuntu:
  New

Bug description:
  Hello, I tried to disable lockdown so I could debug bug 1861359.

  I changed my security= kernel command line parameter to no longer
  reference lockdown or integrity and yet the lockdown still applied:

  sarnold@millbarge:~/Canonical/work-reports$ uname -a
  Linux millbarge 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
  sarnold@millbarge:~/Canonical/work-reports$ cat /proc/cmdline 
  BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-14-generic root=ZFS=rpool/ROOT/ubuntu 
ro root=ZFS=rpool/ROOT/ubuntu quiet splash acpi_osi=! "acpi_osi=Windows 2015" 
security=yama,apparmor vt.handoff=1
  sarnold@millbarge:~/Canonical/work-reports$ dmesg | grep -i lockdown
  [0.000

[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

2020-02-28 Thread Seth Arnold
This web page may be a good reproducer candidate:

https://platform.leolabs.space/visualizations/conjunction?type=conjunction&reportId=2004981040

Loading it in firefox would make my computer unresponsive for over a
minute. (Be careful with firefox reloading it when re-opening firefox.)

Loading it in chromium-browser made my computer unresponsive for 45
seconds.

Thanks

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

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:

[Kernel-packages] [Bug 1865295] [NEW] dangling documentation symlinks

2020-02-29 Thread Seth Arnold
Public bug reported:

Hello, there's dangling symlinks in the zfsutils-linux binary packages
on a bionic system:

lrwxrwxrwx 1 root root7 Apr 13  2016 libnvpair1linux -> zfs-doc
lrwxrwxrwx 1 root root7 Apr 13  2016 libuutil1linux -> zfs-doc
lrwxrwxrwx 1 root root7 Apr 13  2016 libzfs2linux -> zfs-doc
lrwxrwxrwx 1 root root7 Apr 13  2016 libzpool2linux -> zfs-doc
lrwxrwxrwx 1 root root7 Apr 13  2016 zfsutils-linux -> zfs-doc
lrwxrwxrwx 1 root root7 Apr 13  2016 zfs-zed -> zfs-doc

zfs-doc:
total 68
lrwxrwxrwx 1 root root38 Dec 17 06:15 changelog.Debian.gz -> 
../libnvpair1linux/changelog.Debian.gz
-rw-r--r-- 1 root root 53854 Oct  6  2017 copyright
lrwxrwxrwx 1 root root28 Dec 17 06:15 COPYRIGHT -> 
../libnvpair1linux/COPYRIGHT
drwxr-xr-x 2 root root  4096 Feb 29 09:37 examples
lrwxrwxrwx 1 root root41 Dec 17 06:15 OPENSOLARIS.LICENSE.gz -> 
../libnvpair1linux/OPENSOLARIS.LICENSE.gz
-rw-r--r-- 1 root root   684 Oct  6  2017 README.Debian

apt-get install --reinstall zfs-doc fixed it.

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: zfs-doc (not installed)
ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
Uname: Linux 4.15.0-62-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
Date: Sat Feb 29 09:44:37 2020
InstallationDate: Installed on 2012-10-18 (2690 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
ProcEnviron:
 TERM=rxvt-unicode-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: Upgraded to bionic on 2018-05-02 (668 days ago)

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

Title:
  dangling documentation symlinks

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Hello, there's dangling symlinks in the zfsutils-linux binary packages
  on a bionic system:

  lrwxrwxrwx 1 root root7 Apr 13  2016 libnvpair1linux -> zfs-doc
  lrwxrwxrwx 1 root root7 Apr 13  2016 libuutil1linux -> zfs-doc
  lrwxrwxrwx 1 root root7 Apr 13  2016 libzfs2linux -> zfs-doc
  lrwxrwxrwx 1 root root7 Apr 13  2016 libzpool2linux -> zfs-doc
  lrwxrwxrwx 1 root root7 Apr 13  2016 zfsutils-linux -> zfs-doc
  lrwxrwxrwx 1 root root7 Apr 13  2016 zfs-zed -> zfs-doc

  zfs-doc:
  total 68
  lrwxrwxrwx 1 root root38 Dec 17 06:15 changelog.Debian.gz -> 
../libnvpair1linux/changelog.Debian.gz
  -rw-r--r-- 1 root root 53854 Oct  6  2017 copyright
  lrwxrwxrwx 1 root root28 Dec 17 06:15 COPYRIGHT -> 
../libnvpair1linux/COPYRIGHT
  drwxr-xr-x 2 root root  4096 Feb 29 09:37 examples
  lrwxrwxrwx 1 root root41 Dec 17 06:15 OPENSOLARIS.LICENSE.gz -> 
../libnvpair1linux/OPENSOLARIS.LICENSE.gz
  -rw-r--r-- 1 root root   684 Oct  6  2017 README.Debian

  apt-get install --reinstall zfs-doc fixed it.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: zfs-doc (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  Uname: Linux 4.15.0-62-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  Date: Sat Feb 29 09:44:37 2020
  InstallationDate: Installed on 2012-10-18 (2690 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (668 days ago)

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

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


[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

2020-03-02 Thread Seth Arnold
Andrea, this new kernel looks promising.

Linux millbarge 5.4.0-17-generic #21-Ubuntu SMP Fri Feb 28 16:18:44 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux

Unfortunately I didn't check the reproducer before rebooting: the error
message I get with it now suggests that it might not work any more.

However, this visualization
https://platform.leolabs.space/visualizations/leo sure feels like it
would have the heft to reproduce the problem. It worked fine for me in
both firefox and chromium-browser:

sarnold 4987 14.1  3.0 3042112 495860 ?  Sl   03:42   0:46 
/usr/lib/firefox/firefox
sarnold 5070  7.3  1.8 2651760 293108 ?  Sl   03:42   0:23 
/usr/lib/firefox/firefox -contentproc -childID 1
sarnold 5175  2.5  0.9 2559560 155888 ?  Sl   03:42   0:08 
/usr/lib/firefox/firefox -contentproc -childID 2
sarnold 5736  5.6  2.9 4144456 476876 ?  Sl   03:42   0:17 
/usr/lib/firefox/firefox -contentproc -childID 4
sarnold 9668  0.3  0.4 2382156 71616 ?   Sl   03:46   0:00 
/usr/lib/firefox/firefox -contentproc -childID 6


sarnold10394  6.7  1.1 3036576 182812 ?  Sl   03:48   0:04 
/snap/chromium/1040/usr/lib/chrom
sarnold10672  0.0  0.2 407644 47472 ?S03:48   0:00 
/snap/chromium/1040/usr/lib/chrom
sarnold10674  0.0  0.0 407644 12932 ?S03:48   0:00 
/snap/chromium/1040/usr/lib/chrom
sarnold10690 17.9  2.3 1269704 372880 ?  Sl   03:48   0:10 
/snap/chromium/1040/usr/lib/chrom
sarnold10694  0.8  0.4 1014184 77752 ?   Sl   03:48   0:00 
/snap/chromium/1040/usr/lib/chrom
sarnold10735 60.2  3.2 6219072 521464 ?  Sl   03:48   0:36 
/snap/chromium/1040/usr/lib/chrom
sarnold10780  0.0  0.3 5498108 51232 ?   Sl   03:48   0:00 
/snap/chromium/1040/usr/lib/chrom


I also did several git fast-forward merges on various Linux git trees; these 
have not been reliable reproducers, but they also completed without trouble.

An uptime of 30 minutes is perhaps too short to declare success but this
is certainly promising.

Thanks

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

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-

[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

2020-03-03 Thread Seth Arnold
Andrea, unfortunately this updated kernel hasn't fixed the problem:

 01:02:48 up 21:21,  9 users,  load average: 1.45, 0.98, 0.58

Linux millbarge 5.4.0-17-generic #21-Ubuntu SMP Fri Feb 28 16:18:44 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux


I was able to reproduce the swap growth and hangs with Firefox, doing a few 
google image searches.

Thanks

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

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Ge

[Kernel-packages] [Bug 1862708] Re: tracing doesn't work on focal

2020-03-05 Thread Seth Arnold
I couldn't find a way to disable the lockdown functionality short of
disabling secure boot in my UEFI system setup.

If we choose to keep lockdown enabled by default then we will need to
document a way it can be disabled so users can run applications like
https://cilium.io/ or the bcc iovisor tools.

(I wish I could run the iovisor tools. I've come to detest Focal because
my computer freezes for a minute or two every few hours and having no
way to debug it, at all, is frustrating.)

Thanks

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

Title:
  tracing doesn't work on focal

Status in linux package in Ubuntu:
  Confirmed
Status in perf-tools-unstable package in Ubuntu:
  New

Bug description:
  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:

  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options

  
  I'm guessing this is due to lockdown:

  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534785] Could not create tracefs 'tracing_on' entry
  [0.534786] Lockdown: swapper/0: use of tracefs is restricted; se

[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

2020-03-09 Thread Seth Arnold
There is an interesting (to me, anyway) change of behaviour with the -17
kernel: while earlier kernels would appear to be locked solid for 30-60
seconds before the screen could update, -17 allows screen updates every
six seconds or so.

I have an always-running mosh session to a remote host running irssi.
This session has a clock that updates every second. When this problem
strikes I can glance at this clock and by watching the time jumps, gauge
how long the hangs are.

When the -17 kernel hangs during these events, this clock updates
roughly every six seconds:

eg on seconds 36, 42, 48, 54, 00, 06, 13, 19, 25, 31, 37, 43, 50, 56..

The system is by no means usable during this time, but it is interesting
that enough userspace ran for mosh to accept packets and redraw the
urxvt terminal, and xorg to update the screen.

My most recent hang happened while firefox loaded
https://www.google.com/maps/place/20%C2%B054'35.7%22S+55%C2%B035'05.0%22E/@-20.9099167,55.5826253,2281m/data=!3m2!1e3!4b1!4m5!3m4!1s0x0:0x0!8m2!3d-20.90991!4d55.58471
but it might be the case that this is just what pushed my browser over
the edge, after loading several pages of google docs content and a PDF.

Thanks

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

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrN

[Kernel-packages] [Bug 1854881] Re: Boot hang after updating and setting up Iscsi with 4.15.0-72 generic kernel

2019-12-02 Thread Seth Arnold
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: intel-microcode (Ubuntu)

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

Title:
  Boot hang after updating and setting up Iscsi with  4.15.0-72 generic
  kernel

Status in linux package in Ubuntu:
  New

Bug description:
  Hi All,

  Host Server - Dell PowerEdge R630, Dual Xeon E5-2650 v4, 768GB Memory,
  ESX 6.5.0

  I created a VM with 1vCPU, 2GB Memory, 16GB Hard drive.

  I installed Ubuntu Server 16.04.2 (latest ISO I had on hand),
  installed fine.

  I then ran apt-get update, apt-get upgrade... upgrade failed as repos
  were out of date. I then ran do-distribution-upgrade, ran through
  everything and it appears to work.

  --I don't want to mislead anyone - I can't remember if I rebooted or
  not at this point.

  After this, I setup an Iscsi initiator to an external target, added to
  fstab, formatted and confirmed all working.

  I then rebooted, and... nothing!

  No ping, no ssh or anything... Control + Alt + Del did not work,
  looked like it had frozen. The last line was starting SSH, but the
  previous line was the Iscsi initiator. At this point, I figured
  network is down and ISCSI is hanging as it can't connect/maybe I
  messed up the ISCSI mount.

  I then went to GRUB and did advanced, I did the recovery console for
  kernel 4.15.0-72 generic which lead to a kernel panic:
  https://snipboard.io/YCOZwv.jpg

  I then went through the options again and selected 4.4.0-62 generic,
  and it booted fine, and after about 2 seconds at the recovery menu,
  further ISCSI related text came up: https://snipboard.io/ALZcsF.jpg

  I went to the shell as root, deleted the line from fstab, and
  rebooted, but, it hang again at the same point.

  I then went to advanced, booted normally to 4.4.0-62 generic, and, it
  went through without any issue what so ever.

  Messing around with kernels puts me out of my depth... happy to give
  further info or do more diagnostics if required, however, due to it
  working in a different kernel and nothing out of the ordinary - I
  believe this to be a bug.

  This is on Ubuntu 18.04.3 LTS / Release 18.04

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

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


[Kernel-packages] [Bug 1860822] Re: ptrace fails with yama/ptrace_scope=0

2020-01-24 Thread Seth Arnold
Hello, this appears to be working as designed.

In Linux, process tracing is tied with the process dumping flag. The
dumpable flag is cleared at execve(2) time when a setuid or setgid
application is executed. This flag persists to child processes created
by fork(2) and will only be reset when a process calls execve(2) again.

The server.c program does not call any of the exec() family of
functions, nor system(3). Thus the flag is never set in the child
process.

You may be able to amend your application to call prctl(2) with
PR_SET_DUMPABLE if you wish to be able to trace the child. I will
caution you that the child may contain private data from the parent in
either shared memory segments that are open in both, copied memory
segments, duplicated file descriptors, etc. It would be better to change
your application design to use an execve(2) when starting a child
process that must be traced to ensure that a minimum of resources are
shared between parent and child.

Many thanks for the very clear description and source code. It really
helped me to understand what you were seeing and why.

Thanks

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

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

Title:
  ptrace fails with yama/ptrace_scope=0

Status in linux-signed package in Ubuntu:
  Won't Fix

Bug description:
  I cannot attach to a process with gdb despite setting ptrace_scope to
  0.  The process has no capabilities, and is running under my uid &
  gid.

  The process is a child, forked from a privileged program that has
  divested itself of its parent's privileges.  The parent is setgid and
  has some capabilities.  None of that is true of the child.

  First, the OS:

  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS
  Release:16.04

  The ptrace setting:

  $ nl /proc/sys/kernel/yama/ptrace_scope 
   1  0

  Me:

  $ echo uid: $(id -u) gid: $(id -g)
  uid: 1000 gid: 1000

  
  The test program (source included with this PR): 

  $ ls -ln server
  -rwxrwsr-x 1 1000 1002 17760 Jan 24 17:30 server

  $ getcap server
  server = cap_dac_read_search,cap_sys_ptrace+ep

  Please note it is setgid to the group 1002, not my gid.

  The "server" program forks a child.  That child

  1. reports its uid and gid: effective, real, and saved, and its capabilities
  2. removes its capabilities with cap_set_proc and disclaims its gid with 
setregid(getgid(), getgid())
  3. reports its uid and gid, and capabilities again
  4. pauses with pause(2). 

  Although the child reports everything is in order, gdb still cannot
  attach to it.

  To facilitate testing, the child writes its pid to a fifo named on the
  command line.  That lets the following script read the pid from the
  fifo and conveniently demonstrate the whole problem:

  [snip]
  $ echo q | sh -x ./run 
  + set -e
  + rm -f fifo
  + mkfifo fifo
  + ./server fifo
  child 18876 paused awaiting SIGCONT
   inherited: user  1000, euser  1000
   inherited: group 1000, egroup 1002
   inherited: ruid  1000, euid  1000, suid 1000
   inherited: rgid  1000, egid  1002, sgid 1002
   inherited capabilities: '= cap_dac_read_search,cap_sys_ptrace+ep'
 new: user  1000, euser  1000
 new: group 1000, egroup 1000
 new: ruid  1000, euid  1000, suid 1000
 new: rgid  1000, egid  1000, sgid 1000
 new capabilities: '='
  + read pid
  + echo child is 18876
  child is 18876
  + gdb -q -p 18876
  Attaching to process 18876
  Could not attach to process.  If your uid matches the uid of the target
  process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
  again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf
  ptrace: Operation not permitted.
  (gdb) + kill -s CONT 18876
  child exited
  [pins]

  This appears to be a bug that affects everyone using gdb on Ubuntu.
  If so, many dealing with privileged processes are working around it by
  running gdb as root.  It's not clear to me that's an improvement on
  the status quo ante, before the ptrace_scope control was introduced.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-169-generic 4.4.0-169.198
  ProcVersionSignature: Ubuntu 4.4.0-169.198-generic 4.4.197
  Uname: Linux 4.4.0-169-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  Date: Fri Jan 24 17:03:29 2020
  InstallationDate: Installed on 2016-07-15 (1288 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://la

[Kernel-packages] [Bug 1861053] [NEW] no fatrace output in focal

2020-01-27 Thread Seth Arnold
Public bug reported:

Hello, fatrace in focal doesn't seem to work for me in focal.

Start fatrace in one terminal, and perform file operations in another
terminal: man man, echo hi > hi, echo hi > /run/user/1000/hi, etc.

sarnold@millbarge:~$ sudo fatrace
[sudo] password for sarnold: 
^Csarnold@millbarge:~$ sudo strace -yy fatrace
execve("/usr/sbin/fatrace", ["fatrace"], 0x7ffcc89ad9c8 /* 15 vars */) = 0
brk(NULL)   = 0x55c9a1947000
arch_prctl(0x3001 /* ARCH_??? */, 0x7ffd18dbde80) = -1 EINVAL (Invalid argument)
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=71040, ...}) = 0
mmap(NULL, 71040, PROT_READ, MAP_PRIVATE, 3, 0) = 
0x7f3539b15000
close(3)  = 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 
3
read(3, 
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360r\2\0\0\0\0\0"..., 832) = 832
lseek(3, 64, SEEK_SET) = 64
read(3, 
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
lseek(3, 848, SEEK_SET) = 848
read(3, 
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
lseek(3, 880, SEEK_SET) = 880
read(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
 68) = 68
fstat(3, {st_mode=S_IFREG|0755, 
st_size=2025032, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f3539b13000
lseek(3, 64, SEEK_SET) = 64
read(3, 
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
lseek(3, 848, SEEK_SET) = 848
read(3, 
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
lseek(3, 880, SEEK_SET) = 880
read(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
 68) = 68
mmap(NULL, 2032984, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 
3, 0) = 0x7f3539922000
mmap(0x7f3539947000, 1540096, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x25000) = 0x7f3539947000
mmap(0x7f3539abf000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 
3, 0x19d000) = 0x7f3539abf000
mmap(0x7f3539b09000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x1e6000) = 0x7f3539b09000
mmap(0x7f3539b0f000, 13656, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f3539b0f000
close(3) = 0
arch_prctl(ARCH_SET_FS, 0x7f3539b14580) = 0
mprotect(0x7f3539b09000, 12288, PROT_READ) = 0
mprotect(0x55c99fee8000, 4096, PROT_READ) = 0
mprotect(0x7f3539b53000, 4096, PROT_READ) = 0
munmap(0x7f3539b15000, 71040)   = 0
getpid()= 120700
fanotify_init(FAN_CLASS_NOTIF, O_RDONLY|O_LARGEFILE) = 3
brk(NULL)   = 0x55c9a1947000
brk(0x55c9a1968000) = 0x55c9a1968000
openat(AT_FDCWD, "/proc/self/mounts", O_RDONLY|O_CLOEXEC) = 
4
fstat(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(4, "sysfs /sys sysfs rw,nosuid,nodev"..., 1024) = 1024
access("sysfs", F_OK)   = -1 ENOENT (No such file or directory)
access("proc", F_OK)= -1 ENOENT (No such file or directory)
access("udev", F_OK)= -1 ENOENT (No such file or directory)
access("devpts", F_OK)  = -1 ENOENT (No such file or directory)
access("tmpfs", F_OK)   = -1 ENOENT (No such file or directory)
access("rpool/ROOT/ubuntu", F_OK)   = -1 ENOENT (No such file or directory)
access("securityfs", F_OK)  = -1 ENOENT (No such file or directory)
access("tmpfs", F_OK)   = -1 ENOENT (No such file or directory)
access("tmpfs", F_OK)   = -1 ENOENT (No such file or directory)
access("tmpfs", F_OK)   = -1 ENOENT (No such file or directory)
access("cgroup2", F_OK) = -1 ENOENT (No such file or directory)
access("cgroup", F_OK)  = -1 ENOENT (No such file or directory)
access("pstore", F_OK)  = -1 ENOENT (No such file or directory)
access("efivarfs", F_OK)= -1 ENOENT (No such file or directory)
read(4, "de=700 0 0\ncgroup /sys/fs/cgroup"..., 1024) = 
1024
access("none", F_OK)= -1 ENOENT (No such file or directory)
access("cgroup", F_OK)  = -1 ENOENT (No such file or directory)
access("cgroup", F_OK)  = -1 ENOENT (No such file or directory)
access("cgroup", F_OK)  = -1 ENOENT (No such file or directory)
access("cgroup", F_OK)  = -1 ENOENT (No such file or directory)
access("cgroup", F_OK)  = -1 ENOENT (No such file or directory)
access("cgroup", F_OK)  = -1 ENOENT (No such file or directory)
access("cgroup", F_OK)  = -1 ENOENT (No such file or directory)
access("cgroup", F_OK)  = -1 ENOENT (No such file or directory)
access("cgroup", F_OK)  

[Kernel-packages] [Bug 1861053] Re: no fatrace output in focal

2020-01-27 Thread Seth Arnold
I added the linux package too, because the strace doesn't seem too
unusual.

** Attachment added: "strace.out"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861053/+attachment/5323430/+files/strace.out

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

Title:
  no fatrace output in focal

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

Bug description:
  Hello, fatrace in focal doesn't seem to work for me in focal.

  Start fatrace in one terminal, and perform file operations in another
  terminal: man man, echo hi > hi, echo hi > /run/user/1000/hi, etc.

  sarnold@millbarge:~$ sudo fatrace
  [sudo] password for sarnold: 
  ^Csarnold@millbarge:~$ sudo strace -yy fatrace
  execve("/usr/sbin/fatrace", ["fatrace"], 0x7ffcc89ad9c8 /* 15 vars */) = 0
  brk(NULL)   = 0x55c9a1947000
  arch_prctl(0x3001 /* ARCH_??? */, 0x7ffd18dbde80) = -1 EINVAL (Invalid 
argument)
  access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or 
directory)
  openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=71040, ...}) = 0
  mmap(NULL, 71040, PROT_READ, MAP_PRIVATE, 3, 0) = 
0x7f3539b15000
  close(3)  = 0
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 
3
  read(3, 
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360r\2\0\0\0\0\0"..., 832) = 832
  lseek(3, 64, SEEK_SET) = 64
  read(3, 
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
  lseek(3, 848, SEEK_SET) = 848
  read(3, 
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
  lseek(3, 880, SEEK_SET) = 880
  read(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
 68) = 68
  fstat(3, {st_mode=S_IFREG|0755, 
st_size=2025032, ...}) = 0
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f3539b13000
  lseek(3, 64, SEEK_SET) = 64
  read(3, 
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
  lseek(3, 848, SEEK_SET) = 848
  read(3, 
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
  lseek(3, 880, SEEK_SET) = 880
  read(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
 68) = 68
  mmap(NULL, 2032984, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 
3, 0) = 0x7f3539922000
  mmap(0x7f3539947000, 1540096, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x25000) = 0x7f3539947000
  mmap(0x7f3539abf000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 
3, 0x19d000) = 0x7f3539abf000
  mmap(0x7f3539b09000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x1e6000) = 0x7f3539b09000
  mmap(0x7f3539b0f000, 13656, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f3539b0f000
  close(3) = 0
  arch_prctl(ARCH_SET_FS, 0x7f3539b14580) = 0
  mprotect(0x7f3539b09000, 12288, PROT_READ) = 0
  mprotect(0x55c99fee8000, 4096, PROT_READ) = 0
  mprotect(0x7f3539b53000, 4096, PROT_READ) = 0
  munmap(0x7f3539b15000, 71040)   = 0
  getpid()= 120700
  fanotify_init(FAN_CLASS_NOTIF, O_RDONLY|O_LARGEFILE) = 
3
  brk(NULL)   = 0x55c9a1947000
  brk(0x55c9a1968000) = 0x55c9a1968000
  openat(AT_FDCWD, "/proc/self/mounts", O_RDONLY|O_CLOEXEC) = 
4
  fstat(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  read(4, "sysfs /sys sysfs rw,nosuid,nodev"..., 1024) = 
1024
  access("sysfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("proc", F_OK)= -1 ENOENT (No such file or 
directory)
  access("udev", F_OK)= -1 ENOENT (No such file or 
directory)
  access("devpts", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("rpool/ROOT/ubuntu", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("securityfs", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("cgroup2", F_OK) = -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("pstore", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("efivarfs", F_OK)= -1 ENOENT (No such file or 
directory)
  read(4, "de=700 0 0\ncgroup /sys/fs/cgroup"..., 1024) = 
1024
  access("none", F_OK)= -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK) 

[Kernel-packages] [Bug 1861053] Re: no fatrace output in focal

2020-01-27 Thread Seth Arnold
apport information

** Tags added: apport-collected

** Description changed:

  Hello, fatrace in focal doesn't seem to work for me in focal.
  
  Start fatrace in one terminal, and perform file operations in another
  terminal: man man, echo hi > hi, echo hi > /run/user/1000/hi, etc.
  
  sarnold@millbarge:~$ sudo fatrace
  [sudo] password for sarnold: 
  ^Csarnold@millbarge:~$ sudo strace -yy fatrace
  execve("/usr/sbin/fatrace", ["fatrace"], 0x7ffcc89ad9c8 /* 15 vars */) = 0
  brk(NULL)   = 0x55c9a1947000
  arch_prctl(0x3001 /* ARCH_??? */, 0x7ffd18dbde80) = -1 EINVAL (Invalid 
argument)
  access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or 
directory)
  openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=71040, ...}) = 0
  mmap(NULL, 71040, PROT_READ, MAP_PRIVATE, 3, 0) = 
0x7f3539b15000
  close(3)  = 0
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 
3
  read(3, 
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360r\2\0\0\0\0\0"..., 832) = 832
  lseek(3, 64, SEEK_SET) = 64
  read(3, 
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
  lseek(3, 848, SEEK_SET) = 848
  read(3, 
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
  lseek(3, 880, SEEK_SET) = 880
  read(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
 68) = 68
  fstat(3, {st_mode=S_IFREG|0755, 
st_size=2025032, ...}) = 0
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f3539b13000
  lseek(3, 64, SEEK_SET) = 64
  read(3, 
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
  lseek(3, 848, SEEK_SET) = 848
  read(3, 
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
  lseek(3, 880, SEEK_SET) = 880
  read(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
 68) = 68
  mmap(NULL, 2032984, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 
3, 0) = 0x7f3539922000
  mmap(0x7f3539947000, 1540096, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x25000) = 0x7f3539947000
  mmap(0x7f3539abf000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 
3, 0x19d000) = 0x7f3539abf000
  mmap(0x7f3539b09000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x1e6000) = 0x7f3539b09000
  mmap(0x7f3539b0f000, 13656, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f3539b0f000
  close(3) = 0
  arch_prctl(ARCH_SET_FS, 0x7f3539b14580) = 0
  mprotect(0x7f3539b09000, 12288, PROT_READ) = 0
  mprotect(0x55c99fee8000, 4096, PROT_READ) = 0
  mprotect(0x7f3539b53000, 4096, PROT_READ) = 0
  munmap(0x7f3539b15000, 71040)   = 0
  getpid()= 120700
  fanotify_init(FAN_CLASS_NOTIF, O_RDONLY|O_LARGEFILE) = 
3
  brk(NULL)   = 0x55c9a1947000
  brk(0x55c9a1968000) = 0x55c9a1968000
  openat(AT_FDCWD, "/proc/self/mounts", O_RDONLY|O_CLOEXEC) = 
4
  fstat(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  read(4, "sysfs /sys sysfs rw,nosuid,nodev"..., 1024) = 
1024
  access("sysfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("proc", F_OK)= -1 ENOENT (No such file or 
directory)
  access("udev", F_OK)= -1 ENOENT (No such file or 
directory)
  access("devpts", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("rpool/ROOT/ubuntu", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("securityfs", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("cgroup2", F_OK) = -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("pstore", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("efivarfs", F_OK)= -1 ENOENT (No such file or 
directory)
  read(4, "de=700 0 0\ncgroup /sys/fs/cgroup"..., 1024) = 
1024
  access("none", F_OK)= -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No 

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

2020-01-27 Thread Seth Arnold
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1861053/+attachment/5323432/+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/1861053

Title:
  no fatrace output in focal

Status in fatrace package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, fatrace in focal doesn't seem to work for me in focal.

  Start fatrace in one terminal, and perform file operations in another
  terminal: man man, echo hi > hi, echo hi > /run/user/1000/hi, etc.

  sarnold@millbarge:~$ sudo fatrace
  [sudo] password for sarnold: 
  ^Csarnold@millbarge:~$ sudo strace -yy fatrace
  execve("/usr/sbin/fatrace", ["fatrace"], 0x7ffcc89ad9c8 /* 15 vars */) = 0
  brk(NULL)   = 0x55c9a1947000
  arch_prctl(0x3001 /* ARCH_??? */, 0x7ffd18dbde80) = -1 EINVAL (Invalid 
argument)
  access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or 
directory)
  openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=71040, ...}) = 0
  mmap(NULL, 71040, PROT_READ, MAP_PRIVATE, 3, 0) = 
0x7f3539b15000
  close(3)  = 0
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 
3
  read(3, 
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360r\2\0\0\0\0\0"..., 832) = 832
  lseek(3, 64, SEEK_SET) = 64
  read(3, 
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
  lseek(3, 848, SEEK_SET) = 848
  read(3, 
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
  lseek(3, 880, SEEK_SET) = 880
  read(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
 68) = 68
  fstat(3, {st_mode=S_IFREG|0755, 
st_size=2025032, ...}) = 0
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f3539b13000
  lseek(3, 64, SEEK_SET) = 64
  read(3, 
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
  lseek(3, 848, SEEK_SET) = 848
  read(3, 
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
  lseek(3, 880, SEEK_SET) = 880
  read(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
 68) = 68
  mmap(NULL, 2032984, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 
3, 0) = 0x7f3539922000
  mmap(0x7f3539947000, 1540096, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x25000) = 0x7f3539947000
  mmap(0x7f3539abf000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 
3, 0x19d000) = 0x7f3539abf000
  mmap(0x7f3539b09000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x1e6000) = 0x7f3539b09000
  mmap(0x7f3539b0f000, 13656, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f3539b0f000
  close(3) = 0
  arch_prctl(ARCH_SET_FS, 0x7f3539b14580) = 0
  mprotect(0x7f3539b09000, 12288, PROT_READ) = 0
  mprotect(0x55c99fee8000, 4096, PROT_READ) = 0
  mprotect(0x7f3539b53000, 4096, PROT_READ) = 0
  munmap(0x7f3539b15000, 71040)   = 0
  getpid()= 120700
  fanotify_init(FAN_CLASS_NOTIF, O_RDONLY|O_LARGEFILE) = 
3
  brk(NULL)   = 0x55c9a1947000
  brk(0x55c9a1968000) = 0x55c9a1968000
  openat(AT_FDCWD, "/proc/self/mounts", O_RDONLY|O_CLOEXEC) = 
4
  fstat(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  read(4, "sysfs /sys sysfs rw,nosuid,nodev"..., 1024) = 
1024
  access("sysfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("proc", F_OK)= -1 ENOENT (No such file or 
directory)
  access("udev", F_OK)= -1 ENOENT (No such file or 
directory)
  access("devpts", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("rpool/ROOT/ubuntu", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("securityfs", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("cgroup2", F_OK) = -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("pstore", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("efivarfs", F_OK)= -1 ENOENT (No such file or 
directory)
  read(4, "de=700 0 0\ncgroup /sys/fs/cgroup"..., 1024) = 
1024
  access("none", F_OK)= -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No such file or 
directory)
 

[Kernel-packages] [Bug 1861053] Re: no fatrace output in focal

2020-01-27 Thread Seth Arnold
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  no fatrace output in focal

Status in fatrace package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, fatrace in focal doesn't seem to work for me in focal.

  Start fatrace in one terminal, and perform file operations in another
  terminal: man man, echo hi > hi, echo hi > /run/user/1000/hi, etc.

  sarnold@millbarge:~$ sudo fatrace
  [sudo] password for sarnold: 
  ^Csarnold@millbarge:~$ sudo strace -yy fatrace
  execve("/usr/sbin/fatrace", ["fatrace"], 0x7ffcc89ad9c8 /* 15 vars */) = 0
  brk(NULL)   = 0x55c9a1947000
  arch_prctl(0x3001 /* ARCH_??? */, 0x7ffd18dbde80) = -1 EINVAL (Invalid 
argument)
  access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or 
directory)
  openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=71040, ...}) = 0
  mmap(NULL, 71040, PROT_READ, MAP_PRIVATE, 3, 0) = 
0x7f3539b15000
  close(3)  = 0
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 
3
  read(3, 
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360r\2\0\0\0\0\0"..., 832) = 832
  lseek(3, 64, SEEK_SET) = 64
  read(3, 
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
  lseek(3, 848, SEEK_SET) = 848
  read(3, 
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
  lseek(3, 880, SEEK_SET) = 880
  read(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
 68) = 68
  fstat(3, {st_mode=S_IFREG|0755, 
st_size=2025032, ...}) = 0
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f3539b13000
  lseek(3, 64, SEEK_SET) = 64
  read(3, 
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
  lseek(3, 848, SEEK_SET) = 848
  read(3, 
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
  lseek(3, 880, SEEK_SET) = 880
  read(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
 68) = 68
  mmap(NULL, 2032984, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 
3, 0) = 0x7f3539922000
  mmap(0x7f3539947000, 1540096, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x25000) = 0x7f3539947000
  mmap(0x7f3539abf000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 
3, 0x19d000) = 0x7f3539abf000
  mmap(0x7f3539b09000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x1e6000) = 0x7f3539b09000
  mmap(0x7f3539b0f000, 13656, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f3539b0f000
  close(3) = 0
  arch_prctl(ARCH_SET_FS, 0x7f3539b14580) = 0
  mprotect(0x7f3539b09000, 12288, PROT_READ) = 0
  mprotect(0x55c99fee8000, 4096, PROT_READ) = 0
  mprotect(0x7f3539b53000, 4096, PROT_READ) = 0
  munmap(0x7f3539b15000, 71040)   = 0
  getpid()= 120700
  fanotify_init(FAN_CLASS_NOTIF, O_RDONLY|O_LARGEFILE) = 
3
  brk(NULL)   = 0x55c9a1947000
  brk(0x55c9a1968000) = 0x55c9a1968000
  openat(AT_FDCWD, "/proc/self/mounts", O_RDONLY|O_CLOEXEC) = 
4
  fstat(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  read(4, "sysfs /sys sysfs rw,nosuid,nodev"..., 1024) = 
1024
  access("sysfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("proc", F_OK)= -1 ENOENT (No such file or 
directory)
  access("udev", F_OK)= -1 ENOENT (No such file or 
directory)
  access("devpts", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("rpool/ROOT/ubuntu", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("securityfs", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("cgroup2", F_OK) = -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("pstore", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("efivarfs", F_OK)= -1 ENOENT (No such file or 
directory)
  read(4, "de=700 0 0\ncgroup /sys/fs/cgroup"..., 1024) = 
1024
  access("none", F_OK)= -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No such file or 
directory)
  access(

[Kernel-packages] [Bug 1861228] [NEW] zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

2020-01-28 Thread Seth Arnold
Public bug reported:

Hello, I believe these errors happened due to a zfs recv command that
was executing at the time:

[10823702.582392] VERIFY(size != 0) failed
[10823702.582428] PANIC at range_tree.c:304:range_tree_find_impl()
[10823702.582463] Showing stack for process 693172
[10823702.582466] CPU: 7 PID: 693172 Comm: receive_writer Tainted: P   
O 4.15.0-60-generic #67-Ubuntu
[10823702.582466] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 
2.0 12/17/2015
[10823702.582467] Call Trace:
[10823702.582475]  dump_stack+0x63/0x8b
[10823702.582489]  spl_dumpstack+0x42/0x50 [spl]
[10823702.582494]  spl_panic+0xc8/0x110 [spl]
[10823702.582539]  ? dbuf_dirty+0x43d/0x850 [zfs]
[10823702.582542]  ? getrawmonotonic64+0x43/0xd0
[10823702.582544]  ? getrawmonotonic64+0x43/0xd0
[10823702.582581]  ? dmu_zfetch+0x49a/0x500 [zfs]
[10823702.582583]  ? getrawmonotonic64+0x43/0xd0
[10823702.582619]  ? dmu_zfetch+0x49a/0x500 [zfs]
[10823702.582621]  ? mutex_lock+0x12/0x40
[10823702.582654]  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
[10823702.582697]  range_tree_find_impl+0x88/0x90 [zfs]
[10823702.582702]  ? spl_kmem_zalloc+0xdc/0x1a0 [spl]
[10823702.582743]  range_tree_clear+0x4f/0x60 [zfs]
[10823702.582780]  dnode_free_range+0x11f/0x5a0 [zfs]
[10823702.582815]  dmu_object_free+0x53/0x90 [zfs]
[10823702.582850]  dmu_free_long_object+0x9f/0xc0 [zfs]
[10823702.582885]  receive_freeobjects.isra.12+0x7a/0x100 [zfs]
[10823702.582918]  receive_writer_thread+0x6d2/0xa60 [zfs]
[10823702.582920]  ? set_curr_task_fair+0x2b/0x60
[10823702.582925]  ? spl_kmem_free+0x33/0x40 [spl]
[10823702.582928]  ? kfree+0x165/0x180
[10823702.582961]  ? receive_free.isra.13+0xc0/0xc0 [zfs]
[10823702.582967]  thread_generic_wrapper+0x74/0x90 [spl]
[10823702.582969]  kthread+0x121/0x140
[10823702.582974]  ? __thread_exit+0x20/0x20 [spl]
[10823702.582975]  ? kthread_create_worker_on_cpu+0x70/0x70
[10823702.582978]  ret_from_fork+0x35/0x40
[10823907.445420] INFO: task txg_quiesce:4485 blocked for more than 120 seconds.
[10823907.445486]   Tainted: P   O 4.15.0-60-generic #67-Ubuntu
[10823907.445535] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
[10823907.445589] txg_quiesce D0  4485  2 0x8000
[10823907.445594] Call Trace:
[10823907.445608]  __schedule+0x24e/0x880
[10823907.445613]  schedule+0x2c/0x80
[10823907.445629]  cv_wait_common+0x11e/0x140 [spl]
[10823907.445638]  ? wait_woken+0x80/0x80
[10823907.445647]  __cv_wait+0x15/0x20 [spl]
[10823907.445766]  txg_quiesce_thread+0x2cb/0x3d0 [zfs]
[10823907.445835]  ? txg_delay+0x1b0/0x1b0 [zfs]
[10823907.445843]  thread_generic_wrapper+0x74/0x90 [spl]
[10823907.445848]  kthread+0x121/0x140
[10823907.445854]  ? __thread_exit+0x20/0x20 [spl]
[10823907.445857]  ? kthread_create_worker_on_cpu+0x70/0x70
[10823907.445861]  ret_from_fork+0x35/0x40
[10823907.445916] INFO: task zfs:688217 blocked for more than 120 seconds.
[10823907.445962]   Tainted: P   O 4.15.0-60-generic #67-Ubuntu
[10823907.446010] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
[10823907.446063] zfs D0 688217 688214 0x8080
[10823907.446066] Call Trace:
[10823907.446071]  __schedule+0x24e/0x880
[10823907.446075]  schedule+0x2c/0x80
[10823907.446084]  cv_wait_common+0x11e/0x140 [spl]
[10823907.446088]  ? wait_woken+0x80/0x80
[10823907.446095]  __cv_wait+0x15/0x20 [spl]
[10823907.446151]  dmu_recv_stream+0xa51/0xef0 [zfs]
[10823907.446227]  zfs_ioc_recv_impl+0x306/0x1100 [zfs]
[10823907.446232]  ? ttwu_do_activate+0x77/0x80
[10823907.446303]  zfs_ioc_recv_new+0x33d/0x410 [zfs]
[10823907.446312]  ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl]
[10823907.446320]  ? spl_vmem_alloc+0x19/0x20 [spl]
[10823907.446332]  ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair]
[10823907.446338]  ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair]
[10823907.446344]  ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair]
[10823907.446409]  zfsdev_ioctl+0x451/0x610 [zfs]
[10823907.446415]  do_vfs_ioctl+0xa8/0x630
[10823907.446419]  ? __audit_syscall_entry+0xbc/0x110
[10823907.446424]  ? syscall_trace_enter+0x1da/0x2d0
[10823907.446426]  SyS_ioctl+0x79/0x90
[10823907.446430]  do_syscall_64+0x73/0x130
[10823907.446434]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[10823907.446437] RIP: 0033:0x7fc4006905d7
[10823907.446438] RSP: 002b:7ffe7df61dc8 EFLAGS: 0246 ORIG_RAX: 
0010
[10823907.446441] RAX: ffda RBX: 5a46 RCX: 
7fc4006905d7
[10823907.446443] RDX: 7ffe7df61de0 RSI: 5a46 RDI: 
0006
[10823907.446444] RBP: 7ffe7df61de0 R08: 7fc400965ce0 R09: 

[10823907.446446] R10: 555c7adad010 R11: 0246 R12: 
7ffe7df65410
[10823907.446447] R13: 0006 R14: 555c7adb4ae0 R15: 
000c
[10823907.446452] INFO: task receive_writer:693172 blocked for more than 120 
seconds.
[10823907.446504]   Tainted: P   O 4.15.0-60-generic #

[Kernel-packages] [Bug 1861235] [NEW] zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

2020-01-28 Thread Seth Arnold
Public bug reported:

Same as bug 1861228 but with a newer kernel installed.

[  790.702566] VERIFY(size != 0) failed
[  790.702590] PANIC at range_tree.c:304:range_tree_find_impl()
[  790.702611] Showing stack for process 28685
[  790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P   O   
  4.15.0-76-generic #86-Ubuntu
[  790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 2.0 
12/17/2015
[  790.702616] Call Trace:
[  790.702626]  dump_stack+0x6d/0x8e
[  790.702637]  spl_dumpstack+0x42/0x50 [spl]
[  790.702640]  spl_panic+0xc8/0x110 [spl]
[  790.702645]  ? __switch_to_asm+0x41/0x70
[  790.702714]  ? arc_prune_task+0x1a/0x40 [zfs]
[  790.702740]  ? dbuf_dirty+0x43d/0x850 [zfs]
[  790.702745]  ? getrawmonotonic64+0x43/0xd0
[  790.702746]  ? getrawmonotonic64+0x43/0xd0
[  790.702775]  ? dmu_zfetch+0x49a/0x500 [zfs]
[  790.702778]  ? getrawmonotonic64+0x43/0xd0
[  790.702805]  ? dmu_zfetch+0x49a/0x500 [zfs]
[  790.702807]  ? mutex_lock+0x12/0x40
[  790.702833]  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
[  790.702866]  range_tree_find_impl+0x88/0x90 [zfs]
[  790.702870]  ? spl_kmem_zalloc+0xdc/0x1a0 [spl]
[  790.702902]  range_tree_clear+0x4f/0x60 [zfs]
[  790.702930]  dnode_free_range+0x11f/0x5a0 [zfs]
[  790.702957]  dmu_object_free+0x53/0x90 [zfs]
[  790.702983]  dmu_free_long_object+0x9f/0xc0 [zfs]
[  790.703010]  receive_freeobjects.isra.12+0x7a/0x100 [zfs]
[  790.703036]  receive_writer_thread+0x6d2/0xa60 [zfs]
[  790.703040]  ? set_curr_task_fair+0x2b/0x60
[  790.703043]  ? spl_kmem_free+0x33/0x40 [spl]
[  790.703048]  ? kfree+0x165/0x180
[  790.703073]  ? receive_free.isra.13+0xc0/0xc0 [zfs]
[  790.703078]  thread_generic_wrapper+0x74/0x90 [spl]
[  790.703081]  kthread+0x121/0x140
[  790.703084]  ? __thread_exit+0x20/0x20 [spl]
[  790.703085]  ? kthread_create_worker_on_cpu+0x70/0x70
[  790.703088]  ret_from_fork+0x35/0x40
[  967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds.
[  967.636979]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
[  967.637024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  967.637076] txg_quiesce D0 14810  2 0x8000
[  967.637080] Call Trace:
[  967.637089]  __schedule+0x24e/0x880
[  967.637092]  schedule+0x2c/0x80
[  967.637106]  cv_wait_common+0x11e/0x140 [spl]
[  967.637114]  ? wait_woken+0x80/0x80
[  967.637122]  __cv_wait+0x15/0x20 [spl]
[  967.637210]  txg_quiesce_thread+0x2cb/0x3d0 [zfs]
[  967.637278]  ? txg_delay+0x1b0/0x1b0 [zfs]
[  967.637286]  thread_generic_wrapper+0x74/0x90 [spl]
[  967.637291]  kthread+0x121/0x140
[  967.637297]  ? __thread_exit+0x20/0x20 [spl]
[  967.637299]  ? kthread_create_worker_on_cpu+0x70/0x70
[  967.637304]  ret_from_fork+0x35/0x40
[  967.637326] INFO: task zfs:28590 blocked for more than 120 seconds.
[  967.637371]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
[  967.637416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  967.637467] zfs D0 28590  28587 0x8080
[  967.637470] Call Trace:
[  967.637474]  __schedule+0x24e/0x880
[  967.637477]  schedule+0x2c/0x80
[  967.637486]  cv_wait_common+0x11e/0x140 [spl]
[  967.637491]  ? wait_woken+0x80/0x80
[  967.637498]  __cv_wait+0x15/0x20 [spl]
[  967.637554]  dmu_recv_stream+0xa51/0xef0 [zfs]
[  967.637630]  zfs_ioc_recv_impl+0x306/0x1100 [zfs]
[  967.637679]  ? dbuf_read+0x34a/0x920 [zfs]
[  967.637725]  ? dbuf_rele+0x36/0x40 [zfs]
[  967.637728]  ? _cond_resched+0x19/0x40
[  967.637798]  zfs_ioc_recv_new+0x33d/0x410 [zfs]
[  967.637809]  ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl]
[  967.637816]  ? spl_vmem_alloc+0x19/0x20 [spl]
[  967.637828]  ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair]
[  967.637834]  ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair]
[  967.637840]  ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair]
[  967.637905]  zfsdev_ioctl+0x451/0x610 [zfs]
[  967.637913]  do_vfs_ioctl+0xa8/0x630
[  967.637917]  ? __audit_syscall_entry+0xbc/0x110
[  967.637924]  ? syscall_trace_enter+0x1da/0x2d0
[  967.637927]  SyS_ioctl+0x79/0x90
[  967.637930]  do_syscall_64+0x73/0x130
[  967.637935]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[  967.637938] RIP: 0033:0x7fc305a905d7
[  967.637940] RSP: 002b:7ffc45e39618 EFLAGS: 0246 ORIG_RAX: 
0010
[  967.637943] RAX: ffda RBX: 5a46 RCX: 7fc305a905d7
[  967.637945] RDX: 7ffc45e39630 RSI: 5a46 RDI: 0006
[  967.637946] RBP: 7ffc45e39630 R08: 7fc305d65e20 R09: 
[  967.637948] R10: 5648313c7010 R11: 0246 R12: 7ffc45e3cc60
[  967.637949] R13: 0006 R14: 5648313cef10 R15: 000c
[  967.637960] INFO: task receive_writer:28685 blocked for more than 120 
seconds.
[  967.638010]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
[  967.638055] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  967.638107] receive_write

[Kernel-packages] [Bug 1861228] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

2020-01-28 Thread Seth Arnold
*** This bug is a duplicate of bug 1861235 ***
https://bugs.launchpad.net/bugs/1861235

** This bug has been marked a duplicate of bug 1861235
   zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

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

Title:
  zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, I believe these errors happened due to a zfs recv command that
  was executing at the time:

  [10823702.582392] VERIFY(size != 0) failed
  [10823702.582428] PANIC at range_tree.c:304:range_tree_find_impl()
  [10823702.582463] Showing stack for process 693172
  [10823702.582466] CPU: 7 PID: 693172 Comm: receive_writer Tainted: P  
 O 4.15.0-60-generic #67-Ubuntu
  [10823702.582466] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 
2.0 12/17/2015
  [10823702.582467] Call Trace:
  [10823702.582475]  dump_stack+0x63/0x8b
  [10823702.582489]  spl_dumpstack+0x42/0x50 [spl]
  [10823702.582494]  spl_panic+0xc8/0x110 [spl]
  [10823702.582539]  ? dbuf_dirty+0x43d/0x850 [zfs]
  [10823702.582542]  ? getrawmonotonic64+0x43/0xd0
  [10823702.582544]  ? getrawmonotonic64+0x43/0xd0
  [10823702.582581]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [10823702.582583]  ? getrawmonotonic64+0x43/0xd0
  [10823702.582619]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [10823702.582621]  ? mutex_lock+0x12/0x40
  [10823702.582654]  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
  [10823702.582697]  range_tree_find_impl+0x88/0x90 [zfs]
  [10823702.582702]  ? spl_kmem_zalloc+0xdc/0x1a0 [spl]
  [10823702.582743]  range_tree_clear+0x4f/0x60 [zfs]
  [10823702.582780]  dnode_free_range+0x11f/0x5a0 [zfs]
  [10823702.582815]  dmu_object_free+0x53/0x90 [zfs]
  [10823702.582850]  dmu_free_long_object+0x9f/0xc0 [zfs]
  [10823702.582885]  receive_freeobjects.isra.12+0x7a/0x100 [zfs]
  [10823702.582918]  receive_writer_thread+0x6d2/0xa60 [zfs]
  [10823702.582920]  ? set_curr_task_fair+0x2b/0x60
  [10823702.582925]  ? spl_kmem_free+0x33/0x40 [spl]
  [10823702.582928]  ? kfree+0x165/0x180
  [10823702.582961]  ? receive_free.isra.13+0xc0/0xc0 [zfs]
  [10823702.582967]  thread_generic_wrapper+0x74/0x90 [spl]
  [10823702.582969]  kthread+0x121/0x140
  [10823702.582974]  ? __thread_exit+0x20/0x20 [spl]
  [10823702.582975]  ? kthread_create_worker_on_cpu+0x70/0x70
  [10823702.582978]  ret_from_fork+0x35/0x40
  [10823907.445420] INFO: task txg_quiesce:4485 blocked for more than 120 
seconds.
  [10823907.445486]   Tainted: P   O 4.15.0-60-generic 
#67-Ubuntu
  [10823907.445535] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [10823907.445589] txg_quiesce D0  4485  2 0x8000
  [10823907.445594] Call Trace:
  [10823907.445608]  __schedule+0x24e/0x880
  [10823907.445613]  schedule+0x2c/0x80
  [10823907.445629]  cv_wait_common+0x11e/0x140 [spl]
  [10823907.445638]  ? wait_woken+0x80/0x80
  [10823907.445647]  __cv_wait+0x15/0x20 [spl]
  [10823907.445766]  txg_quiesce_thread+0x2cb/0x3d0 [zfs]
  [10823907.445835]  ? txg_delay+0x1b0/0x1b0 [zfs]
  [10823907.445843]  thread_generic_wrapper+0x74/0x90 [spl]
  [10823907.445848]  kthread+0x121/0x140
  [10823907.445854]  ? __thread_exit+0x20/0x20 [spl]
  [10823907.445857]  ? kthread_create_worker_on_cpu+0x70/0x70
  [10823907.445861]  ret_from_fork+0x35/0x40
  [10823907.445916] INFO: task zfs:688217 blocked for more than 120 seconds.
  [10823907.445962]   Tainted: P   O 4.15.0-60-generic 
#67-Ubuntu
  [10823907.446010] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [10823907.446063] zfs D0 688217 688214 0x8080
  [10823907.446066] Call Trace:
  [10823907.446071]  __schedule+0x24e/0x880
  [10823907.446075]  schedule+0x2c/0x80
  [10823907.446084]  cv_wait_common+0x11e/0x140 [spl]
  [10823907.446088]  ? wait_woken+0x80/0x80
  [10823907.446095]  __cv_wait+0x15/0x20 [spl]
  [10823907.446151]  dmu_recv_stream+0xa51/0xef0 [zfs]
  [10823907.446227]  zfs_ioc_recv_impl+0x306/0x1100 [zfs]
  [10823907.446232]  ? ttwu_do_activate+0x77/0x80
  [10823907.446303]  zfs_ioc_recv_new+0x33d/0x410 [zfs]
  [10823907.446312]  ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl]
  [10823907.446320]  ? spl_vmem_alloc+0x19/0x20 [spl]
  [10823907.446332]  ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair]
  [10823907.446338]  ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair]
  [10823907.446344]  ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair]
  [10823907.446409]  zfsdev_ioctl+0x451/0x610 [zfs]
  [10823907.446415]  do_vfs_ioctl+0xa8/0x630
  [10823907.446419]  ? __audit_syscall_entry+0xbc/0x110
  [10823907.446424]  ? syscall_trace_enter+0x1da/0x2d0
  [10823907.446426]  SyS_ioctl+0x79/0x90
  [10823907.446430]  do_syscall_64+0x73/0x130
  [10823907.446434]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [10823907.446437] RIP: 0033:0x7fc4006905d7
  [10823907.446438] RSP:

[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

2020-01-29 Thread Seth Arnold
apport information

** Tags added: apport-collected

** Description changed:

  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty seconds.
  No mouse movement, no keyboard input, the screen output does not change.
  
  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.
  
  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)
  
  Thanks
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
+ --- 
+ ProblemType: Bug
+ AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
+ ApportVersion: 2.20.11-0ubuntu16
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  sarnold2734 F pulseaudio
+  /dev/snd/controlC1:  sarnold2734 F pulseaudio
+ Card0.Amixer.info:
+  Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
+Mixer name : 'Realtek ALC285'
+Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
+Controls  : 53
+Simple ctrls  : 15
+ Card1.Amixer.info:
+  Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
+Mixer name : 'USB Mixer'
+Components : 'USB17ef:306f'
+Controls  : 9
+Simple ctrls  : 4
+ DistroRelease: Ubuntu 20.04
+ HibernationDevice: RESUME=none
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
+ MachineType: LENOVO 20KHCTO1WW
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=rxvt-unicode-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
+ ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-12-generic N/A
+  linux-backports-modules-5.4.0-12-generic  N/A
+  linux-firmware1.185
+ Tags:  focal
+ Uname: Linux 5.4.0-12-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
+ UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
+ _MarkForUpload: True
+ dmi.bios.date: 11/25/2019
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: N23ET69W (1.44 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20KHCTO1WW
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0J40709 WIN
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
+ dmi.product.family: ThinkPad X1 Carbon 6th
+ dmi.product.name: 20KHCTO1WW
+ dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
+ dmi.product.version: ThinkPad X1 Carbon 6th
+ dmi.sys.vendor: LENOVO

** Attachment added: "AlsaDevices.txt"
   
https://bugs.launchpad.net/bugs/1861359/+attachment/5324031/+files/AlsaDevices.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/1861359

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generi

[Kernel-packages] [Bug 1861359] AplayDevices.txt

2020-01-29 Thread Seth Arnold
apport information

** Attachment added: "AplayDevices.txt"
   
https://bugs.launchpad.net/bugs/1861359/+attachment/5324032/+files/AplayDevices.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/1861359

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubunt

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

2020-01-29 Thread Seth Arnold
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1861359/+attachment/5324041/+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/1861359

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubunt

[Kernel-packages] [Bug 1861359] Card0.Amixer.values.txt

2020-01-29 Thread Seth Arnold
apport information

** Attachment added: "Card0.Amixer.values.txt"
   
https://bugs.launchpad.net/bugs/1861359/+attachment/5324037/+files/Card0.Amixer.values.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/1861359

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  Distro

[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

2020-01-29 Thread Seth Arnold
apport information

** Description changed:

  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty seconds.
  No mouse movement, no keyboard input, the screen output does not change.
  
  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.
  
  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)
  
  Thanks
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
+ --- 
+ ProblemType: Bug
+ AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
+ ApportVersion: 2.20.11-0ubuntu16
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  sarnold2734 F pulseaudio
+  /dev/snd/controlC1:  sarnold2734 F pulseaudio
+ Card0.Amixer.info:
+  Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
+Mixer name : 'Realtek ALC285'
+Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
+Controls  : 53
+Simple ctrls  : 15
+ Card1.Amixer.info:
+  Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
+Mixer name : 'USB Mixer'
+Components : 'USB17ef:306f'
+Controls  : 9
+Simple ctrls  : 4
+ DistroRelease: Ubuntu 20.04
+ HibernationDevice: RESUME=none
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
+ MachineType: LENOVO 20KHCTO1WW
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=rxvt-unicode-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/

[Kernel-packages] [Bug 1861359] Card0.Codecs.codec.0.txt

2020-01-29 Thread Seth Arnold
apport information

** Attachment added: "Card0.Codecs.codec.0.txt"
   
https://bugs.launchpad.net/bugs/1861359/+attachment/5324038/+files/Card0.Codecs.codec.0.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/1861359

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  Dist

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

2020-01-29 Thread Seth Arnold
apport information

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

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

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  Hiber

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

2020-01-29 Thread Seth Arnold
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1861359/+attachment/5324042/+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/1861359

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  Hiber

[Kernel-packages] [Bug 1861359] Card0.Codecs.codec.2.txt

2020-01-29 Thread Seth Arnold
apport information

** Attachment added: "Card0.Codecs.codec.2.txt"
   
https://bugs.launchpad.net/bugs/1861359/+attachment/5324039/+files/Card0.Codecs.codec.2.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/1861359

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  Dist

[Kernel-packages] [Bug 1861359] ArecordDevices.txt

2020-01-29 Thread Seth Arnold
apport information

** Attachment added: "ArecordDevices.txt"
   
https://bugs.launchpad.net/bugs/1861359/+attachment/5324035/+files/ArecordDevices.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/1861359

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: U

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

2020-01-29 Thread Seth Arnold
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1861359/+attachment/5324036/+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/1861359

Title:
  swap storms kills interactive use

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  Hiberna

  1   2   3   4   5   6   7   >