Ian Lepore wrote on 03/26/16 04:09 AM:
On Sat, 2016-03-26 at 02:42 +0300, Ruslan Makhmatkhanov wrote:
Ian Lepore wrote on 03/26/16 02:11 AM:
On Fri, 2016-03-25 at 23:33 +0300, Ruslan Makhmatkhanov wrote:
Hello,
I have this in pciconf output:
FreeBSD_HEAD_amd64_gcc4.9 - Build #1137 - Failure:
Build information:
https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/1137/
Full change log:
https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/1137/changes
Full build log:
On 25 Mar 2016, at 19:30, Dimitry Andric wrote:
>
> On 25 Mar 2016, at 05:21, Eric Camachat wrote:
>>
>> I tried to buildworld with -Os CFLAGS, but it failed.
> ...
>> PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
>> Preprocessed source(s) and
hiya,
can you identify a revision where it /doesn't/ do broken pipe? That'd
be the best way to start debugging this and figure out which revision
broke things.
I haven't updated to the latest -HEAD on anything just yet;
everything's a few weeks old.
Thanks,
-a
On 25 March 2016 at 13:30, O.
In message
, Adrian Chadd writes:
I can second that -current isn't too great right now, and I also see
the breaking SSH sessions.
I'm running:
FreeBSD 11.0-CURRENT #32 r296137: Sat Feb 27 11:34:01 UTC 2016
I
In message
, Ultima writes:
> A large zfs send [...]
I am not running zfs.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since
In message <201603262331.u2qnvxvm080...@gw.catspoiler.org>, Don Lewis writes:
>> I am not running zfs.
Ohh, and I should probably add: I don't have a swap-space configured.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD
On 26 Mar, Michael Butler wrote:
> -current is not great for interactive use at all. The strategy of
> pre-emptively dropping idle processes to swap is hurting .. big time.
>
> Compare inactive memory to swap in this example ..
>
> 110 processes: 1 running, 108 sleeping, 1 zombie
> CPU: 1.2%
Having this long timeout issue occur many times during the day. Normally
not this bad, currently on r297060 amd64. A few hours ago had a system hang
that lasted for about 1-2 hours.(not sure how long exactly, gave up
waiting) It occured after a zfs destroy operation and affected sshd. (could
no
On 26 Mar, Poul-Henning Kamp wrote:
>
> In message
>
> , Ultima writes:
>
>> A large zfs send [...]
>
> I am not running zfs.
I am. I'm not seeing any unexpected problems. I haven't really loaded
this system up
On 26 Mar, Poul-Henning Kamp wrote:
>
> In message
>
> , Adrian Chadd writes:
>
> I can second that -current isn't too great right now, and I also see
> the breaking SSH sessions.
>
> I'm running:
>
> FreeBSD
Am Fri, 25 Mar 2016 13:31:31 -0700
"K. Macy" schrieb:
> Does this pre or postage input changes?
???
First of all, and the most visible fact is, that the ssh connection with high
terminal
i/o (compiling world, poudriere bulk ...) receives very often broken pipe. The
Sorry meant inpcb and autocorrect "fixed" it.
On Saturday, March 26, 2016, O. Hartmann
wrote:
> Am Fri, 25 Mar 2016 13:31:31 -0700
> "K. Macy" > schrieb:
>
> > Does this pre or postage input changes?
>
> ???
>
> First of all, and the
-current is not great for interactive use at all. The strategy of
pre-emptively dropping idle processes to swap is hurting .. big time.
Compare inactive memory to swap in this example ..
110 processes: 1 running, 108 sleeping, 1 zombie
CPU: 1.2% user, 0.0% nice, 4.3% system, 0.0% interrupt,
Am Sat, 26 Mar 2016 13:28:16 -0400
Michael Butler schrieb:
> -current is not great for interactive use at all. The strategy of
> pre-emptively dropping idle processes to swap is hurting .. big time.
What is the gain then?
If this "feature" results in corrupted ssh
15 matches
Mail list logo