From: Chris Bainbridge <chris.bainbridge@gmail.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Re: bad ip checksums
Date: Thu, 6 Oct 2005 16:54:18 +0100 [thread overview]
Message-ID: <623652d50510060854j64051bc5q@mail.gmail.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D32E1D0@liverpoolst.ad.cl.cam.ac.uk>
On 06/10/05, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:
> > > My old 20050929 snapshot works ok. The .config files are identical.
> > > Kernel config attached. Any ideas on what broke?
> >
> > Last nights binary release doesn't have this problem. Is the
> > config file available?
>
> linux-2.6-sparse/arch/xen/configs
Using that config, with 7234. I built a dom0 kernel and the problem is
still present. Weird. What gcc and binutils are you using? I've got
gcc 3.4.4 and binutils-2.15.92.0.2.
next prev parent reply other threads:[~2005-10-06 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 14:59 Re: bad ip checksums Ian Pratt
2005-10-06 15:54 ` Chris Bainbridge [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-06 16:16 Ian Pratt
2005-10-06 18:03 ` Chris Bainbridge
2005-10-06 19:47 ` Ted Kaczmarek
2005-10-06 18:26 Ian Pratt
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=623652d50510060854j64051bc5q@mail.gmail.com \
--to=chris.bainbridge@gmail.com \
--cc=m+Ian.Pratt@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.