On Mon, Jun 30, 2014 at 05:08:01AM +0800, lolilolicon wrote:
On Mon, Jun 30, 2014 at 1:08 AM, Larry Finger larry.fin...@lwfinger.net
wrote:
On 06/29/2014 04:32 AM, lolilolicon wrote:
% git bisect start 88daf80 010d3c3 35582ad
88daf80dcca19ff995cc263592426f734a9702f3 is the first bad
Am 30.06.2014 16:20, schrieb John W. Linville:
On Mon, Jun 30, 2014 at 05:08:01AM +0800, lolilolicon wrote:
On Mon, Jun 30, 2014 at 1:08 AM, Larry Finger larry.fin...@lwfinger.net
wrote:
On 06/29/2014 04:32 AM, lolilolicon wrote:
% git bisect start 88daf80 010d3c3 35582ad
On Sun, Jun 29, 2014 at 8:37 AM, Larry Finger larry.fin...@lwfinger.net wrote:
Something went wrong in your bisection. Commit 88daf80 is a merge commit and
is unlikely to be the bad one. You might try a checkout of b080e04 and try
it to see if it is bad or good. That is the first non-merge
On 06/29/2014 04:32 AM, lolilolicon wrote:
On Sun, Jun 29, 2014 at 8:37 AM, Larry Finger larry.fin...@lwfinger.net
wrote:
Something went wrong in your bisection. Commit 88daf80 is a merge commit and
is unlikely to be the bad one. You might try a checkout of b080e04 and try
it to see if it
On Mon, Jun 30, 2014 at 1:08 AM, Larry Finger larry.fin...@lwfinger.net wrote:
On 06/29/2014 04:32 AM, lolilolicon wrote:
% git bisect start 88daf80 010d3c3 35582ad
88daf80dcca19ff995cc263592426f734a9702f3 is the first bad commit
What am I getting wrong?
I am not an expert in git, but I
This bug was introduced in merge commit 88daf80 (if I did the bisect correctly).
A workaround around the bug is to set the ath9k_htc param nohwcrypt=1.
The difference in the journal/log between good and bad is that in the
presence of the bug, dhcpcd would time out soliciting a DHCP lease.
Some
On 06/28/2014 04:17 PM, lolilolicon wrote:
This bug was introduced in merge commit 88daf80 (if I did the bisect
correctly).
A workaround around the bug is to set the ath9k_htc param nohwcrypt=1.
The difference in the journal/log between good and bad is that in the
presence of the bug,
