All of lore.kernel.org
 help / color / mirror / Atom feed
From: rm.riches-BRax14MUi1YI9MI5TlNUSA@public.gmane.org (Robert M. Riches Jr.)
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: message before driver went out to lunch
Date: Tue, 23 Oct 2012 17:41:37 -0700	[thread overview]
Message-ID: <20121024004137.C6B1E26756@one.localnet> (raw)

Caught a message in /var/log/messages about the time Nouveau went
out to lunch:

Oct 22 19:40:12 one kernel: [drm] nouveau 0000:06:00.0: EvoCh 0 Mthd 0x0000 Data 0x00000400 (0x1002 0x01)

This was with kernel 2.6.38.8-server-10.mga on Mageia 1, and I
don't see any other version number in modinfo output.  The
graphics card is an Asus ENGT430.  Motherboard is an Asus P6T6 WS
Revolution.  CPU is a Xeon W3680.

At about the time this message was written, the system had been
driving two monitors.  A number of Firefox and other assorted
windows were on the first monitor, and Mythfrontend was playing
on the second (hanging a few pixels into the first due to a
separate X issue).  The first symptom was the mouse cursor
disappeared.  Window focus and such was perfectly fine, but the
cursor was not visible.  Then, in a minute or two, the cursor got
trapped on the second monitor.  A little later, the whole display
basically locked up.  Reloading the module, logging back in, and
starting X again cleared it up.

Does that message tell anything that might help reduce the
frequency of the display going out to lunch, requiring a reload
of the Nouveau module?

Thanks,

Robert

                 reply	other threads:[~2012-10-24  0:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20121024004137.C6B1E26756@one.localnet \
    --to=rm.riches-brax14mui1yi9mi5tlnusa@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.