linux-kernel - Re: acpiphp makes noise on every lid close/open

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 17 Nov 2006 17:08:10 +0100
From:	David Weinehall <tao@....umu.se>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	Kristen Carlson Accardi <kristen.c.accardi@...el.com>,
	Pavel Machek <pavel@....cz>,
	kernel list <linux-kernel@...r.kernel.org>,
	ACPI mailing list <linux-acpi@...r.kernel.org>
Subject: Re: acpiphp makes noise on every lid close/open

On Fri, Nov 17, 2006 at 03:46:27PM +0000, Matthew Garrett wrote:
> On Fri, Nov 17, 2006 at 04:37:17PM +0100, David Weinehall wrote:
> 
> > The fact that the dock starts to beep annoyingly. It has a button that
> > you should press before undocking, and wait for a green light to light
> > up before removing the laptop.  If you remove the computer without
> > doing so, the dock starts beeping, and it doesn't stop (AFAIK, haven't
> > managed to stand the beeping for more than 30 seconds or so) until you
> > replug the laptop.
> 
> Ah, hm. Interesting. Maybe it does want OS support, then. Have you tried 
> it in the Leading Brand OS?

Nope.

> > My guess is that there is some wait to trigger an undock event from
> > software as well, and that it would be nice to send that signal to the
> > dock before suspending...
> 
> You possibly don't want to do that if there's a mounted bay device in 
> the dock.

Well, right now I don't have a bay device in the dock, but refusing to
suspend in that case would be reasonable.  I need to add some hotplug
script for the bay device anyway if I add one.

> We really need to determine some sort of policy when it comes to mounted 
> devices that will potentially be removed by the user over 
> suspend/resume. Do we support this configuration (by not killing the 
> mount point), or do we prevent users from shooting themselves in the 
> foot?

Good question.  Personally I'd say we refuse to suspend when we have
devices we *know* to be dock-devices etc mounted.


Regards: David
-- 
 /) David Weinehall <tao@....umu.se> /) Northern lights wander      (\
//  Maintainer of the v2.0 kernel   //  Dance across the winter sky //
\)  http://www.acc.umu.se/~tao/    (/   Full colour fire           (/
-
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/