Bug 168766 - savage driver 1.1.27mh hang
Summary: savage driver 1.1.27mh hang
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: XFree86
Version: 3.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 168424
TreeView+ depends on / blocked
 
Reported: 2005-09-20 07:22 UTC by Haruo Tomita
Modified: 2007-11-30 22:07 UTC (History)
3 users (show)

Fixed In Version: RHBA-2006-0071
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-03-15 15:41:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
test program (974 bytes, application/x-gzip-compressed)
2005-09-20 07:50 UTC, Haruo Tomita
no flags Details
patch (7.66 KB, patch)
2005-09-20 07:54 UTC, Haruo Tomita
no flags Details | Diff
The patches were attached. (942 bytes, application/x-gzip-compressed)
2005-09-21 03:33 UTC, Haruo Tomita
no flags Details
The log was attached. (15.44 KB, application/x-gzip-compressed)
2005-09-21 03:34 UTC, Haruo Tomita
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2006:0071 0 qe-ready SHIPPED_LIVE XFree86 bug fix update 2006-03-14 05:00:00 UTC

Description Haruo Tomita 2005-09-20 07:22:02 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; T312461)

Description of problem:
Whenever this test program is executed, the system does hang. 


Version-Release number of selected component (if applicable):
XFree86-4.3.0-81.EL

How reproducible:
Always

Steps to Reproduce:
1. install drawline.tar.gz
2. execute drawline

  

Actual Results:  system is hung.

Expected Results:  Savage driver works. 

Additional info:

Comment 1 Haruo Tomita 2005-09-20 07:50:35 UTC
Created attachment 119015 [details]
test program

Comment 2 Haruo Tomita 2005-09-20 07:54:08 UTC
Created attachment 119016 [details]
patch

Comment 3 Haruo Tomita 2005-09-20 07:59:20 UTC
Issue of hang is corrected with this patch. 


Comment 4 Mike A. Harris 2005-09-20 08:17:42 UTC
Thanks for the report.  I've reviewed the patch, and have some questions:


Where did the patch originate?  It contains a number of changes which don't
actually do anything, ie:

-unsigned
+unsigned int

Curious if you got this from somewhere on the net, or from XFree86 or X.Org
CVS, or somewhere else?

+#if 0
 static void SavageSubsequentSolidTwoPointLine(


This will disable 2 point lines on all savage hardware.  Instead of this,
does using the XaaNoSolidTwoPointLine option with the stock Red Hat driver
yield the same result?

Some of the changes in the patch seem harmless, while other parts of the
patch touch code which is shared among different savage hardware, and of
which it is unclear as to the effect they might have on other Savage
hardware.

In addition to the above questions, please attach your X server log from
before and after this patch for review.

Thanks in advance.


Setting status to "NEEDINFO_REPORTER".  

Comment 5 Haruo Tomita 2005-09-20 08:38:10 UTC
This patch is not original. 
It is backported from savage driver 1.1.27 of RHEL4.
The cause of this issue is xaaptr->SolidBresenhamLineErrorTermBits = 14.
TermBit=14 will generate overfllow of the BCI command.
It should be xaaptr->SolidBresenhamLineErrorTermBits = 13.
I consented for the log. Please wait until tomorrow. 

Thanks.


 

Comment 6 Mike A. Harris 2005-09-20 21:36:23 UTC
Thanks.  We'll review the patch in greater depth, and do a risk analysis for
consideration in a future update.



Comment 7 Haruo Tomita 2005-09-21 03:24:03 UTC
(In reply to comment #6)
> Thanks.  We'll review the patch in greater depth, and do a risk analysis for
> consideration in a future update.

Thanks. Please contact me if there is an update. 
BTW, this isseu is solved with the following patches. 
(See attached file: patch.tar.gz)

diff -urN xc/programs/Xserver/hw/xfree86/drivers/savage.orig/savage_accel.c 
xc/programs/Xserver/hw/xfree86/drivers/savage/savage_accel.c
--- xc/programs/Xserver/hw/xfree86/drivers/savage.orig/savage_accel.c	2005-09-
20 17:41:38.000000000 +0900
+++ xc/programs/Xserver/hw/xfree86/drivers/savage/savage_accel.c	2005-09-
20 17:43:26.000000000 +0900
@@ -485,7 +485,7 @@
     xaaptr->SubsequentSolidFillTrap = SavageSubsequentSolidFillTrap; 
 #endif
 
-    xaaptr->SolidBresenhamLineErrorTermBits = 14;
+    xaaptr->SolidBresenhamLineErrorTermBits = 13;
 #endif
 
     /* ImageWrite */

 




Comment 8 Haruo Tomita 2005-09-21 03:33:31 UTC
Created attachment 119060 [details]
The patches were attached.

Comment 9 Haruo Tomita 2005-09-21 03:34:37 UTC
Created attachment 119061 [details]
The log was attached.

Comment 10 Mike A. Harris 2005-09-26 17:34:02 UTC
Thanks for the additional attachments.  We'll review this during RHEL3 U7
development for potential inclusion, and update the report again.



Comment 11 Mike A. Harris 2005-10-19 06:41:23 UTC
For future reference, when attaching patches or other text files, please attach
them as uncompressed file attachments of mime-type "text/plain" or check the
"patch" checkbox in bugzilla's file attachment feature.  This makes it easy to
review the patch inside the web browser directly, and speeds up our internal
processes.

I've reviewed both patches in the attachment in comment #8:

XFree86-4.3.0-savage-depth-24-made-colors-fix.patch:
  This one seems to be very obvious simple no-brainer fixes which appear
  to be correct and low risk.

XFree86-4.3.0-savage-bci-overflow-fix.patch:
  This one is non-obvious from the patch itself, without familiarity with
  the hardware/specs/driver code.  However, I have confirmed comment #5,
  and reviewed the current driver source as well, and the fix seems to
  be correct for this issue according to cvs commits et al.





Comment 19 Mike A. Harris 2005-11-28 20:46:01 UTC
Patches applied to CVS for XFree86-4.3.0-98.EL

Comment 20 Mike A. Harris 2005-11-29 00:32:01 UTC
XFree86-4.3.0-98.EL rpms built for RHEL3 U7 are temporarily available for
download and testing at the following URL:

    ftp://people.redhat.com/mharris/testing/3.0E

Please download a copy right away, even if you can't test them right away,
as I have limited disk quota, and the files will be removed to make space
for other things soon.

Setting status to "MODIFIED", and waiting for testing feedback from
bug reporter.

Comment 21 Haruo Tomita 2005-11-29 05:58:13 UTC
XFree86-4.3.0-98.EL.src.rpm was downloaded. I begin testing. 


Comment 22 Mike A. Harris 2005-11-29 07:07:09 UTC
Rebuilding the src.rpm can potentially introduce inconsistencies or anomalies
into the build which might not be present in our official buildsystem.
As such, it is preferred if possible that you the Red Hat generated
binaries are used for testing/confirmation, as they are what will
ultimately be released as official erratum.

Thanks for testing, and also for your fast response!


Comment 23 Haruo Tomita 2005-11-29 07:31:11 UTC
> Rebuilding the src.rpm can potentially introduce inconsistencies or anomalies
> into the build which might not be present in our official buildsystem.
> As such, it is preferred if possible that you the Red Hat generated
> binaries are used for testing/confirmation, as they are what will
> ultimately be released as official erratum.
> Thanks for testing, and also for your fast response!

It has understood. 
An official binary of RHEL3 U7
The tester of Toshiba will confirm it by using international β. 

Thanks.

Comment 25 Haruo Tomita 2005-12-16 02:34:00 UTC
I completed the test. XFree86-4.3.0-98.EL works well. 

Thanks.



Comment 26 Suzanne Hillman 2006-01-26 19:56:40 UTC
Tested by reporter, moving to PASSES_QA.

Comment 28 Red Hat Bugzilla 2006-03-15 15:41:15 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2006-0071.html



Note You need to log in before you can comment on or make changes to this bug.