Bug 465123 - inconsistent lock state going to init 5
inconsistent lock state going to init 5
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
rawhide
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-10-01 13:32 EDT by John Reiser
Modified: 2008-10-27 13:03 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-10-27 13:03:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
"INFO: inconsistent lock state" via dmesg (4.13 KB, text/plain)
2008-10-01 13:32 EDT, John Reiser
no flags Details

  None (edit)
Description John Reiser 2008-10-01 13:32:00 EDT
Created attachment 319132 [details]
"INFO: inconsistent lock state" via dmesg

Description of problem:Booting to init state 5 (multiuser with X11) fails with a console message.  Only text login comes up; X11 login does not.  Logging in as root, then "telinit 5" does bring up X11.


Version-Release number of selected component (if applicable):
kernel-PAE-2.6.27-0.370.rc8.fc10.i686

How reproducible: always


Steps to Reproduce:
1. normal boot to init state 5
2.
3.
  
Actual results: Console message "INFO: inconsistent lock state" with many following lines of info (will be attached), "login: " left on text console, X11 greeter not active.


Expected results: X11 greeter active.


Additional info:
Comment 1 Dave Jones 2008-10-27 13:03:43 EDT
this should be fixed by commit f382a0a8e9403c6d7f8b2cfa21e41fefb5d0c9bd upstream, which is backported in the latest -stable which F10 will be based off.

Note You need to log in before you can comment on or make changes to this bug.