From: Andy Furniss <andyqos@ukfsn.org>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: KH <greg@kroah.com>, LKML <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org, Greg@freedesktop.org,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: Revert 737a3bb9416ce2a7c7a4170852473a4fcc9c67e8 ?
Date: Wed, 13 Apr 2011 21:01:42 +0100 [thread overview]
Message-ID: <4DA60126.6030003@ukfsn.org> (raw)
In-Reply-To: <1302704124.15520.72.camel@thor.local>
Michel Dänzer wrote:
>>> That does sound like the GPU locks up. Do you get any messages in dmesg
>>> about lockups and attempts to reset the GPU at any time?
>>
>> No.
>
> Hmm, I guess the constant SIGALRMs might prevent the lockup detection
> from kicking in... Maybe you can try starting the X server with
> -dumbSched to see if that gets things along any further, but in the end
> there's probably no way around figuring out what causes the lockup and
> fixing that anyway.
I have an old AGP box that locks with 600g + agpgart - It used to give
GPU lockup to dmesg/log, but (I only test it occasionally) it doesn't
anymore. I can still sysrq OK.
I wonder if something changed in recent months in the drm/whatever code
that has changed/blocked the logging.
WARNING: multiple messages have this Message-ID (diff)
From: Andy Furniss <andyqos@ukfsn.org>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: "Gabriel Paubert" <paubert@iram.es>, KH <greg@kroah.com>,
linuxppc-dev@lists.ozlabs.org, dri-devel@lists.freedesktop.org,
LKML <linux-kernel@vger.kernel.org>,
Greg@freedesktop.org,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: Revert 737a3bb9416ce2a7c7a4170852473a4fcc9c67e8 ?
Date: Wed, 13 Apr 2011 21:01:42 +0100 [thread overview]
Message-ID: <4DA60126.6030003@ukfsn.org> (raw)
In-Reply-To: <1302704124.15520.72.camel@thor.local>
Michel Dänzer wrote:
>>> That does sound like the GPU locks up. Do you get any messages in dmesg
>>> about lockups and attempts to reset the GPU at any time?
>>
>> No.
>
> Hmm, I guess the constant SIGALRMs might prevent the lockup detection
> from kicking in... Maybe you can try starting the X server with
> -dumbSched to see if that gets things along any further, but in the end
> there's probably no way around figuring out what causes the lockup and
> fixing that anyway.
I have an old AGP box that locks with 600g + agpgart - It used to give
GPU lockup to dmesg/log, but (I only test it occasionally) it doesn't
anymore. I can still sysrq OK.
I wonder if something changed in recent months in the drm/whatever code
that has changed/blocked the logging.
next prev parent reply other threads:[~2011-04-13 20:29 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 23:52 Revert 737a3bb9416ce2a7c7a4170852473a4fcc9c67e8 ? Gabriel Paubert
2011-04-05 10:39 ` Michel Dänzer
2011-04-05 10:39 ` Michel Dänzer
2011-04-06 8:41 ` Uwe Kleine-König
2011-04-06 8:46 ` Dave Airlie
2011-04-06 8:46 ` Dave Airlie
2011-04-06 20:43 ` Gabriel Paubert
2011-04-06 20:43 ` Gabriel Paubert
2011-04-07 14:04 ` Michel Dänzer
2011-04-07 14:04 ` Michel Dänzer
2011-04-11 13:31 ` Gabriel Paubert
2011-04-11 13:31 ` Gabriel Paubert
2011-04-11 15:32 ` Michel Dänzer
2011-04-11 15:32 ` Michel Dänzer
2011-04-11 15:32 ` Michel Dänzer
2011-04-12 11:30 ` Gabriel Paubert
2011-04-12 11:30 ` Gabriel Paubert
2011-04-12 11:46 ` Michel Dänzer
2011-04-12 11:46 ` Michel Dänzer
2011-04-12 11:46 ` Michel Dänzer
2011-04-12 12:00 ` Gabriel Paubert
2011-04-12 12:00 ` Gabriel Paubert
2011-04-12 12:00 ` Gabriel Paubert
2011-04-12 17:29 ` Michel Dänzer
2011-04-12 17:29 ` Michel Dänzer
2011-04-13 7:59 ` Gabriel Paubert
2011-04-13 7:59 ` Gabriel Paubert
2011-04-13 8:16 ` Benjamin Herrenschmidt
2011-04-13 8:16 ` Benjamin Herrenschmidt
2011-04-13 10:01 ` Gabriel Paubert
2011-04-13 10:01 ` Gabriel Paubert
2011-04-13 12:12 ` Michel Dänzer
2011-04-13 12:12 ` Michel Dänzer
2011-04-13 12:12 ` Michel Dänzer
2011-04-13 12:27 ` Gabriel Paubert
2011-04-13 12:27 ` Gabriel Paubert
2011-04-13 14:15 ` Michel Dänzer
2011-04-13 14:15 ` Michel Dänzer
2011-04-13 20:01 ` Andy Furniss [this message]
2011-04-13 20:01 ` Andy Furniss
2011-04-13 8:02 ` Gabriel Paubert
2011-04-13 8:02 ` Gabriel Paubert
2011-04-13 8:02 ` Gabriel Paubert
2011-04-13 8:12 ` small git lesson [Was: Re: Revert 737a3bb9416ce2a7c7a4170852473a4fcc9c67e8 ?] Uwe Kleine-König
2011-04-13 8:12 ` Uwe Kleine-König
[not found] ` <20110413081246.GK18850__3180.67204575545$1302682420$gmane$org@pengutronix.de>
2011-04-13 8:59 ` Andreas Schwab
2011-04-13 8:59 ` Andreas Schwab
2011-04-13 9:36 ` Uwe Kleine-König
2011-04-13 10:31 ` Gabriel Paubert
2011-04-13 10:31 ` Gabriel Paubert
2011-04-13 12:17 ` Uwe Kleine-König
2011-04-13 12:17 ` Uwe Kleine-König
2011-04-07 11:25 ` Revert 737a3bb9416ce2a7c7a4170852473a4fcc9c67e8 ? Gabriel Paubert
2011-04-07 11:25 ` Gabriel Paubert
2011-04-07 11:33 ` Gabriel Paubert
2011-04-07 11:33 ` Gabriel Paubert
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=4DA60126.6030003@ukfsn.org \
--to=andyqos@ukfsn.org \
--cc=Greg@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michel@daenzer.net \
--cc=u.kleine-koenig@pengutronix.de \
/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.