I don't think it is a duplicate. I've never had the crash occur while
browsing (though firefox is always open) and don't see a firefox core
dump or anything like that. I have intel hardware, not ATI. However, I
also cannot find a specific trigger, and it does look like it may be
caused by erroneous handling of a null pointer. Uploading the full
logfiles from each crash is kinda hopeless as they grow to be rather
large. I collect several files after each crash to examine, and the
folder of those files is about 700MiB per crash. Unfortunately, I cannot
trigger the crash, so getting a full gdb backtrace is going to be
difficult.

The backtrace I am finding in my Xorg.failsafe.log is:

(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument                                    
  
<repeated thousands of times>                                                   
  
(==) FBDEV(0): DPMS enabled                                                     
  
(==) RandR enabled                                                              
  
<snip>                                                                          
  
                                                                                
  
Backtrace:                                                                      
  
0: /usr/bin/X (xorg_backtrace+0x28) [0x4a3248]                                  
  
1: /usr/bin/X (0x400000+0x655ad) [0x4655ad]                                     
  
2: /lib/libpthread.so.0 (0x7fd31e800000+0xf8f0) [0x7fd31e80f8f0]                
  
3: /usr/bin/X (DamageUnregister+0x53) [0x4d72f3]                                
  
4: /usr/lib/xorg/modules/libshadow.so (shadowRemove+0x33) [0x7fd31b1303c3]      
  
5: /usr/lib/xorg/modules/libshadow.so (0x7fd31b12f000+0x1884) [0x7fd31b130884]  
  
6: /usr/bin/X (0x400000+0xa77d9) [0x4a77d9]                                     
  
7: /usr/bin/X (0x400000+0x16852c) [0x56852c]                                    
  
8: /usr/bin/X (0x400000+0x2624c) [0x42624c]                                     
  
9: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7fd31d4f8c4d]                     
  
10: /usr/bin/X (0x400000+0x25d59) [0x425d59]                                    
  
Segmentation fault at address (nil)                                             
  

The kdm log gives this: (note that 'batch' is found once in the file while the 
others are repeated):
    ../../intel/intel_bufmgr_gem.c:957: Error mapping buffer 36087 (pixmap): 
Cannot allocate memory .
    ../../intel/intel_bufmgr_gem.c:876: Error mapping buffer 15600 
(surface_state): Cannot allocate memory .
    ../../intel/intel_bufmgr_gem.c:876: Error mapping buffer 15615 
(binding_table): Cannot allocate memory .
    <repeated hundreds of times, number after 'buffer' varies>
    ../../intel/intel_bufmgr_gem.c:876: Error mapping buffer 16230 
(surface_state): Cannot allocate memory .
    ../../intel/intel_bufmgr_gem.c:876: Error mapping buffer 15863 
(binding_table): Cannot allocate memory .
    ../../intel/intel_bufmgr_gem.c:876: Error mapping buffer 15672 
(surface_state): Cannot allocate memory .
    ../../intel/intel_bufmgr_gem.c:876: Error mapping buffer 16084 
(binding_table): Cannot allocate memory .
    ../../intel/intel_bufmgr_gem.c:876: Error mapping buffer 15820 
(binding_table): Cannot allocate memory .
    ../../intel/intel_bufmgr_gem.c:876: Error mapping buffer 15950 
(binding_table): Cannot allocate memory .
    ../../intel/intel_bufmgr_gem.c:876: Error mapping buffer 36091 (batch): 
Cannot allocate memory .

    Fatal server error:
    Failed to map batchbuffer: Cannot allocate memory

And Xorg.0.log yields:
(WW) intel(0): i830_uxa_prepare_access: bo map failed         
(WW) intel(0): i830_uxa_prepare_access: bo map failed         
<repeated thousands of times>                                 
                                                              
Fatal server error:                                           
Failed to map batchbuffer: Cannot allocate memory

-- 
X server crashes randomly
https://bugs.launchpad.net/bugs/573957
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to