All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marios Andreopoulos <opensource@andmarios.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] KWORLD 323U, kernel panic when trying to access ALSA interface
Date: Thu, 15 Oct 2009 20:23:28 +0300	[thread overview]
Message-ID: <200910152023.28840.opensource@andmarios.com> (raw)
In-Reply-To: <829197380910150853l6797a053qd2d9e05ec3b7552e@mail.gmail.com>

On Thursday 15 of October 2009, Devin Heitmueller wrote:
> 
> Hello Marios,
> 
> Sorry about the extended delay on this.  Please try out the following
> tree and see if you still hit a panic:
> 
> http://www.kernellabs.com/hg/~dheitmueller/em28xx-audio-panic
> 
> Cheers,
> 
> Devin
> 
> 
Hello Devin,

There is no need to apologize for anything! I am the one in debt here. :-)

I tried your tree but unfortunately I still get a kernel panic. Could it be that we have different hardware?
I confirmed that the modules compiled from your tree are installed in my current kernel’s module directory and
I made more than enough tries (aka panic and reboot), just to be sure.

Thanks for all the effort,
Marios

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

  reply	other threads:[~2009-10-15 17:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-28 15:50 [linux-dvb] KWORLD 323U, kernel panic when trying to access ALSA interface Marios Andreopoulos
2009-09-28 15:56 ` Devin Heitmueller
2009-09-28 16:09   ` Marios Andreopoulos
2009-10-15 15:53     ` Devin Heitmueller
2009-10-15 17:23       ` Marios Andreopoulos [this message]
2009-11-04 18:33       ` Marios Andreopoulos
2009-11-04 18:42         ` Devin Heitmueller
2009-09-28 16:19   ` Marios Andreopoulos

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=200910152023.28840.opensource@andmarios.com \
    --to=opensource@andmarios.com \
    --cc=dheitmueller@kernellabs.com \
    --cc=linux-dvb@linuxtv.org \
    --cc=linux-media@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.