From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: malc <av1474@comtv.ru>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: Lock-up on PPC64
Date: Wed, 07 Jan 2009 08:17:23 +1100 [thread overview]
Message-ID: <1231276643.14860.30.camel@pasglop> (raw)
In-Reply-To: <Pine.LNX.4.64.0901062032550.2972@linmac.oyster.ru>
> As you wish :) I've written some ad-hoc stuff in the failing path which
> manually triggers sysrq and then sends the klogctl output via network
> and here it is:
Allright, something's unclear to me. What do you mean by the system goes
down then ? The kernel appears to be working at least to a certain
extent if you manage to trigger a sysrq from userspace... And from what
I see, it looks that all processes are somewhere in schedule.
So what is precisely your symptom here ?
Cheers,
Ben.
next prev parent reply other threads:[~2009-01-06 21:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-21 18:18 Lock-up on PPC64 malc
2008-12-22 22:25 ` Marcin Slusarz
2008-12-22 23:32 ` Marcin Slusarz
2008-12-23 3:04 ` malc
2008-12-23 23:45 ` Ken Moffat
2008-12-24 0:08 ` malc
2008-12-25 0:32 ` Benjamin Herrenschmidt
2008-12-28 0:45 ` malc
2008-12-28 0:45 ` malc
2009-01-05 12:28 ` Michael Ellerman
2009-01-05 12:28 ` Michael Ellerman
2009-01-05 16:34 ` malc
2009-01-05 16:34 ` malc
2009-01-06 12:02 ` Benjamin Herrenschmidt
2009-01-06 12:02 ` Benjamin Herrenschmidt
2009-01-06 17:35 ` malc
2009-01-06 21:17 ` Benjamin Herrenschmidt [this message]
2009-01-06 22:23 ` malc
2009-02-22 8:35 ` malc
2009-02-22 22:42 ` Benjamin Herrenschmidt
2009-01-06 12:05 ` Benjamin Herrenschmidt
2009-01-06 12:05 ` Benjamin Herrenschmidt
2009-01-05 15:46 ` Arnd Bergmann
2009-01-05 15:46 ` Arnd Bergmann
2009-02-23 16:36 ` Geoff Levand
-- strict thread matches above, loose matches on Subject: below --
2008-12-25 1:01 malc
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=1231276643.14860.30.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=av1474@comtv.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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.