From owner-freebsd-net@freebsd.org Sat Sep 12 10:43:50 2015 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 8DA50A027C3 for ; Sat, 12 Sep 2015 10:43:50 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5187D1395 for ; Sat, 12 Sep 2015 10:43:50 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1ZaiHb-000Fqw-2d; Sat, 12 Sep 2015 11:43:47 +0100 Date: Sat, 12 Sep 2015 11:43:47 +0100 From: Gary Palmer To: Sreenath Battalahalli Cc: Marius Strobl , freebsd-net@freebsd.org Subject: Re: realtek interface not working Message-ID: <20150912104347.GA45080@in-addr.com> References: <20150910191240.GA97360@alchemy.franken.de> <1442037456.3232.YahooMailBasic@web122106.mail.ne1.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1442037456.3232.YahooMailBasic@web122106.mail.ne1.yahoo.com> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Sep 2015 10:43:50 -0000 On Fri, Sep 11, 2015 at 10:57:36PM -0700, Sreenath Battalahalli wrote: > Hi Marius, > > Thanks for the patch. I manually made changes to the two files, and after building the kernel and installing it, > I can see the re0 interface. I am now sending this email using the new laptop. > > However, I am a bit confused by the dmesg output. I see two sets of lines pertaining to the re0 device. > > $dmesg | grep -i re0 > > re0: port 0x3000-0x30ff mem 0xb0604000-0xb0604fff,0xb0600000-0xb0603fff irq 18 at device 0.0 on pci2 > re0: Using 1 MSI-X message > re0: turning off MSI enable bit. > re0: ASPM disabled > re0: Chip rev. 0x54000000 > re0: MAC rev. 0x00100000 > re0: Unknown H/W revision: 0x54000000 > device_attach: re0 attach returned 6 > re0: port 0x3000-0x30ff mem 0xb0604000-0xb0604fff,0xb0600000-0xb0603fff irq 18 at device 0.0 on pci2 > re0: Using 1 MSI-X message > re0: ASPM disabled > re0: Chip rev. 0x54000000 > re0: MAC rev. 0x00100000 > miibus0: on re0 > re0: Using defaults for TSO: 65518/35/2048 > re0: Ethernet address: 2c:60:0c:92:0f:c2 > > seems the driver attempted to initialize the device twice? > > Anyway, it is working now. The kernel dmesg buffer can be preserved over a reboot, so it's possible the lines up to and including "device_attach: re0 attach returned 6" are from the reboot before you installed the patch. Rather than just grep for re0, do "dmesg | less" or "dmesg | more" and check the context of the "device_attach: re0 attach returned 6" error and see if there are any indications of a reboot between that line and the next re0 probe lines, e.g. "Copyright (c) 1992-2015 The FreeBSD Project" Regards, Gary