public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Steinmetz <ast@domdv.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, <emmanuele.bassi@iol.it (Emmanuele Bassi)>
Subject: Re: Deadlock on kernels > 2.4.13-pre6
Date: Fri, 30 Nov 2001 17:04:43 +0100 (CET)	[thread overview]
Message-ID: <XFMail.20011130170443.ast@domdv.de> (raw)
In-Reply-To: <E169pzm-0003sq-00@the-village.bc.nu>

I had this kind of deadlock on a MSI-6215 (i815) running in console mode (no X).
It always happened during screen blanking while there was interrupt load
(networking via ISDN). APM based screen blanking didn't work so I suspected APM
but at least this is only half true at maximum. The system does run fine with
APM but no APM screen blanking, if you disable console blanking completely by
issuing:

echo -n -e "\033[9;0]\033[10;0]\033[11;0]\033[14;0]"

during the boot sequence, i.e. output to /dev/console (beeps silenced too but I
do believe this can be ignored). By now I do suspect the console blanking code
to be the trigger of the lockup, not the APM code.

On 30-Nov-2001 Alan Cox wrote:
>> So far, I've excluded everything but a bug in the OSS sound drivers,
>> but, according to the ChangeLogs, they did not change from 2.4.13-pre6
>> (the last working kernel) to 2.4.13.
> 
> The OSS core and SB AWE driver have to all intents not changed since before
> 2.4 was released.
> 
> You might want to check when the  various VIA chipset fixes went in if you
> are using a VIA chipset
> -
> 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/
> 

Andreas Steinmetz
D.O.M. Datenverarbeitung GmbH

  reply	other threads:[~2001-11-30 16:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-30 15:40 Deadlock on kernels > 2.4.13-pre6 Emmanuele Bassi
2001-11-30 15:54 ` Alan Cox
2001-11-30 16:04   ` Andreas Steinmetz [this message]
2001-11-30 21:13   ` Emmanuele Bassi
2001-11-30 22:39     ` Alan Cox
2001-12-01 13:39       ` Emmanuele Bassi
2001-12-01 17:41         ` Emmanuele Bassi
2001-12-03  7:52 ` Chris Siebenmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=XFMail.20011130170443.ast@domdv.de \
    --to=ast@domdv.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=emmanuele.bassi@iol.it \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox