Old Synopsis: Panic during shutdown, tcp_ctloutput: inp == NULL
New Synopsis: [tcp] [panic] Panic during shutdown, tcp_ctloutput: inp == NULL
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu Dec 18 00:46:25 UTC 2008
Responsible-Ch
Maksim Yevmenkin wrote:
On Wed, Dec 17, 2008 at 1:53 PM, Uwe Grohnwaldt wrote:
there is nothing mentioned about the network-interface neither in dmesg nor
in pciconf.
in my kernelconfig there are the entries:
device em
device igb
device ixgb
with the old kernel everything works.
i a
We tried 7.1RC and the card works fine.
Jack Vogel wrote:
This is odd, that device is old, its not in igb, the support looks to me
like its
there in the code, its an 82541GI_LF.
I am on vacation, and snowed in even if i weren't :) But I will look into
it.
Can you please try using the RC versio
On Wed, Dec 17, 2008 at 1:53 PM, Uwe Grohnwaldt wrote:
> there is nothing mentioned about the network-interface neither in dmesg nor
> in pciconf.
> in my kernelconfig there are the entries:
> device em
> device igb
> device ixgb
>
> with the old kernel everything works.
>
i actually had somewhat
> Date: Wed, 17 Dec 2008 22:07:18 +0100
> From: Luigi Rizzo
> Sender: owner-freebsd-curr...@freebsd.org
>
> On Wed, Dec 17, 2008 at 12:59:17PM -0800, Paul Saab wrote:
> > are you looking for if_em or em?
>
> also, wasn't the em driver renamed to ixgb or something like that ?
em is still if_em,
This is odd, that device is old, its not in igb, the support looks to me
like its
there in the code, its an 82541GI_LF.
I am on vacation, and snowed in even if i weren't :) But I will look into
it.
Can you please try using the RC version of 7.1 to see if it has the same
problem??
Jack
On Wed,
there is nothing mentioned about the network-interface neither in dmesg
nor in pciconf.
in my kernelconfig there are the entries:
device em
device igb
device ixgb
with the old kernel everything works.
Luigi Rizzo wrote:
On Wed, Dec 17, 2008 at 12:59:17PM -0800, Paul Saab wrote:
are you
On Wed, Dec 17, 2008 at 1:07 PM, Luigi Rizzo wrote:
> On Wed, Dec 17, 2008 at 12:59:17PM -0800, Paul Saab wrote:
> > are you looking for if_em or em?
>
> also, wasn't the em driver renamed to ixgb or something like that ?
>
No... Maybe you need igb in your kernel as well?
___
On Wed, Dec 17, 2008 at 12:59:17PM -0800, Paul Saab wrote:
> are you looking for if_em or em?
also, wasn't the em driver renamed to ixgb or something like that ?
cheers
luigi
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/list
are you looking for if_em or em?
On Wed, Dec 17, 2008 at 12:56 PM, Uwe Grohnwaldt wrote:
> with latest src, there were no messages about if_em in dmesg. miwi built
> src from 2008-07-27 - there the device was active.
>
> Paul Saab wrote:
>
>> does dmesg show the device failing to attach?
>>
>> O
with latest src, there were no messages about if_em in dmesg. miwi built
src from 2008-07-27 - there the device was active.
Paul Saab wrote:
does dmesg show the device failing to attach?
On Wed, Dec 17, 2008 at 11:37 AM, Uwe Grohnwaldt
wrote:
hi,
i've forgotten the cc, sry.
c
does dmesg show the device failing to attach?
On Wed, Dec 17, 2008 at 11:37 AM, Uwe Grohnwaldt wrote:
> hi,
>
> i've forgotten the cc, sry.
>
> chers,
> uwe
>
> howdy,
>
> miwi and me tried to update a freebsd-current server to the todays src.
> after the update my em0-device disappeared. inform
hi,
i've forgotten the cc, sry.
chers,
uwe
--- Begin Message ---
howdy,
miwi and me tried to update a freebsd-current server to the todays src.
after the update my em0-device disappeared. information about the old image:
uname -a
FreeBSD amd.miwibox.org 8.0-CURRENT FreeBSD 8.0-CURRENT #0: F
Hello, Freebsd-net.
Why does adding address and destination for point-to-point interface
add route for destination address? It is not always right. For
example, many providers have VPN concentrator address same as "remote
end" address and this default create loop -- VPN packets (TCP, UDP or
GRE o
I had the same with apache2..
here is the method what i used:
edit these files:
/usr/src/sys/sys/select.h
/usr/include/sys/select.h
change this:
#define FD_SETSIZE 1024U
to this:
#define FD_SETSIZE 4096U
cd /usr/src && make buildworld && make installworld && reboot
after this i got r
At Wed, 17 Dec 2008 21:27:58 +0200,
Artyom Viklenko wrote:
> BIND 9.5.0-P2 already in ports and seems working well.
> Giv it a try.
In this context 9.5.0-P2 won't help. All 9.x.y-P[12] versions have
the same problem.
---
JINMEI, Tatuya
Internet Systems Consortium, Inc.
Ott Köstner пишет:
JINMEI Tatuya / 神明達哉 wrote:
At Wed, 17 Dec 2008 15:20:02 +0200,
Ott Köstner wrote:
named[63198]: socket: too many open file descriptors
last message repeated 26 times
Bind version is: BIND 9.4.2-P2
Please try BIND 9.4.3. Even with all attempts to mitigate the tro
JINMEI Tatuya / 神明達哉 wrote:
At Wed, 17 Dec 2008 15:20:02 +0200,
Ott Köstner wrote:
named[63198]: socket: too many open file descriptors
last message repeated 26 times
Bind version is: BIND 9.4.2-P2
Please try BIND 9.4.3. Even with all attempts to mitigate the trouble
and with tweak
At Wed, 17 Dec 2008 15:20:02 +0200,
Ott Köstner wrote:
> named[63198]: socket: too many open file descriptors
> last message repeated 26 times
>
> Bind version is: BIND 9.4.2-P2
Please try BIND 9.4.3. Even with all attempts to mitigate the trouble
and with tweaking parameters, 9.4.2-P2 still h
At 11:34 PM 12/16/2008, Kip Macy wrote:
Try changeid 186209.
Thanks, no panic now!
---Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubsc
Hi,
I have a big server that has 3 network cards (2 Intel(R) PRO/1000
Gigabit Ethernet adapter and 1 3Com Etherlink XL and Fast Etherlink XL
Ethernet).
I have trouble with the cards : several times per hour, the interface
goes down and up with the following dmesg signal :
Dec 17 07:06:22 picp
Ferdinand Goldmann wrote:
> > Hi there,
> >
> > I just upgraded a FreeBSD 6.x machine to FreeBSD 6.3-STABLE, and now I'm
> > seeing this same problem which has already been reported in different
> > postings:
> >
> > named[51769]: socket: too many open file descriptors
> > last message repeated
Hi Steve
Am 17.12.2008 um 04:33 schrieb Steve Bertrand:
Hi all,
I'm curious to know if the creation of additional 'lo' interfaces is
possible at boot via the traditional /etc/rc.conf as of yet.
Forgive me if I've missed anything regarding this.
I'm still trying to blend some functionality bet
Steve Bertrand wrote:
...
Can anyone provide any feedback or procedural guidance on how I can (for
example):
- ensure that lo1, lo2-lo14 are created at boot
- ensure that disc0 is created at boot, with an assigned IPv4 and IPv6
address
You should be able to do this by putting them into the
'c
Hi,
> On Wed, 10 Dec 2008 13:48:51 +0800
> "=?GB2312?B?s8LQocn6?=" said:
stutiredboy> hi,all,we have a project which must resolv some domains in the
server
stutiredboy> process
stutiredboy> our system in FreeBSD 6.2 or 6.3, the server process may open 7000+
stutiredboy> sockets,not fork
25 matches
Mail list logo
