All of lore.kernel.org
 help / color / mirror / Atom feed
From: schwab@suse.de (Andreas Schwab)
To: linux-riscv@lists.infradead.org
Subject: Kernel panic - not syncing: corrupted stack end detected inside scheduler
Date: Tue, 20 Nov 2018 09:52:42 +0100	[thread overview]
Message-ID: <mvmftvw9llx.fsf@suse.de> (raw)
In-Reply-To: <mhng-ce3ee330-9ac5-41c3-9890-ee9d6dabe105@palmer-si-x1c4> (Palmer Dabbelt's message of "Mon, 19 Nov 2018 15:46:37 -0800 (PST)")

On Nov 19 2018, Palmer Dabbelt <palmer@sifive.com> wrote:

> Sorry I can't be more specific.  Does this require hardware to manifest?

This was on the hifive.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab at suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@suse.de>
To: Palmer Dabbelt <palmer@sifive.com>
Cc: linux-riscv@lists.infradead.org
Subject: Re: Kernel panic - not syncing: corrupted stack end detected inside scheduler
Date: Tue, 20 Nov 2018 09:52:42 +0100	[thread overview]
Message-ID: <mvmftvw9llx.fsf@suse.de> (raw)
Message-ID: <20181120085242.IE1n8ZdwIkEDlUMrjqVXswKqGX0Fz74eABbvwnfGaTI@z> (raw)
In-Reply-To: <mhng-ce3ee330-9ac5-41c3-9890-ee9d6dabe105@palmer-si-x1c4> (Palmer Dabbelt's message of "Mon, 19 Nov 2018 15:46:37 -0800 (PST)")

On Nov 19 2018, Palmer Dabbelt <palmer@sifive.com> wrote:

> Sorry I can't be more specific.  Does this require hardware to manifest?

This was on the hifive.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2018-11-20  8:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19 11:23 Kernel panic - not syncing: corrupted stack end detected inside scheduler Andreas Schwab
2018-11-19 11:23 ` Andreas Schwab
2018-11-19 23:46 ` Palmer Dabbelt
2018-11-19 23:46   ` Palmer Dabbelt
2018-11-20  8:52   ` Andreas Schwab [this message]
2018-11-20  8:52     ` Andreas Schwab
2018-11-20 17:29     ` Palmer Dabbelt
2018-11-20 17:29       ` Palmer Dabbelt
2018-11-21  8:55       ` Andreas Schwab
2018-11-21  8:55         ` Andreas Schwab
  -- strict thread matches above, loose matches on Subject: below --
2018-11-13 21:28 Qian Cai
2018-11-13  4:45 Qian Cai

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=mvmftvw9llx.fsf@suse.de \
    --to=schwab@suse.de \
    --cc=linux-riscv@lists.infradead.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.