linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <dwg@au1.ibm.com>
To: Sachin Sant <sachinp@in.ibm.com>
Cc: Linux/PPC Development <linuxppc-dev@ozlabs.org>,
	linux-next@vger.kernel.org
Subject: Re: [powerpc] Next tree Nov 2 : kernel BUG at mm/mmap.c:2135!
Date: Wed, 18 Nov 2009 13:36:27 +1100	[thread overview]
Message-ID: <20091118023627.GC11991@yookeroo> (raw)
In-Reply-To: <4B02529F.1060801@in.ibm.com>

On Tue, Nov 17, 2009 at 01:07:03PM +0530, Sachin Sant wrote:
> David Gibson wrote:
> >Hrm.  Ok.  I am truly baffled.  Well, below is a revised debug patch
> >which I hope will shed some sort of light on things.  I do also notice
> Thanks for the debug patch. I have attached the collected information.
> 
> >from your full log that it looks like the bug is happening shortly
> >after we start userspace.  So it may be differences in my userspace
> >set up that meant I haven't been able to reproduce it.  I'll have
> >another look at that when I get a chance.
> Let me know if you need access to the system on which i can recreate the
> bug. I can make that system available for you to debug this issue.

That's probably a good idea.  I'm still pretty baffled by this, so it
will probably take several more rounds of debug patches to start
getting a handle on it.


-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

  reply	other threads:[~2009-11-18  3:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02  6:38 linux-next: Tree for November 2 Stephen Rothwell
2009-11-02  9:12 ` [powerpc] Next tree Nov 2 : kernel BUG at mm/mmap.c:2135! Sachin Sant
2009-11-04 12:38   ` Sachin Sant
2009-11-05  0:16     ` David Gibson
2009-11-05  4:42       ` Sachin Sant
2009-11-12 11:16       ` Sachin Sant
2009-11-13  1:37         ` David Gibson
2009-11-13  2:10           ` David Gibson
2009-11-13  9:35             ` Sachin Sant
2009-11-17  5:25               ` David Gibson
2009-11-17  7:37                 ` Sachin Sant
2009-11-18  2:36                   ` David Gibson [this message]
     [not found] ` <20091102173845.210d1c57.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2009-11-02 17:13   ` linux-next: Tree for November 2 (usb/whci) Randy Dunlap
2009-11-11 17:04     ` Randy Dunlap
     [not found]       ` <20091111090403.5fb0229e.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2009-11-11 17:30         ` Greg KH
2009-11-17 11:40           ` David Vrabel
2009-11-17 15:51             ` Randy Dunlap
     [not found]               ` <20091117075101.0bf72415.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2009-11-17 18:49                 ` David Vrabel
2009-11-02 18:01 ` linux-next: Tree for November 2 (wireless/wl1271) Randy Dunlap
2009-11-02 18:44   ` John W. Linville
2009-11-02 18:48     ` John W. Linville
2009-11-02 21:10       ` Luciano Coelho
2009-11-03  6:03         ` Luciano Coelho
2009-11-07 10:37           ` Kalle Valo
2009-11-09 11:20             ` Luciano Coelho
2009-11-04 21:56 ` [PATCH] staging: RTL8192SU depends on USB Randy Dunlap

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=20091118023627.GC11991@yookeroo \
    --to=dwg@au1.ibm.com \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sachinp@in.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).