if you want to comment on the bug, go to the URL shown below and enter your comments there. Could you guys please send me the assembler listing from gdb?
I also would like to know the exact instruction where this happens. This is just a friendly reminder that the weekly dri-devel IRC meeting will be starting in the #dri-devel channel on irc.at 2100 UTC (or PM EDT or PM PDT, if you prefer).
You basically need to have 4 reference trees in your work dir: (a)SIS from recent trunk (c) R128 from ancient trunk (Mesa 3.4) (Mesa 3.4)
-- Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ func=detail&aid=721915&group_id=1&atid=200001 According to that the situation is provisory and should be resolved in August with new hardware. Neither am I about mails with cryptic if any content in the body (or articles describing XFree86 as coming from the 'freeware community', for that matter). Right, and I was wrong, there is way to disable it.
r=daenzer These version comparisons aren't correct, the interrupt handling code was only changed very recently, around 2.5.70 IIRC.
Also, you always return IRQ_HANDLED, even if you weren't interested in the interrupt at all and didn't do anything about it.
Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. Appended below are the individual URLs to get to all of your NEW bugs that haven't been touched for a week or more.
(2) You decide the bug doesn't belong to you, and you reassign it to someone else. You will get this message once a day until you've dealt with these bugs!
I hope this helps any caring sole for these old drivers to be more confident about this task. Status|ASSIGNED |NEW ------- Additional Comments From [email protected]