Sluggish performance with Slackware 12.2 2.6.27.7-smp on Gigabyte GA-8S649MF
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.
Using /lib/modules/2.6.27.7-twk/kernel/fs/reiserfs/reiserfs.ko
mount: mounting /dev/sda1 on /mnt failed: No such file or directory
ERROR: No /sbin/init found on rootdev (or not mounted). Trouble ahead.
You can try to fix it. Type 'exit' when things are done.
/bin/sh: can't access tty; job control turned off
/ $ _
Same story with /dev/hda1.
I'll check out the compositing later today. Need to catch me some Zs.
Well then it seems you need the old library to use the drive. I made a Google search about the model number, there were a couple of hits where it was recognized as sda. There was also another case (kernel 2.6.9) where it was the device hda and hdparm gave 517 MB/s cached read speed. So your low speed in hda mode could be caused some other thing which causes an overall slow down.
At this point I can only think of "deep" things like dynamic ticks, cpu throttling (cpufreq), smp as the possible causes. These features were quite stable in 2.6.27, but who knows. As a somewhat different thing I noticed you have the it87 module, but I'm not sure if it could cause this sort of behaviour.
Do your system logs indicate any errors or unusual things?
Is it possible your bios settings direct the drive to be treated as ide? Many BIOSs have that capability as some systems (OS) cannot boot from an sata drive. My system has 5 sata ports and the bios allows for all of them to be treated as sata or as ide, but it also has a second feature allowing one of the five to be treated differently, so I can have 4 satas and treat the 5th as sata or ide. This is useful for booting with OS that needs ide (hd or cdrom). Early on I had very slow performance with disk operation and I think this was the cause. But also around the same time I upgraded slackware, probably from 12 to 12.1 so that might have done it also.
Sorry for the late response. Been busy times lately.
Actually, the SATA option in BIOS was set to IDE. Changed it to RAID which were the only other option and I'm now doing a recompile with SiS ATA support as changing the BIOS option had no effect on the kernel mentioned in my previous post. This time around I'm leaving out all Generic ATA from SATA/PATA drivers "page" in the kernel setup. Perhaps that'll do the trick..?
Plugged in a SATA drive and hdparm -tT results were much slower than the IDE drive results in previous replies.
Also browsed the logfiles and they were chugging along quite contently. IDE drive running at ATA/100, chipsets detected correctly and so forth.
Last edited by kslen; 05-14-2009 at 10:09 AM.
Reason: WrarHHrhrhar.
Oh, yea. it87 is my precious.. Needs my temp readings.
And no, I doubt it. I fired up lm_sensors late in the game and the issue was present before touching that module. I'll unload it and run hdparm just to be sure though.
The drive previously listed as /dev/hda is now listed as /dev/sda, yet there's no improvement in read speed.
I've gotta backtrack a few steps in order to verify the SiS modules performance to the generic ATA support which is currently compiled into the kernel.
I've recompiled the kernel exactly as disturbed1 suggested earlier and the it booted gleefully. The IDE drive is listed as /dev/sda, however; also as mentioned earlier. The hdparm -tT /dev/sda results are pretty much exactly the same as the results previously posted results..
My nforce2 chipset has the choice to use either module, like you, I noticed no speed increase between /dev/hd$ and /dev/sd$ for IDE drives, but... the system seemed to be more responsive using libata.
The main problem with your hdparm -tT results were the cached reads. For an IDE drive, your buffered disk reads were with in reason (40-60MB/s). All of my ATA 100 hard drives test close to what your getting, but the cached reads are much higher, in the 5,000 - 6,000MB/s range. The cached reads should be this high because it is reading from the cached memory.
Could be that my IDE drives have between 8MB and 32MB of cache.
Have you tried running a smart test on the drive just to rule anything out? You could run smartctl --all /dev/sda to get a brief summary of the drive. I tend to use the manufacturer's tools to diagnose hard drives. These come as bootable isos, and can run a complete hard drive test. Depending on the drive size, you may want to let it run over night, it can take a while.
Some other things I've seen that cause problems are more than one device on the IDE channel, where one of those devices are faulty, or slower. Like having an optical drive and hard drive share the same cable. Faulty cables, and temp issues.
Should be noted that hdparm is like glxgears, not really a benchmark
dd if=/dev/zero of=test.bin bs=512000 count=1000
The above will write a 512MB file and report the write speed. Best to perform more than once, the first one is usually not a true result.
There's been an on going discussion over a huge Kernel regression since 2.6.18 which coincides with the time CFQ became the default scheduler. Not everyone has an issue, and it's been near impossible for the smart people to nail down. If you search this forum, there's a post about changing the default scheduler. You can try that to see if it helps.
Well I have similar thoughts as disturbed1, but what confuses me is that kslen says he didn't notice this performance loss on XP, so it probably isn't faulty hardware. I know one kernel regression which causes loss of system responsiveness during heavy disk I/O (which starts around 2.6.17) and yes, I also remember rare complaints about CFQ which was made the default around 2.6.22 or 23 as far as I can remember. But none of these should affect the cached read speed I think. I suffer from the first regression and I have a slow disk but cached read rate is way better (around 720 MB/s). I suspect another deeper problem could be causing this.
... I just made another Google search. I've come across people reporting bad performance with the Sis 5513 controller. Some of these people seemed to get better performance with the old drivers. If you keep your generic kernel around, could you try the boot options
Code:
ide0=ata66 ide0=autotune hda=autotune
And finally, you could also try the options
Code:
noapic acpi=off
to see if these subsystems could be part of the trouble. These likely won't solve your problem but they are the only things I can think of now.
After one more attempt at scrounging around for a BIOS update, I finally found one. And guess what..
hdparm -tT /dev/sda
Code:
Timing cached reads: 1034 MB in 2.00 seconds = 516.58 MB/sec
Timing buffered disk reads: 166 MB in 3.02 seconds = 54.88 MB/ssec
My choppy issues are no more.
If anyone should happen to be looking for a BIOS upgrade or drivers in general for the Gigabyte GA-8S649MF motherboard, look no further: Link to support site.
Now I've just got to figure out how to boot the kernel successfully as my SATA drive seems to steal sda during boot. Should be easy, but one never knows in these parts of the woods....
If you're wondering "Why the frack is this guy booting offa an IDE drive when he's got a SATA drive in there?". Well, the SATA drive will move along with me in not a too distant future, the rest of the machine will remain at its current location and I don't really need a SATA drive for the work it will be doing, so an IDE drive will suffice. ^^
In any case, great props to you all for the help. I learned a bunch. Greatly appreciate it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.