Bug#346486: Mouse events before card is initalized?
On Wed, 2006-02-08 at 16:20 +0100, Seiden Tiger wrote: There are two facts which may make a difference, and help starting x successfully *no mouse events on startup (since the error doesn't occour on every startup am am only 90% sure on this on). *multihead config (which doesn't work on multihead but starts reliably) This is interesting, but unfortunately doesn't ring any bells here. Also: *the backtrace allways stops in the animCursor etc function. Which in a way is good, because it suggests possible workarounds (SW cursor, non-animated cursor theme, ...). At the same time, this code path seems relatively innocuous, with little potential for hangs. Also, this is definitely not 'before the card is initialized', as it happens after ScreenInit(), which is the last driver init function called by the X server. The driver is supposed to cope with anything after ScreenInit. Ways to resolve this problem: * Is there a way to use pcitweak to look at the registers and look for a difference? If yes, at wich memory range are the offset registers? This approach is impractical because there's a large number of registers, many of which will differ genuinely. However, the contents of the RADEON_RBBM_STATUS register when this happens might be interesting for a start. * Is there a way to abort gracefully when the error message: (EE) RADEON(0): Idle timed out, resetting engine... appeared multiple times? The driver could detect this situation and call FatalError() or something I guess... not sure that would be much of an improvement though. *Is there a way rollback the changes on the radeon driver to track down the problems by binary searching through the patchsets? Sure, this can be done in the upstream CVS repository. At any rate, it would be good if you also brought this up upstream, on the xorg mailing list and/or http://bugs.freedesktop.org . -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
Bug#346486: Mouse events before card is initalized?
On Thursday 09 February 2006 17:26, Michel Dänzer wrote: *no mouse events on startup (since the error doesn't occour on every startup am am only 90% sure on this on). *multihead config (which doesn't work on multihead but starts reliably) This is interesting, but unfortunately doesn't ring any bells here. No? http://bugs.debian.org/255744 has been open for a long time...
Bug#346486: Mouse events before card is initalized?
On Thursday 09 February 2006 18:18, you wrote:
On Thu, 2006-02-09 at 17:49 +0100, Frans Pop wrote:
No? http://bugs.debian.org/255744 has been open for a long time...
Can you elaborate? I fail to see any connection between that and this
bug. ('no mouse events on startup' above is a prerequisite that appears
to avoid the infinite loop in the X server, not a symptom of this bug)
Sorry, I missed the full context of the no mouse events comment. After
browsing the full bug report, I agree this is unrelated.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#346486: Mouse events before card is initalized?
On Thu, 2006-02-09 at 17:49 +0100, Frans Pop wrote:
On Thursday 09 February 2006 17:26, Michel Dänzer wrote:
*no mouse events on startup (since the error doesn't occour on every
startup am am only 90% sure on this on).
*multihead config (which doesn't work on multihead but starts
reliably)
This is interesting, but unfortunately doesn't ring any bells here.
No? http://bugs.debian.org/255744 has been open for a long time...
Can you elaborate? I fail to see any connection between that and this
bug. ('no mouse events on startup' above is a prerequisite that appears
to avoid the infinite loop in the X server, not a symptom of this bug)
--
Earthling Michel Dänzer | Debian (powerpc), X and DRI developer
Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
Bug#346486: Mouse events before card is initalized?
On Mon, 2006-02-06 at 22:49 +0100, Seiden Tiger wrote: Your guess is appreciated (it quite possibly is some kind of timing issue, but that doesn't narrow down the problem enough), but a corresponding log file would be more useful. :) There are two files attached the first is the failure the second one is the successfull startup ableit with the half working dual head config. The major difference I see is Option UseFBDev. Does just disabling that in the failing config avoid the problem? In the all the failed x sessions there is one log message: (EE) RADEON(0): Idle timed out, resetting engine... which can also be seen from the backtrace. Unfortunately, this is a rather unspecific symptom that doesn't really say anything about the cause. -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
Bug#346486: Mouse events before card is initalized?
On Sun, 2006-01-29 at 14:51 +0100, Seiden Tiger wrote: By looking at the backtrace i had an different idea: What if the xserver gets mouse events before the card is initialized. Everytime i removed the ball from my trackball before booting i got an correct x startup. So i strongly suspect that the mouse events handling is enabled to early in the x-server. I haven't looked at the source to back this up. But my experience backs this up. It's still most likely a video driver issue, in particular if Option SWcursor has the same effect as not moving the mouse on X server startup, which seems quite likely given the backtrace. BTW, the actual full backtrace output would be interesting, in particular with xserver-xorg-dbg installed. -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
Bug#346486: Mouse events before card is initalized?
I have tested several cases, starting dpkg-reconfigure xserver-xorg doesn't allways help in starting the x-server. pcitweak also hasn't brought any worthwhile information. By looking at the backtrace i had an different idea: What if the xserver gets mouse events before the card is initialized. Everytime i removed the ball from my trackball before booting i got an correct x startup. So i strongly suspect that the mouse events handling is enabled to early in the x-server. I haven't looked at the source to back this up. But my experience backs this up. The update to xserver-xorg6.9.0.dfsg.1-4 doesn't help with this bug in any way. ST -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
