ubuntu-x-swat team mailing list archive

[Tormod Volden <bugpost.tormod@xxxxxxxxx>]

** Description changed:

  [Impact]
- Affects Savage devices; unknown if it affects all Savage users or just a subset.  Leads to a crash in mesa during X startup.
- 
+ Affects Savage devices; affects all Savage users, but not all GL applications. Leads to a crash in mesa during application startup.
+  
  [Development]
  As Meerkat has not yet opened but Lucid is frozen solid, this fix is not yet in a development release, but it has been committed to the Ubuntu-X git tree and so will be included in the development version once Meerkat opens and we do our first mesa upload.  It will also be included in mesa 7.8 so we'll get it when we merge that in.
  
  [Patch]
- Patch has been proposed in this bug, confirmed to solve the issue, and accepted into the upstream 7.8 mesa branch.
+ Patch has been proposed in this bug, confirmed to solve the issue, and accepted into the upstream 7.8 mesa stable branch.
  
  [Test Case]
- Install latest -savage and mesa, and then make X start up.  Crash ensues.
+ Install latest -savage and mesa, and then run for instance /usr/lib/xscreensaver/glblur.  The application crashes.
  
  [Regression Potential]
  The code changes are specific to the -savage video driver, and as such can't cause regression for non-savage users.
  
- I've not reviewed exactly what the init call does in this case but
- typically they just zero out initial values.  So probably pretty low
- regression risk.
+ The init call creates a meta object and initializes it. Other code
+ depends on the existence of this object and references it without any
+ checking. At one point in the development this init call was done in the
+ common mesa code, but was later moved to the drivers using it. Savage
+ was forgotten, since few upstream developers have access to Savage
+ hardware and can do regular testing. Similar commits were done for a
+ couple of other drivers.
  
  [Original Report]
  
  glblur is not working, my video card is "01:00.0 VGA compatible
  controller: S3 Inc. VT8375 [ProSavage8 KM266/KL266]"
  
  ProblemType: Crash
  DistroRelease: Ubuntu 10.04
  Package: xscreensaver-gl 5.10-3ubuntu3
  ProcVersionSignature: Ubuntu 2.6.32-20.30-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-20-generic i686
  Architecture: i386
  CrashCounter: 1
  Date: Tue Apr 13 23:01:36 2010
  ExecutablePath: /usr/lib/xscreensaver/glblur
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406)
  ProcCmdline: /usr/lib/xscreensaver/glblur -root
  ProcEnviron:
   PATH=(custom, no user)
   LANG=pt_BR.utf8
   LANGUAGE=pt_BR:pt:en
  SegvAnalysis:
   Segfault happened at: 0x10d1825:	mov    %eax,(%edx)
   PC (0x010d1825) ok
   source "%eax" ok
   destination "(%edx)" (0x00000000) not located in a known VMA region (needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: xscreensaver
  StacktraceTop:
   ?? () from /usr/lib/dri/savage_dri.so
   ?? () from /usr/lib/dri/savage_dri.so
   _mesa_CopyTexImage2D () from /usr/lib/dri/savage_dri.so
   ?? ()
   ?? ()
  Title: glblur crashed with SIGSEGV in _mesa_CopyTexImage2D()
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

-- 
[savage] glblur crashed with SIGSEGV in _mesa_CopyTexImage2D()
https://bugs.launchpad.net/bugs/562718
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in ubuntu.