Re: kern/153938: [run] [panic] [patch] Workaround for use-after-free panic

2011-01-20 Thread PseudoCylon
The following reply was made to PR kern/153938; it has been noted by GNATS. From: PseudoCylon To: bug-follo...@freebsd.org, Juergen Lock Cc: Subject: Re: kern/153938: [run] [panic] [patch] Workaround for use-after-free panic Date: Thu, 20 Jan 2011 16:35:48 -0800 (PST) Hello, I have appli

Re: strange netstat -ian output

2011-01-20 Thread Bernd Walter
On Thu, Jan 20, 2011 at 08:00:46PM +0100, Petr Lampa wrote: > > After our private mail exchange with B.Walter I've looked at the sources and > RFC drafts and realised that Node Information ICMPv6 was taken out from KAME > in 2000 and that code was implemented according draft-07. The group addres

Re: kern/153610: [nfe] nfe0 malfunction at boot time

2011-01-20 Thread yongari
Synopsis: [nfe] nfe0 malfunction at boot time Responsible-Changed-From-To: freebsd-net->yongari Responsible-Changed-By: yongari Responsible-Changed-When: Thu Jan 20 21:45:36 UTC 2011 Responsible-Changed-Why: Grab. http://www.freebsd.org/cgi/query-pr.cgi?pr=153610

Re: kern/152411: [re] network card works only on 1000M

2011-01-20 Thread yongari
Synopsis: [re] network card works only on 1000M Responsible-Changed-From-To: freebsd-net->yongari Responsible-Changed-By: yongari Responsible-Changed-When: Thu Jan 20 21:43:48 UTC 2011 Responsible-Changed-Why: Grab. http://www.freebsd.org/cgi/query-pr.cgi?pr=152411 __

Re: bogus 0 len IP packet, was: Hang in VOP_LOCK1_APV on 8-STABLE with NFS.

2011-01-20 Thread Brandon Gooch
On Wed, Jan 19, 2011 at 5:59 PM, Pyun YongHyeon wrote: > On Tue, Jan 18, 2011 at 07:35:30PM +0100, sth...@nethelp.no wrote: >> > > I'm seeing the same problem with Broadcom NetXtreme (bce) cards: >> > > >> > > bce0@pci0:3:0:0:        class=0x02 card=0x03421014 chip=0x164c14e4 >> > > rev=0x12

Re: strange netstat -ian output

2011-01-20 Thread Petr Lampa
After our private mail exchange with B.Walter I've looked at the sources and RFC drafts and realised that Node Information ICMPv6 was taken out from KAME in 2000 and that code was implemented according draft-07. The group address was then changed in draft-13 (2006) to the same format as solicit

Re: strange netstat -ian output

2011-01-20 Thread Bernd Walter
On Fri, Jan 21, 2011 at 12:58:04AM +0900, Hajimu UMEMOTO wrote: > Hi, > > > On Thu, 20 Jan 2011 15:38:13 + (UTC) > > "Bjoern A. Zeeb" said: > > > Yes, it is the internal scope address representation of the KAME IPv6 > > stack. It is hided in the output of 'netstat -rn'. But, it see

Re: strange netstat -ian output

2011-01-20 Thread Hajimu UMEMOTO
Hi, > On Thu, 20 Jan 2011 15:38:13 + (UTC) > "Bjoern A. Zeeb" said: > Yes, it is the internal scope address representation of the KAME IPv6 > stack. It is hided in the output of 'netstat -rn'. But, it seems not > for `netstat -ani'. There is no reason to not hide it for `netstat >

Re: strange netstat -ian output

2011-01-20 Thread Bjoern A. Zeeb
On Fri, 21 Jan 2011, Hajimu UMEMOTO wrote: Hi, On Wed, 19 Jan 2011 03:44:31 +0100 Bernd Walter said: ticso> This is one of the blocks for this interface: ticso> re01500 2a02:21e0:16e 2a02:21e0:16e0:200 - - 1 - - ticso> ff02:1::2

Re: strange netstat -ian output

2011-01-20 Thread Hajimu UMEMOTO
Hi, > On Wed, 19 Jan 2011 03:44:31 +0100 > Bernd Walter said: ticso> This is one of the blocks for this interface: ticso> re01500 2a02:21e0:16e 2a02:21e0:16e0:200 - - 1 - - ticso> ff02:1::2 (refs: 1) ticso>

Re: if_run and wlan_amrr: kernel panics on 8.2-PRERELEASE amd64

2011-01-20 Thread Bernhard Schmidt
On Thursday, January 20, 2011 12:46:02 Alexander Zagrebin wrote: > Hi! > > On 19.01.2011 17:57:00 +0100, Bernhard Schmidt wrote: > > > > So there is the one issue only: the panic if runfw.ko and > > > > wlan_amrr.ko both loaded via loader.conf. > > > > Have you any ideas? > > > > > > No yet, I'll

Re: if_run and wlan_amrr: kernel panics on 8.2-PRERELEASE amd64

2011-01-20 Thread Alexander Zagrebin
Hi! On 19.01.2011 17:57:00 +0100, Bernhard Schmidt wrote: > > > So there is the one issue only: the panic if runfw.ko and > > > wlan_amrr.ko both loaded via loader.conf. > > > Have you any ideas? > > > > No yet, I'll dig around there later today. > > Hmm, I'm not able to reproduce this, works a