linux-kernel - Re: [Bug #14267] Disassociating atheros wlan

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20091117113320.8aef894a.kristoffer.ericson@gmail.com>
Date:	Tue, 17 Nov 2009 11:33:20 +0100
From:	Kristoffer Ericson <kristoffer.ericson@...il.com>
To:	"Justin P. Mattock" <justinmattock@...il.com>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	Johannes Berg <johannes@...solutions.net>,
	"John W. Linville" <linville@...driver.com>
Subject: Re: [Bug #14267] Disassociating atheros wlan

On Mon, 16 Nov 2009 16:53:18 -0800
"Justin P. Mattock" <justinmattock@...il.com> wrote:

> Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.30 and 2.6.31.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.30 and 2.6.31.  Please verify if it still should
> > be listed and let me know (either way).
> >
> >
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14267
> > Subject		: Disassociating atheros wlan
> > Submitter	: Kristoffer Ericson<kristoffer.ericson@...il.com>
> > Date		: 2009-09-24 10:16 (54 days old)
> > References	: http://marc.info/?l=linux-kernel&m=125378723723384&w=4
> >
> >
> >
> >    
> I'm not sure(I've been procrastinating on this one
> with reverting commits to see if it helps
> the guy that reported this).
> 
>  From over here though there never was a problem
> on my side with the wireless connection(maybe a few disconnects,
> but nothing too harsh).
> 
> At this point the best thing to do is to see what the
> response is from the two gentlemen who where really
> hitting this and seem to be running into issues
> then go from there.

Im still hitting this so basicly using 2.6.30 until it get sorted. Will try and make
some time to test the different commits. Last time I waited for it to disconnect which
could take 10-40min. Since it depends on the network load Im now going to increase
the load to see if I hit it quicker (and thus finding the error commit).

So in short, its still valid and I will try and make time to fix it :)


> 
> Justin P. Mattock
> 
> 


-- 
Kristoffer Ericson <kristoffer.ericson@...il.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/