All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@iki.fi>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org, Jouni Malinen <j@w1.fi>
Subject: Re: Problem with IEEE80211_MONITORING_INTERVAL
Date: Wed, 22 Apr 2009 08:04:18 +0300	[thread overview]
Message-ID: <874owhffe5.fsf@litku.valot.fi> (raw)
In-Reply-To: <1240343775.3327.3.camel@localhost.localdomain> (Marcel Holtmann's message of "Tue\, 21 Apr 2009 20\:56\:15 +0100")

Marcel Holtmann <marcel@holtmann.org> writes:

> so I have built the latest wireless-testing tree with a new patches sent
> by Reinette fixing the DMA issue. So far I have no problems and I am
> unable to re-produce it. However this is a different AP and I disabled
> the power control feature for now.
>
> I also updated wpa_supplicant and iw to the latest code and assume that
> no fix in there silently fixed it for me.
>
> So we are suspecting that this issue was because of me having 3GB of RAM
> and running on a 64-bit kernel. Does this makes sense and could be the
> problem why it kept failing until I unload the iwlagn driver?

I would say that don't make any assumptions until you manage to test
with the original AP. APs can be broken so many ways.

-- 
Kalle Valo

  parent reply	other threads:[~2009-04-22  5:04 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-15 23:21 Problem with IEEE80211_MONITORING_INTERVAL Marcel Holtmann
2009-04-16  0:21 ` Johannes Berg
2009-04-16  0:44   ` Johannes Berg
2009-04-16  1:12     ` Marcel Holtmann
2009-04-16  1:08   ` Marcel Holtmann
2009-04-16  1:16     ` Johannes Berg
2009-04-16  6:14   ` Kalle Valo
2009-04-16  9:12     ` Johannes Berg
2009-04-16  9:43       ` Johannes Berg
2009-04-16  9:49         ` Kalle Valo
2009-04-16  9:58           ` Johannes Berg
2009-04-16  9:59       ` Kalle Valo
2009-04-16 10:04         ` Johannes Berg
2009-04-16 10:08           ` Kalle Valo
2009-04-16 10:18             ` Johannes Berg
2009-04-16 10:23               ` Kalle Valo
2009-04-16  9:46 ` Johannes Berg
2009-04-20 17:13   ` Marcel Holtmann
2009-04-20 17:20     ` Johannes Berg
2009-04-20 17:26       ` Marcel Holtmann
2009-04-20 17:32         ` Johannes Berg
2009-04-21 19:56           ` Marcel Holtmann
2009-04-21 21:19             ` Johannes Berg
2009-04-22  7:32               ` Marcel Holtmann
2009-04-22  9:03                 ` Johannes Berg
2009-04-22  9:12                   ` Marcel Holtmann
2009-04-22  9:45                     ` Johannes Berg
2009-04-22 11:17                       ` Marcel Holtmann
2009-04-22 11:53                         ` Marcel Holtmann
2009-04-22 12:14                           ` Johannes Berg
2009-04-22 12:56                             ` Marcel Holtmann
2009-04-22 13:27                           ` John W. Linville
2009-04-22 17:35                       ` reinette chatre
2009-04-22  5:04             ` Kalle Valo [this message]
2009-04-22  7:27               ` Marcel Holtmann
2009-04-20 18:29     ` Jouni Malinen
2009-04-21 10:47       ` Marcel Holtmann

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=874owhffe5.fsf@litku.valot.fi \
    --to=kalle.valo@iki.fi \
    --cc=j@w1.fi \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marcel@holtmann.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.