From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: michael@ellerman.id.au
Cc: linuxppc-dev@ozlabs.org, malc <av1474@comtv.ru>,
linux-kernel@vger.kernel.org
Subject: Re: Lock-up on PPC64
Date: Tue, 06 Jan 2009 23:05:25 +1100 [thread overview]
Message-ID: <1231243525.14860.26.camel@pasglop> (raw)
In-Reply-To: <1231158516.8367.3.camel@localhost>
On Mon, 2009-01-05 at 23:28 +1100, Michael Ellerman wrote:
> I'm confused. Which code never exercises which path, and so what
> deserves a better look?
Well, the thing is with the fix that went into 2.6.30, some error path
will never bit hit, or pretty much.
Without the fix, what can happen is that a syscall incorrectly is
interpreted as returning an error, thus triggering rarely used error
path in Mono. However, that shouldn't lockup the whole machine :-)
So It's still worth investigating what's happening when taking the fix
out, as we may have another bug somewhere lurking.
Cheers,
Ben.
next prev parent reply other threads:[~2009-01-06 12:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0812212058550.2164@linmac.oyster.ru>
[not found] ` <20081222233223.GA6688@joi>
[not found] ` <877i5rh9rm.fsf@linmac.oyster.ru>
[not found] ` <20081223234513.GA8730@deepthought>
[not found] ` <871vvy77v4.fsf@linmac.oyster.ru>
[not found] ` <1230165163.7292.32.camel@pasglop>
2008-12-28 0:45 ` Lock-up on PPC64 malc
2009-01-05 12:28 ` Michael Ellerman
2009-01-05 16:34 ` malc
2009-01-06 12:02 ` Benjamin Herrenschmidt
2009-01-06 17:35 ` malc
2009-01-06 21:17 ` Benjamin Herrenschmidt
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 [this message]
2009-01-05 15:46 ` Arnd Bergmann
2009-02-23 16:36 ` Geoff Levand
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=1231243525.14860.26.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=av1474@comtv.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
/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).