From: David Abdurachmanov <david.abdurachmanov@gmail.com>
To: Andreas Schwab <schwab@suse.de>
Cc: linux-riscv@lists.infradead.org
Subject: Re: Random memory corruption with v5.2
Date: Tue, 30 Jul 2019 01:58:04 +0300 [thread overview]
Message-ID: <CAEn-LTpM-0TMxkNNh6nnLH9Bnr9Zm+VFLf=z1y9sER6RXrQooQ@mail.gmail.com> (raw)
In-Reply-To: <mvm8sshcdwc.fsf@suse.de>
On Mon, Jul 29, 2019 at 1:51 PM Andreas Schwab <schwab@suse.de> wrote:
>
> Since switching to 5.2 kernels I'm seeing random crashes and
> misbehaviors on the HiFive, for example while building gcc or glibc.
> Perhaps missing TLB flushes?
Do you have some examples of crashes?
I am running 5.2-rc7 on a large number QEMU instances for builders,
and I see some strange behavior, but I haven't noticed any issues
on the board using OpenEmbedded build with the final 5.2 yet.
[17983.074847] Unable to handle kernel paging request at virtual
address 0fffffdff5e14700
[17983.085132] Oops [#1]
[133953.710130] kernel BUG at include/linux/mm.h:1023!
[133953.718204] Kernel BUG [#1]
[165770.567652] Unable to handle kernel NULL pointer dereference at
virtual address 0000000000000010
[148578.912479] kernel BUG at lib/list_debug.c:51!
[148578.917701] Kernel BUG [#1]
[163756.869949] EXT4-fs (vda2): pa 00000000e9971722: logic 512, phys.
2558464, len 512
[163756.889549] EXT4-fs error (device vda2):
ext4_mb_release_inode_pa:3837: group 78, free 0, pa_free 149
[163757.757600] EXT4-fs (vda2): pa 0000000066b479c3: logic 32, phys.
2558368, len 96
sbi_trap_error: hart1: misaligned store handler failed (error -10)
sbi_trap_error: hart1: mcause=0x0000000000000006 mtval=0x00000000000002c3
sbi_trap_error: hart1: mepc=0xffffffe0009dc1f4 mstatus=0x0000000000000802
sbi_trap_error: hart1: ra=0xffffffe0009dc1ee sp=0xffffffe1f3c17be0
[178876.406122] Unable to handle kernel paging request at virtual
address 0000000000012a28
[178876.423941] Oops [#1]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-07-29 22:58 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 10:51 Random memory corruption with v5.2 Andreas Schwab
2019-07-29 22:58 ` David Abdurachmanov [this message]
2019-07-30 4:27 ` Atish Patra
2019-07-30 6:56 ` Andreas Schwab
2019-07-31 0:22 ` Paul Walmsley
2019-07-31 7:39 ` Andreas Schwab
2019-07-31 8:14 ` Anup Patel
2019-08-01 19:57 ` Palmer Dabbelt
2019-07-31 10:19 ` Andreas Schwab
2019-07-31 12:57 ` Troy Benjegerdes
2019-07-31 13:10 ` Andreas Schwab
2019-08-01 18:32 ` Andreas Schwab
2019-08-02 2:00 ` Palmer Dabbelt
2019-08-02 2:15 ` Anup Patel
2019-08-05 14:08 ` Andreas Schwab
2019-08-05 14:34 ` Andreas Schwab
2019-08-05 15:36 ` Andreas Schwab
2019-08-05 22:34 ` Atish Patra
2019-08-06 0:25 ` Troy Benjegerdes
2019-08-06 0:30 ` Atish Patra
2019-08-06 6:41 ` Andreas Schwab
2019-08-06 7:43 ` Andreas Schwab
2019-08-02 7:25 ` Paul Walmsley
2019-08-02 12:08 ` Andreas Schwab
2019-08-02 17:32 ` Paul Walmsley
2019-08-05 7:13 ` Andreas Schwab
2019-08-15 20:52 ` Atish Patra
2019-08-16 5:22 ` Atish Patra
2019-08-16 15:38 ` Troy Benjegerdes
2019-08-19 10:53 ` 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='CAEn-LTpM-0TMxkNNh6nnLH9Bnr9Zm+VFLf=z1y9sER6RXrQooQ@mail.gmail.com' \
--to=david.abdurachmanov@gmail.com \
--cc=linux-riscv@lists.infradead.org \
--cc=schwab@suse.de \
/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).