Opened 3 years ago

Closed 3 years ago

#16990 closed bug (fixed)

App_server crash with intel_extreme driver

Reported by: khallebal Owned by: axeld
Priority: normal Milestone: Unscheduled
Component: Servers/app_server Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: x86

Description

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

Attachments (2)

app_server-371-debug-06-06-2021-18-17-22.report (40.7 KB ) - added by khallebal 3 years ago.
syslog (204.8 KB ) - added by khallebal 3 years ago.

Download all attachments as: .zip

Change History (13)

comment:1 by rudolfc, 3 years ago

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

In 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..

Version 0, edited 3 years ago by rudolfc (next)

comment:2 by khallebal, 3 years ago

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.

comment:3 by X512, 3 years ago

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

comment:4 by X512, 3 years ago

Accelerant is intel_extreme.accelerant.

comment:5 by X512, 3 years ago

Can you get and upload syslog?

in reply to:  5 comment:6 by khallebal, 3 years ago

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?

by khallebal, 3 years ago

Attachment: syslog added

comment:7 by khallebal, 3 years ago

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.

comment:8 by rudolfc, 3 years ago

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

comment:9 by khallebal, 3 years ago

No, there isn't one either, sorry.

comment:10 by khallebal, 3 years ago

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

comment:11 by rudolfc, 3 years ago

Resolution: fixed
Status: newclosed

Thanks for the update khallebal! Closing ticket.

Note: See TracTickets for help on using tickets.