All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Kujau <evil@g-house.de>
To: Jesper Juhl <juhl-lkml@dif.dk>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: ALSA Oops (triggered by xmms)
Date: Fri, 15 Apr 2005 02:15:34 +0200	[thread overview]
Message-ID: <425F07A6.2010402@g-house.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0504150150240.3466@dragon.hyggekrogen.localhost>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jesper Juhl wrote:
> 
>   ^^^^^ you should send such info inline in the email - having to go check 
> external links makes a lot of people ignore the stuff right then and 

yeah, but the oops doesn't wrap at 80 chars itsself and often oopses are
hardly readable inline.

> Btw: I believe this is fixed in 2.6.11.7 - from the Changelog : 
>
> <tiwai@suse.de>
> 	[PATCH] Fix Oops with ALSA timer event notification

oh, this sounds good. strange though, that my 2.6.11-gentoo-r5 (whatever
they've patched in there) *never* oopsed the days ago but all of a sudden
started to oops yesterday....


thank you,
Christian.
- --
BOFH excuse #131:

telnet: Unable to connect to remote host: Connection refused
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCXwem+A7rjkF8z0wRAuXSAJ4tZujWF0H5Da5o2J6yfzZQJolhPACgiKUR
YknU154MUkPEB52FuYTTF50=
=5yoy
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2005-04-15  0:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-14 23:22 ALSA Oops (triggered by xmms) Christian Kujau
2005-04-14 23:35 ` Lee Revell
2005-04-14 23:35   ` Lee Revell
2005-04-15  0:16   ` Christian Kujau
2005-04-15  0:21     ` Lee Revell
2005-04-15  8:54   ` [Alsa-devel] " Takashi Iwai
2005-04-15 14:54     ` Christian Kujau
     [not found] ` <Pine.LNX.4.62.0504150150240.3466@dragon.hyggekrogen.localhost>
2005-04-15  0:15   ` Christian Kujau [this message]
2005-04-15  0:29     ` Jesper Juhl
2005-04-15  8:19     ` Daniel Drake

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=425F07A6.2010402@g-house.de \
    --to=evil@g-house.de \
    --cc=juhl-lkml@dif.dk \
    --cc=linux-kernel@vger.kernel.org \
    /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.