Hi, Freebsd-net.
serv1# ifocnfig nfe0
nfe0: flags=8943 metric 0 mtu
1500
options=10b
ether 00:13:d4:ce:82:16
inet 10.11.8.17 netmask 0xfc00 broadcast 10.11.11.255
inet 10.11.8.15 netmask 0xfc00 broadcast 10.11.11.255
media: Ethernet autoselect (1000
Здравствуйте, Chuck.
Вы писали 28 октября 2010 г., 23:41:58:
CS> On Oct 28, 2010, at 1:21 PM, Коньков Евгений wrote:
>> [ ... ]
CS> What is "sysctl kern.clockrate", and have you increased kern.hz
CS> in /boot/loader.conf to at least 1000, if not 2000 or 4000?
# vmstat -i
interrupt
On Fri, Oct 29, 2010 at 06:15:16AM -0400, Kris Moore wrote:
>
> I'm running into a rather interesting problem here on HEAD with a newer Asus
> EEE PC and the "alc" network driver. The device works great when a
> cable is plugged in, no issues at all. However, if I unplug the ethernet
> and reboot
On 10/27/2010 01:27 PM, Sean Bruno wrote:
> We moved an application stack from BSD4(BOO!) to BSD7(YAY!) recently and
> got a great performance increase, so first: GOOD JOB.
>
> Periodically, we are seeing strings of duplicate ACK being sent in
> <100uSec deltas. I can't imagine that this should b
On Oct 28, 2010, at 11:39 PM, Коньков Евгений wrote:
> Здравствуйте, Chuck.
Um, greetings?
> Вы писали 28 октября 2010 г., 23:41:58:
>
> CS> On Oct 28, 2010, at 1:21 PM, Коньков Евгений wrote:
>>> [ ... ]
>
> CS> What is "sysctl kern.clockrate", and have you increased kern.hz
> CS> in /boot/l
Zdravstvuyte, Chuck. (How do you do, Chuck ;-)
Вы писали 29 октября 2010 г., 20:23:19:
CS> On Oct 28, 2010, at 11:39 PM, Коньков Евгений wrote:
>> Здравствуйте, Chuck.
CS> Um, greetings?
yes, it is
>> Вы писали 28 октября 2010 г., 23:41:58:
>>
>> CS> On Oct 28, 2010, at 1:21 PM, Коньков Евген
On Thu, Oct 28, 2010 at 11:21:11PM +0300, ?? ?? wrote:
> Hello,
> w/0 polling:
>
>
> serv1# ifconfig nfe0
> nfe0: flags=8943 metric 0 mtu
> 1500
> options=10b
> ether 00:13:d4:ce:82:16
> inet 10.11.8.17 netmask 0xfc00 broadcast 10.11.11.255
>
On Fri, Oct 29, 2010 at 10:20:10AM +0300, ?? ?? wrote:
> Hi, Freebsd-net.
>
> serv1# ifocnfig nfe0
> nfe0: flags=8943 metric 0 mtu
> 1500
> options=10b
> ether 00:13:d4:ce:82:16
> inet 10.11.8.17 netmask 0xfc00 broadcast 10.11.11.255
> i
Although the tftp protocol has, apparently, been intended from the outset
to provide support for finite-time file transfers, I myself would like to
see if I can use it in the context of a (near-)continuous streaming data
collection application.
This raises a number of issues and questions, and I'
Also make sure kern.polling.idle_poll is enabled. By default it is
disabled. This makes a big difference in polling throughput.
Larry
--
Larry Baird| http://www.gta.com
Global Technology Associates
Howdy,
I have freebsd80-release with an upgraded em0 driver from freebsd8.1
(and an appropriate touch of if_var.h). I'm running an amd64 on a vmware vm.
And I see this in dmesg:
cut-
em0: port 0x2000-203f mem
0xd894-0xd895, 0xd890-0xd890 irq 18
On Fri, Oct 29, 2010 at 09:55:31AM -0700, Pyun YongHyeon wrote:
> On Fri, Oct 29, 2010 at 06:15:16AM -0400, Kris Moore wrote:
> >
> > I'm running into a rather interesting problem here on HEAD with a newer Asus
> > EEE PC and the "alc" network driver. The device works great when a
> > cable is plu
On Fri, Oct 29, 2010 at 08:44:22PM -0400, Kris Moore wrote:
> On Fri, Oct 29, 2010 at 09:55:31AM -0700, Pyun YongHyeon wrote:
> > On Fri, Oct 29, 2010 at 06:15:16AM -0400, Kris Moore wrote:
> > >
> > > I'm running into a rather interesting problem here on HEAD with a newer
> > > Asus
> > > EEE PC
FYI,
That dmesg output I get from my franken-driver on vmware is exactly the same
output I get from the *working* bsd80Release on vmware:
cut
[r...@npx7511 /usr/src/sys/dev/e1000]# dmesg | grep em0
em0: port 0x2000-0x203f mem
0xd894-0xd895,0xd890-0xd8
I remember seeing the same thing when running a FreeBSD guest on
Linux/KVM, its informational, the code will enable said bits right after
it says that.
So, the focus should be on the data, you are saying the delivered
driver in 8.0 out of the box works and which driver exactly are you
trying to us
On Fri, Oct 29, 2010 at 17:07, Ricky Charlet wrote:
> Howdy,
> I have freebsd80-release with an upgraded em0 driver from freebsd8.1
> (and an appropriate touch of if_var.h). I'm running an amd64 on a vmware vm.
> And I see this in dmesg:
>
> cut-
> em0: port 0x
> -Original Message-
> From: j...@clockworksquid.com [mailto:j...@clockworksquid.com] On
> Behalf Of Juli Mallett
> Sent: Friday, October 29, 2010 6:55 PM
> To: Ricky Charlet
> Cc: freebsd-net@freebsd.org
> Subject: Re: em driver problem on vmware
>
> On Fri, Oct 29, 2010 at 17:07, Ricky
pciconf -l
If you got a printf from the driver its VERY odd that it says the interface
does not exist :)
Jack
On Fri, Oct 29, 2010 at 7:03 PM, Ricky Charlet wrote:
>
>
> > -Original Message-
> > From: j...@clockworksquid.com [mailto:j...@clockworksquid.com] On
> > Behalf Of Juli Mallet
Hi Rick,
The FreeBSD -current works fine for me with the newest em(4)
under the VMware player.
Kevin
On Friday, 2010-10-29 at 19:22 -0700, Ricky Charlet wrote:
> Thanks Jack,
>
> The failure is that ifconfig is unaware of em0. My em0 is
> not configured, so link partn
Hi Jack,
My pciconf output is attached. I'm afraid I don't grok it and will need a
hand to even let me know if this is good/not-good.
Ricky
From: Jack Vogel [mailto:jfvo...@gmail.com]
Sent: Friday, October 29, 2010 10:07 PM
To: Ricky Charlet
Cc: Juli Mallett; freebsd-net@freebsd.org
Subject: R
20 matches
Mail list logo
