On Sat, Mar 03, 2007 at 11:40:06PM +, Bruce M Simpson wrote:
> Yar Tikhiy wrote:
> >
> >In fact, there two independent flags indicating interface's readiness:
> >IFF_UP and IFF_DRV_RUNNING. The former is controlled by the admin
> >and the latter, by the driver. E.g., an interface can be UP bu
On Sat, Mar 03, 2007 at 11:44:12PM +0100, Andre Oppermann wrote:
> Yar Tikhiy wrote:
> >On Sat, Mar 03, 2007 at 12:03:05AM +, Bruce M Simpson wrote:
> >>During testing of M_PROMISC I noticed a couple of issues with our CARP.
> >>
> >>1. carp doesn't seem to maintain input/output statistics on i
Yar Tikhiy wrote:
In fact, there two independent flags indicating interface's readiness:
IFF_UP and IFF_DRV_RUNNING. The former is controlled by the admin
and the latter, by the driver. E.g., an interface can be UP but
not really ready to operate due to h/w reasons, or vice versa.
Perhaps we s
On 03/03/07, Kip Macy <[EMAIL PROTECTED]> wrote:
On a sidenote - my laptop runing 6.1 has a tendency to overheat. I'm
installing RELENG_6 on a desktop for different reasons. Can someone
point me to something to hook up a cardbus card to a PC? (I might be
able to check in a fix if I can test it).
Robert Watson wrote:
On Fri, 2 Mar 2007, Andre Oppermann wrote:
Instead of the unlock-lock dance soreceive_stream() pulls a properly
sized (relative to the receive system call buffer space) from the
socket buffer drops the lock and gives copyout as much time as it
needs. In the mean time th
On 03/03/07, Kip Macy <[EMAIL PROTECTED]> wrote:
ral has locking bugs on 6.x. I was under the impression that it is
barely used from how quickly I hit them.
-Kip
is this just a case of "grin & bare it"? unless there is something I
can do, testing wise which I am more then happy to
On 3/3/07, Kip Macy <[EMAIL PROTECTED]> wrote:
ral has locking bugs on 6.x. I was under the impression that it is
barely used from how quickly I hit them.
On a sidenote - my laptop runing 6.1 has a tendency to overheat. I'm
installing RELENG_6 on a desktop for different reasons. Can someone
poi
ral has locking bugs on 6.x. I was under the impression that it is
barely used from how quickly I hit them.
-Kip
On 3/3/07, Kimi Ostro <[EMAIL PROTECTED]> wrote:
Hi list,
I have been using a FreeBSD based wifi network for about 5 months now,
reading the handbook made this a breeze.
Hi list,
I have been using a FreeBSD based wifi network for about 5 months now,
reading the handbook made this a breeze.
Introducing wifi to one of my boxes that would have uptimes of months
now causes lock-ups of some sort, the machine just completely dies
atleast to any networking access and I
Yar Tikhiy wrote:
On Sat, Mar 03, 2007 at 12:03:05AM +, Bruce M Simpson wrote:
During testing of M_PROMISC I noticed a couple of issues with our CARP.
1. carp doesn't seem to maintain input/output statistics on its ifnet.
This should be OK. A carp(4) interface is just a place for CARP
se
On Fri, 2 Mar 2007, Andre Oppermann wrote:
Instead of the unlock-lock dance soreceive_stream() pulls a properly sized
(relative to the receive system call buffer space) from the socket buffer
drops the lock and gives copyout as much time as it needs. In the mean time
the lower half can happi
On Fri, Mar 02, 2007 at 11:55:16PM +, Bruce M Simpson wrote:
> Hello all,
>
> I would like to announce an updated version of the 802.1p input patch,
> available at:
>http://people.freebsd.org/~bms/dump/latest-8021p.diff
>
> I have cut down the original scope of the patch. I previously ra
On Sat, Mar 03, 2007 at 12:03:05AM +, Bruce M Simpson wrote:
> During testing of M_PROMISC I noticed a couple of issues with our CARP.
>
> 1. carp doesn't seem to maintain input/output statistics on its ifnet.
This should be OK. A carp(4) interface is just a place for CARP
settings to live.
Hi.
Ian Smith wrote:
When started the first time, before there's any ng0 interface, mpd logs
the following two lines then immediately exits without further ado:
paqi# /usr/local/etc/rc.d/mpd4.sh start
Try to run mpd from console just by typing "mpd4" to get all logs to
console. To get more l
On Sat, Mar 03, 2007 at 07:01:00PM +0100, Alessandro de Manzano wrote:
> On Fri, Mar 02, 2007 at 11:36:15AM +, Wojciech A. Koszek wrote:
>
> > > What could be ? What could I try ? Ideas ?
> >
> > You can check if changing the interface "UP" flag makes in any better:
> >
> > ifconfig up
On Sat, Mar 03, 2007 at 06:53:17PM +0100, Alessandro de Manzano wrote:
> On Fri, Mar 02, 2007 at 02:37:50PM -0600, Paul Schmehl wrote:
>
> > Shouldn't you be using the bce driver? This is an i386 machine, but amd64
> > should work the same (you're using the same chipset):
>
> well, actually I h
Kernel
device wlan
device iwi
device wlan_tkip
device wlan_acl
device wlan_ccmp
device wlan_wep
kldstat
[EMAIL PROTECTED] kldstat
Id Refs AddressSize Name
1 15 0xc040 3c5288 kernel
21 0xc07c6000 7160 if_rl.ko
31 0xc07ce000 246c8sound.ko
41 0xc07f8000 60f94a
On Fri, Mar 02, 2007 at 11:36:15AM +, Wojciech A. Koszek wrote:
> > What could be ? What could I try ? Ideas ?
>
> You can check if changing the interface "UP" flag makes in any better:
>
> ifconfig up
yep, this worked for use with my 2 switches.
I today also tried with another switc
On Fri, Mar 02, 2007 at 05:55:35PM -0500, Jung-uk Kim wrote:
> > [EMAIL PROTECTED]:0:0: class=0x02 card=0x165914e4 chip=0x165914e4
> > rev=0x21 hdr=0x00 vendor = 'Broadcom Corporation'
> > device = 'BCM5750A1 NetXtreme Gigabit Ethernet PCI Express'
> > class = network
On Fri, Mar 02, 2007 at 02:37:50PM -0600, Paul Schmehl wrote:
> Shouldn't you be using the bce driver? This is an i386 machine, but amd64
> should work the same (you're using the same chipset):
well, actually I have that driver in my kernel but it does not get
attached (tried both i386 and x64
I'm having trouble getting mpd 4.1 going, and am a netgraph noobie.
FreeBSD paqi.nimnet.asn.au 5.5-STABLE FreeBSD 5.5-STABLE #0: Sat Mar 3
03:14:13 EST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PAQI5S_3 i386
paqi# mpd4 -v
Version 4.1 ([EMAIL PROTECTED] 20:51 3-Mar-2007)
/etc/rc.conf (update
21 matches
Mail list logo
