From: <bug...@fr...> - 2005-01-30 00:39:01
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=2419 Summary: Solo crashes on ia64 on startup Product: DRI Version: DRI CVS Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: General AssignedTo: dri...@li... ReportedBy: mar...@ic... When I use solo on ia64, it sometimes causes an MCA upon startup. That's because a memset is done on the framebuffer memory during init. Please refer to this message from Jesse Barnes to know why this is bad : http://sourceforge.net/mailarchive/forum.php?thread_id=6354420&forum_id=7177 Here is a patch that fixes this by changing the memset into a for() loop doing memory access one byte at a time : http://icps.u-strasbg.fr/~marchesin/dri/ia64_solo_memset.patch -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@fr...> - 2005-01-31 21:51:16
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=2419 ------- Additional Comments From mar...@ic... 2005-01-31 13:51 ------- Created an attachment (id=1800) --> (https://bugs.freedesktop.org/attachment.cgi?id=1800&action=view) New patch Other drivers (r128 and mga) are affected too, this patches fixes all the drivers that seemed to have this problem. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@fr...> - 2005-03-05 14:04:40
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=2419 mar...@ic... changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From mar...@ic... 2005-03-05 06:04 ------- Should be fixed in cvs for ia64 and powerpc -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: Jesse B. <jb...@sg...> - 2005-01-30 17:11:47
|
On Saturday, January 29, 2005 4:38 pm, bug...@fr... wrote: > When I use solo on ia64, it sometimes causes an MCA upon startup. That's > because a memset is done on the framebuffer memory during init. > > Please refer to this message from Jesse Barnes to know why this is bad : > http://sourceforge.net/mailarchive/forum.php?thread_id=6354420&forum_id=717 >7 > > Here is a patch that fixes this by changing the memset into a for() loop > doing memory access one byte at a time : > http://icps.u-strasbg.fr/~marchesin/dri/ia64_solo_memset.patch Is it just radeon that suffers from this problem? How about r128 or the other drivers? (I don't have the tree in front of me just now or I'd do a quick audit.) Thanks, Jesse |
From: Stephane M. <mar...@ic...> - 2005-01-31 19:58:22
|
Jesse Barnes wrote: >On Saturday, January 29, 2005 4:38 pm, bug...@fr... wrote: > >>When I use solo on ia64, it sometimes causes an MCA upon startup. That's >>because a memset is done on the framebuffer memory during init. >> >>Please refer to this message from Jesse Barnes to know why this is bad : >>http://sourceforge.net/mailarchive/forum.php?thread_id=6354420&forum_id=717 >>7 >> >>Here is a patch that fixes this by changing the memset into a for() loop >>doing memory access one byte at a time : >>http://icps.u-strasbg.fr/~marchesin/dri/ia64_solo_memset.patch >> > >Is it just radeon that suffers from this problem? How about r128 or the other >drivers? (I don't have the tree in front of me just now or I'd do a quick >audit.) > Yes, other drivers suffer from that too (at least r128, i810 and mga as far as I can see). However, as I said previously I don't understand them enough to touch them. Stephane |
From: Jesse B. <jb...@sg...> - 2005-01-31 20:58:23
|
On Monday, January 31, 2005 12:00 pm, Stephane Marchesin wrote: > Yes, other drivers suffer from that too (at least r128, i810 and mga as > far as I can see). However, as I said previously I don't understand them > enough to touch them. Oh, I must have missed that message, sorry. It sure looks like the r128 case is almost exactly the same as the one you fixed in the radeon driver, in fact your patch almost applies but for the small amount of radeon specific context in it. i810 actually looks like it has the memset #if 0'd out, so is probably safe. And mga again looks nearly identical to the radeon case. Why don't we fix them all up at once? Jesse |
From: Stephane M. <mar...@ic...> - 2005-01-31 21:49:05
|
Jesse Barnes wrote: >On Monday, January 31, 2005 12:00 pm, Stephane Marchesin wrote: > >>Yes, other drivers suffer from that too (at least r128, i810 and mga as >>far as I can see). However, as I said previously I don't understand them >>enough to touch them. >> > >Oh, I must have missed that message, sorry. > No problem, "previously" was quite some time ago... > It sure looks like the r128 case >is almost exactly the same as the one you fixed in the radeon driver, in fact >your patch almost applies but for the small amount of radeon specific context >in it. i810 actually looks like it has the memset #if 0'd out, so is >probably safe. > Ah right, in i810 it's commented out. > And mga again looks nearly identical to the radeon case. Why >don't we fix them all up at once? > Ok, I will attach another patch to the bug. Stephane |