Bug 172048

Summary: hwclock sets wrong time, not fully functional if SELinux is enabled
Product: [Fedora] Fedora Reporter: Michel Alexandre Salim <michel.salim>
Component: selinux-policy-targetedAssignee: Daniel Walsh <dwalsh>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4   
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-10-30 03:32:29 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 Michel Alexandre Salim 2005-10-29 21:39:36 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7

Description of problem:
The hardware clock on my computer is set to local time, (Indianapolis, UTC-5); however, when booting into Fedora with SELinux enabled the clock is always set back 5 hours.

Running hwclock from the command line, it just returns without printing anything - -h does not work, --show does not work; currently working around it by just disabling SELinux.

This only happens with no_timer_check and/or no_apic added to my kernel boot parameters, but unfortunately I need at least the first (to stop clock drift).

Version-Release number of selected component (if applicable):
selinux-policy-targeted-1.27.1-2.6, util-linux-2.12p-9.12

How reproducible:
Always

Steps to Reproduce:
1. Enable SELinux, policy=targeted
2. Add no_timer_check and no_apic to kernel boot parameters
3. Boot
  

Actual Results:  Clock set as if the hardware clock is UTC; hwclock not functional from command line

Expected Results:  Clock should match hardware clock, hwclock should be working if used by the root user

Additional info:

HP Special Edition L2000, AMD Turion 64, no_timer_check, no_apic

Comment 1 Michel Alexandre Salim 2005-10-29 21:59:56 UTC
no_apic is the culprit. Is this perhaps more of a bug in hwclock than in
selinux-policy-targeted? Without SELinux, hwclock works fine even if APIC is
disabled. From this error message in the kernel log it seems like a good thing
to disable APIC anyway, on this machine:

..MP-BIOS bug: 8254 timer not connected to IO-APIC
timer doesn't work through the IO-APIC - disabling NMI Watchdog!
Using local APIC timer interrupts.


Comment 2 Michel Alexandre Salim 2005-10-30 03:32:29 UTC
Found the problem - during a yum update, for some reason selinux-policy-targeted
was removed, and the filesystem was not properly relabeled.