From: Alexander Nyberg <alexn@telia.com>
To: Andrew Morton <akpm@osdl.org>
Cc: ak@suse.de, linux-kernel@vger.kernel.org
Subject: Re: x86_64 access of some bad address
Date: Thu, 4 Aug 2005 22:20:25 +0200 [thread overview]
Message-ID: <20050804202025.GA4101@localhost.localdomain> (raw)
In-Reply-To: <20050804131512.7d464fad.akpm@osdl.org>
On Thu, Aug 04, 2005 at 01:15:12PM -0700 Andrew Morton wrote:
> Alexander Nyberg <alexn@telia.com> wrote:
> >
> > As I only have one x86_64 which is my main workstation it's far too
> > tedious to do binary searching (this doesn't happen on x86).
> >
> > Happens with both latest -git and 2.6.12-mm1
> > The tools to reproduce this is at: http://serkiaden.mine.nu/kp2.tar
> >
> > Just do:
> > gdb lyze
> > run
> >
> > and it crashes here giving:
> >
> > ----------- [cut here ] --------- [please bite here ] ---------
> > Kernel BUG at "mm/memory.c":911
>
> So I think Hugh's patch this morning should fix this up. Please retest
> -rc6 when it's out?
Maybe I forgot to tell but I've already tested and it works fine.
prev parent reply other threads:[~2005-08-04 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 15:13 x86_64 access of some bad address Alexander Nyberg
2005-06-26 16:19 ` Alexey Dobriyan
2005-08-04 20:15 ` Andrew Morton
2005-08-04 20:20 ` Alexander Nyberg [this message]
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=20050804202025.GA4101@localhost.localdomain \
--to=alexn@telia.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox