From: rjones@redhat.com (Richard W.M. Jones)
To: linux-riscv@lists.infradead.org
Subject: [sw-dev] Re: [isa-dev] riscv-qemu - linux boot is failing for vda device
Date: Tue, 16 Oct 2018 14:30:29 +0100 [thread overview]
Message-ID: <20181016133029.GY27120@redhat.com> (raw)
In-Reply-To: <CAOuPNLiR+BLUno8sYjwLwW1BqJbBrH-suBiHEx1-dtMO906Ung@mail.gmail.com>
On Tue, Oct 16, 2018 at 06:42:11PM +0530, Pintu Kumar 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:
>
> > >
> > >> > virtio_blk: probe of virtio0 failed with error -22
> > >
> > > ... I saw this exact error when I was using the upstream kernel
> > > instead of the one which supported interrupt handling. Interrupt
> > > handling for RISC-V was added upstream after 4.18 so wouldn't be
> > > included in upstream 4.18.0-rc6.
> >
> > 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?
It'll be one of the interrupt or irqchip patches here:
https://github.com/riscv/riscv-linux/commits/riscv-linux-4.18
You should follow Palmer's advice and use the kernel he recommends
rather than trying to cherry pick patches.
Rich.
> Because at times during the development, it will be difficult to
> simply upgrade the kernel version.
> So, I wanted to stick to 4.18 itself, however I can back port the
> patches from 4.19 to fix the issue.
> So, if you can point me to the exact patch, it will be of great help.
>
> Thanks,
> Pintu
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
WARNING: multiple messages have this Message-ID (diff)
From: "Richard W.M. Jones" <rjones@redhat.com>
To: Pintu Kumar <pintu.ping@gmail.com>
Cc: linux-riscv@lists.infradead.org, palmer@sifive.com,
sw-dev@groups.riscv.org, Michael Clark <michaeljclark@mac.com>
Subject: Re: [sw-dev] Re: [isa-dev] riscv-qemu - linux boot is failing for vda device
Date: Tue, 16 Oct 2018 14:30:29 +0100 [thread overview]
Message-ID: <20181016133029.GY27120@redhat.com> (raw)
Message-ID: <20181016133029.OPhnnJtO0QXP5YOyeIz6cw_UL7OyUTbSQ0nFttISChk@z> (raw)
In-Reply-To: <CAOuPNLiR+BLUno8sYjwLwW1BqJbBrH-suBiHEx1-dtMO906Ung@mail.gmail.com>
On Tue, Oct 16, 2018 at 06:42:11PM +0530, Pintu Kumar 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:
>
> > >
> > >> > virtio_blk: probe of virtio0 failed with error -22
> > >
> > > ... I saw this exact error when I was using the upstream kernel
> > > instead of the one which supported interrupt handling. Interrupt
> > > handling for RISC-V was added upstream after 4.18 so wouldn't be
> > > included in upstream 4.18.0-rc6.
> >
> > 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?
It'll be one of the interrupt or irqchip patches here:
https://github.com/riscv/riscv-linux/commits/riscv-linux-4.18
You should follow Palmer's advice and use the kernel he recommends
rather than trying to cherry pick patches.
Rich.
> Because at times during the development, it will be difficult to
> simply upgrade the kernel version.
> So, I wanted to stick to 4.18 itself, however I can back port the
> patches from 4.19 to fix the issue.
> So, if you can point me to the exact patch, it will be of great help.
>
> Thanks,
> Pintu
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2018-10-16 13: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 [this message]
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
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=20181016133029.GY27120@redhat.com \
--to=rjones@redhat.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 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.