Red Hat Bugzilla – Bug 601674
[abrt] crash in mingetty-1.08-4.1.el6: Process /sbin/mingetty was killed by signal 3 (SIGQUIT)
Last modified: 2015-11-23 09:42:14 EST
abrt 1.0.7 detected a crash.
Attached file: backtrace
cmdline: /sbin/mingetty --noclear /dev/tty6
comment: The only thing that springs to mind is that I have added "--noclear" option to init's tty startup script, but I doubt that's the cause.
reason: Process /sbin/mingetty was killed by signal 3 (SIGQUIT)
release: Red Hat Enterprise Linux release 6.0 Beta (Santiago)
How to reproduce: No manual intervention, this runs from init.
Created attachment 422178 [details]
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
As there is no clear reproducer and nothing obvious in the backtrace/related sourcecode, there is not much to do with it at the moment. Please add some hints how to reproduce it (if you still experience the issue, maybe some configuration details could help).
It appears to be related to this bug, the two problems always arise together:
I guess this will be somehow related to configuration of /dev/ttyN devices.
Not sure. I'll put RHEL6b on another machine in the next few days and check if it is reproducible there. I suspect it will be, because I had a similar symptom (extreme Xorg CPU usage) on another machine previously. Unfortunately, I repurposed it before I could get to the bottom of what was causing it.
Mingetty dies on SIGQUIT. There is no such signal emitted by mingetty. Mingetty ignores SIGHUP while opening TTY only. The signal has been received in read(0,...) while reading log-in name.
I guess somebody kills (by SIGQUIT) mingetty from outside. init or kdm via ConsoleKit probably.
Default action assigned to SIGQUIT is to core dump that triggers abrt. I can change the code to terminate in other way not to provoke abrt. However better way would be if culprit sent SIGTERM instead of SIGQUIT.
I'm reasonably confident that this is actually the same issue as this one:
which would make it a KDM bug, and a serious one.
Unfortunately, the linked bug was downgraded to low priority even though it makes KDE completely unusable on a single-core machine, not to mention that it also makes it completely unusable on any laptop where non-mains powered operation is required. (100% CPU usage all the time is not good for battery life)
KDM clashes with mingetty over which terminals it runs on because it for some reason ignores the settings regarding which terminal X should run on.
Development Management has reviewed and declined this request. You may appeal
this decision by reopening this request.
Due to a bug in the ABRT reporting tool, this bug report may have contained information that you did not intend to include. As a precaution, we have made the bug report private. You may wish to review the bug report in an effort to identify information that you inadvertently included in the bug report and take appropriate remedial action.
I could not find any sensitive data specific for the host or an user. Thus I'm making the report public again.