From: Pavel Roskin <proski@gnu.org>
To: Sven Neumann <s.neumann@raumfeld.com>
Cc: libertas-dev@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: kernel NULL pointer dereference in lbs_set_11d_domain_info (3.0-rc6)
Date: Tue, 12 Jul 2011 11:20:37 -0400 [thread overview]
Message-ID: <4E1C6645.8060302@gnu.org> (raw)
In-Reply-To: <1310455326.2218.1.camel@sven>
On 07/12/2011 03:22 AM, Sven Neumann wrote:
> On Mon, 2011-07-11 at 17:04 -0400, Pavel Roskin wrote:
>> On 07/11/2011 11:59 AM, Sven Neumann wrote:
>>> Hi,
>>>
>>> we are using a PXA device and I am observing sporadic crashes after
>>> resume from suspend with 3.0-rc6:
>>>
>>>
>>> [ 1296.027645] PM: resume of devices complete after 296.440 msecs
>>> [ 1296.284633] Restarting tasks ...
>>> [ 1296.320276] done.
>>> [ 1296.421618] mmc0: new SDIO card at address 0001
>>> [ 1297.312570] libertas_sdio mmc0:0001:1: (unregistered net_device): 00:19:88:11:db:67, fw 9.70.7p0, cap 0x00000303
>>
>> I think the trouble starts with "unregistered net_device". It looks
>> like some structures in memory are corrupted.
>
> I don't think that is the problem. The output from booting the kernel
> says "unregistered net_device" as well:
>
> [ 9.236512] libertas_sdio: Libertas SDIO driver
> [ 9.245261] libertas_sdio: Copyright Pierre Ossman
> [ 9.762777] libertas_sdio mmc0:0001:1: (unregistered net_device):
> 00:19:88:11:db:67, fw 9.70.7p0, cap 0x00000303
> [ 9.792377] libertas_sdio mmc0:0001:1: wlan0: Marvell WLAN 802.11
> adapter
Oh well. Then you need to add some tracing to
lbs_set_11d_domain_info(). I do it the old way. I put this macro to
the beginning of the file:
#define MARK printk("%s:%d %s()\n", __FILE__, __LINE__, __func__);
And then I add "MARK" to every second line, as long as it's permitted
syntactically. I may skip adding MARK where failures are unlikely, such
as initialization of local variables. Once you find the line where
printing stops, print all variables used on that line.
I would also print the arguments as pointers in the beginning. Maybe
they are corrupt.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2011-07-12 15:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 15:59 kernel NULL pointer dereference in lbs_set_11d_domain_info (3.0-rc6) Sven Neumann
2011-07-11 21:04 ` Pavel Roskin
2011-07-12 7:22 ` Sven Neumann
2011-07-12 15:20 ` Pavel Roskin [this message]
2011-07-12 16:54 ` Sven Neumann
2011-07-12 19:36 ` Pavel Roskin
2011-07-12 13:52 ` [PATCH] cfg80211: really ignore the regulatory request Sven Neumann
2011-07-15 17:33 ` John W. Linville
2011-07-22 20:40 ` Sven Neumann
2011-07-25 20:27 ` Luis R. Rodriguez
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=4E1C6645.8060302@gnu.org \
--to=proski@gnu.org \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=s.neumann@raumfeld.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.