From: Daniel James <daniel@64studio.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Lee Revell <rlrevell@joe-job.com>,
alsa-devel@lists.sourceforge.net,
Free Ekanayaka <free@64studio.com>
Subject: Re: More info on hard lock-ups with MIDI on envy24, x86_64 machine
Date: Mon, 19 Sep 2005 10:17:13 +0100 [thread overview]
Message-ID: <200509191017.13233.daniel@64studio.com> (raw)
In-Reply-To: <s5h4q8lrq80.wl%tiwai@suse.de>
Hi Takashi,
> > It's made no difference I'm afraid - and there are no clues
> > in /var/log/messages that I can see.
>
> The patch is to the lock up of the driver, not the ACPI stuff.
Other than running a MIDI program such as seq24 with strace, is there
anything I can do to help diagnose this lock-up? Any logging options
I should be enabling?
I have found on the Tyan site that they released a BIOS update for
another one of their motherboards which was shipped with buggy IRQ
routing. When we have our second Opteron test system running (which
has an ASUS board) then we'll be able to confirm that it is a
specific hardware problem.
Cheers!
Daniel
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
next prev parent reply other threads:[~2005-09-19 9:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 14:25 More info on hard lock-ups with MIDI on envy24, x86_64 machine Daniel James
2005-08-11 14:29 ` Lee Revell
2005-08-11 14:59 ` Daniel James
2005-08-11 15:43 ` Daniel James
2005-08-11 16:19 ` Lee Revell
2005-09-08 15:53 ` Daniel James
2005-09-14 11:18 ` Daniel James
2005-09-14 12:24 ` Takashi Iwai
2005-09-14 13:34 ` Daniel James
2005-09-16 12:52 ` Daniel James
2005-09-16 15:23 ` Takashi Iwai
2005-09-19 9:17 ` Daniel James [this message]
2005-12-05 12:34 ` Daniel James
2005-12-09 14:40 ` Takashi Iwai
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=200509191017.13233.daniel@64studio.com \
--to=daniel@64studio.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=free@64studio.com \
--cc=rlrevell@joe-job.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox