From: Nivedita Singhvi <niv@us.ibm.com>
To: Vincent Hanquez <vincent.hanquez@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Gerd Knorr <kraxel@suse.de>,
Nate Carlson <natecars@natecarlson.com>
Subject: Re: veth0 stuff in -unstable?
Date: Thu, 14 Jul 2005 08:44:21 -0700 [thread overview]
Message-ID: <42D68855.6030406@us.ibm.com> (raw)
In-Reply-To: <20050714152929.GA17218@snarc.org>
Vincent Hanquez wrote:
> On Thu, Jul 14, 2005 at 04:12:51PM +0100, Keir Fraser wrote:
>
>>I think most likely there's random memory corruption going on, and this
>>must be how it is currently manifesting itself on your system. :-(
>
>
> I don't really think that so much random though,
> Kurt Garloff and IBM daily build reports the same problems.
> I'm still without clues on how to reproduce it, I even installed
> a SLES9 rescue image in case that was related.
>
> However I can have this one on dom0 quite easily as soon as I started a domU:
>
> recvmsg bug: copied C1811631 seq C1811661
> KERNEL: assertion (flags & MSG_PEEK) failed at net/ipv4/tcp.c (1295)
>
The above used to be caused by a problem that was fixed (e100 NAPI
driver issue) in mainline, but 2.6.12 should have that fix. Anything
else corrupting the tcp socket data will provoke the same message,
though, still looking...
thanks,
Nivedita
next prev parent reply other threads:[~2005-07-14 15:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 16:29 veth0 stuff in -unstable? Nate Carlson
2005-07-08 16:39 ` Keir Fraser
2005-07-08 16:49 ` Nate Carlson
2005-07-08 17:02 ` Nate Carlson
2005-07-08 17:22 ` Keir Fraser
2005-07-08 18:16 ` Nate Carlson
2005-07-08 18:29 ` Nate Carlson
2005-07-08 18:27 ` Nivedita Singhvi
2005-07-13 16:37 ` Nate Carlson
2005-07-14 14:22 ` Gerd Knorr
2005-07-14 14:58 ` Gerd Knorr
2005-07-14 15:12 ` Keir Fraser
2005-07-14 15:29 ` Vincent Hanquez
2005-07-14 15:44 ` Nivedita Singhvi [this message]
2005-07-14 16:14 ` Vincent Hanquez
2005-07-08 17:20 ` Keir Fraser
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=42D68855.6030406@us.ibm.com \
--to=niv@us.ibm.com \
--cc=kraxel@suse.de \
--cc=natecars@natecarlson.com \
--cc=vincent.hanquez@cl.cam.ac.uk \
--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.