From: Pavel Machek <pavel@ucw.cz>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-kernel@vger.kernel.org, yi.zhu@intel.com,
reinette.chatre@intel.com, linux-wireless@vger.kernel.org
Subject: Re: 2.6.32-rc0-git: oops in wireless, iwl3945 related?
Date: Sat, 17 Oct 2009 20:33:20 +0200 [thread overview]
Message-ID: <20091017183320.GF16532@elf.ucw.cz> (raw)
In-Reply-To: <1254432469.3959.46.camel@johannes.local>
On Thu 2009-10-01 23:27:49, Johannes Berg wrote:
> On Thu, 2009-10-01 at 23:16 +0200, Johannes Berg wrote:
>
> > > wlan0: Selected IBSS BSSID 02:18:41:de:3f:02 based on configured SSID
> > > wlan0: Trigger new scan to find an IBSS to join
> > > wlan0: Trigger new scan to find an IBSS to join
> > > wlan0: Creating new IBSS network, BSSID f2:d3:80:82:ed:6a
> > > wlan0: Creating new IBSS network, BSSID 52:17:bf:45:d6:9d
> > > skb_over_panic: text:c07b4113 len:130 put:36 head:e4c3edf0
> >
> > This entire log is very odd ... can you reproduce this easily? printk
> > timestamps would be useful.
>
> Kinda looks like a race condition, but it's rather odd. I think there's
> a race condition, so I'm going to submit this patch regardless after
> some testing, but if you want please try the patch below.
Well, the problem is not exactly reproducible... it failed to happen
again. So... thanks and I'll keep my eyes open if it returns.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-10-17 18:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 17:12 2.6.32-rc0-git: oops in wireless, iwl3945 related? Pavel Machek
2009-09-29 18:14 ` reinette chatre
2009-10-01 21:16 ` Johannes Berg
2009-10-01 21:27 ` Johannes Berg
2009-10-17 18:33 ` Pavel Machek [this message]
2009-10-17 22:00 ` Johannes Berg
2009-10-01 22:24 ` Pavel Machek
2009-10-01 22:28 ` Johannes Berg
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=20091017183320.GF16532@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=yi.zhu@intel.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