public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Juan Dos Santos <jdossantos@docs.homelinux.org>
To: Hank Janssen <hjanssen@microsoft.com>
Cc: KY Srinivasan <kys@microsoft.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Error in Hyper-V modules hv_vmbus
Date: Tue, 03 May 2011 23:27:05 +0200	[thread overview]
Message-ID: <4DC07329.30906@docs.homelinux.org> (raw)
In-Reply-To: <8AFC7968D54FB448A30D8F38F259C562498A27AF@TK5EX14MBXC114.redmond.corp.microsoft.com>


>>>> -----Original Message-----
>>>> From: root@docs.homelinux.org [mailto:root@docs.homelinux.org]
>>>> Sent: Tuesday, May 03, 2011 10:52 AM
>>>> To: KY Srinivasan
>>>> Cc: linux-kernel@vger.kernel.org
>>>> Subject: RE: Error in Hyper-V modules hv_vmbus
>>>>
>>>>   On Tue, 3 May 2011 13:42:43 +0000, KY Srinivasan wrote:
>>>>>> -----Original Message-----
>>>>>> From: root [mailto:root@docs.homelinux.org]
>>>>>> Sent: Sunday, May 01, 2011 8:37 AM
>>>>>> To: KY Srinivasan
>>>>>> Cc: linux-kernel@vger.kernel.org
>>>>>> Subject: Re: Error in Hyper-V modules hv_vmbus
>>>>>>
>>>>>> Windows Server Core 2008 R2 with SP2
>>>>> This is a known problem and a fix has been submitted - the patch
>>>>> is yet to be applied though. Once the hv patches that are in the
>>>>> queue are applied, this problem will be fixed. In the interim, if
>>>>> you want an immediate fix, I could send you the patch that will
>>>>> apply against the tree you have.
>>>>>
>>>>> Regards,
>>>>>
>>>>> K. Y
>>>>>> Regards
>>>>>> Juan Dos Santos
>>>>   Could You send me the patch? So I can test it, I am using the
>>>> kernel source from
>>>> http://www.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.39-rc5
>>>> .t ar.bz2,  is the patch compatible with this kernel source?
>>> This is a very old version of the hyper-V driver code compared to what
>>> is in Greg's tree and looking at the code It does not look like the
>>> problem you are seeing is the problem my patch fixes. We will do some
>>> additional testing and get back to you. It would be very useful if you
>>> can post the dmesg or stack trace that can shed additional light on the
>> problem.
> Juan,
>
> I just fixed a few issues in Ubuntu 10.10 that might be similar.
>
> I will spin up a debian system and see if I can reproduce the problem and
> submit a patch To fix it.
>
> Hank.
Hi Hank

Ok thanks, tomorrow I will post dmesg and more debuging stuff about this 
problem...

Regards
Juan Dos Santos

  reply	other threads:[~2011-05-03 21:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-30 14:39 Error in Hyper-V modules hv_vmbus root
2011-04-30 20:28 ` KY Srinivasan
2011-05-01 12:37   ` root
2011-05-01 15:23     ` KY Srinivasan
2011-05-03 13:42     ` KY Srinivasan
2011-05-03 14:51       ` root
     [not found]         ` <6E21E5352C11B742B20C142EB499E0481DF899@TK5EX14MBXC124.redmond.corp.microsoft.com>
2011-05-03 18:29           ` Hank Janssen
2011-05-03 18:42           ` Hank Janssen
2011-05-03 21:27             ` Juan Dos Santos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-05-04  9:48 jdossantos
2011-05-04 16:00 ` Hank Janssen
2011-05-05 12:05   ` jdossantos
2011-05-05 18:05     ` jdossantos
2011-05-05 18:45       ` Hank Janssen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DC07329.30906@docs.homelinux.org \
    --to=jdossantos@docs.homelinux.org \
    --cc=hjanssen@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox