From owner-freebsd-current@freebsd.org Thu Nov 22 15:34:32 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 93D39114ABD3 for ; Thu, 22 Nov 2018 15:34:32 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 437F07A88C for ; Thu, 22 Nov 2018 15:34:31 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id PqrhgSJvzP7x2Pqrig89yE; Thu, 22 Nov 2018 08:26:04 -0700 X-Authority-Analysis: v=2.3 cv=X9GD11be c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=8nJEP1OIZ-IA:10 a=JHtHm7312UAA:10 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=9bHR7MVLAAAA:8 a=Mvx6gL_OPyv-Vn3nflMA:9 a=wPNLvfGTeEIA:10 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=I7KxNEAtLM9g1UmuDjRu:22 Received: from slippy.cwsent.com (slippy8 [10.2.2.6]) by spqr.komquats.com (Postfix) with ESMTPS id 1D6452426; Thu, 22 Nov 2018 07:26:00 -0800 (PST) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id wAMFPiVe003566; Thu, 22 Nov 2018 07:25:44 -0800 (PST) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id wAMFPfhV003563; Thu, 22 Nov 2018 07:25:42 -0800 (PST) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201811221525.wAMFPfhV003563@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Dan Partelly cc: "Bjoern A. Zeeb" , Warner Losh , FreeBSD Current Subject: Re: Devd / devmatch(8) -- netif race 12-RC1 In-Reply-To: Message from Dan Partelly of "Thu, 22 Nov 2018 08:43:49 +0200." <798C848D-5F32-4BF9-87E0-ADD4F9B743AD@rdsor.ro> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Date: Thu, 22 Nov 2018 07:25:41 -0800 X-CMAE-Envelope: MS4wfOMdzKyf3l5BQCpTZIQjCgtC62okyUHnmHnw4TnSnaLFdeGru6n4pZUfYfoC79wjbJhaXUqfMJjgDghFByZObGeQAsNHEYP7qQ3Moaef1gGe82tfqUUD HTH76x8MpEqozv8G+0wc4NT01X4Scz2EtVwkayTBV6NwnFXjK71uaryk7IfInLrmxXzQkJOzeB65DpMbvJXoXgQ07YmH2nauPeihLaQ2ueNyedscthJZwW9v cbanPVTSMk3N9xSUFYXE0VnZ9BeBdv42xhVG6zhy0EE52UOJQNa5stM4kR7kPmNl X-Rspamd-Queue-Id: 437F07A88C X-Spamd-Result: default: False [-3.54 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; HAS_REPLYTO(0.00)[Cy.Schubert@cschubert.com]; REPLYTO_EQ_FROM(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[spqr.komquats.com]; NEURAL_HAM_SHORT(-0.91)[-0.908,0]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; R_SPF_NA(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[12.134.59.64.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; IP_SCORE(-0.93)[ipnet: 64.59.128.0/20(-2.52), asn: 6327(-2.02), country: CA(-0.09)]; RECEIVED_SPAMHAUS_PBL(0.00)[17.125.67.70.zen.spamhaus.org : 127.0.0.11] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Nov 2018 15:34:32 -0000 In message <798C848D-5F32-4BF9-87E0-ADD4F9B743AD@rdsor.ro>, Dan Partelly writes : > wireless lagg initialization is broken in this scenario, all-right. The init/ > rc system as it is now can’t cope easily with a modern asynchronous initial > ization sequence. Sure you could probably find an order which works, only to > find yourself in trouble next time you want add some modern functionality . > It shows it’s age > > @Warner > > Could you tell me please if devmatcher supports taking over a PCI device whic > h is attached by a generic driver already ? vga attaching modern GPUs comes t > o mind . > > Dan We're missing a fair bit of information to come to any conclusion yet. I've been using lagg with ath + rl and iwn + bge since FreeBSD 8, currently on 13, with zero issues or problems on either of them over the many years I've used this configuration. Can you provide output of sysctl net.wlan.devices, please? Also the relevant bits of rc.conf (with PI redacted of course), and any modifications to devfs.conf. dmesg output and anything relevant in messages might also be helpful. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. > > > > On Nov 20, 2018, at 15:26, Bjoern A. Zeeb > wrote: > > > > On 20 Nov 2018, at 8:17, dan_partelly@rdsor.ro wrote: > > > >>>> No, that's not what's happening. wlan0 isn't racing anything, because it > 's no longer listed in ifconfig > >> > >> > >> But when is created lagg0 ? Acording rc output on screen , creation of clo > ned interface lagg0 takes place before wlan0 is created. Then this means SIO > CLAGPORT will fail with Invalid argument. Also lagg0 is started at netif tim > e as far as I know. > >> Firmware for the wireless card is loaded later, and only even later wlan0 > is created. So the way I see it, lagg0 cannot have a wlan0 port until firmwar > e for the card is loaded and wlan0 is created, which takes place way after th > e system attempts to configure lagg0 ? Am I missing something ? > > > > lagg might be a problem. > > > > > > While we are on the topic: I also noticed on a fixed 10G card that the netw > ork startup it went through strangely wasn’t the same as it was when the dr > iver was loaded and service netif start was called again. I have not had tim > e to debug that any further. > > > > > >> Also, can you please tell me what happens that devmatch tries to load uhi > dd multiple times ? > > > > That’s probably similar to https://bugs.freebsd.org/bugzilla/show_bug.cgi > ?id=232782 ? > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >