On Sun, 29 Sep 2013, Nick Lewycky wrote: > >Or failing that, if you could please purge the package, reboot (so that > >you'll be running with BIOS microcode) and install it again (which would do > >a "first microcode update"), just to make sure first installs are safe? > > This worked! (For clarification, I purged, cold rebooted and > installed 2.20131007.1+really20130710.1.)
Thank you, that helps. At least now I know I can just disable online updates on AMD and require a reboot. Still, that's far from optimal :-( Nick, both me and AMD are having a heck of a time trying to reproduce this in order to actually find out what is broken, and so far none of us managed to reproduce it. It would be *really* *really* helpful if you could reproduce it for us and send us kernel state debugging output. Basically, I'd need you to press SysRq+t and SysRq+w *with the system hung on the microcode update*, and send me the (large) logs it will generate in /var/log/kern.log. If you're willing to do this testing, you may need to install the old amd64-microcode package to be able to reproduce things. It is here: http://snapshot.debian.org/package/amd64-microcode/ (and you can find out what packages you had, etc. at /var/log/apt/* and /var/log/aptitude*) Please enable SysRq function first, just in case: (from https://fedoraproject.org/wiki/QA/Sysrq): CONFIG_MAGIC_SYSRQ=y on the kernel (this is usual). add "kernel.sysrq=1" to /etc/sysctl.conf The sysrq+t and sysrq+w combinations are for QWERTY, for other keyboard layouts, please look here: http://en.wikipedia.org/wiki/Magic_SysRq_key Thank you! > microcode module was already loaded at boot, installing > amd64-microcode_2.20120910-1_amd64.deb has this to say in the > kern.log: > > Sep 29 18:00:31 calvin kernel: ld-linux-x32.so[5878] general > protection ip:f771ee8d sp:ffe62ee8 error:0 in > ld-2.17.so[f7708000+21000] > Sep 29 18:00:33 calvin kernel: ld-linux-x32.so[6574] general > protection ip:f7766e8d sp:ffdf2538 error:0 in > ld-2.17.so[f7750000+21000] > Sep 29 18:00:37 calvin kernel: ld-linux-x32.so[7212] general > protection ip:f77cee8d sp:ffbefa68 error:0 in > ld-2.17.so[f77b8000+21000] I wonder what the heck is this. You're running X32? -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
