I haven't heard anything on this in three weeks. I filed a bug report, but no
acceptance yet. Does this imply that there is no intention to fix this
problem? What is happening with this? Am I even posting to the right list? I'm
completely in the dark here.
--
David Johnson
On Sun, 2009-05-31 at 00:12 -0700, David Johnson wrote:
I haven't heard anything on this in three weeks. I filed a bug report, but no
acceptance yet. Does this imply that there is no intention to fix this
problem? What is happening with this? Am I even posting to the right list?
I'm
After much rebuilding and testing, I have narrowed down the introduction of
this bug to commit #189855. Most of this commit is related to r600/700 chips,
but there are other changes. I don't understand the code and can't see
anything obvious. But it is a place to start.
Does this help any? Or
On Sun, 2009-05-17 at 13:54 -0700, David Johnson wrote:
After much rebuilding and testing, I have narrowed down the introduction of
this bug to commit #189855. Most of this commit is related to r600/700 chips,
but there are other changes. I don't understand the code and can't see
anything
I don't know if this helps pinpointing my problem, but when I unload
the drm module, I get the following message:
May 15 19:57:52 radagast kernel: vgapci0: child drm0 requested
pci_disable_busmaster
May 15 19:57:52 radagast kernel: drm0: detached
May 15 19:57:52 radagast kernel: Warning: memory
On Sat, 2009-05-09 at 18:41 -0700, David Johnson wrote:
On Friday 08 May 2009 03:31:04 pm Robert Noland wrote:
In order to guess what might be causing this, drm debugging needs to be
enabled before the hang, so that we can hopefully figure out what leads
up to the hung GPU.
I'm not able
On Tuesday 12 May 2009 08:17:51 am Robert Noland wrote:
On Sat, 2009-05-09 at 18:41 -0700, David Johnson wrote:
On Friday 08 May 2009 03:31:04 pm Robert Noland wrote:
In order to guess what might be causing this, drm debugging needs to be
enabled before the hang, so that we can hopefully
On Tuesday 12 May 2009 11:52:29 am David Johnson wrote:
I may have made a mistake though, and briefly turned on debugging earlier
in the session. I'll get another trace this evening when I have time, to
double check.
Yup, I must have turned on debugging earlier in that session. All I can get
On Friday 08 May 2009 03:31:04 pm Robert Noland wrote:
In order to guess what might be causing this, drm debugging needs to be
enabled before the hang, so that we can hopefully figure out what leads
up to the hung GPU.
Unfortunately that won't work, because turning on hw.dri.0.debug slows down
On Friday 08 May 2009 03:31:04 pm Robert Noland wrote:
In order to guess what might be causing this, drm debugging needs to be
enabled before the hang, so that we can hopefully figure out what leads
up to the hung GPU.
I'm not able to do that, but I did manage to get debug turned on and dmesg
On Thu, 2009-05-07 at 22:29 -0700, David Johnson wrote:
On Tuesday 05 May 2009 08:41:48 pm David Johnson wrote:
On Monday 04 May 2009 11:20:17 pm Robert Noland wrote:
This generally suggests that the GPU is locked up... Given that you say
sometimes it locks up hard (usually a panic, that
On Friday 08 May 2009 07:35:45 am Robert Noland wrote:
I still can't reproduce this... I updated the Xserver, libGL and dri
ports yesterday, all of which could be related to locking up the GPU and
worth a shot. Failing that, I need you to enabled drm debugging. Start
the system without X,
On Fri, 2009-05-08 at 14:58 -0700, David Johnson wrote:
On Friday 08 May 2009 07:35:45 am Robert Noland wrote:
I still can't reproduce this... I updated the Xserver, libGL and dri
ports yesterday, all of which could be related to locking up the GPU and
worth a shot. Failing that, I need
On Tuesday 05 May 2009 08:41:48 pm David Johnson wrote:
On Monday 04 May 2009 11:20:17 pm Robert Noland wrote:
This generally suggests that the GPU is locked up... Given that you say
sometimes it locks up hard (usually a panic, that you can't see since X
is running) and other times only X
On Mon, 2009-05-04 at 20:15 -0700, David Johnson wrote:
This topic has been recently discussed twice before in the past month and a
half, but without resolution. It now reappears on my system as I upgrade to
7.2-RELEASE. It does not happen with a build from RELENG_7 date=2009.03.13. I
am
On Monday 04 May 2009 11:20:17 pm Robert Noland wrote:
This generally suggests that the GPU is locked up... Given that you say
sometimes it locks up hard (usually a panic, that you can't see since X
is running) and other times only X is stalled it might be related to
this patch, if you
This topic has been recently discussed twice before in the past month and a
half, but without resolution. It now reappears on my system as I upgrade to
7.2-RELEASE. It does not happen with a build from RELENG_7 date=2009.03.13. I
am desperately hoping for a resolution.
To reiterate the
17 matches
Mail list logo
