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
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.
johannes
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
On Mon, 2010-08-30 at 21:08 +0200, Francisco Jerez wrote:
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.
Can you identify a fix that I can cherry-pick until (hopefully) -rc4?
johannes
Johannes Berg johannes@sipsolutions.net writes:
On Mon, 2010-08-30 at 21:08 +0200, Francisco Jerez wrote:
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.
Can you identify a fix that I can cherry-pick until (hopefully) -rc4?
Sure, try 5a5608adff833bad37c56278b6194c5b0a5b36bf.
johannes
On Mon, 2010-08-30 at 21:33 +0200, Francisco Jerez wrote:
Johannes Berg johannes@sipsolutions.net writes:
On Mon, 2010-08-30 at 21:08 +0200, Francisco Jerez wrote:
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.
Can you identify a fix that I can cherry-pick until (hopefully) -rc4?
Sure, try 5a5608adff833bad37c56278b6194c5b0a5b36bf.
An actual url would help ... What is "the nouveau kernel tree"?
johannes
Johannes Berg johannes@sipsolutions.net writes:
On Mon, 2010-08-30 at 21:33 +0200, Francisco Jerez wrote:
Johannes Berg johannes@sipsolutions.net writes:
On Mon, 2010-08-30 at 21:08 +0200, Francisco Jerez wrote:
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.
Can you identify a fix that I can cherry-pick until (hopefully) -rc4?
Sure, try 5a5608adff833bad37c56278b6194c5b0a5b36bf.
An actual url would help ... What is "the nouveau kernel tree"?
Ah sorry, git://anongit.freedesktop.org/nouveau/linux-2.6.
johannes
On Mon, 2010-08-30 at 21:55 +0200, Francisco Jerez wrote:
Johannes Berg johannes@sipsolutions.net writes:
On Mon, 2010-08-30 at 21:33 +0200, Francisco Jerez wrote:
Johannes Berg johannes@sipsolutions.net writes:
On Mon, 2010-08-30 at 21:08 +0200, Francisco Jerez wrote:
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.
Can you identify a fix that I can cherry-pick until (hopefully) -rc4?
Sure, try 5a5608adff833bad37c56278b6194c5b0a5b36bf.
An actual url would help ... What is "the nouveau kernel tree"?
Ah sorry, git://anongit.freedesktop.org/nouveau/linux-2.6.
Ah, freedesktop, was looking on git.kernel.org. Thanks, I'll install the kernel now and let you know how it fares when I boot it in the morning.
johannes
On Mon, 2010-08-30 at 21:54 +0200, Johannes Berg wrote:
Sure, try 5a5608adff833bad37c56278b6194c5b0a5b36bf.
An actual url would help ... What is "the nouveau kernel tree"?
Ah sorry, git://anongit.freedesktop.org/nouveau/linux-2.6.
Ah, freedesktop, was looking on git.kernel.org. Thanks, I'll install the kernel now and let you know how it fares when I boot it in the morning.
Seems to have fixed the problem, I've been running with this for the past couple of hours without any problems.
Thanks!
johannes
dri-devel@lists.freedesktop.org
-
Francisco Jerez -
Johannes Berg