From alsa-user-owner@alsa.jcu.cz  Mon Oct 26 10:34:59 1998
Received: from nurock.kek.jp (root@nurock.kek.jp [130.87.218.140])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id KAA25649
	for <alsa-user@jcu.cz>; Mon, 26 Oct 1998 10:26:16 +0100
Received: from nurock.kek.jp (really [127.0.0.1]) by nurock.kek.jp
	via in.smtpd with esmtp (ident sharkey using rfc1413)
	id <m0zXioB-000TJDC@nurock.kek.jp> (Debian Smail3.2.0.101)
	for <alsa-user@jcu.cz>; Mon, 26 Oct 1998 18:19:27 +0900 (JST) 
Message-Id: <m0zXioB-000TJDC@nurock.kek.jp>
To: alsa-user@jcu.cz
cc: zarmzarm@erols.com
From: sharkey@ale.physics.sunysb.edu
Subject: Re: Machine locks on record, ALSA to blame? 
In-reply-to: Your message of "Mon, 26 Oct 1998 02:14:51 EST."
             <3634216B.63C@erols.com> 
Date: Mon, 26 Oct 1998 18:19:26 +0900
Reply-To: alsa-user@alsa.jcu.cz
Sender: alsa-user-owner@alsa.jcu.cz
Precedence: list

> > Normally, if one has the special SysRq functions enabled, I could hit
> > Alt-PrnScrn-S to sync the disks, Alt-PrnScrn-U to unmount them, and
> > Alt-PrnScrn-B to reboot.  I can't sync or umount on this type of lock,
> > but the reboot function works.  This is weird, nothing else makes this
> > happen.  Just thought I'd throw that out.
> 
> How do you enable those? THis is new to me... I can't reboot at all,
> short of just hitting the power button and risking filesystem problems.
>  
> I have yet to try 2.1; I started on Linux at 2.0.18 and am currently at
> 2.0.34.

The latter statement is evident from the former.  The special SysRq
feature is new in the 2.1 series kernels.

Eric

