From: Andreas Schwab <schwab@linux-m68k.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: "Albert Ou" <aou@eecs.berkeley.edu>,
"Björn Töpel" <bjorn.topel@gmail.com>,
"Palmer Dabbelt" <palmerdabbelt@google.com>,
LKML <linux-kernel@vger.kernel.org>,
nylon7@andestech.com, syzkaller <syzkaller@googlegroups.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
linux-riscv <linux-riscv@lists.infradead.org>,
"Tobias Klauser" <tklauser@distanz.ch>
Subject: Re: riscv+KASAN does not boot
Date: Fri, 25 Dec 2020 17:58:27 +0100 [thread overview]
Message-ID: <878s9lbz64.fsf@igel.home> (raw)
In-Reply-To: <CACT4Y+bpkSYTL_UwNoKVd0PDFF_xrNN6=y_S_v8W3YRaAcMm2g@mail.gmail.com> (Dmitry Vyukov's message of "Fri, 25 Dec 2020 15:55:48 +0100")
On Dez 25 2020, Dmitry Vyukov wrote:
> qemu-system-riscv64 \
> -machine virt -bios default -smp 1 -m 2G \
> -device virtio-blk-device,drive=hd0 \
> -drive file=buildroot-riscv64.ext4,if=none,format=raw,id=hd0 \
> -kernel arch/riscv/boot/Image \
> -nographic \
> -device virtio-rng-device,rng=rng0 -object
> rng-random,filename=/dev/urandom,id=rng0 \
> -netdev user,id=net0,host=10.0.2.10,hostfwd=tcp::10022-:22 -device
> virtio-net-device,netdev=net0 \
> -append "root=/dev/vda earlyprintk=serial console=ttyS0 oops=panic
> panic_on_warn=1 panic=86400"
Do you get more output with earlycon=sbi?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@linux-m68k.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: "Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
linux-riscv <linux-riscv@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
nylon7@andestech.com, "Palmer Dabbelt" <palmerdabbelt@google.com>,
"Björn Töpel" <bjorn.topel@gmail.com>,
"Tobias Klauser" <tklauser@distanz.ch>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: riscv+KASAN does not boot
Date: Fri, 25 Dec 2020 17:58:27 +0100 [thread overview]
Message-ID: <878s9lbz64.fsf@igel.home> (raw)
In-Reply-To: <CACT4Y+bpkSYTL_UwNoKVd0PDFF_xrNN6=y_S_v8W3YRaAcMm2g@mail.gmail.com> (Dmitry Vyukov's message of "Fri, 25 Dec 2020 15:55:48 +0100")
On Dez 25 2020, Dmitry Vyukov wrote:
> qemu-system-riscv64 \
> -machine virt -bios default -smp 1 -m 2G \
> -device virtio-blk-device,drive=hd0 \
> -drive file=buildroot-riscv64.ext4,if=none,format=raw,id=hd0 \
> -kernel arch/riscv/boot/Image \
> -nographic \
> -device virtio-rng-device,rng=rng0 -object
> rng-random,filename=/dev/urandom,id=rng0 \
> -netdev user,id=net0,host=10.0.2.10,hostfwd=tcp::10022-:22 -device
> virtio-net-device,netdev=net0 \
> -append "root=/dev/vda earlyprintk=serial console=ttyS0 oops=panic
> panic_on_warn=1 panic=86400"
Do you get more output with earlycon=sbi?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2020-12-25 16:59 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-25 14:55 riscv+KASAN does not boot Dmitry Vyukov
2020-12-25 14:55 ` Dmitry Vyukov
2020-12-25 16:58 ` Andreas Schwab [this message]
2020-12-25 16:58 ` Andreas Schwab
2020-12-25 17:13 ` Dmitry Vyukov
2020-12-25 17:13 ` Dmitry Vyukov
2021-01-14 4:57 ` Palmer Dabbelt
2021-01-14 4:57 ` Palmer Dabbelt
2021-01-14 9:23 ` Dmitry Vyukov
2021-01-14 9:23 ` Dmitry Vyukov
2021-01-14 10:24 ` Dmitry Vyukov
2021-01-14 10:24 ` Dmitry Vyukov
2021-01-14 11:24 ` Dmitry Vyukov
2021-01-14 11:24 ` Dmitry Vyukov
2021-01-18 14:53 ` Tobias Klauser
2021-01-18 14:53 ` Tobias Klauser
2021-01-18 15:05 ` Dmitry Vyukov
2021-01-18 15:05 ` Dmitry Vyukov
2021-01-18 15:43 ` Dmitry Vyukov
2021-01-18 15:43 ` Dmitry Vyukov
2021-01-29 7:45 ` Alex Ghiti
2021-01-29 7:45 ` Alex Ghiti
2021-01-29 8:11 ` Dmitry Vyukov
2021-02-16 11:17 ` Dmitry Vyukov
2021-02-16 11:17 ` Dmitry Vyukov
2021-02-16 11:25 ` Dmitry Vyukov
2021-02-16 11:25 ` Dmitry Vyukov
2021-02-16 13:45 ` Dmitry Vyukov
2021-02-16 13:45 ` Dmitry Vyukov
2021-02-16 20:42 ` Alex Ghiti
2021-02-16 20:42 ` Alex Ghiti
2021-02-17 4:42 ` Dmitry Vyukov
2021-02-17 4:42 ` Dmitry Vyukov
2021-02-17 16:36 ` Alex Ghiti
2021-02-17 16:36 ` Alex Ghiti
2021-02-17 17:34 ` Dmitry Vyukov
2021-02-17 17:34 ` Dmitry Vyukov
2021-02-18 7:54 ` Alex Ghiti
2021-02-18 7:54 ` Alex Ghiti
2021-02-18 11:36 ` Dmitry Vyukov
2021-02-18 11:36 ` Dmitry Vyukov
2021-02-19 17:01 ` Alex Ghiti
2021-02-19 17:01 ` Alex Ghiti
2021-02-19 18:53 ` Dmitry Vyukov
2021-02-19 18:53 ` Dmitry Vyukov
2021-02-19 22:26 ` Palmer Dabbelt
2021-02-19 22:26 ` Palmer Dabbelt
2021-03-09 17:11 ` Dmitry Vyukov
2021-03-09 17:11 ` Dmitry Vyukov
2021-03-09 19:49 ` Alex Ghiti
2021-03-09 19:49 ` Alex Ghiti
2021-03-10 17:25 ` Dmitry Vyukov
2021-03-10 17:25 ` Dmitry Vyukov
2021-02-16 17:35 ` Tobias Klauser
2021-02-16 17:35 ` Tobias Klauser
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=878s9lbz64.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn.topel@gmail.com \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=nylon7@andestech.com \
--cc=palmer@dabbelt.com \
--cc=palmerdabbelt@google.com \
--cc=paul.walmsley@sifive.com \
--cc=syzkaller@googlegroups.com \
--cc=tklauser@distanz.ch \
/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.