Re: [Fwd: Re: bge Ierr rate increase from 5.3R -> 6.1R]

2007-01-08 Thread John Polstra
On 30-Dec-2006 Bruce Evans wrote: > More debugging showed that almost any of the reads of the phy in mii > cause an input error, The errors appear to be caused by the code in bge_miibus_{read,write}reg that clears and then restores the BGE_MIMODE_AUTOPOLL bit of the BGE_MI_MODE register. If you r

Slow FreeBSD -> Windows performance with inflight enabled

2007-01-08 Thread Steven Hartland
I've just been looking at an issue reported by some of our users that downloads from our one of our sites run on FreeBSD 6.1 and Apache 1.3 where strangely slow. After doing some digging around I found that two remote machines on the same network had wildly different results. The difference being

Re: Panic in 6.2-RC2

2007-01-08 Thread gnn
At Sat, 6 Jan 2007 13:54:22 -0500, David Boyd wrote: > > The following panic occurs every one to three hours with 6.2-RC2. > Can you give more info on what, exactly, is going on when this happens? Also I'm redirecting this to net@ Best Geoge > This is the same problem as kern/88472 which is

Current problem reports assigned to you

2007-01-08 Thread FreeBSD bugmaster
Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description a kern/38554 netchanging interface ipaddress doesn't seem to work s kern/39937 netipstealth

Re: Different behavior of ping'ing INADDR_BROADCAST?

2007-01-08 Thread Eygene Ryabinkin
Tadaaki, good day! > This seems to be the same problem as kern/99558: "FreeBSD 6.1 can't send > packets to INADDR_BROADCAST". > > Maybe andre has some thoughts on how to fix this issue? (I'm CC'ing him.) Exactly, thank you very much for the pointer! > It seems to me from the PR above, that befo

Re: Different behavior of ping'ing INADDR_BROADCAST?

2007-01-08 Thread Tadaaki Nagao
Hi, > > When FBSD is pinging 0x it does not use the Ethernet broadcasts, > > when the link-level destination MAC is set to 0x, using some > > 'known MAC' instead. For the network broadcast address -- it does use > > link-level broadcasts. This seems to be the same problem as k