From: Andreas Florath <xen@flonatel.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
Steven Smith <ssmith@xensource.com>
Subject: Re: Strange error in domU after dom0 update
Date: Fri, 30 Oct 2009 10:24:34 +0100 [thread overview]
Message-ID: <20091030102434.hgb31gr74o00w8ws@webmail.flonatel.org> (raw)
In-Reply-To: <4AEA1319.6010608@goop.org>
Hello!
> That's an error; it definitely shouldn't be on by default. What
> happens if you disable it?
Updated to:
commit 7ffdaf2a53889c55d76fa83b6fdc45daa2552927
Merge: 7b927d6... b9a24b7...
Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Date: Thu Oct 29 15:10:35 2009 -0700
Merge branch 'xen/netchannel2' into xen/master
* xen/netchannel2:
xen/netchannel2: don't enable by default
Checked the kernel config: netchannel2 is now disabled.
>
>> The only remaining issue are now the millions of log messages:
>> netfront: rx->offset: 0, size: 4294967295
>> which occur only on the 2.6.31.4 pv_ops systems - and, what
>> I think at the moment, only for iSCSI traffic.
>
> If this is still present when you disable netchannel2 then I'll revert
> the merge.
It's still there - even with netchannel2 disabled.
Kind regards - Andreas
next prev parent reply other threads:[~2009-10-30 9:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 7:47 Strange error in domU after dom0 update Andreas Florath
2009-10-22 11:01 ` Pasi Kärkkäinen
2009-10-22 11:55 ` Andreas Florath
2009-10-22 21:08 ` Jeremy Fitzhardinge
2009-10-23 11:28 ` Andreas Florath
2009-10-23 16:01 ` Andreas Florath
2009-10-27 14:44 ` Andreas Florath
2009-10-27 18:29 ` Jeremy Fitzhardinge
2009-10-29 11:14 ` Andreas Florath
2009-10-29 22:11 ` Jeremy Fitzhardinge
2009-10-30 9:24 ` Andreas Florath [this message]
2009-10-30 11:11 ` Steven Smith
2009-11-02 8:59 ` xen
2009-11-03 10:29 ` Andreas Florath
2009-11-03 22:52 ` Jeremy Fitzhardinge
2009-11-04 9:04 ` Steven Smith
2009-11-04 21:04 ` Jeremy Fitzhardinge
2009-11-05 12:22 ` Steven Smith
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=20091030102434.hgb31gr74o00w8ws@webmail.flonatel.org \
--to=xen@flonatel.org \
--cc=jeremy@goop.org \
--cc=ssmith@xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.