From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 85444] New: [NV46] Heavy corruption, no hardfreeze, back to console and libexa.so segfault
Date: Sat, 25 Oct 2014 14:50:54 +0000 [thread overview]
Message-ID: <bug-85444-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2032 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=85444
Bug ID: 85444
Summary: [NV46] Heavy corruption, no hardfreeze, back to
console and libexa.so segfault
Product: xorg
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: jesus.guerrero.botella-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created attachment 108396
--> https://bugs.freedesktop.org/attachment.cgi?id=108396&action=edit
Screenshot
Hello.
I am trying to use the nouveau driver in an Aspire 9420, which is shipped with
a go7300 nvidia card. The lspci line is this:
01:00.0 VGA compatible controller: NVIDIA Corporation G72M [Quadro NVS
110M/GeForce Go 7300] (rev a1)
I am using the following software:
* gentoo x86_64
* kernel 3.17.1 from kernel.org, no patches
* no fb driver enabled, other than what the nouveau drm stack enables
automatically as deps
* no compositor, no xorg.conf
* libdrm, xf86-video-nouveau and mesa from git as of today (oct 25, 2014)
* xorg-server 1.16.1
When I boot my machine I can see the fb coming up, and the mode is set ok (with
tiny characters and such). When startx takes into scene, then the screen
becomes a pile of garbage. The laptop is not hard-frozen however. Most times,
after like a minute or two I am taken back to the console (not always though).
In any case, the computer is responsive. I can control+alt+del it even when the
console remains garbled. Because of this, I was able to easily save the X log
and the dmesg output, which I attach along with a photo of the corrupted
screen.
I have tried rebuilding everything many times, in the hope that any ABI issues
went away, but no change.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3369 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:[~2014-10-25 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 14:50 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-85444-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-10-25 14:51 ` [Bug 85444] [NV46] Heavy corruption, no hardfreeze, back to console and libexa.so segfault bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-25 14:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-25 14:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-28 12:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 8:50 ` 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-85444-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.