From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 69928] New: [NVAA] Boot of linux kernel 3.12-rc2 hangs
Date: Sun, 29 Sep 2013 13:23:25 +0000 [thread overview]
Message-ID: <bug-69928-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1401 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=69928
Priority: medium
Bug ID: 69928
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Summary: [NVAA] Boot of linux kernel 3.12-rc2 hangs
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: dirkneukirchen-S0/GAf8tV78@public.gmane.org
Hardware: x86 (IA32)
Status: NEW
Version: unspecified
Component: Driver/nouveau
Product: xorg
Created attachment 86798
--> https://bugs.freedesktop.org/attachment.cgi?id=86798&action=edit
3.12-rc2 fails to boot with NVAA
Steps to reproduce:
- Compiling Kernel 3.12-rc2
- boot
- boot hangs at black screen/no signal
System:
- NVAA onboard (Jetway JNC62K)
- Linux Mint 15 (Ubuntu 13.04)
No error with 3.11.0 Kernel.
I compiled kernel 3.12-rc2 once as a dpkg and once with vanilla methods (make
install). Both same behaviour.
Attached are a netconsole log of 3.12-rc2 and a dmesg of a "working" 3.11.0
Example error message of 3.12-rc2:
[ 22.081905] nouveau E[ PFB][0000:02:00.0] trapped write at 0x01002b75b4
on channel 0x00007ee0 [unknown] BAR/PFIFO_WRITE/IN reason: PAGE_NOT_PRESENT
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2858 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:[~2013-09-29 13:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-29 13:23 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-69928-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-09-29 13:24 ` [Bug 69928] [NVAA] Boot of linux kernel 3.12-rc2 hangs bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-29 15:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-29 19:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-01 17:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-11 22:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-14 23:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-15 16:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-15 17:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-15 21:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-16 8:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-16 8:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-16 15:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-20 13:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-20 13:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-20 14:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-09 20:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-25 12:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-18 20:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22 4: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-69928-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.