Bug 660727

Summary: 'serial8250: too much work for irq4', in kvm instance with ttyS0+tty0 console
Product: [Fedora] Fedora Reporter: Frank Ch. Eigler <fche>
Component: plymouthAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 14CC: fedora, rankincj, rstrode, thomasj
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: plymouth-0.8.4-0.20100823.7.fc14 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-12 20:04:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Frank Ch. Eigler 2010-12-07 17:05:46 UTC 
Running under kvm, a rawhide 64-bit instance spews trash into a serial
console, and error messages onto its normal console, if its grub.conf
includes   console=ttyS0,115200 console=tty0   as is an established way
of duplicating the console traffic to a serial line.  (That serial line
is in turn saved by kvm to a host file.)

The main console gets a steady stream of messages of the form:
[   22.932140] serial8250: too much work for irq4
with very little actual progress.  On the serial console, one gets
a flood of control characters and goo, intermingled with the actual
content:

[    2.252634] udev[109]: starting version 164
[    2.328922] udevadm used greatest stack depth: 5168 bytes left
[    2.485948] dracut: Starting plymouth daemon
[    2.509552] console_init[132]: Failed to open tty0: No such file or directory
Failed to open syslog for logging: No such file or directory^M
Failed to open syslog for logging: No such file or directory^M^M
Failed to open syslog for logging: No such file or directory^M^M^M
Failed to open syslog for logging: No such file or directory^M^M^M^M

... and from there, ^M's propagate into a soul-crushing river of invisible
evil, snuffing out any vitality in the system, and spamming the serial console
logs while at it.

rstrode advises it might be an off-by-one bug in plymouth ply_logger_flush_buffer.

kernel 2.6.35-1.fc15.x86_64
plymouth 0.8.4-0.20101119.2.fc15.x86_64
systemd 15-1.fc15.x86_64

Maybe see also bug #501026.
Comment 1 Frank Ch. Eigler 2010-12-07 17:29:16 UTC 
It was not enough to update plymouth/systemd to get the already-fixed code,
/usr/libexec/plymouth/plymouth-update-initrd rebuilt /boot/initramfs* with
it, and it now works.  Installing a new kernel should also make it work.

Moving to f14 on halfline's request, where this isn't fixed yet.
Comment 2 Fedora Update System 2010-12-07 17:56:31 UTC 
plymouth-0.8.4-0.20100823.7.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/plymouth-0.8.4-0.20100823.7.fc14
Comment 3 Fedora Update System 2010-12-08 21:38:42 UTC 
plymouth-0.8.4-0.20100823.7.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update plymouth'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/plymouth-0.8.4-0.20100823.7.fc14
Comment 4 Fedora Update System 2010-12-12 20:04:31 UTC 
plymouth-0.8.4-0.20100823.7.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 5 Chris Rankin 2010-12-20 09:17:37 UTC 
*** Bug 661552 has been marked as a duplicate of this bug. ***