All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: linux-ia64@vger.kernel.org
Subject: Re: current bk goes BUG on ia64 when dumping core
Date: Mon, 06 Oct 2003 12:34:56 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106544400328706@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106533868423168@msgid-missing>

Roland McGrath <roland@redhat.com> wrote:
>
> > When running the latest LTP code, it dies in the new coredump code.
> 
> This is what I predicted when I sent the second ia64 version of the patch.
> Please refer to that message for complete testing instructions to verify
> the core format is correct (assuming it doesn't crash any more with the new
> patch).  I've made another cosmetic change to avoid using "vsyscall" in
> variable names, and here is that version of the patch relative to the
> current 2.6 tree.

OK, thanks.

Now, Linus is trying to get a good 2.6.0-test7 out the door early this week
and it's not helpful that ia64 goes BUG every time it wants to dump core!

I am in Tokyo and am not able to test your patch.  Could someone please
apply Roland's patch to current -bk, then run Linux Test Project (it BUGged
in two seconds for me) and then send the patch to Linus fairly promptly?

Thanks.


  parent reply	other threads:[~2003-10-06 12:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-05  7:24 current bk goes BUG on ia64 when dumping core Andrew Morton
2003-10-05  7:38 ` Andrew Morton
2003-10-06  6:41 ` Roland McGrath
2003-10-06 12:34 ` Andrew Morton [this message]
2003-10-07  5:06 ` current bk goes BUG on ia64 when dumping core; FIXED, PATCH Peter Chubb
2003-10-07  5:19 ` Roland McGrath
2003-10-07  8:17 ` Peter Chubb

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=marc-linux-ia64-106544400328706@msgid-missing \
    --to=akpm@osdl.org \
    --cc=linux-ia64@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.