Ubuntu
linux package

  1. Bug #1436891
  2. Comment #16

Comment 16 for bug 1436891

Revision history for this message
Darren Peets (dpeets) wrote : Re: Cannot connect to any WiFi access point which runs wireless-N

OK, bisect result and a caveat:

d88c8958dc13b4e4eb7fc57e3f06dc1c4abc7b1f is the first bad commit
commit d88c8958dc13b4e4eb7fc57e3f06dc1c4abc7b1f
Author: Emmanuel Grumbach <email address hidden>
Date: Mon Sep 1 09:50:14 2014 +0300

    iwlwifi: bump firmware API version to 10 for 7000 and 8000

    New firmware on the way.

    Signed-off-by: Emmanuel Grumbach <email address hidden>

:040000 040000 6fda9a82d01a59a4edeaee8d1fbeb2cce28eeecc 7b61151b4783bc2f3ae31a132fa36c80a84cb978 M drivers

Now, what I tried to do during the bisect was the following:
$ cp /boot/config-3.19.0-14-generic .config
$ make oldconfig
$ make clean
$ make -j `getconf _NPROCESSORS_ONLN` deb-pkg LOCALVERSION=-dpeets??
for ?? an increasing integer, and accepting all default settings for make oldconfig

HOWEVER, for a vast expanse in the middle of this bisect range, building the kernel image failed if started from the 3.19 config file (here's one example):
...
  INSTALL debian/tmp/lib/firmware/cpia2/stv0672_vp4.bin
  INSTALL debian/tmp/lib/firmware/yam/1200.bin
  INSTALL debian/tmp/lib/firmware/yam/9600.bin
  DEPMOD 3.16.0-dpeets22
depmod: ERROR: Found 5 modules in dependency cycles!
depmod: ERROR: Cycle detected: st21nfcb -> ndlc -> nci -> st21nfcb
depmod: ERROR: Cycle detected: nci -> nci
Makefile:1113: recipe for target '_modinst_post' failed
make[2]: *** [_modinst_post] Error 1
scripts/package/Makefile:90: recipe for target 'deb-pkg' failed
make[1]: *** [deb-pkg] Error 2
Makefile:1205: recipe for target 'deb-pkg' failed
make: *** [deb-pkg] Error 2

I'm not in a position to do anything other than accept the defaults, and I'm not about to edit the config file on my own. So for perhaps half of the bisect steps, the starting point for .config was the previous bisect step's .config (without first checking whether a copied 3.19 version worked), or in a couple cases a config file from a known good 3.16 kernel after the 3.19 config file failed. This means that the starting point was not necessarily the same for all steps.

If there are parts of this I should redo or check, config files you'd like (I didn't save them in general, but I have a few), or anything I can test, let me know.