I haven't seen this reported anywhere, so apologies if you've heard this
before :).
in 2.4.9 and 2.4.16 with APM compiled in on my Sony Vaio FX201 laptop
(Via VT82C686 chipset) sometimes when the hardware screensaver comes on
(as a result of APM) the machine deadlocks and has to be powered off and
on again. (Lots of fscking).
If you want any more info, please ask :).
--
Jonathan Amery. Now there's a light at the end of the tunnel,
##### Someone's lit a campfire in my cave.
#######__o The first rays of dawn are breaking through the clouds,
#######'/ And somehow I know I can be brave. - Steve Kitson
Though not with this chipset this lockup did already appear a few times on the
list. Im my case it happened on a i815 based system. It seems that something is
going wrong during (apm?) screen blanking when there is interrupt activity.
Unfortunately the system is frozen solid so there's no chance for any debug
trace. It would be nice if someone with detail knowledge of the blanking code
could have a look.
On 12-Dec-2001 Jonathan D. Amery wrote:
>
> I haven't seen this reported anywhere, so apologies if you've heard this
> before :).
>
> in 2.4.9 and 2.4.16 with APM compiled in on my Sony Vaio FX201 laptop
> (Via VT82C686 chipset) sometimes when the hardware screensaver comes on
> (as a result of APM) the machine deadlocks and has to be powered off and
> on again. (Lots of fscking).
>
> If you want any more info, please ask :).
>
> --
> Jonathan Amery. Now there's a light at the end of the tunnel,
> ##### Someone's lit a campfire in my cave.
> #######__o The first rays of dawn are breaking through the clouds,
> #######'/ And somehow I know I can be brave. - Steve
> Kitson
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Andreas Steinmetz
D.O.M. Datenverarbeitung GmbH
> going wrong during (apm?) screen blanking when there is interrupt activity.
> Unfortunately the system is frozen solid so there's no chance for any debug
> trace. It would be nice if someone with detail knowledge of the blanking code
> could have a look.
APM power management code is buried in the BIOS. We ask the APM bios nicely
to blank the display and power manage it. If the APM bios does something
daft we can't do much about it.
You can turn apm support off in your XFree86 config and see if that helps
On 12-Dec-2001 Alan Cox wrote:
>> going wrong during (apm?) screen blanking when there is interrupt activity.
>> Unfortunately the system is frozen solid so there's no chance for any debug
>> trace. It would be nice if someone with detail knowledge of the blanking
>> code
>> could have a look.
>
> APM power management code is buried in the BIOS. We ask the APM bios nicely
> to blank the display and power manage it. If the APM bios does something
> daft we can't do much about it.
>
> You can turn apm support off in your XFree86 config and see if that helps
>
At least in my case this wasn't exactly apm related. It happened too with apm
blanking disabled and only screen blanking without apm blanking occuring.
Preventing screen blanking completely by issuing echo -e "\033[9;0]" prevented
the freeze from happening so I do believe it's not the apm blanking code but
the general console blanking code where the problem occurs (no X, no fb, plain
80x25).
Andreas Steinmetz
D.O.M. Datenverarbeitung GmbH
On Wed, 12 Dec 2001, Jonathan D. Amery wrote:
> in 2.4.9 and 2.4.16 with APM compiled in on my Sony Vaio FX201 laptop
> (Via VT82C686 chipset) sometimes when the hardware screensaver comes on
> (as a result of APM) the machine deadlocks and has to be powered off and
> on again. (Lots of fscking).
I have the same deadlock problem like you with the same VIA-chipset, my
Laptop is a gericom hydrospeed. I can reproduce it by mounting a cd in the
cd-drive. (My kernel is a 2.4.16 with ide-cd modules)
Steps to generate a deadlock on my notebook:
1. mount a normal cd
2. unmount the cd-drive
3. make a apm --suspend
4. wake up the laptop
5. try to remount the cd
6. the laptop get immediately lockt!
Please try out this, i think it could be the same problem?
Hetzmannseder Markus http://www.hetzi.at/hetzi/
--------------------------------------------------------------------------
"If I do not return to the pulpit this weekend, millions of people will go
to hell."
-- Jimmy Swaggart, 5/20/88
On Thu, 13 Dec 2001, Markus Hetzmannseder wrote:
> I have the same deadlock problem like you with the same VIA-chipset, my
> Laptop is a gericom hydrospeed. I can reproduce it by mounting a cd in the
> cd-drive. (My kernel is a 2.4.16 with ide-cd modules)
>
> Steps to generate a deadlock on my notebook:
>
> 1. mount a normal cd
> 2. unmount the cd-drive
> 3. make a apm --suspend
> 4. wake up the laptop
> 5. try to remount the cd
> 6. the laptop get immediately lockt!
>
> Please try out this, i think it could be the same problem?
>
This doesn't happen. This is however the first time I've apm --suspended
the laptop, and it doesn't really like it (screen corruption in text
mode).
--
Jonathan Amery. Now there's a light at the end of the tunnel,
##### Someone's lit a campfire in my cave.
#######__o The first rays of dawn are breaking through the clouds,
#######'/ And somehow I know I can be brave. - Steve Kitson
On Wed, Dec 12, 2001 at 04:37:01PM +0000, Jonathan D. Amery wrote:
>
> I haven't seen this reported anywhere, so apologies if you've heard this
> before:).
>
> in 2.4.9 and 2.4.16 with APM compiled in on my Sony Vaio FX201 laptop
> (Via VT82C686 chipset) sometimes when the hardware screensaver comes on
> (as a result of APM) the machine deadlocks and has to be powered off and
> on again. (Lots of fscking).
>
> If you want any more info, please ask :).
I experience the same problem on my Sony Vaio FXA32.
It seems to me to be related to the display.
I can sometimes go into standby mode while in text mode and things
seem fine.
Going into standby while in X cause the system to freeze.
I can go into standby and come right back out immediately and things
come back but there seems to be memory corruption.
--
Brian Litzinger <[email protected]>
Copyright (c) 2000 By Brian Litzinger, All Rights Reserved