From: Andi Kleen <ak@muc.de>
To: Bongani Hlope <bonganilinux@mweb.co.za>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: Tracking a bug in x86-64
Date: 13 Jun 2005 23:48:21 +0200
Date: Mon, 13 Jun 2005 23:48:21 +0200 [thread overview]
Message-ID: <20050613214821.GD86745@muc.de> (raw)
In-Reply-To: <200506132339.13614.bonganilinux@mweb.co.za>
On Mon, Jun 13, 2005 at 11:39:13PM +0200, Bongani Hlope wrote:
> On Monday 13 June 2005 10:59 pm, Bongani Hlope wrote:
> > Hi Andrew and Andi
> >
> > I've been trying to track dow an bug that causes my userspace applications to
> > randomly segfault. I've tracked it down to 2.6.11-mm4 (I'm not sure about mm[1-3]).
> > The bug does not exist in the 2.6.11 kernel. The 2.6.12-rc1 kernel has the bug. The bug
> > is easly triggered by compiling KDE or the kernel using make -j4
> >
>
> I've just tested 2.6.11-mm1 it has that bug as well. So the bug was introduced on that kernel.
Can you please get the individual patches from -mm1 and test them?
I would just unapply the various x86-64 patches and do a binary search.
Thanks,
-Andi
next prev parent reply other threads:[~2005-06-13 21:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-13 20:59 Tracking a bug in x86-64 Bongani Hlope
2005-06-13 21:23 ` Andi Kleen
2005-06-13 21:39 ` Bongani Hlope
2005-06-13 21:48 ` Andi Kleen [this message]
2005-06-14 15:36 ` Linus Torvalds
2005-06-14 20:27 ` Andrew Morton
2005-06-14 21:19 ` Bongani Hlope
2005-06-15 22:20 ` Bongani Hlope
2005-06-15 22:39 ` Linus Torvalds
2005-06-15 23:39 ` Bongani Hlope
2005-06-16 0:46 ` Linus Torvalds
2005-06-16 2:02 ` Andi Kleen
2005-06-16 6:49 ` Bongani Hlope
[not found] ` <xfkll4lfy41.fsf@uxkm53.drewag.de>
2005-07-05 19:52 ` Bongani Hlope
2005-07-05 21:12 ` Andrew Morton
2005-07-06 6:34 ` Arjan van de Ven
2005-07-06 18:20 ` Bongani Hlope
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=20050613214821.GD86745@muc.de \
--to=ak@muc.de \
--cc=akpm@osdl.org \
--cc=bonganilinux@mweb.co.za \
--cc=linux-kernel@vger.kernel.org \
/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.