From: palmer@sifive.com (Palmer Dabbelt)
To: linux-riscv@lists.infradead.org
Subject: Kernel panic - not syncing: corrupted stack end detected inside scheduler
Date: Tue, 20 Nov 2018 09:29:48 -0800 (PST) [thread overview]
Message-ID: <mhng-a200fe90-01a6-444d-9f76-0b00c22249e8@palmer-si-x1c4> (raw)
In-Reply-To: <mvmftvw9llx.fsf@suse.de>
On Tue, 20 Nov 2018 00:52:42 PST (-0800), schwab at suse.de wrote:
> 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.
OK, well, we know there are at least some issues when using an SD card via the
SPI interface as a disk, but nobody has had time to track it down yet. Right
now the only reproducer is to just write a lot of data, which is a pain to
debug. The current issue manifests as a hang in some kernel thread that has a
MMC-like name. What you're seeing may be the same or a different issue.
Do you have a better way to reproduce this than to just hammer the filesystem?
WARNING: multiple messages have this Message-ID (diff)
From: Palmer Dabbelt <palmer@sifive.com>
To: schwab@suse.de
Cc: linux-riscv@lists.infradead.org
Subject: Re: Kernel panic - not syncing: corrupted stack end detected inside scheduler
Date: Tue, 20 Nov 2018 09:29:48 -0800 (PST) [thread overview]
Message-ID: <mhng-a200fe90-01a6-444d-9f76-0b00c22249e8@palmer-si-x1c4> (raw)
Message-ID: <20181120172948.FIaOIJxBOkvlq94PeQSjOF2SbclC1xgpdnGHd58qAUc@z> (raw)
In-Reply-To: <mvmftvw9llx.fsf@suse.de>
On Tue, 20 Nov 2018 00:52:42 PST (-0800), schwab@suse.de wrote:
> 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.
OK, well, we know there are at least some issues when using an SD card via the
SPI interface as a disk, but nobody has had time to track it down yet. Right
now the only reproducer is to just write a lot of data, which is a pain to
debug. The current issue manifests as a hang in some kernel thread that has a
MMC-like name. What you're seeing may be the same or a different issue.
Do you have a better way to reproduce this than to just hammer the filesystem?
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2018-11-20 17:29 UTC|newest]
Thread overview: 10+ 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
2018-11-20 8:52 ` Andreas Schwab
2018-11-20 17:29 ` Palmer Dabbelt [this message]
2018-11-20 17:29 ` Palmer Dabbelt
2018-11-21 8:55 ` Andreas Schwab
2018-11-21 8:55 ` Andreas Schwab
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=mhng-a200fe90-01a6-444d-9f76-0b00c22249e8@palmer-si-x1c4 \
--to=palmer@sifive.com \
--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 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).