From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000167]: alsamixer crashes system when snd-ioctl32 is loaded
Date: Sat, 20 Nov 2004 11:14:13 +0100 [thread overview]
Message-ID: <519484c16a350b2bc3d1910e1eecd0cd@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-20-2004 11:14 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.
======================================================================
----------------------------------------------------------------------
eradicator - 11-20-04 10:23
----------------------------------------------------------------------
A patch for one fix can be found here:
http://bugs.gentoo.org/attachment.cgi?id=44333&action=view
That is sufficient to get 'amixer' working.
I'm going to go through and fix the other IOCTL now, and after it's
tested, I'll post the final patch here for you.
----------------------------------------------------------------------
eradicator - 11-20-04 11:14
----------------------------------------------------------------------
I updated the patch to fix a few more of the broken ioctl32 calls...
http://bugs.gentoo.org/attachment.cgi?id=44338&action=edit
All that's left is pcm32.c... hopefully I'll get to it sometime this
weekend...
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
11-19-04 05:46 weeve Issue Monitored: weeve
11-19-04 05:55 rlrevell Note Added: 0002475
11-20-04 10:23 eradicator Note Added: 0002478
11-20-04 11:14 eradicator Note Added: 0002479
======================================================================
-------------------------------------------------------
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
next reply other threads:[~2004-11-20 10:14 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-20 10:14 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-19 4:55 bugtrack
2004-11-19 4:45 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=519484c16a350b2bc3d1910e1eecd0cd@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