* [linux-dvb] FusionHDTV7 and v4l causes kernel panic @ 2009-03-16 2:22 Timothy D. Lenz 2009-03-16 13:59 ` Steven Toth 0 siblings, 1 reply; 16+ messages in thread From: Timothy D. Lenz @ 2009-03-16 2:22 UTC (permalink / raw) To: linux-dvb 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 _______________________________________________ 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 ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic 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 2009-03-18 7:51 ` Timothy D. Lenz 0 siblings, 2 replies; 16+ messages in thread From: Steven Toth @ 2009-03-16 13:59 UTC (permalink / raw) To: linux-media; +Cc: linux-dvb 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 ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic 2009-03-16 13:59 ` Steven Toth @ 2009-03-17 0:46 ` Timothy D. Lenz 2009-03-17 1:07 ` Andy Walls 2009-03-18 7:51 ` Timothy D. Lenz 1 sibling, 1 reply; 16+ messages in thread From: Timothy D. Lenz @ 2009-03-17 0:46 UTC (permalink / raw) To: linux-media 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 ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic 2009-03-17 0:46 ` Timothy D. Lenz @ 2009-03-17 1:07 ` Andy Walls 2009-03-19 2:16 ` Timothy D. Lenz 0 siblings, 1 reply; 16+ messages in thread From: Andy Walls @ 2009-03-17 1:07 UTC (permalink / raw) To: Timothy D. Lenz; +Cc: linux-media On Mon, 2009-03-16 at 17:46 -0700, Timothy D. Lenz wrote: > 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. Not even Shift+PageUp ? > I looked at the logs and the ones that are text had nothing about it. Digital camera or 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 > ----- 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 > > -- > To unsubscribe from this list: send the line "unsubscribe linux-media" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic 2009-03-17 1:07 ` Andy Walls @ 2009-03-19 2:16 ` Timothy D. Lenz 2009-03-19 2:48 ` Andy Walls 0 siblings, 1 reply; 16+ messages in thread From: Timothy D. Lenz @ 2009-03-19 2:16 UTC (permalink / raw) To: linux-dvb I've added console=ttyS0,115200 console=tty0 to the kernel command line options and with out the console=tty0 part the dump no longer shows on the monitor, so redirect seems to work but loging the serial port on a second computer gets nothing. I tested the connection with echo and that worked but the kernel dump won't go out the port. The last 2 lines of the screen are: EIP: [<c012a8c6>] queue_work+0x3/0x68 SS:ESP 0068:f778dd24 Kernel panic - not syncing: Fatal exception in interrupt Any way to get the dump to go out the serial port? ----- Original Message ----- From: "Andy Walls" <awalls@radix.net> To: "Timothy D. Lenz" <tlenz@vorgon.com> Cc: <linux-media@vger.kernel.org> Sent: Monday, March 16, 2009 6:07 PM Subject: Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic > On Mon, 2009-03-16 at 17:46 -0700, Timothy D. Lenz wrote: > > 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. > > Not even Shift+PageUp ? > > > > > I looked at the logs and the ones that are text had nothing about it. > > Digital camera or 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 > > > > ----- 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 > > > > -- > > To unsubscribe from this list: send the line "unsubscribe linux-media" in > > the body of a message to majordomo@vger.kernel.org > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > > _______________________________________________ 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 ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic 2009-03-19 2:16 ` Timothy D. Lenz @ 2009-03-19 2:48 ` Andy Walls 2009-03-19 7:46 ` Timothy D. Lenz ` (2 more replies) 0 siblings, 3 replies; 16+ messages in thread From: Andy Walls @ 2009-03-19 2:48 UTC (permalink / raw) To: linux-media; +Cc: linux-dvb 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 console=tty0 part the dump no longer shows on the monitor, so redirect seems to > work but loging the serial port on a second computer gets nothing. I tested the connection with echo and that worked but the kernel > dump won't go out the port. The last 2 lines of the screen are: > > EIP: [<c012a8c6>] queue_work+0x3/0x68 SS:ESP 0068:f778dd24 > Kernel panic - not syncing: Fatal exception in interrupt Hmm. The only thing in the cx23885 driver that tries to schedule work, and thus the only thing that could possibly pass in a bad argument, is the netup_ci_slot_status() function. It gets called when an IRQ comes in indicating a GPIO[01] event, and the driver thinks the card is a NetUp Dual DVB-S2 CI card. That's consistent with the "fatal exception in interrupt", but without the backtrace, one can't be completely sure this call to queue work was initiated by the cx23885 driver and a problem with cx23885 data structures. (But it is the most likely scenario, IMO) I just can't see how netup_ci_slot_status() get's called for your card. > Any way to get the dump to go out the serial port? Does 9600 baud help? (Just a guess.) Regards, Andy > ----- Original Message ----- > From: "Andy Walls" <awalls@radix.net> > To: "Timothy D. Lenz" <tlenz@vorgon.com> > Cc: <linux-media@vger.kernel.org> > Sent: Monday, March 16, 2009 6:07 PM > Subject: Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic > > > > On Mon, 2009-03-16 at 17:46 -0700, Timothy D. Lenz wrote: > > > 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. > > > > Not even Shift+PageUp ? > > > > > > > > > I looked at the logs and the ones that are text had nothing about it. > > > > Digital camera or 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 > > > > > > > ----- 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 > > > > > > -- > > > To unsubscribe from this list: send the line "unsubscribe linux-media" in > > > the body of a message to majordomo@vger.kernel.org > > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > > > > > > > _______________________________________________ > 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 > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic 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 2 siblings, 0 replies; 16+ messages in thread From: Timothy D. Lenz @ 2009-03-19 7:46 UTC (permalink / raw) To: linux-media; +Cc: linux-dvb 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" <awalls@radix.net> To: <linux-media@vger.kernel.org> Cc: <linux-dvb@linuxtv.org> Sent: Wednesday, 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 console=tty0 part the dump no longer shows on the monitor, so redirect seems to > > work but loging the serial port on a second computer gets nothing. I tested the connection with echo and that worked but the kernel > > dump won't go out the port. The last 2 lines of the screen are: > > > > EIP: [<c012a8c6>] queue_work+0x3/0x68 SS:ESP 0068:f778dd24 > > Kernel panic - not syncing: Fatal exception in interrupt > > Hmm. The only thing in the cx23885 driver that tries to schedule work, > and thus the only thing that could possibly pass in a bad argument, is > the netup_ci_slot_status() function. It gets called when an IRQ comes > in indicating a GPIO[01] event, and the driver thinks the card is a > NetUp Dual DVB-S2 CI card. > > That's consistent with the "fatal exception in interrupt", but without > the backtrace, one can't be completely sure this call to queue work was > initiated by the cx23885 driver and a problem with cx23885 data > structures. (But it is the most likely scenario, IMO) > I just can't see how netup_ci_slot_status() get's called for your card. > > > > Any way to get the dump to go out the serial port? > > Does 9600 baud help? (Just a guess.) > > Regards, > Andy > > > ----- Original Message ----- > > From: "Andy Walls" <awalls@radix.net> > > To: "Timothy D. Lenz" <tlenz@vorgon.com> > > Cc: <linux-media@vger.kernel.org> > > Sent: Monday, March 16, 2009 6:07 PM > > Subject: Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic > > > > > > > On Mon, 2009-03-16 at 17:46 -0700, Timothy D. Lenz wrote: > > > > 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. > > > > > > Not even Shift+PageUp ? > > > > > > > > > > > > > I looked at the logs and the ones that are text had nothing about it. > > > > > > Digital camera or 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 > > > > > > > > > > ----- 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 > > > > > > > > -- > > > > To unsubscribe from this list: send the line "unsubscribe linux-media" in > > > > the body of a message to majordomo@vger.kernel.org > > > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > > > > > > > > > > > > _______________________________________________ > > 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 > > > > > _______________________________________________ > 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 ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic 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 2 siblings, 0 replies; 16+ messages in thread From: Timothy D. Lenz @ 2009-03-20 2:18 UTC (permalink / raw) To: linux-media After searching the internet for ways to redirect the error to serial or other system and not getting to work, I typed out by hand what is on the screen minus the cpu dump which is mostly scrolled off anyway and thus gone. In trying to get the dump out ttyS0 I found I was getting different dumps to screen. When I use: kernel /boot/vmlinuz-2.6.26.8.20090311.1 root=/dev/hda1 ro quiet console=ttyS0,115200n8 console=tty0 I get: Call Trace: [<f8aa406f>] netup_ci_slot_status+0x2e/0x34 [cx23885] [<f8aa07ff>] cx23885_irq+0x327/0x3d8 [cx23885] [<c013d10c>] handle_IRQ_event+0x1a/0x3f [<c013df36>] handle_fasteoi_irq+0x76/0xab [<c0105236>] do_IRQ+0x4f/0x65 [<c010366f>] common_interrupt+0x23/0x28 ======================= Code: 00 74 04 0f 0b eb fe 89 d8 e8 ed a3 ff ff ba 01 00 00 00 5b 89 d0 5e c3 51 89 d1 8b 15 20 ba 3e c0 e8 52 ff ff ff 5a c3 53 89 c3 <f0> 0f ba 2a 00 19 c0 31 c9 85 c0 75 54 8d 42 04 39 42 04 74 04 EIP: [<c012a8c6>] queue_work+0x3/0x68 SS:ESR 0068:f7733f40 Kernel panic - not syncing: Fatal exception in interrupt When I use the default setting: kernel /boot/vmlinuz-2.6.26.8.20090311.1 root=/dev/hda1 ro quiet I get: Call Trace: [<f8aa406f>] netup_ci_slot_status+0x2e/0x34 [cx23885] [<f8aa07ff>] cx23885_irq+0x327/0x3d8 [cx23885] [<c013d10c>] handle_IRQ_event+0x1a/0x3f [<c013df36>] handle_fasteoi_irq+0x76/0xab [<c0105236>] do_IRQ+0x4f/0x65 [<c010366f>] common_interrupt+0x23/0x28 [<c0308096>] _spin_unlock_irq+0x5/0x19 [<c011e3ba>] do_syslog+0x12f/0x2f1 [<c010369c>] reschedule_interrupt+0x28/0x30 [<c012cd38>] autoremove_wake_function+0x0/0x2d [<c018f27a>] kmsg_read+0x0/0x36 [<c01888cf>] proc_reg_read+0x60/0x73 [<c018886f>] proc_reg_read+0x0/0x73 [<c015d9cf>] vfs_read+0x81/0xf4 [<c015dada>] sys_read+0x3c/0x63 [<c0102c7d>] sysenter_past_esp+0x6a/0x91 ======================= Code: 00 74 04 0f 0b eb fe 89 d8 e8 ed a3 ff ff ba 01 00 00 00 5b 89 d0 5e c3 51 89 d1 8b 15 20 ba 3e c0 e8 52 ff ff ff 5a c3 53 89 c3 <f0> 0f ba 2a 00 19 c0 31 c9 85 c0 75 54 8d 42 04 39 42 04 74 04 EIP: [<c012a8c6>] queue_work+0x3/0x68 SS:ESR 0068:f7693e7c Kernel panic - not syncing: Fatal exception in interrupt It may be a bit different each time because I think I've seen longer "Call Trace" dumps ----- Original Message ----- From: "Andy Walls" <awalls@radix.net> To: <linux-media@vger.kernel.org> Cc: <linux-dvb@linuxtv.org> Sent: Wednesday, 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 console=tty0 part the dump no longer shows on the monitor, so redirect seems to > > work but loging the serial port on a second computer gets nothing. I tested the connection with echo and that worked but the kernel > > dump won't go out the port. The last 2 lines of the screen are: > > > > EIP: [<c012a8c6>] queue_work+0x3/0x68 SS:ESP 0068:f778dd24 > > Kernel panic - not syncing: Fatal exception in interrupt > > Hmm. The only thing in the cx23885 driver that tries to schedule work, > and thus the only thing that could possibly pass in a bad argument, is > the netup_ci_slot_status() function. It gets called when an IRQ comes > in indicating a GPIO[01] event, and the driver thinks the card is a > NetUp Dual DVB-S2 CI card. > > That's consistent with the "fatal exception in interrupt", but without > the backtrace, one can't be completely sure this call to queue work was > initiated by the cx23885 driver and a problem with cx23885 data > structures. (But it is the most likely scenario, IMO) > I just can't see how netup_ci_slot_status() get's called for your card. > > > > Any way to get the dump to go out the serial port? > > Does 9600 baud help? (Just a guess.) > > Regards, > Andy > > > ----- Original Message ----- > > From: "Andy Walls" <awalls@radix.net> > > To: "Timothy D. Lenz" <tlenz@vorgon.com> > > Cc: <linux-media@vger.kernel.org> > > Sent: Monday, March 16, 2009 6:07 PM > > Subject: Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic > > > > > > > On Mon, 2009-03-16 at 17:46 -0700, Timothy D. Lenz wrote: > > > > 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. > > > > > > Not even Shift+PageUp ? > > > > > > > > > > > > > I looked at the logs and the ones that are text had nothing about it. > > > > > > Digital camera or 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 > > > > > > > > > > ----- 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 > > > > > > > > -- > > > > To unsubscribe from this list: send the line "unsubscribe linux-media" in > > > > the body of a message to majordomo@vger.kernel.org > > > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > > > > > > > > > > > > _______________________________________________ > > 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 > > > > > _______________________________________________ > 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 ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic 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 2 siblings, 2 replies; 16+ messages in thread From: Timothy D. Lenz @ 2009-03-20 18:22 UTC (permalink / raw) To: linux-dvb Not sure where I was suposed to reply to. When replying I find the replys are coming from diffrent lists and out look is picking that up. At the bottom it says v4l related stuff should go to linux-media@vger.kernel.org, but the thread started in linux-dvb@linuxtv.org. So I'm re-replying in linux-dvb@linuxtv.org. After searching the internet for ways to redirect the error to serial or other system and not getting to work, I typed out by hand what is on the screen minus the cpu dump which is mostly scrolled off anyway and thus gone. In trying to get the dump out ttyS0 I found I was getting different dumps to screen. When I use: kernel /boot/vmlinuz-2.6.26.8.20090311.1 root=/dev/hda1 ro quiet console=ttyS0,115200n8 console=tty0 I get: Call Trace: [<f8aa406f>] netup_ci_slot_status+0x2e/0x34 [cx23885] [<f8aa07ff>] cx23885_irq+0x327/0x3d8 [cx23885] [<c013d10c>] handle_IRQ_event+0x1a/0x3f [<c013df36>] handle_fasteoi_irq+0x76/0xab [<c0105236>] do_IRQ+0x4f/0x65 [<c010366f>] common_interrupt+0x23/0x28 ======================= Code: 00 74 04 0f 0b eb fe 89 d8 e8 ed a3 ff ff ba 01 00 00 00 5b 89 d0 5e c3 51 89 d1 8b 15 20 ba 3e c0 e8 52 ff ff ff 5a c3 53 89 c3 <f0> 0f ba 2a 00 19 c0 31 c9 85 c0 75 54 8d 42 04 39 42 04 74 04 EIP: [<c012a8c6>] queue_work+0x3/0x68 SS:ESR 0068:f7733f40 Kernel panic - not syncing: Fatal exception in interrupt When I use the default setting: kernel /boot/vmlinuz-2.6.26.8.20090311.1 root=/dev/hda1 ro quiet I get: Call Trace: [<f8aa406f>] netup_ci_slot_status+0x2e/0x34 [cx23885] [<f8aa07ff>] cx23885_irq+0x327/0x3d8 [cx23885] [<c013d10c>] handle_IRQ_event+0x1a/0x3f [<c013df36>] handle_fasteoi_irq+0x76/0xab [<c0105236>] do_IRQ+0x4f/0x65 [<c010366f>] common_interrupt+0x23/0x28 [<c0308096>] _spin_unlock_irq+0x5/0x19 [<c011e3ba>] do_syslog+0x12f/0x2f1 [<c010369c>] reschedule_interrupt+0x28/0x30 [<c012cd38>] autoremove_wake_function+0x0/0x2d [<c018f27a>] kmsg_read+0x0/0x36 [<c01888cf>] proc_reg_read+0x60/0x73 [<c018886f>] proc_reg_read+0x0/0x73 [<c015d9cf>] vfs_read+0x81/0xf4 [<c015dada>] sys_read+0x3c/0x63 [<c0102c7d>] sysenter_past_esp+0x6a/0x91 ======================= Code: 00 74 04 0f 0b eb fe 89 d8 e8 ed a3 ff ff ba 01 00 00 00 5b 89 d0 5e c3 51 89 d1 8b 15 20 ba 3e c0 e8 52 ff ff ff 5a c3 53 89 c3 <f0> 0f ba 2a 00 19 c0 31 c9 85 c0 75 54 8d 42 04 39 42 04 74 04 EIP: [<c012a8c6>] queue_work+0x3/0x68 SS:ESR 0068:f7693e7c Kernel panic - not syncing: Fatal exception in interrupt It may be a bit different each time because I think I've seen longer "Call Trace" dumps ----- Original Message ----- From: "Andy Walls" <awalls@radix.net> To: <linux-media@vger.kernel.org> Cc: <linux-dvb@linuxtv.org> Sent: Wednesday, 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 console=tty0 part the dump no longer shows on the monitor, so redirect seems to > > work but loging the serial port on a second computer gets nothing. I tested the connection with echo and that worked but the kernel > > dump won't go out the port. The last 2 lines of the screen are: > > > > EIP: [<c012a8c6>] queue_work+0x3/0x68 SS:ESP 0068:f778dd24 > > Kernel panic - not syncing: Fatal exception in interrupt > > Hmm. The only thing in the cx23885 driver that tries to schedule work, > and thus the only thing that could possibly pass in a bad argument, is > the netup_ci_slot_status() function. It gets called when an IRQ comes > in indicating a GPIO[01] event, and the driver thinks the card is a > NetUp Dual DVB-S2 CI card. > > That's consistent with the "fatal exception in interrupt", but without > the backtrace, one can't be completely sure this call to queue work was > initiated by the cx23885 driver and a problem with cx23885 data > structures. (But it is the most likely scenario, IMO) > I just can't see how netup_ci_slot_status() get's called for your card. > > > > Any way to get the dump to go out the serial port? > > Does 9600 baud help? (Just a guess.) > > Regards, > Andy > > > ----- Original Message ----- > > From: "Andy Walls" <awalls@radix.net> > > To: "Timothy D. Lenz" <tlenz@vorgon.com> > > Cc: <linux-media@vger.kernel.org> > > Sent: Monday, March 16, 2009 6:07 PM > > Subject: Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic > > > > > > > On Mon, 2009-03-16 at 17:46 -0700, Timothy D. Lenz wrote: > > > > 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. > > > > > > Not even Shift+PageUp ? > > > > > > > > > > > > > I looked at the logs and the ones that are text had nothing about it. > > > > > > Digital camera or 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 > > > > > > > > > > ----- 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 _______________________________________________ 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 ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic 2009-03-20 18:22 ` Timothy D. Lenz @ 2009-03-20 21:33 ` Andy Walls 2009-03-21 1:10 ` Andy Walls 1 sibling, 0 replies; 16+ messages in thread From: Andy Walls @ 2009-03-20 21:33 UTC (permalink / raw) To: linux-media; +Cc: linux-dvb On Fri, 2009-03-20 at 11:22 -0700, Timothy D. Lenz wrote: > Not sure where I was suposed to reply to. When replying I find the replys are coming from diffrent lists and out look is picking > that up. At the bottom it says v4l related stuff should go to linux-media@vger.kernel.org, but the thread started in > linux-dvb@linuxtv.org. So I'm re-replying in linux-dvb@linuxtv.org. Tim, I didn't forget. I saw your message. (I've been busy with yardwork today.) Linux-media or linux-dvb are both appropriate lists. > After searching the internet for ways to redirect the error to serial or other system and not getting to work, I typed out by hand > what is on the screen minus the cpu dump which is mostly scrolled off anyway and thus gone. In trying to get the dump out ttyS0 I > found I was getting different dumps to screen. > When I use: > kernel /boot/vmlinuz-2.6.26.8.20090311.1 root=/dev/hda1 ro quiet console=ttyS0,115200n8 console=tty0 > > I get: > Call Trace: > [<f8aa406f>] netup_ci_slot_status+0x2e/0x34 [cx23885] > [<f8aa07ff>] cx23885_irq+0x327/0x3d8 [cx23885] > [<c013d10c>] handle_IRQ_event+0x1a/0x3f > [<c013df36>] handle_fasteoi_irq+0x76/0xab > [<c0105236>] do_IRQ+0x4f/0x65 > [<c010366f>] common_interrupt+0x23/0x28 > ======================= > Code: 00 74 04 0f 0b eb fe 89 d8 e8 ed a3 ff ff ba 01 00 00 00 5b 89 d0 5e c3 51 > 89 d1 8b 15 20 ba 3e c0 e8 52 ff ff ff 5a c3 53 89 c3 <f0> 0f ba 2a 00 19 c0 31 > c9 85 c0 75 54 8d 42 04 39 42 04 74 04 > EIP: [<c012a8c6>] queue_work+0x3/0x68 SS:ESR 0068:f7733f40 > Kernel panic - not syncing: Fatal exception in interrupt > > When I use the default setting: > kernel /boot/vmlinuz-2.6.26.8.20090311.1 root=/dev/hda1 ro quiet > > I get: > Call Trace: > [<f8aa406f>] netup_ci_slot_status+0x2e/0x34 [cx23885] > [<f8aa07ff>] cx23885_irq+0x327/0x3d8 [cx23885] > [<c013d10c>] handle_IRQ_event+0x1a/0x3f > [<c013df36>] handle_fasteoi_irq+0x76/0xab > [<c0105236>] do_IRQ+0x4f/0x65 > [<c010366f>] common_interrupt+0x23/0x28 > [<c0308096>] _spin_unlock_irq+0x5/0x19 > [<c011e3ba>] do_syslog+0x12f/0x2f1 > [<c010369c>] reschedule_interrupt+0x28/0x30 > [<c012cd38>] autoremove_wake_function+0x0/0x2d > [<c018f27a>] kmsg_read+0x0/0x36 > [<c01888cf>] proc_reg_read+0x60/0x73 > [<c018886f>] proc_reg_read+0x0/0x73 > [<c015d9cf>] vfs_read+0x81/0xf4 > [<c015dada>] sys_read+0x3c/0x63 > [<c0102c7d>] sysenter_past_esp+0x6a/0x91 > ======================= > Code: 00 74 04 0f 0b eb fe 89 d8 e8 ed a3 ff ff ba 01 00 00 00 5b 89 d0 5e c3 51 > 89 d1 8b 15 20 ba 3e c0 e8 52 ff ff ff 5a c3 53 89 c3 <f0> 0f ba 2a 00 19 c0 31 > c9 85 c0 75 54 8d 42 04 39 42 04 74 04 > EIP: [<c012a8c6>] queue_work+0x3/0x68 SS:ESR 0068:f7693e7c > Kernel panic - not syncing: Fatal exception in interrupt > > It may be a bit different each time because I think I've seen longer "Call Trace" dumps OK. This is the failure mode I thought. I'm not sure how it can happen: the driver treats your device like a NetUp unit, but you have a FusionHDTV7. I'll take a harder look later tonight. In the meantime, as a workaround you can "#if 0" out the following block of code in linux/driver/media/video/cx23885/cx23885-core.c:cx23885_irq(): #if 0 if (cx23885_boards[dev->board].cimax > 0 && ((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 not work right though... Regards, Andy > ----- Original Message ----- > From: "Andy Walls" <awalls@radix.net> > To: <linux-media@vger.kernel.org> > Cc: <linux-dvb@linuxtv.org> > Sent: Wednesday, 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 console=tty0 part the dump no longer shows on the monitor, so redirect seems > to > > > work but loging the serial port on a second computer gets nothing. I tested the connection with echo and that worked but the > kernel > > > dump won't go out the port. The last 2 lines of the screen are: > > > > > > EIP: [<c012a8c6>] queue_work+0x3/0x68 SS:ESP 0068:f778dd24 > > > Kernel panic - not syncing: Fatal exception in interrupt > > > > Hmm. The only thing in the cx23885 driver that tries to schedule work, > > and thus the only thing that could possibly pass in a bad argument, is > > the netup_ci_slot_status() function. It gets called when an IRQ comes > > in indicating a GPIO[01] event, and the driver thinks the card is a > > NetUp Dual DVB-S2 CI card. > > > > That's consistent with the "fatal exception in interrupt", but without > > the backtrace, one can't be completely sure this call to queue work was > > initiated by the cx23885 driver and a problem with cx23885 data > > structures. (But it is the most likely scenario, IMO) > > I just can't see how netup_ci_slot_status() get's called for your card. > > > > > > > Any way to get the dump to go out the serial port? > > > > Does 9600 baud help? (Just a guess.) > > > > Regards, > > Andy > > > > > ----- Original Message ----- > > > From: "Andy Walls" <awalls@radix.net> > > > To: "Timothy D. Lenz" <tlenz@vorgon.com> > > > Cc: <linux-media@vger.kernel.org> > > > Sent: Monday, March 16, 2009 6:07 PM > > > Subject: Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic > > > > > > > > > > On Mon, 2009-03-16 at 17:46 -0700, Timothy D. Lenz wrote: > > > > > 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. > > > > > > > > Not even Shift+PageUp ? > > > > > > > > > > > > > > > > > I looked at the logs and the ones that are text had nothing about it. > > > > > > > > Digital camera or 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 > > > > > > > > > > > > > ----- 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 > > > _______________________________________________ > 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 > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic 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 1 sibling, 1 reply; 16+ messages in thread From: Andy Walls @ 2009-03-21 1:10 UTC (permalink / raw) To: linux-media; +Cc: linux-dvb On Fri, 2009-03-20 at 11:22 -0700, Timothy D. Lenz wrote: > Not sure where I was suposed to reply to. When replying I find the replys are coming from diffrent lists and out look is picking > that up. At the bottom it says v4l related stuff should go to linux-media@vger.kernel.org, but the thread started in > linux-dvb@linuxtv.org. So I'm re-replying in linux-dvb@linuxtv.org. > > After searching the internet for ways to redirect the error to serial or other system and not getting to work, I typed out by hand > what is on the screen minus the cpu dump which is mostly scrolled off anyway and thus gone. In trying to get the dump out ttyS0 I > found I was getting different dumps to screen. > When I use: > kernel /boot/vmlinuz-2.6.26.8.20090311.1 root=/dev/hda1 ro quiet console=ttyS0,115200n8 console=tty0 > > I get: > Call Trace: > [<f8aa406f>] netup_ci_slot_status+0x2e/0x34 [cx23885] > [<f8aa07ff>] cx23885_irq+0x327/0x3d8 [cx23885] > [<c013d10c>] handle_IRQ_event+0x1a/0x3f > [<c013df36>] handle_fasteoi_irq+0x76/0xab > [<c0105236>] do_IRQ+0x4f/0x65 > [<c010366f>] common_interrupt+0x23/0x28 > ======================= > Code: 00 74 04 0f 0b eb fe 89 d8 e8 ed a3 ff ff ba 01 00 00 00 5b 89 d0 5e c3 51 > 89 d1 8b 15 20 ba 3e c0 e8 52 ff ff ff 5a c3 53 89 c3 <f0> 0f ba 2a 00 19 c0 31 > c9 85 c0 75 54 8d 42 04 39 42 04 74 04 > EIP: [<c012a8c6>] queue_work+0x3/0x68 SS:ESR 0068:f7733f40 > Kernel panic - not syncing: Fatal exception in interrupt > > When I use the default setting: > kernel /boot/vmlinuz-2.6.26.8.20090311.1 root=/dev/hda1 ro quiet > > I get: > Call Trace: > [<f8aa406f>] netup_ci_slot_status+0x2e/0x34 [cx23885] > [<f8aa07ff>] cx23885_irq+0x327/0x3d8 [cx23885] > [<c013d10c>] handle_IRQ_event+0x1a/0x3f > [<c013df36>] handle_fasteoi_irq+0x76/0xab > [<c0105236>] do_IRQ+0x4f/0x65 > [<c010366f>] common_interrupt+0x23/0x28 > [<c0308096>] _spin_unlock_irq+0x5/0x19 > [<c011e3ba>] do_syslog+0x12f/0x2f1 > [<c010369c>] reschedule_interrupt+0x28/0x30 > [<c012cd38>] autoremove_wake_function+0x0/0x2d > [<c018f27a>] kmsg_read+0x0/0x36 > [<c01888cf>] proc_reg_read+0x60/0x73 > [<c018886f>] proc_reg_read+0x0/0x73 > [<c015d9cf>] vfs_read+0x81/0xf4 > [<c015dada>] sys_read+0x3c/0x63 > [<c0102c7d>] sysenter_past_esp+0x6a/0x91 > ======================= > Code: 00 74 04 0f 0b eb fe 89 d8 e8 ed a3 ff ff ba 01 00 00 00 5b 89 d0 5e c3 51 > 89 d1 8b 15 20 ba 3e c0 e8 52 ff ff ff 5a c3 53 89 c3 <f0> 0f ba 2a 00 19 c0 31 > c9 85 c0 75 54 8d 42 04 39 42 04 74 04 > EIP: [<c012a8c6>] queue_work+0x3/0x68 SS:ESR 0068:f7693e7c > Kernel panic - not syncing: Fatal exception in interrupt Here is the kernel source code that corresponds to where the panic occurs in linux/kernel/workqueue.c: #define work_data_bits(work) ((unsigned long *)(&(work)->data)) #define WORK_STRUCT_PENDING 0 int queue_work(struct workqueue_struct *wq, struct work_struct *work) { int ret; ret = queue_work_on(get_cpu(), wq, work); put_cpu(); return ret; } int queue_work_on(int cpu, struct workqueue_struct *wq, struct work_struct *work) { int ret = 0; if (!test_and_set_bit(WORK_STRUCT_PENDING, work_data_bits(work))) { BUG_ON(!list_empty(&work->entry)); __queue_work(wq_per_cpu(wq, cpu), work); ret = 1; } return ret; } Here is the disassembled code bytes from the oops: ffd9: 74 04 je 0xffffffdf ffdb: 0f 0b ud2a ffdd: eb fe jmp 0xffffffdd ffdf: 89 d8 mov %ebx,%eax ffe1: e8 ed a3 ff ff call 0xffffa3d3 ffe6: ba 01 00 00 00 mov $0x1,%edx ffeb: 5b pop %ebx ffec: 89 d0 mov %edx,%eax ffee: 5e pop %esi ffef: c3 ret fff0: 51 push %ecx fff1: 89 d1 mov %edx,%ecx fff3: 8b 15 20 ba 3e c0 mov 0xc03eba20,%edx fff9: e8 52 ff ff ff call 0xffffff50 fffe: 5a pop %edx ffff: c3 ret 0: 53 push %ebx <--- queue_work() with queue_work_on() inlined starts here 1: 89 c3 mov %eax,%ebx 3: f0 0f ba 2a 00 lock btsl $0x0,(%edx) <--- Ooops here: test_and_set_bit(WORK_STRUCT_PENDING, work_data_bits(work)) 8: 19 c0 sbb %eax,%eax a: 31 c9 xor %ecx,%ecx c: 85 c0 test %eax,%eax e: 75 54 jne 0x64 10: 8d 42 04 lea 0x4(%edx),%eax 13: 39 42 04 cmp %eax,0x4(%edx) 16: 74 04 je 0x1c So "work" is NULL. No big surprise there. Work was never initialized. Here's how the code got there: (IRQ line fires, kernel call the cx23885 irq handler) linux/drivers/media/video/cx23885/cx23885-core.c:cx23885_irq():line 1716 linux/drivers/media/video/cx23885/cimax2.c:netup_ci_slot_status():line 345 linux/kernel/workqueue.c:schedule_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 given the "card=17" module parameter. Could you provide the output of "lspci -nnv" for you card? Could you also provide the startup messages from the module with the "debug=7" 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: "Andy Walls" <awalls@radix.net> > To: <linux-media@vger.kernel.org> > Cc: <linux-dvb@linuxtv.org> > Sent: Wednesday, 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 console=tty0 part the dump no longer shows on the monitor, so redirect seems > to > > > work but loging the serial port on a second computer gets nothing. I tested the connection with echo and that worked but the > kernel > > > dump won't go out the port. The last 2 lines of the screen are: > > > > > > EIP: [<c012a8c6>] queue_work+0x3/0x68 SS:ESP 0068:f778dd24 > > > Kernel panic - not syncing: Fatal exception in interrupt > > > > Hmm. The only thing in the cx23885 driver that tries to schedule work, > > and thus the only thing that could possibly pass in a bad argument, is > > the netup_ci_slot_status() function. It gets called when an IRQ comes > > in indicating a GPIO[01] event, and the driver thinks the card is a > > NetUp Dual DVB-S2 CI card. > > > > That's consistent with the "fatal exception in interrupt", but without > > the backtrace, one can't be completely sure this call to queue work was > > initiated by the cx23885 driver and a problem with cx23885 data > > structures. (But it is the most likely scenario, IMO) > > I just can't see how netup_ci_slot_status() get's called for your card. > > > > > > > Any way to get the dump to go out the serial port? > > > > Does 9600 baud help? (Just a guess.) > > > > Regards, > > Andy > > > > > ----- Original Message ----- > > > From: "Andy Walls" <awalls@radix.net> > > > To: "Timothy D. Lenz" <tlenz@vorgon.com> > > > Cc: <linux-media@vger.kernel.org> > > > Sent: Monday, March 16, 2009 6:07 PM > > > Subject: Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic > > > > > > > > > > On Mon, 2009-03-16 at 17:46 -0700, Timothy D. Lenz wrote: > > > > > 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. > > > > > > > > Not even Shift+PageUp ? > > > > > > > > > > > > > > > > > I looked at the logs and the ones that are text had nothing about it. > > > > > > > > Digital camera or 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 > > > > > > > > > > > > > ----- 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 > > > _______________________________________________ > 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 > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic 2009-03-21 1:10 ` Andy Walls @ 2009-03-21 9:03 ` Timothy D. Lenz 2009-03-21 15:32 ` Andy Walls 0 siblings, 1 reply; 16+ messages in thread From: Timothy D. Lenz @ 2009-03-21 9:03 UTC (permalink / raw) To: linux-media Not sure what you ment by "if you got the panic to stop by commenting out the call to the problem function?" You want me to comment something out in the driver and recompile v4l? With debug=7 it still panics and much of the call trace scrolled off and again, nothing went to serial port so no way to log it that I know of unless there is something else I can do to get the kernel to semd it's panic to ttyS0. As for lspci -nnv: 02:00.0 Multimedia video controller [0400]: Conexant Device [14f1:8852] (rev 02) Subsystem: DViCO Corporation Device [18ac:d618] Flags: bus master, fast devsel, latency 0, IRQ 255 Memory at fdc00000 (64-bit, non-prefetchable) [size=2M] Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [80] Power Management version 2 Capabilities: [90] Vital Product Data <?> Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- Capabilities: [100] Advanced Error Reporting <?> Capabilities: [200] Virtual Channel <?> Kernel modules: cx23885 ----- Original Message ----- From: "Andy Walls" <awalls@radix.net> To: <linux-media@vger.kernel.org> Cc: <linux-dvb@linuxtv.org> Sent: Friday, March 20, 2009 6:10 PM Subject: Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic > On Fri, 2009-03-20 at 11:22 -0700, Timothy D. Lenz wrote: > > Not sure where I was suposed to reply to. When replying I find the replys are coming from diffrent lists and out look is picking > > that up. At the bottom it says v4l related stuff should go to linux-media@vger.kernel.org, but the thread started in > > linux-dvb@linuxtv.org. So I'm re-replying in linux-dvb@linuxtv.org. > > > > After searching the internet for ways to redirect the error to serial or other system and not getting to work, I typed out by hand > > what is on the screen minus the cpu dump which is mostly scrolled off anyway and thus gone. In trying to get the dump out ttyS0 I > > found I was getting different dumps to screen. > > When I use: > > kernel /boot/vmlinuz-2.6.26.8.20090311.1 root=/dev/hda1 ro quiet console=ttyS0,115200n8 console=tty0 > > > > I get: > > Call Trace: > > [<f8aa406f>] netup_ci_slot_status+0x2e/0x34 [cx23885] > > [<f8aa07ff>] cx23885_irq+0x327/0x3d8 [cx23885] > > [<c013d10c>] handle_IRQ_event+0x1a/0x3f > > [<c013df36>] handle_fasteoi_irq+0x76/0xab > > [<c0105236>] do_IRQ+0x4f/0x65 > > [<c010366f>] common_interrupt+0x23/0x28 > > ======================= > > Code: 00 74 04 0f 0b eb fe 89 d8 e8 ed a3 ff ff ba 01 00 00 00 5b 89 d0 5e c3 51 > > 89 d1 8b 15 20 ba 3e c0 e8 52 ff ff ff 5a c3 53 89 c3 <f0> 0f ba 2a 00 19 c0 31 > > c9 85 c0 75 54 8d 42 04 39 42 04 74 04 > > EIP: [<c012a8c6>] queue_work+0x3/0x68 SS:ESR 0068:f7733f40 > > Kernel panic - not syncing: Fatal exception in interrupt > > > > When I use the default setting: > > kernel /boot/vmlinuz-2.6.26.8.20090311.1 root=/dev/hda1 ro quiet > > > > I get: > > Call Trace: > > [<f8aa406f>] netup_ci_slot_status+0x2e/0x34 [cx23885] > > [<f8aa07ff>] cx23885_irq+0x327/0x3d8 [cx23885] > > [<c013d10c>] handle_IRQ_event+0x1a/0x3f > > [<c013df36>] handle_fasteoi_irq+0x76/0xab > > [<c0105236>] do_IRQ+0x4f/0x65 > > [<c010366f>] common_interrupt+0x23/0x28 > > [<c0308096>] _spin_unlock_irq+0x5/0x19 > > [<c011e3ba>] do_syslog+0x12f/0x2f1 > > [<c010369c>] reschedule_interrupt+0x28/0x30 > > [<c012cd38>] autoremove_wake_function+0x0/0x2d > > [<c018f27a>] kmsg_read+0x0/0x36 > > [<c01888cf>] proc_reg_read+0x60/0x73 > > [<c018886f>] proc_reg_read+0x0/0x73 > > [<c015d9cf>] vfs_read+0x81/0xf4 > > [<c015dada>] sys_read+0x3c/0x63 > > [<c0102c7d>] sysenter_past_esp+0x6a/0x91 > > ======================= > > Code: 00 74 04 0f 0b eb fe 89 d8 e8 ed a3 ff ff ba 01 00 00 00 5b 89 d0 5e c3 51 > > 89 d1 8b 15 20 ba 3e c0 e8 52 ff ff ff 5a c3 53 89 c3 <f0> 0f ba 2a 00 19 c0 31 > > c9 85 c0 75 54 8d 42 04 39 42 04 74 04 > > EIP: [<c012a8c6>] queue_work+0x3/0x68 SS:ESR 0068:f7693e7c > > Kernel panic - not syncing: Fatal exception in interrupt > > > Here is the kernel source code that corresponds to where the panic > occurs in linux/kernel/workqueue.c: > > #define work_data_bits(work) ((unsigned long *)(&(work)->data)) > > #define WORK_STRUCT_PENDING 0 > > int queue_work(struct workqueue_struct *wq, struct work_struct *work) > { > int ret; > > ret = queue_work_on(get_cpu(), wq, work); > put_cpu(); > > return ret; > } > > int > queue_work_on(int cpu, struct workqueue_struct *wq, struct work_struct *work) > { > int ret = 0; > > if (!test_and_set_bit(WORK_STRUCT_PENDING, work_data_bits(work))) { > BUG_ON(!list_empty(&work->entry)); > __queue_work(wq_per_cpu(wq, cpu), work); > ret = 1; > } > return ret; > } > > Here is the disassembled code bytes from the oops: > > ffd9: 74 04 je 0xffffffdf > ffdb: 0f 0b ud2a > ffdd: eb fe jmp 0xffffffdd > ffdf: 89 d8 mov %ebx,%eax > ffe1: e8 ed a3 ff ff call 0xffffa3d3 > ffe6: ba 01 00 00 00 mov $0x1,%edx > ffeb: 5b pop %ebx > ffec: 89 d0 mov %edx,%eax > ffee: 5e pop %esi > ffef: c3 ret > fff0: 51 push %ecx > fff1: 89 d1 mov %edx,%ecx > fff3: 8b 15 20 ba 3e c0 mov 0xc03eba20,%edx > fff9: e8 52 ff ff ff call 0xffffff50 > fffe: 5a pop %edx > ffff: c3 ret > 0: 53 push %ebx <--- queue_work() with queue_work_on() inlined starts here > 1: 89 c3 mov %eax,%ebx > 3: f0 0f ba 2a 00 lock btsl $0x0,(%edx) <--- Ooops here: test_and_set_bit(WORK_STRUCT_PENDING, work_data_bits(work)) > 8: 19 c0 sbb %eax,%eax > a: 31 c9 xor %ecx,%ecx > c: 85 c0 test %eax,%eax > e: 75 54 jne 0x64 > 10: 8d 42 04 lea 0x4(%edx),%eax > 13: 39 42 04 cmp %eax,0x4(%edx) > 16: 74 04 je 0x1c > > So "work" is NULL. No big surprise there. > > Work was never initialized. Here's how the code got there: > > (IRQ line fires, kernel call the cx23885 irq handler) > linux/drivers/media/video/cx23885/cx23885-core.c:cx23885_irq():line 1716 > linux/drivers/media/video/cx23885/cimax2.c:netup_ci_slot_status():line 345 > linux/kernel/workqueue.c:schedule_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 > given the "card=17" module parameter. > > Could you provide the output of "lspci -nnv" for you card? > > Could you also provide the startup messages from the module with the > "debug=7" 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: "Andy Walls" <awalls@radix.net> > > To: <linux-media@vger.kernel.org> > > Cc: <linux-dvb@linuxtv.org> > > Sent: Wednesday, 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 console=tty0 part the dump no longer shows on the monitor, so redirect seems > > to > > > > work but loging the serial port on a second computer gets nothing. I tested the connection with echo and that worked but the > > kernel > > > > dump won't go out the port. The last 2 lines of the screen are: > > > > > > > > EIP: [<c012a8c6>] queue_work+0x3/0x68 SS:ESP 0068:f778dd24 > > > > Kernel panic - not syncing: Fatal exception in interrupt > > > > > > Hmm. The only thing in the cx23885 driver that tries to schedule work, > > > and thus the only thing that could possibly pass in a bad argument, is > > > the netup_ci_slot_status() function. It gets called when an IRQ comes > > > in indicating a GPIO[01] event, and the driver thinks the card is a > > > NetUp Dual DVB-S2 CI card. > > > > > > That's consistent with the "fatal exception in interrupt", but without > > > the backtrace, one can't be completely sure this call to queue work was > > > initiated by the cx23885 driver and a problem with cx23885 data > > > structures. (But it is the most likely scenario, IMO) > > > I just can't see how netup_ci_slot_status() get's called for your card. > > > > > > > > > > Any way to get the dump to go out the serial port? > > > > > > Does 9600 baud help? (Just a guess.) > > > > > > Regards, > > > Andy > > > > > > > ----- Original Message ----- > > > > From: "Andy Walls" <awalls@radix.net> > > > > To: "Timothy D. Lenz" <tlenz@vorgon.com> > > > > Cc: <linux-media@vger.kernel.org> > > > > Sent: Monday, March 16, 2009 6:07 PM > > > > Subject: Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic > > > > > > > > > > > > > On Mon, 2009-03-16 at 17:46 -0700, Timothy D. Lenz wrote: > > > > > > 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. > > > > > > > > > > Not even Shift+PageUp ? > > > > > > > > > > > > > > > > > > > > > I looked at the logs and the ones that are text had nothing about it. > > > > > > > > > > Digital camera or 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 > > > > > > > > > > > > > > > > ----- 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 > > > > > > _______________________________________________ > > 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 > > > > > _______________________________________________ > 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 ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic 2009-03-21 9:03 ` Timothy D. Lenz @ 2009-03-21 15:32 ` Andy Walls [not found] ` <000401c9aa59$730d42f0$0a00a8c0@vorg> 0 siblings, 1 reply; 16+ messages in thread From: Andy Walls @ 2009-03-21 15:32 UTC (permalink / raw) To: Timothy D. Lenz; +Cc: linux-media On Sat, 2009-03-21 at 02:03 -0700, Timothy D. Lenz wrote: > Not sure what you ment by "if you got the panic to stop by commenting out the call to the problem function?" You want me to comment > something out in the driver and recompile v4l? Yes. I sent two different e-mails. I'm soory if it caused confusion. To see what's going on we need the panic to stop so we can see what the driver is doing in the logs when being modporbe'd. PLease add "#if 0/#endif" around to following block of code in linux/driver/media/video/cx23885/cx23885-core.c:cx23885_irq(): #if 0 if (cx23885_boards[dev->board].cimax > 0 && ((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 and recompile and reinstall v4l-dvb. That should stop this particular panic for you. (Things still may not work, though.) > With debug=7 it still panics and much of the call trace scrolled off and again, > nothing went to serial port so no way to log it that I know of unless there is something else I can do to get the kernel to semd > it's panic to ttyS0. There is othing more to be learned from the panic(). We need the logs from the driver starting up with debugging turned on. So that those logs get written to disk, we likely need to stop the panic from happening with the above hack. > As for lspci -nnv: > > 02:00.0 Multimedia video controller [0400]: Conexant Device [14f1:8852] (rev 02) > Subsystem: DViCO Corporation Device [18ac:d618] > Flags: bus master, fast devsel, latency 0, IRQ 255 > Memory at fdc00000 (64-bit, non-prefetchable) [size=2M] > Capabilities: [40] Express Endpoint, MSI 00 > Capabilities: [80] Power Management version 2 > Capabilities: [90] Vital Product Data <?> > Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- > Capabilities: [100] Advanced Error Reporting <?> > Capabilities: [200] Virtual Channel <?> > Kernel modules: cx23885 Thanks. This is the PCI Subsystem ID's that the cx23885 driver should recognize as a FusionHDTV7. 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" <awalls@radix.net> > To: <linux-media@vger.kernel.org> > Cc: <linux-dvb@linuxtv.org> > Sent: Friday, March 20, 2009 6:10 PM > Subject: Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic > > > > On Fri, 2009-03-20 at 11:22 -0700, Timothy D. Lenz wrote: > > > Not sure where I was suposed to reply to. When replying I find the replys are coming from diffrent lists and out look is picking > > > that up. At the bottom it says v4l related stuff should go to linux-media@vger.kernel.org, but the thread started in > > > linux-dvb@linuxtv.org. So I'm re-replying in linux-dvb@linuxtv.org. > > > > > > After searching the internet for ways to redirect the error to serial or other system and not getting to work, I typed out by > hand > > > what is on the screen minus the cpu dump which is mostly scrolled off anyway and thus gone. In trying to get the dump out ttyS0 > I > > > found I was getting different dumps to screen. > > > When I use: > > > kernel /boot/vmlinuz-2.6.26.8.20090311.1 root=/dev/hda1 ro quiet console=ttyS0,115200n8 console=tty0 > > > > > > I get: > > > Call Trace: > > > [<f8aa406f>] netup_ci_slot_status+0x2e/0x34 [cx23885] > > > [<f8aa07ff>] cx23885_irq+0x327/0x3d8 [cx23885] > > > [<c013d10c>] handle_IRQ_event+0x1a/0x3f > > > [<c013df36>] handle_fasteoi_irq+0x76/0xab > > > [<c0105236>] do_IRQ+0x4f/0x65 > > > [<c010366f>] common_interrupt+0x23/0x28 > > > ======================= > > > Code: 00 74 04 0f 0b eb fe 89 d8 e8 ed a3 ff ff ba 01 00 00 00 5b 89 d0 5e c3 51 > > > 89 d1 8b 15 20 ba 3e c0 e8 52 ff ff ff 5a c3 53 89 c3 <f0> 0f ba 2a 00 19 c0 31 > > > c9 85 c0 75 54 8d 42 04 39 42 04 74 04 > > > EIP: [<c012a8c6>] queue_work+0x3/0x68 SS:ESR 0068:f7733f40 > > > Kernel panic - not syncing: Fatal exception in interrupt > > > > > > When I use the default setting: > > > kernel /boot/vmlinuz-2.6.26.8.20090311.1 root=/dev/hda1 ro quiet > > > > > > I get: > > > Call Trace: > > > [<f8aa406f>] netup_ci_slot_status+0x2e/0x34 [cx23885] > > > [<f8aa07ff>] cx23885_irq+0x327/0x3d8 [cx23885] > > > [<c013d10c>] handle_IRQ_event+0x1a/0x3f > > > [<c013df36>] handle_fasteoi_irq+0x76/0xab > > > [<c0105236>] do_IRQ+0x4f/0x65 > > > [<c010366f>] common_interrupt+0x23/0x28 > > > [<c0308096>] _spin_unlock_irq+0x5/0x19 > > > [<c011e3ba>] do_syslog+0x12f/0x2f1 > > > [<c010369c>] reschedule_interrupt+0x28/0x30 > > > [<c012cd38>] autoremove_wake_function+0x0/0x2d > > > [<c018f27a>] kmsg_read+0x0/0x36 > > > [<c01888cf>] proc_reg_read+0x60/0x73 > > > [<c018886f>] proc_reg_read+0x0/0x73 > > > [<c015d9cf>] vfs_read+0x81/0xf4 > > > [<c015dada>] sys_read+0x3c/0x63 > > > [<c0102c7d>] sysenter_past_esp+0x6a/0x91 > > > ======================= > > > Code: 00 74 04 0f 0b eb fe 89 d8 e8 ed a3 ff ff ba 01 00 00 00 5b 89 d0 5e c3 51 > > > 89 d1 8b 15 20 ba 3e c0 e8 52 ff ff ff 5a c3 53 89 c3 <f0> 0f ba 2a 00 19 c0 31 > > > c9 85 c0 75 54 8d 42 04 39 42 04 74 04 > > > EIP: [<c012a8c6>] queue_work+0x3/0x68 SS:ESR 0068:f7693e7c > > > Kernel panic - not syncing: Fatal exception in interrupt > > > > > > Here is the kernel source code that corresponds to where the panic > > occurs in linux/kernel/workqueue.c: > > > > #define work_data_bits(work) ((unsigned long *)(&(work)->data)) > > > > #define WORK_STRUCT_PENDING 0 > > > > int queue_work(struct workqueue_struct *wq, struct work_struct *work) > > { > > int ret; > > > > ret = queue_work_on(get_cpu(), wq, work); > > put_cpu(); > > > > return ret; > > } > > > > int > > queue_work_on(int cpu, struct workqueue_struct *wq, struct work_struct *work) > > { > > int ret = 0; > > > > if (!test_and_set_bit(WORK_STRUCT_PENDING, work_data_bits(work))) { > > BUG_ON(!list_empty(&work->entry)); > > __queue_work(wq_per_cpu(wq, cpu), work); > > ret = 1; > > } > > return ret; > > } > > > > Here is the disassembled code bytes from the oops: > > > > ffd9: 74 04 je 0xffffffdf > > ffdb: 0f 0b ud2a > > ffdd: eb fe jmp 0xffffffdd > > ffdf: 89 d8 mov %ebx,%eax > > ffe1: e8 ed a3 ff ff call 0xffffa3d3 > > ffe6: ba 01 00 00 00 mov $0x1,%edx > > ffeb: 5b pop %ebx > > ffec: 89 d0 mov %edx,%eax > > ffee: 5e pop %esi > > ffef: c3 ret > > fff0: 51 push %ecx > > fff1: 89 d1 mov %edx,%ecx > > fff3: 8b 15 20 ba 3e c0 mov 0xc03eba20,%edx > > fff9: e8 52 ff ff ff call 0xffffff50 > > fffe: 5a pop %edx > > ffff: c3 ret > > 0: 53 push %ebx <--- queue_work() with queue_work_on() inlined starts here > > 1: 89 c3 mov %eax,%ebx > > 3: f0 0f ba 2a 00 lock btsl $0x0,(%edx) <--- Ooops here: test_and_set_bit(WORK_STRUCT_PENDING, work_data_bits(work)) > > 8: 19 c0 sbb %eax,%eax > > a: 31 c9 xor %ecx,%ecx > > c: 85 c0 test %eax,%eax > > e: 75 54 jne 0x64 > > 10: 8d 42 04 lea 0x4(%edx),%eax > > 13: 39 42 04 cmp %eax,0x4(%edx) > > 16: 74 04 je 0x1c > > > > So "work" is NULL. No big surprise there. > > > > Work was never initialized. Here's how the code got there: > > > > (IRQ line fires, kernel call the cx23885 irq handler) > > linux/drivers/media/video/cx23885/cx23885-core.c:cx23885_irq():line 1716 > > linux/drivers/media/video/cx23885/cimax2.c:netup_ci_slot_status():line 345 > > linux/kernel/workqueue.c:schedule_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 > > given the "card=17" module parameter. > > > > Could you provide the output of "lspci -nnv" for you card? > > > > Could you also provide the startup messages from the module with the > > "debug=7" 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: "Andy Walls" <awalls@radix.net> > > > To: <linux-media@vger.kernel.org> > > > Cc: <linux-dvb@linuxtv.org> > > > Sent: Wednesday, 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 console=tty0 part the dump no longer shows on the monitor, so redirect > seems > > > to > > > > > work but loging the serial port on a second computer gets nothing. I tested the connection with echo and that worked but the > > > kernel > > > > > dump won't go out the port. The last 2 lines of the screen are: > > > > > > > > > > EIP: [<c012a8c6>] queue_work+0x3/0x68 SS:ESP 0068:f778dd24 > > > > > Kernel panic - not syncing: Fatal exception in interrupt > > > > > > > > Hmm. The only thing in the cx23885 driver that tries to schedule work, > > > > and thus the only thing that could possibly pass in a bad argument, is > > > > the netup_ci_slot_status() function. It gets called when an IRQ comes > > > > in indicating a GPIO[01] event, and the driver thinks the card is a > > > > NetUp Dual DVB-S2 CI card. > > > > > > > > That's consistent with the "fatal exception in interrupt", but without > > > > the backtrace, one can't be completely sure this call to queue work was > > > > initiated by the cx23885 driver and a problem with cx23885 data > > > > structures. (But it is the most likely scenario, IMO) > > > > I just can't see how netup_ci_slot_status() get's called for your card. > > > > > > > > > > > > > Any way to get the dump to go out the serial port? > > > > > > > > Does 9600 baud help? (Just a guess.) > > > > > > > > Regards, > > > > Andy > > > > > > > > > ----- Original Message ----- > > > > > From: "Andy Walls" <awalls@radix.net> > > > > > To: "Timothy D. Lenz" <tlenz@vorgon.com> > > > > > Cc: <linux-media@vger.kernel.org> > > > > > Sent: Monday, March 16, 2009 6:07 PM > > > > > Subject: Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic > > > > > > > > > > > > > > > > On Mon, 2009-03-16 at 17:46 -0700, Timothy D. Lenz wrote: > > > > > > > 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. > > > > > > > > > > > > Not even Shift+PageUp ? > > > > > > > > > > > > > > > > > > > > > > > > > I looked at the logs and the ones that are text had nothing about it. > > > > > > > > > > > > Digital camera or 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 > > > > > > > > > > > > > > > > > > > ----- 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 > > > > > > > > > _______________________________________________ > > > 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 > > > > > > > > > _______________________________________________ > > 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 > > -- > To unsubscribe from this list: send the line "unsubscribe linux-media" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > ^ permalink raw reply [flat|nested] 16+ messages in thread
[parent not found: <000401c9aa59$730d42f0$0a00a8c0@vorg>]
* Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic [not found] ` <000401c9aa59$730d42f0$0a00a8c0@vorg> @ 2009-03-21 23:08 ` Andy Walls 0 siblings, 0 replies; 16+ messages in thread From: Andy Walls @ 2009-03-21 23:08 UTC (permalink / raw) To: Timothy D. Lenz; +Cc: linux-media, linux-dvb On Sat, 2009-03-21 at 12:15 -0700, Timothy D. Lenz wrote: > modprobe cx23885 card=10 debug =7 still cause panic. > > I searched in /usr/src/v4l/v4l-dvb/linux/drivers/media/video/cx23885/cx23885-core.c and the closest section to what you list looks > like this: > > if ((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); > Oh. You're not using the latest v4l-dvb repo. I see Hans fix your particular bug about 8 days 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" <awalls@radix.net> > To: "Timothy D. Lenz" <tlenz@vorgon.com> > Cc: <linux-media@vger.kernel.org> > Sent: Saturday, March 21, 2009 8:32 AM > Subject: Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic > > > > On Sat, 2009-03-21 at 02:03 -0700, Timothy D. Lenz wrote: > > > Not sure what you ment by "if you got the panic to stop by commenting out the call to the problem function?" You want me to > comment > > > something out in the driver and recompile v4l? > > > > Yes. I sent two different e-mails. I'm soory if it caused confusion. > > > > To see what's going on we need the panic to stop so we can see what the > > driver is doing in the logs when being modporbe'd. > > > > PLease add "#if 0/#endif" around to following block of code in > > linux/driver/media/video/cx23885/cx23885-core.c:cx23885_irq(): > > > > #if 0 > > if (cx23885_boards[dev->board].cimax > 0 && > > ((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 > > > > and recompile and reinstall v4l-dvb. That should stop this particular > > panic for you. (Things still may not work, though.) > > > > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic 2009-03-16 13:59 ` Steven Toth 2009-03-17 0:46 ` Timothy D. Lenz @ 2009-03-18 7:51 ` Timothy D. Lenz 2009-03-18 13:27 ` Brandon Jenkins 1 sibling, 1 reply; 16+ messages in thread From: Timothy D. Lenz @ 2009-03-18 7:51 UTC (permalink / raw) To: linux-dvb 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? ----- 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 _______________________________________________ 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 ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] FusionHDTV7 and v4l causes kernel panic 2009-03-18 7:51 ` Timothy D. Lenz @ 2009-03-18 13:27 ` Brandon Jenkins 0 siblings, 0 replies; 16+ messages in thread From: Brandon Jenkins @ 2009-03-18 13:27 UTC (permalink / raw) To: linux-media On Wed, Mar 18, 2009 at 3:51 AM, Timothy D. Lenz <tlenz@vorgon.com> 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 source tree. ^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2009-03-21 23:07 UTC | newest]
Thread overview: 16+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
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
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.