Bug 21151 - System frozen when enabling intel_iommu
Summary: System frozen when enabling intel_iommu
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-26 11:13 CEST by Mubarak Alrashidi
Modified: 2018-09-20 08:32 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Mubarak Alrashidi 2017-06-26 11:13:57 CEST 
Description of problem:
The system freezes when it's idle for sometime if the intel_iommu is enabled/activated.

Version-Release number of selected component (if applicable):
4.4.65-desktop-1.mga5


How reproducible:
Enable/Activate the intel_iommu

Steps to Reproduce:
1. in the boot menu, edit the boot command
2. add 'intel_iommu=on'
3. hit F10


Notes:
I'm using dual intel Xeon e5-2697 v3
Marja Van Waes 2017-06-26 19:36:14 CEST

CC: (none) => marja11
Component: Release (media or process) => RPM Packages

Marja Van Waes 2017-06-26 19:46:42 CEST

Assignee: bugsquad => kernel

Comment 1 Mubarak Alrashidi 2017-06-27 13:33:08 CEST 
I tried it for the third time, with the 'iommu=1 intel_iommu=on'

once I logged-in, I launched terminal and executed `htop`. after about after about 7 minutes, the keyboard & mouse stopped responding. while the htop still was working and showing its things. And I noticed that "dropbox", "teamviewer" were using 100% CPU.

So, I was wrong about the system freezing. it didn't freeze, but input devices sort of lost their communications with mageia/kernel.

And I have no idea why were dropbox & teamviewer using 100% CPU.

If there is any log files I should be attaching please let me know.

Thanks
Comment 2 Marja Van Waes 2017-06-27 20:51:01 CEST 
(In reply to Mubarak Alrashidi from comment #1)

> 
> If there is any log files I should be attaching please let me know.
> 


Thanks for asking.
When you've rebooted right after a freeze, run, as root:

    journalctl -ab-1 > log.txt

and please attach log.txt to this bug report.
Comment 3 Marja Van Waes 2018-09-20 08:32:53 CEST 
(In reply to Marja Van Waes from comment #2)
> (In reply to Mubarak Alrashidi from comment #1)
> 
> > 
> > If there is any log files I should be attaching please let me know.
> > 
> 
> 
> Thanks for asking.
> When you've rebooted right after a freeze, run, as root:
> 
>     journalctl -ab-1 > log.txt
> 
> and please attach log.txt to this bug report.

Hi Mubarak,

For some reason, you never did that :-(

This bug was filed against Mageia 5. Did it get fixed? If so, please change its status to RESOLVED - FIXED.

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It continued to get limited extended support since then, but that support has now ended, too.
As a result we are closing this bug report as OLD.

If you still see this issue in a newer Mageia version, then please reopen this report and attach the requested log file.

==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==

Status: NEW => RESOLVED
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.