lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111211142451.63febb26@pequin>
Date:	Sun, 11 Dec 2011 14:24:51 -0500
From:	Bill Gribble <grib@...lgribble.com>
To:	linux-kernel@...r.kernel.org
Subject: Mystery clicking under keyboard, 3.x only, SSD only

I am running Debian Sid on a Viliv N5, which is an Atom Z520/Poulsbo
(GMA500) UMPC.  It has no rotating media or fans. With Debian's
linux-image-2.6.39-2-686-pae and earlier kernels behavior is normal
(except for flaky libertas wifi, which is why I seek to upgrade). 

Any 3.0 or 3.1 kernel I have tried from Debian (I have tried each
incremental version, most recently linux-image-3.1.0-1-686-pae) starts,
within a minute after boot, to make a soft clicking noise from under
the keyboard.  Clicks appear to be correlated with
interrupt-generating activity such as moving a mouse pointer or
pressing keys.  This clicking does not start in earnest until an X
server comes up, but even booting into single-user mode I hear it
some.  With an X display up, there is a continuous stream of 5-10
clicks per second, more when moving the mouse pointer.

There is no disk or fan on this machine (SSD only).  The audio system
is Intel HDA; I have tried muting all mixer channels, turning all
volumes to 0, even blacklisting all the intel HDA modules and all the
pc speaker modules.  In any case, the speaker for the device is in the
screen bezel, not the keyboard (I think; I have never gotten the
speaker to work properly).  

I have also tried blacklisting the psb_gfx module in 3.1.  

I see nothing of interest in any logs.  Nothing I have done changes the
behavior at all.

Any thoughts about what this could be?  I am getting a little crazy
about it.  

Thanks,
Bill Gribble

 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ