From: Johannes Berg <johannes@sipsolutions.net>
To: reinette chatre <reinette.chatre@intel.com>
Cc: Norbert Preining <preining@logic.at>,
"ipw3945-devel@lists.sourceforge.net"
<ipw3945-devel@lists.sourceforge.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [ipw3945-devel] hang on 2.6.33-rc4
Date: Tue, 19 Jan 2010 18:59:50 +0100 [thread overview]
Message-ID: <1263923990.28066.3.camel@johannes.local> (raw)
In-Reply-To: <1263920481.4838.32.camel@rchatre-DESK>
[-- Attachment #1: Type: text/plain, Size: 497 bytes --]
On Tue, 2010-01-19 at 09:01 -0800, reinette chatre wrote:
> > If you want me to create a bug report or you create one in bugzilla,
> > I can also upload it htere, but I attach it for now.
>
> I see that it fails in skb_pull after being called from one of the RX
> handlers. Let's add Johannes.
>
> Johannes, does anything perhaps look familiar to you in this trace?
Sorry, no, seems weird. The trace is not very useful unfortunately, is
this with CONFIG_FRAME_POINTER?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2010-01-19 20:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 15:22 Norbert Preining
2010-01-15 17:29 ` [ipw3945-devel] " reinette chatre
2010-01-16 2:30 ` Norbert Preining
2010-01-16 18:30 ` Norbert Preining
2010-01-18 17:06 ` reinette chatre
2010-01-18 17:19 ` Norbert Preining
2010-01-19 5:47 ` Norbert Preining
2010-01-19 17:01 ` reinette chatre
2010-01-19 17:59 ` Johannes Berg [this message]
2010-01-20 0:36 ` Norbert Preining
2010-01-20 9:52 ` Johannes Berg
2010-01-20 9:32 ` Zhu Yi
2010-01-21 0:28 ` Norbert Preining
2010-01-21 18:18 ` John Ranson
2010-01-27 15:37 ` Norbert Preining
2010-01-27 16:54 ` reinette chatre
2010-01-28 8:41 ` Norbert Preining
2010-01-28 16:23 ` reinette chatre
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=1263923990.28066.3.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=preining@logic.at \
--cc=reinette.chatre@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
all inboxes | Powered by JetHome®