El 17/4/21 a les 12:44, Damien Zammit ha escrit:
Can you try rebasing on master and see if you have the same issues?
After merging the last changes the arbiter hangs at startup, so it
doesn't live enough to be killed. I think it's probably another effect
of the same bug in my version of
El 17/4/21 a les 14:14, Samuel Thibault ha escrit:
Do you mean that without your changes there is no pci arbiter kill?
Yes
Joan Lledó, le sam. 17 avril 2021 12:12:45 +0200, a ecrit:
> Hi,
>
> El 7/3/21 a les 20:33, Samuel Thibault ha escrit:
> > You could e.g. put mach_prints in glibc's sysdeps/mach/hurd/kill.c's
> > SIGKILL case.
> >
> > Possibly better also add a mach_print in hurd/hurdsig.c SIGKILL on
> > _hurd_or
Hi,
On 17/4/21 8:12 pm, Joan Lledó wrote:
> I spent too much time on this and still haven't found the problem, need
> some help. I suspect the problem is in the kernel b/c it's the part I'm
> less competent. I'm attaching a patch with the changes I made on the
> memory object proxy logic. Could
Hi,
El 7/3/21 a les 20:33, Samuel Thibault ha escrit:
You could e.g. put mach_prints in glibc's sysdeps/mach/hurd/kill.c's
SIGKILL case.
Possibly better also add a mach_print in hurd/hurdsig.c SIGKILL on
_hurd_orphaned.
I tried but I saw nothing, is it supposed to show the messages in the
c
Hi
El 7/3/21 a les 20:33, Samuel Thibault ha escrit:
Joan Lledó, le dim. 07 mars 2021 20:08:21 +0100, a ecrit:
is not there any process that kills the arbiter after a while of not
being used?
That shouldn't be happening.
and how could I know who is sending the SIGKILL?
How do you notice t
Joan Lledó, le dim. 07 mars 2021 20:08:21 +0100, a ecrit:
> is not there any process that kills the arbiter after a while of not
> being used?
That shouldn't be happening.
> and how could I know who is sending the SIGKILL?
How do you notice that it's a SIGKILL?
You could e.g. put mach_prints in
Hi Hurd,
I've observed how my instance of the pci arbiter receives a SIGKILL
about a minute after start, it could be my fault as I've being messing
around with gnumach, libpciaccess and the arbiter itself, but just to
confirm: is not there any process that kills the arbiter after a while
of n
