From owner-freebsd-net@freebsd.org Tue Jan 23 11:37:17 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C398ECD212 for ; Tue, 23 Jan 2018 11:37:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 81795768E1 for ; Tue, 23 Jan 2018 11:37:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 738A632EF for ; Tue, 23 Jan 2018 11:37:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0NBbHuU063704 for ; Tue, 23 Jan 2018 11:37:17 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0NBbH26063703 for freebsd-net@FreeBSD.org; Tue, 23 Jan 2018 11:37:17 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 225325] RealTek 8169 network devices don't seem to work with memory mapped registers Date: Tue, 23 Jan 2018 11:37:17 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: aaron.styx@baesystems.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2018 11:37:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225325 aaron.styx@baesystems.com changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #189913|0 |1 is obsolete| | --- Comment #3 from aaron.styx@baesystems.com --- Created attachment 189996 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D189996&action= =3Dedit /var/log/messages re1 output After submitting the bug, I did some digging and saw how common this chip i= s, so I would agree that simply forcing all of them to use IO mapped registers= is not the right solution. The attached is the relevant output of /var/log/messages. (Note that this is from a 10.1 Live CD).=20 I clearly need to do some more testing with this. I'll try this card in a different machine, and I'd also like to compile with RE_DIAG to see if this= is simply a known problem with this device, but that will take me a bit. I'm n= ot sure if the 10.1 live cd build is compiled with this or not... As for the meaning of "doesn't work," I'm able to set the address and bring= the device up with ifconfig, which reports the device is up and active. However, any attempts to ping another host on the network results in 'sendto: Host is down.' Wireshark shows no packets coming from the 1869 re device.=20 Other network devices on this machine work as expected, so I know it's not a network issue. Setting hw.re.prefer_iomap=3D1 also works. The device works = on Linux in this machine, though I haven't taken a close look at their driver = yet, or figured out if they're using Memory or IO mapped registers. --=20 You are receiving this mail because: You are the assignee for the bug.=