Summary: | Regression: Raven Ridge 2700U does not boot with 4.19-rc7 | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Samantha McVey <samantham> | ||||
Component: | DRM/AMDgpu | Assignee: | Default DRI bug account <dri-devel> | ||||
Status: | RESOLVED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | medium | ||||||
Version: | XOrg git | ||||||
Hardware: | Other | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Samantha McVey
2018-10-09 22:48:58 UTC
Can you bisect? If you set modprobe.blacklist=amdgpu on the kernel command line in grub and you are still getting a problem, it's an issue outside of the graphics driver. If so, does setting pci=noacpi help? Created attachment 141966 [details]
Booting with pci noacpi
I was able to get something on the screen when I added "pci=noacpi" (this was without blacklisting amdgpu). [Firmware Bug]: AMD-Vi: No southbridge IOAPIC fonud AMD-Vi: Disabling interrupt remapping platform USBC000:00 failed to claim resource 0: [mem ...] acpi USBC000:00: platform device creation failed: -16 AMD-Vi: Unable to write to IOMMU perf counter. ... I uploaded an attachment which shows the full output (I only typed out the first several lines). I might be able to bisect if needed. Does the image I uploaded show you anything useful? I just tested on the latest git (v4.19-rc7-15-g64c5e530ac2c) and I didn't see any issues. So the issue has been either fixed between 4.19-rc7 and latest git or something in the kernel config is different. Sounds like it may be related to: https://bugzilla.kernel.org/show_bug.cgi?id=200087 It turns out it is config related, as I compiled the kernel with my old config instead of a minimal one, and I had the same boot issue. I posted about my issue here https://bugzilla.kernel.org/show_bug.cgi?id=200087 since that may be the same bug. |
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.