WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Trying to track down odd behavior, errors in xen dmesg

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Trying to track down odd behavior, errors in xen dmesg
From: Keith Swett <swettk@xxxxxxxxx>
Date: Tue, 12 Apr 2011 11:20:07 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 12 Apr 2011 09:20:53 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=IJ6D7pFDRtmXh4sqAhLscadeHBLlyPZIw5rUnRvW2uI=; b=g5Sq1HNQl7GIfB3OrwmtXaKAtnhxepR5tjo8j+71Px4RMfPn3mleZmuYATK1xLm/EH D72J0C5iepFRMAyy2Z0Nysn2dyRzxgzzTzv6fxHCyv49edv5Y37zmd3a8PskAkic02Qj 2/05HLWxgxC2vIXhuCwvQFqWr8+Tl5KIZQ0gg=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=TPJw3muyHLAgAoqS8/bYD6dHvMCwCups6pE28K0719E4wyM82ZwMoqz/JNcTnN87YU Y2ZWbjJABAuNeBdQvsXONoOi2lQJslbbqymrE0s3rVnlrdIFrXkUHh+mz6j9prctk9vr dWuXv7U2CVe7Ve/sRfXHxVvqYeB/Qo4NZ6uSA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110412102002.GA30108@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <BANLkTinhWt9ka2_eUrkTHRyhsNJbQm58=w@xxxxxxxxxxxxxx> <20110407135459.GB7258@xxxxxxxxxxxx> <BANLkTimAO=X_-o2haJmsgaA-DdBgijQ8tQ@xxxxxxxxxxxxxx> <20110407160139.GA9826@xxxxxxxxxxxx> <BANLkTi=kaTPqPjw_QkaLoLd_-Rx7Y4t7bw@xxxxxxxxxxxxxx> <20110407162307.GA30422@xxxxxxxxxxxx> <BANLkTim_Khsw=KCvHFqg1mzwQGtayQLRpQ@xxxxxxxxxxxxxx> <BANLkTi==g14Na0XCBAC0zqOZ_xFU16YSCQ@xxxxxxxxxxxxxx> <20110408135337.GG6189@xxxxxxxxxxxx> <BANLkTinJ4eu6TFhTujbdW_JUJ_4ZVQ3hQQ@xxxxxxxxxxxxxx> <20110412102002.GA30108@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Konrad,

That seems to have fixed it, i'm not seeing the error messages anymore
and performance seems correct thus far.  I'll continue to test a
couple more scenarios today and let you know if I see anything odd.
How should we go about getting this over to the debian maintainers?

--Keith

On Tue, Apr 12, 2011 at 5:20 AM, Konrad Rzeszutek Wilk
<konrad.wilk@xxxxxxxxxx> wrote:
> On Fri, Apr 08, 2011 at 08:59:58AM -0500, Keith Swett wrote:
>> Not a problem, would be happy to beta test.  Send the patches my way
>> whenever they're available.
>
> Did a backport, but I don't have yet the software iSCSI target
> available so couldn't do proper tests. Please test and email kernel log
> messages.
>
>> Would you like me to be building against the debian-src of the
>> packages or would another tree be more beneficial?
>
> That tree should be OK.
>
> See attached patch.
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>