From: Bernd Zeimetz <bernd@bzed.de>
To: sparclinux@vger.kernel.org
Subject: Re: Fix for sparc64 cpu hangs.
Date: Thu, 06 Dec 2007 10:43:45 +0000 [thread overview]
Message-ID: <4757D261.4090907@bzed.de> (raw)
In-Reply-To: <20071106.203433.144763156.davem@davemloft.net>
David Miller wrote:
> From: Bernd Zeimetz <bernd@bzed.de>
> Date: Fri, 16 Nov 2007 22:17:07 +0100
>
>> The sysrq-g output is attached, I hope you can make sense out of it.
>> We'll also add some extra workload to the other machines here to try to
>> trigger the bug on other CPUs, too.
>
> I just got back from my vacation and started looking at these
> dumps. I think there might be some bug in cheetah_xcall_deliver(),
> I'll try to diagnose this some more.
I'm not sure if it is related, but non-SMP Kernels don't boot at all on
the machine.
> If you cannot reproduce this bug on non-Ultra-III systems that
> would help confirm or deny my theory. Have you been able to
> trigger this on your Ultra-II machine for example? If so, what
> do the sysrq-g traces look like there?
Since your Futex bugfix the Ultra-II machine runs pretty stable. I did
not manage to trigger the bug there, but it was hard to trigger the bug
the first time there already - even if I run a Kernel without the Futex
bugfix the machine will just hang itself at some random point, I never
managed to reproduce the bug easily on US II.
Best regards,
Bernd
--
Bernd Zeimetz
<bernd@bzed.de> <http://bzed.de/>
next prev parent reply other threads:[~2007-12-06 10:43 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 [this message]
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
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=4757D261.4090907@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.