Date: Wed, 20 Jun 2018 18:13:10 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 229188] Bhyve console hang on serial, works on stdio Message-ID: <bug-229188-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229188 Bug ID: 229188 Summary: Bhyve console hang on serial, works on stdio Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: dgilbert@eicat.ca I have a bulldozer (AMD 9590) running -CURRENT (a few days ago) that exhibi= ts some strange behavior lighting up a linux VM that we have transferred over = from Digital Ocean. If it boots with console as stdio (-f argument), it runs. If it boots with= out -f (console is a null-modem serial), then I get the following on the console (and the boot never finishes) [ 54.548000] serial8250: too much work for irq4 [ 57.412000] serial8250: too much work for irq4 [ 61.040000] [sched_delayed] sched: RT throttling activated [ 61.044000] serial8250: too much work for irq4 [ 63.892000] serial8250: too much work for irq4 [ 66.760000] serial8250: too much work for irq4 [ 69.656000] serial8250: too much work for irq4 Now I've done some research on this message. According to old posts (2009-2012-ish) Other virtual machines got this message from linux when they were either delivering interrupts on the serial when the serial was empty _= or_ they were emptying the serial buffer too quickly and interrupting for more output. On that latter point, apparently this is a legitimate failure mode of some physical chips, so the was much pushback on the linux side that the VMs nee= d be fixed. I don't see any published work arounds and I'd rather not leave screens run= ning the console of machines ... so ... --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-229188-227>