From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nivedita Singhvi Subject: Re: veth0 stuff in -unstable? Date: Thu, 14 Jul 2005 08:44:21 -0700 Message-ID: <42D68855.6030406@us.ibm.com> References: <42CEC5A9.1060707@us.ibm.com> <87k6jtlb64.fsf@bytesex.org> <87br55l9id.fsf@bytesex.org> <2926312dbeba41d181f0e0e8aca3a47e@cl.cam.ac.uk> <20050714152929.GA17218@snarc.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20050714152929.GA17218@snarc.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Vincent Hanquez Cc: xen-devel@lists.xensource.com, Gerd Knorr , Nate Carlson List-Id: xen-devel@lists.xenproject.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