From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 88868] PowerPC e5500, kernel crash, GT520, GT610
Date: Thu, 29 Jan 2015 16:32:55 +0000 [thread overview]
Message-ID: <bug-88868-8800-RXdWScKpDx@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-88868-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1189 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=88868
--- Comment #7 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
OK, so this is (part of) your problem:
nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0xa1a0900d
nouveau [ DEVICE][0000:01:00.0] Chipset: nForce (NV1A)
nouveau [ DEVICE][0000:01:00.0] Family : NV10
Once this happens, nothing will work. The boot0 seems swapped, it should read
back 0x0d90a0a1, which would be a NVD9 (GF119) which is a very reasonable
chipset for a GT610 or GT520 to report. [Unlike NV1A which is a GeForce2 IGP
from ~2003 or so.]
Normally we kick the card into the proper LE/BE mode (which byteswaps all the
register reads/writes at the hw level), but perhaps that's not working for some
reason? I assume this is a BE box, and there's not a whole lot of testing that
goes on (esp for newer cards) on BE. Another thing to note is that nouveau
requires 4K pages (not for any great reason, but there's a lot of confusion
inside the driver regarding whether system or gpu pages are being used, and
PAGE_SHIFT/SIZE aren't universally used in the right places).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1911 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2015-01-29 16:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 15:06 [Bug 88868] New: PowerPC e5500, kernel crash, GT520, GT610 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-88868-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-01-29 15:12 ` [Bug 88868] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-29 15:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-29 15:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-29 15:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-29 15:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-29 15:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-29 16:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2015-01-29 19:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-29 22:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-30 1:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-30 1:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-30 9:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-30 9:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-30 9:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-30 10:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-01 22:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-01 22:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-02 10:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-02 10:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-02 12:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-03 16:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-03 23:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-04 9:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-05 15:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-05 15:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-05 15:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-05 16:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 8:55 ` 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-88868-8800-RXdWScKpDx@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.