From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 56202] New: [regression][kms] Clock rework causes kms boot regression for NV4E (v3.7-rc1, 3.6+nouveau)
Date: Fri, 19 Oct 2012 20:21:18 +0000 [thread overview]
Message-ID: <bug-56202-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2757 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=56202
Priority: medium
Bug ID: 56202
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Summary: [regression][kms] Clock rework causes kms boot
regression for NV4E (v3.7-rc1, 3.6+nouveau)
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: ronald645-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Driver/nouveau
Product: xorg
Created attachment 68815
--> https://bugs.freedesktop.org/attachment.cgi?id=68815&action=edit
v3.6.0+ @ the commit that caused the regression
The following commit causes KMS initialisation to result in a scrambled screen
with mostly blue elements. The screen responds to changes based on actual
content (e.g. system booting, lightdm starting).
drm/nouveau/clock: pull in the implementation from all over the place
I have tested and verified this regression on a 3.6 tree and the recent v3.7
tree pulled from git.kernel.org.
Below you will find some more data about my VGA card.
Attached you will find two dmesg output logs (don't know if they differ):
both are from the v3.7-rc1 tree (they are noted as 3.6.0+ in the logs)
dmesg-good.txt @ the commit before the one that caused the regression
dmesg-bad.txt @ the commit that caused the regression
00:05.0 0300: 10de:0244 (rev a2) (prog-if 00 [VGA controller])
Subsystem: 103c:30b7
00:05.0 VGA compatible controller: NVIDIA Corporation C51 [GeForce Go 6150]
(rev a2) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Presario V6133CL
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 18
Region 0: Memory at b2000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at c0000000 (64-bit, prefetchable) [size=256M]
Region 3: Memory at b1000000 (64-bit, non-prefetchable) [size=16M]
[virtual] Expansion ROM at 40000000 [disabled] [size=128K]
Capabilities: [48] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Kernel driver in use: nouveau
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4289 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2012-10-19 20:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 20:21 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-56202-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2012-10-19 20:22 ` [Bug 56202] [regression][kms] Clock rework causes kms boot regression for NV4E (v3.7-rc1, 3.6+nouveau) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-20 7:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-20 7:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-20 8:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-20 9:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-22 4:16 ` 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-56202-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.