openbsd test error: timed out (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4aea2da5f361 drm/amd/display: Fix timer_per_pixel unit error
git tree: openbsd
kernel config: https://syzkaller.appspot.com/x/.config?x=fe55924c11e64b0a
dashboard link: https://syzkaller.appspot.com/bug?extid=d918a7601c8e887e21b2

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



---
This report 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 issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[Anton Lindqvist]

On Sun, Sep 26, 2021 at 09:41:22PM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 4aea2da5f361 drm/amd/display: Fix timer_per_pixel unit error
> git tree: openbsd
> kernel config: https://syzkaller.appspot.com/x/.config?x=fe55924c11e64b0a
> dashboard link: https://syzkaller.appspot.com/bug?extid=d918a7601c8e887e21b2

Why don't we get any logs on this one? Is it failing somewhere too^W
early on?

[Greg Steuck]

Yes, the logs are getting lost.

Alexandr and I debugged it today. I blame the ssh-rsa change, see https://github.com/google/syzkaller/pull/2784

To be verified tomorrow.

--
You received this message because you are subscribed to the Google Groups "syzkaller-openbsd-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-openbsd...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-openbsd-bugs/YVSzRmsvDm5gUvvA%40desk.basename.se.

[Aleksandr Nogikh]

The problem indeed turned out to be related to ssh-rsa. I merged Greg's PR and now OpenBSD targets are working fine.

Regarding why there were no logs - the exact problem is already identified and I put it to my TODO list. I think I'll fix it tomorrow or next week.
It's related to how this method works (link below) - waitForConsoleConnect does not detect all types of errors and yet consumes the part of the output that'd have been important for debugging then.
https://github.com/google/syzkaller/blob/1d849ab4d892af13a249f75628790b47e42b7c74/vm/gce/gce.go#L335

To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-openbsd-bugs/CANMcDo-KGe3DK7UHACmGgH_0-86A_6akUQHJHLFSerMGOTyuBg%40mail.gmail.com.

[Anton Lindqvist]

#syz invalid