From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Michal Kubecek <mkubecek@suse.cz>
Cc: Jiri Pirko <jiri@mellanox.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org,
"ms >> Michael S. Tsirkin" <mst@redhat.com>,
linux-s390 <linux-s390@vger.kernel.org>
Subject: Re: 4.4-rc1 errors on bridge/macvtap interfaces (maybe commit 0bc05d58 switchdev: allow caller to exp...).
Date: Mon, 16 Nov 2015 14:36:20 +0100 [thread overview]
Message-ID: <5649DBD4.90800@de.ibm.com> (raw)
In-Reply-To: <20151116131955.GB24489@unicorn.suse.cz>
On 11/16/2015 02:19 PM, Michal Kubecek wrote:
> On Mon, Nov 16, 2015 at 02:00:32PM +0100, Christian Borntraeger wrote:
>>
>> on 4.4-rc1 running on an s390x box (so qeth OSA network cards as real NICs) I get errors like:
>>
>> [ 10.940523] Ebtables v2.0 registered
>> [ 11.685609] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
>> [ 11.686252] virbr0-nic: set_features() failed (-1); wanted 0x00000080000048c1, left 0x00000080001b48c9
>> [ 11.794553] virbr0: error setting offload STP state on port 1(virbr0-nic)
>> [ 11.794556] virbr0-nic: failed to set HW ageing time
>> [ 11.794558] virbr0: error setting offload STP state on port 1(virbr0-nic)
>> [ 11.794644] virbr0-nic: set_features() failed (-1); wanted 0x00000080000048c1, left 0x00000080001b48c9
>> [ 11.794675] device virbr0-nic entered promiscuous mode
>> [ 11.794706] virbr0: set_features() failed (-1); wanted 0x000000801fdb78c9, left 0x000000801fff78e9
>> [ 11.962901] ip_tables: (C) 2000-2006 Netfilter Core Team
>> [ 12.025317] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
>> [ 12.086880] virbr0: set_features() failed (-1); wanted 0x000000801fdb78c9, left 0x000000801fff78e9
>> [ 12.086924] virbr0: error setting offload STP state on port 1(virbr0-nic)
>> [ 12.086926] virbr0-nic: failed to set HW ageing time
>> [ 12.086927] virbr0: error setting offload STP state on port 1(virbr0-nic)
>> [ 12.086928] virbr0: port 1(virbr0-nic) entered listening state
>> [ 12.086934] virbr0: port 1(virbr0-nic) entered listening state
>> [ 12.087023] virbr0: set_features() failed (-1); wanted 0x000000801fdb78c9, left 0x000000801fff78e9
>> [ 12.087057] virbr0-nic: set_features() failed (-1); wanted 0x00000080000048c1, left 0x00000080001b48c9
>> [ 12.087088] virbr0: set_features() failed (-1); wanted 0x000000801fdb78c9, left 0x000000801fff78e9
>> [ 12.087122] virbr0-nic: set_features() failed (-1); wanted 0x00000080000048c1, left 0x00000080001b48c9
>> [ 12.087153] virbr0: set_features() failed (-1); wanted 0x000000801fdb78c9, left 0x000000801fff78e9
>> [ 12.102634] virbr0: error setting offload STP state on port 1(virbr0-nic)
>> [ 12.102637] virbr0: port 1(virbr0-nic) entered disabled state
>>
> ...
>>
>> [ 260.414547] macvtap0: set_features() failed (-1); wanted 0x00000004001f5209, left 0x00000004001f5a09
>> [ 260.414555] macvtap0: set_features() failed (-1); wanted 0x00000004001f5209, left 0x00000004001f5a09
>> [ 260.541477] macvtap0: set_features() failed (-1); wanted 0x00000004001f5209, left 0x00000004001f5a09
>> [ 260.541532] macvtap0: set_features() failed (-1); wanted 0x00000004001f5209, left 0x00000004001f5a09
>> [ 260.541603] macvtap0: set_features() failed (-1); wanted 0x00000004001f5209, left 0x00000004001f5a09
>> [ 260.984503] device enccw0.0.f500 entered promiscuous mode
>>
>> Does somebody have an idea?
>
> Looks like the issue addressed by
>
> http://patchwork.ozlabs.org/patch/544307/
Yes. The set_features error is indeed fixed.
FWIW;
Tested-by: Christian Borntraeger <borntraeger@de.ibm.com>
The other error is independent.
prev parent reply other threads:[~2015-11-16 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 13:00 4.4-rc1 errors on bridge/macvtap interfaces (maybe commit 0bc05d58 switchdev: allow caller to exp...) Christian Borntraeger
2015-11-16 13:19 ` Michal Kubecek
2015-11-16 13:25 ` Jiri Pirko
2015-11-16 13:38 ` Christian Borntraeger
2015-11-16 13:36 ` Christian Borntraeger [this message]
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=5649DBD4.90800@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=davem@davemloft.net \
--cc=jiri@mellanox.com \
--cc=linux-s390@vger.kernel.org \
--cc=mkubecek@suse.cz \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.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).