linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Alex Romosan <romosan@sycorax.lbl.gov>
Cc: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlwifi connection problems
Date: Wed, 04 Aug 2010 17:03:05 +0200	[thread overview]
Message-ID: <1280934185.3768.8.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <87aap28m8v.fsf@sycorax.lbl.gov>

On Wed, 2010-08-04 at 07:51 -0700, Alex Romosan wrote:
> Johannes Berg <johannes@sipsolutions.net> writes:
> 
> > Could you rebuild your kernel with CONFIG_MAC80211_DRIVER_API_TRACER
> > and CONFIG_IWLWIFI_DEVICE_TRACING, get trace-cmd from
> > git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git
> > and record traces for me? I'd like to have
> > 	trace-cmd record -e iwlwifi -e mac80211
> > for both the working and non-working case, preferably the same kernel
> > with that single line of code changed. Please compress the output.
> 
> you can get both traces from
> 
>   http://caliban.lbl.gov/iwlwifi/
> 
> for the not-working case i also tried to bring down the interface and
> then bring it up again while recording the trace (don't know if it
> matters).

Thanks. The down/up is fine, I'll be able to identify that in the
traces. Except the "working" trace looks like it only starts after you
connected already?

johannes


  reply	other threads:[~2010-08-04 15:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-23 20:14 iwlwifi connection problems Alex Romosan
2010-07-23 20:38 ` Guy, Wey-Yi
2010-07-26  9:17   ` Johannes Berg
2010-07-27  4:59     ` Alex Romosan
2010-07-27  6:37       ` Johannes Berg
2010-08-02  0:18         ` Alex Romosan
2010-08-02 10:58           ` Johannes Berg
2010-08-02 15:42             ` Alex Romosan
2010-08-02 16:23               ` Johannes Berg
2010-08-03  3:53                 ` Alex Romosan
2010-08-03  6:39                   ` Johannes Berg
2010-08-03 12:32                     ` Alex Romosan
2010-08-03 12:43                     ` Alex Romosan
2010-08-04  7:52                       ` Johannes Berg
2010-08-04 14:51                         ` Alex Romosan
2010-08-04 15:03                           ` Johannes Berg [this message]
2010-08-04 15:08                             ` Alex Romosan
2010-08-04 15:11                               ` Johannes Berg
2010-08-04 15:12                                 ` Alex Romosan
2010-08-04 15:23                                   ` Johannes Berg
2010-08-16 13:16                                   ` Johannes Berg
2010-08-16 13:44                                     ` Alex Romosan
2010-08-16 16:40                                     ` Alex Romosan
2010-08-16 19:06                                       ` Johannes Berg
2010-08-17  9:24                                       ` [PATCH] iwlwifi: fix 3945 filter flags Johannes Berg
2010-08-19 16:01                                         ` Alex Romosan

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=1280934185.3768.8.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=romosan@sycorax.lbl.gov \
    --cc=wey-yi.w.guy@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).