From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 34430] New: nouveau driver does not return VGA connector status breaking upower
Date: Fri, 18 Feb 2011 01:25:45 -0800 (PST) [thread overview]
Message-ID: <bug-34430-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=34430
Summary: nouveau driver does not return VGA connector status
breaking upower
Product: xorg
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: nuada-hjuaS3B0pPfVItvQsEIGlw@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
My laptop (Asus UL80VT) has hybrid graphics: intel+nvidia. After switching
nvidia card off using vgaswitcheroo, upower CPU consumption goes to 100%. If
nvidia card is switched back on, problem dissapeares.
This is caused by nouveau driver not returning VGA connector status properly.
When upowerd tries to read status of all connectors, it hangs waiting for VGA.
Gentoo Linux
kernel: 2.6.38-rc*
xorg-server: 1.9.4
upower: 0.9.8
KDE: 4.6.0
Steps to reproduce:
1. Log in to KDE
2. switch off nvidia:
echo OFF > /sys/kernel/debug/vgaswitcheroo/switch
3. cannot read VGA connector status:
cat
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card1/card1-VGA-1/status
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-02-18 9:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 9:25 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-34430-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2012-09-22 6:46 ` [Bug 34430] nouveau driver does not return VGA connector status breaking upower bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-15 18:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-27 16:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-27 16:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-17 0:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 8:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-34430-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.