From: Bernd Zeimetz <bernd@bzed.de>
To: sparclinux@vger.kernel.org
Subject: Re: Fix for sparc64 cpu hangs.
Date: Sun, 16 Dec 2007 22:41:19 +0000 [thread overview]
Message-ID: <4765A98F.2060806@bzed.de> (raw)
In-Reply-To: <20071106.203433.144763156.davem@davemloft.net>
>> I'll leave the kernel running and make sure the machine gets some more
>> users and load during the next days.
>
> Thanks for testing, let me know if any more issues trigger.
One problem I was pointed to was the build failure of erlang. Here the
created erlc binary segfaults with a bus error.
- this only happens on US III machines, works fine on US II.
- on lebrun it doesn't happen on the first call of erlc, but after
several successful runs of it - see
http://buildd.debian.org/fetch.cgi?&pkg=erlang&ver=1%3A11.b.5dfsg-11&arch=sparc&stamp\x1197012623&file=log
- on our v880 here (which is still running the kernel with your test
patch) erlc segfaults instantly. A strace shows that it is stuck at a
well known place - pretty similar to the segfault in aptitude which
successfully shot the machine to death before your patch(es) was(were)
applied:
[pid 1224] clone(Process 1228 attached
child_stack=0xf7951480,
flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID,
parent_tidptr=0xf7951bd8, tls=0xf7951b90, child_tidptr=0xf7951bd8) = 1228
[pid 1224] SYS_300(0xf7951be0, 0xc, 0, 0, 0xf7951df4) = 0
[pid 1224] futex(0xff993338, 0x80 /* FUTEX_??? */, 2
... there it hangs.
I guess you should be able to reproduce this on your US III machine.
dget -x \
ftp://debian.netcologne.de/debian/pool/main/e/erlang/erlang_11.b.5dfsg-11.dsc
cd erlang-11.b.5dfsg
dpkg-buildpackage -rfakeroot
(you'll probably have to install some build-deps...)
when erlc segfaults, change into the directory and set
ERL_TOP=/home/bzed/erlang-11.b.5dfsg
PATH=/home/bzed/erlang-11.b.5dfsg/bootstrap/bin:${PATH}
before retrying to run erlc.
Let me know if you need more informations or want me to test something.
--
Bernd Zeimetz
<bernd@bzed.de> <http://bzed.de/>
next prev parent reply other threads:[~2007-12-16 22:41 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 4:34 Fix for sparc64 cpu hangs David Miller
2007-11-07 4:34 ` David Miller
2007-11-07 5:13 ` David Miller
2007-11-07 5:13 ` David Miller
2007-11-09 20:22 ` Andrew Morton
2007-11-09 20:22 ` Andrew Morton
2007-11-09 22:14 ` David Miller
2007-11-09 22:14 ` David Miller
2007-11-07 14:25 ` Josip Rodin
2007-11-07 14:35 ` Bernd Zeimetz
2007-11-08 0:01 ` David Miller
2007-11-11 6:04 ` David Miller
2007-11-11 6:13 ` David Miller
2007-11-11 6:27 ` Bernd Zeimetz
2007-11-12 13:16 ` Josip Rodin
2007-11-16 21:17 ` Bernd Zeimetz
2007-11-20 6:09 ` David Miller
2007-12-06 8:49 ` David Miller
2007-12-06 10:43 ` Bernd Zeimetz
2007-12-06 11:08 ` David Miller
2007-12-06 12:09 ` Bernd Zeimetz
2007-12-06 13:52 ` David Miller
2007-12-07 8:59 ` David Miller
2007-12-08 0:14 ` Bernd Zeimetz
2007-12-09 8:38 ` David Miller
2007-12-10 9:16 ` Bernd Zeimetz
2007-12-10 9:18 ` David Miller
2007-12-11 14:19 ` David Miller
2007-12-12 16:05 ` Bernd Zeimetz
2007-12-12 16:23 ` David Miller
2007-12-13 20:54 ` Bernd Zeimetz
2007-12-16 22:41 ` Bernd Zeimetz [this message]
2007-12-16 22:48 ` Josip Rodin
2007-12-16 23:30 ` David Miller
2007-12-17 9:40 ` Josip Rodin
2007-12-17 9:57 ` David Miller
2007-12-17 10:10 ` Josip Rodin
2007-12-17 10:21 ` David Miller
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=4765A98F.2060806@bzed.de \
--to=bernd@bzed.de \
--cc=sparclinux@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.