From: Florian <alsa@bome.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: crash/reboot with rawmidi on ice1712 dual opteron
Date: Tue, 24 Apr 2007 19:51:50 +0200 [thread overview]
Message-ID: <462E43B6.7050401@bome.com> (raw)
In-Reply-To: <s5hps5tzue1.wl%tiwai@suse.de>
IT WORKED! I fixed it in this way:
mpu401_uart.c:229
if (mpu->hardware != MPU401_HW_TRID4DWAVE
&& mpu->hardware != MPU401_HW_ICE1712) {
mpu->write(mpu, 0x00, MPU401D(mpu));
/*snd_mpu401_uart_clear_rx(mpu);*/
}
I don't know if this will work on non-AMD machines and if it will
work on all ice1712 machines... Next week I can test it with
different M-Audio cards on single-processor machines (Pentium and AMD).
Thanks a lot!
Florian
On 4/24/2007 5:04 PM, Takashi Iwai wrote:
> At Tue, 24 Apr 2007 16:53:20 +0200,
> Florian wrote:
>>> When the hang-up occurs at the first write, it must be in
>>> snd_mpu401_uart_cmd(). At the very beginning, it calls
>>> mpu->write(mpu, 0x00, MPU401D(mpu)); Try to comment out this and
>>> see what happens.
>> I had tried that - I think that I just commented out the reset
>> command.
>
> The reset command contains a series of writes. The write access (zero
> to 0x304c) is the very first part, and this isn't always necessary.
> For example, trident doesn't like this sequence. So, just commenting
> out this write should be fairly harmless to the later behavior.
>
> So, commenting only the first zero write is worth to try (if you
> didn't do yet).
>
>
>> It would not crash or reboot, but it did not haver
>> functionality either.
>
>>> Do I understand correctly that this bug happens when you open a
>>> rawmidi device for read, e.g. % cat /dev/snd/midiC0D0 > /dev/null
>>>
>> yes. I usually used
>> amidi -p hw:0 -d
>>
>>> Perhaps an easiest but foolishest way to trace this is to put
>>> printk at each io-port access and any other important points, and
>>> give some sleep at each point, then watch the kernel message.
>>> You can get rid of spin_lock_*() around that, just for testing.
>> I've done this until I traced it to the first outb() call, i.e. the
>> initialization mentioned above. The first outb() will cause the reboot.
>
> And this causes an immediate reboot, not panic or oops, right?
> You shouldn't do this kind of debug on X but on VGA console, BTW.
>
>
> Takashi
>
>
--
Florian Bomers
bome.com
-------------------------------------------------------
Music Software, Development Tools: http://www.bome.com
Java Sound extensions, plugins: http://www.tritonus.org
The Java Sound Resources: http://www.jsresources.org
-------------------------------------------------------
Please quote this email in your reply. Thanks!
next prev parent reply other threads:[~2007-04-24 17:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <461FD727.8080400@bome.com>
[not found] ` <s5hfy6zcmtc.wl%tiwai@suse.de>
[not found] ` <4626361D.3080801@bome.com>
2007-04-24 12:54 ` crash/reboot with rawmidi on ice1712 dual opteron Takashi Iwai
2007-04-24 13:27 ` Florian
2007-04-24 13:39 ` Takashi Iwai
2007-04-24 13:43 ` Florian
2007-04-24 13:51 ` Takashi Iwai
2007-04-24 14:12 ` Florian
2007-04-24 14:23 ` Takashi Iwai
2007-04-24 14:53 ` Florian
2007-04-24 15:04 ` Takashi Iwai
2007-04-24 17:51 ` Florian [this message]
2007-04-25 9:12 ` Daniel James
2007-04-25 13:07 ` Florian
2007-04-25 13:11 ` Takashi Iwai
2007-04-25 13:56 ` Florian
2007-04-24 14:23 ` Daniel James
2007-04-24 14:32 ` Takashi Iwai
2007-04-24 15:03 ` Daniel James
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=462E43B6.7050401@bome.com \
--to=alsa@bome.com \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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.