All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Skeggs <bskeggs@redhat.com>, Francisco Jerez <currojerez@riseup.net>
Cc: dri-devel@lists.freedesktop.org
Subject: nouveau X lockup on 36-rc (regression from 2.6.35)
Date: Wed, 25 Aug 2010 15:55:06 +0200	[thread overview]
Message-ID: <1282744506.3667.4.camel@jlt3.sipsolutions.net> (raw)

Since 2.6.36-rc kernels (both rc1 and rc2) I've had X lockups where X
sits in a loop just using CPU.

The only kernel message I got this time was this one:

[22290.792075] [drm] nouveau 0000:02:00.0: PFIFO_DMA_PUSHER - Ch 2

stracing X just repeats, in a loop,

ioctl(9, 0x40086482, 0x7fff6a873af0)    = ? ERESTARTSYS (To be restarted)
--- SIGALRM (Alarm clock) @ 0 (0) ---
rt_sigreturn(0xe)                       = -1 EINTR (Interrupted system call)


so apparently that ioctl never returns.

This has never happened on 2.6.35, and I've gone back now. Large screen
updates seem to trigger it more likely, but I haven't found a way to
really reproduce it. FWIW, I'm running with two screens connected.

johannes

             reply	other threads:[~2010-08-25 14:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-25 13:55 Johannes Berg [this message]
2010-08-30 16:30 ` nouveau X lockup on 36-rc (regression from 2.6.35) Johannes Berg
2010-08-30 19:08   ` Francisco Jerez
2010-08-30 19:13     ` Johannes Berg
2010-08-30 19:33       ` Francisco Jerez
2010-08-30 19:27         ` Johannes Berg
2010-08-30 19:55           ` Francisco Jerez
2010-08-30 19:54             ` Johannes Berg
2010-08-31  9:27               ` Johannes Berg

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=1282744506.3667.4.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=bskeggs@redhat.com \
    --cc=currojerez@riseup.net \
    --cc=dri-devel@lists.freedesktop.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.