All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Chuck Ebbert <76306.1226@compuserve.com>,
	Knut J Bjuland <knutjbj@online.no>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: I can cause kernel panic by using native alsa midi with 2.6.17.1
Date: Sun, 25 Jun 2006 19:43:07 -0400	[thread overview]
Message-ID: <20060625234307.GA29712@redhat.com> (raw)
In-Reply-To: <1151265654.2931.256.camel@mindpipe>

On Sun, Jun 25, 2006 at 04:00:53PM -0400, Lee Revell wrote:
 > On Sun, 2006-06-25 at 02:31 -0400, Dave Jones wrote:
 > > On Sun, Jun 25, 2006 at 02:03:21AM -0400, Chuck Ebbert wrote:
 > >  > In-Reply-To: <449B8A0D.60607@online.no>
 > >  > 
 > >  > On Fri, 23 Jun 2006 08:28:29 +0200, Knut J Bjuland wrote:
 > >  > 
 > >  > > ksymoops 2.4.9 on i686 2.6.17-1.2138_FC5smp.  Options used
 > >  > 
 > >  > Please do not run oops reports through ksymoops.  The recipient
 > >  > can do that.  And report Fedora bugs to Fedora...
 > > 
 > > It's already in Fedora bugzilla. It matches the same thing I reported
 > > here a few days ago. With a list-head debug patch (kinda sorta
 > > the same as the one in -mm), alsa goes boom.
 > 
 > I have not seen a bug report in the ALSA bug tracker
 > or a report on alsa-devel.

http://lkml.org/lkml/2006/6/22/505
was Cc'd to alsa-devel.

		Dave
-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2006-06-25 23:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-25  6:03 I can cause kernel panic by using native alsa midi with 2.6.17.1 Chuck Ebbert
2006-06-25  6:31 ` Dave Jones
2006-06-25 20:00   ` Lee Revell
2006-06-25 23:43     ` Dave Jones [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-06-23  6:28 Knut J Bjuland
2006-06-27 19:58 ` Lee Revell

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=20060625234307.GA29712@redhat.com \
    --to=davej@redhat.com \
    --cc=76306.1226@compuserve.com \
    --cc=knutjbj@online.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    /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.