From: Shannon Nelson <shannon.nelson@intel.com> To: Stefan Assmann <sassmann@redhat.com> Cc: jacob jacob <opstkusr@gmail.com>, Bandan Das <bsd@redhat.com>, Alex Williamson <alex.williamson@redhat.com>, QEMU Developers <qemu-devel@nongnu.org>, kvm-devel <kvm@vger.kernel.org>, netdev@vger.kernel.org Subject: Re: [Qemu-devel] PCI passthrough of 40G ethernet interface (Openstack/KVM) Date: Thu, 19 Mar 2015 09:26:55 -0700 [thread overview] Message-ID: <CAP-MU4N8DsafjBWUVw5Fw0pdnjfYszbARpoRmnFn=s=MsQtGzw@mail.gmail.com> (raw) In-Reply-To: <550A85B3.4070703@redhat.com> On Thu, Mar 19, 2015 at 1:15 AM, Stefan Assmann <sassmann@redhat.com> wrote: > Interesting, the following might explain why my XL710 feels a bit > sketchy then. ;-) > # ethtool -i p4p1 > driver: i40e > version: 1.2.37-k > firmware-version: f4.22.26225 a1.1 n4.24 e12ef > Looks like the firmware on this NIC is even older. > > I tried to update the firmware with nvmupdate64e and the first thing I > noticed is that you cannot update the firmware even with todays linux > git. The tool errors out because it cannot access the NVM. Only with a > recent net-next kernel I was able to update the firmware. > ethtool -i p4p1 > driver: i40e > version: 1.2.37-k > firmware-version: f4.33.31377 a1.2 n4.42 e1932 > > However during the update I got a lot of errors in dmesg. > [ 301.796664] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0702 received > [ 301.893933] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received > [ 302.005223] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received > [...] > [ 387.884635] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received > [ 387.896862] i40e 0000:82:00.0: ARQ Overflow Error detected > [ 387.902995] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received These are bogus messages should not have been generated, but it seems there's a case statement missing in the upstream code. I'll get a patch together for this later today. > [...] > [ 391.583799] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2 > [ 391.714217] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2 > [ 391.842656] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2 > [ 391.973080] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2 > [ 392.107586] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2 > [ 392.244140] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2 > [ 392.373966] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received These are an annoying result of a user tool issue. > > Not sure if that flash was actually successful or not. Since the driver was able to restart and give you the version information from ethtool -i, the update was successful. You are not supposed to have to powercycle your system after the NVM update, but it's a good idea anyway, especially when updating the older firmware like what you had. sln
WARNING: multiple messages have this Message-ID (diff)
From: Shannon Nelson <shannon.nelson@intel.com> To: Stefan Assmann <sassmann@redhat.com> Cc: kvm-devel <kvm@vger.kernel.org>, Bandan Das <bsd@redhat.com>, netdev@vger.kernel.org, Alex Williamson <alex.williamson@redhat.com>, QEMU Developers <qemu-devel@nongnu.org>, jacob jacob <opstkusr@gmail.com> Subject: Re: [Qemu-devel] PCI passthrough of 40G ethernet interface (Openstack/KVM) Date: Thu, 19 Mar 2015 09:26:55 -0700 [thread overview] Message-ID: <CAP-MU4N8DsafjBWUVw5Fw0pdnjfYszbARpoRmnFn=s=MsQtGzw@mail.gmail.com> (raw) In-Reply-To: <550A85B3.4070703@redhat.com> On Thu, Mar 19, 2015 at 1:15 AM, Stefan Assmann <sassmann@redhat.com> wrote: > Interesting, the following might explain why my XL710 feels a bit > sketchy then. ;-) > # ethtool -i p4p1 > driver: i40e > version: 1.2.37-k > firmware-version: f4.22.26225 a1.1 n4.24 e12ef > Looks like the firmware on this NIC is even older. > > I tried to update the firmware with nvmupdate64e and the first thing I > noticed is that you cannot update the firmware even with todays linux > git. The tool errors out because it cannot access the NVM. Only with a > recent net-next kernel I was able to update the firmware. > ethtool -i p4p1 > driver: i40e > version: 1.2.37-k > firmware-version: f4.33.31377 a1.2 n4.42 e1932 > > However during the update I got a lot of errors in dmesg. > [ 301.796664] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0702 received > [ 301.893933] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received > [ 302.005223] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received > [...] > [ 387.884635] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received > [ 387.896862] i40e 0000:82:00.0: ARQ Overflow Error detected > [ 387.902995] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received These are bogus messages should not have been generated, but it seems there's a case statement missing in the upstream code. I'll get a patch together for this later today. > [...] > [ 391.583799] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2 > [ 391.714217] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2 > [ 391.842656] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2 > [ 391.973080] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2 > [ 392.107586] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2 > [ 392.244140] i40e 0000:82:00.0: NVMUpdate write failed err=-53 status=0x0 errno=-16 module=70 offset=0x0 size=2 > [ 392.373966] i40e 0000:82:00.0: ARQ Error: Unknown event 0x0703 received These are an annoying result of a user tool issue. > > Not sure if that flash was actually successful or not. Since the driver was able to restart and give you the version information from ethtool -i, the update was successful. You are not supposed to have to powercycle your system after the NVM update, but it's a good idea anyway, especially when updating the older firmware like what you had. sln
next prev parent reply other threads:[~2015-03-19 16:26 UTC|newest] Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-12 16:17 PCI passthrough of 40G ethernet interface (Openstack/KVM) jacob jacob 2015-03-12 16:17 ` [Qemu-devel] " jacob jacob 2015-03-12 16:26 ` Alex Williamson 2015-03-12 16:26 ` [Qemu-devel] " Alex Williamson 2015-03-12 16:36 ` jacob jacob 2015-03-12 16:36 ` [Qemu-devel] " jacob jacob 2015-03-12 19:07 ` Bandan Das 2015-03-12 19:07 ` [Qemu-devel] " Bandan Das 2015-03-12 23:11 ` jacob jacob 2015-03-12 23:11 ` [Qemu-devel] " jacob jacob 2015-03-13 0:02 ` Bandan Das 2015-03-13 0:02 ` [Qemu-devel] " Bandan Das 2015-03-13 14:08 ` jacob jacob 2015-03-13 14:08 ` [Qemu-devel] " jacob jacob 2015-03-16 16:31 ` jacob jacob 2015-03-16 16:31 ` [Qemu-devel] " jacob jacob 2015-03-16 18:12 ` Bandan Das 2015-03-16 18:24 ` jacob jacob 2015-03-16 19:49 ` Bandan Das 2015-03-16 19:58 ` jacob jacob 2015-03-18 15:24 ` Bandan Das 2015-03-18 15:24 ` Bandan Das 2015-03-18 15:40 ` jacob jacob 2015-03-18 15:40 ` jacob jacob 2015-03-18 22:01 ` Shannon Nelson 2015-03-18 22:01 ` [Qemu-devel] " Shannon Nelson 2015-03-18 22:06 ` Shannon Nelson 2015-03-18 22:06 ` Shannon Nelson 2015-03-19 8:15 ` Stefan Assmann 2015-03-19 8:15 ` Stefan Assmann 2015-03-19 14:00 ` jacob jacob 2015-03-19 14:00 ` [Qemu-devel] " jacob jacob 2015-03-19 14:04 ` jacob jacob 2015-03-19 14:04 ` jacob jacob 2015-03-19 14:18 ` Stefan Assmann 2015-03-19 14:18 ` Stefan Assmann 2015-03-20 20:55 ` jacob jacob 2015-03-20 20:55 ` jacob jacob 2015-03-23 7:19 ` Stefan Assmann 2015-03-23 7:19 ` Stefan Assmann 2015-03-24 14:13 ` jacob jacob 2015-03-24 14:13 ` jacob jacob 2015-03-24 14:53 ` Shannon Nelson 2015-03-24 14:53 ` Shannon Nelson 2015-03-24 15:04 ` jacob jacob 2015-03-24 15:04 ` [Qemu-devel] " jacob jacob 2015-03-26 1:00 ` Shannon Nelson 2015-03-26 1:00 ` Shannon Nelson 2015-03-19 16:26 ` Shannon Nelson [this message] 2015-03-19 16:26 ` Shannon Nelson 2015-03-19 21:04 ` jacob jacob 2015-03-19 21:04 ` jacob jacob 2015-03-19 21:42 ` Shannon Nelson 2015-03-19 21:42 ` Shannon Nelson 2015-03-19 21:53 ` jacob jacob 2015-03-19 21:53 ` jacob jacob 2015-03-19 23:37 ` jacob jacob 2015-03-19 23:37 ` [Qemu-devel] " jacob jacob -- strict thread matches above, loose matches on Subject: below -- 2015-03-12 16:11 jacob jacob 2015-03-12 16:13 ` jacob jacob
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='CAP-MU4N8DsafjBWUVw5Fw0pdnjfYszbARpoRmnFn=s=MsQtGzw@mail.gmail.com' \ --to=shannon.nelson@intel.com \ --cc=alex.williamson@redhat.com \ --cc=bsd@redhat.com \ --cc=kvm@vger.kernel.org \ --cc=netdev@vger.kernel.org \ --cc=opstkusr@gmail.com \ --cc=qemu-devel@nongnu.org \ --cc=sassmann@redhat.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: linkBe 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.