From: "Timothy D. Lenz" <tlenz@vorgon.com>
To: <linux-media@vger.kernel.org>
Subject: Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic
Date: Mon, 16 Mar 2009 17:46:57 -0700 [thread overview]
Message-ID: <003a01c9a69a$0de42640$0a00a8c0@vorg> (raw)
In-Reply-To: 49BE5B36.1080901@linuxtv.org
When it panics, there is no log, just a bunch of stuff that that scrolls fast on the main monitor then cold lock. No way to scroll
back. I looked at the logs and the ones that are text had nothing about it.
----- Original Message -----
From: "Steven Toth" <stoth@linuxtv.org>
To: <linux-media@vger.kernel.org>
Cc: <linux-dvb@linuxtv.org>
Sent: Monday, March 16, 2009 6:59 AM
Subject: Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic
> Timothy D. Lenz wrote:
> > Using kernel 2.6.26.8 and v4l from a few days ago. When I modprobe cx23885 to load the drivers, I get kernel panic
>
> We'll need the oops.
>
> - Steve
>
> _______________________________________________
> 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
next prev parent reply other threads:[~2009-03-17 0:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 2:22 [linux-dvb] FusionHDTV7 and v4l causes kernel panic Timothy D. Lenz
2009-03-16 13:59 ` Steven Toth
2009-03-17 0:46 ` Timothy D. Lenz [this message]
2009-03-17 1:07 ` Andy Walls
2009-03-19 2:16 ` Timothy D. Lenz
2009-03-19 2:48 ` Andy Walls
2009-03-19 7:46 ` Timothy D. Lenz
2009-03-20 2:18 ` Timothy D. Lenz
2009-03-20 18:22 ` Timothy D. Lenz
2009-03-20 21:33 ` Andy Walls
2009-03-21 1:10 ` Andy Walls
2009-03-21 9:03 ` Timothy D. Lenz
2009-03-21 15:32 ` Andy Walls
[not found] ` <000401c9aa59$730d42f0$0a00a8c0@vorg>
2009-03-21 23:08 ` Andy Walls
2009-03-18 7:51 ` Timothy D. Lenz
2009-03-18 13:27 ` Brandon Jenkins
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='003a01c9a69a$0de42640$0a00a8c0@vorg' \
--to=tlenz@vorgon.com \
--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.