All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Veillard <veillard@redhat.com>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
	xen-devel@lists.xensource.com,
	Vincent Hanquez <vincent.hanquez@cl.cam.ac.uk>
Subject: Re: DMA trouble with current xen-sparse
Date: Tue, 8 Nov 2005 01:41:26 -0500	[thread overview]
Message-ID: <20051108064126.GY896@redhat.com> (raw)
In-Reply-To: <1131398939.4844.11.camel@orbit.scot.redhat.com>

On Mon, Nov 07, 2005 at 04:28:59PM -0500, Stephen C. Tweedie wrote:
> Hi,
> 
> On Fri, 2005-11-04 at 14:50 +0000, Ian Pratt wrote:
> 
> >  > Sure, took a bit of time to recompile the kernel (I didn't do 
> > > this for years) and it crashed as expected, here are the info:
> > > 
> > >   ptr: f160ed8e 1514
> > > 
> > > the size looks a full ethernet frame, i.e. 1500 of payload, 2 
> > > ethernet addresses and the 2bytes for the ethernet type, that 
> > > looks kosher to me but clearly it is not aligned.
> > 
> > Please can you try using either our -xen or -xen0 kernel config. I
> > strongly suspect there's something in your config that is breaking this
> > for you, just not sure what.
> 
> I just tried to build it; it would not boot.  That was building the
> 2.6.12 xen-sparse w/ gcc4; retrying with gcc32 now.
> 
> But I suspect that the problem is CONFIG_SLAB_DEBUG.  That sets up slab
> redzoning which checks for buffer overruns.  One consequence is that

  Just to confirm that CONFIG_SLAB_DEBUG is the one exposing the issue.
I recompiled the exact same kernel with just that option turned off
and the tg3 driver does not seems to hang anymore.

Daniel

-- 
Daniel Veillard      | Red Hat http://redhat.com/
veillard@redhat.com  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/

  reply	other threads:[~2005-11-08  6:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-04 14:50 DMA trouble with current xen-sparse Ian Pratt
2005-11-07 21:28 ` Stephen C. Tweedie
2005-11-08  6:41   ` Daniel Veillard [this message]
2005-11-08 15:55     ` Keir Fraser
2005-11-08 15:25       ` Stephen C. Tweedie
  -- strict thread matches above, loose matches on Subject: below --
2005-11-07 23:03 Ian Pratt
2005-11-07 13:51 Ian Pratt
2005-11-07 14:15 ` Daniel Veillard
2005-11-02 15:32 Ian Pratt
2005-11-02 15:36 ` Stephen Tweedie
2005-11-02 15:59   ` Daniel Veillard
2005-11-02 17:12     ` Keir Fraser
2005-11-02 23:04       ` Daniel Veillard
2005-11-03  2:45         ` Vincent Hanquez
2005-11-03 14:51           ` Daniel Veillard
2005-10-28 19:21 Stephen C. Tweedie
2005-10-29  8:55 ` Keir Fraser
2005-10-30  9:52 ` Muli Ben-Yehuda

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=20051108064126.GY896@redhat.com \
    --to=veillard@redhat.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=sct@redhat.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.