From owner-freebsd-hardware@FreeBSD.ORG Thu May 31 18:59:43 2012 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B920C106566C for ; Thu, 31 May 2012 18:59:43 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 8EFC28FC1E for ; Thu, 31 May 2012 18:59:43 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 0D67DB968; Thu, 31 May 2012 14:59:43 -0400 (EDT) From: John Baldwin To: Mike Tancsa Date: Thu, 31 May 2012 14:43:56 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p13; KDE/4.5.5; amd64; ; ) References: <4FC03C83.4030109@sentex.net> <201205311057.05234.jhb@freebsd.org> <4FC7AD6F.60004@sentex.net> In-Reply-To: <4FC7AD6F.60004@sentex.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201205311443.56648.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 31 May 2012 14:59:43 -0400 (EDT) Cc: pyunyh@gmail.com, freebsd-hardware@freebsd.org Subject: Re: pcie realtek issue (re driver) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 May 2012 18:59:43 -0000 On Thursday, May 31, 2012 1:42:07 pm Mike Tancsa wrote: > On 5/31/2012 10:57 AM, John Baldwin wrote: > >> > >> Right, but what if it is not(from the pciconf output)? > >> I'm pretty sure re(4) used RF_ACTIVE with bus_alloc_resource_any(9). > > > > Hmm, is this pciconf output when the driver is attached? > > Hi, > Here are some of the variations attached in a txt file. Could this > just be a broken card ? I will try and boot up another OS on the box > and see if it works. So it seems it is not honoring our writes to the command register to turn on I/O or memory decoding. Oh weird, in your last case it seems they are enabled. (Driver not loaded at all). Wonder if something in the driver startup is stomping on the PCI command register (e.g. in the firmware). Might be interesting to add printfs in re_attach() and see when the relevant bits in the command register change (e.g. do they get turned off by re_reset()). -- John Baldwin