There is for some reason IRQ/sigio handler reentrancy.
Both the debug "by hand" I stuck into irq.c and Thomas traces confirm it.
I have no clue how this is possible as the code in signal.c should guard
against that.
I will sleep on it and try to tackle this tomorrow - no idea what is
going on,
> I will probably add some "manual" debug code to check if the nested
> invocation happens with the debug options off.
Might be timing dependent and/or issue with nested blocking/unblocking
of signals.
Or debug printing when it should not.
Just my two cents
Stian Skjelstad
---
I do not see it with my config. I have cleaned up a few things and can
send an updated version.
At the same time it is 100% reproducible using the config I got from
Thomas. So this is somehow config dependent.
I have compared the configs and the biggest difference I can see is that
Thomas has
On Wed, Nov 11, 2015 at 9:46 PM, Thomas Meyer wrote:
> Am Montag, den 09.11.2015, 15:03 + schrieb Anton Ivanov:
>> It throws a couple of harmless "epoll del fd" warnings on reboot
>> which
>> result the fact that disable_fd/enable_fd are not removed in the
>> terminal/line code.
>>
>> These ar
Am Montag, den 09.11.2015, 15:03 + schrieb Anton Ivanov:
> It throws a couple of harmless "epoll del fd" warnings on reboot
> which
> result the fact that disable_fd/enable_fd are not removed in the
> terminal/line code.
>
> These are harmless and will go away once the term/line code gets
>
