From: Abramo Bagnara <abramo.bagnara@libero.it>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@lists.sourceforge.net
Subject: Re: crash trace under gdb
Date: Fri, 09 May 2003 19:57:57 +0200 [thread overview]
Message-ID: <3EBBEC25.7090909@libero.it> (raw)
In-Reply-To: <E19EBut-0002ql-00@sc8-sf-list1.sourceforge.net>
Paul Davis ha scritto:
>>However it would be nice if Paul help us to track down the source of the
>>bug, or give a test case for someone willing to help and with access to
>>SMP hardware.
>
>
> i'm happy to help out, but there's very little information available
> from the system when it happens. it also turns out (unsuprisingly) not
> to require gdb at all: the last time it happened, i started JACK up
> and within a few seconds the system was locked.
1) Are you using linked streams?
2) What's the complete call trace on lock (alt-sysrq-T)?
--
Abramo Bagnara mailto:abramo.bagnara@libero.it
Opera Unica Phone: +39.546.656023
Via Emilia Interna, 140
48014 Castel Bolognese (RA) - Italy
-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com
next prev parent reply other threads:[~2003-05-09 17:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 14:05 crash trace under gdb Paul Davis
2003-05-09 14:23 ` Takashi Iwai
2003-05-09 14:31 ` Paul Davis
2003-05-09 15:39 ` Paul Davis
[not found] ` <20030509153542.E0A9D14CE5@Cantor.suse.de>
2003-05-09 15:41 ` Takashi Iwai
2003-05-09 17:28 ` Abramo Bagnara
2003-05-09 17:48 ` Paul Davis
2003-05-09 17:57 ` Abramo Bagnara [this message]
2003-05-09 18:11 ` Paul Davis
[not found] ` <20030509174418.C8F9714CE0@Cantor.suse.de>
2003-05-09 17:49 ` 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=3EBBEC25.7090909@libero.it \
--to=abramo.bagnara@libero.it \
--cc=alsa-devel@lists.sourceforge.net \
--cc=paul@linuxaudiosystems.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