Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic

2009-03-21 Thread Andy Walls
ago and it was pulled in some time after then: http://linuxtv.org/hg/v4l-dvb/rev/6e85a8c897e9 [big snip] Use the latest v4l-dvb. I bet you'll be fine. Regards, Andy > - Original Message - > From: "Andy Walls" > To: "Timothy D. Lenz" > Cc: >

Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic

2009-03-21 Thread Andy Walls
When you modprobe the cx23885 module have you tried forcing the card type with the "card=10" option to the FusionHDTV7? Regards, Andy > ----- Original Message - > From: "Andy Walls" > To: > Cc: > Sent: Friday, March 20, 2009 6:10 PM > Subject: Re: [linux-dv

Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic

2009-03-21 Thread Timothy D. Lenz
hedule_work():line 621 > linux/kernel/workqueue.c:queue_work():line 164 > linux/kernel/workqueue.c:queue_work_on():line 187 > > I've looked through the cx23885 code and can't find how a Fusion HDTV7 > could be confued with a NetUp card, unless the cx23885 module is being >

Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic

2009-03-20 Thread Andy Walls
t; module parameter set, if you got the panic to stop by commenting out the call to the problem function? Regards, Andy > It may be a bit different each time because I think I've seen longer "Call > Trace" dumps > > - Original Message - > From: "

Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic

2009-03-20 Thread Andy Walls
amp;& ((pci_status & PCI_MSK_GPIO0) || (pci_status & PCI_MSK_GPIO1))) /* handled += cx23885_irq_gpio(dev, pci_status); */ handled += netup_ci_slot_status(dev, pci_status); #endif that should stop this particular panic for you. Things still may no

Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic

2009-03-19 Thread Timothy D. Lenz
y, March 18, 2009 7:48 PM Subject: Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic > On Wed, 2009-03-18 at 19:16 -0700, Timothy D. Lenz wrote: > > I've added > > console=ttyS0,115200 console=tty0 > > to the kernel command line options and with out the con

Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic

2009-03-19 Thread Timothy D. Lenz
No, changing baud rate to 9600 has no effect. It is simply not sending the log to the serial port. - Original Message - From: "Andy Walls" To: Cc: Sent: Wednesday, March 18, 2009 7:48 PM Subject: Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic > On Wed, 2009-0

Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic

2009-03-18 Thread Andy Walls
r pencil and paper will be least complex way to capture > > the ooops data. Please don't leave out the "Code" bytes at the bottom > > and do your best to make sure those are absolutely correct. > > > > Regards, > > Andy > > > > > > >

Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic

2009-03-18 Thread Brandon Jenkins
On Wed, Mar 18, 2009 at 3:51 AM, Timothy D. Lenz wrote: > Anyone know how to get the crash data to a log file? A way to redirect main > monitor to an ssh client or second linux computer > through serial port and null modem cable? > See the Documentation/serial-console.txt file in your kernel sou

Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic

2009-03-16 Thread Andy Walls
gt; From: "Steven Toth" > To: > Cc: > 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 &g

Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic

2009-03-16 Thread Timothy D. Lenz
h 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 > > W

Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic

2009-03-16 Thread Steven Toth
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 -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.or