openbsd test error: timed out

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: 5dce2af0acb7 In preparation for reusing libLLVM component ..
git tree: openbsd
kernel config: https://syzkaller.appspot.com/x/.config?x=ffa1da4399f74b2b
dashboard link: https://syzkaller.appspot.com/bug?extid=3d5fe3700a4bf4a8480c

Unfortunately, I don't have any reproducer for this crash yet.

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+3d5fe3...@syzkaller.appspotmail.com



---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.

[Dmitry Vyukov]

On Wed, Feb 27, 2019 at 11:27 AM syzbot
<syzbot+3d5fe3...@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 5dce2af0acb7 In preparation for reusing libLLVM component ..
> git tree: openbsd
> kernel config: https://syzkaller.appspot.com/x/.config?x=ffa1da4399f74b2b
> dashboard link: https://syzkaller.appspot.com/bug?extid=3d5fe3700a4bf4a8480c
>
> Unfortunately, I don't have any reproducer for this crash yet.
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+3d5fe3...@syzkaller.appspotmail.com

A similar errors popped up on some linux instances as well.
I can't understand why there is no kernel output at all (in these
other bugs too)...

The testing is started here (only MonitorExecution can return this
"timed out" string, so it should be it):
https://github.com/google/syzkaller/blob/083cfd0e4a471c4f76d872ce6b521e6443246b3a/pkg/instance/instance.go#L272-L282
It always attached whole report to the error.

"timed out" errors is only produces here:
https://github.com/google/syzkaller/blob/083cfd0e4a471c4f76d872ce6b521e6443246b3a/vm/vm.go#L180
And extractError must always attach kernel output to the returned report.

And we've just copied some binaries to the VM, so it must not be
completely dead.
And syz-fuzzer prints periodic keep-alive messages to stdout so at
least should be captured in the output.

Yet somehow there is no output at all in the report...

[Anton Lindqvist]

No action in over a month, closing for now.

#syz invalid