pcie realtek issue (re driver)

[YongHyeon PYUN]

On Thu, May 31, 2012 at 02:05:53PM -0400, Mike Tancsa wrote:
> On 5/31/2012 1:42 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.
> 
> Oh, and doing a load post reboot,
> 
> 0{intel-i3}# kldload if_re
> pci0: driver added
> found-> vendor=0x8086, dev=0x1c3a, revid=0x04
>         domain=0, bus=0, slot=22, func=0
>         class=07-80-00, hdrtype=0x00, mfdev=1
>         cmdreg=0x0006, statreg=0x0010, cachelnsz=0 (dwords)
>         lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
>         intpin=a, irq=16
>         powerspec 3  supports D0 D3  current D0
>         MSI supports 1 message, 64 bit
> pci0:0:22:0: reprobing on driver added
> found-> vendor=0x8086, dev=0x1c22, revid=0x05
>         domain=0, bus=0, slot=31, func=3
>         class=0c-05-00, hdrtype=0x00, mfdev=0
>         cmdreg=0x0003, statreg=0x0280, cachelnsz=0 (dwords)
>         lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
>         intpin=c, irq=18
> pci0:0:31:3: reprobing on driver added
> pci1: driver added
> pci2: driver added
> pci3: driver added
> pci4: driver added
> found-> vendor=0x10ec, dev=0x8168, revid=0x03
>         domain=0, bus=4, slot=0, func=0
>         class=02-00-00, hdrtype=0x00, mfdev=0
>         cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords)
>         lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
>         intpin=a, irq=255
>         powerspec 3  supports D0 D1 D2 D3  current D0
>         MSI supports 1 message, 64 bit
>         MSI-X supports 4 messages in map 0x20
> pci0:4:0:0: reprobing on driver added
> re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F PCIe Gigabit Ethernet> at device
> 0.0 on pci4
> pci4: child re0 requested type 3 for rid 0x18, but the BAR says it is an
> ioport
> pcib4: allocated I/O port range (0xd000-0xd0ff) for rid 10 of re0
> re0: Lazy allocation of 0x100 bytes rid 0x10 type 4 at 0xd000

This is the first time I saw BAR2 is I/O space on RealTek PCI
express device. re(4) switched to use BAR0 with I/O space after
failing to use BAR2. Could you try attached patch?

> re0: MSI count : 1
> re0: MSI-X count : 4
> pcib4: allocated prefetch range (0xf0000000-0xf0003fff) for rid 20 of re0
> re0: Lazy allocation of 0x4000 bytes rid 0x20 type 3 at 0xf0000000
> re0: attempting to allocate 1 MSI-X vectors (4 supported)
> msi: routing MSI-X IRQ 270 to local APIC 1 vector 52
> re0: using IRQ 270 for MSI-X
> re0: Using 1 MSI-X message
> re0: Chip rev. 0x28000000
> re0: MAC rev. 0x00000000
> miibus0: <MII bus> on re0
> rgephy0: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 1 on miibus0
> rgephy0: OUI 0x00e04c, model 0x0011, rev. 2
> rgephy0:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX,
> 100baseTX-FDX, 100baseTX-FDX-flow, 100baseT4, 1000baseSX,
> 1000baseSX-FDX, 1000baseSX-FDX-flow, 1000baseT, 1000baseT-master,
> 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow,
> 1000baseT-FDX-flow-master, auto, auto-flow
> re0: PHY write failed
> re0: PHY write failed
> re0: bpf attached
> re0: Ethernet address: 00:0a:cd:1c:ba:89
> pci5: driver added
> pci6: driver added
> 0{intel-i3}#
> 0{intel-i3}# ifconfig re0 up
> re0: reset never completed!
> re0: PHY write failed
> re0: PHY write failed
> re0: PHY write failed
> re0: PHY write failed
> re0: PHY write failed
> re0: PHY write failed
> re0: PHY write failed
> 0{intel-i3}#
-------------- next part --------------
A non-text attachment was scrubbed...
Name: re.map.diff
Type: text/x-diff
Size: 1176 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-hardware/attachments/20120601/27031821/re.map.bin