Bug 118958

Summary:	Failed to acquire semaphore[dbde35e0\|1\|0], AE_TIME
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Thiago Sayao <thiago.sayao>
Component:	Kernel	Assignee:	Thomas Renninger <trenn>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	asadeghpour, bjorn.helgaas, jeanne.colon-bonet, maureen.hoffert, michael.raskey
Version:	RC 1
Target Milestone:	---
Hardware:	Other
OS:	All
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	revert message to debug-only

Description Thiago Sayao 2005-09-26 23:14:27 UTC

Failed to acquire semaphore[dbde35e0|1|0], AE_TIME

I get lot's and lot's of these messages on my dmesg output.. I have no idea what
this means, but i guess something is wrong..

Comment 1 Andrea Arcangeli 2005-10-14 01:50:09 UTC

It's a down_trylock failing that prints it, however since timeout is 0 this  
may actually be harmless. But it's a bit hard to tell if this is harmless or 
not with only the above information. Best would be that you enable the acpi 
debug messages as a whole, so we get some more meaningful trace info. acpi=off 
will workaround it too...

Comment 2 Bjorn Helgaas 2006-03-31 22:49:50 UTC

Created attachment 76013 [details]
revert message to debug-only

This message should be printed only when debugging
is enabled.  There's no actual error when a semaphore
acquisition times out.

I posted this patch here:
http://marc.theaimsgroup.com/?l=linux-acpi&m=114384441902222&w=2

and Bob Moore confirmed that this is the correct
fix.

Comment 3 Thomas Renninger 2006-04-03 09:07:58 UTC

Thanks.