hyper-v: vmbus: Specify the target CPU that should receive notification

Bug #1295813 reported by Abhishek Gupta
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Unassigned
Trusty
Fix Released
Medium
Unassigned

Bug Description

Hi, Please include the following patch as it is required to do core dump on multiple vCPUs:

http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/patch/drivers/hv/connection.c?id=e28bab4828354583bb66ac09021ca69b341a7db4

Also please verify if the patch below is already integrated:
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/patch/drivers/hv/connection.c?id=269f979467cf49f2ea8132316c1f00f8c9678f7c

I had already filed a bug for these patches before and the issue was resolved as fix released. However it appears that we missed the first patch entirely. Please accept.

Thanks,
Abhishek

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1295813

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Abhishek Gupta (abgupta) wrote :

Issue is confirmed. No logs necessary.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: kernel-hyper-v trusty
Revision history for this message
Abhishek Gupta (abgupta) wrote :

May I suggest to move priority to high pri as without these patches we cannot core dump on multiple vCPUs. This is a significant customer pain point.
Thanks,
Abhishek

description: updated
Tim Gardner (timg-tpi)
Changed in linux (Ubuntu Trusty):
status: Confirmed → In Progress
Revision history for this message
Tim Gardner (timg-tpi) wrote :

cherry picked from commit e28bab4828354583bb66ac09021ca69b341a7db4 (Drivers: hv: vmbus: Specify the target CPU that should receive notification)

269f979467cf49f2ea8132316c1f00f8c9678f7c (Drivers: hv: vmbus: Don't timeout during the initial connection with host) came in with stable update v3.13.5

Changed in linux (Ubuntu Trusty):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 3.13.0-19.40

---------------
linux (3.13.0-19.40) trusty; urgency=low

  [ Tim Gardner ]

  * [Config] Add new mlx modules to d-i
  * [Config] Fix d-i spelling error: ahxi_xgene --> ahci_xgene
  * [Config] Added Muti-Arch support for linux-headers-PKGVER-ABINUM,
    linux-tools-common, and linux-cloud-tools-common
    - LP: #1295112
  * Release Tracking Bug
    - LP: #1296484

  [ Upstream Kernel Changes ]

  * Drivers: hv: vmbus: Specify the target CPU that should receive
    notification
    - LP: #1295813
 -- Tim Gardner <email address hidden> Sun, 23 Mar 2014 19:54:50 -0600

Changed in linux (Ubuntu Trusty):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.