linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ASIC Felix <ic.felix@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Johannes Berg <johannes@sipsolutions.net>,
	"Luis R. Rodriguez" <mcgrof@gmail.com>
Subject: Re: regression?  No connection with master-2009-09-16 was fine until master-2009-09-14
Date: Thu, 17 Sep 2009 16:06:31 -0700	[thread overview]
Message-ID: <1253228791.6914.2.camel@darkslate> (raw)
In-Reply-To: <20090917195141.GB2562@tuxdriver.com>

On Thu, 2009-09-17 at 15:51 -0400, John W. Linville wrote:
> On Thu, Sep 17, 2009 at 10:25:48AM -0700, ASIC Felix wrote:
> > Hi,
> > 
> > with master-2009-09-16 my laptop can no longer connect to the network.
> > I can see all the APs, but can't connect.
> > The issue is new, w-t kernel master-2009-09-14 was fine.
> > 
> > Sorry for pasting the whole /var/log/messages from boot to boot,
> > but I see anything obvious by myself.
> 
> Perhaps you could bisect between master-2009-09-14 and
> master-2009-09-16?  There are only a handful of patches.

]$ git bisect good
389ce02fdca74c15984edced7a2f1879fe08a8b1 is first bad commit
commit 389ce02fdca74c15984edced7a2f1879fe08a8b1
Author: Johannes Berg <johannes@sipsolutions.net>
Date:   Wed Sep 16 09:04:26 2009 -0700

    cfg80211: fix SME connect
    
    There's a check saying
    	/* we're good if we have both BSSID and channel */
    	if (wdev->conn->params.bssid && wdev->conn->params.channel) {


This commit prevents connection for me.

Best regards,
Felix


  reply	other threads:[~2009-09-17 23:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17 17:25 regression? No connection with master-2009-09-16 was fine until master-2009-09-14 ASIC Felix
2009-09-17 19:51 ` John W. Linville
2009-09-17 23:06   ` ASIC Felix [this message]
2009-09-17 23:35 ` Johannes Berg
2009-09-18  0:05   ` ASIC Felix
2009-09-18  0:09     ` Johannes Berg
2009-09-18  0:13       ` Johannes Berg
2009-09-18 20:51         ` ASIC Felix
2009-09-18  7:23       ` Holger Schurig

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=1253228791.6914.2.camel@darkslate \
    --to=ic.felix@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@gmail.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).