From: Helge Hafting <helge.hafting@aitel.hist.no>
To: Roland Scheidegger <rscheidegger_lists@hispeed.ch>
Cc: Dave Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net
Subject: Re: Another drm/dri lockup - when moving the mouse
Date: Wed, 16 Mar 2005 15:45:14 +0100 [thread overview]
Message-ID: <4238467A.3030907@aitel.hist.no> (raw)
In-Reply-To: <423822FA.6020501@hispeed.ch>
Roland Scheidegger wrote:
> Helge Hafting wrote:
>
>> I have reported this before, but now I have some more data.
>>
>> I have an office pc with this video card:
>> VGA compatible controller: ATI Technologies Inc Radeon RV100 QY
>> [Radeon 7000/VE]
>>
>> In previous reports I found that starting xfree or xorg with dri support
>> cause a hang after a little while. It seems that this only happens when
>> the mouse moves. Something I didn't discover before because there
>> are lots of unplanned mouse movements - the thing is sensitive and jumps
>> a pixel now and then when I move stuff on the desk.
>
> What xorg / xfree / drm versions are you talking about?
>
>> Taking care not to move the mouse, I can start X and run glxgears
>> with acceleration. The slightest mouse movement during 3D activity
>> kills the machine instantly so it only responds to the reset button.
>> Mouse
>> movement without 3D activity may or may not kill the pc.
>>
>> Could there be a problem where 3D-stuff and code to move the mouse
>> "steps on each other toes" somehow? Or some way to test this further,
>> by disabling the mouse or force some kind of software fallback for
>> the mouse cursor?
>
> You could use Option "SWcursor" "true".
This didn't help. The cursor was definitely SW, flashing on and off
when over a scrolling xterm. The machine still died quickly.
> Since it crashes even without 3d sometimes, the problem does not seem
> to be related to dri (as in, dri driver). Sounds more like it's
> related to CP activity. Not sure what would cause this, there seem to
> be a lot of mouse cursor movement crashes reported lately... Do you
> have a USB mouse whose controller shares the IRQ with the graphic card
> maybe?
The card gets IRQ 16, which isn't shared with anything in this machine.
Helge Hafting
next prev parent reply other threads:[~2005-03-16 14:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 9:56 Another drm/dri lockup - when moving the mouse Helge Hafting
2005-03-16 12:13 ` Roland Scheidegger
2005-03-16 13:52 ` Helge Hafting
2005-03-16 15:59 ` Roland Scheidegger
2005-03-16 16:14 ` Jon Smirl
2005-03-16 14:45 ` Helge Hafting [this message]
2005-03-16 16:45 ` Martin K. Petersen
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=4238467A.3030907@aitel.hist.no \
--to=helge.hafting@aitel.hist.no \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rscheidegger_lists@hispeed.ch \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox