Bug 114960 - OSD always appears with no reason
Summary: OSD always appears with no reason
Status: VERIFIED FIXED
: 118532 (view as bug list)
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Mobile Devices (show other bugs)
Version: Beta 3
Hardware: i686 All
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Timo Hoenig
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-02 13:22 UTC by Perret Florian
Modified: 2007-06-05 09:57 UTC (History)
4 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
test (3.36 KB, application/octet-stream)
2005-09-06 10:05 UTC, Perret Florian 		Details
test 2 (3.32 KB, application/octet-stream)
2005-09-06 10:41 UTC, Perret Florian 		Details
proposed patch to stop the syslog flood on affected systems (2.40 KB, patch)
2005-09-09 10:34 UTC, Timo Hoenig 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Perret Florian 2005-09-02 13:22:41 UTC 
OSD always appears with no reason. I have "display change : on" or "display
change : off". This text appears at about every minute, even when I don't touch
the computer.
I can't see witch soft is it.

My computer is an Asus A6 with ATI Radeon M 7500.
Comment 1 Perret Florian 2005-09-05 07:57:09 UTC 
/var/log/messages takes 5,5mo !

The start is :
Sep  4 12:00:05 linux syslog-ng[4413]: new configuration initialized
Sep  4 12:00:05 linux syslog-ng[4413]: Changing permissions on special file
/dev/xconsole
Sep  4 12:00:05 linux syslog-ng[4413]: Changing permissions on special file
/dev/tty10
Sep  4 12:00:05 linux kernel: Asus ACPI: Error reading LCD status
Sep  4 12:00:05 linux kernel: Asus ACPI: Error reading LCD status
Sep  4 12:00:05 linux kernel: Asus ACPI: Error reading LCD status
Sep  4 12:00:05 linux kernel: Asus ACPI: Error reading LCD status
...
This last line is repeat every second !
Comment 2 Marcus Schaefer 2005-09-05 08:44:07 UTC 
sorry I'm not responsible for the scenario you mentioned here
Comment 3 Andreas Jaeger 2005-09-05 08:54:34 UTC 
Are you using the ial package?
Comment 4 Perret Florian 2005-09-05 09:04:51 UTC 
I've just made the default install with KDE as desktop, and ial is effectively
install.
Comment 5 Stefan Behlert 2005-09-05 09:32:06 UTC 
Looks like a buggy BIOS, but nevertheless there should not be so many  
messages.  
I see two bugs here: the numner of messages in /var/log/messages (syslog  
should collect them  and say something like 'last message repeated 1234  
times'), and the appearing of the OSD.  
I'll try to find the origin of the message today.
Comment 6 Timo Hoenig 2005-09-06 08:58:39 UTC 
This is clearly a bug of acpi_asus. I will take care.
Comment 7 Timo Hoenig 2005-09-06 09:17:50 UTC 
Please do the following

   $ rmmod acpi_asus
   $ modprobe acpi_asus

and attach the ouput of

   $ tail -n 50 /var/log/messages

to this bug.
Comment 8 Perret Florian 2005-09-06 09:53:19 UTC 
rmmod acpi_asus :
ERROR: Module acpi_asus does not exist in /proc/modules

modprobe acpi_asus :
FATAL: Module acpi_asus not found.

tail -n 50 /var/log/messages :
Sep  6 11:52:39 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:39 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:39 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:39 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:39 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:39 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:39 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:39 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:39 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:39 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:39 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:39 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:39 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:39 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:39 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:39 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:40 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:40 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:40 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:40 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:40 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:40 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:40 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:40 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:40 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:40 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:40 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:40 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:40 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:40 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:40 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:40 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:40 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:40 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:40 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:40 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:41 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:41 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:41 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:41 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:41 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:41 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:41 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:41 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:41 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:41 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:41 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:41 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:41 linux kernel: Asus ACPI: Error reading LCD status
Sep  6 11:52:41 linux kernel: Asus ACPI: Error reading LCD status
Comment 9 Timo Hoenig 2005-09-06 09:57:36 UTC 
Sorry I've it should have been:

   $ rmmod asus_acpi

and

   $ modprobe asus_acpi

Please do not inline the log but rather the output as file.
Comment 10 Perret Florian 2005-09-06 10:05:59 UTC 
Created attachment 48896 [details]
test
Comment 11 Timo Hoenig 2005-09-06 10:09:15 UTC 
Powersave daemon and KDE still accessing the driver's interface. Please close your X session, do 

   $ rcpowersaved stop

and attach a new log of above's procedure.
Comment 12 Perret Florian 2005-09-06 10:41:12 UTC 
Created attachment 48900 [details]
test 2
Comment 13 Perret Florian 2005-09-06 10:42:42 UTC 
It seems better. A "brightness" OSD appears with the two commands.
PS : I didn't have this bug in beata 3.
Comment 14 Timo Hoenig 2005-09-07 08:14:07 UTC 
So here's the analysis:

   * asus_acpi loads with default values for ASUS laptops which are _not_ explicitly supported
   * These default values are not sane for some systems (e.g. the one of this bug report). Thus, once 
/proc/acpi/asus/lcd is read, an error is logged to syslog.
   * If KDE starts up and KMILO is able to access /proc/acpi/asus/lcd it constantly polls this interface 
at a insane rate. A short

    $ strace `pidof kded`

shows almost exclusively syscalls triggered by of KMILO's ASUS module. On each iteration, a syslog 
error gets logged and the OSD pops up (even though it didn't gather any reasonable data from the 
kernel interface).

Solution:

KMILO has to
   * quit polling at such a high rate, a polling intervall of 250ms for gathering the display brightness is 
enough
   * quit showing the OSD if it did not gather reasonable data from /proc/acpi/asus/lcd
Comment 15 Timo Hoenig 2005-09-07 12:53:06 UTC 
Raising severity to gain attention.
Comment 16 Dirk Mueller 2005-09-07 13:22:16 UTC 
its a laptop, right?
Comment 17 Dirk Mueller 2005-09-07 13:27:06 UTC 

*** This bug has been marked as a duplicate of 104270 ***
Comment 18 Timo Hoenig 2005-09-07 13:30:27 UTC 
We're not talking about the probing of modules. We're talking about KMILO's polling intervall 
(comment #14).
Comment 19 Perret Florian 2005-09-07 14:15:45 UTC 
It's a laptop Asus A6G with an ATI Radeon M 9700 and a 1280*800 LCD.
Comment 20 Christoph Thiel 2005-09-08 09:03:35 UTC 
Elevate severity to critical.
Comment 21 Dirk Mueller 2005-09-08 13:17:59 UTC 
fixed for 10.0
Comment 22 Dirk Mueller 2005-09-08 16:34:07 UTC 
/work/built/mbuild/oldboy-dmueller-454 
 
contains the patched rpm that doesn't just disable it.. if only I could get 
hold of one of those asus laptops so that I can test it.. 
 
but maybe someone else here can.
Comment 23 Dirk Mueller 2005-09-08 16:35:59 UTC 
sorting
Comment 24 Perret Florian 2005-09-08 17:08:12 UTC 
Could you give a complete URL to test this patch ? Thanks.
Comment 25 Timo Hoenig 2005-09-09 07:04:19 UTC 
Perret, I can provide a
Comment 26 Timo Hoenig 2005-09-09 07:06:07 UTC 
... a updated rpm of kdeutils3. See private mail.
Comment 27 Timo Hoenig 2005-09-09 07:26:14 UTC 
cc'ing Daniel. He's got a ASUS with RC1. He originally doesn't suffer from this bug's problem, but there 
are chances that we can provoke the bug on his system.

Daniel, please install kdeutils3 and kdeutils3-laptop of Dirk's mbuild (comment #22).
Comment 28 Timo Hoenig 2005-09-09 08:39:48 UTC 
Florian, please post the results once you're on RC1 with the updated packages I've sent.
Comment 29 Adrian Schröter 2005-09-09 09:55:40 UTC 
It would make more sense to fix the kernel module or to drop it. 
Andreas ?
Comment 30 Timo Hoenig 2005-09-09 10:12:06 UTC 
Fixing yes, dropping no.

I am preparing a patch for the module which prevents the flodding of syslog.
Comment 31 Timo Hoenig 2005-09-09 10:34:04 UTC 
Created attachment 49354 [details]
proposed patch to stop the syslog flood on affected systems
Comment 32 Timo Hoenig 2005-09-09 10:38:48 UTC 
cc'ing Olaf and Thomas.

Please review the patch.

It applies on top of patches.suse/acpi-asus-panasonic-sony.patch. I've tested the patched driver and 
it works fine.
Comment 33 Thomas Renninger 2005-09-09 12:51:51 UTC 
I'd say the proc_read_lcd should return -ENODEV if the get_lcd_state() fails and
KMilo/whatever should evaluate whether the read was successful and stop polling
if not. But this would certainly be too much change for RCX.
And you could do it with every func...

So let's just suppress the message as Timo supposed ...
Hmm, KMilo will probably use the wrong value as it cannot evaluate an error? But
as said, I think it's too much for RC.

Reassigning to okir, I don't have kernel commit rights...
Comment 34 Olaf Kirch 2005-09-09 13:02:09 UTC 
It's not the optimal solution, indeed. I would also have suggested using 
printk_ratelimit(KERN_NOTICE) rather than these somewhat awkward #ifdefs. 
Nevertheless, it's rather late in the game so in it goes. 
 
Please make sure you discuss this with the upstream maintainer.
Comment 35 Timo Hoenig 2005-09-09 13:07:40 UTC 
That's what I first thought of. Does rate_limit also help in this case:

   Error A
   Error A
   Error B
   Error B
   Error A
   Error A

I'll talk to the upstream maintainers. There's more to discuss than this one...
Comment 36 Olaf Kirch 2005-09-09 13:11:39 UTC 
printk_ratelimit will basically blanket out any kernel messages within a 
certain interval if we're flooding the syslog. So it may not be such a 
good idea after all.
Comment 37 Hubert Mantel 2005-09-09 13:33:12 UTC 
The patch committed to CVS does not even apply, so it is obviously totally
untested. So the patch has been dropped now.
Comment 39 Perret Florian 2005-09-10 09:21:16 UTC 
I've the same problem with RC1 and patches. OSD always appears and here the log :
linux:/home/flo #rmmod asus_acpi
linux:/home/flo # modprobe asus_acpi
linux:/home/flo # tail -n 50 /var/log/messages
Sep 10 08:25:41 linux kernel: Asus ACPI: Error reading LCD status
Sep 10 08:25:41 linux kernel: Asus ACPI: Error reading LCD status
Sep 10 08:25:41 linux kernel: Asus ACPI: Error reading LCD status
Sep 10 08:25:41 linux kernel: Asus ACPI: Error reading LCD status
Sep 10 08:25:42 linux kernel: Asus ACPI: Error reading LCD status
Sep 10 08:25:42 linux kernel: Asus ACPI: Error reading LCD status
...
Comment 40 Timo Hoenig 2005-09-10 10:18:00 UTC 
The syslog flooding will be gone in RC2, I can send you an updated kernel module to verify the 
resolution in RC1.

I'll take care of the OSD appearing on Monday once I got my hands on a ASUS machine. If I don't find 
a quick solution we will disable the KMILO plugin.

Reopening the bug.
Comment 41 Timo Hoenig 2005-09-10 10:18:56 UTC 
I'll take care. Reassigning to me.
Comment 42 Timo Hoenig 2005-09-12 14:56:56 UTC 
Florian, Daniel: Can you please tell me whether the OSD pops up _after_ logging into X/KDE? If so, 
and if it is annoying I'd vote for disabling the ASUS KMILO plugin.

Please respond quick, we're already in the middle of the RC phase.
Comment 43 Timo Hoenig 2005-09-12 15:31:08 UTC 
According to dmueller the KMILO plugins for ASUS laptops is now disabled.

We'll look into this one again once the the kernel module is fixed.
Comment 44 Stefan Dirsch 2005-09-25 08:20:47 UTC 
*** Bug 118532 has been marked as a duplicate of this bug. ***
Comment 45 Perret Florian 2005-10-07 15:04:13 UTC 
Now WOFOME with Suse 10 GM
Comment 46 Perret Florian 2005-11-12 10:46:02 UTC 
This bug be back when I upgrade to KDE 3.5 RC1.
Comment 47 Perret Florian 2005-11-12 11:13:44 UTC 
How could I disable Kmilo ?
Comment 48 Timo Hoenig 2006-01-19 20:03:53 UTC 
Folrian, are you still with us?  Will you be able and willing to have a look on a upcoming Beta1?
Comment 49 Perret Florian 2006-01-19 20:24:10 UTC 
I'm still here. What should I do for testing ?
Comment 50 Timo Hoenig 2006-01-19 20:29:59 UTC 
Cool, glad to hear this.

With Beta1 being released by tomorrow, I'd love to know whether your issues are fixed now.

I expect the ASUS driver to be working (it was a kernel bug, the ACPI subsystem is to blame, not the ASUS driver).  Thus, I expect the kmilo bug to be gone, too.

Hence, would be great if you grab a copy of Beta1 and check if everything is working as expected.

Thanks!
Comment 51 Timo Hoenig 2006-01-19 20:37:54 UTC 
Just had a look ar our kernel source.  2.6.15 _still_ seems not to provide support for the A6.  I'll cook up a patch for you over the next days.

Moving to 10.1, cc'ing seife.
Comment 52 Perret Florian 2006-02-03 10:33:17 UTC 
I always have in /var/log/messages :
Feb  3 11:21:24 linux klogd: Asus ACPI: Error reading LCD status
Feb  3 11:21:24 linux klogd: Asus ACPI: Error reading LCD status
Feb  3 11:21:24 linux klogd: Asus ACPI: Error reading LCD status
Feb  3 11:21:24 linux klogd: Asus ACPI: Error reading LCD status
Feb  3 11:21:24 linux klogd: Asus ACPI: Error reading LCD status
Feb  3 11:21:24 linux klogd: Asus ACPI: Error reading LCD status
Feb  3 11:21:24 linux klogd: Asus ACPI: Error reading LCD status
Feb  3 11:21:24 linux klogd: Asus ACPI: Error reading LCD status

But now the Kmilo advert doesn't appear.
Comment 53 Timo Hoenig 2006-03-20 13:03:35 UTC 
Florian -- again ;-) -- are you still with us?  ASUS ACPI 0.30 is in and it now should be easy to add support for the A6.  However, I'd need your help for testing.
Comment 54 Perret Florian 2006-03-20 15:38:40 UTC 
I'm stil here but I don't have anymore my Asus laptop. I've changed for a laptop with less problem (a Sony Vaio SZ). Sorry, I can't help you anymore... anyone else with an Asus here ?
Comment 55 Timo Hoenig 2006-03-20 15:41:23 UTC 
Well, it has to be a A6 in order to fix the issue for this model ;-) Nevermind, I'll see whether I can find someone with a A6.

Thanks!
Comment 58 Timo Hoenig 2006-05-02 11:39:00 UTC 
The bug as described in the initial report was fixed with a patch for asus_acpi.c.  See bug #166920 for details.

To support more ASUS models I've opened a bug for 10.2 (bug #171517).

Closing as FIXED.