xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keith Swett <swettk@gmail.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Trying to track down odd behavior, errors in xen dmesg
Date: Tue, 12 Apr 2011 15:59:48 -0500	[thread overview]
Message-ID: <BANLkTikiWVXgvANu2RAph6m5T5i4_aE7Hw@mail.gmail.com> (raw)
In-Reply-To: <20110412204123.GA7308@dumpdata.com>

Konrad,

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.


--Keith


On Tue, Apr 12, 2011 at 3:41 PM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> 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@oracle.com> 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.
>> >
>

  reply	other threads:[~2011-04-12 20:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-06 16:30 Trying to track down odd behavior, errors in xen dmesg Keith Swett
2011-04-07 13:54 ` Konrad Rzeszutek Wilk
2011-04-07 14:45   ` Keith Swett
2011-04-07 15:52   ` Keith Swett
2011-04-07 16:01     ` Konrad Rzeszutek Wilk
2011-04-07 16:02       ` Keith Swett
2011-04-07 16:23         ` Konrad Rzeszutek Wilk
2011-04-07 16:39           ` Keith Swett
2011-04-08 13:40             ` Keith Swett
2011-04-08 13:53               ` Konrad Rzeszutek Wilk
2011-04-08 13:59                 ` Keith Swett
2011-04-12 10:20                   ` Konrad Rzeszutek Wilk
2011-04-12 16:20                     ` Keith Swett
2011-04-12 20:41                       ` Konrad Rzeszutek Wilk
2011-04-12 20:59                         ` Keith Swett [this message]
2011-04-12 21:08                           ` Konrad Rzeszutek Wilk
2011-04-12 21:23                             ` Keith Swett
2011-04-12 22:48                               ` Konrad Rzeszutek Wilk
2011-04-12 23:02                                 ` Keith Swett
2011-04-13 13:05                                   ` Konrad Rzeszutek Wilk
2011-04-14 13:24                               ` Konrad Rzeszutek Wilk

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=BANLkTikiWVXgvANu2RAph6m5T5i4_aE7Hw@mail.gmail.com \
    --to=swettk@gmail.com \
    --cc=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    /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;
as well as URLs for NNTP newsgroup(s).