All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: HP accelerometer driver: testers wanted
Date: Fri, 23 Jan 2009 00:11:31 +0100	[thread overview]
Message-ID: <200901230011.31871.elendil@planet.nl> (raw)
In-Reply-To: <20090122221708.GA3430@elf.ucw.cz>

Minor issue in the patch: hpfall.c should not be executable:
-rwxr-xr-x 1 fjp fjp  1759 2009-01-22 23:31 hpfall.c

With patch applied:
$ ls -l /dev/freefall
crw-rw---- 1 root root 10, 59 2009-01-22 23:44 /dev/freefall

$ gcc -o hpfall -Os hpfall.c
hpfall.c: In function ‘main’:
hpfall.c:73: warning: passing argument 2 of ‘signal’ from incompatible 
pointer type

> Run hpfall, and see if LED lights and disk parks if you "drop" a
> computer. (*)

$ sudo ./hpfall &

The LED lights up yellow, but I have problems telling if the disk gets 
parked or not. One time I got a green led and seemingly a fair amount of 
activity immediately after getting the yellow led.

After looking at hpfall.c, I checked /sys/block/sda/device/unload_heads 
after a drop:
$ cat /sys/block/sda/device/unload_heads
19616
$ cat /sys/block/sda/device/unload_heads
0

The last was at most 2 seconds after the first, certainly not 20...

Wouldn't it be good to have locks/unlocks registered in the logs when
/sys/block/sda/device/unload_heads changes (assuming the actual write will 
get delayed until the head is unparked)?

Cheers,
FJP

  reply	other threads:[~2009-01-22 23:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-22 21:31 HP accelerometer driver: testers wanted Pavel Machek
2009-01-22 22:01 ` Frans Pop
2009-01-22 22:17   ` Pavel Machek
2009-01-22 23:11     ` Frans Pop [this message]
2009-01-23  8:59       ` Frans Pop
2009-01-23  9:13         ` Pavel Machek
2009-01-23 15:22       ` Pavel Machek
     [not found] ` <20090122213139.GD2159-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2009-01-22 23:16   ` Mariusz Kozlowski
2009-01-22 23:16     ` Mariusz Kozlowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200901230011.31871.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.