App_server crash with intel_extreme driver

[khallebal]

I can only save_report from the debugger and reset the system with the reset button, i tried all the new revisions from Rudolfc but nothing has changed. The gfx in question is the 82G33/G31, there are 2 old tickets with similar output which were closed as fixed. #2350 #634

[rudolfc]

Hi, Hmm. My expectation is that some other problem is happening here. Would assigning memory for the display maybe fail? Looks like the crash happens upon the first access to it by the app_server.

Upto this hrev you mention I only changed something with the pixelPLL which has nothing to do with assigned memory. I expect I cannot be of help here..

[khallebal]

Yes, i figured it had nothing to do with your driver, as i said i get the same output with the system driver,so i guess some of the app_server experts could shed some light on it.

[X512]

i guess some of the app_server experts could shed some light on it.

app_server experts are here.

It looks like pointer to framebuffer memory is NULL. Something is wrong with accelerant and/or graphics kernel driver.

add (%rcx,%r10,8), %r8 <--

rcx: 0x0000000000000000

r10: 0x0000000000000000

[X512]

Accelerant is intel_extreme.accelerant.

[X512]

Can you get and upload syslog?

[khallebal]

Replying to X512:

Can you get and upload syslog?

Unfortunately no syslog was written to disk?!, i'll try again and see if can get a syslog this time, what else can i do to help?

[khallebal]

This log is when booted with vesa driver i don't know if it has useful info, there is no log of the crash on the disk.

[rudolfc]

Could you see if after the crash and reboot there's a previous syslog maybe? If so, upload it as well..

[khallebal]

No, there isn't one either, sorry.

[khallebal]

After updating to hrev55668 the driver works now, thank you for the fixes rudolfc, ticket can be closed.

[rudolfc]

Thanks for the update khallebal! Closing ticket.