From: Larry Finger <Larry.Finger@lwfinger.net>
To: hubert Liao <liao.hubertt@gmail.com>
Cc: Chaoming Li <chaoming_li@realsil.com.cn>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Oops when insmod rtl8192ce
Date: Wed, 27 Jul 2011 09:37:13 -0500 [thread overview]
Message-ID: <4E302299.2070309@lwfinger.net> (raw)
In-Reply-To: <CAMzZzFGpDiFAhsLAb+SQxjbGMzBoOStF_Lr7Eb3PT6Drcf=VdA@mail.gmail.com>
On 07/27/2011 04:26 AM, hubert Liao wrote:
> Hi,
> We got an oops when insmod rtl8192ce module (the board is an ARM soc),
> accroding the oops message, find it's because in rtl_pci_probe()
> called _rtl_pci_find_adapter(),
> in this funcation, the pdev->bus->self is a NULL pointer .
> static boot _rtl_pci_find_adapter(strcut pci_dev *dev,
> struct ieee80211_hw *hw)
> {
> struct pci_dev *bridge_pdev = pdev->bus->self; //line 1601
> ...
> pcipriv->ndis_adapter.pcibridge_vendorid = bridge_pdev->vendor;<--
> [oops here] line 1700
> ...
> }
> here, I just want to know why the bus->self is NULL?
> ----
> [ 148.186632] Unable to handle kernel NULL pointer dereference at
> virtual address 00000020
As John Linville suggested, please open a bugzilla report.
I would also like some additional information. What kernel are you using? In
addition, please post the 'lspci -nnk' information for your card.
I also think that pdev->bus should have been setup before the initialization
code in rtl8192ce was called. I have not tested the driver on other than x86 and
x86_64 architectures because of hardware availability, thus ARM may expose some
problems. Is this soc little-endian?
Thanks,
Larry
next prev parent reply other threads:[~2011-07-27 14:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMzZzFGqPv6Nbw8J8JGNKcLA76sAs3oD6+hH9NPCjwA33fYpOQ@mail.gmail.com>
2011-07-27 9:26 ` Oops when insmod rtl8192ce hubert Liao
2011-07-27 14:37 ` Larry Finger [this message]
2011-07-28 1:21 ` hubert Liao
2011-07-27 13:53 ` John W. Linville
2011-07-28 7:06 ` hubert Liao
2011-07-28 14:56 ` Larry Finger
2011-07-29 1:21 ` Hubert Liao
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=4E302299.2070309@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=chaoming_li@realsil.com.cn \
--cc=liao.hubertt@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).