Current problem reports assigned to freebsd-net@FreeBSD.org

[FreeBSD bugmaster]

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker  Resp.  Description

o kern/152148  net[pfil] vnet_pfil_init() happens too late if pfil_head_
o kern/152141  net[vlan] encapsulate vlan in ng_ether before output to i
o kern/151908  net[netinet6] [patch] nd6_ns_input: panic may happen, for
o kern/151690  netnetwork connectivity won't work until dhclient is run 
o kern/151681  net[nfs] NFS mount via IPv6 leads to hang on client with 
o kern/151593  net[igb] [panic] Kernel panic when bringing up igb networ
o kern/150920  net[ixgbe][igb] Panic when packets are dropped with heade
o bin/150642   netnetstat(1) doesn't print anything for SCTP sockets
o kern/150557  net[igb] igb0: Watchdog timeout -- resetting
o kern/150251  net[patch] [ixgbe] Late cable insertion broken
o kern/150249  net[ixgbe] Media type detection broken
o kern/150247  net[patch] [ixgbe] Version in -current won't build on 7.x
o bin/150224   netppp(8) does not reassign static IP after kill -KILL co
o kern/150148  net[ath] Atheros 5424/2424 - AR2425 stopped working with 
o kern/150052  net[wi] wi(4) driver does not work with wlan(4) driver fo
f kern/149969  net[wlan] [ral] ralink rt2661 fails to maintain connectio
o kern/149937  net[ipfilter] [patch] kernel panic in ipfilter IP fragmen
o kern/149786  net[bwn] bwn on Dell Inspiron 1150: connections stall
o kern/149643  net[rum] device not sending proper beacon frames in ap mo
o kern/149609  net[panic] reboot after adding second default route
o kern/149539  net[ath] atheros ar9287 is not supported by ath_hal
o kern/149516  net[ath] ath(4) hostap with fake MAC/BSSID results in sta
o kern/149373  net[realtek/atheros]: None of my network card working
o kern/149307  net[ath] Doesn't work Atheros 9285
o kern/149306  net[alc] Doesn't work Atheros AR8131 PCIe Gigabit Etherne
o kern/149117  net[inet] [patch] in_pcbbind: redundant test
o kern/149086  net[multicast] Generic multicast join failure in 8.1
o kern/148862  net[panic] page fault while in kernel mode at _mtx_lock_s
o kern/148780  net[panic] mtx_lock() of spin mutex (null) @ /usr/src/sys
o kern/148322  net[ath] Triggering atheros wifi beacon misses in hostap 
o kern/148317  net[ath] FreeBSD 7.x hostap memory leak in net80211 or At
o kern/148078  net[ath] wireless networking stops functioning
o kern/147894  net[ipsec] IPv6-in-IPv4 does not work inside an ESP-only 
o kern/147862  net[wpi] Possible bug in the wpi driver.  Network Manager
o kern/147155  net[ip6] setfb not work with ipv6
o kern/146845  net[libc] close(2) returns error 54 (connection reset by 
o kern/146792  net[flowtable] flowcleaner 100% cpu's core load
o kern/146759  net[cxgb] [patch] cxgb panic calling cxgb_set_lro() witho
o kern/146719  net[pf] [panic] PF or dumynet kernel panic
o kern/146534  net[icmp6] wrong source address in echo reply
o kern/146517  net[ath] [wlan] device timeouts for ath wlan device on re
o kern/146427  net[mwl] Additional virtual access points don't work on m
o kern/146426  net[mwl] 802.11n rates not possible on mwl
o kern/146425  net[mwl] mwl dropping all packets during and after high u
f kern/146394  net[vlan] IP source address for outgoing connections
o bin/146377   net[ppp] [tun] Interface doesn't clear addresses when PPP
o kern/146358  net[vlan] wrong destination MAC address
o kern/146165  net[wlan] [panic] Setting bssid in adhoc mode causes pani
o kern/146082  net[ng_l2tp] a false invaliant check was performed in ng_
o kern/146037  net[panic] mpd + CoA = kernel panic
o bin/145934   net[patch] add count option to netstat(1)
o kern/145826  net[ath] Unable to configure adhoc mode on ath0/wlan0
o kern/145825  net[panic] panic: soabort: so_count
o kern/145777  net[wpi] Intel 3945ABG driver breaks the connection after
o kern/145728  net[lagg] Stops working lagg between two servers.
o amd64/145654 netamd64-curent memory leak in kernel
o kern/144987  net[wpi] [panic] injecting packets with wlaninject using 
o kern/144882  netMacBookPro =>4.1 does not connect to BSD in hostap wit
o kern/144874  net[if_bridge] [patch] if_bridge frees mbuf after pfil ho
o conf/144700  net[rc.d] async dhclient breaks stuff for too many people
o kern/144642  net[rum] [panic] Ena

ndis: fix panic on i386

[Paul B Mahol]

Hi,

Following patch fix panic on i386 for drivers using such functions.

Those two functions take 64-bit variable(s) for their arguments.
On i386 that takes additional 32-bit variable per argument.
This is required so that windrv_wrap() can correctly wrap function that
miniport driver calls with stdcall convention.
Similar explanation is provided in subr_ndis.c for other functions.
On amd64 we do not use these numbers.

diff --git a/sys/compat/ndis/subr_ntoskrnl.c b/sys/compat/ndis/subr_ntoskrnl.c
index f169de5..0335561 100644
--- a/sys/compat/ndis/subr_ntoskrnl.c
+++ b/sys/compat/ndis/subr_ntoskrnl.c
@@ -4212,8 +4212,8 @@ image_patch_table ntoskrnl_functbl[] = {
IMPORT_FFUNC(ExInterlockedAddLargeStatistic, 2),
IMPORT_SFUNC(IoAllocateMdl, 5),
IMPORT_SFUNC(IoFreeMdl, 1),
-   IMPORT_SFUNC(MmAllocateContiguousMemory, 2),
-   IMPORT_SFUNC(MmAllocateContiguousMemorySpecifyCache, 5),
+   IMPORT_SFUNC(MmAllocateContiguousMemory, 2 + 1),
+   IMPORT_SFUNC(MmAllocateContiguousMemorySpecifyCache, 5 + 3),
IMPORT_SFUNC(MmFreeContiguousMemory, 1),
IMPORT_SFUNC(MmFreeContiguousMemorySpecifyCache, 3),
IMPORT_SFUNC_MAP(MmGetPhysicalAddress, pmap_kextract, 1),
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

problem setting up a mesh portal with a bridge to wired lan

[Monthadar Al Jaberi]

Hi,

I am having trouble finding a full documentation on how to set an mesh
portal (MPP) bridged to wired lan.
I gathered things from here and there, and here what I have came up to.

SETUP: I have a PC, and two RSPRO boards with atheros wifi. PC and one
RSPRO connected to a router.

On the mesh node (MP) my ifconfig:
wlan0: flags=8843 metric 0 mtu 1500
ether 00:15:6d:65:fe:b2
inet 192.168.1.42 netmask 0xff00 broadcast 192.168.1.255
media: IEEE 802.11 Wireless Ethernet autoselect mode 11g 
status: running
meshid my_mesh channel 10 (2457 MHz 11g) bssid 00:15:6d:65:fe:b2
country US ecm authmode OPEN privacy OFF txpower 21 scanvalid 60
protmode CTS wme burst meshttl 31 meshpeering meshforward
meshmetric AIRTIME meshpath HWMP hwmprootmode DISABLED hwmpmaxhops 31

On the mesh portal ifconfig:
arge0: flags=8943
metric 0 mtu 1500
options=8
ether 00:15:6d:c3:30:e5
inet 0.0.0.0 netmask 0xff00 broadcast 0.255.255.255
media: Ethernet autoselect (100baseTX )
status: active
bridge0: flags=28943
metric 0 mtu 1500
ether 00:15:6d:67:21:8d
inet 192.168.1.41 netmask 0xff00 broadcast 192.168.1.255
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: wlan0 flags=143
ifmaxaddr 0 port 8 priority 128 path cost 370370
member: arge0 flags=143
ifmaxaddr 0 port 4 priority 128 path cost 20
wlan0: flags=8943
metric 0 mtu 1500
ether 00:15:6d:67:21:8d
inet 0.0.0.0 netmask 0xff00 broadcast 0.255.255.255
media: IEEE 802.11 Wireless Ethernet autoselect mode 11g 
status: running
meshid my_mesh channel 10 (2457 MHz 11g) bssid 00:15:6d:67:21:8d
country US ecm authmode OPEN privacy OFF txpower 20 scanvalid 60
protmode CTS wme burst meshttl 31 meshpeering meshforward
meshmetric AIRTIME meshpath HWMP hwmprootmode PROACTIVE hwmpmaxhops 31

>From the MPP I can ping ping the PC and internet. Also I can ping the
MP on the second RSPRO.
>From the MP I can ping the MPP, but I cant ping the PC or internet.
>From PC I can ping MPP, but not MP.

Arp broadcast goes through, but not ARP reply (got lost?). I checked
from tcpdump that the mac addresses are correct for ARP reply
destination.

I have changed these in sysctl on the MPP:
sysctl -a | grep forwarding
net.inet.ip.forwarding: 1
net.inet.ip.fastforwarding: 1
net.link.bridge.ipfw: 0
net.link.bridge.inherit_mac: 0
net.link.bridge.log_stp: 0
net.link.bridge.pfil_local_phys: 0
net.link.bridge.pfil_member: 0
net.link.bridge.pfil_bridge: 0
net.link.bridge.ipfw_arp: 0
net.link.bridge.pfil_onlyip: 0

I have no firewall enabled. Seems like something is missing to make
this work. It works if I setup the boards as AP and STA.
I also found this old post,
http://lists.freebsd.org/pipermail/freebsd-net/2010-February/024538.html...
but didnt help me.

Thank you in advance!
-- 
//Monthadar Al Jaberi
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

kern/152141: [vlan] encapsulate vlan in ng_ether before output to if

[rozhuk . im]

This is a patched version of original function

code
/*
 * If underlying interface can not do VLAN tag insertion itself
 * then attach a packet tag that holds it.
 */
if ((m->m_flags & M_VLANTAG) &&
(ifp->if_capenable & IFCAP_VLAN_HWTAGGING) == 0) {
m = ether_vlanencap(m, m->m_pkthdr.ether_vtag);
if (m == NULL) {
ifp->if_oerrors++;
return (ENOBUFS);
}
m->m_flags &= ~M_VLANTAG;
}


was added.

Iam does not test this path - haven’t net with vlan support.

Code was taken from if_bridge and adapted.


 
--
Rozhuk Ivan
  



___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: em(4): 4-port Intel Pro/1000 PF card not detected

[Charles Owens]

Great... thanks!   Please see attached.   BTW, the system is running 
8.0-RELEASE-p2 i386 (PAE).



Charles


On 11/13/10 2:24 AM, Jack Vogel wrote:
pciconf -l please, I'll betcha these are the new quad ports that are 
in my next igb driver
update, it would have gone in already but I've been fighting a bug in 
the header split

code.

Show me what the output looks like, and I'll get ya fixed up, dont 
worry :)


Jack


On Fri, Nov 12, 2010 at 2:08 PM, Charles Owens 
mailto:cow...@greatbaysoftware.com>> wrote:


Hello,

We're trying to work with newly purcharsed Intel EXPi9404PF NICs
("Intel PRO/1000 PF Quad Port Server Adapter") but they do not
seem to be detected (no ports showing with 'ifconfig -l').   We're
having no problems with the 2-port version of the same card -- is
there a known issue with the 4-port version?

We've tried three different cards of this model, all with same
result.  Thanks in advance for any help.

Charles

-- 
 Charles Owens

 Great Bay Software, Inc.



___
freebsd-net@freebsd.org  mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to
"freebsd-net-unsubscr...@freebsd.org
"


hos...@pci0:0:0:0:  class=0x06 card=0x34de8086 chip=0x34068086 rev=0x13 
hdr=0x00
pc...@pci0:0:1:0:   class=0x060400 card=0x34de8086 chip=0x34088086 rev=0x13 
hdr=0x01
pc...@pci0:0:3:0:   class=0x060400 card=0x34de8086 chip=0x340a8086 rev=0x13 
hdr=0x01
pc...@pci0:0:7:0:   class=0x060400 card=0x34de8086 chip=0x340e8086 rev=0x13 
hdr=0x01
pc...@pci0:0:9:0:   class=0x060400 card=0x34de8086 chip=0x34108086 rev=0x13 
hdr=0x01
pc...@pci0:0:10:0:  class=0x060400 card=0x34de8086 chip=0x34118086 rev=0x13 
hdr=0x01
no...@pci0:0:16:0:  class=0x08 card=0x00de0086 chip=0x34258086 rev=0x13 
hdr=0x00
no...@pci0:0:16:1:  class=0x08 card=0x00de0086 chip=0x34268086 rev=0x13 
hdr=0x00
no...@pci0:0:17:0:  class=0x08 card=0x00de0086 chip=0x34278086 rev=0x13 
hdr=0x00
no...@pci0:0:17:1:  class=0x08 card=0x00de0086 chip=0x34288086 rev=0x13 
hdr=0x00
ioap...@pci0:0:19:0:class=0x080020 card=0x00de0086 chip=0x342d8086 rev=0x13 
hdr=0x00
no...@pci0:0:20:0:  class=0x08 card=0x00de0086 chip=0x342e8086 rev=0x13 
hdr=0x00
no...@pci0:0:20:1:  class=0x08 card=0x00de0086 chip=0x34228086 rev=0x13 
hdr=0x00
no...@pci0:0:20:2:  class=0x08 card=0x00de0086 chip=0x34238086 rev=0x13 
hdr=0x00
no...@pci0:0:20:3:  class=0x08 card=0x00de0086 chip=0x34388086 rev=0x13 
hdr=0x00
ioap...@pci0:0:21:0:class=0x080020 card=0x00de0086 chip=0x342f8086 rev=0x13 
hdr=0x00
no...@pci0:0:22:0:  class=0x088000 card=0x34de8086 chip=0x34308086 rev=0x13 
hdr=0x00
no...@pci0:0:22:1:  class=0x088000 card=0x34de8086 chip=0x34318086 rev=0x13 
hdr=0x00
non...@pci0:0:22:2: class=0x088000 card=0x34de8086 chip=0x34328086 rev=0x13 
hdr=0x00
non...@pci0:0:22:3: class=0x088000 card=0x34de8086 chip=0x34338086 rev=0x13 
hdr=0x00
non...@pci0:0:22:4: class=0x088000 card=0x34de8086 chip=0x34298086 rev=0x13 
hdr=0x00
non...@pci0:0:22:5: class=0x088000 card=0x34de8086 chip=0x342a8086 rev=0x13 
hdr=0x00
non...@pci0:0:22:6: class=0x088000 card=0x34de8086 chip=0x342b8086 rev=0x13 
hdr=0x00
non...@pci0:0:22:7: class=0x088000 card=0x34de8086 chip=0x342c8086 rev=0x13 
hdr=0x00
uh...@pci0:0:26:0:  class=0x0c0300 card=0x34de8086 chip=0x3a378086 rev=0x00 
hdr=0x00
uh...@pci0:0:26:1:  class=0x0c0300 card=0x34de8086 chip=0x3a388086 rev=0x00 
hdr=0x00
uh...@pci0:0:26:2:  class=0x0c0300 card=0x34de8086 chip=0x3a398086 rev=0x00 
hdr=0x00
eh...@pci0:0:26:7:  class=0x0c0320 card=0x34de8086 chip=0x3a3c8086 rev=0x00 
hdr=0x00
pc...@pci0:0:28:0:  class=0x060400 card=0x34de8086 chip=0x3a408086 rev=0x00 
hdr=0x01
pc...@pci0:0:28:4:  class=0x060400 card=0x34de8086 chip=0x3a488086 rev=0x00 
hdr=0x01
pc...@pci0:0:28:5:  class=0x060400 card=0x34de8086 chip=0x3a4a8086 rev=0x00 
hdr=0x01
uh...@pci0:0:29:0:  class=0x0c0300 card=0x34de8086 chip=0x3a348086 rev=0x00 
hdr=0x00
uh...@pci0:0:29:1:  class=0x0c0300 card=0x34de8086 chip=0x3a358086 rev=0x00 
hdr=0x00
uh...@pci0:0:29:2:  class=0x0c0300 card=0x34de8086 chip=0x3a368086 rev=0x00 
hdr=0x00
eh...@pci0:0:29:7:  class=0x0c0320 card=0x34de8086 chip=0x3a3a8086 rev=0x00 
hdr=0x00
pc...@pci0:0:30:0:  class=0x060401 card=0x34de8086 chip=0x244e8086 rev=0x90 
hdr=0x01
is...@pci0:0:31:0:  class=0x060100 card=0x34de8086 chip=0x3a168086 rev=0x00 
hdr=0x00
atap...@pci0:0:31:2:class=0x01018f card=0x34de8086 chip=0x3a208086 rev=0x00 
hdr=0x00
non...@pci0:0:31:3: class=0x0c0500 card=0x34de8086 chip=0x3a308086 rev=0x00 
hdr=0x00
atap...@pci0:0:31:5:class=0x010185 card=0x34de8086 chip=0x3a268086 rev=0x00 
hdr=0x00
i...@pci0:1:0:0:class=0x02 car

Re: em(4): 4-port Intel Pro/1000 PF card not detected

[Jack Vogel]

UH, did you do that with the adapter in the system?? I do not see the ID I
expected
to see. Some reason you're running 32 bit??

Can you run the pciconf with the adapter in and out, compare and tell me
what its
ID is?  All the unidentified devices I see are in the 0x3XXX range and those
are not
network devices.

Maybe its a bad slot?

Jack


On Mon, Nov 15, 2010 at 11:59 AM, Charles Owens  wrote:

>  Great... thanks!   Please see attached.   BTW, the system is running
> 8.0-RELEASE-p2 i386 (PAE).
>
>
> Charles
>
>
>
> On 11/13/10 2:24 AM, Jack Vogel wrote:
>
> pciconf -l please, I'll betcha these are the new quad ports that are in my
> next igb driver
> update, it would have gone in already but I've been fighting a bug in the
> header split
> code.
>
> Show me what the output looks like, and I'll get ya fixed up, dont worry :)
>
> Jack
>
>
> On Fri, Nov 12, 2010 at 2:08 PM, Charles Owens <
> cow...@greatbaysoftware.com> wrote:
>
>> Hello,
>>
>> We're trying to work with newly purcharsed Intel EXPi9404PF NICs ("Intel
>> PRO/1000 PF Quad Port Server Adapter") but they do not seem to be detected
>> (no ports showing with 'ifconfig -l').   We're having no problems with the
>> 2-port version of the same card -- is there a known issue with the 4-port
>> version?
>>
>> We've tried three different cards of this model, all with same result.
>>  Thanks in advance for any help.
>>
>> Charles
>>
>> --
>>  Charles Owens
>>  Great Bay Software, Inc.
>>
>>
>>
>> ___
>> freebsd-net@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-net
>> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>>
>
>
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Qlogic - NexLan 10GE

[Sean Bruno]

Looks like the higher end HP Proliant servers are coming with 10GE
adapters.

When I was at MeetBSD I ran into an engineer that was working on this
driver and I failed to document his contact information.

If anyone has that contact, I'd really appreciate it.

Sean



___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: em(4): 4-port Intel Pro/1000 PF card not detected

[Charles Owens]

Jack, I'm afraid that with the card _not_ installed we get identical 
pciconf output.  We're running 32 bit simply because that's where we got 
rolling with our product, and have not yet made the call to invest in 
the effort required to make the jump to 64.  Do you think that our being 
at 32 bit could be a factor here?


So far the same card model has been tested on several of these server 
appliances, so I doubt it's a bad-slot situation.


In case it's helpful, I've attached  a boot log.  Anything else that I 
can provide that might help?


Thank you,
Charles


On 11/15/10 3:23 PM, Jack Vogel wrote:

UH, did you do that with the adapter in the system?? I do not see the ID I
expected
to see. Some reason you're running 32 bit??

Can you run the pciconf with the adapter in and out, compare and tell me
what its
ID is?  All the unidentified devices I see are in the 0x3XXX range and those
are not
network devices.

Maybe its a bad slot?

Jack


On Mon, Nov 15, 2010 at 11:59 AM, Charles Owens
wrote:
  Great... thanks!   Please see attached.   BTW, the system is running
8.0-RELEASE-p2 i386 (PAE).


Charles



On 11/13/10 2:24 AM, Jack Vogel wrote:

pciconf -l please, I'll betcha these are the new quad ports that are in my
next igb driver
update, it would have gone in already but I've been fighting a bug in the
header split
code.

Show me what the output looks like, and I'll get ya fixed up, dont worry :)

Jack


On Fri, Nov 12, 2010 at 2:08 PM, Charles Owens<
cow...@greatbaysoftware.com>  wrote:


Hello,

We're trying to work with newly purcharsed Intel EXPi9404PF NICs ("Intel
PRO/1000 PF Quad Port Server Adapter") but they do not seem to be detected
(no ports showing with 'ifconfig -l').   We're having no problems with the
2-port version of the same card -- is there a known issue with the 4-port
version?

We've tried three different cards of this model, all with same result.
  Thanks in advance for any help.

Charles

--
  Charles Owens
  Great Bay Software, Inc.



___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"




___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Copyright (c) 1992-2009 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 8.0-RELEASE-p2 #8: Mon Apr 19 16:31:20 UTC 2010
se...@newcastle.greatbaysoftware.com:/usr/obj/usr/src/sys/BEACON
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(R) CPU   E5520  @ 2.27GHz (2261.27-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x106a5  Stepping = 5
  
Features=0xbfebfbff
  
Features2=0x9ce3bd
  AMD Features=0x2810
  AMD Features2=0x1
  TSC: P-state invariant
real memory  = 6442450944 (6144 MB)
avail memory = 6202404864 (5915 MB)
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 16 CPUs
FreeBSD/SMP: 2 package(s) x 4 core(s) x 2 SMT threads
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
 cpu2 (AP): APIC ID:  2
 cpu3 (AP): APIC ID:  3
 cpu4 (AP): APIC ID:  4
 cpu5 (AP): APIC ID:  5
 cpu6 (AP): APIC ID:  6
 cpu7 (AP): APIC ID:  7
 cpu8 (AP): APIC ID: 16
 cpu9 (AP): APIC ID: 17
 cpu10 (AP): APIC ID: 18
 cpu11 (AP): APIC ID: 19
 cpu12 (AP): APIC ID: 20
 cpu13 (AP): APIC ID: 21
 cpu14 (AP): APIC ID: 22
 cpu15 (AP): APIC ID: 23
ioapic0  irqs 0-23 on motherboard
ioapic1  irqs 24-47 on motherboard
lapic0: Forcing LINT1 to edge trigger
ispfw: registered firmware 
ispfw: registered firmware 
ispfw: registered firmware 
ispfw: registered firmware 
ispfw: registered firmware 
ispfw: registered firmware 
ispfw: registered firmware 
ispfw: registered firmware 
ispfw: registered firmware 
ispfw: registered firmware 
ispfw: registered firmware 
ispfw: registered firmware 
ispfw: registered firmware 
ispfw: registered firmware 
kbd0 at kbdmux0
acpi0:  on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
acpi_hpet0:  iomem 0xfed0-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 900
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
pcib1:  irq 28 at device 1.0 on pci0
pci1:  on pcib1
igb0:  port 0x2020-0x203f 
mem 0xb1a2-0xb1a3,0xb1a44000-0xb1a47fff irq 40 at device 0.0 on pci1
igb0: Using MSIX interrupts with 3 vectors
igb0: [ITHREAD]
igb0: [ITHREAD]
igb0: [ITHREAD]
igb0: Ethernet address: 00:15:17:b4:cf:e4
igb1:  port 0x2000-0x201f 
mem 0xb1a0-0xb1a1,0xb1a4-0xb1a43fff irq 28 at device 0.1 on pci1
igb1: Using MSIX interrupts with 3 vectors
igb1: [I

Proposed new information from netstat

[George Neville-Neil]

Howdy,

Please review this patch which adds the -T flag to netstat so that you can get 
TCP information, per socket,
including retransmits, out-of-order receives, and zero window advertisements.

Best,
George



head-tcpinfo.diff
Description: Binary data
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: em(4): 4-port Intel Pro/1000 PF card not detected

[Jack Vogel]

Well, if the system doesnt show the hardware in a PCI scan there isn't much
my driver can do :)

The last line in your log says 'eth0', what's that about?

You could try booting 8.1 64 bit, you can also send me all the details about
the board, just to
make sure I can get the exact one and then I'll try it here. This is quad
port fiber, right? I was
thinking this was PCI ID 0x1527, 82580 adapter.  The support is in HEAD now.

Regards,

Jack


On Mon, Nov 15, 2010 at 1:45 PM, Charles Owens
wrote:

> Jack, I'm afraid that with the card _not_ installed we get identical
> pciconf output.  We're running 32 bit simply because that's where we got
> rolling with our product, and have not yet made the call to invest in the
> effort required to make the jump to 64.  Do you think that our being at 32
> bit could be a factor here?
>
> So far the same card model has been tested on several of these server
> appliances, so I doubt it's a bad-slot situation.
>
> In case it's helpful, I've attached  a boot log.  Anything else that I can
> provide that might help?
>
> Thank you,
> Charles
>
>
>
> On 11/15/10 3:23 PM, Jack Vogel wrote:
>
>> UH, did you do that with the adapter in the system?? I do not see the ID I
>> expected
>> to see. Some reason you're running 32 bit??
>>
>> Can you run the pciconf with the adapter in and out, compare and tell me
>> what its
>> ID is?  All the unidentified devices I see are in the 0x3XXX range and
>> those
>> are not
>> network devices.
>>
>> Maybe its a bad slot?
>>
>> Jack
>>
>>
>> On Mon, Nov 15, 2010 at 11:59 AM, Charles Owens<
>> cow...@greatbaysoftware.com
>>
>>> wrote:
>>>  Great... thanks!   Please see attached.   BTW, the system is running
>>> 8.0-RELEASE-p2 i386 (PAE).
>>>
>>>
>>> Charles
>>>
>>>
>>>
>>> On 11/13/10 2:24 AM, Jack Vogel wrote:
>>>
>>> pciconf -l please, I'll betcha these are the new quad ports that are in
>>> my
>>> next igb driver
>>> update, it would have gone in already but I've been fighting a bug in the
>>> header split
>>> code.
>>>
>>> Show me what the output looks like, and I'll get ya fixed up, dont worry
>>> :)
>>>
>>> Jack
>>>
>>>
>>> On Fri, Nov 12, 2010 at 2:08 PM, Charles Owens<
>>> cow...@greatbaysoftware.com>  wrote:
>>>
>>>  Hello,

 We're trying to work with newly purcharsed Intel EXPi9404PF NICs ("Intel
 PRO/1000 PF Quad Port Server Adapter") but they do not seem to be
 detected
 (no ports showing with 'ifconfig -l').   We're having no problems with
 the
 2-port version of the same card -- is there a known issue with the
 4-port
 version?

 We've tried three different cards of this model, all with same result.
  Thanks in advance for any help.

 Charles

 --
  Charles Owens
  Great Bay Software, Inc.



 ___
 freebsd-net@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-net
 To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


>>>  ___
>> freebsd-net@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-net
>> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>>
>>
>>
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: em(4): 4-port Intel Pro/1000 PF card not detected

[Charles Owens]

The eth0 line in log:  we rename our NICs to be ethX (via "iconfig em0 
name eth0").  That line is just one of the copper NICs coming up.


Info on the card -- model number (EXPi9404PFBLK), chipset (dual 82571 GB 
chips).  Here's the Intel page:


http://www.intel.com/Products/Server/Adapters/PRO1000PF-QuadPort/PRO1000PF-QuadPort-overview.htm


Is this what you were expecting?We can also work on booting into 8.1 
64bit.


Thanks much,

Charles


On 11/15/10 4:58 PM, Jack Vogel wrote:
Well, if the system doesnt show the hardware in a PCI scan there isn't 
much my driver can do :)


The last line in your log says 'eth0', what's that about?

You could try booting 8.1 64 bit, you can also send me all the details 
about the board, just to
make sure I can get the exact one and then I'll try it here. This is 
quad port fiber, right? I was
thinking this was PCI ID 0x1527, 82580 adapter.  The support is in 
HEAD now.


Regards,

Jack


On Mon, Nov 15, 2010 at 1:45 PM, Charles Owens 
mailto:cow...@greatbaysoftware.com>> wrote:


Jack, I'm afraid that with the card _not_ installed we get
identical pciconf output.  We're running 32 bit simply because
that's where we got rolling with our product, and have not yet
made the call to invest in the effort required to make the jump to
64.  Do you think that our being at 32 bit could be a factor here?

So far the same card model has been tested on several of these
server appliances, so I doubt it's a bad-slot situation.

In case it's helpful, I've attached  a boot log.  Anything else
that I can provide that might help?

Thank you,
Charles



On 11/15/10 3:23 PM, Jack Vogel wrote:

UH, did you do that with the adapter in the system?? I do not
see the ID I
expected
to see. Some reason you're running 32 bit??

Can you run the pciconf with the adapter in and out, compare
and tell me
what its
ID is?  All the unidentified devices I see are in the 0x3XXX
range and those
are not
network devices.

Maybe its a bad slot?

Jack


On Mon, Nov 15, 2010 at 11:59 AM, Charles
Owensmailto:cow...@greatbaysoftware.com>

wrote:
 Great... thanks!   Please see attached.   BTW, the system
is running
8.0-RELEASE-p2 i386 (PAE).


Charles



On 11/13/10 2:24 AM, Jack Vogel wrote:

pciconf -l please, I'll betcha these are the new quad
ports that are in my
next igb driver
update, it would have gone in already but I've been
fighting a bug in the
header split
code.

Show me what the output looks like, and I'll get ya fixed
up, dont worry :)

Jack


On Fri, Nov 12, 2010 at 2:08 PM, Charles Owens<
cow...@greatbaysoftware.com
>  wrote:

Hello,

We're trying to work with newly purcharsed Intel
EXPi9404PF NICs ("Intel
PRO/1000 PF Quad Port Server Adapter") but they do not
seem to be detected
(no ports showing with 'ifconfig -l').   We're having
no problems with the
2-port version of the same card -- is there a known
issue with the 4-port
version?

We've tried three different cards of this model, all
with same result.
 Thanks in advance for any help.

Charles

--
 Charles Owens
 Great Bay Software, Inc.



___
freebsd-net@freebsd.org
 mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to
"freebsd-net-unsubscr...@freebsd.org
"


___
freebsd-net@freebsd.org 
mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to
"freebsd-net-unsubscr...@freebsd.org
"




___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: em(4): 4-port Intel Pro/1000 PF card not detected

[Charles Owens]

Well, I believe we have an answer:

http://www.intel.com/support/network/adapter/pro100/sb/CS-030873.htm

The motherboard definitely is PCIe 2.0 .   The page suggests these cards 
for use with a PCIe2.0 system:


# Intel® PRO/1000 PT Quad Port LP Server Adapter (P/N EXPI9404PTL)
# Intel® Gigabit ET Quad Port Server Adapter (P/N E1G44ET)
# Intel® Gigabit ET2 Quad Port Server Adapter (P/N E1G44ET2)


Notably there's not a PF option shown, so we're going to have to think 
about that.   But in any case, do you think these models will function 
with 8.0?  8.0 plus a patch?   or is 8.1 the only option?


Thanks,
Charles


On 11/15/10 4:58 PM, Jack Vogel wrote:
Well, if the system doesnt show the hardware in a PCI scan there isn't 
much my driver can do :)


The last line in your log says 'eth0', what's that about?

You could try booting 8.1 64 bit, you can also send me all the details 
about the board, just to
make sure I can get the exact one and then I'll try it here. This is 
quad port fiber, right? I was
thinking this was PCI ID 0x1527, 82580 adapter.  The support is in 
HEAD now.


Regards,

Jack


On Mon, Nov 15, 2010 at 1:45 PM, Charles Owens 
mailto:cow...@greatbaysoftware.com>> wrote:


Jack, I'm afraid that with the card _not_ installed we get
identical pciconf output.  We're running 32 bit simply because
that's where we got rolling with our product, and have not yet
made the call to invest in the effort required to make the jump to
64.  Do you think that our being at 32 bit could be a factor here?

So far the same card model has been tested on several of these
server appliances, so I doubt it's a bad-slot situation.

In case it's helpful, I've attached  a boot log.  Anything else
that I can provide that might help?

Thank you,
Charles



On 11/15/10 3:23 PM, Jack Vogel wrote:

UH, did you do that with the adapter in the system?? I do not
see the ID I
expected
to see. Some reason you're running 32 bit??

Can you run the pciconf with the adapter in and out, compare
and tell me
what its
ID is?  All the unidentified devices I see are in the 0x3XXX
range and those
are not
network devices.

Maybe its a bad slot?

Jack


On Mon, Nov 15, 2010 at 11:59 AM, Charles
Owensmailto:cow...@greatbaysoftware.com>

wrote:
 Great... thanks!   Please see attached.   BTW, the system
is running
8.0-RELEASE-p2 i386 (PAE).


Charles



On 11/13/10 2:24 AM, Jack Vogel wrote:

pciconf -l please, I'll betcha these are the new quad
ports that are in my
next igb driver
update, it would have gone in already but I've been
fighting a bug in the
header split
code.

Show me what the output looks like, and I'll get ya fixed
up, dont worry :)

Jack


On Fri, Nov 12, 2010 at 2:08 PM, Charles Owens<
cow...@greatbaysoftware.com
>  wrote:

Hello,

We're trying to work with newly purcharsed Intel
EXPi9404PF NICs ("Intel
PRO/1000 PF Quad Port Server Adapter") but they do not
seem to be detected
(no ports showing with 'ifconfig -l').   We're having
no problems with the
2-port version of the same card -- is there a known
issue with the 4-port
version?

We've tried three different cards of this model, all
with same result.
 Thanks in advance for any help.

Charles

--
 Charles Owens
 Great Bay Software, Inc.



___
freebsd-net@freebsd.org
 mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to
"freebsd-net-unsubscr...@freebsd.org
"


___
freebsd-net@freebsd.org 
mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to
"freebsd-net-unsubscr...@freebsd.org
"




___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

if_msk not working after suspend/resume if only one adapter is present

[Bruce Cran]

I've been trying to get suspend/resume working on my Dell laptop.  I have two 
if_msk adapters: one's the built-in 100Mb port and the other's a Sonnet Gb 
ExpressCard NIC. I've noticed that if I boot with the Gb card installed both 
ports work fine when the laptop has been resumed but if I don't have the Gb 
card installed then the built-in port stops working.   Is there any way to 
debug what might be going wrong?

-- 
Bruce Cran
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: em(4): 4-port Intel Pro/1000 PF card not detected

[Jack Vogel]

The way you talked about this at first made me think this was something new,
but its actually
fairly old, its just a quad port 82571, id is 0x10A5, support has been in
the drivers for ages :)

The issue is the hardware not the OS or driver, even if the motherboard is
PCIE 2.0, does it
not have slots that are 1 ?

For server adapters you might consider going 82576 or 82580.

Jack


On Mon, Nov 15, 2010 at 2:38 PM, Charles Owens
wrote:

>  Well, I believe we have an answer:
>
> http://www.intel.com/support/network/adapter/pro100/sb/CS-030873.htm
>
> The motherboard definitely is PCIe 2.0 .   The page suggests these cards
> for use with a PCIe2.0 system:
>
> Intel® PRO/1000 PT Quad Port LP Server Adapter (P/N EXPI9404PTL)
> Intel® Gigabit ET Quad Port Server Adapter (P/N E1G44ET)
> Intel® Gigabit ET2 Quad Port Server Adapter (P/N E1G44ET2)
>
> Notably there's not a PF option shown, so we're going to have to think
> about that.   But in any case, do you think these models will function with
> 8.0?  8.0 plus a patch?   or is 8.1 the only option?
>
> Thanks,
> Charles
>
>
> On 11/15/10 4:58 PM, Jack Vogel wrote:
>
> Well, if the system doesnt show the hardware in a PCI scan there isn't much
> my driver can do :)
>
> The last line in your log says 'eth0', what's that about?
>
> You could try booting 8.1 64 bit, you can also send me all the details
> about the board, just to
> make sure I can get the exact one and then I'll try it here. This is quad
> port fiber, right? I was
> thinking this was PCI ID 0x1527, 82580 adapter.  The support is in HEAD
> now.
>
> Regards,
>
> Jack
>
>
> On Mon, Nov 15, 2010 at 1:45 PM, Charles Owens <
> cow...@greatbaysoftware.com> wrote:
>
>> Jack, I'm afraid that with the card _not_ installed we get identical
>> pciconf output.  We're running 32 bit simply because that's where we got
>> rolling with our product, and have not yet made the call to invest in the
>> effort required to make the jump to 64.  Do you think that our being at 32
>> bit could be a factor here?
>>
>> So far the same card model has been tested on several of these server
>> appliances, so I doubt it's a bad-slot situation.
>>
>> In case it's helpful, I've attached  a boot log.  Anything else that I can
>> provide that might help?
>>
>> Thank you,
>>  Charles
>>
>>
>>
>> On 11/15/10 3:23 PM, Jack Vogel wrote:
>>
>>> UH, did you do that with the adapter in the system?? I do not see the ID
>>> I
>>> expected
>>> to see. Some reason you're running 32 bit??
>>>
>>> Can you run the pciconf with the adapter in and out, compare and tell me
>>> what its
>>> ID is?  All the unidentified devices I see are in the 0x3XXX range and
>>> those
>>> are not
>>> network devices.
>>>
>>> Maybe its a bad slot?
>>>
>>> Jack
>>>
>>>
>>> On Mon, Nov 15, 2010 at 11:59 AM, Charles Owens<
>>> cow...@greatbaysoftware.com
>>>
 wrote:
  Great... thanks!   Please see attached.   BTW, the system is running
 8.0-RELEASE-p2 i386 (PAE).


 Charles



 On 11/13/10 2:24 AM, Jack Vogel wrote:

 pciconf -l please, I'll betcha these are the new quad ports that are in
 my
 next igb driver
 update, it would have gone in already but I've been fighting a bug in
 the
 header split
 code.

 Show me what the output looks like, and I'll get ya fixed up, dont worry
 :)

 Jack


 On Fri, Nov 12, 2010 at 2:08 PM, Charles Owens<
 cow...@greatbaysoftware.com>  wrote:

  Hello,
>
> We're trying to work with newly purcharsed Intel EXPi9404PF NICs
> ("Intel
> PRO/1000 PF Quad Port Server Adapter") but they do not seem to be
> detected
> (no ports showing with 'ifconfig -l').   We're having no problems with
> the
> 2-port version of the same card -- is there a known issue with the
> 4-port
> version?
>
> We've tried three different cards of this model, all with same result.
>  Thanks in advance for any help.
>
> Charles
>
> --
>  Charles Owens
>  Great Bay Software, Inc.
>
>
>
> ___
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>
>
  ___
>>> freebsd-net@freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-net
>>> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>>>
>>>
>>>
>
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: em(4): 4-port Intel Pro/1000 PF card not detected

[Charles Owens]

The appliance is in a 1U form-factor with just a single riser-based slot 
(PCIe 2.0).


Thanks for your help with this,

Charles


On 11/15/10 6:14 PM, Jack Vogel wrote:
The way you talked about this at first made me think this was 
something new, but its actually
fairly old, its just a quad port 82571, id is 0x10A5, support has been 
in the drivers for ages :)


The issue is the hardware not the OS or driver, even if the 
motherboard is PCIE 2.0, does it

not have slots that are 1 ?

For server adapters you might consider going 82576 or 82580.

Jack


On Mon, Nov 15, 2010 at 2:38 PM, Charles Owens 
mailto:cow...@greatbaysoftware.com>> wrote:


Well, I believe we have an answer:

http://www.intel.com/support/network/adapter/pro100/sb/CS-030873.htm

The motherboard definitely is PCIe 2.0 .   The page suggests these
cards for use with a PCIe2.0 system:

  # Intel® PRO/1000 PT Quad Port LP Server Adapter (P/N EXPI9404PTL)
  # Intel® Gigabit ET Quad Port Server Adapter (P/N E1G44ET)
  # Intel® Gigabit ET2 Quad Port Server Adapter (P/N E1G44ET2)


Notably there's not a PF option shown, so we're going to have to
think about that.   But in any case, do you think these models
will function with 8.0?  8.0 plus a patch?   or is 8.1 the
only option?

Thanks,
Charles


On 11/15/10 4:58 PM, Jack Vogel wrote:

Well, if the system doesnt show the hardware in a PCI scan there
isn't much my driver can do :)

The last line in your log says 'eth0', what's that about?

You could try booting 8.1 64 bit, you can also send me all the
details about the board, just to
make sure I can get the exact one and then I'll try it here. This
is quad port fiber, right? I was
thinking this was PCI ID 0x1527, 82580 adapter.  The support is
in HEAD now.

Regards,

Jack


On Mon, Nov 15, 2010 at 1:45 PM, Charles Owens
mailto:cow...@greatbaysoftware.com>> wrote:

Jack, I'm afraid that with the card _not_ installed we get
identical pciconf output.  We're running 32 bit simply
because that's where we got rolling with our product, and
have not yet made the call to invest in the effort required
to make the jump to 64.  Do you think that our being at 32
bit could be a factor here?

So far the same card model has been tested on several of
these server appliances, so I doubt it's a bad-slot situation.

In case it's helpful, I've attached  a boot log.  Anything
else that I can provide that might help?

Thank you,
Charles



On 11/15/10 3:23 PM, Jack Vogel wrote:

UH, did you do that with the adapter in the system?? I do
not see the ID I
expected
to see. Some reason you're running 32 bit??

Can you run the pciconf with the adapter in and out,
compare and tell me
what its
ID is?  All the unidentified devices I see are in the
0x3XXX range and those
are not
network devices.

Maybe its a bad slot?

Jack


On Mon, Nov 15, 2010 at 11:59 AM, Charles
Owensmailto:cow...@greatbaysoftware.com>

wrote:
 Great... thanks!   Please see attached.   BTW, the
system is running
8.0-RELEASE-p2 i386 (PAE).


Charles



On 11/13/10 2:24 AM, Jack Vogel wrote:

pciconf -l please, I'll betcha these are the new quad
ports that are in my
next igb driver
update, it would have gone in already but I've been
fighting a bug in the
header split
code.

Show me what the output looks like, and I'll get ya
fixed up, dont worry :)

Jack


On Fri, Nov 12, 2010 at 2:08 PM, Charles Owens<
cow...@greatbaysoftware.com
>  wrote:

Hello,

We're trying to work with newly purcharsed Intel
EXPi9404PF NICs ("Intel
PRO/1000 PF Quad Port Server Adapter") but they
do not seem to be detected
(no ports showing with 'ifconfig -l').   We're
having no problems with the
2-port version of the same card -- is there a
known issue with the 4-port
version?

We've tried three different cards of this model,
all with same result.
 Thanks in advance for any help.

Charles

--
 Charles Owens
 Great Bay Software, Inc.



__

Re: if_msk not working after suspend/resume if only one adapter is present

[Pyun YongHyeon]

On Mon, Nov 15, 2010 at 11:11:42PM +, Bruce Cran wrote:
> I've been trying to get suspend/resume working on my Dell laptop.  I have two 
> if_msk adapters: one's the built-in 100Mb port and the other's a Sonnet Gb 
> ExpressCard NIC. I've noticed that if I boot with the Gb card installed both 
> ports work fine when the laptop has been resumed but if I don't have the Gb 
> card installed then the built-in port stops working.   Is there any way to 
> debug what might be going wrong?
> 

Could you show me dmesg output?
I've attached a blind patch which could be related with
suspend/resume. I guess powering down code was not synchronized
well for newer controllers.
Index: sys/dev/msk/if_msk.c
===
--- sys/dev/msk/if_msk.c	(revision 215345)
+++ sys/dev/msk/if_msk.c	(working copy)
@@ -2941,8 +2941,6 @@
 	CSR_WRITE_4(sc, B0_HWE_IMSK, 0);
 	CSR_READ_4(sc, B0_HWE_IMSK);
 
-	msk_phy_power(sc, MSK_PHY_POWERDOWN);
-
 	/* Put hardware reset. */
 	CSR_WRITE_2(sc, B0_CTST, CS_RST_SET);
 	sc->msk_pflags |= MSK_FLAG_SUSPEND;
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: Problem with re0

[Pyun YongHyeon]

On Sat, Nov 13, 2010 at 09:09:18AM +0200, Zeus V Panchenko wrote:
> Pyun YongHyeon (pyu...@gmail.com) [10.11.13 01:01] wrote:
> > 
> > Please be more specific for the issue. Your description is hard to
> > narrow down possible cause.
> > 
> > > i was sure it is the problem of the onboard rt nics ...
> > > 
> > 
> > pciconf output of all re(4) controllers are useless because the
> > vendor uses the same device id. Please show me the output of dmesg
> > which will contain necessary information to identify your
> > controller revision.
> > 
> 
> oh, sorry :(
> 
> here is what you say:
> 
> the integrated onboard nic:
> re0:  port 
> 0xe800-0xe8ff mem 0xfafff000-0xfaff,0xfaff8000-0xfaffbfff irq 17 at 
> device 0.0 on pci2
> re0: Using 1 MSI messages
> re0: Chip rev. 0x2800
> re0: MAC rev. 0x
> miibus0:  on re0
> rgephy0:  PHY 1 on miibus0
> rgephy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
> 1000baseT-FDX, auto
> re0: Ethernet address: 48:5b:39:d2:1d:89
> re0: [FILTER]
> 
> 
> external PCI nic:
> re1:  port 0xd800-0xd8ff mem 
> 0xfbeffc00-0xfbeffcff irq 17 at device 0.0 on pci1
> re1: Chip rev. 0x1000
> re1: MAC rev. 0x
> miibus1:  on re1
> rgephy1:  PHY 1 on miibus1
> rgephy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
> 1000baseT-FDX, auto
> re1: Ethernet address: 00:21:91:f4:5f:e4
> re1: [FILTER]
> 
> 
> all that data i was posting here before (several months ago) and
> nothing changed since that time 
> 
> due to production state of the boxes i was forced finally to switch to
> external nics and to configure it with vlans and even to unplug the
> cable of the onboard nic
> 
> since nic with plugged cable but without assigned ip address did begin
> flap (may be it's specific of the swith it plugged in, it is TP-Link
> TL-SG5426 but no other nic behaves this way)
> 
> i have 7 boxes of this configuration and all 6 are running
> now on external nics
> 
> 
> if i can provide any debug/info/e.t.c. please let me know, i'd be
> happy it'd work at last :)
>  

Ok, please try latest re(4) in HEAD. If that does not change the
behavior, give attached patch spin and let me know whether it makes
any difference. Note, the attached may trigger watchdog timeouts
under certain conditions but if you do not remove UTP cable that
wouldn't happen. I have to verify whether it can really trigger
watchdog timeouts and it takes more time on my side.
Index: sys/dev/re/if_re.c
===
--- sys/dev/re/if_re.c	(revision 215345)
+++ sys/dev/re/if_re.c	(working copy)
@@ -2151,9 +2151,10 @@
 	RL_LOCK_ASSERT(sc);
 
 	mii = device_get_softc(sc->rl_miibus);
-	mii_tick(mii);
-	if ((sc->rl_flags & RL_FLAG_LINK) == 0)
+	if ((sc->rl_flags & RL_FLAG_LINK) == 0) {
+		mii_tick(mii);
 		re_miibus_statchg(sc->rl_dev);
+	}
 	/*
 	 * Reclaim transmitted frames here. Technically it is not
 	 * necessary to do here but it ensures periodic reclamation
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"