From owner-freebsd-stable@FreeBSD.ORG Fri Jun 27 06:18:31 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9790C70A; Fri, 27 Jun 2014 06:18:31 +0000 (UTC) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.12]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4793A2600; Fri, 27 Jun 2014 06:18:30 +0000 (UTC) Received: from th-04.cs.huji.ac.il ([132.65.80.125]) by kabab.cs.huji.ac.il with esmtp id 1X0PUM-000IQ5-6j; Fri, 27 Jun 2014 09:18:22 +0300 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) Subject: Re: pci issues with SBC (AMD G-T40E) - PCEngines apu From: Daniel Braniss In-Reply-To: <201406251117.55634.jhb@freebsd.org> Date: Fri, 27 Jun 2014 09:17:59 +0300 Message-Id: <5FAF1189-4200-4B2D-8049-F317BA174BB5@cs.huji.ac.il> References: <0D577669-BF58-4B30-B29A-9A5B05C95112@cs.huji.ac.il> <201406241111.42023.jhb@freebsd.org> <3920AC99-4197-4A36-A573-3D283F36E035@cs.huji.ac.il> <201406251117.55634.jhb@freebsd.org> To: John Baldwin X-Mailer: Apple Mail (2.1878.2) Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2014 06:18:31 -0000 I let it cool off overnight, and has been ok ever since, very strange. danny On Jun 25, 2014, at 6:17 PM, John Baldwin wrote: > On Wednesday, June 25, 2014 7:57:12 am Daniel Braniss wrote: >>=20 >> On Jun 24, 2014, at 6:11 PM, John Baldwin wrote: >>=20 >>> On Tuesday, June 24, 2014 6:48:56 am Daniel Braniss wrote: >>>> Hi all, >>>> the short story is that not always all the devices are discovered >>>> correctly, i.e. there are 3 RealTek and sometimes all 3 are = discovered, >>>> sometimes 2,sometimes only one. >>>> My guts are telling me it=92s a timing issue, is there some delay I = can put in? >>>> I tried booting verbose but the problem is till there. >>>> example: >>>> =85 >>>> re1: = port 0x2000-0x20ff mem 0xf7b00000-0xf7b00fff,0xf7a00000-0xf7a03fff irq = 17 at device 0.0 on=20 > pci2 >>>> re1: MSI count : 1 >>>> re1: MSI-X count : 4 >>>> re1: attempting to allocate 1 MSI-X vectors (4 supported) >>>> msi: routing MSI-X IRQ 260 to local APIC 0 vector 55 >>>> re1: using IRQ 260 for MSI-X >>>> re1: Using 1 MSI-X message >>>> re1: ASPM disabled >>>> re1: Chip rev. 0x2c000000 >>>> re1: MAC rev. 0x00200000 >>>> miibus1: on re1 >>>> rgephy1: PHY 1 on = miibus1 >>>> rgephy1: OUI 0x00e04c, model 0x0011, rev. 4 >>>> rgephy1: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, = 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, = 1000baseT-FDX, 1000baseT- > FDX- >>> master, 1000baseT- >>>> FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow >>>> re1: bpf attached >>>> re1: Ethernet address: 00:0d:b9:34:28:c5 >>>> pcib3: irq 18 at device 6.0 on pci0 >>>> pcib0: allocated type 4 (0x3000-0x3fff) for rid 1c of pcib3 >>>> pcib0: allocated type 3 (0xf7d00000-0xf7dfffff) for rid 20 of pcib3 >>>> pcib0: allocated type 3 (0xf7c00000-0xf7cfffff) for rid 24 of pcib3 >>>> pcib3: domain 0 >>>> pcib3: secondary bus 3 >>>> pcib3: subordinate bus 3 >>>> pcib3: I/O decode 0x3000-0x3fff >>>> pcib3: memory decode 0xf7d00000-0xf7dfffff >>>> pcib3: prefetched decode 0xf7c00000-0xf7cfffff >>>> pci3: on pcib3 >>>> pci3: domain=3D0, physical bus=3D3 >>>> found-> vendor=3D0x10ec, dev=3D0x8168, revid=3D0x06 >>>> domain=3D0, bus=3D3, slot=3D0, func=3D0 >>>> class=3D02-00-00, hdrtype=3D0x00, mfdev=3D0 >>>> cmdreg=3D0x0007, statreg=3D0x0010, cachelnsz=3D16 (dwords) >>>> lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 = (0 ns) >>>> intpin=3Da, irq=3D10 >>>> powerspec 3 supports D0 D1 D2 D3 current D0 >>>> MSI supports 1 message, 64 bit >>>> MSI-X supports 4 messages in map 0x20 >>>> map[10]: type I/O Port, range 32, base 0x3000, size 8, = enabled >>>> pcib3: allocated I/O port range (0x3000-0x30ff) for rid 10 of = pci0:3:0:0 >>>> map[18]: type Memory, range 64, base 0xf7d00000, size 12, = enabled >>>> pcib3: allocated memory range (0xf7d00000-0xf7d00fff) for rid 18 of = pci0:3:0:0 >>>> map[20]: type Prefetchable Memory, range 64, base 0xf7c00000, = size 14, enabled >>>> pcib3: allocated prefetch range (0xf7c00000-0xf7c03fff) for rid 20 = of pci0:3:0:0 >>>> pcib3: matched entry for 3.0.INTA >>>> pcib3: slot 0 INTA hardwired to IRQ 18 >>>> re2: = port 0x3000-0x30ff mem 0xf7d00000-0xf7d00fff,0xf7c00000-0xf7c03fff irq = 18 at device 0.0 on=20 > pci3 >>>> re2: MSI count : 1 >>>> re2: MSI-X count : 4 >>>> re2: attempting to allocate 1 MSI-X vectors (4 supported) >>>> msi: routing MSI-X IRQ 261 to local APIC 0 vector 56 >>>> re2: using IRQ 261 for MSI-X >>>> re2: Using 1 MSI-X message >>>> re2: ASPM disabled >>>> re2: Chip rev. 0x80000000 >>>> re2: MAC rev. 0x00000000 <=97=97=97=97=97=97=97=97=97------------ = notice this is now zero! >>>> re2: Unknown H/W revision: 0x80000000 >>>> device_attach: re2 attach returned 6 >>>=20 >>> The chip rev also looks wrong. I don't know why you are not getting = the >>> correct values though. I don't see anything obviously wrong like = resource >>> issues with the BARs. >>=20 >> anything I can do to try and track this down?, except diving into the = sources :-) >> i have almost no idea where to start (well, I could with the re = driver =85) >> a flashlight might help. >=20 > Normally when there are resource problems reads of registers return = all 1's > (e.g 0xffffffff). I would check to see if the register reads to = determine the > chip rev are returning that first. >=20 > --=20 > John Baldwin