Re: AMD microcode fails to update with v3.8.3 and newer, bisect failed

[Ken Moffat <zarniwhoop@ntlworld.com>]

On Thu, Jan 02, 2014 at 04:08:15AM +0000, Ken Moffat wrote:
> 
>  Anyway, best of luck and I hope you get it sorted.
> 
 One further suggestion, since you appear to be at the "running
round in circles" stage -

1. Start with a good kernel.  In this case, I suppose 3.8.2 is the
right place to begin.

2. But then change the .config to -

2.1 ensure that your disk filesystems are built in - e.g. all of
ext2, ext3, ext4 and anything else you know you are using.
Normally, only the fs for '/' needs to be built in, but you seem to
have seen other issues so I would just build in everything you need.

2.2 build in everything else you need to boot (normally, the disk
controller(s) ) so that you don't need an initrd.

2.3 drop the things you don't need - this is merely to reduce the
time it takes to build a kernel.  Distros normally build
_everything_ as a module.  Provided you can boot without an initrd,
reducing the number of modules only makes it quicker to build a new
kernel - but if you are starting from something which looks like
"allmodconfig" it can save a lot of time.

2.4 for your convenience, ensure that you have enabled the config to
be stored in /proc/config.gz - once you are building your own
slimmed-down kernels, you probably won't want to mess about with
distro "install" scripts so just copying the bzimage to
/boot/vmlinuz-x.y.z, make modules_install, and editing
/boot/grub/grub.cfg (yes, really!) will save a lot of time.

2.5 Add your own version, e.g. for 3.8.2 change EXTRAVERSION to 2-A
so that the kernel will be 3.8.2-A (this stops it overwriting
existing existing 3.8.2 modules, in case the first attempt doesn't
do what you want).

3.  That might take two or three attempts to get to a good config,
but after that you should be able to use the slimmer config (from
zcat /proc/config.gz) to create .config for any newer version you
want to test or bisect, and then just run make oldconfig before you
build.

 Also, when you get back to bisecting, the version in the kernel
Makefile might not be what you expect.  If in doubt, you can change
it to something which doesn't overwrite any existing modules, e.g.
3.8.bisect-1 etc.

 HTH

ĸen
-- 
das eine Mal als Tragödie, dieses Mal als Farce