From: Andrew Morton <akpm@digeo.com>
To: Daniel Jacobowitz <dan@debian.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, mingo@elte.hu
Subject: Re: 2.5.59-mm9
Date: Fri, 7 Feb 2003 11:52:37 -0800 [thread overview]
Message-ID: <20030207115237.7f58e69e.akpm@digeo.com> (raw)
In-Reply-To: <20030207141114.GA31151@nevyn.them.org>
Daniel Jacobowitz <dan@debian.org> wrote:
>
> On Fri, Feb 07, 2003 at 03:03:50AM -0800, Andrew Morton wrote:
> > Andrew Morton <akpm@digeo.com> wrote:
> > >
> > > http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.59/2.5.59-mm9/
> >
> > I've taken this down.
> >
> > Ingo, there's something bad in the signal changes in Linus's current tree.
> >
> > mozilla won't display, and is unkillable:
>
> Yeah, I'm seeing hangs in rt_sigsuspend under GDB also. Thanks for
> saying that they show up without ptrace; I hadn't been able to
> reproduce them without it.
>
> Something is causing realtime signals to drop.
OK. Looks like Linus is hot on the trail.
BTW, some nice people have been sending in smalldevfs testing results
(successful). I've put that patch back up at
http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.59/smalldevfs.patch
for other testers. It applies to 2.5.59 base.
And it is not clear why I copied Ingo on the signal thing, when it is not he
who is working that code. Sorry about that.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
prev parent reply other threads:[~2003-02-07 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 9:39 2.5.59-mm9 Andrew Morton
2003-02-07 11:03 ` 2.5.59-mm9 Andrew Morton
2003-02-07 14:11 ` 2.5.59-mm9 Daniel Jacobowitz
2003-02-07 19:52 ` Andrew Morton [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=20030207115237.7f58e69e.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=dan@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
/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