Bug 200809 - various stack traces related to amdgpu on kernel 4.18.0-rc8+
Summary: various stack traces related to amdgpu on kernel 4.18.0-rc8+
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: x86-64 Linux
: P1 low
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-13 19:19 UTC by Jaya Balan Aaron
Modified: 2018-08-18 15:12 UTC (History)
1 user (show)

See Also:
Kernel Version: 4.18.0-rc8
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg when crash/freeze occurred (70.62 KB, text/plain)
2018-08-13 19:19 UTC, Jaya Balan Aaron
Details
dmesg of 4.18.0 kernel with drm.debug=4 (104.40 KB, text/plain)
2018-08-18 03:31 UTC, Jaya Balan Aaron
Details

Description Jaya Balan Aaron 2018-08-13 19:19:17 UTC
Created attachment 277835 [details]
dmesg when crash/freeze occurred

updated from stock 4.15 kernel to 4.18-rc8.
lightdm freezes on boot without boot param `nomodeset` everytime.
graphical startup is proper with boot param `nomodeset`.
not passing amdgpu.dc=1 as it has no effect.

-- system --
kernel: 4.18-rc8 from https://github.com/M-Bab/linux-kernel-amdgpu-binaries
cpu: AMD Ryzen 3 2200G with Radeon Vega Graphics
mainboard: Gigabyte Technology Co., Ltd. A320M-S2H/A320M-S2H-CF, BIOS F22 03/15/2018

-- dmesg log summary --
multiple stack traces, varying everytime, with common line as:
> [    3.197767] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector
> ObjectID from Adapter Service for connector index:2! type 0 expected 3
Comment 1 Nicholas Kazlauskas 2018-08-15 20:28:43 UTC
I'm unable to reproduce the issue you describe on the kernel you've linked. Do you still see the problem occur on a stock kernel or amd-staging-drm-next?

Additional details on your setup would also be appreciated (Xorg log, monitor details, dmesg log with drm.debug=4, etc). If you think this is a regression then a bisection point could also help with debugging the issue, if any.
Comment 2 Jaya Balan Aaron 2018-08-17 17:43:26 UTC
Problem is with kernel 4.18.0-rc8 build from a 3rd party => https://github.com/M-Bab/linux-kernel-amdgpu-binaries.

Not sure if the amd-staging-drm-next is in it. It only says: "Kernel source code of amd-staging with DAL and latest security patches". So I doubt it has "amd-staging-drm-next".

Seems like 4.18.1 is latest stable, will compile that myself tonight and check if i'm able to reproduce.

Will get back with more details.
Comment 3 Jaya Balan Aaron 2018-08-18 03:14:15 UTC
Might have committed a blunder while testing.

I have a "DELL ST2220L" connected on analog VGA and "Panasonic Tv" connected on HDMI.

All the while primary might have been selected as the TV and the extended desktop presented on VGA line, which I mistook as a hung lightdm/Xorg.

But also upgraded the kernel to latest from git.
Will revert back to 4.18.1 and test further.

Sorry if this lead to any waste of your time.
Comment 4 Jaya Balan Aaron 2018-08-18 03:30:54 UTC
Unable to reproduce any error with HDMI display unplugged, primary display is being selected as VGA device.

Kernel used: Problem is with kernel 4.18.0 build from a 3rd party => https://github.com/M-Bab/linux-kernel-amdgpu-binaries.

Still see a lot of error traces and [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3

Setting priority as low.
Comment 5 Jaya Balan Aaron 2018-08-18 03:31:42 UTC
Created attachment 277921 [details]
dmesg of 4.18.0 kernel with drm.debug=4

Note You need to log in before you can comment on or make changes to this bug.