From: Peter Surda <shurdeek@panorama.sth.ac.at>
To: alsa-user@lists.sourceforge.net, alsa-devel@lists.sourceforge.net
Subject: Re: second repost: oops on intel8x0
Date: Thu, 14 Feb 2002 11:32:26 +0100 [thread overview]
Message-ID: <a4g4hc$tr1$1@quimby2.netfonds.no> (raw)
In-Reply-To: <Pine.LNX.4.32.0202140117440.14856-100000@yme.mo.himolde.no>; from knan@mo.himolde.no on Thu, Feb 14, 2002 at 01:21:43AM +0100
[-- Attachment #1.1: Type: text/plain, Size: 508 bytes --]
Hi!
Finally an answer :-)
On Thu, Feb 14, 2002 at 01:21:43AM +0100, Erik Inge Bolsř wrote:
> <oopses snipped>
> >After they happen, sound card remains silent and module blocked.
> Decode the oopses with ksymoops, then we'll have a better chance of
> figuring out what the problem is.
Attached, all 4 oopses thru ksymoops -dd.
Bye,
Peter Surda (Shurdeek) <shurdeek@panorama.sth.ac.at>, ICQ 10236103, +436505122023
--
My mind is like a steel trap - rusty and illegal in 37 states.
[-- Attachment #1.2: ksymoops.tar.bz2 --]
[-- Type: application/x-bzip2, Size: 10346 bytes --]
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-02-14 10:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020214001543.V2103@shurdeek.cb.ac.at>
2002-02-14 0:21 ` second repost: oops on intel8x0 Erik Inge Bolsø
[not found] ` <Pine.LNX.4.32.0202140117440.14856-100000@yme.mo.himolde.no>
2002-02-14 10:32 ` Peter Surda [this message]
[not found] <20020214113226.A2103@shurdeek.cb.ac.at>
2002-02-14 10:56 ` Erik Inge Bolsø
[not found] ` <Pine.LNX.4.32.0202141150430.11654-100000@yme.mo.himolde.no>
2002-02-14 11:42 ` Peter Surda
2002-02-14 12:22 ` Takashi Iwai
[not found] ` <s5hit9045i6.wl@alsa2.suse.de>
2002-02-14 12:45 ` Peter Surda
2002-02-13 23:15 Peter Surda
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='a4g4hc$tr1$1@quimby2.netfonds.no' \
--to=shurdeek@panorama.sth.ac.at \
--cc=alsa-devel@lists.sourceforge.net \
--cc=alsa-user@lists.sourceforge.net \
/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.