linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: michaeljclark@mac.com (Michael Clark)
To: linux-riscv@lists.infradead.org
Subject: [sw-dev] Re: [isa-dev] riscv-qemu - linux boot is failing for vda device
Date: Wed, 17 Oct 2018 11:30:50 +1300	[thread overview]
Message-ID: <D9003246-0336-4327-97D3-D8F079F640D3@mac.com> (raw)
In-Reply-To: <20181016200245.j2gesmdjgoi7zmqh@excalibur.cnev.de>



> On 17/10/2018, at 9:02 AM, Karsten Merker <merker@debian.org> wrote:
> 
>> On Tue, Oct 16, 2018 at 11:38:53AM -0700, Palmer Dabbelt wrote:
>>> On Tue, 16 Oct 2018 06:12:11 PDT (-0700), pintu.ping at gmail.com wrote:
>>>> On Tue, Oct 16, 2018 at 6:10 AM Palmer Dabbelt <palmer@sifive.com> wrote:
>>>> On Mon, 15 Oct 2018 14:14:51 PDT (-0700), rjones at redhat.com wrote:
> [...]
>>>> Your best bet today is to run 4.19-rc8, which should be pretty stable.
>>> 
>>> Yes, I checked with mainline linux-kernel 4.19.
>>> Now I am able to boot successfully and login into qemu-riscv shell.
>>> Thank you so much :)
>>> 
>>> But I am curious to know what changes resulted into this fix, in 4.19 kernel ?
>>> Which is the exact patch in mainline, that fixes this issue?
>>> Because at times during the development, it will be difficult to
>>> simply upgrade the kernel version.
>> 
>> Yes, that's expected.  RISC-V Linux is still pretty bleeding edge, you just
>> happened to catch it between when master started working and when there was
>> a proper release that contained your patches.  Since master is very calm
>> right now (there was an rc8 before release, but it's very close to a
>> release) it's OK to use, but you best bet going forward is to use the
>> release tarballs just like normal.
> 
> Just as a data point in case you should find it helpful: I'm
> since two weeks running 4.19-rc6/-rc7 on the qemu-riscv "virt"
> board under permanent heavy load (the system is running a Debian
> package builder) without a single hiccup.

Hi Karsten,

Have you tried riscv-qemu? I know qemu-riscv gets quite a lot of testing but I?d like to gain some more confidence in riscv-qemu.

We might have a PLIC bug in QEMU. If anyone has a reproducer they can file an issue on the riscv-qemu issue tracker and I?ll take a look...

Michael

WARNING: multiple messages have this Message-ID (diff)
From: Michael Clark <michaeljclark@mac.com>
To: Karsten Merker <merker@debian.org>
Cc: linux-riscv@lists.infradead.org,
	Palmer Dabbelt <palmer@sifive.com>,
	sw-dev@groups.riscv.org, pintu.ping@gmail.com, rjones@redhat.com
Subject: Re: [sw-dev] Re: [isa-dev] riscv-qemu - linux boot is failing for vda device
Date: Wed, 17 Oct 2018 11:30:50 +1300	[thread overview]
Message-ID: <D9003246-0336-4327-97D3-D8F079F640D3@mac.com> (raw)
Message-ID: <20181016223050.rtxiXDmJdmyLVHnF7mA3NbjfaIf_BKK77IEpj_EaojE@z> (raw)
In-Reply-To: <20181016200245.j2gesmdjgoi7zmqh@excalibur.cnev.de>



> On 17/10/2018, at 9:02 AM, Karsten Merker <merker@debian.org> wrote:
> 
>> On Tue, Oct 16, 2018 at 11:38:53AM -0700, Palmer Dabbelt wrote:
>>> On Tue, 16 Oct 2018 06:12:11 PDT (-0700), pintu.ping@gmail.com wrote:
>>>> On Tue, Oct 16, 2018 at 6:10 AM Palmer Dabbelt <palmer@sifive.com> wrote:
>>>> On Mon, 15 Oct 2018 14:14:51 PDT (-0700), rjones@redhat.com wrote:
> [...]
>>>> Your best bet today is to run 4.19-rc8, which should be pretty stable.
>>> 
>>> Yes, I checked with mainline linux-kernel 4.19.
>>> Now I am able to boot successfully and login into qemu-riscv shell.
>>> Thank you so much :)
>>> 
>>> But I am curious to know what changes resulted into this fix, in 4.19 kernel ?
>>> Which is the exact patch in mainline, that fixes this issue?
>>> Because at times during the development, it will be difficult to
>>> simply upgrade the kernel version.
>> 
>> Yes, that's expected.  RISC-V Linux is still pretty bleeding edge, you just
>> happened to catch it between when master started working and when there was
>> a proper release that contained your patches.  Since master is very calm
>> right now (there was an rc8 before release, but it's very close to a
>> release) it's OK to use, but you best bet going forward is to use the
>> release tarballs just like normal.
> 
> Just as a data point in case you should find it helpful: I'm
> since two weeks running 4.19-rc6/-rc7 on the qemu-riscv "virt"
> board under permanent heavy load (the system is running a Debian
> package builder) without a single hiccup.

Hi Karsten,

Have you tried riscv-qemu? I know qemu-riscv gets quite a lot of testing but I’d like to gain some more confidence in riscv-qemu.

We might have a PLIC bug in QEMU. If anyone has a reproducer they can file an issue on the riscv-qemu issue tracker and I’ll take a look...

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

  reply	other threads:[~2018-10-16 22:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-15 14:00 riscv-qemu - linux boot is failing for vda device Pintu Kumar
2018-10-15 14:00 ` Pintu Kumar
2018-10-15 20:26 ` [isa-dev] " Michael Clark
2018-10-15 20:26   ` Michael Clark
2018-10-15 21:14   ` [sw-dev] " Richard W.M. Jones
2018-10-15 21:14     ` Richard W.M. Jones
2018-10-16  0:40     ` Palmer Dabbelt
2018-10-16  0:40       ` Palmer Dabbelt
2018-10-16 13:12       ` Pintu Kumar
2018-10-16 13:12         ` Pintu Kumar
2018-10-16 13:30         ` Richard W.M. Jones
2018-10-16 13:30           ` Richard W.M. Jones
2018-10-16 18:38         ` Palmer Dabbelt
2018-10-16 18:38           ` Palmer Dabbelt
2018-10-16 20:02           ` Karsten Merker
2018-10-16 22:30             ` Michael Clark [this message]
2018-10-16 22:30               ` Michael Clark
2018-10-17  5:19               ` Karsten Merker
2018-10-17  7:34                 ` Michael Clark
2018-10-17  7:34                   ` Michael Clark
2018-10-17 12:03           ` Pintu Agarwal
2018-10-17 12:03             ` Pintu Agarwal

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=D9003246-0336-4327-97D3-D8F079F640D3@mac.com \
    --to=michaeljclark@mac.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).