[Kernel-packages] [Bug 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
This bug was fixed in the package linux - 4.4.0-63.84
---
linux (4.4.0-63.84) xenial; urgency=low
[ Thadeu Lima de Souza Cascardo ]
* Release Tracking Bug
- LP: #1660704
* Backport Dirty COW patch to prevent wineserver freeze (LP: #1658270)
- SAUCE: mm: Respect FOLL_FORCE/FOLL_COW for thp
* Kdump through NMI SMP and single core not working on Ubuntu16.10
(LP: #1630924)
- x86/hyperv: Handle unknown NMIs on one CPU when unknown_nmi_panic
- SAUCE: hv: don't reset hv_context.tsc_page on crash
* [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on Acer
Chromebook R11 (LP: #1630238)
- [Config] CONFIG_PINCTRL_CHERRYVIEW=y
* Call trace when testing fstat stressor on ppc64el with virtual keyboard and
mouse present (LP: #1652132)
- SAUCE: HID: usbhid: Quirk a AMI virtual mouse and keyboard with
ALWAYS_POLL
* VLAN SR-IOV regression for IXGBE driver (LP: #1658491)
- ixgbe: Force VLNCTRL.VFE to be set in all VMDq paths
* "Out of memory" errors after upgrade to 4.4.0-59 (LP: #1655842)
- mm, page_alloc: convert alloc_flags to unsigned
- mm, compaction: change COMPACT_ constants into enum
- mm, compaction: distinguish COMPACT_DEFERRED from COMPACT_SKIPPED
- mm, compaction: simplify __alloc_pages_direct_compact feedback interface
- mm, compaction: distinguish between full and partial COMPACT_COMPLETE
- mm, compaction: abstract compaction feedback to helpers
- mm, oom: protect !costly allocations some more
- mm: consider compaction feedback also for costly allocation
- mm, oom, compaction: prevent from should_compact_retry looping for ever
for
costly orders
- mm, oom: protect !costly allocations some more for !CONFIG_COMPACTION
- mm, oom: prevent premature OOM killer invocation for high order request
* Backport 3 patches to fix bugs with AIX clients using IBMVSCSI Target Driver
(LP: #1657194)
- SAUCE: ibmvscsis: Fix max transfer length
- SAUCE: ibmvscsis: fix sleeping in interrupt context
- SAUCE: ibmvscsis: Fix srp_transfer_data fail return code
* NVMe: adapter is missing after abnormal shutdown followed by quick reboot,
quirk needed (LP: #1656913)
- nvme: apply DELAY_BEFORE_CHK_RDY quirk at probe time too
* Ubuntu 16.10 KVM SRIOV: if enable sriov while ping flood is running ping
will stop working (LP: #1625318)
- PCI: Do any VF BAR updates before enabling the BARs
- PCI: Ignore BAR updates on virtual functions
- PCI: Update BARs using property bits appropriate for type
- PCI: Separate VF BAR updates from standard BAR updates
- PCI: Don't update VF BARs while VF memory space is enabled
- PCI: Remove pci_resource_bar() and pci_iov_resource_bar()
- PCI: Decouple IORESOURCE_ROM_ENABLE and PCI_ROM_ADDRESS_ENABLE
- PCI: Add comments about ROM BAR updating
* Linux rtc self test fails in a VM under xenial (LP: #1649718)
- kvm: x86: Convert ioapic->rtc_status.dest_map to a struct
- kvm: x86: Track irq vectors in ioapic->rtc_status.dest_map
- kvm: x86: Check dest_map->vector to match eoi signals for rtc
* Xenial update to v4.4.44 stable release (LP: #1658091)
- Input: xpad - use correct product id for x360w controllers
- Input: i8042 - add Pegatron touchpad to noloop table
- selftests: do not require bash to run netsocktests testcase
- selftests: do not require bash for the generated test
- mm: fix devm_memremap_pages crash, use mem_hotplug_{begin, done}
- ocfs2: fix crash caused by stale lvb with fsdlm plugin
- mm/hugetlb.c: fix reservation race when freeing surplus pages
- KVM: x86: fix emulation of "MOV SS, null selector"
- KVM: eventfd: fix NULL deref irqbypass consumer
- jump_labels: API for flushing deferred jump label updates
- KVM: x86: flush pending lapic jump label updates on module unload
- KVM: x86: add Align16 instruction flag
- KVM: x86: add asm_safe wrapper
- KVM: x86: emulate FXSAVE and FXRSTOR
- KVM: x86: Introduce segmented_write_std
- nl80211: fix sched scan netlink socket owner destruction
- USB: serial: kl5kusb105: fix line-state error handling
- USB: serial: ch341: fix initial modem-control state
- USB: serial: ch341: fix open error handling
- USB: serial: ch341: fix control-message error handling
- USB: serial: ch341: fix open and resume after B0
- Input: elants_i2c - avoid divide by 0 errors on bad touchscreen data
- i2c: print correct device invalid address
- i2c: fix kernel memory disclosure in dev interface
- xhci: fix deadlock at host remove by running watchdog correctly
- vme: Fix wrong pointer utilization in ca91cx42_slave_get
- mnt: Protect the mountpoint hashtable with mount_lock
- tty/serial: atmel_serial: BUG: stop DMA from transmitting in stop_tx
- sysrq: attach sysrq handler correctly for 32-bit kernel
- sysctl: Drop reference added by grab_header in
[Kernel-packages] [Bug 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
This bug was fixed in the package linux - 4.8.0-38.41 --- linux (4.8.0-38.41) yakkety; urgency=low [ Thadeu Lima de Souza Cascardo ] * Release Tracking Bug - LP: #1661232 * Backport Dirty COW patch to prevent wineserver freeze (LP: #1658270) - SAUCE: mm: Respect FOLL_FORCE/FOLL_COW for thp * Kdump through NMI SMP and single core not working on Ubuntu16.10 (LP: #1630924) - x86/hyperv: Handle unknown NMIs on one CPU when unknown_nmi_panic - SAUCE: hv: don't reset hv_context.tsc_page on crash * Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present (LP: #1652132) - HID: usbhid: Quirk a AMI virtual mouse and keyboard with ALWAYS_POLL * regression in linux-libc-dev in yakkety: C++ style comments are not allowed in ISO C90 (LP: #1659654) - generic syscalls: kill cruft from removed pkey syscalls * [16.04.2] POWER9 patches on top of 4.8 (LP: #1650263) - powerpc/book3s: Add a cpu table entry for different POWER9 revs - powerpc/mm/radix: Use different RTS encoding for different POWER9 revs - powerpc/mm/radix: Use different pte update sequence for different POWER9 revs - powerpc/mm: Update the HID bit when switching from radix to hash - powerpc/64/kexec: NULL check "clear_all" in kexec_sequence - powerpc/64/kexec: Fix MMU cleanup on radix - powerpc/mm: Add radix flush all with IS=3 - powerpc/64/kexec: Copy image with MMU off when possible - powerpc/64: Simplify adaptation to new ISA v3.00 HPTE format - powerpc/mm/radix: Invalidate ERAT on tlbiel for POWER9 DD1 - powerpc/mm: Fix missing update of HID register on secondary CPUs - powerpc/64: Add some more SPRs and SPR bits for POWER9 - powerpc/64: Provide functions for accessing POWER9 partition table - powerpc/powernv: Define real-mode versions of OPAL XICS accessors - powerpc/64: Define new ISA v3.00 logical PVR value and PCR register value - mm: update mmu_gather range correctly - mm/hugetlb: add tlb_remove_hugetlb_entry for handling hugetlb pages - mm: add tlb_remove_check_page_size_change to track page size change - powerpc: Revert Load Monitor Register Support - powerpc/mm: Correct process and partition table max size - powernv: Clear SPRN_PSSCR when a POWER9 CPU comes online - powerpc/mm/radix: Setup AMOR in HV mode to allow key 0 - powerpc/mm: Detect instruction fetch denied and report - powerpc/mm/radix: Prevent kernel execution of user space - powerpc/mm: Rename hugetlb-radix.h to hugetlb.h - powerpc/mm/hugetlb: Handle hugepage size supported by hash config - powerpc/mm: Introduce _PAGE_LARGE software pte bits - powerpc/mm: Add radix__tlb_flush_pte_p9_dd1() - powerpc/mm: update radix__ptep_set_access_flag to not do full mm tlb flush - powerpc/mm: update radix__pte_update to not do full mm tlb flush - powerpc/mm: Batch tlb flush when invalidating pte entries - powerpc/sparse: Make a bunch of things static - powerpc/perf: factor out the event format field - powerpc/perf: update attribute_group data structure - powerpc/perf: power9 raw event format encoding - powerpc/perf: macros for power9 format encoding - KVM: PPC: Book3S: Don't crash if irqfd used with no in-kernel XICS emulation - KVM: PPC: Implement kvm_arch_intc_initialized() for PPC - KVM: PPC: Book3S HV: Move struct kvmppc_vcore from kvm_host.h to kvm_book3s.h - KVM: PPC: Book3S HV: Change vcore element runnable_threads from linked-list to array - KVM: Export kvm module parameter variables - KVM: PPC: Book3S HV: Implement halt polling - KVM: Add provisioning for ulong vm stats and u64 vcpu stats - KVM: PPC: Implement existing and add new halt polling vcpu stats - powerpc/mm: Speed up computation of base and actual page size for a HPTE - powerpc: Add simple cache inhibited MMIO accessors - KVM: PPC: Book3S HV: Convert kvmppc_read_intr to a C function - KVM: PPC: select IRQ_BYPASS_MANAGER - KVM: PPC: Book3S HV: Introduce kvmppc_passthru_irqmap - powerpc/powernv: Provide facilities for EOI, usable from real mode - KVM: PPC: Book3S HV: Enable IRQ bypass - KVM: PPC: Book3S HV: Handle passthrough interrupts in guest - KVM: PPC: Book3S HV: Complete passthrough interrupt in host - KVM: PPC: Book3S HV: Dump irqmap in debugfs - KVM: PPC: Book3S HV: Tunable to disable KVM IRQ bypass - KVM: PPC: Book3S HV: Update irq stats for IRQs handled in real mode - KVM: PPC: Book3S HV: Set server for passed-through interrupts - KVM: PPC: Book3S HV: Counters for passthrough IRQ stats - KVM: PPC: e500: Use kmalloc_array() in kvm_vcpu_ioctl_config_tlb() - KVM: PPC: e500: Less function calls in kvm_vcpu_ioctl_config_tlb() after error detection - KVM: PPC: e500: Delete an unnecessary initialisation in kvm_vcpu_ioctl_config_tlb() - KVM: PPC: e500:
[Kernel-packages] [Bug 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
Tested with Yakkety 4.8.0-38-generic #41-Ubuntu, no failures ** Tags removed: verification-needed-yakkety ** Tags added: verification-done-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Bug description: == SRU REQUEST [Xenial, Yakkety, Zesty] == Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. == Fix == Quirking the Virtual AMI keyboard and mouse with ALWAYS_POLL addresses the issue. The patch has been accepted into the upstream queue for 4.11, see http://www.spinics.net/lists/linux-usb/msg152977.html == Test Case == run 10 times: sudo stress-ng --fstat 128 -t 60 -v Without the fix, it will hang, with the fix there is no hang or USB error messages. == Regression Potential == This only quirks a specific AMI virtual keyboard and mouse into a poll mode, so it touches one device. Futhermore, the poll mode shouldn't affect operation; it just makes the URB handling less efficient. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1652132/+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 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
Tested with Xenial 4.4.0-63-generic #84-Ubuntu, no failures. ** 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 linux in Ubuntu. https://bugs.launchpad.net/bugs/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Bug description: == SRU REQUEST [Xenial, Yakkety, Zesty] == Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. == Fix == Quirking the Virtual AMI keyboard and mouse with ALWAYS_POLL addresses the issue. The patch has been accepted into the upstream queue for 4.11, see http://www.spinics.net/lists/linux-usb/msg152977.html == Test Case == run 10 times: sudo stress-ng --fstat 128 -t 60 -v Without the fix, it will hang, with the fix there is no hang or USB error messages. == Regression Potential == This only quirks a specific AMI virtual keyboard and mouse into a poll mode, so it touches one device. Futhermore, the poll mode shouldn't affect operation; it just makes the URB handling less efficient. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1652132/+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 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed- yakkety'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Bug description: == SRU REQUEST [Xenial, Yakkety, Zesty] == Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. == Fix == Quirking the Virtual AMI keyboard and mouse with ALWAYS_POLL addresses the issue. The patch has been accepted into the upstream queue for 4.11, see http://www.spinics.net/lists/linux-usb/msg152977.html == Test Case == run 10 times: sudo stress-ng --fstat 128 -t 60 -v Without the fix, it will hang, with the fix there is no hang or USB error messages. == Regression Potential == This only quirks a specific AMI virtual keyboard and mouse into a poll mode, so it touches one device. Futhermore, the poll mode shouldn't affect operation; it just makes the URB handling less efficient. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1652132/+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 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial ** Tags added: verification-needed-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Bug description: == SRU REQUEST [Xenial, Yakkety, Zesty] == Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. == Fix == Quirking the Virtual AMI keyboard and mouse with ALWAYS_POLL addresses the issue. The patch has been accepted into the upstream queue for 4.11, see http://www.spinics.net/lists/linux-usb/msg152977.html == Test Case == run 10 times: sudo stress-ng --fstat 128 -t 60 -v Without the fix, it will hang, with the fix there is no hang or USB error messages. == Regression Potential == This only quirks a specific AMI virtual keyboard and mouse into a poll mode, so it touches one device. Futhermore, the poll mode shouldn't affect operation; it just makes the URB handling less efficient. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1652132/+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 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
Note, the above comment was validated on a Fujitsu CX1640 Xeon Phi system with Xenial and the stock ubuntu kernel: Linux cx1640-1 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Bug description: == SRU REQUEST [Xenial, Yakkety, Zesty] == Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. == Fix == Quirking the Virtual AMI keyboard and mouse with ALWAYS_POLL addresses the issue. The patch has been accepted into the upstream queue for 4.11, see http://www.spinics.net/lists/linux-usb/msg152977.html == Test Case == run 10 times: sudo stress-ng --fstat 128 -t 60 -v Without the fix, it will hang, with the fix there is no hang or USB error messages. == Regression Potential == This only quirks a specific AMI virtual keyboard and mouse into a poll mode, so it touches one device. Futhermore, the poll mode shouldn't affect operation; it just makes the URB handling less efficient. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1652132/+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 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
FWIW, I have run this on a Xeon Phi system and not reproduced the failure using stress-ng 0.07.16 (built in our PPA for Xenial). This appears to have an AMI fake keyboard and mouse as the Power system that fails does. Bus 003 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x046b American Megatrends, Inc. idProduct 0xff10 Virtual Keyboard and Mouse bcdDevice1.00 iManufacturer 1 iProduct2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 59 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 1 Keyboard iInterface 3 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.10 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 65 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 4 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.10 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 63 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 and ubuntu@cx1640-1:~$ lsusb Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 003 Device 002: ID 05af:1012 Jing-Mold Enterprise Co., Ltd Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub This appears to be the same virtual HID device that the failing power system has. Though as this is a Xeon Phi system, not an OpenPower box, do not treat this as conclusive that the bug is fixed for the failing system. The summary says to run fstat 10 times, so I ran it in a loop like so and did not experience any lockups: for x in `seq 1 10`; do sudo stress-ng --fstat 128 -t 60 -v; done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Bug description: == SRU REQUEST [Xenial, Yakkety, Zesty] == Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on
[Kernel-packages] [Bug 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Bug description: == SRU REQUEST [Xenial, Yakkety, Zesty] == Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. == Fix == Quirking the Virtual AMI keyboard and mouse with ALWAYS_POLL addresses the issue. The patch has been accepted into the upstream queue for 4.11, see http://www.spinics.net/lists/linux-usb/msg152977.html == Test Case == run 10 times: sudo stress-ng --fstat 128 -t 60 -v Without the fix, it will hang, with the fix there is no hang or USB error messages. == Regression Potential == This only quirks a specific AMI virtual keyboard and mouse into a poll mode, so it touches one device. Futhermore, the poll mode shouldn't affect operation; it just makes the URB handling less efficient. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1652132/+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 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
** Description changed: + == SRU REQUEST [Xenial, Yakkety, Zesty] == + Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. + + == Fix == + + Quirking the Virtual AMI keyboard and mouse with ALWAYS_POLL addresses + the issue. The patch has been accepted into the upstream queue for + 4.11. + + == Test Case == + + run 10 times: + sudo stress-ng --fstat 128 -t 60 -v + + Without the fix, it will hang, with the fix there is no hang or USB + error messages. + + == Regression Potential == + + This only quirks a specific AMI virtual keyboard and mouse into a poll + mode, so it touches one device. Futhermore, the poll mode shouldn't + affect operation; it just makes the URB handling less efficient. ** Description changed: == SRU REQUEST [Xenial, Yakkety, Zesty] == Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. == Fix == Quirking the Virtual AMI keyboard and mouse with ALWAYS_POLL addresses the issue. The patch has been accepted into the upstream queue for - 4.11. + 4.11, see http://www.spinics.net/lists/linux-usb/msg152977.html == Test Case == run 10 times: sudo stress-ng --fstat 128 -t 60 -v Without the fix, it will hang, with the fix there is no hang or USB error messages. == Regression Potential == This only quirks a specific AMI virtual keyboard and mouse into a poll mode, so it touches one device. Futhermore, the poll mode shouldn't affect operation; it just makes the URB handling less efficient. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Bug description: == SRU REQUEST [Xenial, Yakkety, Zesty] == Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. == Fix == Quirking the Virtual AMI keyboard and mouse with ALWAYS_POLL addresses the issue. The patch has been accepted into the upstream queue for 4.11, see http://www.spinics.net/lists/linux-usb/msg152977.html == Test Case == run 10 times: sudo stress-ng --fstat 128 -t 60 -v Without the fix, it will hang, with the fix there is no hang or USB error messages. == Regression Potential == This only quirks a specific AMI virtual keyboard and mouse into a poll mode, so it touches one device. Futhermore, the poll mode shouldn't affect operation; it just makes the URB handling less efficient. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1652132/+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 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
Going to quirk this with polling to avoid the issue with the urb kill. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Bug description: Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1652132/+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 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
Checked this right through 4.0 to 4.10-rc5, it can be triggered with any of these kernels with enough run time. ** Bug watch added: Linux Kernel Bug Tracker #193301 http://bugzilla.kernel.org/show_bug.cgi?id=193301 ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=193301 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Bug description: Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1652132/+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 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
OK, so this is annoying race condition, so bisecting it has been causing me some pain today. It turns out that 4.10-rc4 seems OK, whereas 4.10-rc3 and before will hang after two or 3 iterations of my stress test. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in linux package in Ubuntu: In Progress Bug description: Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652132/+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 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
4.9 fails, 4.10-rc1 OK, bisecting on that -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in linux package in Ubuntu: In Progress Bug description: Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652132/+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 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
Can't break the kernel with 4.10-rc4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in linux package in Ubuntu: In Progress Bug description: Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652132/+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 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
Fails on mainline 4.9 too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in linux package in Ubuntu: In Progress Bug description: Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652132/+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 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
Hang seems to occur when on a race when fstat'ing /dev/psaux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in linux package in Ubuntu: In Progress Bug description: Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652132/+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 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
OK, I've got access to the machine and can easily reproduce this. This is not a stress-ng bug per-se, it's a locking issue so I'll remove stress-ng from the bug. ** No longer affects: stress-ng ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in linux package in Ubuntu: In Progress Bug description: Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652132/+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 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
This test has been run dozens of times across multiple machines and deployments and reboots. It is completely reproducible. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in Stress-ng: New Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1652132/+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 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
It looks to me that a reset on a USB device from an atomic context occurred, causing __usb_queue_reset_device to be executed from a worker thread but this got hung for some reason. The fstat stressor was being run at the time, and that also locks up. So my current hunch is that this may have been triggered by a USB device issue and then it snarls up causing subsequent hangs. Can this test be re-run to see if this fails again. My expectation is that it won't because its not a stress-ng specific triggered 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/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in Stress-ng: New Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1652132/+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 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
FYI, Added stress-ng task as a specific test case in that tool is exposing this issue. Just want to be sure this is not a test tool issue instead of a legit kernel 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/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in Stress-ng: New Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1652132/+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 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: stress-ng Assignee: (unassigned) => Colin Ian King (colin-king) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in Stress-ng: New Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1652132/+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 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
apport-collect is not functioning on this server: The collected information can be sent to the developers to improve the application. This might take a few minutes. tar: Removing leading `/' from member names tar: Removing leading `/' from member names tar: Removing leading `/' from member names tar: /var/log/opal-elog: Cannot stat: No such file or directory tar: Exiting with failure status due to previous errors ...dpkg-query: no packages found matching linux . The dots go on forever -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in Stress-ng: New Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1652132/+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 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
** 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/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in Stress-ng: New Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1652132/+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 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
** Summary changed: - Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse + Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present ** Tags added: blocks-hwcert-server -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652132/+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
