Bug 577120
Summary: | possible circular locking dependency in nouveau with 2.6.33 and kms disabled | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Arenas Belon, Carlo Marcelo <carenas> |
Component: | xorg-x11-drv-nouveau | Assignee: | Ben Skeggs <bskeggs> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 13 | CC: | airlied, ajax, awilliam, bskeggs |
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: | 2010-04-12 17:47:26 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
Arenas Belon, Carlo Marcelo
2010-03-26 08:40:36 UTC
also failing if using KMS with 2.6.33.1 (2.6.33.1-19.fc13.i686) that fixed my plymouth problem. So you get the same failure with graphical plymouth and KMS, in current F13? What's the actual functional issue here ('possible circular locking dependency' doesn't always cause any real problems...)? Thanks. (In reply to comment #2) > So you get the same failure with graphical plymouth and KMS, in current F13? Yes > What's the actual functional issue here ('possible circular locking dependency' > doesn't always cause any real problems...)? I have no functional issue, but my use of the system is limited (don't even have 3D acceleration configured and it fails to work if I do, but unsure is it is related) 3D failing to work is likely a different issue and not too important anyway (we don't guarantee anything wrt 3D yet). This looks like a dupe of 572220 to me; please un-dupe if I'm wrong, Ben. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers *** This bug has been marked as a duplicate of bug 572220 *** |