From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Colin LEROY <colin@colino.net>
Cc: Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: PREEMPT problems
Date: Fri, 02 Apr 2004 10:29:37 +1000 [thread overview]
Message-ID: <1080865776.1286.8.camel@gaston> (raw)
In-Reply-To: <1b6001c417f6$229c2a70$3cc8a8c0@epro.dom>
On Fri, 2004-04-02 at 00:32, Colin LEROY wrote:
> Hi,
>
> This won't be really helpful, as I have no time to investigate, but I seem
> to have problems with preempt (and latest main-tree BK). After a few hours
> of uptime, I get hanging processes (sed, cvs (can't be network related as
> the CVSROOT is local)) and gcc segfaults while compiling kernel.
>
> Maybe it's not completely fixed yet...
Ah. Well, no problem here nor for other testers so far, weird...
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-04-02 0:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 14:32 PREEMPT problems Colin LEROY
2004-04-02 0:29 ` Benjamin Herrenschmidt [this message]
2004-04-02 0:56 ` Benjamin Herrenschmidt
2004-04-02 16:00 ` Michel Dänzer
2004-04-02 16:43 ` Michel Dänzer
2004-04-03 3:06 ` Benjamin Herrenschmidt
2004-04-03 12:56 ` Michel Dänzer
2004-04-04 2:20 ` Benjamin Herrenschmidt
2004-04-06 0:51 ` Benjamin Herrenschmidt
2004-04-06 23:28 ` Michel Dänzer
2004-04-06 23:33 ` Benjamin Herrenschmidt
2004-04-02 9:57 ` Wolfram Quester
2004-04-19 14:26 ` ppc4xx_find_bridges( ) hangs kernel on Xilinx ML300 (PCI) Mike Wellington
2004-04-19 19:48 ` Mike Wellington
2004-04-19 20:48 ` Peter Ryser
2004-04-19 20:54 ` Mike Wellington
2004-04-19 20:58 ` PCI - i *thought* the edk2 was what I was using! Mike Wellington
2004-04-19 22:05 ` Peter Ryser
2004-04-19 22:13 ` did you give me the right ml300_edk*.zip link? Mike Wellington
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=1080865776.1286.8.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=colin@colino.net \
--cc=linuxppc-dev@lists.linuxppc.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.