From: Daniel Walker <dwalker@fifo99.com>
To: Luca Olivetti <luca@ventoso.org>
Cc: Ingo Molnar <mingo@elte.hu>, Greg KH <gregkh@suse.de>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org, Hans Verkuil <hverkuil@xs4all.nl>,
Janne Grunau <janne-dvb@grunau.be>
Subject: Re: [crash] af9005_usb_module_init(): BUG: unable to handle kernel paging request at ff100000
Date: Wed, 04 Feb 2009 07:16:47 -0800 [thread overview]
Message-ID: <1233760607.15119.85.camel@desktop> (raw)
In-Reply-To: <4989ABA8.8010807@ventoso.org>
On Wed, 2009-02-04 at 15:52 +0100, Luca Olivetti wrote:
> En/na Daniel Walker ha escrit:
> > On Tue, 2009-02-03 at 21:41 +0100, Luca Olivetti wrote:
> >
> >> No, I don't have 2.6.28, but I guess that maybe once usb_register is
> >> called the dvb-usb subsystem asynchronously (is that an smp system?)
> >> starts polling the remote before the rc_decode function pointer has been
> >> initialized.
> >> Could you try to initialize it to NULL before calling usb_register?
> >
> > What happens to the decode function when you have,
> >
> > CONFIG_DVB_USB_AF9005=y
> > CONFIG_DVB_USB_AF9005_REMOTE=n
> >
> > It seems that the decode function is defined inside,
> > drivers/media/dvb/dvb-usb/af9005-remote.c
> >
> > but that doesn't get compiled in the case above. It looks like you end
> > up with af9005_rc_decode being a function local weak symbol
> > (uninitialized) which then gets assigned to rc_decode .. I think the
> > crash actually happens on rc_keys_size which get assigned another
> > uninitialized local, and it gets de-referenced .
>
> Doesn't symbol_request return a NULL in such a case?
> At the time I didn't try the above configuration
> (CONFIG_DVB_USB_AF9005_REMOTE=n), but removed the compiled
> dvb-usb-af9005-remote.ko, and all was well (i.e. the symbol_request
> returned NULL and the remote handling was disabled).
I'm not sure what symbol request returns when CONFIG_MODULES=n .. Since
it basically drops symbol_request() into a macro , and you have externs
for all these functions .. Now that I look at it again, I'm not sure how
it compiles..
> > Here's a patch I compile tested, and I think it would fix the issue.
>
> But it'd break the alternative rc decoding module (not integrated in the
> kernel because it uses lirc):
>
> http://ventoso.org/luca/af9005/README.lirc
I guess that would have to be fix with another patch then ..
Daniel
next prev parent reply other threads:[~2009-02-04 15:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 17:28 [crash] af9005_usb_module_init(): BUG: unable to handle kernel paging request at ff100000 Ingo Molnar
2009-02-03 17:45 ` Arjan van de Ven
2009-02-03 18:22 ` Daniel Walker
2009-02-03 19:30 ` Ingo Molnar
2009-02-03 20:41 ` Luca Olivetti
2009-02-03 21:18 ` Luca Olivetti
2009-02-03 21:32 ` Ingo Molnar
2009-02-04 1:14 ` Daniel Walker
2009-02-04 14:52 ` Luca Olivetti
2009-02-04 15:16 ` Daniel Walker [this message]
2009-02-04 15:49 ` Luca Olivetti
2009-02-04 16:12 ` Daniel Walker
2009-02-04 18:12 ` Luca Olivetti
2009-02-04 18:30 ` Daniel Walker
2009-02-04 18:41 ` Luca Olivetti
2009-02-04 19:27 ` Daniel Walker
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=1233760607.15119.85.camel@desktop \
--to=dwalker@fifo99.com \
--cc=gregkh@suse.de \
--cc=hverkuil@xs4all.nl \
--cc=janne-dvb@grunau.be \
--cc=linux-kernel@vger.kernel.org \
--cc=luca@ventoso.org \
--cc=mchehab@infradead.org \
--cc=mingo@elte.hu \
/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