I've been running slackware with the generic kernel provided since slack12.0. my computer is a Fujitsu Siemens V2045 PRO, with the ATI radeom mobility X300 as Gcard. I updated my system some days ago to the 12.1, i'm using radeon driver Module radeon: vendor="X.Org Foundation" compiled for 1.4.0.90, module version = 4.3.0 I can switch off the screen backlight by pressing Fn+F4, I usually do that when i'm off for some time and don't want to switch off the pc. I can do that only since i recently updated to slack12.1. The computer crashes when I press the Fn key for some purpose (for exemple to switch on wifi) just after switching back on the backlight. The computer crashes at the time i press Fn without any other key. The crash is as follows: the screen gets blank but with backlight on. I cannot do anything, even Ctrl+Alt+Del doesn't help. So I cannot have a backtrace of the bug. I just press the ON/OFF button for some seconds to then start again the computer.
This sounds like an acpi/bios issue. What does the fn-f4 key actually do on your system? Does it execute an acpi method or does it generate an acpi event that is hooked to a script? If it's a script, what does that script do? At the very least attach your xorg log and config and the output of dmesg.
Created attachment 16835 [details] dmesg after reboot because of crash
Created attachment 16836 [details] Xorg.0.log.old after reboot because of crash
(In reply to comment #1) > This sounds like an acpi/bios issue. What does the fn-f4 key actually do on > your system? Does it execute an acpi method or does it generate an acpi event > that is hooked to a script? I actually do not know how to get such information. I think this is not an acpi event because acpi I think is driven by the bios, so even without any OS i could use Fn+F4 keys to switch the screen backlight off. before upgrading to radeon 4.3.0 I couldn't switch off the screen backlight. I can for now add some clarification to the bug: actually it seems pressing any key after switching back on the backlight throws the computer into a crash. It doesn't always happen, sometimes everything works alright. > If it's a script, what does that script do? At > the very least attach your xorg log and config and the output of dmesg. >
the bug is clarified a bit. Actually once the the screen's backlight if off thanks with Fn+F4, it should come back on by pressing any key BUT not when moving the mouse. but sometimes (i can't tel when exactly) the screen's backlight gets on when the mouse is moved. In this latter case if i press any key the screen becomes blank, but the backlight on. I can actually get back the screen as normal, i.e. not blank by switching off the backlight again (Fn+F4) and then getting it back on by pressing any key (unless i'm unlucky, it works). actually that's why i decreased the degree of severity of the bug report. what annoys me with this bug is that It adds up the number of switch off to on sequences. This reduces the lifespan of the tube.
Sounds like an acpi bug.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.