* upstream boot error: can't ssh into the instance (7)
@ 2020-02-22 5:18 syzbot
2020-02-22 7:02 ` Dmitry Vyukov
0 siblings, 1 reply; 2+ messages in thread
From: syzbot @ 2020-02-22 5:18 UTC (permalink / raw)
To: linux-kernel, syzkaller-bugs
Hello,
syzbot found the following crash on:
HEAD commit: 11a48a5a Linux 5.6-rc2
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1563eb95e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=31018567b8f0fc70
dashboard link: https://syzkaller.appspot.com/bug?extid=b68d37acb74a6ac82cc9
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
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+b68d37acb74a6ac82cc9@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 syzkaller@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: upstream boot error: can't ssh into the instance (7)
2020-02-22 5:18 upstream boot error: can't ssh into the instance (7) syzbot
@ 2020-02-22 7:02 ` Dmitry Vyukov
0 siblings, 0 replies; 2+ messages in thread
From: Dmitry Vyukov @ 2020-02-22 7:02 UTC (permalink / raw)
To: syzbot; +Cc: LKML, syzkaller-bugs
On Sat, Feb 22, 2020 at 6:18 AM syzbot
<syzbot+b68d37acb74a6ac82cc9@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 11a48a5a Linux 5.6-rc2
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1563eb95e00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=31018567b8f0fc70
> dashboard link: https://syzkaller.appspot.com/bug?extid=b68d37acb74a6ac82cc9
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
>
> 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+b68d37acb74a6ac82cc9@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 syzkaller@googlegroups.com.
>
> syzbot will keep track of this bug report. See:
> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
Somehow "eth0" randomly disappears in some boots...
The same happened before on net and net-next:
Cannot find device "eth0"
Bind socket to interface: No such device
Failed to bring up eth0.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-02-22 7:02 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-02-22 5:18 upstream boot error: can't ssh into the instance (7) syzbot
2020-02-22 7:02 ` Dmitry Vyukov
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).