All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kirill Korotaev <dev@sw.ru>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, devel@openvz.org
Subject: Re: [SPARC64]: resumable error decoding
Date: Wed, 22 Nov 2006 13:19:28 +0300	[thread overview]
Message-ID: <45642430.6030009@sw.ru> (raw)
In-Reply-To: <20061121.161158.63124759.davem@davemloft.net>

>>Running stress tests on OpenVZ 2.6.18 sparc64 kernel we hit the following:
>>------- cut --------
>>[285401.094964] RESUMABLE ERROR: Reporting on cpu 0
>>[285401.626736] RESUMABLE ERROR: err_handle[410000000000c6f] err_stick[103921ee2007c] err_type[00000004:warning resumable]
>>[285402.869015] RESUMABLE ERROR: err_attrs[00000020:       ]
>>[285403.491920] RESUMABLE ERROR: err_raddr[0000000000000000] err_size[0] err_cpu[0]
> 
> 
> This is a power-off request, did someone push the power-off button
> or give the power-off command from the System Controller console?
ahh, looks like this :)
one of our users reproduced an issue which causes both mainstream and
2.6.18 OVZ kerenls to hang on sparc :/ will investigate...
probably he reset the box after the hang :)

> I should add proper support for this, this report is a good reminder
> :-)
would be nice :@)

> All resumable errors of type 0x4 are power-off requests.
> Unfortunately these encodings are not in any of the publicly published
> documents.
thanks a lot for the explanation!

Thanks,
Kirill


  reply	other threads:[~2006-11-22 10:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-21 13:42 [SPARC64]: resumable error decoding Kirill Korotaev
2006-11-22  0:11 ` David Miller
2006-11-22 10:19   ` Kirill Korotaev [this message]
2006-11-30 20:29     ` 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=45642430.6030009@sw.ru \
    --to=dev@sw.ru \
    --cc=davem@davemloft.net \
    --cc=devel@openvz.org \
    --cc=linux-kernel@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.