Bug 212017
Summary: | System doesn't boot with amd_iommu=off | ||
---|---|---|---|
Product: | IO/Storage | Reporter: | Mthw (matejm98mthw) |
Component: | Other | Assignee: | io_other |
Status: | RESOLVED CODE_FIX | ||
Severity: | high | CC: | basic89, dwmw2, haultalented, jan.steffens, jordicoma22, mario.limonciello, matejm98mthw, mingo, steven, tglx |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 5.11 | Subsystem: | |
Regression: | Yes | Bisected commit-id: |
Description
Mthw
2021-03-02 08:49:45 UTC
Reverting this commit fixes the issue and there haven't been any side-effects yet. I tried reverting f36a74b9 in Zen Kernel and it made my own system not bootable. System configuration affected: Machine: Type: Desktop System: ASUS product: All Series v: N/A serial: <superuser required> Mobo: ASUSTeK model: X99-DELUXE II v: Rev 1.xx serial: <superuser required> UEFI [Legacy]: American Megatrends v: 2101 date: 07/10/2019 CPU: Info: 8-Core Intel Core i7-5960X [MT MCP] speed: 3787 MHz min/max: 1200/3001 MHz Maybe this commit's change is mutually exclusive between AMD and Intel systems? (In reply to Steven Barrett from comment #2) > > Maybe this commit's change is mutually exclusive between AMD and Intel > systems? Might be, I don't have any other hardware to test it with though. (In reply to matejm98mthw from comment #3) > Might be, I don't have any other hardware to test it with though. I can confirm a Thinkpad T495s (AMD Zen+) will not boot with "amd_iommu=off" in 5.11.1 abd 5.11.2 as delivered with manjaro linux. (and will sometimes fail to recover from suspend if I do not pass this parameter). (In reply to Mav from comment #4) > (In reply to matejm98mthw from comment #3) > > Might be, I don't have any other hardware to test it with though. > > I can confirm a Thinkpad T495s (AMD Zen+) will not boot with "amd_iommu=off" > in 5.11.1 abd 5.11.2 as delivered with manjaro linux. (and will sometimes > fail to recover from suspend if I do not pass this parameter). Have you tried 5.11.3 or .4? The issue with waking up from suspend seems to be fixed now. I have tried the last kernel from arch 5.11.6 and it still doesn't boot. I'm one of the reporters from the arch thread https://bugs.archlinux.org/task/69810 and the kernel compiled with this commit rollback worked. Are the changes pushed to the main branch? I have ryzen 1600x (zen1) and it's confirmed that removing "amd_iommu=off" boots. (In reply to jordicoma from comment #6) > I have tried the last kernel from arch 5.11.6 and it still doesn't boot. > I'm one of the reporters from the arch thread > https://bugs.archlinux.org/task/69810 and the kernel compiled with this > commit rollback worked. > > Are the changes pushed to the main branch? > > I have ryzen 1600x (zen1) and it's confirmed that removing "amd_iommu=off" > boots. Yes, it's still broken, someone has to make the change, which would be either reverting the commit or figure out a better way to fix the original issue. I just built it on 5.12-rc3 and it fixes the issue. (In reply to David Woodhouse from comment #8) > Please test > https://lore.kernel.org/r/20210315111502.440451-1-dwmw2@infradead.org Is this patch still needed after 36013e9ffc0a17eee8d3e4d92aea0dc37687760d (9f81ca8d1fd68f5697c201f26632ed622e9e462f upstream, bug 212133)? I am currently on 5.11.11 and I haven't had this issue for a while now. |