From: Alistair <alistair23@gmail.com>
To: Stephen Bates <sbates@raithlin.com>,
Andrea Bolognani <abologna@redhat.com>,
Alistair Francis <Alistair.Francis@wdc.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"mjc@sifive.com" <mjc@sifive.com>
Cc: Keith Busch <keith.busch@intel.com>,
"palmer@sifive.com" <palmer@sifive.com>,
"Richard W.M. Jones" <rjones@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5 0/5] Connect a PCIe host and graphics support to RISC-V
Date: Wed, 10 Oct 2018 11:01:48 -0700 [thread overview]
Message-ID: <63b741e2-b3e5-283a-4dfc-9c1db757c575@gmail.com> (raw)
In-Reply-To: <5A5F4A2B-2DAF-4D70-BF1D-7ABC8461FDC8@raithlin.com>
On 10/10/2018 10:32 AM, Stephen Bates wrote:
>>> I plan to also try with a e1000 network interface model tomorrow and see how that behaves....
>>
>> Please do :)
>
> I added e1000 and e1000e support to my kernel and changed the QEMU command to:
>
> $QEMU -nographic \
> -machine virt \
> -smp 1 -m 8G \
> -append "console=hvc0 ro root=/dev/vda nvme.admin_timeout=1" \
> -kernel $KERNEL \
> -drive file=${ROOTFS},format=raw,id=hd0 \
> -device virtio-blk-device,drive=hd0 \
> -device virtio-net-device,netdev=net0 \
> -netdev user,id=net0 \
> -device e1000,netdev=net1 \
> -netdev user,id=net1
Why do you need two networking options?
>
> And the kernel ooops:
>
> [ 0.224000] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
> [ 0.224000] e1000: Copyright (c) 1999-2006 Intel Corporation.
> [ 0.224000] e1000 0000:00:01.0: enabling device (0000 -> 0002)
> [ 0.244000] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
> [ 0.244000] Oops [#1]
> [ 0.244000] Modules linked in:
> [ 0.244000] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.19.0-rc6-eideticom-riscv-00038-gc2b45b2fe26a-dirty #41
> [ 0.244000] sepc: ffffffd20040cc18 ra : ffffffd20040e912 sp : ffffffd3f7a77b60
> [ 0.244000] gp : ffffffd2007e5960 tp : ffffffd3f7ac0000 t0 : ffffffd3f754b4c0
> [ 0.244000] t1 : 0000000000000000 t2 : 00000000000003af s0 : ffffffd3f7a77b70
> [ 0.244000] s1 : ffffffd3f7554b20 a0 : ffffffd3f7554b20 a1 : 0000000000000000
> [ 0.244000] a2 : 0000000000000000 a3 : 0000000000000001 a4 : 0000000000000002
> [ 0.244000] a5 : 0000000000000002 a6 : 00000000eac0c6e6 a7 : 0000000000000000
> [ 0.244000] s2 : 0000000004140240 s3 : 0000000000000000 s4 : ffffffd3f7554f08
> [ 0.244000] s5 : ffffffd3f7554000 s6 : ffffffd2007e7794 s7 : ffffffd3f7555000
> [ 0.244000] s8 : ffffffd3f75546c0 s9 : ffffffd3f7554b20 s10: 0000000000001000
> [ 0.244000] s11: 0000000000000000 t3 : ffffffd20078e918 t4 : ffffffd20078e920
> [ 0.244000] t5 : 0000000000000007 t6 : 0000000000000006
> [ 0.244000] sstatus: 0000000000000120 sbadaddr: 0000000000000000 scause: 000000000000000f
> [ 0.252000] ---[ end trace 371f7702831e633b ]---
Strange. Is there any reason you need to use the e1000? The VirtIO
networking device works for me.
Alistair
>
>
next prev parent reply other threads:[~2018-10-10 18:01 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 20:06 [Qemu-devel] [PATCH v5 0/5] Connect a PCIe host and graphics support to RISC-V Alistair Francis
2018-10-04 20:06 ` [Qemu-devel] [PATCH v5 1/5] hw/riscv/virt: Increase the number of interrupts Alistair Francis
2018-10-04 20:06 ` [Qemu-devel] [PATCH v5 2/5] hw/riscv/virt: Connect the gpex PCIe Alistair Francis
2018-10-25 18:47 ` Peter Maydell
2018-10-30 21:39 ` Alistair Francis
2018-10-04 20:06 ` [Qemu-devel] [PATCH v5 3/5] riscv: Enable VGA and PCIE_VGA Alistair Francis
2018-10-04 20:06 ` [Qemu-devel] [PATCH v5 4/5] hw/riscv/sifive_u: Connect the Xilinx PCIe Alistair Francis
2018-10-04 20:06 ` [Qemu-devel] [PATCH v5 5/5] hw/riscv/virt: Connect a VirtIO net PCIe device Alistair Francis
2018-10-10 12:26 ` [Qemu-devel] [PATCH v5 0/5] Connect a PCIe host and graphics support to RISC-V Andrea Bolognani
2018-10-10 13:11 ` Stephen Bates
2018-10-10 13:43 ` Andrea Bolognani
2018-10-10 17:24 ` Stephen Bates
2018-10-10 17:32 ` Stephen Bates
2018-10-10 18:01 ` Alistair [this message]
2018-10-10 18:47 ` Stephen Bates
2018-10-10 19:53 ` Alistair
2018-10-11 5:45 ` Andrea Bolognani
2018-10-10 19:01 ` Stephen Bates
2018-10-10 19:55 ` Alistair
2018-10-10 17:57 ` Alistair
2018-10-11 5:59 ` Andrea Bolognani
2018-10-11 7:55 ` Richard W.M. Jones
2018-10-11 12:00 ` Peter Maydell
2018-10-11 8:01 ` Richard W.M. Jones
2018-10-11 11:45 ` Richard W.M. Jones
2018-10-11 12:15 ` Andrea Bolognani
2018-10-11 12:25 ` Stephen Bates
2018-10-11 17:40 ` Alistair Francis
2018-10-12 13:46 ` Andrea Bolognani
2018-10-12 16:12 ` Alistair Francis
2018-10-15 14:39 ` Andrea Bolognani
2018-10-15 16:59 ` Alistair Francis
2018-10-16 7:38 ` Andrea Bolognani
2018-10-16 14:11 ` Andrea Bolognani
2018-10-16 14:55 ` Andrea Bolognani
2018-10-16 17:31 ` Stephen Bates
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=63b741e2-b3e5-283a-4dfc-9c1db757c575@gmail.com \
--to=alistair23@gmail.com \
--cc=Alistair.Francis@wdc.com \
--cc=abologna@redhat.com \
--cc=keith.busch@intel.com \
--cc=mjc@sifive.com \
--cc=palmer@sifive.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=sbates@raithlin.com \
/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).