Kristoffer Ericson wrote:
On Tue, 17 Nov 2009 10:07:09 -0800
"Justin P. Mattock"<justinmattock@xxxxxxxxx> wrote:
Kristoffer Ericson wrote:
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 :)
o.k. so it is something that is enough to
cause an inconvenience.
Especially if you are using your computer as a router to other computers
and they start screaming every time internet goes down. :(
ah. yeah I'm not doing that over here
just simply connecting to a router and streaming music.
my guess is you can try the commits that I found
but then again might not get you in the right
direction i.g. during the bisect I was watching the
"retry" in dmesg with ath* as soon as I saw that it was git bisect bad
(seems like a new mechanism) as soon as I didn't see
that the commit was good.
In your case you might be seeing something different(not sure though)
because of having the computer as a router etc..
Justin P. Mattock
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
