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:
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
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
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 &&
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
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
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
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
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
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:
>>
>>
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.
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
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
13 matches
Mail list logo