From: Takashi Iwai <tiwai@suse.de>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: Jaroslav Kysela <perex@suse.cz>,
"alsa-devel@lists.sourceforge.net"
<alsa-devel@lists.sourceforge.net>
Subject: Re: ALSA CVS and JACK?
Date: Wed, 26 Feb 2003 10:13:27 +0100 [thread overview]
Message-ID: <s5hsmubxv48.wl@alsa2.suse.de> (raw)
In-Reply-To: <E18nkIs-0002Oa-00@sc8-sf-list1.sourceforge.net>
At Tue, 25 Feb 2003 14:02:05 -0500,
Paul Davis wrote:
>
> >Can we see reports? I don't see any reason for crashes.
>
> nobody that this has happened to so far has had an oops trace. they
> are always running graphical apps and do not have a serial console. i
> am too nervous (:) to try it myself (hence i still have ALSA CVS from
> way back). apparently it may it also be connected to a particular
> kernel version.
isn't it the 2.4.20+ext3 problem?
> i would say that at least 6-8 people on jackit-dev have reported this.
hmm, i couldn't find the thread... oops+ALSA hits only the ext3
problem.
could you give the pointer?
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
next prev parent reply other threads:[~2003-02-26 9:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 17:37 ALSA CVS and JACK? Paul Davis
2003-02-25 17:57 ` Jaroslav Kysela
2003-02-25 19:02 ` Paul Davis
2003-02-26 9:13 ` Takashi Iwai [this message]
2003-02-26 19:25 ` jfm3
2003-02-25 18:06 ` Maarten de Boer
2003-02-25 19:00 ` Paul Davis
2003-02-25 20:53 ` jfm3
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=s5hsmubxv48.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=paul@linuxaudiosystems.com \
--cc=perex@suse.cz \
/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.