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/
Home Products Support Community News


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 15:59:48 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 12 Apr 2011 14:02:19 -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=rHmNGK3oKSjbeyv7SfsdsAx1+paQhEAffQwjuqUz6L4=; b=hLR2nobI0fkPlEtD9Q6qY/7ALulKs7wGZDdmAHUr1MA6lFadDY6dLC4uUuhh9Esoha oRUZ8YqeB3bWFhysb900f3GQtRKQR9LXwe+zl4MbB0E1dCxbAxbNT09tOV1g/vH2fQAn 5VSIiNxZapWLztTm+lWrCELuh/NezugY7Jwgg=
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=mUJpQTfefUxRTYWWYv0UrjnbGHQV+PYyHSYfDfJsnrN6U8cYOeqMX+OrErMKWIzEN1 22UzBZM3o8sLnrJbU76wmrht0j7ECLoTXx+DY/+ySCdGdhpNiserpaDrXCCqx26MX7Wq uFnU9pcWqPMnY4mxRoeYK9aV4C/t6Re86y1zo=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110412204123.GA7308@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: <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> <BANLkTi=p3h7jyxpZhkbect25tPngFf5Xiw@xxxxxxxxxxxxxx> <20110412204123.GA7308@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

I'm not seeing the kernel messages, so i'm wondering if something else
changed, and if I applied the patch correctly.
Trying to repeat the process from this morning with a clean tree to confirm.


On Tue, Apr 12, 2011 at 3:41 PM, Konrad Rzeszutek Wilk
<konrad.wilk@xxxxxxxxxx> wrote:
> On Tue, Apr 12, 2011 at 11:20:07AM -0500, Keith Swett wrote:
>> 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.
> OK. It might take a bit of time. You should see some kernel logs when
> it detects the iSCSI retransmission errors. Why don't we let this
> run for a week or so to make sure it does not cause regressions.
>> How should we go about getting this over to the debian maintainers?
> Lets make sure it does not break anything.
>> --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

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