SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Currently I've been using Slackware64-Current since it is first released, and one thing I noticed is file operation (copy, move) from my hard drive (ext4) to external USB drive (NTFS), even copying data from DVD to my hard drive would heavily load my CPU (almost 100%).
My machine is using a Intel dual core E2160 clocked at 3 GHz, and file operation putting heavy load on both core is kind of strange.
I'm using stock kernel from Slackware64-Current, anybody using a custom build kernel (2.6.30.x) having this problem? If this problem gone in the new kernel then I'm going to build & install a new kernel.
The machine I use to test Slackware64 is also a dual core 3GHz box and cpu load is very low...
Just a wild guess: how much memory does your machine have?
Another question: Does this only happen copying to external drives?
Copying on your local drives works w/o problems?
Thanks for your reply, my machine has 4 GB of RAM, and after more file copy-move testing the highest CPU load occurred when copy or move files to external HDD. Do you ever have similar experience like this?
My machine is using a Intel dual core E2160 clocked at 3 GHz, and file operation putting heavy load on both core is kind of strange.
I'm using stock kernel from Slackware64-Current, anybody using a custom build kernel (2.6.30.x) having this problem? If this problem gone in the new kernel then I'm going to build & install a new kernel.
Thanks.
Check that you are using the correct chipset driver(s) and not generic drivers. Which file system are you using? File systems can cause some overhead, but should not cause 100% spikes.
If you are using the huge kernel, this could be the case. For my systems, using the huge kernel has resulted in using the generic-ide adapter, with ~22 MB/s throughput with 99% CPU. Using the generic kernel with an intrid or compiling my own gives me ~75 MB/s and 2-5% CPU.
My hard drive is IDE, connected to JMB368 IDE controller on Abit IP35-E mainboard and it's using the pata_jmicron module. All partition is formatted as ext4 and my external USB HDD is formatted with NTFS. I use the generic kernel not the huge one. I've heard rumors about the JMicron controller causing some performance problem, and yes not only the CPU usage is insane, copying lots of file could take very long, which in my opinion indicates low transfer rate.
I've even tried compile a custom 2.6.30.4 kernel based on the config from Slackware64 generic kernel, still no progress though. Please share your advice or experience regarding the JMB368 IDE on Linux.
I've even tried compile a custom 2.6.30.4 kernel based on the config from Slackware64 generic kernel, still no progress though. Please share your advice or experience regarding the JMB368 IDE on Linux.
Thanks.
Code:
03:00.0 IDE interface: JMicron Technologies, Inc. JMB368 IDE controller (prog-if 85 [Master SecO PriO])
Kernel driver in use: pata_jmicron
The driver is provided by libata, and listed as /dev/sd$. If you use the older driver, this controller will be listed as /dev/hd$. I currently have my optical drives connected to this controller - with out using libata burning a disc faster than 8x was not possible, also had high CPU usage. IDE drives connected to this chipset while not using the correct drivers exhibit the same problems you have.
If you compiled your own kernel I'm sure you read this. Why didn't you use the libata driver as suggested?
Quote:
Basic support for the JMicron ATA controllers. For full support
use the libata drivers.
Quote:
Since the high cpu load happens when copying from or to the external drive, let's investigate that.
Check with 'lsusb -v' the information about your external drive and post it here.
Have to agree If the problem is only with an externel drive. But if you are using a JMicron chipset without the correct drivers, other problems could arise as well.
The driver is provided by libata, and listed as /dev/sd$. If you use the older driver, this controller will be listed as /dev/hd$. I currently have my optical drives connected to this controller - with out using libata burning a disc faster than 8x was not possible, also had high CPU usage. IDE drives connected to this chipset while not using the correct drivers exhibit the same problems you have.
Thanks for the suggestion, re-compiled my kernel today so the JMicron use the new driver. The drive is recognized as /dev/sda and now my CPU load on copy operation is much better.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.