Changes between Initial Version and Version 1 of Ticket #13580


Ignore:
Timestamp:
Jul 2, 2017, 5:21:44 PM (7 years ago)
Author:
waddlesplash
Comment:

Woah, a VESA crash. I've never seen one of those before.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #13580

    • Property Component - General → Drivers/Graphics

  • Ticket #13580 – Description

    initial v1  
    33After initial messages on the screen, the boot ends at a black screen. When attaching to the serial console, the following trace is shown with default boot options:
    44
     5{{{
    56intel_extreme: CALLED status_t intel_get_frame_buffer_config(frame_buffer_config*)
    67PANIC: _mutex_lock(): using unitialized lock 0xffffffff801c83e0
    … …  
    464725 00007ff7fb564ff0 (+  48) 000001a21b1abe48   </boot/system/runtime_loader@0x000001a21b198000> <unknown> + 0x13e48
    474826 00007ff7fb565020 (+   0) 00007f70db2aa260   <commpage> commpage_thread_exit + 0x00
    48 
     49}}}
    4950In safemode (all safe mode options enabled), the following trace is shown:
    50 
     51{{{
    5152vm_soft_fault: va 0x0 not covered by area in address space
    5253vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x0, ip 0xffffffff815096e1, write 0, user 0, thread 0x61
    … …  
    11211335 00007f9cc21fdd10 (+  48) 000001dfbd55be48   </boot/system/runtime_loader@0x000001dfbd548000> <unknown> + 0x13e48
    11311436 00007f9cc21fdd40 (+   0) 00007f74d2220260   <commpage> commpage_thread_exit + 0x00
    114 
     115}}}
    115116I'll attach full serial output for different configurations to the ticket. Please tell me if I can provide any further information or run any tests to help investigate this issue.