From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001477]: inserting maestro3 hangs system
Date: Mon, 17 Oct 2005 19:37:58 +0200 [thread overview]
Message-ID: <f313ffd950a193fae69dd32e150575ed@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1477>
======================================================================
Reported By: cra
Assigned To: tiwai
======================================================================
Project: ALSA - driver
Issue ID: 1477
Category: PCI - maestro3
Reproducibility: always
Severity: crash
Priority: normal
Status: assigned
Distribution: Fedora Core 5 (development)
Kernel Version: 2.6.13-1.1600_FC5
======================================================================
Date Submitted: 10-16-2005 17:03 CEST
Last Modified: 10-17-2005 19:37 CEST
======================================================================
Summary: inserting maestro3 hangs system
Description:
Kernel hangs upon loading snd-maestro3 driver during hardware
initialization. The system only hangs if Windows was not booted prior to
booting Linux. So it seems that the Windows driver is poking the hardware
in some way that "helps" the Linux driver, and basically the ALSA driver
is not initializing the hardware correctly.
Bug cross-reference:
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000376
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=134507
======================================================================
----------------------------------------------------------------------
cra - 10-17-05 19:37
----------------------------------------------------------------------
The attached patch linux-2.6-maestro3-assp-init.patch fixes this issue for
me. It seems that the driver tries to start the ASSP before downloading
the DSP code to it, which explains why booting Windows before warm-booting
Linux works. A warm boot must not clear the DSP memory, which allows the
ASSP startup to succeed.
The fix is to call the snd_m3_assp_init function to write the DSP firmware
into the ASSP chip before sending the RUN_ASSP command. I also made the
same fix in the OSS driver, but I did not test the OSS fix.
Issue History
Date Modified Username Field Change
======================================================================
10-16-05 17:03 cra New Issue
10-16-05 17:03 cra Distribution => Fedora Core 5
(development)
10-16-05 17:03 cra Kernel Version => 2.6.13-1.1600_FC5
10-16-05 17:18 cra File Added: dmesg.txt
10-16-05 17:19 cra File Added: lspci.txt
10-16-05 17:19 cra File Added: dmidecode.txt
10-16-05 17:40 cra File Added: linux-2.6-debug-maestro3.patch
10-16-05 17:41 cra File Added: alsa-warmboot-after-win2k.txt
10-16-05 17:43 cra File Added: alsa-coldboot-hang.txt
10-16-05 17:44 cra File Added: oss-coldboot-hang.txt
10-17-05 19:32 cra File Added: linux-2.6-maestro3-assp-init.patch
10-17-05 19:37 cra Note Added: 0006487
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
next reply other threads:[~2005-10-17 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 17:37 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-20 12:53 [ALSA - driver 0001477]: inserting maestro3 hangs system bugtrack
2005-10-18 16:40 bugtrack
2005-10-18 15:27 bugtrack
2005-10-16 15:03 bugtrack
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=f313ffd950a193fae69dd32e150575ed@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