From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 20341] [NV31] lockup when using AGP. agpmode=0 fixes it.
Date: Sun, 25 Aug 2013 15:09:36 +0000 [thread overview]
Message-ID: <bug-20341-8800-UkBNe5Dt8w@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-20341-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1253 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=20341
--- Comment #21 from mypersonalmailbox1-O5WfVfzUwx8@public.gmane.org ---
Hi,
I believe VIA Technologies KT133's AGP may be the culprit.
http://us.download.nvidia.com/XFree86/Linux-x86/173.14.09/README/chapter-12.html
KT133's (VT8363) AGP is likely to be generationally be closer to Apollo Pro133A
(VT82C694X) and KX133 (VT8371).
KT133 and KX133 are fairly similar with KT133 correctly supporting AMD Socket
A.
KX133 supposedly did not implement a certain type of I/O buffer for EV6 bus to
support Socket A, and as a result, it will not be able to support Socket A.
Of course, that issue is not related to AGP, but since KT133 came out fairly
quickly after the EV6 bus issue was acknowledged, it is probably a minor
updated version of KX133.
Nouveau may have to add special code to detect the chipset, and if it detects
certain known VIA Technologies chipsets, it should turn off AGP 4X mode (i.e.,
run at 2X mode).
I do not know if VIA Technologies really fixed the AGP for these chipsets, or
perhaps they fixed it with their newer chipsets.
I hope this information adds to the discussion.
Regards,
fpgahardwareengineer
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2118 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 prev parent reply other threads:[~2013-08-25 15:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 1:51 [Bug 20341] New: NV31 lockup bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-20341-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2009-02-27 1:51 ` [Bug 20341] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-27 1:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-03-18 3:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-03-18 4:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-03-18 4:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-03-19 4:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-03-19 17:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-03-20 4:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-13 7:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-08-15 4:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-10-17 15:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-18 18:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-23 5:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-23 8:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-23 15:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 3:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 4:04 ` [Bug 20341] [NV31] lockup when using AGP. agpmode=0 fixes it bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 4:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 4:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 4:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-25 15:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2013-08-25 15:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-26 23:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-27 5:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-19 15:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-21 1:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-05 7:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-09 0:23 ` 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-20341-8800-UkBNe5Dt8w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox