linux-kernel - 2.6.33-rc2 odd messages

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-id: <200912251429.52426.gene.heskett@verizon.net>
Date:	Fri, 25 Dec 2009 14:29:52 -0500
From:	Gene Heskett <gene.heskett@...izon.net>
To:	linux-kernel@...r.kernel.org
Subject: 2.6.33-rc2 odd messages

Greetings;

I just built & installed 2.6.33-rc2, and on the reboot, had a long stall
here, which apparently timed out while I was going after my camera:

Dec 25 14:04:47 coyote kernel: [    0.653106] platform microcode: firmware: requesting amd-ucode/microcode_amd.bin
Dec 25 14:04:47 coyote kernel: [   60.643402] microcode: failed to load file amd-ucode/microcode_amd.bin
Dec 25 14:04:47 coyote kernel: [   60.643522] microcode: CPU0: patch_level=0x1000065
Dec 25 14:04:47 coyote kernel: [   60.643643] microcode: CPU1: patch_level=0x1000065
Dec 25 14:04:47 coyote kernel: [   60.643768] microcode: CPU2: patch_level=0x1000065
Dec 25 14:04:47 coyote kernel: [   60.643887] microcode: CPU3: patch_level=0x1000065
Dec 25 14:04:47 coyote kernel: [   60.644046] microcode: Microcode Update Driver: v2.00 <tigran@...azian.fsnet.co.uk>, Peter Oruba

However, /lib/firmware/amd-ucode has this file:
[root@...ote amd-ucode]# ls -l
total 4
-rw-r--r-- 1 root root 2012 2009-01-20 04:48 microcode_amd.bin

And, from the looks of the patch_level reported above, it did eventually load 
it, or it was still there since it was a hot reboot, not a full powerdown 
since that's a bit hard on drives.

Is this something in the way of a path that I could pass on the grub kernel 
command line in grub.conf to aid it in finding this file?

Also, quite a bit later (and I have to run blueman-manager and play with it
before a bluetooth 'rfcomm0' link can be re-established that was there
and working fine when I did the reboot logout in x:

Dec 25 14:04:49 coyote bluetoothd[2597]: Failed to access HAL

Any hints on that would be nice too.

Merry Christmas everybody.  And other than the above, 2.6.33-rc2 seems to be 
well, and I note that something has recently taken the glxgears speed up about 
150% on rv610 based cards, thank you for that too.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)

	"For I perceive that behind this seemingly unrelated sequence
of events, there lurks a singular, sinister attitude of mind."
	"Whose?"
	"MINE! HA-HA!"
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/