Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 12 Dec 2001 12:18:15 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 12 Dec 2001 12:18:05 -0500 Received: from hermes.domdv.de ([193.102.202.1]:34322 "EHLO zeus.domdv.de") by vger.kernel.org with ESMTP id ; Wed, 12 Dec 2001 12:17:49 -0500 Message-ID: X-Mailer: XFMail 1.5.1 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 12 Dec 2001 18:11:45 +0100 (CET) Organization: D.O.M. Datenverarbeitung GmbH From: Andreas Steinmetz To: Alan Cox Subject: Re: VT82C686 && APM deadlock bug? Cc: linux-kernel@vger.kernel.org Cc: linux-kernel@vger.kernel.org, Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/