Thrashing turns system unusable

Bug #620074 reported by John Kennedy
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Linux
Fix Released
High
linux (Ubuntu)
Incomplete
Medium
Unassigned

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 <amount of memory>

where <amount of memory> 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:
 USER PID 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 0xfe020000 irq 21'
   Mixer name : 'Nvidia MCP78 HDMI'
   Components : 'HDA:10ec0888,10250153,00100202 HDA:10de0002,10de0101,00100000'
   Controls : 37
   Simple ctrls : 20
Card1.Amixer.info:
 Card hw:1 'U0x46d0x8da'/'USB Device 0x46d:0x8da at usb-0000: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" - Release amd64 (20100429)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: eMachines EL1210-09
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic root=UUID=93f3d657-74ac-4853-acab-704f74ab4cd0 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.1
RfKill:

SourcePackage: linux
dmi.bios.date: 09/23/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: R01-A0
dmi.board.name: WMCP78M
dmi.board.vendor: eMachines
dmi.chassis.asset.tag: 0000000000000000000000
dmi.chassis.type: 3
dmi.chassis.vendor: eMachines
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrR01-A0:bd09/23/2008:svneMachines:pnEL1210-09:pvrR01-A0:rvneMachines:rnWMCP78M:rvr:cvneMachines:ct3:cvr:
dmi.product.name: EL1210-09
dmi.product.version: R01-A0
dmi.sys.vendor: eMachines

Revision history for this message
In , bgamari (bgamari-linux-kernel-bugs) wrote :

This is an attempt at bringing sanity to bug #7372. Please only comment here is you are experiencing high I/O wait times and interactvity on reasonable workloads.

Latest working kernel version: 2.6.18?

Problem Description:
I/O operations on large files tend to produce extremely high iowait times and poor system I/O performance (degraded interactivity). This behavior can be seen to varying degrees in tasks such as,
 - Backing up /home (40GB with numerous large files) with diffbackup to external USB hard drive
 - Moving messages between large maildirs
 - updatedb
 - Upgrading large numbers of packages with rpm

Steps to reproduce:
The best synthetic reproduction case I have found is,
$ dd if=/dev/zero of=/tmp/test bs=1M count=1M
During this copy, IO wait times are very high (70-80%) with extremely degraded interactivity although throughput averages about 29MB/s (about the disk's capacity I think). Even starting a new shell takes minutes, especially after letting the machine copy for a while without being actively used. Could this mean it's a caching issue?

Revision history for this message
In , bgamari (bgamari-linux-kernel-bugs) wrote :

For the record, this is even reproducible with Linus's master.

Revision history for this message
In , ozan (ozan-linux-kernel-bugs) wrote :

I'm also having this problem.

Latest working kernel version: 2.6.18.8 with config:
http://svn.pardus.org.tr/pardus/2007/kernel/kernel/files/pardus-kernel-config.patch

Currently working on 2.6.25.20 with config:
http://svn.pardus.org.tr/pardus/2008/kernel/kernel/files/pardus-kernel-config.patch

Tested also with 2.6.28 and felt no significant performance improvement.

--

During heavy disk IO's like running 'svn up' hogs the system avoiding the start a new shell, browse on the internet, do some text editing using vim, etc.

For example, after being able to open a text buffer with vim, 4-5 seconds delays happens between consecutive search attempts.

Revision history for this message
In , thomas.pi (thomas.pi-linux-kernel-bugs) wrote :
Download full text (3.1 KiB)

Hello Ben,

I don't known where to post it exactly. Why Linux Memory Management? Or why -mm and not mainstream? Can you do it for me please?

I have added a second test case, which using threads with pthread_mutex and pthread_cond instead of processes with pipes for communicating, to ensure it is a cpu scheduler issue.

I have repeated the tests with some vanilla kernels again, as there is a remark in the bug report for tainted or distro kernels. As I got a segmentation fault with the 2.6.28 kernel, I added the result of the Ubuntu 9.04 kernel (see attachment). The results are not comparable to the results posted before, as I have changed the time handling (doubles instead of int32_t as some echo messages takes more than one second).
The first three results are 2*100, 2*50 and 2*20 processes exchanging 100k, 200k and 1M messages over a pipe. The last three results are 2*100, 2*50, and 2*20 threads exchanging 100k, 200k and 1M messages with pthread_mutex and pthread_cond. I have added a 10 second pause at the beginning of every thread/process to assure the 2*100 processes or threads are all created and start to exchange the messages nearby at the same time. This was not the case at the old test-case with 2*100 processes, as the first thread was already destroyed before the last was created.

With the second test-case with threads, I got the problems (threads:2*100/msg:1M) immediately with the kernel 2.6.22.19. There kernel 2.6.20.21 was fine with both test-cases.

The meaning of the results:
- min message time
- average message time (80% of the messages)
- message time at median
- maximal message time
- test duration

Here the result.
Linux balrog704 2.6.20.21 #1 SMP Wed Jan 14 10:11:34 CET 2009 x86_64 GNU/Linux
min:0.000ms|avg:0.241-0.249ms|mid:0.244ms|max:18.367ms|duration:25.304s
min:0.002ms|avg:0.088-0.094ms|mid:0.093ms|max:17.845ms|duration:19.694s
min:0.002ms|avg:0.030-0.038ms|mid:0.038ms|max:564.062ms|duration:38.370s
min:0.002ms|avg:0.004-0.007ms|mid:0.004ms|max:1212.746ms|duration:33.137s
min:0.002ms|avg:0.004-0.005ms|mid:0.004ms|max:1092.045ms|duration:31.686s
min:0.002ms|avg:0.004-0.007ms|mid:0.004ms|max:4532.159ms|duration:59.773s

Linux balrog704 2.6.22.19 #1 SMP Wed Jan 14 10:16:43 CET 2009 x86_64 GNU/Linux
min:0.003ms|avg:0.394-0.413ms|mid:0.403ms|max:19.673ms|duration:42.422s
min:0.003ms|avg:0.083-0.188ms|mid:0.182ms|max:13.405ms|duration:37.038s
min:0.003ms|avg:0.056-0.075ms|mid:0.070ms|max:656.112ms|duration:72.943s
min:0.003ms|avg:0.005-0.010ms|mid:0.007ms|max:1756.113ms|duration:49.163s
min:0.003ms|avg:0.005-0.010ms|mid:0.007ms|max:11560.976ms|duration:52.836s
min:0.003ms|avg:0.008-0.010ms|mid:0.010ms|max:5316.424ms|duration:111.323s

Linux balrog704 2.6.24.7 #1 SMP Wed Jan 14 10:21:04 CET 2009 x86_64 GNU/Linux
min:0.003ms|avg:0.223-0.450ms|mid:0.428ms|max:8.494ms|duration:46.123s
min:0.003ms|avg:0.140-0.209ms|mid:0.200ms|max:12.514ms|duration:39.100s
min:0.003ms|avg:0.068-0.084ms|mid:0.076ms|max:38.778ms|duration:78.157s
min:0.003ms|avg:0.454-0.784ms|mid:0.625ms|max:11.063ms|duration:65.619s
min:0.004ms|avg:0.244-0.399ms|mid:0.319ms|max:21.018ms|duration:64.741s
min:0.003ms|avg:0.061-0.138ms|mid:0.111ms|max:23.861ms|durati...

Read more...

Revision history for this message
In , thomas.pi (thomas.pi-linux-kernel-bugs) wrote :

Created attachment 19795
test case with processes and pipes

Revision history for this message
In , thomas.pi (thomas.pi-linux-kernel-bugs) wrote :

Created attachment 19796
test case with threads and mutexes

Revision history for this message
In , thomas.pi (thomas.pi-linux-kernel-bugs) wrote :

Created attachment 19797
All testresult on Core2 T7700 @ 2.40GHz / 4GB RAM

Revision history for this message
In , thomas.pi (thomas.pi-linux-kernel-bugs) wrote :

I guess the high I/O wait time and the poor responsiveness are the same problem, caused by the cpu scheduler, as I can produce the same symptoms without disc I/O.
Since 2.6.26/27 everyone should be affected by this issue.

What I did not understand is:
Why takes the test with threads and mutexes twice as long as the test with processes and pipes, but stresses the system much more? The mouses freezes nearby immediately, while the test with processes and pipes allows to move the windows.

Revision history for this message
In , l.wandrebeck (l.wandrebeck-linux-kernel-bugs) wrote :

I've met the high I/O wait problem with 3ware cards on Centos 5.x.
This is related to pci_try_set_mwi. More information here:
https://bugzilla.redhat.com/show_bug.cgi?id=444759
Now Thomas seems to have found another source for the problem. Maybe mwi is adding on top of that (not every controller driver sets MWI - BIOS is supposed to do so, but I've met a couple of boards that do not).
HTH.

Revision history for this message
In , rick.richardson (rick.richardson-linux-kernel-bugs) wrote :

If I run "google desktop indexer", then I get the long waits. E.G. vim goes away for up to 5-30 seconds, repeatably!

So, I don't run "google desktop indexer". No problem since 12/15/08!

Revision history for this message
In , humufr (humufr-linux-kernel-bugs) wrote :

You can also add the task:

- copy a file from a compactflash card through usb adaptor or pcmcia card. The
computer is not usable until the copy of the file (3 to 5 megas) is finish. It
doesn't matter if it copy the whole card or only a file. It seems to be similar
to the description of the bug here.

Revision history for this message
In , unixg33k (unixg33k-linux-kernel-bugs) wrote :

I have found that this may be an issue with the Complete Fair Queuing I/O scheduler that was introduced as default in 2.6.18 (when most started observing this performance issue). Reverting back to the old AS scheduler for me seems to have resolved the problem.

To use the AS scheduler and test for yourself, just specify "elevator=as" as a boot option.

Revision history for this message
In , brice+lklm (brice+lklm-linux-kernel-bugs) wrote :

(In reply to comment #2)
> I'm also having this problem.
>
> Latest working kernel version: 2.6.18.8 with config:
>
> http://svn.pardus.org.tr/pardus/2007/kernel/kernel/files/pardus-kernel-config.patch
>
> Currently working on 2.6.25.20 with config:
>
> http://svn.pardus.org.tr/pardus/2008/kernel/kernel/files/pardus-kernel-config.patch
>
> Tested also with 2.6.28 and felt no significant performance improvement.
>
> --
>
> During heavy disk IO's like running 'svn up' hogs the system avoiding the
> start
> a new shell, browse on the internet, do some text editing using vim, etc.
>
> For example, after being able to open a text buffer with vim, 4-5 seconds
> delays happens between consecutive search attempts.

You seem to be able to reproduce the bug easily, and have found a non affected kernel version.
Can you git bisect between those kernels to at least isolate the culprit commit?

Revision history for this message
In , brice+lklm (brice+lklm-linux-kernel-bugs) wrote :

(In reply to comment #3)
>
> With the second test-case with threads, I got the problems
> (threads:2*100/msg:1M) immediately with the kernel 2.6.22.19. There kernel
> 2.6.20.21 was fine with both test-cases.

I'm not sure that's the same issue I had when I posted but 7372, but since you seem to be a programmer you should git bisect between those kernels to isolate the culprit commit.

Revision history for this message
In , pvz (pvz-linux-kernel-bugs) wrote :

I'm not sure if this is related or not, but I'm getting similar behaviour on my own system, but *only* when copying files *from* my USB memory stick (a 4 GB Corsair Flash Voyager) *to* the internal SSD on my Asus Eee PC 900 running Ubuntu 8.10 with a custom build of Linux 2.6.27 (probably slightly patched) provided by array.org.

I.e. reading a file from the USB stick to /dev/null, no slowdown.
Writing /dev/zero to USB stick, no slowdown.
Reading a file from the internal SSD to /dev/null, no slowdown.
Writing /dev/zero to internal SSD, no slowdown.
Copying a file from internal SSD to USB stick, no slowdown.
Copying a file from USB stick to internal SSD, I get massive slowdowns on interactive performance. Launching a terminal, which usually takes a few seconds, suddenly takes the better part of a minute.

Linux used is 2.6.27-8-eeepc on i686 SMP, as prebuilt by http://www.array.org/ubuntu/

The filesystem on the internal SSD is ext3, running on LVM, running on LUKS (encrypted filesystem). As set up by the Ubuntu 8.10 installer. Swap is also on the same encrypted LVM.

The filesystem on the USB stick is vfat. Nothing fancy at all.

I should also add that the read performance of my USB stick is faster (about 25 MB/s) than the write performance on the built-in SSD (about 10 MB/s).

If you feel that it is useful, I can provide dumps of lspci/lsusb/lsmod or any other information. As for the exact build options and patches, that should be determinable by checking the web site specified above.

Hope more data makes it possible to determine a pattern to this bug.

Revision history for this message
In , humufr (humufr-linux-kernel-bugs) wrote :

I tried the solution of Mike the comment http://bugzilla.kernel.org/show_bug.cgi?id=12309#c11 and indeed that solved my issue. So he seens that he is right at least for my problem.

Revision history for this message
In , pvz (pvz-linux-kernel-bugs) wrote :

I tried elevator=as on my system, and it did not change the behaviour. Copying files from external USB to internal encrypted SSD still totally smashes interactive performance. So this issue might be unrelated.

Revision history for this message
In , unixg33k (unixg33k-linux-kernel-bugs) wrote :

(In reply to comment #16)
> I tried elevator=as on my system, and it did not change the behaviour.
> Copying
> files from external USB to internal encrypted SSD still totally smashes
> interactive performance. So this issue might be unrelated.
>

This may be an unrelated issue having to do with USB I/O - since USB seems to be more CPU intensive anyway.

When I experienced this bug (prior to switching from CFQ), it would happen whenever I copied a large file on ATA or SCSI devices and I noticed extremely high I/O wait times - with very low CPU usage. Not only during copying - but during any disk-intensive operation. Everything on my affected machines would come to a grinding halt until the operation was complete. Using AS for me so far has seemed to resolve the issue - as my machines are now responsive as they should be during heavy disk I/O.

Revision history for this message
In , bpenglase (bpenglase-linux-kernel-bugs) wrote :

I have had a very similar problem to this. I still have it often, but not as
much from when I changed from EXT3 to ReiserFS. For the Scheduler, I've been
using BFQ or V(R) thats included in the Zen Patchset. I have tried the stock
kernel, and same problem exists, however I can't remember which scheduler I
used at that point, I believe Deadline.
Most of the IOWait I get comes when either I'm copying files to the local
drives, or using multiple VM's (generally Windows as thats what is needed for
work). I'm willing to try about anything to get this fixed. It's a little
better since I switched FS's on my VM Drive, but still isn't totally fixed.

Revision history for this message
In , kernel (kernel-linux-kernel-bugs) wrote :

(In reply to comment #11)
> I have found that this may be an issue with the Complete Fair Queuing I/O
> scheduler that was introduced as default in 2.6.18 (when most started
> observing
> this performance issue). Reverting back to the old AS scheduler for me seems
> to have resolved the problem.
>
> To use the AS scheduler and test for yourself, just specify "elevator=as" as
> a
> boot option.
>

Fwiw, I've never used the CFQ scheduler. I'm on the deadline scheduler with my 3ware 9560SE and still see this problem crop up from time to time, usually when doing a file copy large enough to fill the page cache.

Revision history for this message
In , bgamari (bgamari-linux-kernel-bugs) wrote :

I too have found that the choice of I/O scheduler makes little difference. Using AS generally yields no noticable improvement.

Revision history for this message
In , funtoos (funtoos-linux-kernel-bugs) wrote :

>
> Fwiw, I've never used the CFQ scheduler. I'm on the deadline scheduler with
> my
> 3ware 9560SE and still see this problem crop up from time to time, usually
> when
> doing a file copy large enough to fill the page cache.
>

Another deadliner here. And the same thing. There are two clear cut triggers for me:

1. The test case thomas posted.
2. large copies which fill up page cache.

I think its a process scheduling bug because page cache fill up might be triggering the pdflush processes (which are btw, normal priority. why?) into hyper drive and causing all other processes to wait. We do see various processes going into 'D' state and pdflush at the top of the cpu usage list, when the symptoms occur.

If CFQ is used, and process priority determines IO priority, aren't pdflush processes going to compete with processes doing their own IO when dirty_ratio is reached and the process has priority equal or better than 0 (-1 and higher)? That may explain some of the stories with CFQ here.

Revision history for this message
In , andi-bz (andi-bz-linux-kernel-bugs) wrote :

Re: blaming the scheduler in 2.6.26

The problem was observed a long time before that. There might be additional
scheduler problems (this bug in general suffers from the "lots of different problems" disease), but that is unlikely to be the old well known disk starvation with different devices issue.

Re comment #9 vim stalls while disk is pounded:

You're running ext3 or reiser right? That's a known problem in that vim
regularly does fsync on its auto safe file and that causes a synchronous
JBD transaction and since all transactions are strictly ordered if there
are enough of them in front and the disk is busy it takes quite a long time.

At least on the higher level that is supposed to be mostly solved by ext4
or by XFS.

Of course it's another problem that the disk schedulers allow that long starvation in the first time.

Revision history for this message
In , theparanoidone (theparanoidone-linux-kernel-bugs) wrote :
Download full text (7.3 KiB)

Hi Thomas~

Can you elaborate on your test?

You wrote:
"The first three results are 2*100, 2*50 and 2*20 processes exchanging 100k,
200k and 1M messages over a pipe. The last three results are 2*100, 2*50, and
2*20 threads exchanging 100k, 200k and 1M messages with pthread_mutex and
pthread_cond."

So, I'm guessing you want the test to be run like this:
./processtest 200 100000
./processtest 100 200000
./processtest 40 1000000
./threadtest 200 100000
./threadtest 100 200000
./threadtest 40 1000000

Is that correct? Just want to be sure i'm running the same tests (Also, the code limits number of processes to max 100... so I just edited this allowing the max limit to be 200)

Here's our results:

2.6.15.7-ubuntu1-custom-1000HZ_CLK #1 SMP Thu Jan 15 19:06:30 PST 2009 x86_64 GNU/Linux (ubuntu 6.06.2 server LTS with clk_hz set to 1000HZ)
min:0.004ms|avg:0.004-0.271ms|mid:0.005ms|max:42.049ms|duration:34.029s
min:0.004ms|avg:0.004-0.138ms|mid:0.035ms|max:884.865ms|duration:33.105s
min:0.004ms|avg:0.004-0.042ms|mid:0.004ms|max:2319.621ms|duration:62.438s
min:0.005ms|avg:0.010-0.026ms|mid:0.012ms|max:1407.923ms|duration:92.132s
min:0.005ms|avg:0.011-0.029ms|mid:0.013ms|max:1539.929ms|duration:97.034s
min:0.005ms|avg:0.010-0.031ms|mid:0.013ms|max:18669.095ms|duration:176.555s

2.6.24-23-server #1 SMP Thu Nov 27 18:45:02 UTC 2008 x86_64 GNU/Linux (default ubuntu 64 8.04 server LTS at default 100HZ clock)
min:0.004ms|avg:0.034-0.357ms|mid:0.324ms|max:39.789ms|duration:43.390s
min:0.004ms|avg:0.006-0.149ms|mid:0.131ms|max:79.430ms|duration:39.288s
min:0.004ms|avg:0.046-0.057ms|mid:0.052ms|max:52.427ms|duration:64.481s
min:0.005ms|avg:0.006-0.650ms|mid:0.330ms|max:22.120ms|duration:60.142s
min:0.005ms|avg:0.053-0.309ms|mid:0.276ms|max:21.560ms|duration:62.353s
min:0.004ms|avg:0.033-0.123ms|mid:0.112ms|max:22.007ms|duration:131.029s

Linux la 2.6.24.6-custom #1 SMP Thu Jan 15 23:34:10 UTC 2009 x86_64 GNU/Linux (ubuntu 8.04 server LTS with clk_hz custom set to 1000HZ)
min:0.004ms|avg:0.054-0.364ms|mid:0.332ms|max:24.524ms|duration:42.522s
min:0.004ms|avg:0.125-0.156ms|mid:0.144ms|max:13.171ms|duration:33.573s
min:0.004ms|avg:0.046-0.058ms|mid:0.052ms|max:13.005ms|duration:64.388s
min:0.005ms|avg:0.006-0.594ms|mid:0.302ms|max:13.481ms|duration:61.105s
min:0.005ms|avg:0.109-0.336ms|mid:0.307ms|max:13.345ms|duration:65.000s
min:0.002ms|avg:0.070-0.130ms|mid:0.120ms|max:13.137ms|duration:133.786s

Side notes... we have been experiencing problems with MySQL specifically with sync-binlog=1 and log-bin on and performing high volume of concurrent transactions. Although we run raid-1 with battery cache on... our throughput is horrible. For some reason, we have found that by increasing the CONFIG_HZ=1000 from 100 in the kernel, we get much higher throughput. Otherwise our benchmarks just sit around and have trouble context switching.

#CONFIG_HZ_100=y
#CONFIG_HZ=100
#change to:
CONFIG_HZ_1000=y
CONFIG_HZ=1000

I do not know if the problems we are experiencing with the clock are related to this bug listed here. However, I did want to submit our feed back showing the difference in kernels where our bottleneck runs better.

We use sysbench for our test (wi...

Read more...

Revision history for this message
In , pvz (pvz-linux-kernel-bugs) wrote :

Did some more testing. My father has an Eee PC 900 exactly the same as mine also running Ubuntu 8.10 with the same kernel as mentioned before. Only difference that I can think of - he doesn't use LUKS and LVM like me, he instead has his / directly on /dev/sdb1 (internal SSD).

I also, in addition to trying to launch a Terminal via Gnome (as I did previously) I tried the vim "stuttering" test by creating a file, saving it, and holding down a key to see when it stutters.

The results of these tests:

- On both my own (encypted) and the other (unencrypted) computer, vim occasionally freezes for a few seconds while I cp a file from USB memory to internal SSD.

- On my computer (encrypted) lauching a gnome-terminal takes much longer while copying a file from SSD than on the other computer. While there is a noticable slowdown on the unencrypted machine, on the encrypted machine sometimes the gnome-terminal won't even launch until *after* the copy is complete.

In conclusion - the effect exists on both machines, but the encryption of the SSD very significantly increases the problem. While some slowdown due to encryption should be expected, it should not make the machine almost completely unusable while copying a file from a USB stick to the internal SSD.

Revision history for this message
In , larppaxyz (larppaxyz-linux-kernel-bugs) wrote :

Different scheduler (#11) doesn't seem to do much. I did some quick and dirty testing with my laptop :

Linux lupaus 2.6.28-customlupaus #4 SMP PREEMPT Thu Dec 25 15:05:35 EET 2008 x86_64 GNU/Linux
Vanilla 2.6.28 kernel, config from Ubuntu 8.10, with some modifications to suit my laptop

with io scheduler cfq
./threadtest 100 200000
min:0.004ms|avg:0.007-0.008ms|mid:0.008ms|max:894.480ms|duration:187.588s

with elevator=as (eg. io scheduler anticipatory)
./threadtest 100 200000
min:0.004ms|avg:0.007-0.008ms|mid:0.008ms|max:884.016ms|duration:188.248s

---

with io scheduler cfq
./proctest 50 100000
min:0.005ms|avg:0.005-0.006ms|mid:0.006ms|max:460.631ms|duration:35.773s

with elevator=as (eg. io scheduler anticipatory)
./proctest 50 100000
min:0.005ms|avg:0.006-0.006ms|mid:0.006ms|max:479.695ms|duration:36.645s

Revision history for this message
In , pvz (pvz-linux-kernel-bugs) wrote :

One more observation from another experiment I did:

I have swap on the same encrypted LVM as my root partition. Disabling swap makes the terminal launch much faster while copying -- still slower than when not copying files, but within a few seconds of clicking instead of within minutes.

However! Now, instead individual running processes (like Firefox and vim) hang much more agressively and frequently during copying. I'm not sure what to make of this, but I hope somebody who actually knows something about the Linux kernel will find this useful. :-)

Revision history for this message
In , nalimilan (nalimilan-linux-kernel-bugs) wrote :

I'm not sure any developer will be able to pinpoint the problem in all this mess! ;-) There are likely several bugs here.

For a start, I think it could be nice to separate people whose problem is fixed by elevator=as. And then separate people using encrypted disks. And then problems occurring only with USB disks. Please open new reports. What do developers think?

38 comments hidden view all 711 comments
Revision history for this message
John Kennedy (legendre17) wrote :
Revision history for this message
John Kennedy (legendre17) wrote :
visibility: private → public
Revision history for this message
bbordwell (benbordwell) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in Linux 2.6.36-rc1 (http://lkml.org/lkml/2010/8/1/40). It won't be fixed in previous versions of Ubuntu because the package doesn't fit the requirements for backporting. See https://help.ubuntu.com/community/UbuntuBackports for more information.

Changed in linux (Ubuntu):
status: New → Fix Released
Revision history for this message
Ole Laursen (olau) wrote :

Sorry to jump in like this, but I had the previous bug about this open for many years, and it was closed for no good reason several times (by people who never bothered to try reproducing it), so I remain a bit sceptical. bbordwell: Did you try reproducing the problem with the new kernel? Have you confirmed that the problem is gone?

If not, would you please reopen this bug?

The email you link to seems to indicate that it is merely fixing a problem introduced a year ago. This problem is much, much older. I first experienced it at least ten years ago.

Revision history for this message
Olafur Arason (olafura) wrote :

bbordwell you cant "Fix released" unless you are going to backport the patch to the current unstable ( Maverick 2.6.35 ).

Changed in linux (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
bbordwell (benbordwell) wrote :

@olafur: ok sorry, I just know the code for this fix is not easily backported and it is a rather large change so I doubt it will get backported so I was not 100% sure what to do.

@Ole, I have not personaly tested it but here are reports of it working: http://www.phoronix.com/scan.php?page=news_item&px=ODQ3OQ

Also Some unresponsiveness is to be expected under low memory/high i/o no matter what, it is a hardware issue not a software one. At its current state it is just much more excessive than it should be.

Revision history for this message
John Kennedy (legendre17) wrote :

Thanks bbordwell, I'm looking forward to trying this patch.

Actually, maybe I should already know this, but do you know when kernel 2.6.36 should become available to Ubuntu users through the usual upgrade procedures?

Revision history for this message
bbordwell (benbordwell) wrote :

A 2.6.36+ kernel will not be officially available until natty narwhal. It does not look like it is available now but check http://kernel.ubuntu.com/~kernel-ppa/mainline/ you can usually easily install newer kernels using this ppa.

Revision history for this message
Anders Hall (kallebolle) wrote :

Might be related: Bug #689787

Changed in linux:
status: Unknown → Confirmed
Changed in linux:
importance: Unknown → High
security vulnerability: yes → no
Changed in linux:
status: Confirmed → Fix Released
Revision history for this message
Phill (phill.l) wrote :

Are we sure this has been fixed?

I'm on 13.04 and it certainly becomes unusable when a program gets hungry (usually it'll be Firefox or, unrelated, something using python). I've used all the recent Ubuntu's and they've all suffered from it, no exception. What's worse is that switching and logging into another terminal to kill the problem takes ages too, gets stuck loggin in for minutes. Mouse doesn't move at all, never mind being sluggish.

Revision history for this message
Ole Laursen (olau) wrote :

It's probably not fixed. bbordwell who closed it never bothered to test what he believed would be a fix, as far as I can tell. He just went with something he thought might be related that he read on Phoronix.

On the previous bug #27441 on this matter I provided a simple test program you can compile and use to reproduce the problem. I don't if that still reproduces it, but you can give it a try.

BUT before you waste your breath and try reopening this, note that I reported that old bug many years ago, and it was closed repeatedly by people who never bothered to actually think about the problem. After 5 years, Tim Gardner came by, didn't read the description properly (so it seems from his closing remark) or tried my test program and closed it for good.

So I would recommend against reopening. If you want to see this fixed, try to get some developers on the kernel mailing list interested in the problem. If you could get a solid test case going, e.g. with a VM with constrained memory and a simple script or program to run, I guess some people might see it as a fun challenge. Over the years I've come to the conclusion that the people in the other end of this bug tracker probably see it as a low-priority, long-running, hard-to-fix annoyance, and that's not the right starting point.

penalvch (penalvch)
tags: added: latest-bios-r01-a0 lucid needs-upstream-testing
removed: paging thrashing
Revision history for this message
penalvch (penalvch) wrote :

John Kennedy, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc3

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
659 comments hidden view all 711 comments
Revision history for this message
In , zvova7890 (zvova7890-linux-kernel-bugs) wrote :

Created attachment 274511
Per deice dirty ration configuration support

Per device dirty bytes configuration

Revision history for this message
In , zvova7890 (zvova7890-linux-kernel-bugs) wrote :

Per device dirty bytes configuration. Patch is not ideal, i'm make it for smoothly flash drive wriring by passing smaller value of dirty byte per removeable device.

>> Path
# ls /sys/block/sdc/bdi/
dirty_background_bytes dirty_background_ratio dirty_bytes dirty_ratio max_ratio min_pages_to_flush min_ratio power read_ahead_kb stable_pages_required subsystem uevent

>> udev Rule for removeables device
# cat /etc/udev/rules.d/90-dirty-flash.rules
ACTION=="add|change", KERNEL=="sd[a-z]", ATTR{removable}=="1", ATTR{bdi/dirty_bytes}="4194304"

Revision history for this message
In , castro8583bennett (castro8583bennett-linux-kernel-bugs) wrote :

Hello Ben,

I was trying to figure out the issue but not really sure what exactly the error here. Is the bug fixed already? Or do we have some sources that maybe help us? Thank you

Carlo B.
https://bondereduction.ci/

Revision history for this message
In , chriswy27 (chriswy27-linux-kernel-bugs) wrote :

Was this bug actually fixed? The status shows CLOSED CODE_FIX with a last modified date of Dec 5 2018. I don't see any updates as to what was corrected, and what version the fix will be put into?

Revision history for this message
In , gatekeeper.mail (gatekeeper.mail-linux-kernel-bugs) wrote :

Created attachment 282477
attachment-6179-0.html

This was never fixed and since bug state cheating with no commit info ever
provided even if asked directly, will never be fixed. Nobody just cares and
I guess nobody even figured out who broke the kernel by which changeset and
when. Just buy another couple of Xeons for your zupa-dupa web-serfing
desktop and pray it's enough for loads of waits when you format your
diskette. Another approach is to buy enough ram to hold whole your block
devices set there so write-outs are quick enough and you won't see
microsecond lags. This is complete workaround list they provided since the
bug opened.

вт, 23 апр. 2019 г., 18:21 <email address hidden>:

> https://bugzilla.kernel.org/show_bug.cgi?id=12309
>
> protivakid (<email address hidden>) changed:
>
> What |Removed |Added
>
> ----------------------------------------------------------------------------
> CC| |<email address hidden>
>
> --- Comment #663 from protivakid (<email address hidden>) ---
> Was this bug actually fixed? The status shows CLOSED CODE_FIX with a last
> modified date of Dec 5 2018. I don't see any updates as to what was
> corrected,
> and what version the fix will be put into?
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

Revision history for this message
In , vi0oss (vi0oss-linux-kernel-bugs) wrote :

As far as I understand, this is kind of meta-bug: there are multiple causes and multiple fixes.

"I do bulk IO and it gets slow" sounds rather general, and problem that can resurface anytime due to some new underlying issue. So the problem cannot be really "closed for good" no matter how much technical progress is made.

For me 12309 basically stopped happening unless I deliberately tune "/proc/sys/vm/dirty_*" values to non-typical ranges and forgot to revert them back. I see system controllably slowing down processes doing bulk IO so the system in general stays reasonable. This behaviour is one of outcomes of this bug.

I don't expect meaningful technical discussion to be happen in this thread. It should just serve as a hub for linking to specific new issues.

Revision history for this message
In , powerman-asdf (powerman-asdf-linux-kernel-bugs) wrote :

Sure it's a meta bug, but for me 12309 is still actual, and I don't use any tuning for I/O subsystem at all.

Not as bad as years ago when it happens for the first time, but I still have to throttle rtorrent to download at 2.5MB/sec maximum instead of usual 10MB/s if I like to view films in mplayer at same time without jitter/freeze/lag. And that's on powerful and modern enough system with kernel 4.19.27, CPU i7-2600K @ 4.5GHz, RAM 24GB, and HDD 3TB Western Digital Caviar Green WD30EZRX-00D. This is annoying, and I remember time before 12309 when rtorrent without any throttling won't make mplayer to freeze on less powerful hardware.

Revision history for this message
In , gatekeeper.mail (gatekeeper.mail-linux-kernel-bugs) wrote :

Created attachment 282483
attachment-22369-0.html

Well, I've tried to report a new bug to investigate my own "my CPU does
nothing because waiting is too hard for it". Of no interest of any kernel
dev. So, just as Linus once said "f**k you Nvidia", the very same goes back
to linux itself. Pity some devs think that make their software linux-bound
(via udev only binding or alsa only sound out) is a good idea (gnome and
even parts of KDE). They forgot 15 years ago they picketed Adobe for having
flash for win only. Now one has to use 12309-bound crap for not having a
way to run his software on another platform.

вт, 23 апр. 2019 г., 21:29 <email address hidden>:

> https://bugzilla.kernel.org/show_bug.cgi?id=12309
>
> --- Comment #665 from _Vi (<email address hidden>) ---
> As far as I understand, this is kind of meta-bug: there are multiple
> causes and
> multiple fixes.
>
> "I do bulk IO and it gets slow" sounds rather general, and problem that can
> resurface anytime due to some new underlying issue. So the problem cannot
> be
> really "closed for good" no matter how much technical progress is made.
>
> For me 12309 basically stopped happening unless I deliberately tune
> "/proc/sys/vm/dirty_*" values to non-typical ranges and forgot to revert
> them
> back. I see system controllably slowing down processes doing bulk IO so the
> system in general stays reasonable. This behaviour is one of outcomes of
> this
> bug.
>
> I don't expect meaningful technical discussion to be happen in this
> thread. It
> should just serve as a hub for linking to specific new issues.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

Revision history for this message
In , mpartap (mpartap-linux-kernel-bugs) wrote :

Can 'someone' please open a bounty on creation of a VM test case, f.e. with `vagrant` or `phoronix test suite`?
Basically, a way to reproduce and quantify the perceived/actual performance difference between
> Linux 2.6.17 Released 17 June, 2006
and
> Linux 5.0 Released Sun, 3 Mar 2019

(In reply to Alex Efros from comment #666)
> Not as bad as years ago […]
> And that's on powerful and modern enough system with
> kernel 4.19.27, CPU i7-2600K @ 4.5GHz, RAM 24GB, and HDD 3TB […]
> This is annoying, and I remember time before
> 12309 when rtorrent without any throttling won't make mplayer to freeze on
> less powerful hardware.

Oh yeah, this... i can clearly remember back then when on a then mid-range machine with a lot of compiling (gentoo => 100% cpu �[U+1F923]�) and filesystem work, VLC used to play an HD video stream even under heavy load without any hiccups and micro-stuttering.. It was impressive at the time.. and then.. it broke �[U+1F928]�

Revision history for this message
In , luciamandela55 (luciamandela55-linux-kernel-bugs) wrote :
Revision history for this message
In , luciamandela55 (luciamandela55-linux-kernel-bugs) wrote :
Revision history for this message
In , vitaly.v.ch (vitaly.v.ch-linux-kernel-bugs) wrote :

According to my attempts to fix this bug, I totally disagree with you.

This bug is caused by pure design of current block dev layer. Methods which are good to develop code is absolutely improper for developing ideas. It's probably the key problem of the Linux Comunity. Currently, there is merged WA for block devices with a good queue such as Samsung Pro NVMe.

WBR,

Vitaly

(In reply to _Vi from comment #665)
> As far as I understand, this is kind of meta-bug: there are multiple causes
> and multiple fixes.
>
> "I do bulk IO and it gets slow" sounds rather general, and problem that can
> resurface anytime due to some new underlying issue. So the problem cannot be
> really "closed for good" no matter how much technical progress is made.
>
> For me 12309 basically stopped happening unless I deliberately tune
> "/proc/sys/vm/dirty_*" values to non-typical ranges and forgot to revert
> them back. I see system controllably slowing down processes doing bulk IO so
> the system in general stays reasonable. This behaviour is one of outcomes of
> this bug.
>
> I don't expect meaningful technical discussion to be happen in this thread.
> It should just serve as a hub for linking to specific new issues.

Revision history for this message
In , todorovic.s (todorovic.s-linux-kernel-bugs) wrote :

Had this again 20 minutes ago.
Was dopying 8.7GiB of data from one directory to another directory on the same filesystem (ext4 (rw,relatime,data=ordered)) on the same disk (Western Digital WDC WD30EZRX-00D8PB0 spinning metal disk).

The KDE UI became unresponsive (Everything other than /home and user data in on a SSD), could not launch any new applications. Opening a new tab on Firefox to go to Youtube didnt load the page, and kept saying waiting for youtube.com in the status bar (network gets halted?).

dmesg shows these, are they important?

[25013.905943] INFO: task DOMCacheThread:17496 blocked for more than 120 seconds.
[25013.905945] Tainted: P OE 4.15.0-54-generic #58-Ubuntu
[25013.905947] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[25013.905949] DOMCacheThread D 0 17496 2243 0x00000000
[25013.905951] Call Trace:
[25013.905954] __schedule+0x291/0x8a0
[25013.905957] schedule+0x2c/0x80
[25013.905959] jbd2_log_wait_commit+0xb0/0x120
[25013.905962] ? wait_woken+0x80/0x80
[25013.905965] __jbd2_journal_force_commit+0x61/0xb0
[25013.905967] jbd2_journal_force_commit+0x21/0x30
[25013.905970] ext4_force_commit+0x29/0x2d
[25013.905972] ext4_sync_file+0x14a/0x3b0
[25013.905975] vfs_fsync_range+0x51/0xb0
[25013.905977] do_fsync+0x3d/0x70
[25013.905980] SyS_fsync+0x10/0x20
[25013.905982] do_syscall_64+0x73/0x130
[25013.905985] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[25013.905987] RIP: 0033:0x7fc9cb839b07
[25013.905988] RSP: 002b:00007fc9a7aeb200 EFLAGS: 00000293 ORIG_RAX: 000000000000004a
[25013.905990] RAX: ffffffffffffffda RBX: 00000000000000a0 RCX: 00007fc9cb839b07
[25013.905992] RDX: 0000000000000000 RSI: 00007fc9a7aeaff0 RDI: 00000000000000a0
[25013.905993] RBP: 0000000000000000 R08: 0000000000000000 R09: 72732f656d6f682f
[25013.905994] R10: 0000000000000000 R11: 0000000000000293 R12: 00000000000001f6
[25013.905995] R13: 00007fc97fc5d038 R14: 00007fc9a7aeb340 R15: 00007fc987523380

Revision history for this message
In , alpha_one_x86 (alphaonex86-linux-kernel-bugs) wrote :

KDE have problem too, same copy via CLI or via Ultracopier (GUI) have no problem.
I note too KDE have UI more slow, plasma doing CPU usage in case I use the HDD...

Revision history for this message
In , howaboutsynergy (howaboutsynergy-linux-kernel-bugs) wrote :

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)

Revision history for this message
In , howaboutsynergy (howaboutsynergy-linux-kernel-bugs) wrote :

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.

Brad Figg (brad-figg)
tags: added: cscc
Revision history for this message
In , davidguptil05 (davidguptil05-linux-kernel-bugs) wrote :

https://www.technical-help-support.com/device-support/alexa-support/
https://www.technical-help-support.com/email-support/att-email-support/
https://www.technical-help-support.com/device-support/arlo-support/
https://www.technical-help-support.com/email-support/roadrunner-email-support/
https://www.technical-help-support.com/email-support/sbcglobal-email-support/
https://www.technical-help-support.com/email-support/bellsouth-email-support/
https://www.technical-help-support.com/device-support/roku-support/
https://www.technical-help-support.com/device-support/garmin-support/
https://www.technical-help-support.com/device-support/kindle-support/
https://www.technical-help-support.com/device-support/tomtom-support/
https://www.technical-help-support.com/hp-support/hp-tech-support/
https://www.technical-help-support.com/device-support/netflix-support/
https://www.technical-help-support.com/router-support/cisco-support/
https://www.technical-help-support.com/device-support/
https://www.technical-help-support.com/router-support/linksys-support/
https://www.technical-help-support.com/email-support/gmail-support/
https://www.technical-help-support.com/email-support/yahoo-mail-support/
https://www.technical-help-support.com/router-support/netgear-support/
https://www.technical-help-support.com/quickbooks-support/quickbooks-upgrade/
https://www.technical-help-support.com/quickbooks-support/quickbooks-cost/
https://www.technical-help-support.com/quickbooks-support/quickbooks-license/
https://www.technical-help-support.com/quickbooks-support/buy-quickbooks/

Revision history for this message
In , davidguptil05 (davidguptil05-linux-kernel-bugs) wrote :

https://www.technical-help-support.com/quicken-support/buy-quicken/
https://www.technical-help-support.com/quickbooks-support/quickbooks-pricing/
https://www.technical-help-support.com/quickbooks-support/quickbooks-discount/
https://www.technical-help-support.com/quickbooks-support/quickbooks-technical-support/
https://www.technical-help-support.com/quickbooks-support/quickbooks-help/
https://www.technical-help-support.com/router-support/
https://www.technical-help-support.com/microsoft-support/microsoft-activation-support/
https://www.technical-help-support.com/quickbooks-support/quickbooks-payroll-support/
https://www.technical-help-support.com/quickbooks-support/quickbooks-customer-service/
https://www.technical-help-support.com/quicken-support/quicken-customer-service/
https://www.technical-help-support.com/quickbooks-support/quickbooks-phone-number/
https://www.technical-help-support.com/quicken-support/quicken-technical-support/
https://www.technical-help-support.com/quicken-support/quicken-bill-pay-support/
https://www.technical-help-support.com/quicken-support/quicken-online-support/
https://www.technical-help-support.com/quickbooks-support/quickbooks-online-support/
https://www.technical-help-support.com/quicken-support/quicken-help/
https://www.technical-help-support.com/email-support/
https://www.technical-help-support.com/apple-support/icloud-support/
https://www.technical-help-support.com/quickbooks-support/quickbooks-enterprise-support/
https://www.technical-help-support.com/quicken-support/quicken-phone-number/
https://www.technical-help-support.com/quickbooks-support/intuit-quickbooks-support/
https://www.technical-help-support.com/pogo-support/pogo-screen-size-problem/
https://www.technical-help-support.com/microsoft-support/microsoft-help/
https://www.technical-help-support.com/microsoft-support/microsoft-phone-support/
https://www.technical-help-support.com/microsoft-support/microsoft-contact/
https://www.technical-help-support.com/hp-support/hp-contact-number/
https://www.technical-help-support.com/hp-support/hp-computer-support/
https://www.technical-help-support.com/microsoft-support/microsoft-number/
https://www.technical-help-support.com/hp-support/hp-phone-number/
https://www.technical-help-support.com/pogo-support/pogo-games-flash-error/
https://www.technical-help-support.com/microsoft-support/microsoft-technical-support/
https://www.technical-help-support.com/hp-support/hp-printer-support/
https://www.technical-help-support.com/microsoft-support/microsoft-telephone-support/
https://www.technical-help-support.com/hp-support/hp-laptop-support/
https://www.technical-help-support.com/microsoft-support/microsoft-customer-service/
https://www.technical-help-support.com/hp-support/hp-help/

Revision history for this message
In , davidguptil05 (davidguptil05-linux-kernel-bugs) wrote :

https://www.technical-help-support.com/apple-support/apple-help-number/
https://www.technical-help-support.com/pogo-support/pogo-games-java-problem/
https://www.technical-help-support.com/hp-support/hp-customer-service/
https://www.technical-help-support.com/quickbooks-support/
https://www.technical-help-support.com/quicken-support/
https://www.technical-help-support.com/pogo-support/
https://www.technical-help-support.com/apple-support/apple-id-support/
https://www.technical-help-support.com/apple-support/macintosh-support/
https://www.technical-help-support.com/apple-support/macbook-support/
https://www.technical-help-support.com/
https://www.technical-help-support.com/hp-support/
https://www.technical-help-support.com/apple-support/apple-ipad-support/
https://www.technical-help-support.com/pogo-support/pogo-technical-support/
https://www.technical-help-support.com/apple-support/itunes-support/
https://www.technical-help-support.com/apple-support/mac-support/
https://www.technical-help-support.com/pogo-support/pogo-customer-service/
https://www.technical-help-support.com/apple-support/apple-customer-service/
https://www.technical-help-support.com/apple-support/iphone-support/
https://www.technical-help-support.com/apple-support/apple-tech-support/
https://www.technical-help-support.com/microsoft-support/microsoft-outlook-support/
https://www.technical-help-support.com/microsoft-support/microsoft-office-support/
https://www.technical-help-support.com/microsoft-support/microsoft-windows-support/
https://www.technical-help-support.com/apple-support/
https://www.technical-help-support.com/microsoft-support/

Revision history for this message
In , dblogsng (dblogsng-linux-kernel-bugs) wrote :
Revision history for this message
In , blueskyluv11 (blueskyluv11-linux-kernel-bugs) wrote :
Revision history for this message
In , blueskyluv11 (blueskyluv11-linux-kernel-bugs) wrote :
Revision history for this message
In , blueskyluv11 (blueskyluv11-linux-kernel-bugs) wrote :

https://medium.com/@neolifeupdate/health-wises-a37a23ba1723
https://basc.berkeley.edu/author/foxyblue/
https://www.theverge.com/users/Victor%20Chijioke
https://www.theverge.com/users/Foxy%20blue
https://www.theverge.com/users/foxybluesky

https://rainfords-surveyors.vpweb.co.uk/blog/2012/01/12/RICS-reminds-buyers-of-the-importance-of-a-home-survey.aspx
http://profs.if.uff.br/tjpp/blog/entradas/o-azeite-bebado#comment_28729d44134e753926ba91729b038577
http://drna.pr.gov/permisos/index.php?module=faq&FAQ_op=view&FAQ_id=153
http://naked-angel.kir.jp/photobbs.myc/photobbs.cgi?mode=disp&no=2799&page=840
http://sn.ras.ru/index.php/forums/topic/2477/came-online-di-indonesia/view/post_id/282906
http://www.cafepedagogique.net/communautes/Vandongen11/Lists/Billets/Post.aspx?ID=394
http://groupspaces.com/WIM/item/1090936#wall
https://forum.dramexchange.com/viewtopic.php?f=7&t=56633
http://ekomazury2.wm.pl/Skandawa:-przyroda-i-zabytki,79396
https://ngcproject.org/habitat-connections-exploring-your-local-environment-through-birds-and-citizen-science-0?page=1#comment-2728
http://official.sportnetwork.net/boards/read/s388.htm?737,413239
http://peertrainer.com/default.aspx?c=45&threadid=14310
http://ftp.loislowry.com/index.php?option=com_easyblog&view=entry&id=563&Itemid=194
http://jskim9699.hosting.paran.com/xe/?mid=product_laser_gray&document_srl=611&rnd=16518#comment_16518
http://blog.tubabel.com/definicion/20204-aboganster#
http://forums.delphiforums.com/vpshostinguae/messages/441/1
https://blogs.apache.org/logging/entry/announce-apache-groovy-2-5

https://dev.labornotes.org/exclusiverep#comment-6655

Revision history for this message
In , info.healthscholar (info.healthscholar-linux-kernel-bugs) wrote :

This is a very unique way of getting it right. https://pestclue.com/

Revision history for this message
In , info.healthscholar (info.healthscholar-linux-kernel-bugs) wrote :

(In reply to Vesselin Kostadinov from comment #547)
> This seems to be a hardware related issue, at least in some cases.
> Can the other people experiencing it confirm whether they have a WD Greed
> hard disk?
> Google search for "wd15eads firmware" reveals quite a few people having
> similar problems.
> I have one of these hard disks and I was using it on a fanless VIA Samuel 2
> (pre-686) CPU and I was seeing the high IOWait problem and associated poor
> performance. When I put the same hard disk in a dual AMD opteron it had the
> same problem.
> Then I did a full backup and restore on a different hard disk. It is the
> same debian system on the same VIA cpu but now the high IOWait times are
> gone and the performance is adequate for the CPU.
> I should point out that the kernel should not suffer poor overall
> performance during disk I/O even on flakey hardware, especially with swap
> disabled.
> The offending hard disk is now blanked. I can run a few tests with it if
> somebody is interested. http://pestclue.com/

Revision history for this message
In , issablogger8 (issablogger8-linux-kernel-bugs) wrote :

Great Info I Love ThIs Post And I'll Like To Share It With my Pals Too https://legitsong.com that's my personal blog Incase you wish to know where I found kernel

Revision history for this message
In , jackbilla01 (jackbilla01-linux-kernel-bugs) wrote :
Revision history for this message
In , kehindequyum17 (kehindequyum17-linux-kernel-bugs) wrote :

I'm a professional web developer and you can checkout my portfolio on <a href="https://quyumshub.com">Quyumshub</a> and I also provide you with all latest online registration guides, web platform reviews and tech tutorials on <a href="https://registerhow.net">Registerhow</a>. I'm also the official blogger of the popular musician <a href="https://kissdaniel.com.ng">Kizz Daniel</a>. I love writing and here is one of my articles on <a href="https://registerhow.net/how-to-set-up-cash-app/">how to set up cash app</a>, <a href="https://registerhow.net/recharge-and-get-paid-ragp-review-and-registration/">recharge and get paid review</a>

Revision history for this message
In , opeyemi041 (opeyemi041-linux-kernel-bugs) wrote :
Revision history for this message
In , aoitechsolutionss (aoitechsolutionss-linux-kernel-bugs) wrote :

AOI Tech Solutions provides you a best internet and network security provider. To get in touch with the internet security service provider, just dial 8888754666. Visit - https://aoitechsolutions.com

Revision history for this message
In , odiditech (odiditech-linux-kernel-bugs) wrote :
Revision history for this message
In , anelkansirim01 (anelkansirim01-linux-kernel-bugs) wrote :

My brother has apparently been having the same problem on his computer. I hadn't realized it when I submitted my bug. For him, he has an ICH8 family of chipsets.

The following works for him, and the problem goes away while accessing his website https://beatplaza.com.
echo anticipatory > /sys/block/sda/queue/scheduler

Looks like this may be a tough one to nail down, because everyone's symptoms are slightly different. I'm wondering if perhaps there are multiple issues going on here.

Revision history for this message
In , wusmnjg (wusmnjg-linux-kernel-bugs) wrote :

Download free movies

Https://nigeriantvseries.com

Revision history for this message
In , ccloughwilliams (ccloughwilliams-linux-kernel-bugs) wrote :

https://immiguy.com/

Mp3 Download: David & Nicole Binion ft. Todd Dulaney – Faith Sees + Video

Revision history for this message
In , cigapeseo2 (cigapeseo2-linux-kernel-bugs) wrote :
Revision history for this message
In , mricon (mricon-linux-kernel-bugs) wrote :

I'm making this bug private to prevent more spam from being added to it.

Revision history for this message
In , caroljames972022 (caroljames972022-linux-kernel-bugs) wrote :
Revision history for this message
In , alexwrinner (alexwrinner-linux-kernel-bugs) wrote :

[25013.905943] INFO: task DOMCacheThread:17496 blocked for more than 120 seconds.
[25013.905945] Tainted: P OE 4.15.0-54-generic #58-Ubuntu
[25013.905947] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[25013.905949] DOMCacheThread D 0 17496 2243 0x00000000
[25013.905951] Call Trace:
[25013.905954] __schedule+0x291/0x8a0
[25013.905957] schedule+0x2c/0x80
[25013.905959] jbd2_log_wait_commit+0xb0/0x120
[25013.905962] ? wait_woken+0x80/0x80 cheap essay https://trustanalytica.com/online/top-cheap-essay-writing-services /0xb0
[25013.905965] __jbd2_journal_force_commit+0x61/0xb0
[25013.905967] jbd2_journal_force_commit+0x21/0x30
[25013.905970] ext4_force_commit+0x29/0x2d
[25013.905972] ext4_sync_file+0x14a/0x3b0
[25013.905975] vfs_fsync_range+0x51/0xb0
[25013.905977] do_fsync+0x3d/0x70
[25013.905980] SyS_fsync+0x10/0x20
[25013.905982] do_syscall_64+0x73/0x130
[25013.905985] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[25013.905987] RIP: 0033:0x7fc9cb839b07

Revision history for this message
In , r.piedfer (r.piedfer-linux-kernel-bugs) wrote :

Created attachment 305400
attachment-13101-0.html

Bonjour,

Je suis actuellement absent.
J'aurai d'ici là un accès très limité à mes emails.
Je reviendrai vers vous dès que possible à mon retour.
Pour toute urgence, vous pouvez contacter Vincent Ophele / <email address hidden>

Cordialement,

----------

Hello,

I am OOO with no access to my emails.
I will get back to you as quickly as possible when I return.
In case of emergency, please contact Vincent Ophele / <email address hidden>

Best regards,

Ce courriel provient de la société Financière Amuse BidCo. Le contenu de ce courriel et les pièces jointes le cas échéant sont confidentiels pour le destinataire. Ils ne peuvent être ni divulgués, ni utilisés, ni copiés de quelque manière que ce soit par une personne autre que le destinataire prévu. Si ce courriel vous a été adressé par erreur, merci d'en informer son auteur par téléphone et par courriel en intégrant le message original dans votre réponse, puis supprimez-le. Pour plus d'informations sur la manière dont nous traitons les données personnelles, veuillez consulter notre Politique de protection des données personnelles <https://cdn.svc.asmodee.net/corporate/uploads/Templates/AH_Politique_de_protection_des_donnees_personnelles_du_groupe_FR.pdf> . Veuillez noter que Financière Amuse BidCo n'assume aucune responsabilité vis-à-vis des virus et qu'il vous incombe d'analyser ou de consulter ce courriel et ses pièces jointes le cas échéant. Financière Amuse BidCo est une société par actions simplifiée à associé unique (RCS Versailles 815 143 904). Son siège social est situé 18 rue Jacqueline Auriol - Quartier Villaroy - 78280 Guyancourt. Pour plus d'informations, veuillez consulter le site https://corporate.asmodee.com/.

This email is from Financière Amuse BidCo. The content of this email and any attachments are confidential to the intended recipient. They may not be disclosed to or used by or copied in any way by anyone other than the intended recipient. If this email is received in error, please inform the author by phone and email, including the original message in your reply, and then delete it. For more information on how we process personal data, please see our Privacy policy <https://cdn.svc.asmodee.net/corporate/uploads/Templates/AH_Asmodee_Global_Privacy_Policy_EN.pdf> . Please note that Financière Amuse BidCo does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. Financière Amuse BidCo is a French « Société par actions simplifiée à associé unique » (Commerce and Companies Register of Versailles 815 143 904) Its registered office is at 18 rue Jacqueline Auriol - Quartier Villaroy - 78280 Guyancourt. For further information, please refer to https://corporate.asmodee.com/.

Revision history for this message
In , konoha02 (konoha02-linux-kernel-bugs) wrote :

I am facing this issue with both debian and archlinux. xfs and ext4
https://forums.debian.net/viewtopic.php?p=778803

Displaying first 40 and last 40 comments. View all 711 comments or add a comment.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.