From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 96836] New: Kernel unaligned access at TPC[105d9fb4] nvkm_instobj_wr32+0x14/0x20 [nouveau]
Date: Thu, 07 Jul 2016 02:23:25 +0000 [thread overview]
Message-ID: <bug-96836-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1441 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=96836
Bug ID: 96836
Summary: Kernel unaligned access at TPC[105d9fb4]
nvkm_instobj_wr32+0x14/0x20 [nouveau]
Product: xorg
Version: unspecified
Hardware: SPARC
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: ciaran.gillespie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
When attempting to use Nouveau driver with Xorg on my SunBlade 2500 running the
latested build from Debian-9.0 Sid SPARC64 CPU 0 runs up to 100% and then
eventually the Xorg session shuts down. It appears that it's timing out on a
GPU lock. A bunch of messages appears in the Xorg.0.log indicating fifo:
CACH_ERROR also with in the messages log there are several repeating errors.
log_unaligned: 598 callbacks suppressed
Kernel unaligned access at TPC[105d9fb4] nvkm_instobj_wr32+0x14/0x20 [nouveau]
Eventually the Xorg session gives up and times out.
I'll try and attach some more logs but it appears to have something to do with
the iowrite32_native macro on SPARC V9 systems.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2737 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2016-07-07 2:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 2:23 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-96836-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2016-07-07 2:51 ` [Bug 96836] Kernel unaligned access at TPC[105d9fb4] nvkm_instobj_wr32+0x14/0x20 [nouveau] bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-08 23:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-08 23:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-10 2:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-10 2:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-10 2:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-10 2:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-10 2:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-10 2:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-10 2:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-10 2:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-10 2:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-10 2:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-10 2:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-10 3:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-10 3:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-10 4:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-27 23:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:15 ` 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-96836-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.