From: Wolfram Quester <wolfi@mittelerde.physik.uni-konstanz.de>
To: Colin LEROY <colin@colino.net>
Cc: Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>,
benh@kernel.crashing.org
Subject: Re: PREEMPT problems
Date: Fri, 2 Apr 2004 11:57:00 +0200 [thread overview]
Message-ID: <20040402095700.GB1047@halley.zuhause> (raw)
In-Reply-To: <1b6001c417f6$229c2a70$3cc8a8c0@epro.dom>
Hi!
On Thu, Apr 01, 2004 at 04:32:18PM +0200, Colin LEROY wrote:
>
> 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...
Hm, are you sure this is related to PREEMPT? I got this acouple of days
(30 Mar 2004) ago, when I tried to rcompile inkscape, a package I
maintain for debian.
I compiled the package and the recompiled in a chroot, to check
dependencies. sed crashed two times, attaching gdb to told me it was in
glibc-calls. To verify I compiled the same code out of the chroot and
got
if powerpc-linux-g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I.. -I../../src
-DINKSCAPE_ICONS_DIR=\""/usr/share/inkscape"\"
-DINKSCAPE_PIXMAPDIR=\""/usr/share/inkscape"\" -I/usr/include/gtk-2.0
-I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0
-I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/X11R6/include
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
-I/usr/include/libart-2.0 -I/usr/include/libxml2
-I/usr/lib/sigc++-1.2/include -I/usr/include/sigc++-1.2 -Wall -W
-Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual
-Wswitch -Wstrict-prototypes -Wno-unused-parameter -g -O2 -MT
dialog-events.o -Molekular-Dynamik -MP -MF ".deps/dialog-events.Tpo" \
-c -o dialog-events.o `test -f 'dialog-events.cpp' || echo
'./'`dialog-events.cpp; \
then mv -f ".deps/dialog-events.Tpo" ".deps/dialog-events.Po"; \
else rm -f ".deps/dialog-events.Tpo"; exit 1; \
fi
/tmp/ccmgySoN.s: Assembler messages:
/tmp/ccmgySoN.s:17161: Error: value of 40696f11000a3ab8 too large for
field of 4 bytes at 0000000000007be8
make[4]: *** [dialog-events.o] Error 1
make[4]: Leaving directory
`/usr/local/src/packages/inkscape/temp/inkscape-0.37/src/dialogs'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/usr/local/src/packages/inkscape/temp/inkscape-0.37/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/usr/local/src/packages/inkscape/temp/inkscape-0.37'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/usr/local/src/packages/inkscape/temp/inkscape-0.37'
make: *** [build-stamp] Error 2
I had no explanation for this, except the update I did shortly before.
But IIRC I did not get an update of gcc or glibc. Later I went home and
recompiled there (same machine, PB 12", 1Ghz) and all was well. I didn't
have problems since then. Wierd.
My Kernel is still 2.4.24-ben1.
Best regards,
Wolfi
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-04-02 9:57 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
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 [this message]
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=20040402095700.GB1047@halley.zuhause \
--to=wolfi@mittelerde.physik.uni-konstanz.de \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).