From: Chris W <lkml@psychogeeks.com>
To: Jarod Wilson <jarod@wilsonet.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
linux-kernel@vger.kernel.org, Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: Imon module Oops and kernel hang
Date: Wed, 13 Jul 2011 15:42:29 +1000 [thread overview]
Message-ID: <4E1D3045.7050507@psychogeeks.com> (raw)
In-Reply-To: <1B380AD0-FE0D-47DF-B2C3-605253C9C783@wilsonet.com>
On 13/07/11 14:20, Jarod Wilson wrote:
>> Chris W wrote:
>> The rc keymap modules have been built (en masse as a result of
>> CONFIG_RC_MAP=m) but I am not explicitly loading them and they do not
>> get automatically loaded.
>
> Huh. That's unexpected. They get auto-loaded here, last I knew. I'll
> have to give one of my devices a spin tomorrow, not sure exactly what
> the last kernel I tried one of them on was. Pretty sure they're
> working fine with the Fedora 15 2.6.38.x kernels and vanilla (but
> Fedora-configured) 3.0-rc kernels though.
I just ran depmod to make sure things were straight in this dept.
kepler ~ # depmod -F System.map -e -av 2.6.39.3
There are no reported errors. The modules rc-imon-mce.ko,
rc-imon-pad.ko and imon.ko depend only on rc-core.ko according to the
output. There don't seem to be any explicit dependencies to the keymaps
(not a kernel dev so I don't know if there should be)
>> I just tried this:
>>
>> kepler ~ # rmmod rc_winfast ir_lirc_codec lirc_dev ir_sony_decoder
>> ir_jvc_decoder ir_rc6_decoder ir_rc5_decoder ir_nec_decoder
>>
>> kepler ~ # modprobe -v rc-imon-pad
>> insmod
/lib/modules/2.6.39.3/kernel/drivers/media/rc/keymaps/rc-imon-pad.ko
>>
>> kepler ~ # modprobe -v rc-imon-mce
>> insmod
/lib/modules/2.6.39.3/kernel/drivers/media/rc/keymaps/rc-imon-mce.ko
> ...
>> kepler ~ # modprobe -v imon debug=1
>> insmod /lib/modules/2.6.39.3/kernel/drivers/media/rc/imon.ko debug=1
>>
>> with the same crash (below). (I have the tainting nvidia driver
>> loaded today but it was absent yesterday)
>>
>> Perhaps there something else in the kernel config that must be on in
>> order to support the keymaps?
>>
>> Any other thoughts?
>
> Not at the moment. That T.889 line is... odd. No clue what the heck
> that thing is. Lemme see what I can see tomorrow (just past midnight
> here at the moment), if I don't hit anything, I might need a copy of
> your kernel config to repro.
I can only see the "T.889" string in the System.map, kernel binary and
kernel/sched.o (but not the source?). I have sent the config file
off-list to Jarod.
I will try a Gentoo out-of-the-box kernel config when I finish work also.
Thanks once again for your time
Regards,
--
Chris Williams
Brisbane, Australia
next prev parent reply other threads:[~2011-07-13 5:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E1B978C.2030407@psychogeeks.com>
2011-07-12 15:03 ` Imon module Oops and kernel hang Randy Dunlap
2011-07-12 19:55 ` Jarod Wilson
2011-07-12 22:35 ` Chris W
2011-07-13 4:20 ` Jarod Wilson
2011-07-13 5:42 ` Chris W [this message]
2011-07-13 22:11 ` Jarod Wilson
2011-07-14 2:41 ` Chris W
2011-07-17 0:43 ` Andy Walls
2011-07-17 1:38 ` Chris W
2011-07-17 13:36 ` Andy Walls
2011-07-18 15:04 ` Jarod Wilson
2011-07-18 16:46 ` [PATCH] [media] imon: don't submit urb before rc_dev set up Jarod Wilson
2011-07-18 22:29 ` Chris W
2011-07-19 12:23 ` Jarod Wilson
2011-07-19 16:12 ` [PATCH] [media] imon: don't parse scancodes until intf configured Jarod Wilson
2011-07-19 22:05 ` Chris W
2011-07-20 13:18 ` Jarod Wilson
2011-07-20 22:56 ` Chris W
2011-07-26 17:57 ` Jarod Wilson
2011-07-22 14:06 ` [PATCH] [media] imon: don't submit urb before rc_dev set up Jarod Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E1D3045.7050507@psychogeeks.com \
--to=lkml@psychogeeks.com \
--cc=jarod@wilsonet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox