Re: [PROBLEM]: hdparm strange behaviour for 2.6.21 and later

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanos Kyritsis wrote:
Hello,

starting with kernel 2.6.21 and up to kernel 2.6.22-rc4, I'm having the following problem:

/etc/rc.d/rc.local contains the following:
/usr/sbin/hdparm -q -d1 -q -u1 -q -c1 -q -k1 /dev/hda
/usr/sbin/hdparm -q -d1 -q -u1 -q -c1 -q -k1 /dev/hdb
/usr/sbin/hdparm -q -d1 -q -u1 -q -c1 -q -k1 /dev/hdc
/usr/sbin/hdparm -q -d1 -q -u1 -q -c1 -q -k1 /dev/hdd

(I'm using Slackware, no Debian-style automated hdparm.conf is running during bootup, that's why these are in rc.local)

The above seem to somehow lock up the boot procedure just at the point where rc.local gets executed, so the system never reaches login prompt. All drivers (kernelspace) and system daemons (userspace) before rc.local do normally load, but there are no strange messages in the console or in the system logs and because I cannot login, I cannot trace it any further. I believe the kernel is in running state because the machine responds to ICMP pings from the ethernet, but since the login prompt is not up, the already running sshd/telnetd do not provide any help.

The strange thing is that if I remove all the quiet options (-q) from the above commands, everything works like it should. Furthermore, if I comment them out from rc.local, then boot, login, and execute them by hand (with -q), again everything works like it should. Lockup only happens if I run 2 or more hdparm commands, if I leave only one (doesn't matter which one) hdparm command in rc.local (with -q), it works.

Sounds like a (kernel) timing issue.
The "-q" option gets rid of some intermediary printf's,
and nothing else.  So with -q, the ioctl() calls happen
much closer together in time.  Without -q, the intermediary
printf's likely cause a resched, giving the kernel more time
to complete anything left over from the earlier call.

????

Any difference with a modern version of hdparm?

-ml
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Filesystems]     [Linux SCSI]     [Linux RAID]     [Git]     [Kernel Newbies]     [Linux Newbie]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Samba]     [Device Mapper]

  Powered by Linux