Bug 439323
| Summary: | serial console broken | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dave Jones <davej> |
| Component: | upstart | Assignee: | Casey Dahlin <cdahlin> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | rawhide | CC: | dwalsh, notting, pfrields, vanhoof |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-03-29 12:21:06 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
Dave Jones
2008-03-28 02:06:57 UTC
Jeremy mentioned that this may be more likely to be upstart. I'm inclined to believe him. Is a getty running on the box? 2138 tty4 Ss+ 0:00 /sbin/mingetty tty4 2139 tty5 Ss+ 0:00 /sbin/mingetty tty5 2140 tty2 Ss+ 0:00 /sbin/mingetty tty2 2141 tty3 Ss+ 0:00 /sbin/mingetty tty3 2142 tty1 Ss+ 0:00 /sbin/mingetty tty1 2143 tty6 Ss+ 0:00 /sbin/mingetty tty6 If I boot with just 'console=ttyS0' I see boot messages. I can then log in etc over serial, that all works. kernel printk's still don't appear. If I do what I usually do... 'console=ttyS0 console=tty0' I see boot messages on both the screen, and over serial. Until the initscripts start, and then nothing until shutdown. That's weird, that almost sounds like a kernel bug. If I got no messages over serial during bootup/shutdown, I'd have looked there first, but 'something' seems to be diddling 'something else' at some point, which makes stuff stop working. debugged this a little further with notting on irc. if I replace /sbin/init with one from f8, everything works as expected, so this is definitely an upstart problem, but why is a mystery. ok, now I'm even more confused.
to test the f8 /sbin/init, I had to boot with selinux=off, because..
<notting> davej: we switched to loading the policy in the initramfs to be more
sane. unfortunately, the old init code was 'policy already loaded? wtf? I CAN'T
HANDLE THIS!'
After testing the f8 /sbin/init, I switched things back to the regular f9
upstart /sbin/init, rebooted, and was really confused when things worked.
Then I noticed I still had selinux=off in my boot flags.
It turns out that's the key. With selinux enabled, I don't see output. With it
disabled, I do. But it has to be 'selinux=off', just running 'setenforce 0'
doesn't cut it.
Perhaps I was right the first time, and this is a consolekit problem.. I see
this in the audit log..
type=USER_AVC msg=audit(1206734217.347:22): user pid=1845 uid=81 auid=4294967295
subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc: denied {
send_msg } for msgtype=method_call interface=org.freedesktop.ConsoleKit.Manager
member=OpenSessionWithParameters dest=org.freedesktop.ConsoleKit spid=1063
tpid=1950 scontext=system_u:system_r:initrc_t:s0
tcontext=system_u:system_r:consolekit_t:s0-s0:c0.c1023 tclass=dbus :
exe="/bin/dbus-daemon" (sauid=81, hostname=?, addr=?, terminal=?)'
I can add this, but what script executable is talking dbus to consolekit? It should have a policy for it. Well I added this allow to selinux-policy-3.3.1-26.fc9 I'm confused. Something futzing with dbus to CK shouldn't affect kernel messages to the console. |