Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000167]: alsamixer crashes system when snd-ioctl32 is loaded
Date: Fri, 19 Nov 2004 05:45:39 +0100	[thread overview]
Message-ID: <3cbfe813e4945a9e071d4cef3c5c168b@bugtrack.alsa-project.org> (raw)


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=167> 
======================================================================
Reported By:                bons78
Assigned To:                
======================================================================
Project:                    ALSA - driver
Issue ID:                   167
Category:                   SPARC - cs4231
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Distribution:               debian/unstable
Kernel Version:             linux-2.6.4+
======================================================================
Date Submitted:             03-30-2004 00:02 CEST
Last Modified:              11-19-2004 05:45 CET
======================================================================
Summary:                    alsamixer crashes system when snd-ioctl32 is loaded
Description: 
alsamixer crashes system hard when snd-ioctl32 is loaded.
System still responds to some sysrq commands (sync remount boot show) -
sysrq (term killall) has no effect.
There's no chance to do any other keyboard input. No logs, no traps, no
oops. Machine still responds to ping,(even port 22 stays open) but login
via ssh is not possible. 

alsamixer, of course, is useless without the ioctl32 wrapper loaded - but
does not crash the system then.
So I suspect a problem in the ioctl32 wrapper.



======================================================================

----------------------------------------------------------------------
 weeve - 07-04-04 22:32 
----------------------------------------------------------------------
Just an update to say that this is still valid up through 2.6.7-bk12

----------------------------------------------------------------------
 weeve - 11-19-04 05:45 
----------------------------------------------------------------------
>From a recent thread on the sparclinux mailing list
<http://marc.theaimsgroup.com/?t=110017101000004&r=1&w=2>, get_fs() ==
KERNEL_DS will always cause a SPARC64 machne to hang.

Issue History
Date Modified  Username       Field                    Change              
======================================================================
03-30-04 00:02 bons78         New Issue                                    
03-30-04 00:02 bons78         Distribution              => debian/unstable 
03-30-04 00:02 bons78         Kernel Version            => linux-2.6.4+    
04-13-04 19:41 tiwai          Note Added: 0000795                          
07-04-04 22:32 weeve          Note Added: 0001381                          
07-05-04 08:09 eradicator     Issue Monitored: eradicator                    
11-19-04 05:45 weeve          Note Added: 0002474                          
======================================================================




-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8

             reply	other threads:[~2004-11-19  4:45 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-19  4:45 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-03 15:55 [ALSA - driver 0000167]: alsamixer crashes system when snd-ioctl32 is loaded bugtrack
2004-12-02 18:22 bugtrack
2004-11-29 14:08 bugtrack
2004-11-29 13:45 bugtrack
2004-11-29 12:20 bugtrack
2004-11-28 12:14 bugtrack
2004-11-27 21:05 bugtrack
2004-11-27 18:25 bugtrack
2004-11-26 20:53 bugtrack
2004-11-26 20:40 bugtrack
2004-11-26 20:05 bugtrack
2004-11-26 19:31 bugtrack
2004-11-26 14:17 bugtrack
2004-11-26 11:40 bugtrack
2004-11-26  8:22 bugtrack
2004-11-26  7:26 bugtrack
2004-11-25 11:22 bugtrack
2004-11-24 22:31 bugtrack
2004-11-24 22:24 bugtrack
2004-11-24 13:52 bugtrack
2004-11-24 13:29 bugtrack
2004-11-24 12:09 bugtrack
2004-11-24 12:01 bugtrack
2004-11-24 12:01 bugtrack
2004-11-24 11:53 bugtrack
2004-11-24  9:26 bugtrack
2004-11-23 14:34 bugtrack
2004-11-23  9:16 bugtrack
2004-11-22 15:22 bugtrack
2004-11-21 23:49 bugtrack
2004-11-21 23:08 bugtrack
2004-11-21 21:46 bugtrack
2004-11-21 20:36 bugtrack
2004-11-21 20:26 bugtrack
2004-11-21 16:44 bugtrack
2004-11-21 11:54 bugtrack
2004-11-21 10:57 bugtrack
2004-11-21 10:50 bugtrack
2004-11-21 10:39 bugtrack
2004-11-21  2:05 bugtrack
2004-11-20 15:36 bugtrack
2004-11-20 10:14 bugtrack
2004-11-19  4:55 bugtrack
2004-07-04 20:32 noreply

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=3cbfe813e4945a9e071d4cef3c5c168b@bugtrack.alsa-project.org \
    --to=bugtrack@alsa-project.org \
    --cc=alsa-devel@alsa-project.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