From: Ernst Persson <ernstp@mac.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Random segfaults with 2.6
Date: Sat, 6 Sep 2003 16:11:03 +0200 [thread overview]
Message-ID: <200309061611.03915.ernstp@mac.com> (raw)
I'm running the latest linuxppc-2.5-benh and I'm getting a lot of random
segfaults, specially in development tools.
Emergeing in gentoo works half the time. Gcc and configure crashes, and this
never happens with 2.4.*.
Linux zapp.no-ip.com 2.6.0-test4 #5 lör sep 6 12:40:19 CEST 2003 ppc 740/750
GNU/Linux
Module Size Used by
dmasound_pmac 85464 2 [unsafe]
dmasound_core 20460 3 dmasound_pmac
soundcore 9344 3 dmasound_core
i2c_core 25060 1 dmasound_pmac
Ext3 filesystem, atyfb.
I can't reproduce the crashes, they are really random.
//ernie
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-09-06 14:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-06 14:11 Ernst Persson [this message]
2003-09-06 15:07 ` Random segfaults with 2.6 Michel Dänzer
2003-09-06 15:16 ` Ernst Persson
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=200309061611.03915.ernstp@mac.com \
--to=ernstp@mac.com \
--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).