Bug 781832

Summary: imon module: Input from ffdc device type ignored
Product: [Fedora] Fedora Reporter: Corinna Vinschen <vinschen>
Component: kernelAssignee: Jarod Wilson <jarod>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: rawhideCC: gansalmon, itamar, jarod, jonathan, kernel-maint, madhu.chinakonda, mchehab
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: kernel-3.3.0-0.rc4.git1.4.fc17 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-28 10:56:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Patch to fix ignoring input from ffdc iMon device none

Description Corinna Vinschen 2012-01-15 15:48:25 UTC
Created attachment 555361 [details]
Patch to fix ignoring input from ffdc iMon device

Description of problem:

  I have an iMON device (device ID 15c2:ffdc) in my multimedia pc, which
  worked without too many problems with pre-3.x kernels and the lirc_imon
  module.  With the new imon module since kernel 3.0 the remote worked as
  expected, just everytime the module got reloaded or the machine was rebooted,
  the machine got a kernel oops.

  With kernel version 3.2, the oops is fixed, but now the input from the
  remote is not recognized at all.  There are no input entries in the log.

  I have a patch to drivers/media/rc/imon.c for this issue which works for
  me(TM), but I'm not sure it's the right thing to do.  With this patch
  keypresses from the remote are recognized and the kernel oops doesn't occur
  either.  The patch is attached.

Version-Release number of selected component (if applicable):

  kernel-3.2.1-4.fc17.src.rpm


Corinna

Comment 1 Corinna Vinschen 2012-01-24 10:28:57 UTC
Ping?  Is anything essential missing in this bug report/patch submission?


TIA,
Corinna

Comment 2 Josh Boyer 2012-01-24 12:35:38 UTC
(In reply to comment #1)
> Ping?  Is anything essential missing in this bug report/patch submission?

Sorry, this report got lost in the sea of bugs.  The one simple thing I can comment on is that the patch would need to be at strip level one to be readily applicable.

Jarod, Mauro, can you review the patch and see if it's suitable for upstream submission?

Comment 3 Mauro Carvalho Chehab 2012-01-24 13:06:22 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > Ping?  Is anything essential missing in this bug report/patch submission?
> 
> Sorry, this report got lost in the sea of bugs.  The one simple thing I can
> comment on is that the patch would need to be at strip level one to be readily
> applicable.
> 
> Jarod, Mauro, can you review the patch and see if it's suitable for upstream
> submission?

The patch looks ok on my eyes. We need patch author's Signed-off-by, in order to
merge it upstream. A Jarod's ack would also be a nice-to-have.

The better procedure would be if Corinna could send the patch with the SOB on it, to the linux-media.org. I'll get it there and apply upstream.

Comment 4 Corinna Vinschen 2012-01-24 20:10:57 UTC
Hi,

I'll send the original report with a fixed patch and a SOB to
the linux-media list in a couple of minutes.


Thanks guys,
Corinna

Comment 5 Jarod Wilson 2012-01-24 22:54:21 UTC
Will hopefully take a closer look tomorrow. I think it might actually be that we need some additional locking to ensure that intf0 init has actually finished before we start processing packets.

Comment 6 Jarod Wilson 2012-01-25 21:04:44 UTC
I just sent an updated patch based on Corinna's but with a bit more detail on what's going on and the same treatment for the second imon device interface to linux-media, and I've verified it with both an ffdc device and a newer device. Wasn't the locking like I was thinking, it was the callback firing, and us bailing without submitting a new rx urb.

Comment 7 Josh Boyer 2012-02-21 00:00:27 UTC
http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/43872/focus=43980

which still isn't in linux-next or any other tree I can find.

Comment 8 Jarod Wilson 2012-02-21 17:30:49 UTC
Mauro has it queued up here at least:

http://git.linuxtv.org/mchehab/media-next.git

I've asked that it get sent along for v3.3. with 3.2-stable cc'd.

Comment 9 Josh Boyer 2012-02-21 18:30:20 UTC
(In reply to comment #8)
> Mauro has it queued up here at least:
> 
> http://git.linuxtv.org/mchehab/media-next.git
> 
> I've asked that it get sent along for v3.3. with 3.2-stable cc'd.

I see.  I was looking at the two trees below.  Those seem stale:

http://git.kernel.org/?p=linux/kernel/git/mchehab/linux-media.git;a=summary
http://git.kernel.org/?p=linux/kernel/git/mchehab/media-next.git;a=summary

Comment 10 Josh Boyer 2012-02-21 19:33:01 UTC
OK, threw the patch in f17 and rawhide since it's queued in a tree somewhere now.

Comment 11 Fedora Update System 2012-02-22 19:58:33 UTC
kernel-3.3.0-0.rc4.git1.4.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/kernel-3.3.0-0.rc4.git1.4.fc17

Comment 12 Fedora Update System 2012-02-23 22:31:29 UTC
Package kernel-3.3.0-0.rc4.git1.4.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-3.3.0-0.rc4.git1.4.fc17'
as soon as you are able to, then reboot.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-2304/kernel-3.3.0-0.rc4.git1.4.fc17
then log in and leave karma (feedback).

Comment 13 Fedora Update System 2012-02-28 10:56:17 UTC
kernel-3.3.0-0.rc4.git1.4.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 14 Jarod Wilson 2012-02-28 14:32:17 UTC
Got this note this morning:

This is a note to let you know that I've just added the patch titled

    [media] imon: don't wedge hardware after early callbacks

to the 3.2-stable tree which can be found at:
    http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     imon-don-t-wedge-hardware-after-early-callbacks.patch
and it can be found in the queue-3.2 subdirectory.

So this should also get taken care of automagically for Fedora 16 by way of a 3.2-stable update at some point in the future.