[Kernel-packages] [Bug 1833281]
On an unrelated note(but since btrfs was thought to be a problem at some point), I've discovered that btrfs with zstd:5 (or worse zstd:15) can cause (at least) mouse cursor stuttering(like it was skipping frames), while zstd:1 doesn't(likely because of the low CPU usage during compression), regardless of how fast/many writes are happening on the SSD(2-6M/s with zstd:15, 38-50+M/s with zstd:1), apparently due to high CPU usage during the compression. (zstd unspecified means zstd:3 aka default) Normal CPU usage by itself(eg. during compiling) doesn't cause such stuttering though. I've tested this on a Lenovo Ideapad Z575, 16G RAM, Kingston SSD SA400S37240G firmware SBFK71F1, and I've personally switched to zstd:1 ie. ``` diff --git a/fs/btrfs/zstd.c b/fs/btrfs/zstd.c index 6b9e29d050f3..02ffdb27c360 100644 --- a/fs/btrfs/zstd.c +++ b/fs/btrfs/zstd.c @@ -22,7 +22,7 @@ #define ZSTD_BTRFS_MAX_WINDOWLOG 17 #define ZSTD_BTRFS_MAX_INPUT (1 << ZSTD_BTRFS_MAX_WINDOWLOG) -#define ZSTD_BTRFS_DEFAULT_LEVEL 3 +#define ZSTD_BTRFS_DEFAULT_LEVEL 1 #define ZSTD_BTRFS_MAX_LEVEL 15 /* 307s to avoid pathologically clashing with transaction commit */ #define ZSTD_BTRFS_RECLAIM_JIFFIES (307 * HZ) ``` but zstd:1 in /etc/fstab should also work, unless using too old kernel that doesn't know about it (hence why I prefer using the patch anyway) -- 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/1833281 Title: System freeze when memory is put on SWAP in Linux >4.10.x Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I'm reporting this since it's reproduceable the 70% of the time. Summary: In different circumstances, when the systems starts to swap out RAM memory, even small amounts, the system becomes completely unusuable and the screen freezes up, no mouse movement, no TTY access or SSH access can be made, only SYSRQ keys seem to do something (only reboot, so REISUB worked so far though, OOM is useless since the memory/swap is not even full) The I/O Disk led is stuck to 100% in ALL the following cases when this happens. So far: - This happens even when only ZRAM is enabled, and no swap partition is used. - Happens when ZSWAP is used with a swap partition - Happens also when a partition without zram or zswap is used - Maybe it's AMD specific? However, I'm not experiencing this on my laptop using the same tests. My laptop is an Intel one, while my desktop is an AMD Ryzen platform. Here are the specs: CPU: AMD Ryzen 5 1600 no OC GPU: AMD RX 580 8GB SSD: Crucial MX500 500GB MOBO: MSI B350M Grenade RAM: 8GB HyperX Kingston 2667Mhz Ubuntu version: 18.04 LTS, backports repo enabled Kernel version: 4.18.0-18, official ubuntu repo Bios settings: Default Additional info: Maybe I'm not 100% sure, but I noticed when using the 5.0.0-17 generic kernel, the lockups seem to still happen, but they recover eventually. Happened only a few times though... But will always be frozen for at least 30 seconds, differently from my intel laptop where those do occur. The SSD make is the same. I bought two of these, they got also the same amount of RAM. In my laptop those do not occur at all. Swapping memory even huge quantities like 1GB or more, do not produce any issues. Tests made: For testing this behaviour I tried: - Compiling the chromium-browser source code (takes up a lot of system RAM) - Used the "stress" command, using a specific amount of memory to decide how many it will be swapped, and here I noticed that even small quantities like a couple of megabytes will cause the system to freeze the 70% of the times Example: "stress --vm 1 --vm-bytes=7G" What should happen: I expect system slowdowns when swapping out memory since I do not have enough RAM, but unlikely when using Windows or my laptop with the same Linux version, not a completely unusuable environment. The swap partition is in both cases on an SSD. Reproduceability: 70% of the times Additional info again: I'm not sure this is due to any hardware failure, my SSD health is fine, as my CPU and RAM. As I said swapping in Windows works fine... --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: haru 2076 F pulseaudio /dev/snd/controlC2: haru 2076 F pulseaudio /dev/snd/controlC0: haru 2076 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic
[Kernel-packages] [Bug 620074]
correction: > In this case it's 1 seconds. *In this case it's 10 seconds. Also, heads up: I found that 'tlp' in `/etc/default/tlp`, on ArchLinux, will overwrite the values set in `/etc/sysctl.d/*.conf` files if these are set to non `0`, ie. MAX_LOST_WORK_SECS_ON_AC=10 MAX_LOST_WORK_SECS_ON_BAT=10 will set: vm.dirty_expire_centisecs=1000 vm.dirty_writeback_centisecs=1000 regardless of what values you set them in `/etc/sysctl.d/*.conf` files. /etc/default/tlp is owned by tlp 1.2.2-1 Not setting those (eg. commenting them out) will have tlp set the to its default of 15 sec (aka =1500). So the workaround is to set them to =0 which makes tlp not set them at all, thus the values from `/etc/sysctl.d/*.conf` files is allowed to remain as set. -- 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/620074 Title: Thrashing turns system unusable Status in Linux: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: Thrashing on Ubuntu seems to make it almost impossible to interact with the system. It can be minutes before any interaction has an effect, including remote connections. This means that if a program either misbehaves or simply needs more memory than available RAM, it might be hard or impossible to stop it, either locally or remotely. This can be both an annoyance and a security threat (since a process without elevated privileges can effectively hang the system). It is not hard to make a system go into thrashing, especially if it is low on memory (that's probably true in general, not only of Ubuntu). On my ASUS netbook running Ubuntu 10.04, with only 1GB RAM, thrashing can occur as easily as running both Chromium (which is a bit of a memory hog) and the Resynthesizer plugin in the GIMP at the same time. Running these programs plus another memory-intensive program like Mathematica can generate thrashing even when 2GB or 4GB of physical memory are available. I am including a short C++ program that allocates and accesses a large amount of memory, guaranteeing thrashing will occur on any system. Using this or any other memory-intensive program, the steps required to reproduce the condition I described are 1. Start one or more memory-intensive programs. 2. As RAM is filled, paging will start, and if the programs try to access the memory that has been swapped out, thrashing occurs. What happens? - Interactivity with the system drops to almost zero. Mouse barely moves, keyboard interaction has huge delays (tens of seconds), starting a terminal or switching to one if one is already open can take minutes, as is the case with remote (e.g. SSH) connections. What I would expect/want to happen? - The system should keep interactivity levels high at all times. While I'm not at all an expert on this, I would think this could be achieved by either not allowing paging out of essential user-interface elements, or more generally by giving processes that generate a lot of page faults comparatively lower priority than other processes, especially processes that are just starting, or are part of the user interface. To use the included program, compile with g++ -o bug bug.cc and run with ./bug where is the amount of memory in MB to be allocated. One can run several instances of the program at the same time, to compete for memory. One can use top, free or the System Monitor to check when RAM is completely filled, and thrashing starts. PS: This seems to be a long-standing issue with Linux, it's not limited to the current version of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-24-generic 2.6.32-24.39 Regression: No Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tibi 1596 F pulseaudio /dev/snd/pcmC0D0p: tibi 1596 F...m pulseaudio /dev/snd/controlC1: tibi 1596 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xfe02 irq 21' Mixer name : 'Nvidia MCP78 HDMI' Components : 'HDA:10ec0888,10250153,00100202 HDA:10de0002,10de0101,0010' Controls : 37 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'U0x46d0x8da'/'USB Device 0x46d:0x8da at usb-:00:04.0-2, full speed' Mixer name : 'USB Mixer' Components : 'USB046d:08da' Controls : 3 Simple ctrls : 2 Date: Wed Aug 18 13:01:30 2010 HibernationDevice: RESUME=UUID=9464cfb9-e39a-46ab-bf3a-01a7f2194ab1 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" -
[Kernel-packages] [Bug 620074]
What's the value of `vm.dirty_writeback_centisecs` ?, ie. $ sysctl vm.dirty_writeback_centisecs try setting it to 0 to disable it, ie. `$ sudo sysctl -w vm.dirty_writeback_centisecs=0` I found that this helps my network transfer not stall/stop at all(for a few seconds when that is =1000 for example) while some kinda of non- async `sync`(command)-like flushing is going on periodically while transferring GiB of data files from sftp to SSD!(via Midnight Commander, on a link limited to 10MiB per second) vm.dirty_writeback_centisecs is how often the pdflush/flush/kdmflush processes wake up and check to see if work needs to be done. Coupled with the above I've been using another value: `vm.dirty_expire_centisecs=1000` for both cases (when stall and not stall), so this one remained fixed to =1000. vm.dirty_expire_centisecs is how long something can be in cache before it needs to be written. In this case it's 1 seconds. When the pdflush/flush/kdmflush processes kick in they will check to see how old a dirty page is, and if it's older than this value it'll be written asynchronously to disk. Since holding a dirty page in memory is unsafe this is also a safeguard against data loss. Well, with the above, at least I'm not experiencing network stalls when copying GiB of data via Midnight Commander's sftp to my SSD until some kernel-caused sync-ing is completed in the background. I don't know if this will work for others, but if curious about any of my other (sysctl)settings, they should be available for perusing [here](https://github.com/howaboutsynergy/q1q/tree/0a2cd4ba658067140d3f0ae89a0897af54da52a4/OSes/archlinux/etc/sysctl.d) -- 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/620074 Title: Thrashing turns system unusable Status in Linux: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: Thrashing on Ubuntu seems to make it almost impossible to interact with the system. It can be minutes before any interaction has an effect, including remote connections. This means that if a program either misbehaves or simply needs more memory than available RAM, it might be hard or impossible to stop it, either locally or remotely. This can be both an annoyance and a security threat (since a process without elevated privileges can effectively hang the system). It is not hard to make a system go into thrashing, especially if it is low on memory (that's probably true in general, not only of Ubuntu). On my ASUS netbook running Ubuntu 10.04, with only 1GB RAM, thrashing can occur as easily as running both Chromium (which is a bit of a memory hog) and the Resynthesizer plugin in the GIMP at the same time. Running these programs plus another memory-intensive program like Mathematica can generate thrashing even when 2GB or 4GB of physical memory are available. I am including a short C++ program that allocates and accesses a large amount of memory, guaranteeing thrashing will occur on any system. Using this or any other memory-intensive program, the steps required to reproduce the condition I described are 1. Start one or more memory-intensive programs. 2. As RAM is filled, paging will start, and if the programs try to access the memory that has been swapped out, thrashing occurs. What happens? - Interactivity with the system drops to almost zero. Mouse barely moves, keyboard interaction has huge delays (tens of seconds), starting a terminal or switching to one if one is already open can take minutes, as is the case with remote (e.g. SSH) connections. What I would expect/want to happen? - The system should keep interactivity levels high at all times. While I'm not at all an expert on this, I would think this could be achieved by either not allowing paging out of essential user-interface elements, or more generally by giving processes that generate a lot of page faults comparatively lower priority than other processes, especially processes that are just starting, or are part of the user interface. To use the included program, compile with g++ -o bug bug.cc and run with ./bug where is the amount of memory in MB to be allocated. One can run several instances of the program at the same time, to compete for memory. One can use top, free or the System Monitor to check when RAM is completely filled, and thrashing starts. PS: This seems to be a long-standing issue with Linux, it's not limited to the current version of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-24-generic 2.6.32-24.39 Regression: No Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: amd64
[Kernel-packages] [Bug 1833281]
Just an idea, try reproducing with kernel patch `le9g.patch`:
```
diff --git a/mm/vmscan.c b/mm/vmscan.c
index dbdc46a84f63..7a0b7e32ff45 100644
--- a/mm/vmscan.c
+++ b/mm/vmscan.c
@@ -2445,6 +2445,13 @@ static void get_scan_count(struct lruvec *lruvec, struct
mem_cgroup *memcg,
BUG();
}
+if (NR_ACTIVE_FILE == lru) {
+ long long kib_active_file_now=global_node_page_state(NR_ACTIVE_FILE) *
MAX_NR_ZONES;
+ if (kib_active_file_now <= 256*1024) {
+nr[lru] = 0; //don't reclaim any Active(file) (see /proc/meminfo) if
they are under 256MiB
+continue;
+ }
+}
*lru_pages += size;
nr[lru] = scan;
}
```
see:
https://gist.github.com/constantoverride/84eba764f487049ed642eb2111a20830#gistcomment-2997481
(^ scroll a bit up for some details of what the patch does)
--
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/1833281
Title:
System freeze when memory is put on SWAP in Linux >4.10.x
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
I'm reporting this since it's reproduceable the 70% of the time.
Summary:
In different circumstances, when the systems starts to swap out RAM
memory, even small amounts, the system becomes completely unusuable
and the screen freezes up, no mouse movement, no TTY access or SSH
access can be made, only SYSRQ keys seem to do something (only reboot,
so REISUB worked so far though, OOM is useless since the memory/swap
is not even full)
The I/O Disk led is stuck to 100% in ALL the following cases when this
happens.
So far:
- This happens even when only ZRAM is enabled, and no swap partition is used.
- Happens when ZSWAP is used with a swap partition
- Happens also when a partition without zram or zswap is used
- Maybe it's AMD specific?
However, I'm not experiencing this on my laptop using the same tests.
My laptop is an Intel one, while my desktop is an AMD Ryzen platform.
Here are the specs:
CPU: AMD Ryzen 5 1600 no OC
GPU: AMD RX 580 8GB
SSD: Crucial MX500 500GB
MOBO: MSI B350M Grenade
RAM: 8GB HyperX Kingston 2667Mhz
Ubuntu version: 18.04 LTS, backports repo enabled
Kernel version: 4.18.0-18, official ubuntu repo
Bios settings: Default
Additional info: Maybe I'm not 100% sure, but I noticed when using the
5.0.0-17 generic kernel, the lockups seem to still happen, but they
recover eventually. Happened only a few times though...
But will always be frozen for at least 30 seconds, differently from my
intel laptop where those do occur.
The SSD make is the same. I bought two of these, they got also the
same amount of RAM.
In my laptop those do not occur at all. Swapping memory even huge
quantities like 1GB or more, do not produce any issues.
Tests made:
For testing this behaviour I tried:
- Compiling the chromium-browser source code (takes up a lot of system
RAM)
- Used the "stress" command, using a specific amount of memory to
decide how many it will be swapped, and here I noticed that even small
quantities like a couple of megabytes will cause the system to freeze
the 70% of the times
Example: "stress --vm 1 --vm-bytes=7G"
What should happen:
I expect system slowdowns when swapping out memory since I do not have enough
RAM, but unlikely when using Windows or my laptop with the same Linux version,
not a completely unusuable environment. The swap partition is in both cases on
an SSD.
Reproduceability: 70% of the times
Additional info again:
I'm not sure this is due to any hardware failure, my SSD health is fine, as
my CPU and RAM. As I said swapping in Windows works fine...
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: haru 2076 F pulseaudio
/dev/snd/controlC2: haru 2076 F pulseaudio
/dev/snd/controlC0: haru 2076 F pulseaudio
CurrentDesktop: communitheme:ubuntu:GNOME
DistroRelease: Ubuntu 18.04
IwConfig:
enp24s0 no wireless extensions.
lono wireless extensions.
MachineType: Micro-Star International Co., Ltd. MS-7A37
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic
root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet
splash vt.handoff=1
ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8
RelatedPackageVersions:
linux-restricted-modules-5.0.0-17-generic N/A
linux-backports-modules-5.0.0-17-generic N/A
linux-firmware1.173.6
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: bionic
Uname: Linux 5.0.0-17-generic x86_64
UpgradeStatus: No
[Kernel-packages] [Bug 988799]
correction: > In this case it's 1 seconds. *In this case it's 10 seconds. Also, heads up: I found that 'tlp' in `/etc/default/tlp`, on ArchLinux, will overwrite the values set in `/etc/sysctl.d/*.conf` files if these are set to non `0`, ie. MAX_LOST_WORK_SECS_ON_AC=10 MAX_LOST_WORK_SECS_ON_BAT=10 will set: vm.dirty_expire_centisecs=1000 vm.dirty_writeback_centisecs=1000 regardless of what values you set them in `/etc/sysctl.d/*.conf` files. /etc/default/tlp is owned by tlp 1.2.2-1 Not setting those (eg. commenting them out) will have tlp set the to its default of 15 sec (aka =1500). So the workaround is to set them to =0 which makes tlp not set them at all, thus the values from `/etc/sysctl.d/*.conf` files is allowed to remain as set. -- 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/988799 Title: Precise freezes under heavy i/o Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Whilst creating a VM with 20 GB persistent HD and my system froze until the disk was created. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-23-generic 3.2.0-23.36 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gema 2526 F pulseaudio /dev/snd/controlC0: gema 2526 F pulseaudio /dev/snd/controlC1: gema 2526 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfbaf8000 irq 52' Mixer name : 'VIA VT1708S' Components : 'HDA:11060397,104383c4,0010' Controls : 45 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'U0x46d0x81d'/'USB Device 0x46d:0x81d at usb-:00:1d.0-1.3, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:081d' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 16 Mono: Capture 12 [75%] [24.00dB] [on] Card2.Amixer.info: Card hw:2 'Generic'/'HD-Audio Generic at 0xfbbfc000 irq 53' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 6 Simple ctrls : 1 Card2.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Thu Apr 26 11:59:11 2012 HibernationDevice: RESUME=UUID=f32abdd2-8167-48c2-9d93-61eeb2632ca0 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) IwConfig: lono wireless extensions. virbr0no wireless extensions. eth0 no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/zsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=109d1e55-4f64-489e-91e8-48ff46f6ba16 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-23-generic N/A linux-backports-modules-3.2.0-23-generic N/A linux-firmware1.79 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to precise on 2012-04-25 (0 days ago) dmi.bios.date: 03/26/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55D-E LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0401:bd03/26/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D-ELX:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/988799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 988799]
What's the value of `vm.dirty_writeback_centisecs` ?, ie. $ sysctl vm.dirty_writeback_centisecs try setting it to 0 to disable it, ie. `$ sudo sysctl -w vm.dirty_writeback_centisecs=0` I found that this helps my network transfer not stall/stop at all(for a few seconds when that is =1000 for example) while some kinda of non- async `sync`(command)-like flushing is going on periodically while transferring GiB of data files from sftp to SSD!(via Midnight Commander, on a link limited to 10MiB per second) vm.dirty_writeback_centisecs is how often the pdflush/flush/kdmflush processes wake up and check to see if work needs to be done. Coupled with the above I've been using another value: `vm.dirty_expire_centisecs=1000` for both cases (when stall and not stall), so this one remained fixed to =1000. vm.dirty_expire_centisecs is how long something can be in cache before it needs to be written. In this case it's 1 seconds. When the pdflush/flush/kdmflush processes kick in they will check to see how old a dirty page is, and if it's older than this value it'll be written asynchronously to disk. Since holding a dirty page in memory is unsafe this is also a safeguard against data loss. Well, with the above, at least I'm not experiencing network stalls when copying GiB of data via Midnight Commander's sftp to my SSD until some kernel-caused sync-ing is completed in the background. I don't know if this will work for others, but if curious about any of my other (sysctl)settings, they should be available for perusing [here](https://github.com/howaboutsynergy/q1q/tree/0a2cd4ba658067140d3f0ae89a0897af54da52a4/OSes/archlinux/etc/sysctl.d) -- 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/988799 Title: Precise freezes under heavy i/o Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Whilst creating a VM with 20 GB persistent HD and my system froze until the disk was created. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-23-generic 3.2.0-23.36 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gema 2526 F pulseaudio /dev/snd/controlC0: gema 2526 F pulseaudio /dev/snd/controlC1: gema 2526 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfbaf8000 irq 52' Mixer name : 'VIA VT1708S' Components : 'HDA:11060397,104383c4,0010' Controls : 45 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'U0x46d0x81d'/'USB Device 0x46d:0x81d at usb-:00:1d.0-1.3, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:081d' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 16 Mono: Capture 12 [75%] [24.00dB] [on] Card2.Amixer.info: Card hw:2 'Generic'/'HD-Audio Generic at 0xfbbfc000 irq 53' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 6 Simple ctrls : 1 Card2.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Thu Apr 26 11:59:11 2012 HibernationDevice: RESUME=UUID=f32abdd2-8167-48c2-9d93-61eeb2632ca0 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) IwConfig: lono wireless extensions. virbr0no wireless extensions. eth0 no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/zsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=109d1e55-4f64-489e-91e8-48ff46f6ba16 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-23-generic N/A linux-backports-modules-3.2.0-23-generic N/A linux-firmware1.79 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to precise on 2012-04-25 (0 days ago) dmi.bios.date: 03/26/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55D-E LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chas
[Kernel-packages] [Bug 336652]
correction: > In this case it's 1 seconds. *In this case it's 10 seconds. Also, heads up: I found that 'tlp' in `/etc/default/tlp`, on ArchLinux, will overwrite the values set in `/etc/sysctl.d/*.conf` files if these are set to non `0`, ie. MAX_LOST_WORK_SECS_ON_AC=10 MAX_LOST_WORK_SECS_ON_BAT=10 will set: vm.dirty_expire_centisecs=1000 vm.dirty_writeback_centisecs=1000 regardless of what values you set them in `/etc/sysctl.d/*.conf` files. /etc/default/tlp is owned by tlp 1.2.2-1 Not setting those (eg. commenting them out) will have tlp set the to its default of 15 sec (aka =1500). So the workaround is to set them to =0 which makes tlp not set them at all, thus the values from `/etc/sysctl.d/*.conf` files is allowed to remain as set. -- 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/336652 Title: Poor system performance under I/O load Status in Linux: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: This bug seems to particularly affect the Dell Latitude D420, D430 and (from the kernel.org bug) at least the D830 laptop models; but others have been reported. Under I/O load, which need not be excessive - running usb-creator or even just checking one's email - the system performs remarkably poorly, far less than other laptop users see. It can often take minutes to open a window, and sometimes the screen isn't repainted. Certainly most applications are "dimmed" by Compiz under I/O. It also appears to massively negatively affect boot performance, with one core spending its entire time in I/O wait - something we don't see elsewhere. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/336652/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 336652]
What's the value of `vm.dirty_writeback_centisecs` ?, ie. $ sysctl vm.dirty_writeback_centisecs try setting it to 0 to disable it, ie. `$ sudo sysctl -w vm.dirty_writeback_centisecs=0` I found that this helps my network transfer not stall/stop at all(for a few seconds when that is =1000 for example) while some kinda of non- async `sync`(command)-like flushing is going on periodically while transferring GiB of data files from sftp to SSD!(via Midnight Commander, on a link limited to 10MiB per second) vm.dirty_writeback_centisecs is how often the pdflush/flush/kdmflush processes wake up and check to see if work needs to be done. Coupled with the above I've been using another value: `vm.dirty_expire_centisecs=1000` for both cases (when stall and not stall), so this one remained fixed to =1000. vm.dirty_expire_centisecs is how long something can be in cache before it needs to be written. In this case it's 1 seconds. When the pdflush/flush/kdmflush processes kick in they will check to see how old a dirty page is, and if it's older than this value it'll be written asynchronously to disk. Since holding a dirty page in memory is unsafe this is also a safeguard against data loss. Well, with the above, at least I'm not experiencing network stalls when copying GiB of data via Midnight Commander's sftp to my SSD until some kernel-caused sync-ing is completed in the background. I don't know if this will work for others, but if curious about any of my other (sysctl)settings, they should be available for perusing [here](https://github.com/howaboutsynergy/q1q/tree/0a2cd4ba658067140d3f0ae89a0897af54da52a4/OSes/archlinux/etc/sysctl.d) -- 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/336652 Title: Poor system performance under I/O load Status in Linux: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: This bug seems to particularly affect the Dell Latitude D420, D430 and (from the kernel.org bug) at least the D830 laptop models; but others have been reported. Under I/O load, which need not be excessive - running usb-creator or even just checking one's email - the system performs remarkably poorly, far less than other laptop users see. It can often take minutes to open a window, and sometimes the screen isn't repainted. Certainly most applications are "dimmed" by Compiz under I/O. It also appears to massively negatively affect boot performance, with one core spending its entire time in I/O wait - something we don't see elsewhere. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/336652/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 595047]
correction:
> In this case it's 1 seconds.
*In this case it's 10 seconds.
Also, heads up:
I found that 'tlp' in `/etc/default/tlp`, on ArchLinux, will overwrite the
values set in `/etc/sysctl.d/*.conf` files if these are set to non `0`, ie.
MAX_LOST_WORK_SECS_ON_AC=10
MAX_LOST_WORK_SECS_ON_BAT=10
will set:
vm.dirty_expire_centisecs=1000
vm.dirty_writeback_centisecs=1000
regardless of what values you set them in `/etc/sysctl.d/*.conf` files.
/etc/default/tlp is owned by tlp 1.2.2-1
Not setting those (eg. commenting them out) will have tlp set the to its
default of 15 sec (aka =1500). So the workaround is to set them to =0
which makes tlp not set them at all, thus the values from
`/etc/sysctl.d/*.conf` files is allowed to remain as set.
--
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/595047
Title:
Frequent swapping causes system to hang
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Incomplete
Bug description:
Periodically I notice my system slows to a near stand still, and the
hard drive light is constantly going. This seems to be a massive
amount of disk i/o and it lasts for a long time (lets say 30 mins to
put a number on it). I installed and ran iotop (`iotop -a`) and it
seems to point to jbd2. From what I can see jbd2 is related to ext4
journaling, but I cannot figure out how to kill this operation. It
might even be a red herring because I have also stopped the disk
activity by kill either chromium or firefox. I need to understand
what else I can do to troubleshoot this.
$ lsb_release -rd
Description: Ubuntu maverick (development branch)
Release: 10.10
Up-to-date as of 16th June 2010.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pgoodall 1372 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0x5644 irq 44'
Mixer name : 'Realtek ALC272X'
Components : 'HDA:10ec0272,1025022c,0011'
Controls : 14
Simple ctrls : 8
DistroRelease: Ubuntu 10.10
Frequency: Once a day.
HibernationDevice: RESUME=UUID=145f27a9-859a-4987-8132-ac878c832747
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100602.2)
MachineType: Acer AO531h
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-6-generic
root=UUID=11f96f8b-5e04-4e20-a201-0fa5d0fc07fa ro quiet splash
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.utf8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-6.9-generic 2.6.35-rc3
Regression: Yes
RelatedPackageVersions: linux-firmware 1.37
Reproducible: No
Tags: maverick ubuntu-une kconfig regression-potential needs-upstream-testing
Uname: Linux 2.6.35-6-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/22/2009
dmi.bios.vendor: Acer
dmi.bios.version: v0.3304
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAcer:bvrv0.3304:bd12/22/2009:svnAcer:pnAO531h:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: AO531h
dmi.product.version: 1
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/595047/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 595047]
What's the value of `vm.dirty_writeback_centisecs` ?, ie.
$ sysctl vm.dirty_writeback_centisecs
try setting it to 0 to disable it, ie.
`$ sudo sysctl -w vm.dirty_writeback_centisecs=0`
I found that this helps my network transfer not stall/stop at all(for a
few seconds when that is =1000 for example) while some kinda of non-
async `sync`(command)-like flushing is going on periodically while
transferring GiB of data files from sftp to SSD!(via Midnight Commander,
on a link limited to 10MiB per second)
vm.dirty_writeback_centisecs is how often the pdflush/flush/kdmflush
processes wake up and check to see if work needs to be done.
Coupled with the above I've been using another value:
`vm.dirty_expire_centisecs=1000`
for both cases (when stall and not stall), so this one remained fixed to =1000.
vm.dirty_expire_centisecs is how long something can be in cache before
it needs to be written. In this case it's 1 seconds. When the
pdflush/flush/kdmflush processes kick in they will check to see how old
a dirty page is, and if it's older than this value it'll be written
asynchronously to disk. Since holding a dirty page in memory is unsafe
this is also a safeguard against data loss.
Well, with the above, at least I'm not experiencing network stalls when
copying GiB of data via Midnight Commander's sftp to my SSD until some
kernel-caused sync-ing is completed in the background.
I don't know if this will work for others, but if curious about any of
my other (sysctl)settings, they should be available for perusing
[here](https://github.com/howaboutsynergy/q1q/tree/0a2cd4ba658067140d3f0ae89a0897af54da52a4/OSes/archlinux/etc/sysctl.d)
--
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/595047
Title:
Frequent swapping causes system to hang
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Incomplete
Bug description:
Periodically I notice my system slows to a near stand still, and the
hard drive light is constantly going. This seems to be a massive
amount of disk i/o and it lasts for a long time (lets say 30 mins to
put a number on it). I installed and ran iotop (`iotop -a`) and it
seems to point to jbd2. From what I can see jbd2 is related to ext4
journaling, but I cannot figure out how to kill this operation. It
might even be a red herring because I have also stopped the disk
activity by kill either chromium or firefox. I need to understand
what else I can do to troubleshoot this.
$ lsb_release -rd
Description: Ubuntu maverick (development branch)
Release: 10.10
Up-to-date as of 16th June 2010.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pgoodall 1372 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0x5644 irq 44'
Mixer name : 'Realtek ALC272X'
Components : 'HDA:10ec0272,1025022c,0011'
Controls : 14
Simple ctrls : 8
DistroRelease: Ubuntu 10.10
Frequency: Once a day.
HibernationDevice: RESUME=UUID=145f27a9-859a-4987-8132-ac878c832747
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100602.2)
MachineType: Acer AO531h
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-6-generic
root=UUID=11f96f8b-5e04-4e20-a201-0fa5d0fc07fa ro quiet splash
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.utf8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-6.9-generic 2.6.35-rc3
Regression: Yes
RelatedPackageVersions: linux-firmware 1.37
Reproducible: No
Tags: maverick ubuntu-une kconfig regression-potential needs-upstream-testing
Uname: Linux 2.6.35-6-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/22/2009
dmi.bios.vendor: Acer
dmi.bios.version: v0.3304
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAcer:bvrv0.3304:bd12/22/2009:svnAcer:pnAO531h:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: AO531h
dmi.product.version: 1
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/595047/+subscriptions
--
Mailing l
