Re: 3.7/3.8 kernel won't boot with Hauppauge pvr-150

Re: 3.7/3.8 kernel won't boot with Hauppauge pvr-150

[Andy Walls]

Ron Andreasen <dlanor78@gmail.com> wrote:

>I've been having trouble getting distros that have any kernel above the
>3.5
>series to boot (only tried 64-bit). I get a black screen with a bunch
>of
>text and the boot process goes no further. I don't know if this is
>usually
>okay, but I'm posting a link to a picture I took of my monitor with my
>cell
>phone. It's a bit blurry but hopefully it's still okay:
>
>http://imgur.com/viP1kWk,3YJXKbG
>
>The distros I've had this problem in are Kubuntu (I've tried several of
>the
>daily builds) which uses the 3.8.? (can't boot far enough to see)
>kernel,
>Cinnarch which uses the 3.7.3 kernel, and openSUSE 12.3 and I don't
>remember what version of the kernel that one used.
>
>My processor is a AMD Phenom(tm) 9850 Quad-Core Processor with all four
>cores unlocked. The output of lspci -vvv (in Kubuntu 12.10) can be
>found at
>[redacted]. I have 6 gb of ddr2 ram. Not sure
>what
>else I need to include so if you need more please let me know.
>
>When I was testing out Cinnarch I was able to boot by taking the
>Hauppauge
>PVR-150 out of the computer so I know for sure that's the hardware that
>was
>causing the problem. I haven't found any other way to boot with the
>card
>in. I tried different boot options. The ones I can remember are
>nomodeset
>and noacpi (or something like that). The distro I'm currently using is
>Kubuntu 12.10 and the kernel as of this writing is 3.5.0-24

For now rename the ivtv-alsa.ko module to ivtv-alsa.ko.orig 

If that doesn't allow a normal boot, blacklist the ivtv module in /etc/modprobe.d/blacklist.  That way your machine will at least boot.

It looks like the ivtv module is failing to initialize, starts to unload, and in the process of unloading, the cleanup path causes an Ooops.  

I should have time to look closer at it this weekend.

Regards,
Andy

Re: 3.7/3.8 kernel won't boot with Hauppauge pvr-150

[Andy Walls]

On Thu, 2013-02-21 at 22:32 -0500, Andy Walls wrote:
> Ron Andreasen <dlanor78@gmail.com> wrote:
> 
> >I've been having trouble getting distros that have any kernel above the
> >3.5
> >series to boot (only tried 64-bit). I get a black screen with a bunch
> >of
> >text and the boot process goes no further. I don't know if this is
> >usually
> >okay, but I'm posting a link to a picture I took of my monitor with my
> >cell
> >phone. It's a bit blurry but hopefully it's still okay:
> >
> >http://imgur.com/viP1kWk,3YJXKbG
> >
> >The distros I've had this problem in are Kubuntu (I've tried several of
> >the
> >daily builds) which uses the 3.8.? (can't boot far enough to see)
> >kernel,
> >Cinnarch which uses the 3.7.3 kernel, and openSUSE 12.3 and I don't
> >remember what version of the kernel that one used.
> >
> >

> It looks like the ivtv module is failing to initialize, starts to
> unload, and in the process of unloading, the cleanup path causes an
> Ooops.  
> 
> I should have time to look closer at it this weekend.

Test this patch (made against Kernel v3.8-rc5).

Hopefully, it will fix the oops and then let you see why the
ivtv_probe() function fails when initializing the PVR-150.

Regards,
Andy

diff --git a/drivers/media/pci/ivtv/ivtv-driver.c b/drivers/media/pci/ivtv/ivtv-driver.c
index df88dc4..de5db69 100644
--- a/drivers/media/pci/ivtv/ivtv-driver.c
+++ b/drivers/media/pci/ivtv/ivtv-driver.c
@@ -298,7 +298,6 @@ static void request_module_async(struct work_struct *work)
 
 static void request_modules(struct ivtv *dev)
 {
-	INIT_WORK(&dev->request_module_wk, request_module_async);
 	schedule_work(&dev->request_module_wk);
 }
 
@@ -307,6 +306,9 @@ static void flush_request_modules(struct ivtv *dev)
 	flush_work_sync(&dev->request_module_wk);
 }
 #else
+static void request_module_async(struct work_struct *work)
+{
+}
 #define request_modules(dev)
 #define flush_request_modules(dev)
 #endif /* CONFIG_MODULES */
@@ -751,6 +753,8 @@ static int ivtv_init_struct1(struct ivtv *itv)
 	spin_lock_init(&itv->lock);
 	spin_lock_init(&itv->dma_reg_lock);
 
+	INIT_WORK(&itv->request_module_wk, request_module_async);
+
 	init_kthread_worker(&itv->irq_worker);
 	itv->irq_worker_task = kthread_run(kthread_worker_fn, &itv->irq_worker,
 					   itv->v4l2_dev.name);

Re: 3.7/3.8 kernel won't boot with Hauppauge pvr-150

[Hans Verkuil]

On Friday, February 22, 2013 07:17:42 Andy Walls wrote:
> On Thu, 2013-02-21 at 22:32 -0500, Andy Walls wrote:
> > Ron Andreasen <dlanor78@gmail.com> wrote:
> > 
> > >I've been having trouble getting distros that have any kernel above the
> > >3.5
> > >series to boot (only tried 64-bit). I get a black screen with a bunch
> > >of
> > >text and the boot process goes no further. I don't know if this is
> > >usually
> > >okay, but I'm posting a link to a picture I took of my monitor with my
> > >cell
> > >phone. It's a bit blurry but hopefully it's still okay:
> > >
> > >http://imgur.com/viP1kWk,3YJXKbG
> > >
> > >The distros I've had this problem in are Kubuntu (I've tried several of
> > >the
> > >daily builds) which uses the 3.8.? (can't boot far enough to see)
> > >kernel,
> > >Cinnarch which uses the 3.7.3 kernel, and openSUSE 12.3 and I don't
> > >remember what version of the kernel that one used.

Please note that any 3.8 kernel is terminally broken with ivtv/cx18 and will
crash during boot as long as this patch is not applied:

http://git.linuxtv.org/media_tree.git/commit/cfb046cb800ba306b211fbbe4ac633486e11055f

It can be worked around by renaming ivtv-alsa.ko, as Andy mentioned.

I hope to get this patch into the 3.8 stable series as soon as possible.
I have to wait until it is merged into mainline first, though.

Regards,

    Hans

> > >
> > >
> 
> > It looks like the ivtv module is failing to initialize, starts to
> > unload, and in the process of unloading, the cleanup path causes an
> > Ooops.  
> > 
> > I should have time to look closer at it this weekend.
> 
> Test this patch (made against Kernel v3.8-rc5).
> 
> Hopefully, it will fix the oops and then let you see why the
> ivtv_probe() function fails when initializing the PVR-150.
> 
> Regards,
> Andy
> 
> diff --git a/drivers/media/pci/ivtv/ivtv-driver.c b/drivers/media/pci/ivtv/ivtv-driver.c
> index df88dc4..de5db69 100644
> --- a/drivers/media/pci/ivtv/ivtv-driver.c
> +++ b/drivers/media/pci/ivtv/ivtv-driver.c
> @@ -298,7 +298,6 @@ static void request_module_async(struct work_struct *work)
>  
>  static void request_modules(struct ivtv *dev)
>  {
> -	INIT_WORK(&dev->request_module_wk, request_module_async);
>  	schedule_work(&dev->request_module_wk);
>  }
>  
> @@ -307,6 +306,9 @@ static void flush_request_modules(struct ivtv *dev)
>  	flush_work_sync(&dev->request_module_wk);
>  }
>  #else
> +static void request_module_async(struct work_struct *work)
> +{
> +}
>  #define request_modules(dev)
>  #define flush_request_modules(dev)
>  #endif /* CONFIG_MODULES */
> @@ -751,6 +753,8 @@ static int ivtv_init_struct1(struct ivtv *itv)
>  	spin_lock_init(&itv->lock);
>  	spin_lock_init(&itv->dma_reg_lock);
>  
> +	INIT_WORK(&itv->request_module_wk, request_module_async);
> +
>  	init_kthread_worker(&itv->irq_worker);
>  	itv->irq_worker_task = kthread_run(kthread_worker_fn, &itv->irq_worker,
>  					   itv->v4l2_dev.name);
> 
> 
> 
> --
> 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
> 

Re: 3.7/3.8 kernel won't boot with Hauppauge pvr-150

[Mauro Carvalho Chehab]

Em Fri, 22 Feb 2013 07:51:58 -0800
Hans Verkuil <hverkuil@xs4all.nl> escreveu:

> On Friday, February 22, 2013 07:17:42 Andy Walls wrote:
> > On Thu, 2013-02-21 at 22:32 -0500, Andy Walls wrote:
> > > Ron Andreasen <dlanor78@gmail.com> wrote:
> > > 
> > > >I've been having trouble getting distros that have any kernel above the
> > > >3.5
> > > >series to boot (only tried 64-bit). I get a black screen with a bunch
> > > >of
> > > >text and the boot process goes no further. I don't know if this is
> > > >usually
> > > >okay, but I'm posting a link to a picture I took of my monitor with my
> > > >cell
> > > >phone. It's a bit blurry but hopefully it's still okay:
> > > >
> > > >http://imgur.com/viP1kWk,3YJXKbG
> > > >
> > > >The distros I've had this problem in are Kubuntu (I've tried several of
> > > >the
> > > >daily builds) which uses the 3.8.? (can't boot far enough to see)
> > > >kernel,
> > > >Cinnarch which uses the 3.7.3 kernel, and openSUSE 12.3 and I don't
> > > >remember what version of the kernel that one used.
> 
> Please note that any 3.8 kernel is terminally broken with ivtv/cx18 and will
> crash during boot as long as this patch is not applied:
> 
> http://git.linuxtv.org/media_tree.git/commit/cfb046cb800ba306b211fbbe4ac633486e11055f
> 
> It can be worked around by renaming ivtv-alsa.ko, as Andy mentioned.
> 
> I hope to get this patch into the 3.8 stable series as soon as possible.
> I have to wait until it is merged into mainline first, though.

The patch got merged upstream yesterday:

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=cfb046cb800ba306b211fbbe4ac633486e11055f

As it was tagged with:
	 Cc: stable@vger.kernel.org # for 3.8

I expect that it will be available for 3.8.1 after the end of the
merge window.

Regards,
Mauro