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: Mon, 11 Jul 2011 17:04:30 -0400 [thread overview]
Message-ID: <4E1B655E.6010209@gnu.org> (raw)
In-Reply-To: <1310399981.11331.4.camel@sven>
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. Debugging that may be
tricky. I think the first step would be to print stack where that
message is printed in lbs_update_hw_spec(). Also, add statements to
print priv and priv->dev at that point. You should be able to compare
the pointers before and after the suspend.
Once you find what is corrupted, go up the stack and see where the
corruption happens.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2011-07-11 21:04 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 [this message]
2011-07-12 7:22 ` Sven Neumann
2011-07-12 15:20 ` Pavel Roskin
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=4E1B655E.6010209@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 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).