** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/159356
Title:
System freeze on high memory usage when DMA is disabled
Status in linux package in Ubuntu:
It is also possible, since we now know how the bug is triggered, should
Marcus open a new report?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/159356
Title:
System freeze on high
This also explains the reason a person with a USB drive was seeing
thrashing (constant blinking) when using the fedora live environment
with many tabs open.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Do you think this could eventually be merged into a kernel? Has anyone
filed a kernel bugzilla with the patch so we can improve it, and get it
merged to the kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The attached kernel patch (applied on top of 4.18.5) that I've tried,
almost completely eliminates the disk thrashing(the constant reading of
executable(and .so) files on every context switch) associated with
freezing the OS and so, with this patch, the OOM-killer is triggered
within a maxium of 1
jecks (slayerproof32), it is most unhelpful to post comments or
attachments here, or give pastebin links. If you want to motivate
developers to want to look into your issue, file a new report. If you
want developers to ignore your problem, continue posting here.
marco (nazgul17), one may always
Consider also posting the output of
Sudo parted -l
Here are my results if these commands. Iam running top right now and
will be posted soon.
https://pastebin.com/8q75EXyz 1 ā Inxi-Fzxc0
https://pastebin.com/mnj4Bamu ā Lspci -V
https://pastebin.com/KqpKuCa3 1 --Dmesg
--
You received this bug
Iād say you probably want to start with these 4 commands and posting the results
Lspci -v
Inxi -Fzxc0
dmesg > dmesg.log (will save to ~/dmesg.log)
top -b > top.log (run this command, then trigger the memory issue. It will save
to ~/top.log. If you have to hard reboot, the file will still be
Hi Christopher,
How does one go about providing debugging information?
Please consider the limitations of an environment that does not respond to
commands.
Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
jecks (slayerproof32), this report is poorly defined, and not root caused as no
debugging logs have been provided by the original reporter. However, what
little is known is that the issue for the original reporter was correlated to
when DMA was disabled in the BIOS, using a now old, and
** Package changed: linux (Arch Linux) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** No longer affects: linux (Ubuntu)
** Package changed: fedora => ubuntu
** Changed in: ubuntu
Importance: Medium => Undecided
** Changed in: ubuntu
Status: Won't
** Summary changed:
- System freeze on high memory usage
+ System freeze on high memory usage when DMA is disabled
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/159356
13 matches
Mail list logo