From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 39980] freezing nouveau
Date: Wed, 10 Aug 2011 11:53:54 -0700 (PDT) [thread overview]
Message-ID: <20110810185354.DF679130193@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-39980-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=39980
--- Comment #3 from Christoph Anton Mitterer <calestyo-Jy7UQHNrZ9Pk1uMJSBkQmQ@public.gmane.org> 2011-08-10 11:53:54 PDT ---
Hi.
>Would you mind removing the following package in order to
>establish if it's related/triggers the issue
>libgl1-mesa-dri-experimental
I feared you'd ask this ^^...
Well I can give it a try, of course I'll loose compiz, which I'm particularly
used to... might very well happen that it doesn't happen without this.
>For future reference would you mind attaching the whole log (dmesg)
>rather than pasting fragments of it in the report
ok,.. that was just a huge mess... and apart for the usual log messages
detection the card/etc. there was not DRI related output at all.
I just hat the same(?) issue on a nother machine, with basically the same
software config but a G94 (Geforce 9600 GT) with two monitors attached.
But this time,.. no output to the logs at all. Neither xorg.log, nor kernel
log.
And even the SysRq messages made it into the syslog before the system rebooted.
This particular system shows also a very easily reproducable bug, but I'll
report that in a spearate bug report.
>Can you please take a look at our Bugs [1] and FAQ [2]
>section to eliminite one of the most common root cause
I've actually read them,.. but honestly,... some things you suggest there are
rather "difficult" (and I've studied computer science) for end users to do...
especially using git head for everything is quite an effort, especially when
you want to keep rather in sync with your distro.
Cheers,
Chris.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-08-10 18:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 13:44 [Bug 39980] New: freezing nouveau bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-39980-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-08-10 13:47 ` [Bug 39980] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-10 18:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-10 18:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2011-08-10 18:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-03-27 2:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-03-27 2:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-04-25 13:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-06 22:04 ` [Bug 39980] [NV86] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-08 17:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-14 1:38 ` 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=20110810185354.DF679130193@annarchy.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