From: Jurij Smakov <jurij@wooyd.org>
To: Leif Sawyer <lsawyer@gci.com>
Cc: gentoo-sparc@lists.gentoo.org, sparclinux@vger.kernel.org
Subject: RE: [gentoo-sparc] kernel-2.6.15-r4 (in)stability on U2-SMP, etc.
Date: Fri, 17 Feb 2006 21:48:11 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.63.0602172131420.3243@bobcat> (raw)
In-Reply-To: <38D04BF3A4B7B2499D19EB1DB54285EA01F198ED@FNB1EX01.gci.com>
On Fri, 17 Feb 2006, Leif Sawyer wrote:
> I can also add that my U2 (2x300) is also having the same lockup
> on high disk activity. I've been able to 'nice' my portage related
> activity down and avoid it crashing on the last few package emerges,
> but it's not a cure-all.
If you can easily reproduce this problem, could you try to get some useful
debugging info? If you can drop into prom after machine hangs, what
backtrace does the ctrace command give you? Could you try compiling the
kernel with spinlock debugging ang magic sysrq key support and see if you
can get some information on where it hangs that way?
We are hitting some kind of SMP lockup issues in Debian, however it is
much harder to reproduce. The automatic sparc build machines (running
2.6.8) occasionally hang when trying to build large packages, like
openoffice.org. All attempts to reproduce this failure locally failed so
far. As it might be caused by the same bug you are hitting, we would be
*very* interested in any progress on this, since these hangs currently
are the main obstacle which might prevent the inclusion of sparc port into
the next official Debian release.
Best regards,
Jurij Smakov jurij@wooyd.org
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC
--
gentoo-sparc@gentoo.org mailing list
next prev parent reply other threads:[~2006-02-18 5:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 18:15 [gentoo-sparc] kernel-2.6.15-r4 (in)stability on U2-SMP, etc Leif Sawyer
2006-02-18 5:48 ` Jurij Smakov [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-15 13:09 Ferris McCormick
2006-02-15 13:28 ` Jameel Akari
2006-02-15 14:01 ` Ferris McCormick
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=Pine.LNX.4.63.0602172131420.3243@bobcat \
--to=jurij@wooyd.org \
--cc=gentoo-sparc@lists.gentoo.org \
--cc=lsawyer@gci.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox