[Kernel-packages] [Bug 1712481] Re: HID: multitouch: Support ALPS PTP Stick and Touchpad devices

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.12.0-13.14

---
linux (4.12.0-13.14) artful; urgency=low

  * linux: 4.12.0-13.14 -proposed tracker (LP: #1714687)

  * vhost guest network randomly drops under stress (kvm) (LP: #1711251)
- Revert "vhost: cache used event for better performance"

  * EDAC sbridge: Failed to register device with error -22. (LP: #1714112)
- [Config] CONFIG_EDAC_GHES=n

  * Artful update to v4.12.10 stable release (LP: #1714525)
- sparc64: remove unnecessary log message
- bonding: require speed/duplex only for 802.3ad, alb and tlb
- bonding: ratelimit failed speed/duplex update warning
- af_key: do not use GFP_KERNEL in atomic contexts
- dccp: purge write queue in dccp_destroy_sock()
- dccp: defer ccid_hc_tx_delete() at dismantle time
- ipv4: fix NULL dereference in free_fib_info_rcu()
- net_sched/sfq: update hierarchical backlog when drop packet
- net_sched: remove warning from qdisc_hash_add
- bpf: fix bpf_trace_printk on 32 bit archs
- net: igmp: Use ingress interface rather than vrf device
- openvswitch: fix skb_panic due to the incorrect actions attrlen
- ptr_ring: use kmalloc_array()
- ipv4: better IP_MAX_MTU enforcement
- nfp: fix infinite loop on umapping cleanup
- tun: handle register_netdevice() failures properly
- sctp: fully initialize the IPv6 address in sctp_v6_to_addr()
- tipc: fix use-after-free
- ipv6: reset fn->rr_ptr when replacing route
- ipv6: repair fib6 tree in failure case
- tcp: when rearming RTO, if RTO time is in past then fire RTO ASAP
- net/mlx4_core: Enable 4K UAR if SRIOV module parameter is not enabled
- irda: do not leak initialized list.dev to userspace
- net: sched: fix NULL pointer dereference when action calls some targets
- net_sched: fix order of queue length updates in qdisc_replace()
- bpf, verifier: add additional patterns to evaluate_reg_imm_alu
- bpf: fix mixed signed/unsigned derived min/max value bounds
- bpf/verifier: fix min/max handling in BPF_SUB
- Input: trackpoint - add new trackpoint firmware ID
- Input: elan_i2c - add ELAN0602 ACPI ID to support Lenovo Yoga310
- Input: ALPS - fix two-finger scroll breakage in right side on ALPS 
touchpad
- KVM: s390: sthyi: fix sthyi inline assembly
- KVM: s390: sthyi: fix specification exception detection
- KVM: x86: simplify handling of PKRU
- KVM, pkeys: do not use PKRU value in vcpu->arch.guest_fpu.state
- KVM: x86: block guest protection keys unless the host has them enabled
- ALSA: usb-audio: Add delay quirk for H650e/Jabra 550a USB headsets
- ALSA: core: Fix unexpected error at replacing user TLV
- ALSA: hda - Add stereo mic quirk for Lenovo G50-70 (17aa:3978)
- ALSA: firewire: fix NULL pointer dereference when releasing uninitialized
  data of iso-resource
- ALSA: firewire-motu: destroy stream data surely at failure of card
  initialization
- ARCv2: SLC: Make sure busy bit is set properly for region ops
- ARCv2: PAE40: Explicitly set MSB counterpart of SLC region ops addresses
- ARCv2: PAE40: set MSB even if !CONFIG_ARC_HAS_PAE40 but PAE exists in SoC
- PM/hibernate: touch NMI watchdog when creating snapshot
- mm, shmem: fix handling /sys/kernel/mm/transparent_hugepage/shmem_enabled
- dax: fix deadlock due to misaligned PMD faults
- i2c: designware: Fix system suspend
- mm/madvise.c: fix freeing of locked page with MADV_FREE
- fork: fix incorrect fput of ->exe_file causing use-after-free
- mm/memblock.c: reversed logic in memblock_discard()
- arm64: fpsimd: Prevent registers leaking across exec
- drm: Fix framebuffer leak
- drm: Release driver tracking before making the object available again
- drm/sun4i: Implement drm_driver lastclose to restore fbdev console
- drm/atomic: Handle -EDEADLK with out-fences correctly
- drm/atomic: If the atomic check fails, return its value first
- drm/i915/vbt: ignore extraneous child devices for a port
- drm/i915/gvt: Fix the kernel null pointer error
- Revert "drm/amdgpu: fix vblank_time when displays are off"
- ACPI: device property: Fix node lookup in 
acpi_graph_get_child_prop_value()
- tracing: Call clear_boot_tracer() at lateinit_sync
- tracing: Missing error code in tracer_alloc_buffers()
- tracing: Fix kmemleak in tracing_map_array_free()
- tracing: Fix freeing of filter in create_filter() when set_str is false
- RDMA/uverbs: Initialize cq_context appropriately
- kbuild: linker script do not match C names unless
  LD_DEAD_CODE_DATA_ELIMINATION is configured
- cifs: Fix df output for users with quota limits
- cifs: return ENAMETOOLONG for overlong names in cifs_open()/cifs_lookup()
- nfsd: Limit end of page list when decoding NFSv4 WRITE
- ring-buffer: Have ring_buffer_alloc_read_page() return error on offline 
CPU
- virtio_pci: fix 

[Kernel-packages] [Bug 1713106] Re: Artful update to v4.12.9 stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.12.0-13.14

---
linux (4.12.0-13.14) artful; urgency=low

  * linux: 4.12.0-13.14 -proposed tracker (LP: #1714687)

  * vhost guest network randomly drops under stress (kvm) (LP: #1711251)
- Revert "vhost: cache used event for better performance"

  * EDAC sbridge: Failed to register device with error -22. (LP: #1714112)
- [Config] CONFIG_EDAC_GHES=n

  * Artful update to v4.12.10 stable release (LP: #1714525)
- sparc64: remove unnecessary log message
- bonding: require speed/duplex only for 802.3ad, alb and tlb
- bonding: ratelimit failed speed/duplex update warning
- af_key: do not use GFP_KERNEL in atomic contexts
- dccp: purge write queue in dccp_destroy_sock()
- dccp: defer ccid_hc_tx_delete() at dismantle time
- ipv4: fix NULL dereference in free_fib_info_rcu()
- net_sched/sfq: update hierarchical backlog when drop packet
- net_sched: remove warning from qdisc_hash_add
- bpf: fix bpf_trace_printk on 32 bit archs
- net: igmp: Use ingress interface rather than vrf device
- openvswitch: fix skb_panic due to the incorrect actions attrlen
- ptr_ring: use kmalloc_array()
- ipv4: better IP_MAX_MTU enforcement
- nfp: fix infinite loop on umapping cleanup
- tun: handle register_netdevice() failures properly
- sctp: fully initialize the IPv6 address in sctp_v6_to_addr()
- tipc: fix use-after-free
- ipv6: reset fn->rr_ptr when replacing route
- ipv6: repair fib6 tree in failure case
- tcp: when rearming RTO, if RTO time is in past then fire RTO ASAP
- net/mlx4_core: Enable 4K UAR if SRIOV module parameter is not enabled
- irda: do not leak initialized list.dev to userspace
- net: sched: fix NULL pointer dereference when action calls some targets
- net_sched: fix order of queue length updates in qdisc_replace()
- bpf, verifier: add additional patterns to evaluate_reg_imm_alu
- bpf: fix mixed signed/unsigned derived min/max value bounds
- bpf/verifier: fix min/max handling in BPF_SUB
- Input: trackpoint - add new trackpoint firmware ID
- Input: elan_i2c - add ELAN0602 ACPI ID to support Lenovo Yoga310
- Input: ALPS - fix two-finger scroll breakage in right side on ALPS 
touchpad
- KVM: s390: sthyi: fix sthyi inline assembly
- KVM: s390: sthyi: fix specification exception detection
- KVM: x86: simplify handling of PKRU
- KVM, pkeys: do not use PKRU value in vcpu->arch.guest_fpu.state
- KVM: x86: block guest protection keys unless the host has them enabled
- ALSA: usb-audio: Add delay quirk for H650e/Jabra 550a USB headsets
- ALSA: core: Fix unexpected error at replacing user TLV
- ALSA: hda - Add stereo mic quirk for Lenovo G50-70 (17aa:3978)
- ALSA: firewire: fix NULL pointer dereference when releasing uninitialized
  data of iso-resource
- ALSA: firewire-motu: destroy stream data surely at failure of card
  initialization
- ARCv2: SLC: Make sure busy bit is set properly for region ops
- ARCv2: PAE40: Explicitly set MSB counterpart of SLC region ops addresses
- ARCv2: PAE40: set MSB even if !CONFIG_ARC_HAS_PAE40 but PAE exists in SoC
- PM/hibernate: touch NMI watchdog when creating snapshot
- mm, shmem: fix handling /sys/kernel/mm/transparent_hugepage/shmem_enabled
- dax: fix deadlock due to misaligned PMD faults
- i2c: designware: Fix system suspend
- mm/madvise.c: fix freeing of locked page with MADV_FREE
- fork: fix incorrect fput of ->exe_file causing use-after-free
- mm/memblock.c: reversed logic in memblock_discard()
- arm64: fpsimd: Prevent registers leaking across exec
- drm: Fix framebuffer leak
- drm: Release driver tracking before making the object available again
- drm/sun4i: Implement drm_driver lastclose to restore fbdev console
- drm/atomic: Handle -EDEADLK with out-fences correctly
- drm/atomic: If the atomic check fails, return its value first
- drm/i915/vbt: ignore extraneous child devices for a port
- drm/i915/gvt: Fix the kernel null pointer error
- Revert "drm/amdgpu: fix vblank_time when displays are off"
- ACPI: device property: Fix node lookup in 
acpi_graph_get_child_prop_value()
- tracing: Call clear_boot_tracer() at lateinit_sync
- tracing: Missing error code in tracer_alloc_buffers()
- tracing: Fix kmemleak in tracing_map_array_free()
- tracing: Fix freeing of filter in create_filter() when set_str is false
- RDMA/uverbs: Initialize cq_context appropriately
- kbuild: linker script do not match C names unless
  LD_DEAD_CODE_DATA_ELIMINATION is configured
- cifs: Fix df output for users with quota limits
- cifs: return ENAMETOOLONG for overlong names in cifs_open()/cifs_lookup()
- nfsd: Limit end of page list when decoding NFSv4 WRITE
- ring-buffer: Have ring_buffer_alloc_read_page() return error on offline 
CPU
- virtio_pci: fix 

[Kernel-packages] [Bug 1714525] Re: Artful update to v4.12.10 stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.12.0-13.14

---
linux (4.12.0-13.14) artful; urgency=low

  * linux: 4.12.0-13.14 -proposed tracker (LP: #1714687)

  * vhost guest network randomly drops under stress (kvm) (LP: #1711251)
- Revert "vhost: cache used event for better performance"

  * EDAC sbridge: Failed to register device with error -22. (LP: #1714112)
- [Config] CONFIG_EDAC_GHES=n

  * Artful update to v4.12.10 stable release (LP: #1714525)
- sparc64: remove unnecessary log message
- bonding: require speed/duplex only for 802.3ad, alb and tlb
- bonding: ratelimit failed speed/duplex update warning
- af_key: do not use GFP_KERNEL in atomic contexts
- dccp: purge write queue in dccp_destroy_sock()
- dccp: defer ccid_hc_tx_delete() at dismantle time
- ipv4: fix NULL dereference in free_fib_info_rcu()
- net_sched/sfq: update hierarchical backlog when drop packet
- net_sched: remove warning from qdisc_hash_add
- bpf: fix bpf_trace_printk on 32 bit archs
- net: igmp: Use ingress interface rather than vrf device
- openvswitch: fix skb_panic due to the incorrect actions attrlen
- ptr_ring: use kmalloc_array()
- ipv4: better IP_MAX_MTU enforcement
- nfp: fix infinite loop on umapping cleanup
- tun: handle register_netdevice() failures properly
- sctp: fully initialize the IPv6 address in sctp_v6_to_addr()
- tipc: fix use-after-free
- ipv6: reset fn->rr_ptr when replacing route
- ipv6: repair fib6 tree in failure case
- tcp: when rearming RTO, if RTO time is in past then fire RTO ASAP
- net/mlx4_core: Enable 4K UAR if SRIOV module parameter is not enabled
- irda: do not leak initialized list.dev to userspace
- net: sched: fix NULL pointer dereference when action calls some targets
- net_sched: fix order of queue length updates in qdisc_replace()
- bpf, verifier: add additional patterns to evaluate_reg_imm_alu
- bpf: fix mixed signed/unsigned derived min/max value bounds
- bpf/verifier: fix min/max handling in BPF_SUB
- Input: trackpoint - add new trackpoint firmware ID
- Input: elan_i2c - add ELAN0602 ACPI ID to support Lenovo Yoga310
- Input: ALPS - fix two-finger scroll breakage in right side on ALPS 
touchpad
- KVM: s390: sthyi: fix sthyi inline assembly
- KVM: s390: sthyi: fix specification exception detection
- KVM: x86: simplify handling of PKRU
- KVM, pkeys: do not use PKRU value in vcpu->arch.guest_fpu.state
- KVM: x86: block guest protection keys unless the host has them enabled
- ALSA: usb-audio: Add delay quirk for H650e/Jabra 550a USB headsets
- ALSA: core: Fix unexpected error at replacing user TLV
- ALSA: hda - Add stereo mic quirk for Lenovo G50-70 (17aa:3978)
- ALSA: firewire: fix NULL pointer dereference when releasing uninitialized
  data of iso-resource
- ALSA: firewire-motu: destroy stream data surely at failure of card
  initialization
- ARCv2: SLC: Make sure busy bit is set properly for region ops
- ARCv2: PAE40: Explicitly set MSB counterpart of SLC region ops addresses
- ARCv2: PAE40: set MSB even if !CONFIG_ARC_HAS_PAE40 but PAE exists in SoC
- PM/hibernate: touch NMI watchdog when creating snapshot
- mm, shmem: fix handling /sys/kernel/mm/transparent_hugepage/shmem_enabled
- dax: fix deadlock due to misaligned PMD faults
- i2c: designware: Fix system suspend
- mm/madvise.c: fix freeing of locked page with MADV_FREE
- fork: fix incorrect fput of ->exe_file causing use-after-free
- mm/memblock.c: reversed logic in memblock_discard()
- arm64: fpsimd: Prevent registers leaking across exec
- drm: Fix framebuffer leak
- drm: Release driver tracking before making the object available again
- drm/sun4i: Implement drm_driver lastclose to restore fbdev console
- drm/atomic: Handle -EDEADLK with out-fences correctly
- drm/atomic: If the atomic check fails, return its value first
- drm/i915/vbt: ignore extraneous child devices for a port
- drm/i915/gvt: Fix the kernel null pointer error
- Revert "drm/amdgpu: fix vblank_time when displays are off"
- ACPI: device property: Fix node lookup in 
acpi_graph_get_child_prop_value()
- tracing: Call clear_boot_tracer() at lateinit_sync
- tracing: Missing error code in tracer_alloc_buffers()
- tracing: Fix kmemleak in tracing_map_array_free()
- tracing: Fix freeing of filter in create_filter() when set_str is false
- RDMA/uverbs: Initialize cq_context appropriately
- kbuild: linker script do not match C names unless
  LD_DEAD_CODE_DATA_ELIMINATION is configured
- cifs: Fix df output for users with quota limits
- cifs: return ENAMETOOLONG for overlong names in cifs_open()/cifs_lookup()
- nfsd: Limit end of page list when decoding NFSv4 WRITE
- ring-buffer: Have ring_buffer_alloc_read_page() return error on offline 
CPU
- virtio_pci: fix 

[Kernel-packages] [Bug 1713821] Re: arm64 arch_timer fixes

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.12.0-13.14

---
linux (4.12.0-13.14) artful; urgency=low

  * linux: 4.12.0-13.14 -proposed tracker (LP: #1714687)

  * vhost guest network randomly drops under stress (kvm) (LP: #1711251)
- Revert "vhost: cache used event for better performance"

  * EDAC sbridge: Failed to register device with error -22. (LP: #1714112)
- [Config] CONFIG_EDAC_GHES=n

  * Artful update to v4.12.10 stable release (LP: #1714525)
- sparc64: remove unnecessary log message
- bonding: require speed/duplex only for 802.3ad, alb and tlb
- bonding: ratelimit failed speed/duplex update warning
- af_key: do not use GFP_KERNEL in atomic contexts
- dccp: purge write queue in dccp_destroy_sock()
- dccp: defer ccid_hc_tx_delete() at dismantle time
- ipv4: fix NULL dereference in free_fib_info_rcu()
- net_sched/sfq: update hierarchical backlog when drop packet
- net_sched: remove warning from qdisc_hash_add
- bpf: fix bpf_trace_printk on 32 bit archs
- net: igmp: Use ingress interface rather than vrf device
- openvswitch: fix skb_panic due to the incorrect actions attrlen
- ptr_ring: use kmalloc_array()
- ipv4: better IP_MAX_MTU enforcement
- nfp: fix infinite loop on umapping cleanup
- tun: handle register_netdevice() failures properly
- sctp: fully initialize the IPv6 address in sctp_v6_to_addr()
- tipc: fix use-after-free
- ipv6: reset fn->rr_ptr when replacing route
- ipv6: repair fib6 tree in failure case
- tcp: when rearming RTO, if RTO time is in past then fire RTO ASAP
- net/mlx4_core: Enable 4K UAR if SRIOV module parameter is not enabled
- irda: do not leak initialized list.dev to userspace
- net: sched: fix NULL pointer dereference when action calls some targets
- net_sched: fix order of queue length updates in qdisc_replace()
- bpf, verifier: add additional patterns to evaluate_reg_imm_alu
- bpf: fix mixed signed/unsigned derived min/max value bounds
- bpf/verifier: fix min/max handling in BPF_SUB
- Input: trackpoint - add new trackpoint firmware ID
- Input: elan_i2c - add ELAN0602 ACPI ID to support Lenovo Yoga310
- Input: ALPS - fix two-finger scroll breakage in right side on ALPS 
touchpad
- KVM: s390: sthyi: fix sthyi inline assembly
- KVM: s390: sthyi: fix specification exception detection
- KVM: x86: simplify handling of PKRU
- KVM, pkeys: do not use PKRU value in vcpu->arch.guest_fpu.state
- KVM: x86: block guest protection keys unless the host has them enabled
- ALSA: usb-audio: Add delay quirk for H650e/Jabra 550a USB headsets
- ALSA: core: Fix unexpected error at replacing user TLV
- ALSA: hda - Add stereo mic quirk for Lenovo G50-70 (17aa:3978)
- ALSA: firewire: fix NULL pointer dereference when releasing uninitialized
  data of iso-resource
- ALSA: firewire-motu: destroy stream data surely at failure of card
  initialization
- ARCv2: SLC: Make sure busy bit is set properly for region ops
- ARCv2: PAE40: Explicitly set MSB counterpart of SLC region ops addresses
- ARCv2: PAE40: set MSB even if !CONFIG_ARC_HAS_PAE40 but PAE exists in SoC
- PM/hibernate: touch NMI watchdog when creating snapshot
- mm, shmem: fix handling /sys/kernel/mm/transparent_hugepage/shmem_enabled
- dax: fix deadlock due to misaligned PMD faults
- i2c: designware: Fix system suspend
- mm/madvise.c: fix freeing of locked page with MADV_FREE
- fork: fix incorrect fput of ->exe_file causing use-after-free
- mm/memblock.c: reversed logic in memblock_discard()
- arm64: fpsimd: Prevent registers leaking across exec
- drm: Fix framebuffer leak
- drm: Release driver tracking before making the object available again
- drm/sun4i: Implement drm_driver lastclose to restore fbdev console
- drm/atomic: Handle -EDEADLK with out-fences correctly
- drm/atomic: If the atomic check fails, return its value first
- drm/i915/vbt: ignore extraneous child devices for a port
- drm/i915/gvt: Fix the kernel null pointer error
- Revert "drm/amdgpu: fix vblank_time when displays are off"
- ACPI: device property: Fix node lookup in 
acpi_graph_get_child_prop_value()
- tracing: Call clear_boot_tracer() at lateinit_sync
- tracing: Missing error code in tracer_alloc_buffers()
- tracing: Fix kmemleak in tracing_map_array_free()
- tracing: Fix freeing of filter in create_filter() when set_str is false
- RDMA/uverbs: Initialize cq_context appropriately
- kbuild: linker script do not match C names unless
  LD_DEAD_CODE_DATA_ELIMINATION is configured
- cifs: Fix df output for users with quota limits
- cifs: return ENAMETOOLONG for overlong names in cifs_open()/cifs_lookup()
- nfsd: Limit end of page list when decoding NFSv4 WRITE
- ring-buffer: Have ring_buffer_alloc_read_page() return error on offline 
CPU
- virtio_pci: fix 

[Kernel-packages] [Bug 1714687] Re: linux: 4.12.0-13.14 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.12.0-13.14

---
linux (4.12.0-13.14) artful; urgency=low

  * linux: 4.12.0-13.14 -proposed tracker (LP: #1714687)

  * vhost guest network randomly drops under stress (kvm) (LP: #1711251)
- Revert "vhost: cache used event for better performance"

  * EDAC sbridge: Failed to register device with error -22. (LP: #1714112)
- [Config] CONFIG_EDAC_GHES=n

  * Artful update to v4.12.10 stable release (LP: #1714525)
- sparc64: remove unnecessary log message
- bonding: require speed/duplex only for 802.3ad, alb and tlb
- bonding: ratelimit failed speed/duplex update warning
- af_key: do not use GFP_KERNEL in atomic contexts
- dccp: purge write queue in dccp_destroy_sock()
- dccp: defer ccid_hc_tx_delete() at dismantle time
- ipv4: fix NULL dereference in free_fib_info_rcu()
- net_sched/sfq: update hierarchical backlog when drop packet
- net_sched: remove warning from qdisc_hash_add
- bpf: fix bpf_trace_printk on 32 bit archs
- net: igmp: Use ingress interface rather than vrf device
- openvswitch: fix skb_panic due to the incorrect actions attrlen
- ptr_ring: use kmalloc_array()
- ipv4: better IP_MAX_MTU enforcement
- nfp: fix infinite loop on umapping cleanup
- tun: handle register_netdevice() failures properly
- sctp: fully initialize the IPv6 address in sctp_v6_to_addr()
- tipc: fix use-after-free
- ipv6: reset fn->rr_ptr when replacing route
- ipv6: repair fib6 tree in failure case
- tcp: when rearming RTO, if RTO time is in past then fire RTO ASAP
- net/mlx4_core: Enable 4K UAR if SRIOV module parameter is not enabled
- irda: do not leak initialized list.dev to userspace
- net: sched: fix NULL pointer dereference when action calls some targets
- net_sched: fix order of queue length updates in qdisc_replace()
- bpf, verifier: add additional patterns to evaluate_reg_imm_alu
- bpf: fix mixed signed/unsigned derived min/max value bounds
- bpf/verifier: fix min/max handling in BPF_SUB
- Input: trackpoint - add new trackpoint firmware ID
- Input: elan_i2c - add ELAN0602 ACPI ID to support Lenovo Yoga310
- Input: ALPS - fix two-finger scroll breakage in right side on ALPS 
touchpad
- KVM: s390: sthyi: fix sthyi inline assembly
- KVM: s390: sthyi: fix specification exception detection
- KVM: x86: simplify handling of PKRU
- KVM, pkeys: do not use PKRU value in vcpu->arch.guest_fpu.state
- KVM: x86: block guest protection keys unless the host has them enabled
- ALSA: usb-audio: Add delay quirk for H650e/Jabra 550a USB headsets
- ALSA: core: Fix unexpected error at replacing user TLV
- ALSA: hda - Add stereo mic quirk for Lenovo G50-70 (17aa:3978)
- ALSA: firewire: fix NULL pointer dereference when releasing uninitialized
  data of iso-resource
- ALSA: firewire-motu: destroy stream data surely at failure of card
  initialization
- ARCv2: SLC: Make sure busy bit is set properly for region ops
- ARCv2: PAE40: Explicitly set MSB counterpart of SLC region ops addresses
- ARCv2: PAE40: set MSB even if !CONFIG_ARC_HAS_PAE40 but PAE exists in SoC
- PM/hibernate: touch NMI watchdog when creating snapshot
- mm, shmem: fix handling /sys/kernel/mm/transparent_hugepage/shmem_enabled
- dax: fix deadlock due to misaligned PMD faults
- i2c: designware: Fix system suspend
- mm/madvise.c: fix freeing of locked page with MADV_FREE
- fork: fix incorrect fput of ->exe_file causing use-after-free
- mm/memblock.c: reversed logic in memblock_discard()
- arm64: fpsimd: Prevent registers leaking across exec
- drm: Fix framebuffer leak
- drm: Release driver tracking before making the object available again
- drm/sun4i: Implement drm_driver lastclose to restore fbdev console
- drm/atomic: Handle -EDEADLK with out-fences correctly
- drm/atomic: If the atomic check fails, return its value first
- drm/i915/vbt: ignore extraneous child devices for a port
- drm/i915/gvt: Fix the kernel null pointer error
- Revert "drm/amdgpu: fix vblank_time when displays are off"
- ACPI: device property: Fix node lookup in 
acpi_graph_get_child_prop_value()
- tracing: Call clear_boot_tracer() at lateinit_sync
- tracing: Missing error code in tracer_alloc_buffers()
- tracing: Fix kmemleak in tracing_map_array_free()
- tracing: Fix freeing of filter in create_filter() when set_str is false
- RDMA/uverbs: Initialize cq_context appropriately
- kbuild: linker script do not match C names unless
  LD_DEAD_CODE_DATA_ELIMINATION is configured
- cifs: Fix df output for users with quota limits
- cifs: return ENAMETOOLONG for overlong names in cifs_open()/cifs_lookup()
- nfsd: Limit end of page list when decoding NFSv4 WRITE
- ring-buffer: Have ring_buffer_alloc_read_page() return error on offline 
CPU
- virtio_pci: fix 

[Kernel-packages] [Bug 1714112] Re: EDAC sbridge: Failed to register device with error -22.

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.12.0-13.14

---
linux (4.12.0-13.14) artful; urgency=low

  * linux: 4.12.0-13.14 -proposed tracker (LP: #1714687)

  * vhost guest network randomly drops under stress (kvm) (LP: #1711251)
- Revert "vhost: cache used event for better performance"

  * EDAC sbridge: Failed to register device with error -22. (LP: #1714112)
- [Config] CONFIG_EDAC_GHES=n

  * Artful update to v4.12.10 stable release (LP: #1714525)
- sparc64: remove unnecessary log message
- bonding: require speed/duplex only for 802.3ad, alb and tlb
- bonding: ratelimit failed speed/duplex update warning
- af_key: do not use GFP_KERNEL in atomic contexts
- dccp: purge write queue in dccp_destroy_sock()
- dccp: defer ccid_hc_tx_delete() at dismantle time
- ipv4: fix NULL dereference in free_fib_info_rcu()
- net_sched/sfq: update hierarchical backlog when drop packet
- net_sched: remove warning from qdisc_hash_add
- bpf: fix bpf_trace_printk on 32 bit archs
- net: igmp: Use ingress interface rather than vrf device
- openvswitch: fix skb_panic due to the incorrect actions attrlen
- ptr_ring: use kmalloc_array()
- ipv4: better IP_MAX_MTU enforcement
- nfp: fix infinite loop on umapping cleanup
- tun: handle register_netdevice() failures properly
- sctp: fully initialize the IPv6 address in sctp_v6_to_addr()
- tipc: fix use-after-free
- ipv6: reset fn->rr_ptr when replacing route
- ipv6: repair fib6 tree in failure case
- tcp: when rearming RTO, if RTO time is in past then fire RTO ASAP
- net/mlx4_core: Enable 4K UAR if SRIOV module parameter is not enabled
- irda: do not leak initialized list.dev to userspace
- net: sched: fix NULL pointer dereference when action calls some targets
- net_sched: fix order of queue length updates in qdisc_replace()
- bpf, verifier: add additional patterns to evaluate_reg_imm_alu
- bpf: fix mixed signed/unsigned derived min/max value bounds
- bpf/verifier: fix min/max handling in BPF_SUB
- Input: trackpoint - add new trackpoint firmware ID
- Input: elan_i2c - add ELAN0602 ACPI ID to support Lenovo Yoga310
- Input: ALPS - fix two-finger scroll breakage in right side on ALPS 
touchpad
- KVM: s390: sthyi: fix sthyi inline assembly
- KVM: s390: sthyi: fix specification exception detection
- KVM: x86: simplify handling of PKRU
- KVM, pkeys: do not use PKRU value in vcpu->arch.guest_fpu.state
- KVM: x86: block guest protection keys unless the host has them enabled
- ALSA: usb-audio: Add delay quirk for H650e/Jabra 550a USB headsets
- ALSA: core: Fix unexpected error at replacing user TLV
- ALSA: hda - Add stereo mic quirk for Lenovo G50-70 (17aa:3978)
- ALSA: firewire: fix NULL pointer dereference when releasing uninitialized
  data of iso-resource
- ALSA: firewire-motu: destroy stream data surely at failure of card
  initialization
- ARCv2: SLC: Make sure busy bit is set properly for region ops
- ARCv2: PAE40: Explicitly set MSB counterpart of SLC region ops addresses
- ARCv2: PAE40: set MSB even if !CONFIG_ARC_HAS_PAE40 but PAE exists in SoC
- PM/hibernate: touch NMI watchdog when creating snapshot
- mm, shmem: fix handling /sys/kernel/mm/transparent_hugepage/shmem_enabled
- dax: fix deadlock due to misaligned PMD faults
- i2c: designware: Fix system suspend
- mm/madvise.c: fix freeing of locked page with MADV_FREE
- fork: fix incorrect fput of ->exe_file causing use-after-free
- mm/memblock.c: reversed logic in memblock_discard()
- arm64: fpsimd: Prevent registers leaking across exec
- drm: Fix framebuffer leak
- drm: Release driver tracking before making the object available again
- drm/sun4i: Implement drm_driver lastclose to restore fbdev console
- drm/atomic: Handle -EDEADLK with out-fences correctly
- drm/atomic: If the atomic check fails, return its value first
- drm/i915/vbt: ignore extraneous child devices for a port
- drm/i915/gvt: Fix the kernel null pointer error
- Revert "drm/amdgpu: fix vblank_time when displays are off"
- ACPI: device property: Fix node lookup in 
acpi_graph_get_child_prop_value()
- tracing: Call clear_boot_tracer() at lateinit_sync
- tracing: Missing error code in tracer_alloc_buffers()
- tracing: Fix kmemleak in tracing_map_array_free()
- tracing: Fix freeing of filter in create_filter() when set_str is false
- RDMA/uverbs: Initialize cq_context appropriately
- kbuild: linker script do not match C names unless
  LD_DEAD_CODE_DATA_ELIMINATION is configured
- cifs: Fix df output for users with quota limits
- cifs: return ENAMETOOLONG for overlong names in cifs_open()/cifs_lookup()
- nfsd: Limit end of page list when decoding NFSv4 WRITE
- ring-buffer: Have ring_buffer_alloc_read_page() return error on offline 
CPU
- virtio_pci: fix 

[Kernel-packages] [Bug 1715655] Re: linux-aws: 4.4.0-1034.43 -proposed tracker

[Kleber Sacilotto de Souza]

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

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

Title:
  linux-aws: 4.4.0-1034.43 -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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
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 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: 1715651
  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/1715655/+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 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)

[Anton Rusnanto]

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

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

Title:
  ASUS G752VS: Touchpad and Fn keys not working (Ubuntu
  16.04.1/16.10/17.04)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Non-Optimus laptop ASUS G752VS-GC063D-CST256.
  17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 
NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 
802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 
x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS.

  Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and
  17.04, among other problems I found that touchpad and Fn keys (all
  except volume control) doesn't work on my brand new ASUS G752VS.

  It is very hard even to try Ubuntu 16.10 and 17.04 because of the
  missing mouse pointer. This problem must be related to a video driver
  because if after installing one is capable to install Nvidia drivers -
  problem is solved. This problem doesn't exist both while trying and
  installing Ubuntu 16.04.1!

  I'm currently on Windows 10, and this bug report is made from Ubuntu
  16.04.1 LiveCD.

  
  dmesg | grep -i elan
  [  101.082929] input: ELAN1203:00 04F3:3043 Touchpad as 
/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11
  [  101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID 
v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00

  
  xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ G-SPY USB Gaming Mouse  id=10   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=13   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=14   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN1203:00 04F3:3043 Touchpad  id=15   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ G-SPY USB Gaming Mouse  id=9[slave  
keyboard (3)]
  ↳ USB2.0 HD UVC WebCamid=11   [slave  
keyboard (3)]
  ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=12   [slave  
keyboard (3)]
  ↳ Asus WMI hotkeysid=16   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=17   [slave  
keyboard (3)]

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

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

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

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

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

  I: Bus=0003 Vendor=04d9 Product=a070 Version=0110
  N: Name="G-SPY USB Gaming Mouse"
  P: Phys=usb-:00:14.0-2/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:04D9:A070.0001/input/input5
  U: Uniq=
  H: Handlers=sysrq kbd event5 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=e080ffdf01cf fffe
  B: MSC=10
  B: LED=1f

  I: Bus=0003 Vendor=04d9 Product=a070 Version=0110
  N: Name="G-SPY USB Gaming Mouse"
  P: 

[Kernel-packages] [Bug 1687262] Re: 16.10, 17.04, 17.10 Wired connection stopped working RTL 8111/8168/8411

[Joseph Salisbury]

Can you also test the 4.13 final kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13

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

Title:
  16.10, 17.04, 17.10 Wired connection stopped working RTL
  8111/8168/8411

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Zesty:
  Confirmed

Bug description:
  == Regression details ==
  Discovered in version: yakkety
  Last known good version: xenial

  This is a regression.

  Upon upgrading 16.04 -> 16.10. Wired connection provided by
  "RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" has
  stopped working.

  Quickly looked around for possible solution, and decided to go on with
  upgrade to 17.04, since it was my initial upgrade target anyway, and
  wireless on the system continued to function. So, ended up in this
  situation: running 17.04, wireless adapter is working, while wired
  does not work any more.

  Extra observation: I've also tried live session from USB based on
  17.04 ISO-image, wired network adapter just works in the live session.

  Conclusion: it is a software issue.

  Note that similar problem was reported be other user on the forum:

  https://ubuntuforums.org/showthread.php?t=2354675

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-generic 4.10.0.20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alexei 1894 F pulseaudio
   /dev/snd/controlC0:  alexei 1894 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Sun Apr 30 09:33:01 2017
  HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546
  InstallationDate: Installed on 2016-01-06 (479 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-23 (6 days ago)
  dmi.bios.date: 09/16/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: HM65-MXM
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687262/+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 1704479] Re: Change CONFIG_IBMVETH to module

[Frank Heimes]

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

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

Title:
  Change CONFIG_IBMVETH to module

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

Bug description:
  == Comment: #0 - Breno Leitao  - 2017-07-14 15:07:47 ==
  Dear Canonical,

  Please change the CONFIG_IBMVETH=y to module on artful kernel.

  Thank you,
  Breno

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1704479/+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 1670634] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From jac...@de.ibm.com 2017-09-11 10:46 EDT---
Ok, I think then the discussion is back at the point I addressed with my 
comment from June 6th (comment 36 or 38)! If the Multi-Queue feature doesn't 
work with Kernel 4.4 yet, then you must not deliver it (that's exactly why SUSE 
did not activate that feature in their 4.4-Kernel package)!
And then again with Kernel 4.11 or 4.12 you can turn that option for those 
kernel packages on as finally there the feature seems to be mature and can be 
rolled out.

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

Title:
  blk-mq: possible deadlock on CPU hot(un)plug

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

Bug description:
  == Comment: #0 - Carsten Jacobi  - 2017-03-07 03:35:31 ==
  I'm evaluating Ubuntu-Xenial on z for development purposes, the test system 
is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all 
pathes are configured).
  The system hangs regularly when I make packages with "pdebuild" using the 
pbuilder packaging suit.
  The local Linux development team helped me out with a pre-analysis that I can 
post here (thanks a lot for that):

  With the default settings and under a certain workload,
  blk_mq seems to get into a presumed "deadlock".
  Possibly this happens on CPU hot(un)plug.

  After the I/O stalled, a dump was pulled manually.
  The following information is from the crash dump pre-analysis.

  $ zgetdump -i dump.0
  General dump info:
Dump format: elf
Version: 1
UTS node name..: mclint
UTS kernel release.: 4.4.0-65-generic
UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
System arch: s390x (64 bit)
CPU count (online).: 2
Dump memory range..: 8192 MB
  Memory map:
 - 0001b831afff (7043 MB)
0001b831b000 - 0001 (1149 MB)

  Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1.

KERNEL: vmlinux.full
  DUMPFILE: dump.0
  CPUS: 2
  DATE: Fri Mar  3 14:31:07 2017
UPTIME: 02:11:20
  LOAD AVERAGE: 13.00, 12.92, 11.37
 TASKS: 411
  NODENAME: mclint
   RELEASE: 4.4.0-65-generic
   VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
   MACHINE: s390x  (unknown Mhz)
MEMORY: 7.8 GB
 PANIC: ""
   PID: 0
   COMMAND: "swapper/0"
  TASK: bad528  (1 of 2)  [THREAD_INFO: b78000]
   CPU: 0
 STATE: TASK_RUNNING (ACTIVE)
  INFO: no panic task found

  crash> dev -d
  MAJOR GENDISKNAME   REQUEST_QUEUE  TOTAL ASYNC  SYNC   DRV
  ...
  8 1e1d6d800  sda1e1d51210  0 23151 4294944145 
N/A(MQ)
  8 1e4e06800  sdc2081b180 23148 4294944148 
N/A(MQ)
  8 1f07800sdb20c75680 23195 4294944101 
N/A(MQ)
  8 1e4e06000  sdd1e4e31210  0 23099 4294944197 
N/A(MQ)
252 1e1d6c800  dm-0   1e1d51b18  9 1 8 
N/A(MQ)
  ...

  So both dm-mpath and sd have requests pending in their block multiqueue.
  The large numbers of sd look strange and seem to be the unsigned formatting 
of the values shown for async multiplied by -1.

  [0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 
5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 
17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49)
  [0.798262] setup: Linux is running natively in 64-bit mode
  [0.798290] setup: Max memory size: 8192MB
  [0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel 
(System RAM: 7996MB)

  [0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root
  rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0

  [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 
seconds.
  [ 5281.179437]   Not tainted 4.4.0-65-generic #86-Ubuntu
  [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 5281.179440] xfsaild/dm-11   D 007bcf52 0  1604  2 
0x
  [ 5281.179444]0001e931c230 001a6964 0001e6f9b958 
0001e6f9b9d8
0001e15795f0 0001e6f9b988 00ce8c00 
0001ea805c70
0001ea805c00 00ba5ed0 0001e931c1d0 
0001e1579b20
0001ea805c00 0001e15795f0 0001ea805c00 

007d3978 007bc9f8 0001e6f9b9d8 
0001e6f9ba40
  [ 5281.179454] Call Trace:
  [ 5281.179461] ([<007bc9f8>] __schedule+0x300/0x810)
  [ 5281.179462]  [<007bcf52>] schedule+0x4a/0xb0
  [ 5281.179465]  [<007c02aa>] 

[Kernel-packages] [Bug 1715368] Re: Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03 'kernel-fixed-upstream'

[Joseph Salisbury]

I'd like to perform a reverse bisect to figure out which commit upstream
fixes this regression.  We need to figure out  the last kernel that had
this issue and the first kernel that did not.

Can you test the following kernels and report back? We are looking for
the last kernel version that has the bug and the first that does not:

v4.11 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11
v4.12 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12
v4.13-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc1

You don't have to test every kernel, just up until the first kernel that
does not have this bug.

Thanks in advance!

** Tags added: performing-bisect

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

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

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

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

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

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

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

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

Title:
  Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03
  'kernel-fixed-upstream'

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Triaged

Bug description:
  Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03.
  CuW B1 device IDs are missing with Ubuntu 16.04.03 inbox bnxt_en 
driver(0.1.24) 

  Below is the modinfo output of Ubuntu 16.04.03 inbox bnxt_en driver.

  root@ubuntu160403:~# modinfo bnxt_en 
  filename: 
/lib/modules/4.4.0-87-generic/kernel/drivers/net/ethernet/broadcom/bnxt/bnxt_en.ko
 
  version: 0.1.24 
  description: Broadcom BCM573xx network driver 
  license: GPL 
  srcversion: 0110469E9118262B301CA46 
  alias: pci:v14E4d16D3sv*sd*bc*sc*i* 
  alias: pci:v14E4d16CBsv*sd*bc*sc*i* 
  alias: pci:v14E4d16D2sv*sd*bc*sc*i* 
  alias: pci:v14E4d16D1sv*sd*bc*sc*i* 
  alias: pci:v14E4d16CAsv*sd*bc*sc*i* 
  alias: pci:v14E4d16C9sv*sd*bc*sc*i* 
  depends: vxlan 
  intree: Y 
  vermagic: 4.4.0-87-generic SMP mod_unload modversions 

  OS Details: 
  root@ubuntu160403:~# cat /etc/issue 
  Ubuntu 16.04.3 LTS \n \l 

  root@ubuntu160403:~# uname -a 
  Linux ubuntu160403 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715368/+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 1714859] Re: oops in 4.4.0-62-generic (ppc64le)

[Joseph Salisbury]

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

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

** Also affects: linux (Ubuntu Artful)
   Importance: Medium
   Status: Triaged

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

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

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

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

Title:
  oops in 4.4.0-62-generic (ppc64le)

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

Bug description:
  Sep  1 14:23:30 p87 kernel: [17274563.423972] device vnet2 entered 
promiscuous mode
  Sep  1 14:23:30 p87 kernel: [17274563.436101] br0: port 4(vnet2) entered 
forwarding state
  Sep  1 14:23:30 p87 kernel: [17274563.436113] br0: port 4(vnet2) entered 
forwarding state
  Sep  1 14:23:31 p87 kernel: [17274564.005034] audit: type=1400 
audit(1504239811.140:793): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5" 
pid=18952 comm="apparmor_parser"
  Sep  1 14:23:31 p87 kernel: [17274564.019911] audit: type=1400 
audit(1504239811.156:794): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" 
name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5//qemu_bridge_helper" 
pid=18952 comm="apparmor_parser"
  Sep  1 14:23:31 p87 kernel: [17274564.324291] KVM guest htab at 
c079a100 (order 29), LPID 3
  Sep  1 14:23:45 p87 kernel: [17274578.483572] br0: port 4(vnet2) entered 
forwarding state
  Sep  1 14:26:53 p87 kernel: [17274766.572284] br0: port 4(vnet2) entered 
disabled state
  Sep  1 14:26:53 p87 kernel: [17274766.579930] device vnet2 left promiscuous 
mode
  Sep  1 14:26:53 p87 kernel: [17274766.579932] br0: port 4(vnet2) entered 
disabled state
  Sep  1 14:26:54 p87 kernel: [17274767.303109] audit: type=1400 
audit(1504240014.441:795): apparmor="STATUS" operation="profile_remove" 
profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5" 
pid=22668 comm="apparmor_parser"
  Sep  1 14:26:56 p87 kernel: [17274768.917394] audit: type=1400 
audit(1504240016.053:796): apparmor="STATUS" operation="profile_load" 
profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5" 
pid=22672 comm="apparmor_parser"
  Sep  1 14:26:56 p87 kernel: [17274768.917673] audit: type=1400 
audit(1504240016.053:797): apparmor="STATUS" operation="profile_load" 
profile="unconfined" 
name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5//qemu_bridge_helper" 
pid=22672 comm="apparmor_parser"
  Sep  1 14:26:56 p87 kernel: [17274768.982783] device vnet2 entered 
promiscuous mode
  Sep  1 14:26:56 p87 kernel: [17274768.994891] br0: port 4(vnet2) entered 
forwarding state
  Sep  1 14:26:56 p87 kernel: [17274768.994902] br0: port 4(vnet2) entered 
forwarding state
  Sep  1 14:26:56 p87 kernel: [17274769.535982] audit: type=1400 
audit(1504240016.673:798): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5" 
pid=22702 comm="apparmor_parser"
  Sep  1 14:26:56 p87 kernel: [17274769.546719] audit: type=1400 
audit(1504240016.685:799): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" 
name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5//qemu_bridge_helper" 
pid=22702 comm="apparmor_parser"
  Sep  1 14:26:57 p87 kernel: [17274769.861666] KVM guest htab at 
c079a100 (order 29), LPID 3
  Sep  1 14:27:11 p87 kernel: [17274784.050382] br0: port 4(vnet2) entered 
forwarding state
  Sep  1 14:28:30 p87 kernel: [17274863.605174] Unable to handle kernel paging 
request for data at address 0x0008
  Sep  1 14:28:30 p87 kernel: [17274863.605188] Faulting instruction address: 
0xc044edcc
  Sep  1 14:28:30 p87 kernel: [17274863.605195] Oops: Kernel access of bad 
area, sig: 11 [#1]
  Sep  1 14:28:30 p87 kernel: [17274863.605199] SMP NR_CPUS=2048 NUMA PowerNV
  Sep  1 14:28:30 p87 kernel: [17274863.605206] Modules linked in: tcp_diag 
inet_diag ebtable_filter ebtables binfmt_misc veth xfrm_user xfrm_algo 
vhost_net vhost macvtap macvlan xt_CHECKSUM iptable_mangle ipt_REJECT 
nf_reject_ipv4 xt_tcpudp ip6table_filter ip6_tables ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack 
br_netfilter overlay bridge stp llc kvm_hv uio_pdrv_genirq powernv_rng 
ibmpowernv vmx_crypto leds_powernv uio ipmi_powernv ipmi_msghandler kvm_pr kvm 
autofs4 xfs btrfs raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid0 multipath linear raid10 

Re: [Kernel-packages] [Bug 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

[Byron Sommardahl]

How can I install the version on Ubuntu with this fix?

On Sat, Sep 9, 2017, 7:20 PM Mike Schwartz  wrote:

> Looks to me like the patch is in Ubuntu kernel.
>
> http://kernel.ubuntu.com/git/kernel-
> ppa/mirror/linux.git/tree/drivers/mfd/intel-lpss-pci.c
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1700657
>
> Title:
>   Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB
>
> Status in Linux:
>   Unknown
> Status in linux package in Ubuntu:
>   Fix Committed
>
> Bug description:
>   Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I
>   tried in live mode and after full installation. I was able to connect
>   an external mouse and a bluetooth mouse and both worked. I checked my
>   xinput list and no sign:
>
>   ⎡ Virtual core pointerid=2[master pointer
>   (3)] ⎜   ↳ Virtual core XTEST pointer  id=4[slave
>   pointer  (2)] ⎜   ↳ Wacom HID 50FE Finger touch id=12
>   [slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen stylus
>   id=13[slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen eraser
>   id=16[slave  pointer  (2)] ⎜   ↳ byron's trackpad
>   id=17[slave  pointer  (2)] ⎣ Virtual core keyboard
>   id=3[master keyboard (2)]↳ Virtual core XTEST keyboard
>   id=5[slave  keyboard (3)]↳ Power Button
>   id=6[slave  keyboard (3)]↳ Video Bus
>   id=7[slave  keyboard (3)]↳ Video Bus
>   id=8[slave  keyboard (3)]↳ Power Button
>   id=9[slave  keyboard (3)]↳ Apple Inc. Magic Keyboard
>   id=10[slave  keyboard (3)]↳ EasyCamera
>   id=11[slave  keyboard (3)]↳ Ideapad extra buttons
>   id=14[slave  keyboard (3)]↳ AT Translated Set 2 keyboard
>   id=15[slave  keyboard (3)]
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.04
>   Package: linux-image-4.10.0-24-generic 4.10.0-24.28
>   ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
>   Uname: Linux 4.10.0-24-generic x86_64
>   ApportVersion: 2.20.4-0ubuntu4
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  byron  1794 F pulseaudio
>   CurrentDesktop: Unity:Unity7
>   Date: Mon Jun 26 16:51:37 2017
>   InstallationDate: Installed on 2017-06-26 (0 days ago)
>   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
>   MachineType: LENOVO 80X7
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed
> root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7
>   RelatedPackageVersions:
>linux-restricted-modules-4.10.0-24-generic N/A
>linux-backports-modules-4.10.0-24-generic  N/A
>linux-firmware 1.164
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 04/12/2017
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: 4MCN20WW(V1.06)
>   dmi.board.asset.tag: NO Asset Tag
>   dmi.board.name: Lenovo YOGA 720-15IKB
>   dmi.board.vendor: LENOVO
>   dmi.board.version: SDK0J40709 WIN
>   dmi.chassis.asset.tag: NO Asset Tag
>   dmi.chassis.type: 31
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Lenovo YOGA 720-15IKB
>   dmi.modalias:
> dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB:
>   dmi.product.name: 80X7
>   dmi.product.version: Lenovo YOGA 720-15IKB
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/1700657/+subscriptions
>

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

Title:
  Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I
  tried in live mode and after full installation. I was able to connect
  an external mouse and a bluetooth mouse and both worked. I checked my
  xinput list and no sign:

  ⎡ Virtual core pointerid=2[master pointer
  (3)] ⎜   ↳ Virtual core XTEST pointer  id=4[slave
  pointer  (2)] ⎜   ↳ Wacom HID 50FE Finger touch id=12
  [slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen stylus
  id=13[slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen eraser
  id=16[slave  pointer  (2)] ⎜   ↳ byron's trackpad
  id=17[slave  pointer  (2)] ⎣ Virtual core keyboard
  id=3[master keyboard (2)]↳ Virtual core XTEST keyboard
  id=5[slave  keyboard (3)]↳ Power Button
  id=6[slave  keyboard (3)]↳ Video Bus
  id=7[slave  keyboard (3)]↳ Video Bus
  id=8[slave  keyboard (3)]↳ 

Re: [Kernel-packages] [Bug 1716213] Re: package linux-image-4.10.0-33-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

[squire koroma]

Thanks so much for die Effort. I will do so. 
Have a nice day! 

> Gesendet: Montag, 11. September 2017 um 16:12 Uhr
> Von: "Joseph Salisbury" 
> An: squire.kor...@gmx.net
> Betreff: [Bug 1716213] Re: package linux-image-4.10.0-33-generic (not 
> installed) failed to install/upgrade: subprocess new pre-installation script 
> returned error exit status 1
>
> You may need to run the following from a terminal:
> 
> sudo apt-get install -f
> sudo apt-get clean
> sudo apt-get update
> 
> Then re-install the package or updates.
> 
> If that does not resolve your issue, please mark the bug as "Confirmed"
> 
> 
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Low
> 
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Incomplete
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1716213
> 
> Title:
>   package linux-image-4.10.0-33-generic (not installed) failed to
>   install/upgrade: subprocess new pre-installation script returned error
>   exit status 1
> 
> Status in linux package in Ubuntu:
>   Incomplete
> 
> Bug description:
>   cannot
> 
>   ProblemType: Package
>   DistroRelease: Ubuntu 17.04
>   Package: linux-image-4.10.0-33-generic (not installed)
>   ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
>   Uname: Linux 4.10.0-19-generic i686
>   ApportVersion: 2.20.4-0ubuntu4.5
>   Architecture: i386
>   Date: Sun Sep 10 09:48:45 2017
>   DuplicateSignature:
>package:linux-image-4.10.0-33-generic:(not installed)
>Preparing to unpack 
> .../77-linux-image-4.10.0-33-generic_4.10.0-33.37_i386.deb ...
>This kernel does not support a non-PAE CPU.
>dpkg: error processing archive 
> /tmp/apt-dpkg-install-8m4Snl/77-linux-image-4.10.0-33-generic_4.10.0-33.37_i386.deb
>  (--unpack):
> subprocess new pre-installation script returned error exit status 1
>   ErrorMessage: subprocess new pre-installation script returned error exit 
> status 1
>   InstallationDate: Installed on 2017-09-10 (0 days ago)
>   InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
> root=UUID=5dfe327d-30d2-4c3f-b8c5-844b8424c47e ro quiet splash vt.handoff=7
>   RelatedPackageVersions:
>dpkg 1.18.10ubuntu2
>apt  1.4
>   SourcePackage: linux
>   Title: package linux-image-4.10.0-33-generic (not installed) failed to 
> install/upgrade: subprocess new pre-installation script returned error exit 
> status 1
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.vendor: ACER
>   dmi.product.version: Rev 1
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716213/+subscriptions
>

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

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  cannot

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-33-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: i386
  Date: Sun Sep 10 09:48:45 2017
  DuplicateSignature:
   package:linux-image-4.10.0-33-generic:(not installed)
   Preparing to unpack 
.../77-linux-image-4.10.0-33-generic_4.10.0-33.37_i386.deb ...
   This kernel does not support a non-PAE CPU.
   dpkg: error processing archive 
/tmp/apt-dpkg-install-8m4Snl/77-linux-image-4.10.0-33-generic_4.10.0-33.37_i386.deb
 (--unpack):
subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  InstallationDate: Installed on 2017-09-10 (0 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=5dfe327d-30d2-4c3f-b8c5-844b8424c47e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: linux
  Title: package linux-image-4.10.0-33-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: ACER
  dmi.product.version: Rev 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716213/+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 1716332] Re: HP Thunderbolt 3 Dock (90W): USB does not work

[Matthias Lohr]

I bought the docking station some days ago and tested with kernels 4.10,
4.12 and 4.13 - all with the same result. For using the ubuntu-bug
command, i switched back to 4.10. So, there's no (known) working kernel.

** Tags added: kernel-bug-exists-upstream

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

Title:
  HP Thunderbolt 3 Dock (90W): USB does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  i'm using a Lenovo Carbon x1 (5th generation) with a HP Thunderbolt 3
  dock (90W version). All ports are working, except USB Ports - for ~30
  minutes. After ~30 minutes, also the USB ports get activated.

  While waiting for that, dmesg shows something like a "loop" through
  usb devices:

  [...]
  [  389.023845] usb 3-1: new high-speed USB device number 55 using xhci_hcd
  [  389.491841] usb 3-1: new high-speed USB device number 56 using xhci_hcd
  [  389.959928] usb 3-1: new high-speed USB device number 57 using xhci_hcd
  [  390.427925] usb 3-1: new high-speed USB device number 58 using xhci_hcd
  [  390.895832] usb 3-1: new high-speed USB device number 59 using xhci_hcd
  [  391.363817] usb 3-1: new high-speed USB device number 60 using xhci_hcd
  [  391.831818] usb 3-1: new high-speed USB device number 61 using xhci_hcd
  [  392.299759] usb 3-1: new high-speed USB device number 62 using xhci_hcd
  [  392.771813] usb 3-1: new high-speed USB device number 63 using xhci_hcd
  [  393.239765] usb 3-1: new high-speed USB device number 64 using xhci_hcd
  [...]

  Some lines which might be interesting:
  [   13.908506] usb 3-2: 2:1: cannot get freq at ep 0x1
  [   14.058807] usb 3-2: 2:1: cannot get freq at ep 0x1
  [   14.210694] usb 3-2: 2:1: cannot get freq at ep 0x1

  Best regards
  Matthias

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mlohr  5068 F pulseaudio
   /dev/snd/controlC0:  mlohr  5068 F pulseaudio
   /dev/snd/seq:timidity   1311 F timidity
  Date: Mon Sep 11 09:34:54 2017
  HibernationDevice: RESUME=UUID=50da97f8-11c6-4a09-979a-313bba30057d
  InstallationDate: Installed on 2017-04-12 (151 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: LENOVO 20HRCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=6216746e-6b05-4609-9464-e4322637d512 ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET37W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716332/+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 1701222] Re: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
0cff5d394aaba1d6c75fe0036981b7a93a1c4b36

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

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

Hide

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

Title:
  [Hyper-V] LIS daemons fail to start after disable/re-enable VM
  integration services

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  Issue description: Hyper-V daemons fail to start after disable/re-
  enable VM integration services.

  Platform: host independent
  Affected daemons - KVP, FCOPY and VSS.

  Distribution name and release: Ubuntu 16.04, Ubuntu 17.04
  Kernel version: 4.11.0-rc7-next-20170421 (for Ubuntu 16.04), 
4.10.0-19-generic (for Ubuntu 17.04)

  Repro rate: 100%

  Steps to reproduce:
  1.Start VM with Guest Services enabled (FCopy daemon starts automatically)
  2.Go to File > Settings > Integration Services, uncheck Guest Services 
and apply (FCopy daemon will stop at this point)
  3.Re-enable Guest Services from VM Settings (Fcopy daemon is not running).
  This is the issue. systemd monitors for the service and if we have the hook 
for the Guest Service, it tries to start the daemon again.
  systemd attempt to start any of the LIS daemons will fail, but manually 
executing the daemon binary, it will start the daemon.

  Additional Info:
  - the steps above can be repro'd with KVP / Data Exchange integration service 
as well.
  - Manually starting hv_fcopy_daemon works fine.
  - other distros (RHEL) does not have this behavior, the LIS daemons are 
started automatically by systemd once we re-enable the integration service.

  On the upstream kernel and the upstream hv daemons, these messages are 
recorded in syslog, once we re-enable the Guest service:
  HV_FCOPY: pread failed: Bad file descriptor
  systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, 
status=1/FAILURE
  systemd[1]: hv-fcopy-daemon.service: Unit entered failed state.
  systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701222/+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 1708096] Re: Ubuntu16.04.3 Installation fails for JFS file system

[Manoj Iyer]

** Tags added: triage-r

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

Title:
  Ubuntu16.04.3 Installation fails for JFS file system

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

Bug description:
  ---Problem Description---

  Ubuntu16.04.3 installation fails for JFS file system.

  
  ---Environment---
  Garrison Power8

  
  ---Steps to reproduce---
   Install Ubuntu 16.04.3 with 
   - prepboot
  - /root [JFS filesystem]
  - swap space

  
  ---Fails in below step---

   ?? [!!] Install the GRUB boot loader on a hard disk ??
? ?
?  ?Unable to install GRUB in /dev/sdi1 ? ?
?  ? Executing 'grub-install /dev/sdi1' failed. ? ?
?  ?? ?
? Running "? This is a fatal error. ? ?
?  ?? ?
 ? ?
   ??
   ??



  
   moves;  selects;  activates buttons



  
   ? [!!] Install the GRUB boot loader on a hard disk ??
   ?   ?
   ? Installation step failed  ?
   ? An installation step failed. You can try to run the failing item  ?
   ? again from the menu, or skip it and choose something else. The?
   ? failing step is: Install the GRUB boot loader on a hard disk  ?
   ?   ?
   ? ?
   ?   ?
   ?



  
   moves;  selects;  activates buttons

  
  Comment 3 2017-07-20 04:31:05 CDT

  Based on your error, may be you deleted partition 1 (8MB the PReP boot
  partition) which is required for installing the boot loader in IBM
  power systems.  Or maybe you changed the use type to JFS from PReP
  boot.

  Partition 1 (PReP boot) does NOT contain a filesystem and is not
  mounted.Grub is written to it raw and the firmware loads the contents
  of the partition into ram and executes it raw.

  Can you try one more time,
  Pick the default guided partitioning, then change the root 
partition(partition 2) from ext4(or  filesystem) to JFS.Do not delete and 
create any partitions from the default guided setup. Paste the results.

  Comment 4  2017-07-20 09:22:22 CDT

  (In reply to comment #3)
  > Based on your error, may be you deleted partition 1 (8MB the PReP boot
  > partition) which is required for installing the boot loader in IBM power
  > systems.  Or maybe you changed the use type to JFS from PReP boot. 
  > 
  > Partition 1 (PReP boot) does NOT contain a filesystem and is not
  > mounted.Grub is written to it raw and the firmware loads the contents of the
  > partition into ram and executes it raw.
  > 
  > Can you try one more time,
  > Pick the default guided partitioning, then change the root
  > partition(partition 2) from ext4(or  filesystem) to JFS.Do not delete
  > and create any partitions from the default guided setup. Paste the results.

  No, I have not deleted partition and I have not changed the use type
  to JFS from PReP boot.

  Any ways I tried again and it still fails.

  ?? [!!] Partition disks ???
? ?
? This is an overview of your currently configured partitions and mount   ?
? points. Select a partition to modify its settings (file system, mount   ?
? point, etc.), a free space to create partitions, or a device to ?
? initialize its partition table. ?
? ?
?  SCSI4 (0,0,0) (sdi) - 1.0 TB ATA ST1000NX0313  ?
?  >1.0 MBFREE SPACE  ?   ?
?  > #1 7.3 MB K  ?   ?
?  > #2   959.7 GB F  ext4  / ?   ?
?  > #340.5 GB f  swap  swap  ?
?  >  728.6 kBFREE SPACE  ?   ?
?  SCSI5 (0,0,0) (sdj) - 1.0 TB ATA ST1000NX0313  ?   ?
?  > #1  primary4.2 MB  B  

[Kernel-packages] [Bug 1696049] Re: xfstest sanity checks on seek operations fails

[Joseph Salisbury]

Before I start the bisect, can you test the kernel posted to:
http://kernel.ubuntu.com/~jsalisbury/lp1696049/

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

Title:
  xfstest sanity checks on seek operations fails

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

Bug description:
  == Comment: #0 - Harish Sriram 
  Issue:
  --
  xfstest fails with sanity checks on seek operations

  # uname -a
  Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 
12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Create a loop device with xfs filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd 
xfstests-dev
  3. make
  4. Create a local.config for running with created loop device
  5. Run xfstests-dev test  : ./check tests/generic/285 or ./check 
tests/generic/436

  The test 285 fails with following
  ...
  ...
  07. Test file with unwritten extents, only have dirty pages
  07.01 SEEK_HOLE expected 0 or 45056, got 0.   succ
  07.02 SEEK_HOLE expected 1 or 45056, got 1.   succ
  07.03 SEEK_DATA expected 40960 or 40960, got -1.  FAIL
  07.04 SEEK_DATA expected 40960 or 40960, got -1.  FAIL

  08. Test file with unwritten extents, only have unwritten pages
  08.01 SEEK_HOLE expected 0 or 45056, got 0.   succ
  08.02 SEEK_HOLE expected 1 or 45056, got 1.   succ
  08.03 SEEK_DATA expected 40960 or 40960, got -1.  FAIL
  08.04 SEEK_DATA expected 40960 or 40960, got -1.  FAIL

  The test 436 fails with 
  ...
  ...
  14. Test file with unwritten extents, small hole after pagevec dirty pages
  14.01 SEEK_HOLE expected 917504 or 4194304, got 3670016.  FAIL
  14.02 SEEK_HOLE expected 917504 or 4194304, got 3670016.  FAIL
  14.03 SEEK_HOLE expected 3670016 or 4194304, got 3670016. succ
  14.04 SEEK_DATA expected 0 or 0, got 0.   succ
  14.05 SEEK_DATA expected 1 or 1, got 1.   succ
  14.06 SEEK_DATA expected 2752512 or 2752512, got 2752512. succ

  seek sanity check failed!

  Full log is attached.

  == Comment: #6 - Harish Sriram

  commit 5375023ae1266553a7baa0845e82917d8803f48c
  Author: Jan Kara 
  Date:   Thu May 18 16:36:22 2017 -0700

  xfs: Fix missed holes in SEEK_HOLE implementation
  XFS SEEK_HOLE implementation could miss a hole in an unwritten extent as
  can be seen by the following command:
  
  xfs_io -c "falloc 0 256k" -c "pwrite 0 56k" -c "pwrite 128k 8k"
 -c "seek -h 0" file
  wrote 57344/57344 bytes at offset 0
  56 KiB, 14 ops; 0. sec (49.312 MiB/sec and 12623.9856 ops/sec)
  wrote 8192/8192 bytes at offset 131072
  8 KiB, 2 ops; 0. sec (70.383 MiB/sec and 18018.0180 ops/sec)
  Whence  Result
  HOLE139264
  
  Where we can see that hole at offset 56k was just ignored by SEEK_HOLE
  implementation. The bug is in xfs_find_get_desired_pgoff() which does
  not properly detect the case when pages are not contiguous.
  
  Fix the problem by properly detecting when found page has larger offset
  than expected.
  
  CC: sta...@vger.kernel.org
  Fixes: d126d43f631f996daeee5006714fed914be32368
  Signed-off-by: Jan Kara 
  Reviewed-by: Brian Foster 
  Reviewed-by: Darrick J. Wong 
  Signed-off-by: Darrick J. Wong 

  
  The above commit fixes the generic/436 test, but generic/285 still FAILS.

  The generic/285 failure is reproducible on most P8/P9 systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696049/+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 1716213] Re: package linux-image-4.10.0-33-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

[Joseph Salisbury]

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"


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

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

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

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  cannot

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-33-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: i386
  Date: Sun Sep 10 09:48:45 2017
  DuplicateSignature:
   package:linux-image-4.10.0-33-generic:(not installed)
   Preparing to unpack 
.../77-linux-image-4.10.0-33-generic_4.10.0-33.37_i386.deb ...
   This kernel does not support a non-PAE CPU.
   dpkg: error processing archive 
/tmp/apt-dpkg-install-8m4Snl/77-linux-image-4.10.0-33-generic_4.10.0-33.37_i386.deb
 (--unpack):
subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  InstallationDate: Installed on 2017-09-10 (0 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=5dfe327d-30d2-4c3f-b8c5-844b8424c47e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: linux
  Title: package linux-image-4.10.0-33-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: ACER
  dmi.product.version: Rev 1

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

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

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

[Manoj Iyer]

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

** Tags added: triage-g

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

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

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

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

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

  ---Steps to Reproduce---

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

  Machine hangs after below log. Attaching console log.

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

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

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

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

[Kernel-packages] [Bug 1716091] Re: Please make linux-libc-dev Provide: aufs-dev

[Joseph Salisbury]

** Tags added: kernel-da-key

** Tags removed: kernel-da-key
** Tags added: kernel-key

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

Title:
  Please make linux-libc-dev Provide: aufs-dev

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The aufs-tools package build-depends on aufs-dev, which is a separate
  package in Debian.  Since the Ubuntu kernel includes aufs, the only
  aufs header, /usr/include/linux/aufs_type.h, is already shipped by
  linux-libc-dev.  Please have linux-libc-dev declare Provides: aufs-dev
  so that this package is buildable in Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716091/+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 1716332] Re: HP Thunderbolt 3 Dock (90W): USB does not work

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.13 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13


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

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

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

Title:
  HP Thunderbolt 3 Dock (90W): USB does not work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  i'm using a Lenovo Carbon x1 (5th generation) with a HP Thunderbolt 3
  dock (90W version). All ports are working, except USB Ports - for ~30
  minutes. After ~30 minutes, also the USB ports get activated.

  While waiting for that, dmesg shows something like a "loop" through
  usb devices:

  [...]
  [  389.023845] usb 3-1: new high-speed USB device number 55 using xhci_hcd
  [  389.491841] usb 3-1: new high-speed USB device number 56 using xhci_hcd
  [  389.959928] usb 3-1: new high-speed USB device number 57 using xhci_hcd
  [  390.427925] usb 3-1: new high-speed USB device number 58 using xhci_hcd
  [  390.895832] usb 3-1: new high-speed USB device number 59 using xhci_hcd
  [  391.363817] usb 3-1: new high-speed USB device number 60 using xhci_hcd
  [  391.831818] usb 3-1: new high-speed USB device number 61 using xhci_hcd
  [  392.299759] usb 3-1: new high-speed USB device number 62 using xhci_hcd
  [  392.771813] usb 3-1: new high-speed USB device number 63 using xhci_hcd
  [  393.239765] usb 3-1: new high-speed USB device number 64 using xhci_hcd
  [...]

  Some lines which might be interesting:
  [   13.908506] usb 3-2: 2:1: cannot get freq at ep 0x1
  [   14.058807] usb 3-2: 2:1: cannot get freq at ep 0x1
  [   14.210694] usb 3-2: 2:1: cannot get freq at ep 0x1

  Best regards
  Matthias

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mlohr  5068 F pulseaudio
   /dev/snd/controlC0:  mlohr  5068 F pulseaudio
   /dev/snd/seq:timidity   1311 F timidity
  Date: Mon Sep 11 09:34:54 2017
  HibernationDevice: RESUME=UUID=50da97f8-11c6-4a09-979a-313bba30057d
  InstallationDate: Installed on 2017-04-12 (151 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: LENOVO 20HRCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=6216746e-6b05-4609-9464-e4322637d512 ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET37W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716332/+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 1716304] Re: Environmental Variables Have Improper Values

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.13 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13


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

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

Title:
  Environmental Variables Have Improper Values

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With Lubuntu-LXDE the variables DESKTOP_SESSION, XDG_SESSION_DESKTOP,
  and GDMSESSION are set to Lubuntu. A more appropriate and useful value
  would be LXDE. This is not a problem with Lubuntu-Openbox.

  Kernel: 4.10.0-28-generic x86_64 (64 bit gcc: 5.4.0) Desktop: LXDE
  (Openbox 3.6.1) dm: lightdm Distro: Ubuntu 16.04 xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716304/+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 1716258] Re: Keyboard input temporarily ignored when typing root encryption password

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.13 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13


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

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

Title:
  Keyboard input temporarily ignored when typing root encryption
  password

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Symptoms:

  The computer begins its boot process, then the root decryption
  password prompt appears (via Plymouth) and I start typing. The first
  letters are caught, but some letters are not captured. It's as if the
  keyboard shut down during a few seconds and then returned, and I could
  type the whole password properly.

  Things I tried:

  - Typing the password blindly (just inputting the entire password and hitting 
Enter without worrying about missing characters) but it rejected the password 
as incorrect.
  - Typing decryption password without Plymouth (this is not a Plymouth bug).

  
  This affects Debian 9 (didn't affect Debian 8), Fedora, Arch Linux and 
possibly others. It cannot be reproduced with Ubuntu or other distributions 
with old packages. Some component introduced this problem recently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716258/+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 1716368] Re: NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [kworker/2:10:3467]

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.13 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13

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

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

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s!
  [kworker/2:10:3467]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 4.12.0-12.13-generic 4.12.8

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-12-generic 4.12.0-12.13 [modified: 
boot/vmlinuz-4.12.0-12-generic]
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  david  1293 F pulseaudio
   /dev/snd/controlC0:  david  1293 F pulseaudio
   /dev/snd/controlC1:  david  1293 F pulseaudio
  Date: Mon Sep 11 11:30:46 2017
  Failure: oops
  InstallationDate: Installed on 2017-09-10 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170904)
  IwConfig:
   eno1  no wireless extensions.
   
   enp5s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-12-generic 
root=UUID=b66faf19-2c41-4a84-bd17-864f9f1a5db1 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! 
[kworker/2:10:3467]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2906
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H97-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2906:bd02/24/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH97-PRO:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716368/+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 1716301] Re: wifi driver: mt7601u not work on 16.04

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.13 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13


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

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

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

Title:
  wifi driver: mt7601u not work on 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In the beginning, when the adapter is pluged in, it's mounted as a disk 
including driver files for Windows, and
  $> lsusb
  Bus 003 Device 010: ID 148f:2878 Ralink Technology, Corp.

  after eject the disk,
  $> lsusb
  Bus 003 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless 
Adapter

  I tried following 3 drivers:
  1) the default mt7601u included in the kernel: 4.4.0-91-generic
  after eject the disk,
  $> lsmod|grep mt
  mt7601u 102400 0
  mac80211 737280 1 mt7601u
  cfg80211 565248 2 mac80211,mt7601u
  binfmt_misc 20480 1
  $> modinfo mt7601u
  filename: 
/lib/modules/4.4.0-91-generic/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko
  srcversion: E8B632D369E0C2A9F1CF7D8
  alias: usb:v7392p7710d*dc*dsc*dp*ic*isc*ip*in*
  ..
  depends: mac80211,cfg80211
  intree: Y
  vermagic: 4.4.0-91-generic SMP mod_unload modversions

  $> dmesg
  // begin
  [ 4581.094119] usb 3-4: USB disconnect, device number 6
  [ 4584.872751] usb 3-4: new high-speed USB device number 7 using xhci_hcd
  [ 4585.001408] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4585.001413] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4585.001416] usb 3-4: Product: Љ
  [ 4585.001418] usb 3-4: Manufacturer: Љ
  [ 4585.001753] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4585.001873] scsi host6: usb-storage 3-4:1.0
  [ 4586.001122] scsi 6:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4586.001978] sr 6:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4586.002529] sr 6:0:0:0: Attached scsi CD-ROM sr0
  [ 4586.002716] sr 6:0:0:0: Attached scsi generic sg1 type 5
  [ 4619.658385] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4619.691737] ISOFS: changing to secondary root
  [ 4691.563347] usb 3-4: USB disconnect, device number 7
  [ 4693.638315] usb 3-4: new high-speed USB device number 8 using xhci_hcd
  [ 4693.766896] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4693.766901] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4693.766903] usb 3-4: Product: Љ
  [ 4693.766905] usb 3-4: Manufacturer: Љ
  [ 4693.767338] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4693.768063] scsi host7: usb-storage 3-4:1.0
  [ 4694.766737] scsi 7:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4694.767423] sr 7:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4694.767908] sr 7:0:0:0: Attached scsi CD-ROM sr0
  [ 4694.768147] sr 7:0:0:0: Attached scsi generic sg1 type 5
  [ 4728.418255] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4728.427856] ISOFS: changing to secondary root
  [ 4733.824182] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824190] sr 7:0:0:0: [sr0] tag#0 CDB: Start/Stop Unit 1b 00 00 00 02 00
  [ 4733.824218] usb 3-4: USB disconnect, device number 8
  [ 4733.824281] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824291] sr 7:0:0:0: [sr0] tag#0 CDB: Prevent/Allow Medium Removal 1e 
00 00 00 00 00
  [ 4734.099901] usb 3-4: new high-speed USB device number 9 using xhci_hcd
  [ 4734.238749] usb 3-4: New USB device found, idVendor=148f, idProduct=7601
  [ 4734.238754] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 4734.238757] usb 3-4: Product: 802.11 n WLAN
  [ 4734.238772] usb 3-4: Manufacturer: MediaTek
  [ 4734.238775] usb 3-4: SerialNumber: 1.0
  [ 4735.432096] usb 3-4: reset high-speed USB device number 9 using xhci_hcd
  [ 4735.562543] mt7601u 3-4:1.0: ASIC revision: 76010001 MAC revision: 76010500
  [ 4735.563089] mt7601u 3-4:1.0: Firmware Version: 0.1.00 Build: 7640 Build 
time: 201302052146
  [ 4739.011624] mt7601u 3-4:1.0: Vendor request req:07 off:09a8 failed:-110
  [ 4742.131399] mt7601u 3-4:1.0: Vendor request 

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

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2017-09-11 09:52 EDT---
No specific requirement for s390 know, for enabled this config options.
They can be set to N

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

Title:
  blk-mq: possible deadlock on CPU hot(un)plug

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

Bug description:
  == Comment: #0 - Carsten Jacobi  - 2017-03-07 03:35:31 ==
  I'm evaluating Ubuntu-Xenial on z for development purposes, the test system 
is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all 
pathes are configured).
  The system hangs regularly when I make packages with "pdebuild" using the 
pbuilder packaging suit.
  The local Linux development team helped me out with a pre-analysis that I can 
post here (thanks a lot for that):

  With the default settings and under a certain workload,
  blk_mq seems to get into a presumed "deadlock".
  Possibly this happens on CPU hot(un)plug.

  After the I/O stalled, a dump was pulled manually.
  The following information is from the crash dump pre-analysis.

  $ zgetdump -i dump.0
  General dump info:
Dump format: elf
Version: 1
UTS node name..: mclint
UTS kernel release.: 4.4.0-65-generic
UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
System arch: s390x (64 bit)
CPU count (online).: 2
Dump memory range..: 8192 MB
  Memory map:
 - 0001b831afff (7043 MB)
0001b831b000 - 0001 (1149 MB)

  Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1.

KERNEL: vmlinux.full
  DUMPFILE: dump.0
  CPUS: 2
  DATE: Fri Mar  3 14:31:07 2017
UPTIME: 02:11:20
  LOAD AVERAGE: 13.00, 12.92, 11.37
 TASKS: 411
  NODENAME: mclint
   RELEASE: 4.4.0-65-generic
   VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
   MACHINE: s390x  (unknown Mhz)
MEMORY: 7.8 GB
 PANIC: ""
   PID: 0
   COMMAND: "swapper/0"
  TASK: bad528  (1 of 2)  [THREAD_INFO: b78000]
   CPU: 0
 STATE: TASK_RUNNING (ACTIVE)
  INFO: no panic task found

  crash> dev -d
  MAJOR GENDISKNAME   REQUEST_QUEUE  TOTAL ASYNC  SYNC   DRV
  ...
  8 1e1d6d800  sda1e1d51210  0 23151 4294944145 
N/A(MQ)
  8 1e4e06800  sdc2081b180 23148 4294944148 
N/A(MQ)
  8 1f07800sdb20c75680 23195 4294944101 
N/A(MQ)
  8 1e4e06000  sdd1e4e31210  0 23099 4294944197 
N/A(MQ)
252 1e1d6c800  dm-0   1e1d51b18  9 1 8 
N/A(MQ)
  ...

  So both dm-mpath and sd have requests pending in their block multiqueue.
  The large numbers of sd look strange and seem to be the unsigned formatting 
of the values shown for async multiplied by -1.

  [0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 
5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 
17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49)
  [0.798262] setup: Linux is running natively in 64-bit mode
  [0.798290] setup: Max memory size: 8192MB
  [0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel 
(System RAM: 7996MB)

  [0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root
  rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0

  [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 
seconds.
  [ 5281.179437]   Not tainted 4.4.0-65-generic #86-Ubuntu
  [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 5281.179440] xfsaild/dm-11   D 007bcf52 0  1604  2 
0x
  [ 5281.179444]0001e931c230 001a6964 0001e6f9b958 
0001e6f9b9d8
0001e15795f0 0001e6f9b988 00ce8c00 
0001ea805c70
0001ea805c00 00ba5ed0 0001e931c1d0 
0001e1579b20
0001ea805c00 0001e15795f0 0001ea805c00 

007d3978 007bc9f8 0001e6f9b9d8 
0001e6f9ba40
  [ 5281.179454] Call Trace:
  [ 5281.179461] ([<007bc9f8>] __schedule+0x300/0x810)
  [ 5281.179462]  [<007bcf52>] schedule+0x4a/0xb0
  [ 5281.179465]  [<007c02aa>] schedule_timeout+0x232/0x2a8
  [ 5281.179466]  [<007bde50>] wait_for_common+0x110/0x1c8
  [ 5281.179472]  [<0017b602>] flush_work+0x42/0x58
  [ 5281.179564]  [<03ff805e14ba>] xlog_cil_force_lsn+0x7a/0x238 [xfs]
  [ 5281.179589]  [<03ff805dee82>] _xfs_log_force+0x9a/0x2e8 [xfs]
  [ 5281.179615]  [<03ff805df114>] 

[Kernel-packages] [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue

[Shawn Thornton]

shawn@budgie:~$ dmesg
[0.00] microcode: microcode updated early to revision 0x62, date = 
2017-04-27
[0.00] random: get_random_bytes called from start_kernel+0x42/0x4e1 
with crng_init=0
[0.00] Linux version 4.13.0-041300-generic (kernel@gloin) (gcc version 
7.2.0 (Ubuntu 7.2.0-2ubuntu1)) #201709031731 SMP Sun Sep 3 21:33:09 UTC 2017
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.13.0-041300-generic 
root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Centaur CentaurHauls
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
[0.00] x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
[0.00] x86/fpu: Enabled xstate features 0x1f, context size is 960 
bytes, using 'compacted' format.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x00057fff] usable
[0.00] BIOS-e820: [mem 0x00058000-0x00058fff] reserved
[0.00] BIOS-e820: [mem 0x00059000-0x0009dfff] usable
[0.00] BIOS-e820: [mem 0x0009e000-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x75807fff] usable
[0.00] BIOS-e820: [mem 0x75808000-0x75808fff] ACPI NVS
[0.00] BIOS-e820: [mem 0x75809000-0x75809fff] reserved
[0.00] BIOS-e820: [mem 0x7580a000-0x7a844fff] usable
[0.00] BIOS-e820: [mem 0x7a845000-0x7abc] reserved
[0.00] BIOS-e820: [mem 0x7abd-0x7ac10fff] ACPI data
[0.00] BIOS-e820: [mem 0x7ac11000-0x7aef5fff] ACPI NVS
[0.00] BIOS-e820: [mem 0x7aef6000-0x7b51] reserved
[0.00] BIOS-e820: [mem 0x7b52-0x7b5fefff] type 20
[0.00] BIOS-e820: [mem 0x7b5ff000-0x7b5f] usable
[0.00] BIOS-e820: [mem 0x7b60-0x7f7f] reserved
[0.00] BIOS-e820: [mem 0xe000-0xefff] reserved
[0.00] BIOS-e820: [mem 0xfe00-0xfe010fff] reserved
[0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved
[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved
[0.00] BIOS-e820: [mem 0xff00-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00027e7f] usable
[0.00] NX (Execute Disable) protection: active
[0.00] efi: EFI v2.40 by American Megatrends
[0.00] efi:  ACPI=0x7abdd000  ACPI 2.0=0x7abdd000  SMBIOS=0xf  
SMBIOS 3.0=0xf0020  ESRT=0x7b29f118  MEMATTR=0x78220018 
[0.00] random: fast init done
[0.00] SMBIOS 3.0.0 present.
[0.00] DMI: Dell Inc. XPS 13 9360/05JK94, BIOS 2.1.0 08/02/2017
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] e820: last_pfn = 0x27e800 max_arch_pfn = 0x4
[0.00] MTRR default type: write-back
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-B uncachable
[0.00]   C-F write-protect
[0.00] MTRR variable ranges enabled:
[0.00]   0 base 008000 mask 7F8000 uncachable
[0.00]   1 base 007E00 mask 7FFE00 uncachable
[0.00]   2 base 007D00 mask 7FFF00 uncachable
[0.00]   3 disabled
[0.00]   4 disabled
[0.00]   5 disabled
[0.00]   6 disabled
[0.00]   7 disabled
[0.00]   8 disabled
[0.00]   9 disabled
[0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
[0.00] e820: last_pfn = 0x7b600 max_arch_pfn = 0x4
[0.00] esrt: Reserving ESRT space from 0x7b29f118 to 
0x7b29f150.
[0.00] Scanning 1 areas for low memory corruption
[0.00] Base memory trampoline at [8e2bc0098000] 98000 size 24576
[0.00] Using GB pages for direct mapping
[0.00] BRK [0x23eb23000, 0x23eb23fff] PGTABLE
[0.00] BRK [0x23eb24000, 0x23eb24fff] PGTABLE
[0.00] BRK [0x23eb25000, 0x23eb25fff] PGTABLE
[0.00] BRK [0x23eb26000, 0x23eb26fff] PGTABLE
[0.00] BRK [0x23eb27000, 0x23eb27fff] PGTABLE
[0.00] BRK 

[Kernel-packages] [Bug 1713576] Re: More migrations with constant load

[Joseph Salisbury]

You may have to install the linux-tools-common with the stock kernel
before installing the test 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/1713576

Title:
  More migrations with constant load

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

Bug description:
  == Comment: #0 - PUVICHAKRAVARTHY RAMACHANDRAN  - 2017-08-06 13:44:45 ==
  ---Problem Description---
  Significantly higher number of task migrations when the load is fixed but not 
balanced across cores.
   
  ---uname output---
  Linux isvbos3 4.10.0-29-generic #33~16.04.1-Ubuntu SMP Tue Jul 25 18:17:06 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  Power9 dd2.0 

  Machine Type = Power9 
   
  ---Steps to Reproduce---
   Benchmark : Multithreaded - cpu intensive. The system had 2 socket/ 32 
cores/ SMT4 mode.

  When 64 threads was run - the migrations were less over 10s interval.
  when 80 threads were run - the migrations were very high.

  Ideally, it should have been very minimal, as the over all load was constant
   
  == Comment: #3 - SRIKAR DRONAMRAJU - 2017-08-11 06:56:47 ==
  As suspected (commit :  05b40e0577 : "sched/fair: Prefer sibiling only if 
local group is under-utilized")
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=05b40e0577
  should fix the problem

  Ran ' perf stat -a -r 5 -e sched:sched_migrate_task 
/home/srikar/work/ebizzy-0.3/ebizzy -t 35 -S 100'
  to detect the problem and verify the fix

  Here is perf stat without fix.

  Performance counter stats for 'system wide' (5 runs):

   7,758  sched:sched_migrate_task
  ( +-  1.28% )

   100.015658079 seconds time elapsed
  ( +-  0.00% )

  perf stat with fix.

  Performance counter stats for 'system wide' (5 runs):

 415  sched:sched_migrate_task
  ( +- 11.74% )

   100.016021787 seconds time elapsed
  ( +-  0.00% )

  
  git describe on upstream kernel says v4.11-rc2
  # git describe 05b40e0577
  v4.11-rc2-227-g05b40e0

  == Comment: #4 - SRIKAR DRONAMRAJU - 2017-08-11 07:05:37 ==
  Attaching the patch that needs to be applied to fix this bug.
  Verified that patch fixes the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1713576/+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 1711104] Re: [P9][Ubuntu 16.04.03] Additional PMU fixes for P9

[Andrew Cloke]

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

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

Title:
  [P9][Ubuntu 16.04.03] Additional PMU fixes for P9

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Zesty:
  Triaged
Status in perforate source package in Zesty:
  New

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2017-08-16 
04:07:45 ==
  Please integrate the following PMU fixes for P9.

  93fc5ca9a0048c ('powerpc/perf: Cleanup of PM_BR_CMPL vs. PM_BRU_CMPL in 
Power9 event list')
  91e0bd1e62519b ('powerpc/perf: Add PM_LD_MISS_L1 and PM_BR_2PATH to power9 
event list')
  70a7e720998d5b ('powerpc/perf: Factor out PPMU_ONLY_COUNT_RUN check code from 
power8')
  7aa345d84245a7 ('powerpc/perf: Update default sdar_mode value for power9')
  101dd590a7fa37 ('powerpc/perf: Avoid spurious PMU interrupts after idle')
  bdd21ddb919d28 ('powerpc/perf: Avoid spurious PMU interrupts after idle on 
Power9')
  3f0bd8dad0db73 ('powerpc/perf: Add POWER9 alternate PM_RUN_CYC and 
PM_RUN_INST_CMPL events')
  20dd4c624d2515 ('powerpc/perf: Fix SDAR_MODE value for continous sampling on 
Power9')
  24bedcb7c81137 ('powerpc/perf: Fix branch event code for power9')
  8c218578fcbbbd ('powerpc/perf: Fix Power9 test_adder fields')

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1711104/+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 1713884] Re: [CIFS] Fix maximum SMB2 header size

[Joseph Salisbury]

Do we have any reason to do this for Vivid (At this point, Vivid is only
high and critical CVEs).

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

Title:
  [CIFS] Fix maximum SMB2 header size

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress

Bug description:
  Currently the maximum size of SMB2/3 header is set incorrectly which
  leads to hanging of directory listing operations on encrypted SMB3
  connections. Fix this by setting the maximum size to 170 bytes that
  is calculated as RFC1002 length field size (4) + transform header
  size (52) + SMB2 header size (64) + create response size (56).

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=47690ab81f4f29b12bbb0676d3579e61ab4d84de

  This applies across the board 3.16, 4.4, 4.10, artful, and azure.
  Microsoft would be happy to help test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713884/+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 1707875] Re: include support for Python bindings in "perf"

[Manoj Iyer]

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

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

Title:
  include support for Python bindings in "perf"

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

Bug description:
  == Comment: #0 - Paul A. Clarke  - 2017-07-26 09:59:57 ==
  ---Problem Description---
  Request to build python bindings support with perf.

  ---Steps to Reproduce---
   Ubuntu-17.04# perf script -g python
  Python scripting not supported.  Install libpython and rebuild perf to enable 
it.
  For example:
# apt-get install python-dev (ubuntu)
# yum install python-devel (Fedora)
etc.
   
  Userspace tool common name: perf 
   
  Userspace rpm: linux-tools-common 

  Userspace tool obtained from project website:  na

  == Comment: #2 - MAMATHA INAMDAR  - 2017-08-01 05:02:34 
==
  After installing libpython, downloaded ubuntu 17.04 linux source code and 
compiled perf tool then it works fine.

  # ./perf script  -g python 
  generated Python script: perf-script.py

  but when I run perf tool without rebuilding after installing libpython
  it shows an error

  # perf script  -g python 
  Python scripting not supported.  Install libpython and rebuild perf to enable 
it.
  For example:
# apt-get install python-dev (ubuntu)
# yum install python-devel (Fedora)
etc.
  root@p8wookie:/home/Mamatha/ubuntu/ubuntu-zesty/tools/perf# perf --version
  perf version 4.10.17

  == Comment: #3 - MAMATHA INAMDAR  - 2017-08-01 05:03:44 
==
  Request to build python bindings support with perf.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1707875/+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 1707875] Re: include support for Python bindings in "perf"

[Andrew Cloke]

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

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

Title:
  include support for Python bindings in "perf"

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

Bug description:
  == Comment: #0 - Paul A. Clarke  - 2017-07-26 09:59:57 ==
  ---Problem Description---
  Request to build python bindings support with perf.

  ---Steps to Reproduce---
   Ubuntu-17.04# perf script -g python
  Python scripting not supported.  Install libpython and rebuild perf to enable 
it.
  For example:
# apt-get install python-dev (ubuntu)
# yum install python-devel (Fedora)
etc.
   
  Userspace tool common name: perf 
   
  Userspace rpm: linux-tools-common 

  Userspace tool obtained from project website:  na

  == Comment: #2 - MAMATHA INAMDAR  - 2017-08-01 05:02:34 
==
  After installing libpython, downloaded ubuntu 17.04 linux source code and 
compiled perf tool then it works fine.

  # ./perf script  -g python 
  generated Python script: perf-script.py

  but when I run perf tool without rebuilding after installing libpython
  it shows an error

  # perf script  -g python 
  Python scripting not supported.  Install libpython and rebuild perf to enable 
it.
  For example:
# apt-get install python-dev (ubuntu)
# yum install python-devel (Fedora)
etc.
  root@p8wookie:/home/Mamatha/ubuntu/ubuntu-zesty/tools/perf# perf --version
  perf version 4.10.17

  == Comment: #3 - MAMATHA INAMDAR  - 2017-08-01 05:03:44 
==
  Request to build python bindings support with perf.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1707875/+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 1667245] Re: ISST-LTE:pVM:roselp4:ubuntu 17.04: kdump failed after memory DLPAR

[Manoj Iyer]

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

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 17.04: kdump failed after memory DLPAR

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

Bug description:
  ---Problem Description---
  After a memory DLPAR removal, kdump doesn't work:

   Starting Kernel crash dump capture service...
  [   67.714593] kdump-tools[3850]: Starting kdump-tools:  * running 
makedumpfile -c -d 31 /proc/vmcore /var/crash/201702230005/dump-incomplete
  Copying data   : [  2.1 %] -/usr/sbin/kdump-config: line 
639:  3897 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [   72.314140] kdump-tools[3850]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [   73.693881] kdump-tools[3850]: cp: error reading '/proc/vmcore': Bad 
address
  [   73.704152] kdump-tools[3850]:  * kdump-tools: failed to save vmcore in 
/var/crash/201702230005
  [   73.823643] kdump-tools[3850]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201702230005/dmesg.201702230005
  [   73.973813] kdump-tools[3850]: The kernel version is not supported.
  [   73.974078] kdump-tools[3850]: The makedumpfile operation may be 
incomplete.
  [   73.983506] kdump-tools[3850]: The dmesg log is saved to 
/var/crash/201702230005/dmesg.201702230005.
  [   73.983752] kdump-tools[3850]: makedumpfile Completed.
  [   73.983998] kdump-tools[3850]:  * kdump-tools: saved dmesg content in 
/var/crash/201702230005
  [   74.104555] kdump-tools[3850]: Thu, 23 Feb 2017 00:05:15 -0600
  [   74.233502] kdump-tools[3850]: Failed to read reboot parameter file: No 
such file or directory
  [   74.233782] kdump-tools[3850]: Rebooting.
  [   86.629777] reboot: Restarting system

  
  The kdump service should be restarted after the memory DLPAR operation.
   
  C
  ---uname output---
  Linux roselp4 4.10.0-8-generic #10-Ubuntu SMP Mon Feb 13 14:00:06 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = lpar 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1. config kdump on roselp4
  2. do a memory DLPAR removal operation
  3. trigger kdump

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

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

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

[Manoj Iyer]

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

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

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

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

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

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

  ---Steps to Reproduce---

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

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

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

[Kernel-packages] [Bug 1664545] Re: In Ubuntu17.04 as Kvm guest : While trigger kdump console hung having call traces

[Manoj Iyer]

IBM, is the proposed work around of setting "noirqdistrib" acceptable ?
If so could we close this bug?

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

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

Title:
  In Ubuntu17.04 as Kvm guest  : While trigger kdump console hung having
  call traces

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

Bug description:
  In ubuntu17.04 as KVM guest on ubuntu KVM Host and trying kdump on
  guest while kdump process  console got hung having call traces

  
  Reproducible Step:

  1- Install Ubuntu17.04 as kvm guest  on ubuntu kvm host 
  2- configure kdump 
  3- trigger kdump 

  Expected Result :

  Kdump should capture

  Actual Result :

  Kdump console hung having continuous call traces

  LOG:

  [0.488534] Freeing unused kernel memory: 4416K (c8e8 - 
c92d)
  [0.488725] This architecture does not have kernel memory protection.
  Loading, please wait...
  starting version 232
  [0.501616] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.501830] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.501981] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.502162] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.502254] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.502433] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.503188] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.503270] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.503978] random: systemd-udevd: uninitialized urandom read (16 bytes 
read)
  [0.504218] random: systemd-udevd: uninitialized urandom read (16 bytes 
read)
  [  242.663388] INFO: task systemd-udevd:151 blocked for more than 120 seconds.
  [  242.663514]   Not tainted 4.9.0-15-generic #16-Ubuntu
  [  242.663553] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.663755] systemd-udevd   D0   151145 0x00040002
  [  242.663795] Call Trace:
  [  242.663868] [c0001fe4ecd0] [c801c3a0] __switch_to+0x2e0/0x4c0
  [  242.663964] [c0001fe4ed30] [c8b19398] __schedule+0x2f8/0x990
  [  242.664076] [c0001fe4ee10] [c8b19a78] schedule+0x48/0xc0
  [  242.664179] [c0001fe4ee40] [c8b1de54] 
schedule_timeout+0x274/0x470
  [  242.664334] [c0001fe4ef30] [c8b19010] 
io_schedule_timeout+0xd0/0x160
  [  242.664502] [c0001fe4ef80] [c8b1a720] bit_wait_io+0x30/0x90
  [  242.664618] [c0001fe4efb0] [c8b1a168] __wait_on_bit+0xf8/0x170
  [  242.664754] [c0001fe4f000] [c824b238] 
wait_on_page_bit+0x98/0xb0
  [  242.664847] [c0001fe4f060] [c824d60c] 
do_read_cache_page+0x21c/0x4e0
  [  242.665008] [c0001fe4f0d0] [c859be78] 
read_dev_sector+0xb8/0x140
  [  242.665126] [c0001fe4f100] [c85a5d88] 
read_lba.isra.0+0x148/0x250
  [  242.665259] [c0001fe4f170] [c85a652c] efi_partition+0x12c/0x830
  [  242.665363] [c0001fe4f2e0] [c859e768] 
check_partition+0x158/0x2d0
  [  242.665469] [c0001fe4f360] [c859c760] 
rescan_partitions+0xe0/0x390
  [  242.665552] [c0001fe4f430] [c8371828] __blkdev_get+0x358/0x490
  [  242.665669] [c0001fe4f4a0] [c8372b50] blkdev_get+0x1a0/0x4a0
  [  242.665784] [c0001fe4f550] [c8599538] 
device_add_disk+0x4a8/0x500
  [  242.665894] [c0001fe4f600] [d0511cc8] 
virtblk_probe+0x560/0x928 [virtio_blk]
  [  242.665983] [c0001fe4f6c0] [c8687700] 
virtio_dev_probe+0x1d0/0x350
  [  242.666050] [c0001fe4f700] [c8716f30] 
driver_probe_device+0x240/0x540
  [  242.666116] [c0001fe4f790] [c871738c] 
__driver_attach+0x15c/0x160
  [  242.666174] [c0001fe4f810] [c87138ec] 
bus_for_each_dev+0x8c/0xf0
  [  242.666232] [c0001fe4f860] [c87162e4] driver_attach+0x34/0x50
  [  242.666289] [c0001fe4f880] [c8715a78] 
bus_add_driver+0x238/0x380
  [  242.666345] [c0001fe4f910] [c871829c] 
driver_register+0x9c/0x180
  [  242.666403] [c0001fe4f980] [c8686abc] 
register_virtio_driver+0x4c/0x60
  [  242.666470] [c0001fe4f9a0] [d0512114] init+0x84/0xd4 
[virtio_blk]
  [  242.666527] [c0001fe4fa10] [c800dde8] 
do_one_initcall+0x68/0x1d0
  [  242.666584] [c0001fe4fad0] [c8b28e00] do_init_module+0x90/0x244
  [  242.43] [c0001fe4fb60] [c8184794] load_module+0x1614/0x17a0
  [  242.666701] [c0001fe4fd30] [c8184c60] 
SyS_finit_module+0xf0/0x170
  [  242.666759] [c0001fe4fe30] [c800bd84] system_call+0x38/0xe0
  

[Kernel-packages] [Bug 1670634] Re: blk-mq: possible deadlock on CPU hot(un)plug

[Joseph Salisbury]

** Tags removed: kernel-key
** Tags added: kernel-da-key

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

Title:
  blk-mq: possible deadlock on CPU hot(un)plug

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

Bug description:
  == Comment: #0 - Carsten Jacobi  - 2017-03-07 03:35:31 ==
  I'm evaluating Ubuntu-Xenial on z for development purposes, the test system 
is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all 
pathes are configured).
  The system hangs regularly when I make packages with "pdebuild" using the 
pbuilder packaging suit.
  The local Linux development team helped me out with a pre-analysis that I can 
post here (thanks a lot for that):

  With the default settings and under a certain workload,
  blk_mq seems to get into a presumed "deadlock".
  Possibly this happens on CPU hot(un)plug.

  After the I/O stalled, a dump was pulled manually.
  The following information is from the crash dump pre-analysis.

  $ zgetdump -i dump.0
  General dump info:
Dump format: elf
Version: 1
UTS node name..: mclint
UTS kernel release.: 4.4.0-65-generic
UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
System arch: s390x (64 bit)
CPU count (online).: 2
Dump memory range..: 8192 MB
  Memory map:
 - 0001b831afff (7043 MB)
0001b831b000 - 0001 (1149 MB)

  Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1.

KERNEL: vmlinux.full
  DUMPFILE: dump.0
  CPUS: 2
  DATE: Fri Mar  3 14:31:07 2017
UPTIME: 02:11:20
  LOAD AVERAGE: 13.00, 12.92, 11.37
 TASKS: 411
  NODENAME: mclint
   RELEASE: 4.4.0-65-generic
   VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
   MACHINE: s390x  (unknown Mhz)
MEMORY: 7.8 GB
 PANIC: ""
   PID: 0
   COMMAND: "swapper/0"
  TASK: bad528  (1 of 2)  [THREAD_INFO: b78000]
   CPU: 0
 STATE: TASK_RUNNING (ACTIVE)
  INFO: no panic task found

  crash> dev -d
  MAJOR GENDISKNAME   REQUEST_QUEUE  TOTAL ASYNC  SYNC   DRV
  ...
  8 1e1d6d800  sda1e1d51210  0 23151 4294944145 
N/A(MQ)
  8 1e4e06800  sdc2081b180 23148 4294944148 
N/A(MQ)
  8 1f07800sdb20c75680 23195 4294944101 
N/A(MQ)
  8 1e4e06000  sdd1e4e31210  0 23099 4294944197 
N/A(MQ)
252 1e1d6c800  dm-0   1e1d51b18  9 1 8 
N/A(MQ)
  ...

  So both dm-mpath and sd have requests pending in their block multiqueue.
  The large numbers of sd look strange and seem to be the unsigned formatting 
of the values shown for async multiplied by -1.

  [0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 
5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 
17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49)
  [0.798262] setup: Linux is running natively in 64-bit mode
  [0.798290] setup: Max memory size: 8192MB
  [0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel 
(System RAM: 7996MB)

  [0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root
  rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0

  [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 
seconds.
  [ 5281.179437]   Not tainted 4.4.0-65-generic #86-Ubuntu
  [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 5281.179440] xfsaild/dm-11   D 007bcf52 0  1604  2 
0x
  [ 5281.179444]0001e931c230 001a6964 0001e6f9b958 
0001e6f9b9d8
0001e15795f0 0001e6f9b988 00ce8c00 
0001ea805c70
0001ea805c00 00ba5ed0 0001e931c1d0 
0001e1579b20
0001ea805c00 0001e15795f0 0001ea805c00 

007d3978 007bc9f8 0001e6f9b9d8 
0001e6f9ba40
  [ 5281.179454] Call Trace:
  [ 5281.179461] ([<007bc9f8>] __schedule+0x300/0x810)
  [ 5281.179462]  [<007bcf52>] schedule+0x4a/0xb0
  [ 5281.179465]  [<007c02aa>] schedule_timeout+0x232/0x2a8
  [ 5281.179466]  [<007bde50>] wait_for_common+0x110/0x1c8
  [ 5281.179472]  [<0017b602>] flush_work+0x42/0x58
  [ 5281.179564]  [<03ff805e14ba>] xlog_cil_force_lsn+0x7a/0x238 [xfs]
  [ 5281.179589]  [<03ff805dee82>] _xfs_log_force+0x9a/0x2e8 [xfs]
  [ 5281.179615]  [<03ff805df114>] xfs_log_force+0x44/0x100 [xfs]
  [ 5281.179640]  [<03ff805ec668>] xfsaild+0x170/0x798 [xfs]
  [ 5281.179643]  [<0018335a>] 

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

[Manoj Iyer]

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

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

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

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

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

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

  ---Steps to Reproduce---

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

  Machine details
  ===

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

  $ ssh ubuntu@9.47.70.29

  PW: shriya101

  
  Attaching logs

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

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

  Attaching the logs.

  Network info:

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

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

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

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

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


  Thanks,
  Pavithra

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

  
  == Comment: #7 - PAVITHRA R. PRAKASH  - 2017-03-07 
23:21:27 ==

  
  == Comment: #8 - Urvashi Jawere  - 2017-03-08 02:48:15 ==
  I am able to see some errors in syslog ;

  auxiliary
  Mar  7 04:57:44 

[Kernel-packages] [Bug 1635597] Re: Ubuntu16.10:talclp1: Kdump failed with multipath disk

[Manoj Iyer]

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

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

Title:
  Ubuntu16.10:talclp1: Kdump failed with multipath disk

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

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

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

[Kernel-packages] [Bug 1635597] Re: Ubuntu16.10:talclp1: Kdump failed with multipath disk

[Andrew Cloke]

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

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

Title:
  Ubuntu16.10:talclp1: Kdump failed with multipath disk

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

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

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

[Kernel-packages] [Bug 1702998] Re: Ubuntu 17.04: Guest crashed @writeback_sb_inodes+0x310/0x590

[Andrew Cloke]

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

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

Title:
  Ubuntu 17.04: Guest crashed @writeback_sb_inodes+0x310/0x590

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

Bug description:
  == Comment: #0 - Lata Kuntal  - 2017-03-03 00:50:54 ==
  Ubuntu 17.04 guest dropped at xmon after crashing at 
writeback_sb_inodes+0x310/0x590. 
  The guest is having XFS rootfs and NPIV disk. It crashed after 30+ hrs of 
BASE and NFS stress test .

  Crash logs
  ===
  root@guskvm:~# virsh console gusg1 --force
  Connected to domain gusg1
  Escape character is ^]

  0:mon>
  0:mon> t
  [c000a4bc7940] c036f790 writeback_sb_inodes+0x310/0x590
  [c000a4bc7a50] c036faf4 __writeback_inodes_wb+0xe4/0x150
  [c000a4bc7ab0] c036ff1c wb_writeback+0x2cc/0x440
  [c000a4bc7b80] c0370c30 wb_workfn+0x150/0x560
  [c000a4bc7c90] c00ed8c0 process_one_work+0x2b0/0x5a0
  [c000a4bc7d20] c00edc58 worker_thread+0xa8/0x650
  [c000a4bc7dc0] c00f67b4 kthread+0x154/0x1a0
  [c000a4bc7e30] c000b4e8 ret_from_kernel_thread+0x5c/0x74
  0:mon> r
  R00 = c036f790   R16 = c000eca70300
  R01 = c000a4bc78e0   R17 = c000f7035240
  R02 = c143c900   R18 = 
  R03 = c000f7035150   R19 = 
  R04 = 0019   R20 = c000a4bc4000
  R05 = 0100   R21 = ff7f
  R06 =    R22 = c433d758
  R07 =    R23 = c433d738
  R08 = 00034995   R24 = 
  R09 =    R25 = 
  R10 = 8000   R26 = c000f70351d8
  R11 = c000a4bc7a40   R27 = 
  R12 = 2200   R28 = 0001
  R13 = cfb8   R29 = c433d728
  R14 =    R30 = c000f7035150
  R15 = c000f70351d8   R31 = 
  pc  = c036c120 locked_inode_to_wb_and_lock_list+0x50/0x290
  cfar= c00b2a14 kvmppc_save_tm+0x168/0x16c
  lr  = c036f790 writeback_sb_inodes+0x310/0x590
  msr = 80009033   cr  = 24002482
  ctr = c0381e30   xer =    trap =  300
  dar =    dsisr = 4000
  0:mon> e
  cpu 0x0: Vector: 300 (Data Access) at [c000a4bc7660]
  pc: c036c120: locked_inode_to_wb_and_lock_list+0x50/0x290
  lr: c036f790: writeback_sb_inodes+0x310/0x590
  sp: c000a4bc78e0
 msr: 80009033
 dar: 0
   dsisr: 4000
current = 0xc000fbe96000
paca= 0xcfb8   softe: 0irq_happened: 0x01
  pid   = 17305, comm = kworker/u16:0
  Linux version 4.10.0-8-generic (buildd@bos01-ppc64el-001) (gcc version 6.3.0 
20161229 (Ubuntu 6.3.0-2ubuntu1) ) #10-Ubuntu SMP Mon Feb 13 14:00:06 UTC 2017 
(Ubuntu 4.10.0-8.10-generic 4.10.0-rc8)
  0:mon> d
      ||
  0:mon>

  
  Host and guest kernel build
  =
  4.10.0-8-generic

  
  OPAL firmware version
  
T side: FW860.20 (SV860_078)
Boot side : FW860.20 (SV860_078)

  
  == Comment: #4 - VIPIN K. PARASHAR  - 2017-03-03 
02:55:20 ==
  [140071.761707] Adding 153536k swap on /dev/loop0.  Priority:-2 extents:1 
across:153536k FS
  [140072.153143] Adding 153472k swap on /dev/loop0.  Priority:-2 extents:1 
across:153472k FS
  [140072.441833] Unable to handle kernel paging request for data at address 
0x
  [140072.442064] Faulting instruction address: 0xc036c120
  0:mon>

  0:mon> e
  cpu 0x0: Vector: 300 (Data Access) at [c000a4bc7660]
  pc: c036c120: locked_inode_to_wb_and_lock_list+0x50/0x290
  lr: c036f790: writeback_sb_inodes+0x310/0x590
  sp: c000a4bc78e0
 msr: 80009033
 dar: 0
   dsisr: 4000
current = 0xc000fbe96000
paca= 0xcfb8 softe: 0irq_happened: 0x01
  pid   = 17305, comm = kworker/u16:0
  Linux version 4.10.0-8-generic (buildd@bos01-ppc64el-001) (gcc version 6.3.0 
20161229 (Ubuntu 6.3.0-2ubuntu1) ) #10-Ubuntu SMP Mon Feb 13 14:00:06 UTC 2017 
(Ubuntu 4.10.0-8.10-generic 4.10.0-rc8)
  0:mon> t
  [c000a4bc7940] c036f790 writeback_sb_inodes+0x310/0x590
  [c000a4bc7a50] c036faf4 __writeback_inodes_wb+0xe4/0x150
  [c000a4bc7ab0] c036ff1c wb_writeback+0x2cc/0x440
  [c000a4bc7b80] c0370c30 wb_workfn+0x150/0x560
  [c000a4bc7c90] c00ed8c0 process_one_work+0x2b0/0x5a0
  [c000a4bc7d20] c00edc58 

[Kernel-packages] [Bug 1643527] Re: dasdfmt fails after vary online. syslog show strange message "The disk layout of the DASD is not supported"

[Frank Heimes]

** Changed in: linux (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => Frank Heimes 
(frank-heimes)

** Changed in: linux (Ubuntu)
 Assignee: Frank Heimes (frank-heimes) => (unassigned)

** Changed in: ubuntu-z-systems
   Status: Invalid => Won't Fix

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

Title:
  dasdfmt fails after vary online. syslog show strange message "The disk
  layout of the DASD is not supported"

Status in Ubuntu on IBM z Systems:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  Problem description:
  procedure:
 echo 1 > /sys/bus/ccw/devices/0.0.0199/online
 /sbin/chzdev dasd-eckd 0199 -e -p
 /sbin/dasdfmt -b 4096 -d cdl -f /dev/disk/by-path/ccw-0.0.0199 -y

  dasdfmt fails with:
 /sbin/dasdfmt: Unable to open device /dev/disk/by-path/ccw-0.0.0199: No 
such device

  looking at the syslog i can see a strange message that only comes out when i 
am having this issue:
  Nov 21 08:52:12 JUUB16MS kernel: [   67.412484] dasd-eckd 0.0.0199: The disk 
layout of the DASD is not supported
  lsdasd returns:
 root@JUUB16MS:~# lsdasd
  Bus-ID Status  Name  Device  Type  BlkSz  Size  Blocks
  ==
  0.0.0192   active  dasda 94:0ECKD  4096   5070MB1298160
  0.0.0195   active  dasdb 94:4FBA   51240MB  81920
  0.0.0193   n/f dasdc 94:8ECKD
  0.0.0196   active  dasdd 94:12   FBA   51240MB  81920
  0.0.0194   n/f dasde 94:16   ECKD
  0.0.0197   n/f dasdf 94:20   ECKD
  0.0.0198   n/f dasdg 94:24   ECKD
  0.0.0199   n/f dasdh 94:28   ECKD

  you can see that the 199 is not format and can't be formatted...
  a workaround is to vary the disk offline and then online again.
  this time it will start ok and you can format it and work with it.
  --
  just to be clear... this happens after linking to an un-formatted disk 
dynamically and then vary it online...
  for example:
 vmcp link '*' 199 199
 echo 1 > /sys/bus/ccw/devices/0.0.0199/online
 /sbin/chzdev dasd-eckd 0199 -e -p
 /sbin/dasdfmt -b 4096 -d cdl -f /dev/disk/by-path/ccw-0.0.0199 -y

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1643527/+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 1643527] Re: dasdfmt fails after vary online. syslog show strange message "The disk layout of the DASD is not supported"

[Andrew Cloke]

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

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

Title:
  dasdfmt fails after vary online. syslog show strange message "The disk
  layout of the DASD is not supported"

Status in Ubuntu on IBM z Systems:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  Problem description:
  procedure:
 echo 1 > /sys/bus/ccw/devices/0.0.0199/online
 /sbin/chzdev dasd-eckd 0199 -e -p
 /sbin/dasdfmt -b 4096 -d cdl -f /dev/disk/by-path/ccw-0.0.0199 -y

  dasdfmt fails with:
 /sbin/dasdfmt: Unable to open device /dev/disk/by-path/ccw-0.0.0199: No 
such device

  looking at the syslog i can see a strange message that only comes out when i 
am having this issue:
  Nov 21 08:52:12 JUUB16MS kernel: [   67.412484] dasd-eckd 0.0.0199: The disk 
layout of the DASD is not supported
  lsdasd returns:
 root@JUUB16MS:~# lsdasd
  Bus-ID Status  Name  Device  Type  BlkSz  Size  Blocks
  ==
  0.0.0192   active  dasda 94:0ECKD  4096   5070MB1298160
  0.0.0195   active  dasdb 94:4FBA   51240MB  81920
  0.0.0193   n/f dasdc 94:8ECKD
  0.0.0196   active  dasdd 94:12   FBA   51240MB  81920
  0.0.0194   n/f dasde 94:16   ECKD
  0.0.0197   n/f dasdf 94:20   ECKD
  0.0.0198   n/f dasdg 94:24   ECKD
  0.0.0199   n/f dasdh 94:28   ECKD

  you can see that the 199 is not format and can't be formatted...
  a workaround is to vary the disk offline and then online again.
  this time it will start ok and you can format it and work with it.
  --
  just to be clear... this happens after linking to an un-formatted disk 
dynamically and then vary it online...
  for example:
 vmcp link '*' 199 199
 echo 1 > /sys/bus/ccw/devices/0.0.0199/online
 /sbin/chzdev dasd-eckd 0199 -e -p
 /sbin/dasdfmt -b 4096 -d cdl -f /dev/disk/by-path/ccw-0.0.0199 -y

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1643527/+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 1716033] Please help test kernel in PPA for tpm-crb

[Manoj Iyer]

Jeff,

A test kernel with patches to enable tcm-crb is available for testing 
in https://launchpad.net/~centriq-team/+archive/ubuntu/lp1716033-tpm/ 
This kernel has patches to enable tcm-crb for ARM64.

Could you please test this kernel and post test results here? Once we 
get positive test results I can submit the patches for SRU.

Thanks
Manoj Iyer

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

Title:
  [SRU][Zesty]  enable TPM CRB driver on ARM64 for Qualcomm Centriq 2400

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Enable TPM CRB driver on ARM64 for Qualcomm Centriq 2400. Where, control area 
buffer address is greater than 32-bit.

  [Test]
  Currently only built for X64 & ACPI. 

  [Fix]
  This is upstream:
  19b7bf51fc3d tpm, tpm_crb: Handle 64-bit resource in crb_check_resource()
  08eff49d63ca tpm/tpm_crb: Enable TPM CRB interface for ARM64

  [Regression Potential]
  None.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716033/+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 1643527] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2017-09-11 09:06 EDT---
IBM bugzilla status -> closed , not reproducable. If the problem will be 
detected in the future, a new bugzilla should be opened

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

Title:
  dasdfmt fails after vary online. syslog show strange message "The disk
  layout of the DASD is not supported"

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  Problem description:
  procedure:
 echo 1 > /sys/bus/ccw/devices/0.0.0199/online
 /sbin/chzdev dasd-eckd 0199 -e -p
 /sbin/dasdfmt -b 4096 -d cdl -f /dev/disk/by-path/ccw-0.0.0199 -y

  dasdfmt fails with:
 /sbin/dasdfmt: Unable to open device /dev/disk/by-path/ccw-0.0.0199: No 
such device

  looking at the syslog i can see a strange message that only comes out when i 
am having this issue:
  Nov 21 08:52:12 JUUB16MS kernel: [   67.412484] dasd-eckd 0.0.0199: The disk 
layout of the DASD is not supported
  lsdasd returns:
 root@JUUB16MS:~# lsdasd
  Bus-ID Status  Name  Device  Type  BlkSz  Size  Blocks
  ==
  0.0.0192   active  dasda 94:0ECKD  4096   5070MB1298160
  0.0.0195   active  dasdb 94:4FBA   51240MB  81920
  0.0.0193   n/f dasdc 94:8ECKD
  0.0.0196   active  dasdd 94:12   FBA   51240MB  81920
  0.0.0194   n/f dasde 94:16   ECKD
  0.0.0197   n/f dasdf 94:20   ECKD
  0.0.0198   n/f dasdg 94:24   ECKD
  0.0.0199   n/f dasdh 94:28   ECKD

  you can see that the 199 is not format and can't be formatted...
  a workaround is to vary the disk offline and then online again.
  this time it will start ok and you can format it and work with it.
  --
  just to be clear... this happens after linking to an un-formatted disk 
dynamically and then vary it online...
  for example:
 vmcp link '*' 199 199
 echo 1 > /sys/bus/ccw/devices/0.0.0199/online
 /sbin/chzdev dasd-eckd 0199 -e -p
 /sbin/dasdfmt -b 4096 -d cdl -f /dev/disk/by-path/ccw-0.0.0199 -y

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1643527/+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 1670634] Re: blk-mq: possible deadlock on CPU hot(un)plug

[Juerg Haefliger]

The difference between the Xenial and SUSE kernel is that Xenial has:
  CONFIG_SCSI_MQ_DEFAULT=y
  CONFIG_DM_MQ_DEFAULT=y
but SUSE:
  # CONFIG_SCSI_MQ_DEFAULT is not set
  # CONFIG_DM_MQ_DEFAULT is not set

If I disable blk-mq in the Xenial kernel, the test passes.

The easiest 'fix' would be to simply disable blk-mq. This can be
accomplished via the kernel commandline parameters:
scsi_mod.use_blk_mq=0 dm_mod.use_blk_mq=0.

I also noticed that s390x is the only architecture where these options
are enabled in the Xenial kernel. Is there a specific requirement for
this?

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

Title:
  blk-mq: possible deadlock on CPU hot(un)plug

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

Bug description:
  == Comment: #0 - Carsten Jacobi  - 2017-03-07 03:35:31 ==
  I'm evaluating Ubuntu-Xenial on z for development purposes, the test system 
is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all 
pathes are configured).
  The system hangs regularly when I make packages with "pdebuild" using the 
pbuilder packaging suit.
  The local Linux development team helped me out with a pre-analysis that I can 
post here (thanks a lot for that):

  With the default settings and under a certain workload,
  blk_mq seems to get into a presumed "deadlock".
  Possibly this happens on CPU hot(un)plug.

  After the I/O stalled, a dump was pulled manually.
  The following information is from the crash dump pre-analysis.

  $ zgetdump -i dump.0
  General dump info:
Dump format: elf
Version: 1
UTS node name..: mclint
UTS kernel release.: 4.4.0-65-generic
UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
System arch: s390x (64 bit)
CPU count (online).: 2
Dump memory range..: 8192 MB
  Memory map:
 - 0001b831afff (7043 MB)
0001b831b000 - 0001 (1149 MB)

  Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1.

KERNEL: vmlinux.full
  DUMPFILE: dump.0
  CPUS: 2
  DATE: Fri Mar  3 14:31:07 2017
UPTIME: 02:11:20
  LOAD AVERAGE: 13.00, 12.92, 11.37
 TASKS: 411
  NODENAME: mclint
   RELEASE: 4.4.0-65-generic
   VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
   MACHINE: s390x  (unknown Mhz)
MEMORY: 7.8 GB
 PANIC: ""
   PID: 0
   COMMAND: "swapper/0"
  TASK: bad528  (1 of 2)  [THREAD_INFO: b78000]
   CPU: 0
 STATE: TASK_RUNNING (ACTIVE)
  INFO: no panic task found

  crash> dev -d
  MAJOR GENDISKNAME   REQUEST_QUEUE  TOTAL ASYNC  SYNC   DRV
  ...
  8 1e1d6d800  sda1e1d51210  0 23151 4294944145 
N/A(MQ)
  8 1e4e06800  sdc2081b180 23148 4294944148 
N/A(MQ)
  8 1f07800sdb20c75680 23195 4294944101 
N/A(MQ)
  8 1e4e06000  sdd1e4e31210  0 23099 4294944197 
N/A(MQ)
252 1e1d6c800  dm-0   1e1d51b18  9 1 8 
N/A(MQ)
  ...

  So both dm-mpath and sd have requests pending in their block multiqueue.
  The large numbers of sd look strange and seem to be the unsigned formatting 
of the values shown for async multiplied by -1.

  [0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 
5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 
17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49)
  [0.798262] setup: Linux is running natively in 64-bit mode
  [0.798290] setup: Max memory size: 8192MB
  [0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel 
(System RAM: 7996MB)

  [0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root
  rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0

  [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 
seconds.
  [ 5281.179437]   Not tainted 4.4.0-65-generic #86-Ubuntu
  [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 5281.179440] xfsaild/dm-11   D 007bcf52 0  1604  2 
0x
  [ 5281.179444]0001e931c230 001a6964 0001e6f9b958 
0001e6f9b9d8
0001e15795f0 0001e6f9b988 00ce8c00 
0001ea805c70
0001ea805c00 00ba5ed0 0001e931c1d0 
0001e1579b20
0001ea805c00 0001e15795f0 0001ea805c00 

007d3978 007bc9f8 0001e6f9b9d8 
0001e6f9ba40
  [ 5281.179454] Call Trace:
  [ 5281.179461] ([<007bc9f8>] __schedule+0x300/0x810)
  [ 5281.179462]  [<007bcf52>] 

[Kernel-packages] [Bug 1713765] Re: Consider "s390/mm: avoid empty zero pages for KVM guests to avoid postcopy hangs" for Artful

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: Confirmed => Won't Fix

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

Title:
  Consider "s390/mm: avoid empty zero pages for KVM guests to avoid
  postcopy hangs" for Artful

Status in Ubuntu on IBM z Systems:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  Hi,
  there is this patch in discussion [1].

  If I read correctly between the lines that is supposed to go to -stable trees 
as well as to linxu-s390x next (4.14) submissions.
  But the change is rather big and we have to consider taking that early or as 
SRU or not at all.

  I wanted to ask the kernel Team to keep an eye on that discussion and take 
the patch into consideration - IMHO it might change KVM behavior on s390 quite 
a bit.
  So I'm not sure how SRUable it is while on Artful we migth add it rather soon 
before release.

  To some extend we should wait for the discussion on the upstreaming,
  but then I wanted to make you aware asap.

  [1]: https://lists.gnu.org/archive/html/qemu-
  devel/2017-08/msg05286.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1713765/+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 1715696] Re: linux 4.12.0-13.14 ADT test failure with linux 4.12.0-13.14

[Seth Forshee]

No kernel bugs found, closing.

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

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

Title:
  linux 4.12.0-13.14 ADT test failure with linux 4.12.0-13.14

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/l/linux/20170907_105519_350cf@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/i386/l/linux/20170907_043106_1d132@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/l/linux/20170907_100504_350cf@/log.gz

  This bug is for the stress-ng smoke test failures on i386.

   Summary:
  Stressors run: 148
  Skipped: 2,  bind-mount sock-diag
  Failed:  2,  cyclic filename
  Oopsed:  0, 
  Passed:  144,  
  Badret:  0,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715696/+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 1713765] Re: Consider "s390/mm: avoid empty zero pages for KVM guests to avoid postcopy hangs" for Artful

[ChristianEhrhardt]

Seth missed to actually close it, doing so.

** Changed in: linux (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: linux (Ubuntu)
 Assignee: Seth Forshee (sforshee) => (unassigned)

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

Title:
  Consider "s390/mm: avoid empty zero pages for KVM guests to avoid
  postcopy hangs" for Artful

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  Hi,
  there is this patch in discussion [1].

  If I read correctly between the lines that is supposed to go to -stable trees 
as well as to linxu-s390x next (4.14) submissions.
  But the change is rather big and we have to consider taking that early or as 
SRU or not at all.

  I wanted to ask the kernel Team to keep an eye on that discussion and take 
the patch into consideration - IMHO it might change KVM behavior on s390 quite 
a bit.
  So I'm not sure how SRUable it is while on Artful we migth add it rather soon 
before release.

  To some extend we should wait for the discussion on the upstreaming,
  but then I wanted to make you aware asap.

  [1]: https://lists.gnu.org/archive/html/qemu-
  devel/2017-08/msg05286.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1713765/+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 1715145] Re: linux: 4.13.0-9.10 -proposed tracker

[Seth Forshee]

*** This bug is a duplicate of bug 1716287 ***
https://bugs.launchpad.net/bugs/1716287

** This bug has been marked a duplicate of bug 1716287
   linux: 4.13.0-10.11 -proposed tracker

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

Title:
  linux: 4.13.0-9.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  This bug is for tracking the 4.13.0-9.10 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

  kernel-phase:Packaging
  kernel-phase-changed:Tuesday, 05. September 2017 13:00 UTC

  -- swm properties --
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1715145/+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 1678477] Re: Kernel has troule recognizing Corsair Strafe RGB keyboard

[Stefan Bader]

** Also affects: linux (Ubuntu Zesty)
   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/1678477

Title:
  Kernel has troule recognizing Corsair Strafe RGB keyboard

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  New

Bug description:
  I recently bought a Corsair Strafe RGB keyboard, and while it works
  well when successfully recognized by Ubuntu at boot, that doesn't
  always happen.

  I see messages like this when booting my desktop up:

  [6.619510] usb 3-10: unable to read config index 0 descriptor/all
  [6.619543] usb 3-10: can't read configurations, error -110

  They sometimes repeat at 5-second intervals, culminating on a "can't
  set config #1" message or even "unable to enumerate USB device". This
  happens on the logic that deals with a new USB device being connected,
  so when it doesn't work it never gets to the HID drivers part of the
  code. When it does, hid-generic is quite able to control the keyboard,
  though this message appears on dmesg:

  [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt
  endpoint

  
  From what I have been able to determine, the Corsair Strafe RGB has three 
inputs, with the last one being used as input/output and having something to do 
with the LEDs. It only has a single USB configuration, though I don't know why 
it times out.

  Searching on Google has a lot of people recommending this userspace
  drive to me: https://github.com/mattanger/ckb-next , and I've tried
  it, but it seems to be more about programming lighting effects into
  the keyboard than in controlling its basic operation, which is all I'm
  interested in. Its daemon was supposed to handle that part too, but it
  didn't fix those connection errors on boot.

  I have the following boot parameter set in my kernel, following advice
  from ckb-next's README, but it doesn't see to have an appreciable
  effect on my success rate:

  usbhid.quirks=0x1B1C:0x1B20:0x2448

  ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT
  as well in an attempt to improve things, without success.

  GRUB is always able to correctly identify the keyboard and get it to
  work, too, which makes the fact that the full kernel can't always do
  it a little more frustrating.

  I would be happy to provide any extra information you require on this
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-45-generic 4.8.0-45.48
  ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
  Uname: Linux 4.8.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bira   2322 F pulseaudio
   /dev/snd/controlC0:  bira   2322 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Apr  1 10:23:52 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-24 (767 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic 
root=UUID=d1db423d-2a50-49ac-b4e7-fd50d73afaff ro quiet splash 
usbhid.quirks=0x1B1C:0x1B20:0x2448
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-45-generic N/A
   linux-backports-modules-4.8.0-45-generic  N/A
   linux-firmware1.161.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/30/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97M-D3H
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678477/+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 1713765] Re: Consider "s390/mm: avoid empty zero pages for KVM guests to avoid postcopy hangs" for Artful

[Frank Heimes]

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
   Status: New => Confirmed

** Changed in: ubuntu-z-systems
   Importance: Undecided => Medium

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => bugproxy (bugproxy)

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

Title:
  Consider "s390/mm: avoid empty zero pages for KVM guests to avoid
  postcopy hangs" for Artful

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  there is this patch in discussion [1].

  If I read correctly between the lines that is supposed to go to -stable trees 
as well as to linxu-s390x next (4.14) submissions.
  But the change is rather big and we have to consider taking that early or as 
SRU or not at all.

  I wanted to ask the kernel Team to keep an eye on that discussion and take 
the patch into consideration - IMHO it might change KVM behavior on s390 quite 
a bit.
  So I'm not sure how SRUable it is while on Artful we migth add it rather soon 
before release.

  To some extend we should wait for the discussion on the upstreaming,
  but then I wanted to make you aware asap.

  [1]: https://lists.gnu.org/archive/html/qemu-
  devel/2017-08/msg05286.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1713765/+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 1707921] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2017-09-11 06:33 EDT---
Commit IDs available for integration...

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

Title:
  [17.10 FEAT] SCM multi-queue support

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  The upstream Linux kernel developers indicated that the traditional 
single-queue block layer interface will be deprecated in the near future.
  Block device drivers using this interface must be migrated to the new 
multi-queue Linux block layer (blk-mq) interface to remain compatible with 
future versions of the Linux kernel.x

  Commit information:
  s390/scm: remove cluster option [94d26bf (+3/-361)
  s390/scm: convert to blk-mq [12d9076] (+74/-65)   
  s390/scm: convert tasklet [c7b3e923] (+15/-40)
  s390/scm: use multiple queues [9861dbd] (+42/-13) 
  s390/cio: introduce io_subchannel_type [36f6237] (+50/-99)
  s390/pci: don't cleanup in arch_setup_msi_irqs [795818e] (+18/-29)
  s390/pci: improve error handling during interrupt deregistration [4dfbd3e] 
(+25/-16)
  s390/pci: improve unreg_ioat error handling [7257083] (+17/-6)
  s390/pci: improve error handling during fmb (de)registration [4e5bd78] 
(+21/-30)
  s390/pci: introduce clp_get_state [783684f] (+47/-14)
  s390/pci: improve pci hotplug [623bd44] (+21/-3)
  s390/pci: fix handling of PEC 306 [01553d9] (+24/-32)
  s390/pci: provide more debug information [be2c367] (+4/-2)
  s390/pci: recognize name clashes with uids [312e846] (+11/-1)
  genirq/debugfs: Fix build for !CONFIG_IRQ_DOMAIN [e5682b4] (+3/-1)
  s390/dasd: remove unneeded code [4bca698] (+3/-5)
  s390/vfio_ccw: remove unused variable [c14b7a8] (+0/-2)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1707921/+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 1716368] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s!
  [kworker/2:10:3467]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.12.0-12.13-generic 4.12.8

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-12-generic 4.12.0-12.13 [modified: 
boot/vmlinuz-4.12.0-12-generic]
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  david  1293 F pulseaudio
   /dev/snd/controlC0:  david  1293 F pulseaudio
   /dev/snd/controlC1:  david  1293 F pulseaudio
  Date: Mon Sep 11 11:30:46 2017
  Failure: oops
  InstallationDate: Installed on 2017-09-10 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170904)
  IwConfig:
   eno1  no wireless extensions.
   
   enp5s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-12-generic 
root=UUID=b66faf19-2c41-4a84-bd17-864f9f1a5db1 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! 
[kworker/2:10:3467]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2906
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H97-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2906:bd02/24/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH97-PRO:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716368/+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 1716368] [NEW] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [kworker/2:10:3467]

[David]

Public bug reported:

Ubuntu 4.12.0-12.13-generic 4.12.8

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.12.0-12-generic 4.12.0-12.13 [modified: 
boot/vmlinuz-4.12.0-12-generic]
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  david  1293 F pulseaudio
 /dev/snd/controlC0:  david  1293 F pulseaudio
 /dev/snd/controlC1:  david  1293 F pulseaudio
Date: Mon Sep 11 11:30:46 2017
Failure: oops
InstallationDate: Installed on 2017-09-10 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170904)
IwConfig:
 eno1  no wireless extensions.
 
 enp5s0no wireless extensions.
 
 lono wireless extensions.
MachineType: ASUS All Series
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-12-generic 
root=UUID=b66faf19-2c41-4a84-bd17-864f9f1a5db1 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
RfKill:
 
SourcePackage: linux
Title: NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [kworker/2:10:3467]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/24/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2906
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H97-PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2906:bd02/24/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH97-PRO:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS

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


** Tags: amd64 apport-kerneloops artful kernel-oops

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/1716368/+attachment/4947836/+files/lspci-vnvn.log

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s!
  [kworker/2:10:3467]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.12.0-12.13-generic 4.12.8

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-12-generic 4.12.0-12.13 [modified: 
boot/vmlinuz-4.12.0-12-generic]
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  david  1293 F pulseaudio
   /dev/snd/controlC0:  david  1293 F pulseaudio
   /dev/snd/controlC1:  david  1293 F pulseaudio
  Date: Mon Sep 11 11:30:46 2017
  Failure: oops
  InstallationDate: Installed on 2017-09-10 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170904)
  IwConfig:
   eno1  no wireless extensions.
   
   enp5s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-12-generic 
root=UUID=b66faf19-2c41-4a84-bd17-864f9f1a5db1 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! 
[kworker/2:10:3467]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2906
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H97-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2906:bd02/24/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH97-PRO:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  

[Kernel-packages] [Bug 1708399] Re: kernel panic -not syncing: Fatal exception: panic_on_oops

[Frank Heimes]

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

** Changed in: ubuntu-z-systems
   Status: New => In Progress

** Changed in: ubuntu-z-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/1708399

Title:
  kernel panic -not syncing: Fatal exception: panic_on_oops

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  == Comment: #0 - QI YE  - 2017-08-02 04:11:25 ==
  ---Problem Description---
  Ubuntu got kernel panic

  ---uname output---
  #110-Ubuntu SMP Tue Jul 18 12:56:43 UTC 2017 s390x s390x s390x GNU/Linux
   
  ---Debugger Data---
  PID: 10991  TASK: 19872a0e8 CPU: 2   COMMAND: "hyperkube"
   LOWCORE INFO:
-psw  : 0x0004c0018000 0x00115fa6
-function : pcpu_delegate at 115fa6
-prefix   : 0x7fe42000
-cpu timer: 0x7ffab2827828aa50
-clock cmp: 0xd2eb8b31445e4200
-general registers:
   0x0004e001 0x001283b6
   0xc001 0x8380fcb8
   0x00115f9e 0x0056f6e2
   0x0004 0x00cf9070
   0x0001f3bfc000 0x00112fd8
   0x0001c72bb400 0x0002
   0x7fffc000 0x007c9ef0
   0x00115f9e 0x8380fc18
-access registers:
   0x03ff 0x7910 00 00
   00 00 00 00
   00 00 00 00
   00 00 00 00
-control registers:
   0x14066a12 0x7e6d81c7
   0x00011140 00
   0x2aef 0x0400
   0x5000 0x7e6d81c7
   00 00
   00 00
   00 0x00cfc007
   0xdb00 0x00011280
-floating point registers:
   0x409c7e258000 0x401de4e0
   00 0x3fd24407ab0e073a
   0x3ff0 0x3fee
   0x3fef218f8a7a41a0 0x3fee
   0x0080 00
   0x03ff7f80 0x02aa4940e9e0
   0xd401 0x03ffe81fe110
   00 0x03fff2cfe638

   #0 [8380fc78] smp_find_processor_id at 1160f8
   #1 [8380fc90] machine_kexec at 1135d4
   #2 [8380fcb8] crash_kexec at 1fbb8a
   #3 [8380fd88] panic at 27d0e0
   #4 [8380fe28] die at 1142cc
   #5 [8380fe90] do_low_address at 12215e
   #6 [8380fea8] pgm_check_handler at 7c2ab4
   PSW:  070520018000 02aa267e0e42 (user space)
   GPRS:   02aa2c4fd690 0001
 02aa2c4fd690 03ff7fffee38  0002
 00029c0f 00c42001ea00 0001 0001
 00c42001c5c8 00c42082c1a0 02aa2666325e 03ff7fffed90 
   
  Contact Information = Chee Ye / y...@cn.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   [43200.761465] docker0: port 10(vethb9132e9) entered forwarding state
  [50008.560926] hrtimer: interrupt took 1698076 ns
  [123483.768984] systemd[1]: apt-daily.timer: Adding 7h 34min 22.582204s 
random time.
  [123483.930058] systemd[1]: apt-daily.timer: Adding 2h 18min 14.857162s 
random time.
  [123484.064879] systemd[1]: apt-daily.timer: Adding 10h 46min 2.301756s 
random time.
  [123484.824760] systemd[1]: apt-daily.timer: Adding 6h 16min 22.178655s 
random time.
  [153113.703126] conntrack: generic helper won't handle protocol 47. Please 
consider loading the specific helper module.
  [477085.704538] Low-address protection: 0004 ilc:2 [#1] SMP
  [477085.704551] Modules linked in: xt_physdev veth xt_recent xt_comment 
xt_mark xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 xt_addrtype nf_nat br_netfilter bridge stp llc aufs 
ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 
xt_conntrack nf_conntrack iptable_filter ip_tables x_tables ghash_s390 prng 
aes_s390 des_s390 des_generic sha512_s390 qeth_l2 sha256_s390 qeth sha1_s390 
qdio sha_common ccwgroup vmur dasd_eckd_mod dasd_mod
  [477085.705522] CPU: 2 PID: 10991 Comm: hyperkube Not tainted 
4.4.0-87-generic #110-Ubuntu
  [477085.705525] task: 00019872a0e8 ti: 8380c000 task.ti: 
8380c000
  [477085.705529] User PSW : 070520018000 02aa267e0e42
  [477085.705532]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
EA:3
  User GPRS:   02aa2c4fd690 
0001
  [477085.705539]02aa2c4fd690 03ff7fffee38  
0002
  [477085.705553]00029c0f 00c42001ea00 0001 

[Kernel-packages] [Bug 1711104] Re: [P9][Ubuntu 16.04.03] Additional PMU fixes for P9

[Frank Heimes]

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

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

Title:
  [P9][Ubuntu 16.04.03] Additional PMU fixes for P9

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

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2017-08-16 
04:07:45 ==
  Please integrate the following PMU fixes for P9.

  93fc5ca9a0048c ('powerpc/perf: Cleanup of PM_BR_CMPL vs. PM_BRU_CMPL in 
Power9 event list')
  91e0bd1e62519b ('powerpc/perf: Add PM_LD_MISS_L1 and PM_BR_2PATH to power9 
event list')
  70a7e720998d5b ('powerpc/perf: Factor out PPMU_ONLY_COUNT_RUN check code from 
power8')
  7aa345d84245a7 ('powerpc/perf: Update default sdar_mode value for power9')
  101dd590a7fa37 ('powerpc/perf: Avoid spurious PMU interrupts after idle')
  bdd21ddb919d28 ('powerpc/perf: Avoid spurious PMU interrupts after idle on 
Power9')
  3f0bd8dad0db73 ('powerpc/perf: Add POWER9 alternate PM_RUN_CYC and 
PM_RUN_INST_CMPL events')
  20dd4c624d2515 ('powerpc/perf: Fix SDAR_MODE value for continous sampling on 
Power9')
  24bedcb7c81137 ('powerpc/perf: Fix branch event code for power9')
  8c218578fcbbbd ('powerpc/perf: Fix Power9 test_adder fields')

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1711104/+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 1712724] Re: s390 zKVM complains about "illegal operation" to s390/mm/pgalloc.c

[Frank Heimes]

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

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

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => bugproxy (bugproxy)

** Changed in: ubuntu-z-systems
   Importance: Undecided => Medium

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

Title:
  s390 zKVM complains about "illegal operation" to s390/mm/pgalloc.c

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

Bug description:
  [  543.516708] kernel BUG at 
/build/linux-a7axPg/linux-4.12.0/arch/s390/mm/pgalloc.c:84!
  [  543.516783] illegal operation: 0001 ilc:1 [#1] SMP 
  [  543.516785] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat xt_tcpudp bridge stp llc iptable_filter 
openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack binfmt_misc zfs(PO) zunicode(PO) 
zavl(PO) zcommon(PO) znvpair(PO) spl(O) vfio_ccw vfio_mdev mdev 
vfio_iommu_type1 vfio ib_iser rdma_cm iw_cm ib_cm ib_core nfsd iscsi_tcp 
auth_rpcgss nfs_acl lockd grace libiscsi_tcp libiscsi sunrpc 
scsi_transport_iscsi ip_tables x_tables btrfs zlib_deflate raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 linear ghash_s390 prng aes_s390 des_s390 des_generic 
sha512_s390 sha256_s390 virtio_net sha1_s390 sha_common virtio_blk virtio_scsi
  [  543.516828] CPU: 0 PID: 10024 Comm: task-size-overr Tainted: P   O 
   4.12.0-12-generic #13-Ubuntu
  [  543.516829] Hardware name: IBM 2964 N63 400 (KVM/Linux)
  [  543.516830] task: 0cdb9e00 task.stack: 099e8000
  [  543.516831] Krnl PSW : 0704d0018000 001274ec 
(crst_table_upgrade+0x124/0x130)
  [  543.516841]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 
RI:0 EA:3
  [  543.516842] Krnl GPRS: 0001 0400 243d7800 
0020
  [  543.516843]1000  0032 

  [  543.516844]8000 0020  
1000
  [  543.516845]0020 243d7800 001239f6 
099ebbe0
  [  543.516853] Krnl Code: 001274de: c0e5002446c1  brasl   
%r14,5b0260
  [  543.516853]001274e4: a7f4ffb8  brc 
15,127454
  [  543.516853]   #001274e8: a7f40001  brc 
15,1274ea
  [  543.516853]   >001274ec: a728fff4  lhi %r2,-12
  [  543.516853]001274f0: a7f4ffee  brc 
15,1274cc
  [  543.516853]001274f4: 0707  bcr 0,%r7
  [  543.516853]001274f6: 0707  bcr 0,%r7
  [  543.516853]001274f8: c004  brcl0,1274f8
  [  543.516862] Call Trace:
  [  543.516864] ([<085d8578>] 0x85d8578)
  [  543.516868]  [<002f529a>] get_unmapped_area+0x72/0x120 
  [  543.516870]  [<002f931a>] do_mmap+0xfa/0x3e0 
  [  543.516873]  [<002d6292>] vm_mmap_pgoff+0xca/0x120 
  [  543.516874]  [<002f6962>] SyS_mmap_pgoff+0x10a/0x2a0 
  [  543.516875]  [<002f6b72>] SyS_old_mmap+0x7a/0xa8 
  [  543.516880]  [<00864c1c>] system_call+0xc4/0x27c 
  [  543.516881] Last Breaking-Event-Address:
  [  543.516882]  [<001274e8>] crst_table_upgrade+0x120/0x130
  [  543.516883]  
  [  543.516883] ---[ end trace 036f94bf79a83905 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-12-generic 4.12.0-12.13
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic s390x
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  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: 'aplay'
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Thu Aug 24 05:01:08 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=d86dc8de-6ac8-4e4b-aba8-92872a209a8c 
crashkernel=196M
  RelatedPackageVersions:
   linux-restricted-modules-4.12.0-12-generic N/A
   linux-backports-modules-4.12.0-12-generic  N/A
   

[Kernel-packages] [Bug 1697395] Re: Thunderbolt devices don't work if connected during boot

[Yehezkel Bernat]

FYI, the patches that Mario mentioned above landed Linus' tree for v4.14-rc1 
and hopefully will be backported to 4.13.
See details here:
https://github.com/01org/thunderbolt-software-user-space/issues/24#issuecomment-328011428

** Bug watch added: github.com/01org/thunderbolt-software-user-space/issues #24
   https://github.com/01org/thunderbolt-software-user-space/issues/24

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

Title:
  Thunderbolt devices don't work if connected during boot

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I am using a Dell XP 15 9550, if my Dockingstation (Dell TB16) is
  connected during boot time, all the USB devices (like Keyboard,
  Ethernet, ...) are only working while in grub boot menu. After booting
  they stop working.

  The two 4k screens which are connected to the dock, are working
  properly in boot menu and after booting. If booting into Windows
  everything is working, only linux is affected.

  Disconnecting and reconnecting the dock solves this problem.

  I have created the bug-report directly after boot, where the USB
  devices are not working and attached "lspci-vnvn_after_reconnect.log"
  after reconnecting the dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-22-generic 4.10.0-22.24
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andre_duewel   3163 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Mon Jun 12 11:17:26 2017
  InstallationDate: Installed on 2017-04-12 (60 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed 
root=UUID=0ba04b8b-151f-4522-81a8-b6b01352ea35 ro quiet splash 
nvme_core.default_ps_max_latency_us=6000 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-22-generic N/A
   linux-backports-modules-4.10.0-22-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.19:bd12/22/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697395/+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 1716332] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  HP Thunderbolt 3 Dock (90W): USB does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  i'm using a Lenovo Carbon x1 (5th generation) with a HP Thunderbolt 3
  dock (90W version). All ports are working, except USB Ports - for ~30
  minutes. After ~30 minutes, also the USB ports get activated.

  While waiting for that, dmesg shows something like a "loop" through
  usb devices:

  [...]
  [  389.023845] usb 3-1: new high-speed USB device number 55 using xhci_hcd
  [  389.491841] usb 3-1: new high-speed USB device number 56 using xhci_hcd
  [  389.959928] usb 3-1: new high-speed USB device number 57 using xhci_hcd
  [  390.427925] usb 3-1: new high-speed USB device number 58 using xhci_hcd
  [  390.895832] usb 3-1: new high-speed USB device number 59 using xhci_hcd
  [  391.363817] usb 3-1: new high-speed USB device number 60 using xhci_hcd
  [  391.831818] usb 3-1: new high-speed USB device number 61 using xhci_hcd
  [  392.299759] usb 3-1: new high-speed USB device number 62 using xhci_hcd
  [  392.771813] usb 3-1: new high-speed USB device number 63 using xhci_hcd
  [  393.239765] usb 3-1: new high-speed USB device number 64 using xhci_hcd
  [...]

  Some lines which might be interesting:
  [   13.908506] usb 3-2: 2:1: cannot get freq at ep 0x1
  [   14.058807] usb 3-2: 2:1: cannot get freq at ep 0x1
  [   14.210694] usb 3-2: 2:1: cannot get freq at ep 0x1

  Best regards
  Matthias

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mlohr  5068 F pulseaudio
   /dev/snd/controlC0:  mlohr  5068 F pulseaudio
   /dev/snd/seq:timidity   1311 F timidity
  Date: Mon Sep 11 09:34:54 2017
  HibernationDevice: RESUME=UUID=50da97f8-11c6-4a09-979a-313bba30057d
  InstallationDate: Installed on 2017-04-12 (151 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: LENOVO 20HRCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=6216746e-6b05-4609-9464-e4322637d512 ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET37W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716332/+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 1716332] Re: HP Thunderbolt 3 Dock (90W): USB does not work

[Matthias Lohr]

** Summary changed:

- Thunderbolt 3 Dock - USB does not work
+ HP Thunderbolt 3 Dock (90W): USB does not work

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

Title:
  HP Thunderbolt 3 Dock (90W): USB does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  i'm using a Lenovo Carbon x1 (5th generation) with a HP Thunderbolt 3
  dock (90W version). All ports are working, except USB Ports - for ~30
  minutes. After ~30 minutes, also the USB ports get activated.

  While waiting for that, dmesg shows something like a "loop" through
  usb devices:

  [...]
  [  389.023845] usb 3-1: new high-speed USB device number 55 using xhci_hcd
  [  389.491841] usb 3-1: new high-speed USB device number 56 using xhci_hcd
  [  389.959928] usb 3-1: new high-speed USB device number 57 using xhci_hcd
  [  390.427925] usb 3-1: new high-speed USB device number 58 using xhci_hcd
  [  390.895832] usb 3-1: new high-speed USB device number 59 using xhci_hcd
  [  391.363817] usb 3-1: new high-speed USB device number 60 using xhci_hcd
  [  391.831818] usb 3-1: new high-speed USB device number 61 using xhci_hcd
  [  392.299759] usb 3-1: new high-speed USB device number 62 using xhci_hcd
  [  392.771813] usb 3-1: new high-speed USB device number 63 using xhci_hcd
  [  393.239765] usb 3-1: new high-speed USB device number 64 using xhci_hcd
  [...]

  Some lines which might be interesting:
  [   13.908506] usb 3-2: 2:1: cannot get freq at ep 0x1
  [   14.058807] usb 3-2: 2:1: cannot get freq at ep 0x1
  [   14.210694] usb 3-2: 2:1: cannot get freq at ep 0x1

  Best regards
  Matthias

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mlohr  5068 F pulseaudio
   /dev/snd/controlC0:  mlohr  5068 F pulseaudio
   /dev/snd/seq:timidity   1311 F timidity
  Date: Mon Sep 11 09:34:54 2017
  HibernationDevice: RESUME=UUID=50da97f8-11c6-4a09-979a-313bba30057d
  InstallationDate: Installed on 2017-04-12 (151 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: LENOVO 20HRCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=6216746e-6b05-4609-9464-e4322637d512 ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET37W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716332/+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 1716332] Re: Thunderbolt 3 Dock - USB does not work

[Matthias Lohr]

Btw: HP Thunderbolt Dock 65W variant works like a charm, without his problem.
USB devices (e.g. USB Keyboard) works, e.g. for boot selection, before booting 
the linux 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/1716332

Title:
  Thunderbolt 3 Dock - USB does not work

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  i'm using a Lenovo Carbon x1 (5th generation) with a HP Thunderbolt 3
  dock (90W version). All ports are working, except USB Ports - for ~30
  minutes. After ~30 minutes, also the USB ports get activated.

  While waiting for that, dmesg shows something like a "loop" through
  usb devices:

  [...]
  [  389.023845] usb 3-1: new high-speed USB device number 55 using xhci_hcd
  [  389.491841] usb 3-1: new high-speed USB device number 56 using xhci_hcd
  [  389.959928] usb 3-1: new high-speed USB device number 57 using xhci_hcd
  [  390.427925] usb 3-1: new high-speed USB device number 58 using xhci_hcd
  [  390.895832] usb 3-1: new high-speed USB device number 59 using xhci_hcd
  [  391.363817] usb 3-1: new high-speed USB device number 60 using xhci_hcd
  [  391.831818] usb 3-1: new high-speed USB device number 61 using xhci_hcd
  [  392.299759] usb 3-1: new high-speed USB device number 62 using xhci_hcd
  [  392.771813] usb 3-1: new high-speed USB device number 63 using xhci_hcd
  [  393.239765] usb 3-1: new high-speed USB device number 64 using xhci_hcd
  [...]

  Some lines which might be interesting:
  [   13.908506] usb 3-2: 2:1: cannot get freq at ep 0x1
  [   14.058807] usb 3-2: 2:1: cannot get freq at ep 0x1
  [   14.210694] usb 3-2: 2:1: cannot get freq at ep 0x1

  Best regards
  Matthias

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mlohr  5068 F pulseaudio
   /dev/snd/controlC0:  mlohr  5068 F pulseaudio
   /dev/snd/seq:timidity   1311 F timidity
  Date: Mon Sep 11 09:34:54 2017
  HibernationDevice: RESUME=UUID=50da97f8-11c6-4a09-979a-313bba30057d
  InstallationDate: Installed on 2017-04-12 (151 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: LENOVO 20HRCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=6216746e-6b05-4609-9464-e4322637d512 ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET37W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716332/+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 1716332] [NEW] Thunderbolt 3 Dock - USB does not work

[Matthias Lohr]

Public bug reported:

Hello,

i'm using a Lenovo Carbon x1 (5th generation) with a HP Thunderbolt 3
dock (90W version). All ports are working, except USB Ports - for ~30
minutes. After ~30 minutes, also the USB ports get activated.

While waiting for that, dmesg shows something like a "loop" through usb
devices:

[...]
[  389.023845] usb 3-1: new high-speed USB device number 55 using xhci_hcd
[  389.491841] usb 3-1: new high-speed USB device number 56 using xhci_hcd
[  389.959928] usb 3-1: new high-speed USB device number 57 using xhci_hcd
[  390.427925] usb 3-1: new high-speed USB device number 58 using xhci_hcd
[  390.895832] usb 3-1: new high-speed USB device number 59 using xhci_hcd
[  391.363817] usb 3-1: new high-speed USB device number 60 using xhci_hcd
[  391.831818] usb 3-1: new high-speed USB device number 61 using xhci_hcd
[  392.299759] usb 3-1: new high-speed USB device number 62 using xhci_hcd
[  392.771813] usb 3-1: new high-speed USB device number 63 using xhci_hcd
[  393.239765] usb 3-1: new high-speed USB device number 64 using xhci_hcd
[...]

Some lines which might be interesting:
[   13.908506] usb 3-2: 2:1: cannot get freq at ep 0x1
[   14.058807] usb 3-2: 2:1: cannot get freq at ep 0x1
[   14.210694] usb 3-2: 2:1: cannot get freq at ep 0x1

Best regards
Matthias

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-33-generic 4.10.0-33.37
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  mlohr  5068 F pulseaudio
 /dev/snd/controlC0:  mlohr  5068 F pulseaudio
 /dev/snd/seq:timidity   1311 F timidity
Date: Mon Sep 11 09:34:54 2017
HibernationDevice: RESUME=UUID=50da97f8-11c6-4a09-979a-313bba30057d
InstallationDate: Installed on 2017-04-12 (151 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
MachineType: LENOVO 20HRCTO1WW
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=6216746e-6b05-4609-9464-e4322637d512 ro quiet splash vt.handoff=7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-33-generic N/A
 linux-backports-modules-4.10.0-33-generic  N/A
 linux-firmware 1.164.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: N1MET37W (1.22 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HRCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20HRCTO1WW
dmi.product.version: ThinkPad X1 Carbon 5th
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug zesty

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

Title:
  Thunderbolt 3 Dock - USB does not work

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  i'm using a Lenovo Carbon x1 (5th generation) with a HP Thunderbolt 3
  dock (90W version). All ports are working, except USB Ports - for ~30
  minutes. After ~30 minutes, also the USB ports get activated.

  While waiting for that, dmesg shows something like a "loop" through
  usb devices:

  [...]
  [  389.023845] usb 3-1: new high-speed USB device number 55 using xhci_hcd
  [  389.491841] usb 3-1: new high-speed USB device number 56 using xhci_hcd
  [  389.959928] usb 3-1: new high-speed USB device number 57 using xhci_hcd
  [  390.427925] usb 3-1: new high-speed USB device number 58 using xhci_hcd
  [  390.895832] usb 3-1: new high-speed USB device number 59 using xhci_hcd
  [  391.363817] usb 3-1: new high-speed USB device number 60 using xhci_hcd
  [  391.831818] usb 3-1: new high-speed USB device number 61 using xhci_hcd
  [  392.299759] usb 3-1: new high-speed USB device number 62 using xhci_hcd
  [  392.771813] usb 3-1: new high-speed USB device number 63 using xhci_hcd
  [  393.239765] usb 3-1: new high-speed USB device number 64 using xhci_hcd
  [...]

  Some lines which might be interesting:
  [   13.908506] usb 3-2: 2:1: cannot get freq at ep 0x1
  [   14.058807] usb 3-2: 2:1: cannot get freq at ep 0x1
  [   14.210694] usb 3-2: 2:1: cannot get freq at ep 0x1

  Best regards
  Matthias

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  

[Kernel-packages] [Bug 1270676] Re: SD Card Reader broken on UX302LG

[Dylan Borg]

Is there anyone who tried to upstream the au6601 driver? Its till seems
like there is no upstream driver for Alcor Micro card readers.

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

Title:
  SD Card Reader broken on UX302LG

Status in linux package in Ubuntu:
  Triaged

Bug description:
  SD card reader (controller Alcor Micro AU6601) is dysfunctional in UX302LG 
laptop. USB readers work without problem. Nothing happens when pluggin 
SD/mSD/SDHC/mSDHC cards in the reader (might as well use a piece of wood).
  Nothing is listed in lsusb -v that could be the reader.
  Nohting is listed in lspci -k -vv -nnn.
  Nothing in acpi_listen.
  Nothing in kern.log etc.

  According to (select "Windows 8" then "Card Reader") :
  
http://support.asus.com/download.aspx?SLanguage=en=3=597=UX302LG==GEZaY8oaj8oSlQ3U

  Reader vendor is :
  Alcor Multi-Card Reader Driver
  http://www.pcidatabase.com/vendor_details.php?id=1672

  There is only one device that is "Unassigned class" 1aea:6601 but
  searching this online only pops up my other bug reports (sigh) and
  vendor is unassigned on pcidatabase.com.

  But...Downloading the 14M Win driver for the reader, vendor id 1aea and 
device id 6601 is present at multiple instances :
  [DeviceList.NTamd64]
  ; For XP and later
  %AMPCIECR% = DriverInstall_6601, PCI\VEN_1aea_6601

  Also there is mention of _Gen instance in the .inf, might point to a 
"Generic" alternative ?
  [DeviceList_Gen.NTamd64]
  ; For XP and later
  %AMPCIECR_GEN% = DriverInstall_Gen, PCI\VEN_105b_0ef6

  This does point to something totally different online 105b:0ef6 points to 
some Realtek HD Audio device...
  ---
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-12-31 (21 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131231)
  Package: linux (not installed)
  Tags:  trusty
  Uname: Linux 3.13.0-031300-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  ---
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=e6458b44-fdb9-4db5-8cac-40ee0bbf9cf6
  InstallationDate: Installed on 2013-12-31 (21 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131231)
  MachineType: ASUSTeK COMPUTER INC. UX302LG
  Package: linux (not installed)
  ProcFB: 0 simple
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-4-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi= nomodeset 
plymouth:debug vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-4-generic N/A
   linux-backports-modules-3.13.0-4-generic  N/A
   linux-firmware1.121
  Tags:  trusty
  Uname: Linux 3.13.0-4-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 10/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX302LG.207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX302LG
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX302LG.207:bd10/30/2013:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX302LG
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270676/+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 1715064] Re: 17.10 fails to boot on POWER9 DD2.0 with Deep stop states

[Frank Heimes]

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

Title:
  17.10 fails to boot on POWER9 DD2.0 with Deep stop states

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

Bug description:
  == Comment: #0 - Ranjal G. Shenoy
  On Boston DD2.0 system, where deep stop states such as stop4 are enabled, the 
17.10 kernel Ubuntu-4.12.0-12.13 fails to boot.

  It requires the following upstream fixes to be backported.

  1) commit 5f221c3ca13d ("powerpc/powernv/idle: Correctly initialize 
core_idle_state_ptr")
  2) commit ec4867355244 ("powerpc/powernv/idle: Decouple Timebase restore & 
Per-core SPRs restore")
  3) commit cb0be7ec0307 ("powerpc/powernv/idle: Restore LPCR on wakeup from 
deep-stop")
  4) commit 1e1601b38e6e ("powerpc/powernv/idle: Restore SPRs for deep idle 
states via stop API.")
  5) commit 22c6663dc69a ("powerpc/powernv/idle: Use Requested Level for 
restoring state on P9 DD1")
  6) commit f9122ee4f558 ("cpuidle-powernv: Allow Deep stop states that don't 
stop time")
  7) commit 785a12afdb4a ("powerpc/powernv/idle: Disable LOSE_FULL_CONTEXT 
states when stop-api fails")
  8) commit e1c1cfed5432 ("powerpc/powernv: Save/Restore additional SPRs for 
stop4 cpuidle")
  9) commit 24be85a23d1f ("powerpc/powernv: Clear PECE1 in LPCR via stop-api 
only on Hotplug")
  10) https://patchwork.ozlabs.org/patch/808233/ ("powerpc/powernv: Clear 
LPCR[PECE1] via stop-api only for deep state offline")

  Of these 1-7 are in Linux Kernel 4.13. 8 and 9 are in
  powerpc/linux.git -next branch. and 10) is posted upstream which fixes
  9).

  These patches have been backported on top of  Ubuntu-4.12.0-12.13 and
  tested on Boston where they are working as expected.

  == Comment: #1 - Ranjal G. Shenoy 
 
  The lower 8 bits of core_idle_state_ptr tracks the number of non-idle
  threads in the core. This is supposed to be initialized to bit-map
  corresponding to the threads_per_core. However, currently it is
  initialized to PNV_CORE_IDLE_THREAD_BITS (0xFF). This is correct for
  POWER8 which has 8 threads per core, but not for POWER9 which has 4
  threads per core.
  
  As a result, on POWER9, core_idle_state_ptr gets initialized to
  0xFF. In case when all the threads of the core are idle, the bits
  corresponding tracking the idle-threads are non-zero. As a result, the
  idle entry/exit code fails to save/restore per-core hypervisor state
  since it assumes that there are threads in the cores which are still
  active.
  
  Fix this by correctly initializing the lower bits of the
  core_idle_state_ptr on the basis of threads_per_core.
  
  Cherry-picked from commit 5f221c3ca13d ("powerpc/powernv/idle:
  Correctly initialize core_idle_state_ptr")

  == Comment: #2 - Ranjal G. Shenoy 
 On POWER8, in case of
 -  nap: both timebase and hypervisor state is retained.
 -  fast-sleep: timebase is lost. But the hypervisor state is retained.
 -  winkle: timebase and hypervisor state is lost.
  
  Hence, the current code for handling exit from a idle state assumes
  that if the timebase value is retained, then so is the hypervisor
  state. Thus, the current code doesn't restore per-core hypervisor
  state in such cases.
  
  But that is no longer the case on POWER9 where we do have stop states
  in which timebase value is retained, but the hypervisor state is
  lost. So we have to ensure that the per-core hypervisor state gets
  restored in such cases.
  
  Fix this by ensuring that even in the case when timebase is retained,
  we explicitly check if we are waking up from a deep stop that loses
  per-core hypervisor state (indicated by cr4 being eq or gt), and if
  this is the case, we restore the per-core hypervisor state.
  
  Cherry-picked from commit ec4867355244 ("powerpc/powernv/idle:
  Decouple Timebase restore & Per-core SPRs restore")

  == Comment: #3 - Ranjal G. Shenoy 
 On wakeup from a deep stop state which is supposed to lose the
  hypervisor state, we don't restore the LPCR to the old value but set
  it to a "sane" value via cur_cpu_spec->cpu_restore().
  
  The problem is that the "sane" value doesn't include UPRT and the HR
  bits which are required to run correctly in Radix mode.
  
  Fix this on POWER9 onwards by restoring the LPCR value whatever it was
  before executing the stop instruction.
  
  Cherry-picked from commit cb0be7ec0307 ("powerpc/powernv/idle: Restore
  LPCR on wakeup from deep-stop")

  == Comment: #4 - Ranjal G. Shenoy 
 Some of the SPR values (HID0, MSR, SPRG0) 

[Kernel-packages] [Bug 1714859] Re: oops in 4.4.0-62-generic (ppc64le)

[Daniel Black]

fyi - did more testing - seems to not to affect x86_64 - detailed test
should appear in https://lists.ozlabs.org/pipermail/linuxppc-dev soon.

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

Title:
  oops in 4.4.0-62-generic (ppc64le)

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Confirmed

Bug description:
  Sep  1 14:23:30 p87 kernel: [17274563.423972] device vnet2 entered 
promiscuous mode
  Sep  1 14:23:30 p87 kernel: [17274563.436101] br0: port 4(vnet2) entered 
forwarding state
  Sep  1 14:23:30 p87 kernel: [17274563.436113] br0: port 4(vnet2) entered 
forwarding state
  Sep  1 14:23:31 p87 kernel: [17274564.005034] audit: type=1400 
audit(1504239811.140:793): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5" 
pid=18952 comm="apparmor_parser"
  Sep  1 14:23:31 p87 kernel: [17274564.019911] audit: type=1400 
audit(1504239811.156:794): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" 
name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5//qemu_bridge_helper" 
pid=18952 comm="apparmor_parser"
  Sep  1 14:23:31 p87 kernel: [17274564.324291] KVM guest htab at 
c079a100 (order 29), LPID 3
  Sep  1 14:23:45 p87 kernel: [17274578.483572] br0: port 4(vnet2) entered 
forwarding state
  Sep  1 14:26:53 p87 kernel: [17274766.572284] br0: port 4(vnet2) entered 
disabled state
  Sep  1 14:26:53 p87 kernel: [17274766.579930] device vnet2 left promiscuous 
mode
  Sep  1 14:26:53 p87 kernel: [17274766.579932] br0: port 4(vnet2) entered 
disabled state
  Sep  1 14:26:54 p87 kernel: [17274767.303109] audit: type=1400 
audit(1504240014.441:795): apparmor="STATUS" operation="profile_remove" 
profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5" 
pid=22668 comm="apparmor_parser"
  Sep  1 14:26:56 p87 kernel: [17274768.917394] audit: type=1400 
audit(1504240016.053:796): apparmor="STATUS" operation="profile_load" 
profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5" 
pid=22672 comm="apparmor_parser"
  Sep  1 14:26:56 p87 kernel: [17274768.917673] audit: type=1400 
audit(1504240016.053:797): apparmor="STATUS" operation="profile_load" 
profile="unconfined" 
name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5//qemu_bridge_helper" 
pid=22672 comm="apparmor_parser"
  Sep  1 14:26:56 p87 kernel: [17274768.982783] device vnet2 entered 
promiscuous mode
  Sep  1 14:26:56 p87 kernel: [17274768.994891] br0: port 4(vnet2) entered 
forwarding state
  Sep  1 14:26:56 p87 kernel: [17274768.994902] br0: port 4(vnet2) entered 
forwarding state
  Sep  1 14:26:56 p87 kernel: [17274769.535982] audit: type=1400 
audit(1504240016.673:798): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5" 
pid=22702 comm="apparmor_parser"
  Sep  1 14:26:56 p87 kernel: [17274769.546719] audit: type=1400 
audit(1504240016.685:799): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" 
name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5//qemu_bridge_helper" 
pid=22702 comm="apparmor_parser"
  Sep  1 14:26:57 p87 kernel: [17274769.861666] KVM guest htab at 
c079a100 (order 29), LPID 3
  Sep  1 14:27:11 p87 kernel: [17274784.050382] br0: port 4(vnet2) entered 
forwarding state
  Sep  1 14:28:30 p87 kernel: [17274863.605174] Unable to handle kernel paging 
request for data at address 0x0008
  Sep  1 14:28:30 p87 kernel: [17274863.605188] Faulting instruction address: 
0xc044edcc
  Sep  1 14:28:30 p87 kernel: [17274863.605195] Oops: Kernel access of bad 
area, sig: 11 [#1]
  Sep  1 14:28:30 p87 kernel: [17274863.605199] SMP NR_CPUS=2048 NUMA PowerNV
  Sep  1 14:28:30 p87 kernel: [17274863.605206] Modules linked in: tcp_diag 
inet_diag ebtable_filter ebtables binfmt_misc veth xfrm_user xfrm_algo 
vhost_net vhost macvtap macvlan xt_CHECKSUM iptable_mangle ipt_REJECT 
nf_reject_ipv4 xt_tcpudp ip6table_filter ip6_tables ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack 
br_netfilter overlay bridge stp llc kvm_hv uio_pdrv_genirq powernv_rng 
ibmpowernv vmx_crypto leds_powernv uio ipmi_powernv ipmi_msghandler kvm_pr kvm 
autofs4 xfs btrfs raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid0 multipath linear raid10 raid1 ses 
enclosure mlx4_en be2net lpfc mlx4_core vxlan ip6_udp_tunnel scsi_transport_fc 
udp_tunnel ipr [last unloaded: ebtables]
  Sep  1 14:28:30 p87 kernel: [17274863.605294] CPU: 24 PID: 19018 Comm: sshfs 
Not tainted 4.4.0-62-generic #83-Ubuntu
  Sep  1 14:28:30 p87 kernel: [17274863.605300] task: c01fc9c7c8e0 ti: 
c01fe4c1 task.ti: c01fe4c1
  Sep  1 14:28:30 p87 kernel: 

[Kernel-packages] [Bug 1045985] Re: support environment filtering

[Vincas Dargis]

This bug is rather old. Is there a progress in this? Is it relevant on
latest AppArmor?

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

Title:
  support environment filtering

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Confined applications have too much control over executables due to a
  lack of environment filtering in AppArmor. Bug #851986 is one such
  example. While we have employed the sanitized_helper to help, it
  should not be considered the final solution as it causes usability
  issues and is limited in what it can achieve. This bug is to track the
  environment filtering work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1045985/+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 1713575] Re: Vlun resize request could fail with cxlflash driver

[Frank Heimes]

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

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

Title:
  Vlun resize request could fail with cxlflash driver

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

Bug description:
  == Comment: #0 - UMA KRISHNAN  - 2017-08-28 12:14:12 ==
  ---Problem Description---
  Recently a regression in cxlflash driver was identified and a fix has been 
upstreamed to  kernel.org. We would like to get that included in Xenial 16.04.3 
SRU (HWE v4.10 kernel). Even though regression patch is the very last one, I 
have also listed the missing patches in-between, that are minor and will be 
easier for further cxlflash updates to Xenial.

  eeac8cda2c957e156093933b860eec09e488fe15 scsi: cxlflash: return -EFAULT if 
copy_from_user() fails
  9ff870417e56b1fb7b15b2cda74de639d3cd8559 scsi: cxlflash: Fix an error 
handling path in 'cxlflash_disk_attach()'
  48a17ad5931c3832eec68411620bc3527021c193 scsi: cxlflash: Remove unnecessary 
existence check
  1a9e394154e34728f58c1f697b993aaaf89a4db2 scsi: cxlflash: Avoid double mutex 
unlock
  07a191f762a7b8d0db13c38036380927116e29bb scsi: cxlflash: Fix vlun resize 
failure in the shrink path
   
  ---Steps to Reproduce---
   Vlun resize request could fail after updating to a kernel that includes 
Commit 565180723294 ("scsi: cxlflash: SISlite updates to support 4 ports")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1713575/+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 1713575] Re: Vlun resize request could fail with cxlflash driver

[bugproxy]

** Tags removed: bugnameltc-158076 kernel-da-key severity-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/1713575

Title:
  Vlun resize request could fail with cxlflash driver

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

Bug description:
  == Comment: #0 - UMA KRISHNAN  - 2017-08-28 12:14:12 ==
  ---Problem Description---
  Recently a regression in cxlflash driver was identified and a fix has been 
upstreamed to  kernel.org. We would like to get that included in Xenial 16.04.3 
SRU (HWE v4.10 kernel). Even though regression patch is the very last one, I 
have also listed the missing patches in-between, that are minor and will be 
easier for further cxlflash updates to Xenial.

  eeac8cda2c957e156093933b860eec09e488fe15 scsi: cxlflash: return -EFAULT if 
copy_from_user() fails
  9ff870417e56b1fb7b15b2cda74de639d3cd8559 scsi: cxlflash: Fix an error 
handling path in 'cxlflash_disk_attach()'
  48a17ad5931c3832eec68411620bc3527021c193 scsi: cxlflash: Remove unnecessary 
existence check
  1a9e394154e34728f58c1f697b993aaaf89a4db2 scsi: cxlflash: Avoid double mutex 
unlock
  07a191f762a7b8d0db13c38036380927116e29bb scsi: cxlflash: Fix vlun resize 
failure in the shrink path
   
  ---Steps to Reproduce---
   Vlun resize request could fail after updating to a kernel that includes 
Commit 565180723294 ("scsi: cxlflash: SISlite updates to support 4 ports")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1713575/+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 1710690] Re: Ubuntu16.04.3: System running network stress crashes with Alignment exception

[Frank Heimes]

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

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

Title:
  Ubuntu16.04.3: System running network stress crashes with Alignment
  exception

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

Bug description:
   State: Open by: nguyenp on 11 August 2017 11:03:32 

  Contact:
  ===
  Paul Nguyen
  nguy...@us.ibm.com

  BMC:
  
  bos1u1

  Firmware Revision : 00.25 
  Firmware Build Time : 20170807BMC MAC address : 0c:c4:7a:f4:4d:60
  PNOR Build Time : 20170729
  CPLD Version : B2.91.00   

  Ubuntu 16.04.3:
  ===
  bos1u1p1

 ver 1.5.4.5 - OS, HTX, Firmware and Machine details

 OS: GNU/Linux
 OS Version: Ubuntu 16.04.3 LTS \n \l
 Kernel Version: 4.11.0-12-generic
HTX Version: htxubuntu-448
  Host Name: bos1u1p1
  Machine Serial No: C819UAF32B2 
 Machine Type/Model: 9006-12C

  root@bos1u1p1:~# dpkg -l |grep mlx
  ii  libmlx4-1  41mlnx1-OFED.4.1.0.1.0.41014   
ppc64el  Userspace driver for Mellanox ConnectX 

  InfiniBand HCAs
  ii  libmlx4-1-dbg  41mlnx1-OFED.4.1.0.1.0.41014   
ppc64el  Debugging symbols for the libmlx4 driver
  ii  libmlx4-dev41mlnx1-OFED.4.1.0.1.0.41014   
ppc64el  Development files for the libmlx4 driver
  ii  libmlx5-1  41mlnx1-OFED.4.1.0.1.3.0.1.41014   
ppc64el  Userspace driver for Mellanox ConnectX 

  InfiniBand HCAs
  ii  libmlx5-1-dbg  41mlnx1-OFED.4.1.0.1.3.0.1.41014   
ppc64el  Debugging symbols for the libmlx5 driver
  ii  libmlx5-dev41mlnx1-OFED.4.1.0.1.3.0.1.41014   
ppc64el  Development files for the libmlx5 driver

  root@bos1u1p1:~# lsscsi
  [0:2:0:0]diskSEAGATE  ST4000NM0034 E005  /dev/sda 
  [0:3:123:0]  enclosu ADAPTEC  Smart Adapter2.99  -
  root@bos1u1p1:~# lspci
  :00:00.0 PCI bridge: IBM Device 04c1
  0001:00:00.0 PCI bridge: IBM Device 04c1
  0002:00:00.0 PCI bridge: IBM Device 04c1
  0002:01:00.0 Ethernet controller: Intel Corporation Ethernet Controller 
X710/X557-AT 10GBASE-T (rev 02)
  0002:01:00.1 Ethernet controller: Intel Corporation Ethernet Controller 
X710/X557-AT 10GBASE-T (rev 02)
  0002:01:00.2 Ethernet controller: Intel Corporation Ethernet Controller 
X710/X557-AT 10GBASE-T (rev 02)
  0002:01:00.3 Ethernet controller: Intel Corporation Ethernet Controller 
X710/X557-AT 10GBASE-T (rev 02)
  0003:00:00.0 PCI bridge: IBM Device 04c1
  0003:01:00.0 Serial Attached SCSI controller: Adaptec Series 8 12G SAS/PCIe 3 
(rev 01)
  0004:00:00.0 PCI bridge: IBM Device 04c1
  0004:01:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge 
(rev 04)
  0004:02:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED 
Graphics Family (rev 41)
  0005:00:00.0 PCI bridge: IBM Device 04c1
  0005:01:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 
xHCI Host Controller (rev 02)
  0030:00:00.0 PCI bridge: IBM Device 04c1
  0030:01:00.0 Infiniband controller: Mellanox Technologies Device 1019
  0030:01:00.1 Infiniband controller: Mellanox Technologies Device 1019
  0031:00:00.0 PCI bridge: IBM Device 04c1
  0031:01:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit 
SFI/SFP+ Network Connection (rev 01)
  0031:01:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit 
SFI/SFP+ Network Connection (rev 01)
  0032:00:00.0 PCI bridge: IBM Device 04c1
  0033:00:00.0 PCI bridge: IBM Device 04c1
  0033:01:00.0 Ethernet controller: Intel Corporation 82575EB Gigabit Network 
Connection (rev 02)
  0033:01:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network 
Connection (rev 02)

  root@bos1u1p1:~# ifconfig -a
  enP2p1s0f0 Link encap:Ethernet  HWaddr ac:1f:6b:09:c0:9e  
inet addr:9.3.20.217  Bcast:9.3.21.255  Mask:255.255.254.0
inet6 addr: fe80::ae1f:6bff:fe09:c09e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:62603 errors:0 dropped:0 overruns:0 frame:0
TX packets:105 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:4784741 (4.7 MB)  TX bytes:14043 (14.0 KB)

  enP2p1s0f1 Link encap:Ethernet  HWaddr ac:1f:6b:09:c0:9f  
BROADCAST MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  

[Kernel-packages] [Bug 1715073] Re: SRIOV: warning if unload VFs

[Frank Heimes]

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

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

Title:
  SRIOV: warning if unload VFs

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

Bug description:
  == Comment: #0 - Carol L. Soto  - 2017-02-23 16:11:47 ==
  ---Problem Description---
  When doing SRIOV if I unload VFs will see a warning:

  Feb 23 16:05:56 powerio-le11 kernel: [  201.343397] 
mlx5_3:wait_for_async_commands:674:(pid 6272): done with all pending requests
  Feb 23 16:05:56 powerio-le11 kernel: [  201.603999] iommu: Removing device 
0004:01:00.2 from group 7
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604078] pci 0004:01: 0.2: [PE# 
00] Removing DMA window #0
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604084] pci 0004:01: 0.2: [PE# 
00] Disabling 64-bit DMA bypass
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604350] mlx5_core 0004:01:00.0: 
VF BAR0: [mem 0x2400-0x2401 64bit pref] shifted to [mem 
0x2400-0x2401 64bit pref] (Disabling 1 VFs shifted by 0)
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604363] mlx5_core 0004:01:00.0: 
can't update enabled VF BAR0 [mem 0x2400-0x2401 64bit pref]
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604379] [ cut here 
]
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604386] WARNING: CPU: 14 PID: 
6272 at /build/linux-twbIHf/linux-4.10.0/drivers/pci/iov.c:584 
pci_iov_update_resource+0x178/0x1d0
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604388] Modules linked in: 
mlx5_ib xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp kvm_hv kvm_pr kvm 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bridge stp 
llc binfmt_misc ipmi_powernv ipmi_devintf uio_pdrv_genirq ipmi_msghandler uio 
vmx_crypto powernv_rng powernv_op_panel leds_powernv ibmpowernv ib_iser rdma_cm 
iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi knem(OE) ip_tables x_tables autofs4 btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear mlx4_en ses enclosure scsi_transport_sas 
crc32c_vpmsum mlx5_core mlx4_core
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604451]  tg3 ipr devlink
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604456] CPU: 14 PID: 6272 Comm: 
bash Tainted: G   OE   4.10.0-8-generic #10-Ubuntu
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604457] task: c00f40a6d600 
task.stack: c00f40ac8000
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604459] NIP: c06721b8 LR: 
c06721b4 CTR: 
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604461] REGS: c00f40acb590 
TRAP: 0700   Tainted: G   OE(4.10.0-8-generic)
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604462] MSR: 9282b033 

  Feb 23 16:05:56 powerio-le11 kernel: [  201.604470]   CR: 42424422  XER: 
2000
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] CFAR: c0b49db4 
SOFTE: 1
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR00: c06721b4 
c00f40acb810 c143c900 0063
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR04: 0001 
0539 c01fff70 00021a50
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR08: 0007 
0007 0001 656d5b2030524142
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR12: 4400 
cfb87e00 10180df8 10189e60
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR16: 10189ed8 
c00fdd0a2400 c01fff97d180 c0d46268
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR20: c0d4e410 
c0d41df8 c01fff97d190 c0d4d8d8
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR24: c0d4d8e0 
c00fe8f460a0 0001 
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR28: c00fe8f80f80 
 c00fe8f46580 c00fe8f46000
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604498] NIP [c06721b8] 
pci_iov_update_resource+0x178/0x1d0
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604501] LR [c06721b4] 
pci_iov_update_resource+0x174/0x1d0
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604501] Call Trace:
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604504] [c00f40acb810] 
[c06721b4] pci_iov_update_resource+0x174/0x1d0 (unreliable)
  Feb 23 16:05:56 

[Kernel-packages] [Bug 1715609] Re: kernel warning: skb_warn_bad_offload

[Jo Vanvoorden]

I'm also experiencing this issue with 4.4.0-93-generic in combination
with docker,kvm and bonding on host. Not sure if docker or kvm is
causing the warnings.

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

Title:
  kernel warning: skb_warn_bad_offload

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

Bug description:
  Since upgrading to kernel version 4.10.0-33.37, we're seeing a lot of
  call traces triggered by skb_warn_bad_offload in the syslog.

  Regression introduced when fixing this bug?
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705447


  kernel: [570943.49] [ cut here ]
  kernel: [570943.494448] WARNING: CPU: 3 PID: 21982 at 
/build/linux-hwe-YA6IuF/linux-hwe-4.10.0/net/core/dev.c:2576 
skb_warn_bad_offload+0xd1/0x120
  kernel: [570943.494450] e1000e: caps=(0x0030002149a9, 0x) 
len=1701 data_len=1659 gso_size=1480 gso_type=2 ip_summed=0
  kernel: [570943.494451] Modules linked in: udp_diag tcp_diag inet_diag 
echainiv authenc xfrm4_mode_tunnel xt_state binfmt_misc veth xfrm_user 
xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo bridge stp 
llc iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_nat_ipv4 nf_nat ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter ip_tables x_tables 
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm ppdev 
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel 
aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf hci_uart 
ie31200_edac btbcm edac_core intel_pch_thermal btqca serio_raw btintel 
bluetooth parport_pc parport mac_hid intel_lpss_acpi acpi_pad intel_lpss autofs4
  kernel: [570943.494500]  btrfs raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 
e1000e psmouse ptp ahci pps_core libahci wmi pinctrl_sunrisepoint i2c_hid video 
pinctrl_intel hid fjes
  kernel: [570943.494524] CPU: 3 PID: 21982 Comm: charon Tainted: GW
   4.10.0-33-generic #37~16.04.1-Ubuntu
  kernel: [570943.494524] Hardware name: ...
  kernel: [570943.494525] Call Trace:
  kernel: [570943.494541]  
  kernel: [570943.494544]  dump_stack+0x63/0x90
  kernel: [570943.494545]  __warn+0xcb/0xf0
  kernel: [570943.494546]  warn_slowpath_fmt+0x5f/0x80
  kernel: [570943.494547]  ? ___ratelimit+0xa2/0xf0
  kernel: [570943.494549]  skb_warn_bad_offload+0xd1/0x120
  kernel: [570943.494550]  __skb_gso_segment+0x17d/0x190
  kernel: [570943.494564]  validate_xmit_skb+0x14f/0x2a0
  kernel: [570943.494565]  validate_xmit_skb_list+0x43/0x70
  kernel: [570943.494567]  sch_direct_xmit+0x16b/0x1c0
  kernel: [570943.494568]  __dev_queue_xmit+0x47e/0x690
  kernel: [570943.494569]  dev_queue_xmit+0x10/0x20
  kernel: [570943.494570]  ip_finish_output2+0x27a/0x370
  kernel: [570943.494571]  ip_finish_output+0x176/0x270
  kernel: [570943.494571]  ip_output+0x76/0xe0
  kernel: [570943.494572]  ? ip_fragment.constprop.49+0x80/0x80
  kernel: [570943.494573]  ip_forward_finish+0x43/0x70
  kernel: [570943.494574]  ip_forward+0x385/0x460
  kernel: [570943.494575]  ? ip_frag_mem+0x50/0x50
  kernel: [570943.494575]  ip_rcv_finish+0x11b/0x400
  kernel: [570943.494576]  ip_rcv+0x28b/0x3a0
  ...
  kernel: [570943.494632] ---[ end trace f01d0adcc1256afe ]---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715609/+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 1715271] Re: Middle button of trackpoint doesn't work

[Andreas Lindhé]

Works again for me since 4.12.12-1

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

Title:
  Middle button of trackpoint doesn't work

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  Fix Committed

Bug description:
  Middle button doesn't work on several Thinkpad laptops like E570,
  E475, E470, E575 and X1Carbon.

  When middle button fails to work, logs show:
  psmouse serio2: trackpoint: failed to get extended button data

  It fails to read out ext button info via PS2 command.
  Almost all the Thinkpad have 3 buttons, so set it to 3 button when it fails 
to read button info.

  And on Lenovo X1, there is a new version of trackpoint, add this ID
  for this new device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1715271/+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