All of lore.kernel.org
 help / color / mirror / Atom feed
From: James <bjlockie@lockie.ca>
To: linux-media Mailing List <linux-media@vger.kernel.org>
Subject: Re: freeze/crash
Date: Fri, 14 Oct 2011 14:38:46 -0400	[thread overview]
Message-ID: <4E9881B6.8070606@lockie.ca> (raw)
In-Reply-To: <op.v3b9bll93xmt7q@00-25-22-b5-7b-09.dummy.porta.siemens.net>

On 10/14/11 07:10, semiRocket wrote:
> On Fri, 14 Oct 2011 01:51:37 +0200, James <bjlockie@lockie.ca> wrote:
>
>> It always crashes when I access the hardware but the place it crashes
>> is random.
>
> Maybe you would want to pass those crash logs for debugging purposes :)
What crash logs?
The kernel locks up, is there a log somewhere?
>
> It's possible for developers to track from them where the crash occurs
> in driver.

It occurred to me to try the mythbuntu livedvd. :-)

That didn't work so I tried my other PCIe slot (I had to disconnect 
stuff to make it fit :-() and it works now.


  reply	other threads:[~2011-10-14 18:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-13 23:51 freeze/crash James
2011-10-14 11:10 ` freeze/crash semiRocket
2011-10-14 18:38   ` James [this message]
2011-10-14 21:53     ` freeze/crash semiRocket
2011-10-15  7:35       ` freeze/crash James
2011-10-15 11:38         ` freeze/crash semiRocket

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=4E9881B6.8070606@lockie.ca \
    --to=bjlockie@lockie.ca \
    --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.