From: Johannes Berg <johannes@sipsolutions.net>
To: Pavel Machek <pavel@ucw.cz>
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: Thu, 01 Oct 2009 23:16:23 +0200 [thread overview]
Message-ID: <1254431783.3959.45.camel@johannes.local> (raw)
In-Reply-To: <20090929171249.GB14405@elf.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]
On Tue, 2009-09-29 at 19:12 +0200, Pavel Machek wrote:
>
> Happened while playing with wireless.
>
> Kernel is:
>
> Linux version 2.6.31 (pavel@amd) (gcc version 4.3.3 (Debian 4.3.3-10)
> ) #72 SMP Thu Sep 10 21:56:19 CEST 2009
> KERNEL supported cpus:
>
> (Could we get kernels between release and -rc1 mark themselves
> somehow?)
CONFIG_LOCALVERSION_AUTO?
> Registered led device: iwl-phy0::radio
> Registered led device: iwl-phy0::assoc
> Registered led device: iwl-phy0::RX
> Registered led device: iwl-phy0::TX
> 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.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-10-01 21:16 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 [this message]
2009-10-01 21:27 ` Johannes Berg
2009-10-17 18:33 ` Pavel Machek
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=1254431783.3959.45.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pavel@ucw.cz \
--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;
as well as URLs for NNTP newsgroup(s).