On Aug 26 17:35, Chris H wrote:
On Wed, 26 Aug 2015 18:38:46 +0100 Matt Smith wrote
On Aug 26 12:27, Matt Smith wrote:
>On Aug 26 13:10, Slawa Olhovchenkov wrote:
Hardware error or memory exhausted
>>>
>>>It does appear to be something along those lines. It's not memory
>>>exhaustion as it
It's working for me so far and I haven't seen any watchdog timeouts.
With 10.2-RELEASE I got timeouts and lost connectivity in less that a
minute.
Johann
On Wed, Aug 26, 2015 at 10:28 AM, Yonghyeon PYUN wrote:
> On Wed, Aug 26, 2015 at 10:06:29AM +0200, Johann Hugo wrote:
>> 10.2-RELEASE does no
> Hi Pete!
>
> I cannot reproduce the error, but I'm using fvwm. Can you give a step-bystep
> instruction to reproduce the error?
>
> nik
Hello Nik, thanks for looking at this for me - I havent yet found a reliable way
to reproduce it unfortunately. It seems to happen on wiindows where I have
run
Pete French wrote:
I updated to stable yesterday, plus updated all my porst to
the latest pecompiled packages, but I am now seeing odd problems
with bash on exit. Sometimes it quits, but leaves a zombie
process... e.g
PID TT STATTIME COMMAND
44308 v0 IW 0:00.00 -bash (bash)
44312 v0 I
ia64 stable/10 r286315 boots, but
r286316 hangs at "Entering /boot/kernel/kernel".
Please advise
Thanks
Anton
P.S. This is a continuation of
http://lists.freebsd.org/pipermail/freebsd-stable/2015-August/083203.html
However, since I now found the revision
that broke the boot,
I decided to start
> I can reproduce this easily, although not every time.
Ah, thats good to hear, as it means I am not going completely mad,
thanks! :)
> Running 10.2 under KDE, with bash as a default shell:
> start xterm from a KDE 'konsole', then move to within the xterm
> and try closing it (^D or exit). More o
On Thu, Aug 27, 2015 at 01:12:16PM +0100, Anton Shterenlikht wrote:
> ia64 stable/10 r286315 boots, but
> r286316 hangs at "Entering /boot/kernel/kernel".
>
> Please advise
To state an obvious thing. The commit which you pointed to, changes
the code which is not executed at that early kernel bo
On Thu, Aug 27, 2015 at 02:04:05PM +0200, Mark Martinec wrote:
> Pete French wrote:
>
> > I updated to stable yesterday, plus updated all my porst to
> > the latest pecompiled packages, but I am now seeing odd problems
> > with bash on exit. Sometimes it quits, but leaves a zombie
> > process... e
> Try to obtain the backtrace from the hung xterm. Ideally, you would
> rebuild xterm and the system libraries (rtld+libc+libthr) with debug
> symbols and get the backtraces after that.
I can try this tomorrow - what do I need to set in src.conf to add
debug symbols in when I do a buidlworld (that
On Thu, Aug 27, 2015 at 06:06:26PM +0100, Pete French wrote:
> > Try to obtain the backtrace from the hung xterm. Ideally, you would
> > rebuild xterm and the system libraries (rtld+libc+libthr) with debug
> > symbols and get the backtraces after that.
>
> I can try this tomorrow - what do I need
> On Aug 27, 2015, at 9:23 AM, Konstantin Belousov wrote:
>
> On Thu, Aug 27, 2015 at 01:12:16PM +0100, Anton Shterenlikht wrote:
>> ia64 stable/10 r286315 boots, but
>> r286316 hangs at "Entering /boot/kernel/kernel".
>>
>> Please advise
>
> To state an obvious thing. The commit which you po
The xterm program has a SIGCHLD signal handler that calls wait().
If the handler is invoked while xterm is exiting, a deadlock occurs in rtld.
Cheers
Michiel
#0 _umtx_op_err () at /usr/src/lib/libthr/arch/amd64/amd64/_umtx_op_err.S:37
#1 0x00080305a2b0 in __thr_rwlock_rdlock (rwlock=0x8032
On Thu, Aug 27, 2015 at 08:53:09PM +0200, Michiel Boland wrote:
> The xterm program has a SIGCHLD signal handler that calls wait().
> If the handler is invoked while xterm is exiting, a deadlock occurs in rtld.
>
> Cheers
> Michiel
>
> #0 _umtx_op_err () at /usr/src/lib/libthr/arch/amd64/amd64/_
On Thu, Aug 27, 2015 at 11:29:28AM +0200, Johann Hugo wrote:
> It's working for me so far and I haven't seen any watchdog timeouts.
> With 10.2-RELEASE I got timeouts and lost connectivity in less that a
> minute.
>
Ok, great. Committed in r287238.
Thanks again.
> Johann
>
> On Wed, Aug 26, 20
On 08/27/2015 22:16, Konstantin Belousov wrote:
[...]
I just verified that the signal handler is correctly wrapped for me, on
the latest stable/10. Both with the pre-linked libthr.so and with the
library loaded dynamically at runtime. I used the test program at the
end of the message, put break
15 matches
Mail list logo
