All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francisco Jerez <currojerez@riseup.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Ben Skeggs <bskeggs@redhat.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: nouveau X lockup on 36-rc (regression from 2.6.35)
Date: Mon, 30 Aug 2010 21:08:49 +0200	[thread overview]
Message-ID: <87sk1v535q.fsf@riseup.net> (raw)
In-Reply-To: <1283185822.3694.1.camel@jlt3.sipsolutions.net> (Johannes Berg's message of "Mon, 30 Aug 2010 18:30:22 +0200")


[-- Attachment #1.1.1: Type: text/plain, Size: 1182 bytes --]

Johannes Berg <johannes@sipsolutions.net> writes:

> On Wed, 2010-08-25 at 15:55 +0200, Johannes Berg wrote:
>> 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.
>
> This problem persists in -rc3, where I'd hoped the nouveau changes would
> actually fix it :-( In fact, it seems I was either "lucky" or it was
> made easier to trigger, this time it already happened during my login.
>
That's already fixed in the nouveau kernel tree.

> johannes

[-- Attachment #1.2: Type: application/pgp-signature, Size: 229 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2010-08-30 19:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-25 13:55 nouveau X lockup on 36-rc (regression from 2.6.35) Johannes Berg
2010-08-30 16:30 ` Johannes Berg
2010-08-30 19:08   ` Francisco Jerez [this message]
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=87sk1v535q.fsf@riseup.net \
    --to=currojerez@riseup.net \
    --cc=bskeggs@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=johannes@sipsolutions.net \
    --cc=rjw@sisk.pl \
    /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.