Re: 11.0 stuck on high network load

2016-10-10 Thread Slawa Olhovchenkov
On Mon, Oct 10, 2016 at 05:44:21PM +0200, Julien Charbon wrote: > >> can check the current other usages of goto findpcb in tcp_input(). The > >> rational here being: > >> > >> - Behavior before the patch: If the inp we found was deleted then goto > >> findpcb. > >> - Behavior after the patch:

Re: 11.0 stuck on high network load

2016-10-10 Thread Julien Charbon
Hi, On 10/10/16 4:29 PM, Slawa Olhovchenkov wrote: > On Mon, Oct 10, 2016 at 04:03:39PM +0200, Julien Charbon wrote: >> On 10/10/16 3:32 PM, Slawa Olhovchenkov wrote: >>> On Mon, Oct 10, 2016 at 01:26:12PM +0200, Julien Charbon wrote: On 10/6/16 1:10 PM, Slawa Olhovchenkov wrote: > On

Re: 11-current becoming 11-stable

2016-10-10 Thread Kevin Oberman
On Mon, Oct 10, 2016 at 3:48 AM, tech-lists wrote: > Hi, > > I have a desktop that has run 11-current for at least the last year. I > periodically rebuild kernel and world to keep on top of things. As it's a > desktop, there are lots of ports installed. These are installed

Re: 11-current becoming 11-stable

2016-10-10 Thread Johan Hendriks
Op 10/10/2016 om 12:48 schreef tech-lists: > Hi, > > I have a desktop that has run 11-current for at least the last year. I > periodically rebuild kernel and world to keep on top of things. As > it's a desktop, there are lots of ports installed. These are installed > via the older cd /port &&

Re: 11.0 stuck on high network load

2016-10-10 Thread Slawa Olhovchenkov
On Mon, Oct 10, 2016 at 04:03:39PM +0200, Julien Charbon wrote: > > Hi Slawa, > > On 10/10/16 3:32 PM, Slawa Olhovchenkov wrote: > > On Mon, Oct 10, 2016 at 01:26:12PM +0200, Julien Charbon wrote: > >> On 10/6/16 1:10 PM, Slawa Olhovchenkov wrote: > >>> On Thu, Oct 06, 2016 at 09:28:06AM

Re: 11.0 stuck on high network load

2016-10-10 Thread Julien Charbon
Hi Slawa, On 10/10/16 3:32 PM, Slawa Olhovchenkov wrote: > On Mon, Oct 10, 2016 at 01:26:12PM +0200, Julien Charbon wrote: >> On 10/6/16 1:10 PM, Slawa Olhovchenkov wrote: >>> On Thu, Oct 06, 2016 at 09:28:06AM +0200, Julien Charbon wrote: >>> 2. thread1: In tcp_close() the inp is marked

Re: Failing to upgrade from 10.1-RELEASE to 10.3-STABLE

2016-10-10 Thread George Mitchell
On 10/10/16 03:04, Matthew Seaman wrote: > [...] > Most of the time you should be able to upgrade from any patch level of > release to the latest on any supported release branch using > freebsd-update(8). However there have been a number of occasions where > changes to freebsd-update itself cause

Re: 11.0 stuck on high network load

2016-10-10 Thread Slawa Olhovchenkov
On Mon, Oct 10, 2016 at 01:26:12PM +0200, Julien Charbon wrote: > > Hi, > > On 10/6/16 1:10 PM, Slawa Olhovchenkov wrote: > > On Thu, Oct 06, 2016 at 09:28:06AM +0200, Julien Charbon wrote: > > > >> 2. thread1: In tcp_close() the inp is marked with INP_DROPPED flag, the > >> process

Re: 11.0 stuck on high network load

2016-10-10 Thread Slawa Olhovchenkov
On Mon, Oct 10, 2016 at 01:26:12PM +0200, Julien Charbon wrote: > > Hi, > > On 10/6/16 1:10 PM, Slawa Olhovchenkov wrote: > > On Thu, Oct 06, 2016 at 09:28:06AM +0200, Julien Charbon wrote: > > > >> 2. thread1: In tcp_close() the inp is marked with INP_DROPPED flag, the > >> process

Re: 11.0 stuck on high network load

2016-10-10 Thread Julien Charbon
Hi, On 10/6/16 1:10 PM, Slawa Olhovchenkov wrote: > On Thu, Oct 06, 2016 at 09:28:06AM +0200, Julien Charbon wrote: > >> 2. thread1: In tcp_close() the inp is marked with INP_DROPPED flag, the >> process continues and calls INP_WUNLOCK() here: >> >>

11-current becoming 11-stable

2016-10-10 Thread tech-lists
Hi, I have a desktop that has run 11-current for at least the last year. I periodically rebuild kernel and world to keep on top of things. As it's a desktop, there are lots of ports installed. These are installed via the older cd /port && make install clean way, rather than poudiere.

Do not upgrade Hyper-V instances from 10.x to 11.x yet

2016-10-10 Thread Alexander Shitov
11.0-RELEASE has issues with Hyper-V compatibility. It does not recognizes and then detaches virtual disk. storvsc0: on vmbus0 (probe0:blkvsc0:0:0:0): storvsc scsi_status = 2 (probe0:blkvsc0:0:1:1): invalid LUN 1 ... (probe0:blkvsc0:0:0:1): invalid LUN 1 da0 at blkvsc0 bus 0 scbus1 target 0 lun

Re: Failing to upgrade from 10.1-RELEASE to 10.3-STABLE

2016-10-10 Thread Matthew Seaman
On 09/10/2016 23:56, George Mitchell wrote: > On 10/09/16 15:57, Kurt Jaeger wrote: >> Hi! >> >>> What am I doing wrong? (I get the same failure attempting to upgrade >>> to 10.1-RELEASE and 10.2-RELEASE.) -- George >> >> Ah, one thing: >> >> Please do update to the latest