From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 25762] New: Quadro NVS 140M doesn't wake up anymore
Date: Tue, 22 Dec 2009 12:21:32 -0800 (PST) [thread overview]
Message-ID: <bug-25762-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=25762
Summary: Quadro NVS 140M doesn't wake up anymore
Product: xorg
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: martin.peres-Iz16wY1oaNPLSKGbIzaifA@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Hi,
My laptop (featuring a Quadro NVS 140M) doesn't wake up after a suspend to ram.
This used to work two months ago but hasn't been working for the last month.
Today, I decided to track the problem a bit and this is what I got when
resuming :
[drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 0
[drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 0
[drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 0
[drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 0
....
My dmesg is full of this message and then shows
....
[drm] nouveau 0000:01:00.0: PFIFO still angry after 101 spins, halt
This happens with drm-next or with a stock kernel 2.6.32 with drm from
http://people.freedesktop.org/~pq/nouveau-drm/master.tar.gz.
Do you guys have any idea on what's going on ?
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2009-12-22 20:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 20:21 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-25762-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2010-01-22 8:12 ` [Bug 25762] Quadro NVS 140M doesn't wake up anymore bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-24 21:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-24 22:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-03-25 9:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-12-05 17:58 ` 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-25762-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.