Re: kern/146759: commit references a PR

2010-05-20 Thread dfilter service
The following reply was made to PR kern/146759; it has been noted by GNATS. From: dfil...@freebsd.org (dfilter service) To: bug-follo...@freebsd.org Cc: Subject: Re: kern/146759: commit references a PR Date: Thu, 20 May 2010 18:22:57 + (UTC) Author: np Date: Thu May 20 18:22:45 2010 New

Re: kern/146759: [cxgb] [patch] cxgb panic calling cxgb_set_lro() without port lock held

2010-05-20 Thread linimon
Old Synopsis: cxgb panic calling without cxgb_set_lro() without port lock held New Synopsis: [cxgb] [patch] cxgb panic calling cxgb_set_lro() without port lock held Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 20 15:45:51

Re: increasing em(4) buffer sizes

2010-05-20 Thread rihad
On 05/20/2010 05:19 PM, Eugene Grosbein wrote: On 20.05.2010 13:06, rihad wrote: Some more useful tunnables for loader.conf: dev.em.0.rx_int_delay=200 dev.em.0.tx_int_delay=200 dev.em.0.rx_abs_int_delay=200 dev.em.0.tx_abs_int_delay=200 dev.em.0.rx_processing_limit=-1 So this interrupt delay

Strange BGP/OSPF problem

2010-05-20 Thread Thodoris S.
an one of my border router ospf started flapping without reason the link was ok i have tested it the log file shows the following at the beggining started with this messages 2010/05/01 17:36:25 ZEBRA: kernel_rtm_ipv4: 222.213.128.0/17: rtm_write() unexpectedly returned -4 for command RTM_DELETE 2

Re: increasing em(4) buffer sizes

2010-05-20 Thread Eugene Grosbein
On 20.05.2010 13:06, rihad wrote: Some more useful tunnables for loader.conf: dev.em.0.rx_int_delay=200 dev.em.0.tx_int_delay=200 dev.em.0.rx_abs_int_delay=200 dev.em.0.tx_abs_int_delay=200 dev.em.0.rx_processing_limit=-1 >>> So this interrupt delay is the m

Re:Re: Re: convert Windows NDIS drivers for use with FreeBSD

2010-05-20 Thread jiani1012
Thank you in advance! I got it with success! Today, I do the same thing with Intel 4965agn driver corresponding to iwn on FREEBSD8.0 release. I create wlan0 from iwn0, as well kldload the iwn,iwnfw before a ping successful conmunication. But when I do wlan0 scan, take errors: iwn0:error,INTR=2