DragonFlyBSD bugtracker

06/16/2020

06:20 AM DragonFlyBSD Bug #2953: open(2) returns "Permission denied" instead of "File exists"

Wow!
This was blocking me from creating a proper pull-request for ChezScheme that would enable DF support. Of course... zhtw

03/08/2020

08:55 AM DragonFlyBSD Bug #3224 (New): [vkernel] Kernel panic when trying to ping6

I got a kernel panic on my vkernel trying to ping6 another vkernel on the same host.
I might have done an incorrect ... zhtw

10/04/2016

06:55 AM DragonFlyBSD Bug #2951: clock_gettime always repots 0 sec, 0 nsec

Checked on my real machine using 4.6 kernel with your patch. This specific test passes now. zhtw

10/03/2016

01:58 AM DragonFlyBSD Bug #2952 (Closed): vkernel crashes during boot

I'm closing this ticket because the problem was solved for me. But I wander if it makes sense to back-port (basically... zhtw

09/22/2016

11:55 PM DragonFlyBSD Bug #2953 (Resolved): open(2) returns "Permission denied" instead of "File exists"

I am porting ChezScheme to DragonFly. Turned out ChezScheme has very thorough set of tests. I found that open(2) retu... zhtw

09/21/2016

04:31 PM DragonFlyBSD Bug #2951: clock_gettime always repots 0 sec, 0 nsec

Thanks!
It should definitely solve the problem with the nsec overflow. But turned out I was very lucky with this t... zhtw

01:22 PM DragonFlyBSD Bug #2951: clock_gettime always repots 0 sec, 0 nsec

When I said million, I of course meant billion. But the example is correct anyway.
I am also looking at the code, bu... zhtw

01:18 PM DragonFlyBSD Bug #2951: clock_gettime always repots 0 sec, 0 nsec

This is interesting. When you asked me to doublecheck if clock_gettime works with CLOCK_THREAD_CPUTIME_ID (because yo... zhtw

11:01 AM DragonFlyBSD Bug #2951: clock_gettime always repots 0 sec, 0 nsec

Thank you. Just tried it. The result is still 0. But again, I'm testing in under a vkernel.
Did you test it on a rea... zhtw

07:57 AM DragonFlyBSD Bug #2951: clock_gettime always repots 0 sec, 0 nsec

Antonio Huete (tuxillo) just gave me the fix for 4.6 vkernel.
Still no luck, CLOCK_PROCESS_CPUTIME_ID returns 0. zhtw