Bug 111761 - Latest Git Kernel doesn’t boot with Radeon NI with the drm-next-2019-09-18 updates
Summary: Latest Git Kernel doesn’t boot with Radeon NI with the drm-next-2019-09-18 up...
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: DRI git
Hardware: All All
: high critical
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-21 06:59 UTC by Christian Zigotzky
Modified: 2019-11-19 09:35 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
DRM patch (249.91 KB, patch)
2019-09-23 22:01 UTC, Christian Zigotzky 		no flags Details | Splinter Review
This patch reverts the changes in "drivers/gpu/drm/drm" and "include/drm/". (249.91 KB, patch)
2019-09-23 22:04 UTC, Christian Zigotzky 		no flags Details | Splinter Review
Show Obsolete (1) View All

Description Christian Zigotzky 2019-09-21 06:59:55 UTC 
Hello,

I compiled the latest Git kernel with the new drm-next-2019-09-18 updates yesterday.


Unfortunately it doesn't boot with my Radeon Northern Islands graphics cards anymore. I tested it with a Radeon HD6870 and with a Radeon HD4870. 

The kernel boots with a Radeon SI graphics card. (R7 240) 

I reverted the latest DRM updates and after that the kernel boots with my Radeon HD6870 and with my Radeon HD4870 without any problems.

Could you please test the latest Git kernel with the drm-next-2019-09-18 updates with Radeon NI graphics cards?

Thanks,
Christian
Comment 1 Alex Deucher 2019-09-23 14:53:40 UTC 
Can you bisect?  Please attach your xorg log and dmesg output.
Comment 2 Christian Zigotzky 2019-09-23 18:56:55 UTC 
The changes of the following files are responsible for the boot issue. 

- drivers/gpu/drm/drm_*
- include/drm/*

The kernel doesn't boot with the updates in the files above from the drm-next-2019-09-18 so I can't attach the output of dmesg and the Xorg log file.

Which of the files in

- drivers/gpu/drm/drm_*
- include/drm/*

are responsible at the beginning of the kernel boot? Is there a patch in the dri git for the files above?

I can bisect but actually I need only to know which of the files above are responsible at the beginning of the kernel boot.

Could someone please test the latest Git kernel with a Radeon HD NI graphics card?

Thanks
Comment 3 Christian Zigotzky 2019-09-23 22:01:20 UTC 
Created attachment 145482 [details] [review]
DRM patch
Comment 4 Christian Zigotzky 2019-09-23 22:04:30 UTC 
Created attachment 145483 [details] [review]
This patch reverts the changes in "drivers/gpu/drm/drm" and "include/drm/".

I created a patch today. This patch reverts the changes in the following files.

- drivers/gpu/drm/drm_*
- include/drm/*

It also reverts all files which depends on these files above. 

Now I can boot the latest Git kernel with my Radeon HD NI graphics cards again.

Please check the updates in the files

- drivers/gpu/drm/drm_*
- include/drm/*

Thanks
Comment 5 Christian Zigotzky 2019-09-24 07:00:44 UTC 
Hello,

Another user has confirmed the boot issue with an ATi FirePro 2260.

With which good and bad commit should I start bisecting?

Thanks,
Christian
Comment 6 Christian Zigotzky 2019-09-25 19:07:30 UTC 
With which good and bad commit should I start bisecting?

Thanks
Comment 8 Christian Zigotzky 2019-09-26 08:30:36 UTC 
Alex,

Success!

I compiled the latest Git kernel with this patch today. After that I could boot this kernel with my Radeon NI graphics cards without any problems!

Many thanks for this patch!

Cheers,
Christian
Comment 9 Christian Zigotzky 2019-09-26 12:05:09 UTC 
It boots with a Radeon SI graphics card too.
Comment 10 Martin Peres 2019-11-19 09:35:58 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/872.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.