From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000006]: Machine locks up hard on rmmod snd_es1968
Date: Tue, 31 May 2005 18:02:15 +0200 [thread overview]
Message-ID: <8ed07d31b819993706adf7b4644fbe40@bugtrack.alsa-project.org> (raw)
The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=6>
======================================================================
Reported By: Hai
Assigned To: perex
======================================================================
Project: ALSA - driver
Issue ID: 6
Category: PCI - es1968
Reproducibility: always
Severity: crash
Priority: normal
Status: closed
Distribution: SuSE 9.0
Kernel Version: 2.6.1-4-default
Resolution: suspended
Fixed in Version:
======================================================================
Date Submitted: 01-27-2004 21:49 CET
Last Modified: 05-31-2005 18:02 CEST
======================================================================
Summary: Machine locks up hard on rmmod snd_es1968
Description:
When my init scripts rmmod snd_es1968 on shutdown, the machine locks up
completely. SysRq-[TPUS] all do not work, only SysRq-[OB] work. This means
I get an hang on every shutdown/reboot
======================================================================
----------------------------------------------------------------------
tiwai - 01-28-04 15:23
----------------------------------------------------------------------
the irq should be disabled in snd_es1968_reset(), which is called
before synchronize_irq().
as mentioned, the purpose of the patch is to disable the docking
station and the hw volume features, i suspect as the culprit.
----------------------------------------------------------------------
perex - 03-09-04 18:43
----------------------------------------------------------------------
No input from user.
Issue History
Date Modified Username Field Change
======================================================================
01-27-04 21:49 Hai New Issue
01-28-04 11:37 tiwai Status new => assigned
01-28-04 11:37 tiwai Assigned To => tiwai
01-28-04 12:25 tiwai Note Added: 0000015
01-28-04 12:26 tiwai File Added: es1968-no-hwvol.dif
01-28-04 12:40 Hai Note Added: 0000016
01-28-04 15:23 tiwai Note Added: 0000017
03-09-04 18:43 perex Status assigned => resolved
03-09-04 18:43 perex Resolution open => suspended
03-09-04 18:43 perex Assigned To tiwai => perex
03-09-04 18:43 perex Note Added: 0000553
05-31-05 18:02 perex Status resolved => closed
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
next reply other threads:[~2005-05-31 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 16:02 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-28 11:40 [ALSA - driver 0000006]: Machine locks up hard on rmmod snd_es1968 noreply
2004-01-28 11:25 noreply
2004-01-28 10:37 noreply
2004-01-27 20:49 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=8ed07d31b819993706adf7b4644fbe40@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.