All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Rolf Eike Beer <eike-kernel@sf-tec.de>, linux-parisc@vger.kernel.org
Subject: Re: pagefaults and hang with 5.15.11
Date: Wed, 5 Jan 2022 13:08:00 +0100	[thread overview]
Message-ID: <4f725f27-744c-c34d-5eec-fbc04eb7f623@gmx.de> (raw)
In-Reply-To: <2089338.irdbgypaU6@daneel.sf-tec.de>

On 1/5/22 08:42, Rolf Eike Beer wrote:
> Am Samstag, 1. Januar 2022, 23:12:16 CET schrieb Sven Schnelle:
>
>> Looks like you have a serial console connected? If yes, could you trigger a
>> 'TOC s' from the BMC, and post the output from 'ser x 0 toc', where x is
>> the processer number? This could help debugging this.
>
> It locked up again, but the important part is not in the mail or the wiki:
> clear the error log before :/ And even worse, the C8000 does not seem to
> support "ser clearpim". You can see the firmware commands of a C8000 here:
> https://parisc.wiki.kernel.org/index.php/BMC.

I think you mix up the BMC console (for remote management, always available) and
the BCH (boot console handler, only available on machine reboot before starting
the OS).
I'm sure the C8000 has a "ser clearpim" in the BCH.

> Fun fact: when doing a command in firmware that prints a lot of stuff, like
> "se", and then switching back to the normal system console via ESC-) seems not
> to stop the firmware from printing more of it's stuff, so you get junk on the
> serial line until the firmware is eventually finished.

Yes, I saw this once too.

> Is there a way to
> switch the C8000 firmware to more than 9600 baud?

In the BCH I assume.

> Sorry for the bad mood, but if that is what you first find after wakeup…

:-)

Helge

  reply	other threads:[~2022-01-05 12:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-26 16:21 pagefaults and hang with 5.15.11 Rolf Eike Beer
2021-12-26 17:22 ` John David Anglin
2021-12-27 14:30   ` Rolf Eike Beer
2021-12-28 21:55     ` Rolf Eike Beer
2022-01-01 22:12       ` Sven Schnelle
2022-01-01 22:28         ` Rolf Eike Beer
2022-01-02 10:24           ` Sven Schnelle
2022-01-02 22:42             ` John David Anglin
2022-01-02 22:53               ` Helge Deller
2022-01-02 23:14                 ` John David Anglin
2022-01-05  7:42         ` Rolf Eike Beer
2022-01-05 12:08           ` Helge Deller [this message]
2022-01-06  0:40         ` Rolf Eike Beer
2022-01-23 11:53   ` Rolf Eike Beer
2022-01-23 13:51     ` John David Anglin
2022-01-23 14:36       ` Helge Deller
2022-01-24  6:41     ` Rolf Eike Beer
2022-01-24 17:24       ` John David Anglin
2022-01-24 17:41         ` John David Anglin
2022-01-25 16:54           ` Rolf Eike Beer
2022-01-25 17:26             ` John David Anglin

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=4f725f27-744c-c34d-5eec-fbc04eb7f623@gmx.de \
    --to=deller@gmx.de \
    --cc=eike-kernel@sf-tec.de \
    --cc=linux-parisc@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.