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
On Wed, 2011-04-13 at 09:59 +0200, Gabriel Paubert wrote:
>
> Well, X is dead, or rather in an infinite ioctl loop as described
> above.
> IIRC, the display enters a power-down mode and there is nothing to
> see.
So basically the card crashed. There's about an infinite amount of
reasons why
On Mit, 2011-04-13 at 14:27 +0200, Gabriel Paubert wrote:
> On Wed, Apr 13, 2011 at 02:12:16PM +0200, Michel D?nzer wrote:
> > On Mit, 2011-04-13 at 09:59 +0200, Gabriel Paubert wrote:
> > > On Tue, Apr 12, 2011 at 07:29:22PM +0200, Michel D?nzer wrote:
> > > > On Die, 2011-04-12 at 14:00 +0200,
On Wed, Apr 13, 2011 at 02:12:16PM +0200, Michel D?nzer wrote:
> On Mit, 2011-04-13 at 09:59 +0200, Gabriel Paubert wrote:
> > On Tue, Apr 12, 2011 at 07:29:22PM +0200, Michel D?nzer wrote:
> > > On Die, 2011-04-12 at 14:00 +0200, Gabriel Paubert wrote:
> > > > On Tue, Apr 12, 2011 at 01:46:10PM
Hello Gabriel
On Wed, Apr 13, 2011 at 12:31:44PM +0200, Gabriel Paubert wrote:
> On Wed, Apr 13, 2011 at 10:59:14AM +0200, Andreas Schwab wrote:
> > Uwe Kleine-K?nig writes:
> >
> > > $ git name-rev --refs=refs/tags/v2.6\*
> > > 69a07f0b117a40fcc1a479358d8e1f41793617f2
> > >
On Mit, 2011-04-13 at 09:59 +0200, Gabriel Paubert wrote:
> On Tue, Apr 12, 2011 at 07:29:22PM +0200, Michel D?nzer wrote:
> > On Die, 2011-04-12 at 14:00 +0200, Gabriel Paubert wrote:
> > > On Tue, Apr 12, 2011 at 01:46:10PM +0200, Michel D?nzer wrote:
> > > > >
> > > > > With no_wb=1 the
On Wed, Apr 13, 2011 at 10:59:14AM +0200, Andreas Schwab wrote:
> Uwe Kleine-K?nig writes:
>
> > $ git name-rev --refs=refs/tags/v2.6\*
> > 69a07f0b117a40fcc1a479358d8e1f41793617f2
> > 69a07f0b117a40fcc1a479358d8e1f41793617f2 tags/v2.6.39-rc2~3^2~43^2~4
> >
> > so it was introduced just before
On Wed, Apr 13, 2011 at 06:16:13PM +1000, Benjamin Herrenschmidt wrote:
> On Wed, 2011-04-13 at 09:59 +0200, Gabriel Paubert wrote:
> >
> > Well, X is dead, or rather in an infinite ioctl loop as described
> > above.
> > IIRC, the display enters a power-down mode and there is nothing to
> > see.
Uwe Kleine-K?nig writes:
> $ git name-rev --refs=refs/tags/v2.6\*
> 69a07f0b117a40fcc1a479358d8e1f41793617f2
> 69a07f0b117a40fcc1a479358d8e1f41793617f2 tags/v2.6.39-rc2~3^2~43^2~4
>
> so it was introduced just before -rc2.
$ git tag --contains 69a07f0b117a40fcc1a479358d8e1f41793617f2
On Wed, Apr 13, 2011 at 10:02:04AM +0200, Gabriel Paubert wrote:
> On Tue, Apr 12, 2011 at 01:46:10PM +0200, Michel D?nzer wrote:
> > BTW, if your kernel contains commit
> > 69a07f0b117a40fcc1a479358d8e1f41793617f2, can you try if reverting that
> > helps?
>
> My kernel is pristine 2.6.38 and
On Tue, Apr 12, 2011 at 01:46:10PM +0200, Michel D?nzer wrote:
> BTW, if your kernel contains commit
> 69a07f0b117a40fcc1a479358d8e1f41793617f2, can you try if reverting that
> helps?
My kernel is pristine 2.6.38 and does not include this commit
(was introduced before 2.6.39-rc1 according to
On Tue, Apr 12, 2011 at 07:29:22PM +0200, Michel D?nzer wrote:
> On Die, 2011-04-12 at 14:00 +0200, Gabriel Paubert wrote:
> > On Tue, Apr 12, 2011 at 01:46:10PM +0200, Michel D?nzer wrote:
> > > >
> > > > With no_wb=1 the driver goes a bit further but the X server ends
> > > > up in an infinite
On Tue, Apr 12, 2011 at 07:29:22PM +0200, Michel Dänzer wrote:
On Die, 2011-04-12 at 14:00 +0200, Gabriel Paubert wrote:
On Tue, Apr 12, 2011 at 01:46:10PM +0200, Michel Dänzer wrote:
With no_wb=1 the driver goes a bit further but the X server ends
up in an infinite ioctl loop and
On Tue, Apr 12, 2011 at 01:46:10PM +0200, Michel Dänzer wrote:
BTW, if your kernel contains commit
69a07f0b117a40fcc1a479358d8e1f41793617f2, can you try if reverting that
helps?
My kernel is pristine 2.6.38 and does not include this commit
(was introduced before 2.6.39-rc1 according to gitk).
On Wed, 2011-04-13 at 09:59 +0200, Gabriel Paubert wrote:
Well, X is dead, or rather in an infinite ioctl loop as described
above.
IIRC, the display enters a power-down mode and there is nothing to
see.
So basically the card crashed. There's about an infinite amount of
reasons why radeons
On Wed, Apr 13, 2011 at 06:16:13PM +1000, Benjamin Herrenschmidt wrote:
On Wed, 2011-04-13 at 09:59 +0200, Gabriel Paubert wrote:
Well, X is dead, or rather in an infinite ioctl loop as described
above.
IIRC, the display enters a power-down mode and there is nothing to
see.
So
On Wed, Apr 13, 2011 at 10:59:14AM +0200, Andreas Schwab wrote:
Uwe Kleine-König u.kleine-koe...@pengutronix.de writes:
$ git name-rev --refs=refs/tags/v2.6\*
69a07f0b117a40fcc1a479358d8e1f41793617f2
69a07f0b117a40fcc1a479358d8e1f41793617f2 tags/v2.6.39-rc2~3^2~43^2~4
so it was
On Mit, 2011-04-13 at 09:59 +0200, Gabriel Paubert wrote:
On Tue, Apr 12, 2011 at 07:29:22PM +0200, Michel Dänzer wrote:
On Die, 2011-04-12 at 14:00 +0200, Gabriel Paubert wrote:
On Tue, Apr 12, 2011 at 01:46:10PM +0200, Michel Dänzer wrote:
With no_wb=1 the driver goes a bit
On Wed, Apr 13, 2011 at 02:12:16PM +0200, Michel Dänzer wrote:
On Mit, 2011-04-13 at 09:59 +0200, Gabriel Paubert wrote:
On Tue, Apr 12, 2011 at 07:29:22PM +0200, Michel Dänzer wrote:
On Die, 2011-04-12 at 14:00 +0200, Gabriel Paubert wrote:
On Tue, Apr 12, 2011 at 01:46:10PM +0200,
On Wed, Apr 13, 2011 at 10:02:04AM +0200, Gabriel Paubert wrote:
On Tue, Apr 12, 2011 at 01:46:10PM +0200, Michel Dänzer wrote:
BTW, if your kernel contains commit
69a07f0b117a40fcc1a479358d8e1f41793617f2, can you try if reverting that
helps?
My kernel is pristine 2.6.38 and does not
Uwe Kleine-König u.kleine-koe...@pengutronix.de writes:
$ git name-rev --refs=refs/tags/v2.6\*
69a07f0b117a40fcc1a479358d8e1f41793617f2
69a07f0b117a40fcc1a479358d8e1f41793617f2 tags/v2.6.39-rc2~3^2~43^2~4
so it was introduced just before -rc2.
$ git tag --contains
Hello Gabriel
On Wed, Apr 13, 2011 at 12:31:44PM +0200, Gabriel Paubert wrote:
On Wed, Apr 13, 2011 at 10:59:14AM +0200, Andreas Schwab wrote:
Uwe Kleine-König u.kleine-koe...@pengutronix.de writes:
$ git name-rev --refs=refs/tags/v2.6\*
69a07f0b117a40fcc1a479358d8e1f41793617f2
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
On Die, 2011-04-12 at 14:00 +0200, Gabriel Paubert wrote:
> On Tue, Apr 12, 2011 at 01:46:10PM +0200, Michel D?nzer wrote:
> > >
> > > With no_wb=1 the driver goes a bit further but the X server ends
> > > up in an infinite ioctl loop and the logs are:
> >
> > Which ioctl does it loop on?
On Tue, Apr 12, 2011 at 01:46:10PM +0200, Michel D?nzer wrote:
> >
> > With no_wb=1 the driver goes a bit further but the X server ends
> > up in an infinite ioctl loop and the logs are:
>
> Which ioctl does it loop on? Please provide the Xorg.0.log file as well.
On Die, 2011-04-12 at 13:30 +0200, Gabriel Paubert wrote:
>
> On Mon, Apr 11, 2011 at 05:32:43PM +0200, Michel D?nzer wrote:
> >
> > Have you ruled out any MSI related problems? I think the IRQ not working
> > could explain the symptoms...
>
> Booting with MSI disabled does not change
Hi Micel,
On Mon, Apr 11, 2011 at 05:32:43PM +0200, Michel D?nzer wrote:
> [ Adding the dri-devel list ]
>
> Have you ruled out any MSI related problems? I think the IRQ not working
> could explain the symptoms...
Booting with MSI disabled does not change anything. Actually on this
On Die, 2011-04-12 at 13:30 +0200, Gabriel Paubert wrote:
On Mon, Apr 11, 2011 at 05:32:43PM +0200, Michel Dänzer wrote:
Have you ruled out any MSI related problems? I think the IRQ not working
could explain the symptoms...
Booting with MSI disabled does not change anything. Actually
Hi Micel,
On Mon, Apr 11, 2011 at 05:32:43PM +0200, Michel Dänzer wrote:
[ Adding the dri-devel list ]
Have you ruled out any MSI related problems? I think the IRQ not working
could explain the symptoms...
Booting with MSI disabled does not change anything. Actually on this
machine
On Tue, Apr 12, 2011 at 01:46:10PM +0200, Michel Dänzer wrote:
With no_wb=1 the driver goes a bit further but the X server ends
up in an infinite ioctl loop and the logs are:
Which ioctl does it loop on? Please provide the Xorg.0.log file as well.
From memory, the code was 0x64, which
On Die, 2011-04-12 at 14:00 +0200, Gabriel Paubert wrote:
On Tue, Apr 12, 2011 at 01:46:10PM +0200, Michel Dänzer wrote:
With no_wb=1 the driver goes a bit further but the X server ends
up in an infinite ioctl loop and the logs are:
Which ioctl does it loop on? Please provide the
[ Adding the dri-devel list ]
On Mon, 2011-04-11 at 15:31 +0200, Gabriel Paubert wrote:
> On Thu, Apr 07, 2011 at 04:04:35PM +0200, Michel D?nzer wrote:
> > On Mit, 2011-04-06 at 22:43 +0200, Gabriel Paubert wrote:
> > >
> > > The probem is that, at least on one of my machines, the new driver
[ Adding the dri-devel list ]
On Mon, 2011-04-11 at 15:31 +0200, Gabriel Paubert wrote:
On Thu, Apr 07, 2011 at 04:04:35PM +0200, Michel Dänzer wrote:
On Mit, 2011-04-06 at 22:43 +0200, Gabriel Paubert wrote:
The probem is that, at least on one of my machines, the new driver
does
33 matches
Mail list logo
