linux-kernel - Re: Linux 2.6.33-rc3, rc2 regression at boot

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-id: <201001061936.10315.gene.heskett@verizon.net>
Date:	Wed, 06 Jan 2010 19:36:10 -0500
From:	Gene Heskett <gene.heskett@...izon.net>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.33-rc3, rc2 regression at boot

On Wednesday 06 January 2010, Jiri Kosina wrote:
>On Wed, 6 Jan 2010, Gene Heskett wrote:
>> >[    0.558368] Unpacking initramfs...
>> >[    0.648644] Freeing initrd memory: 3431k freed
>> >[    0.651635] platform microcode: firmware: requesting
>> > amd-ucode/microcode_amd.bin [   60.646738] microcode: failed to load
>> > file amd-ucode/microcode_amd.bin [   60.646858] microcode: CPU0:
>> > patch_level=0x1000065
>> >[   60.646977] microcode: CPU1: patch_level=0x1000065
>> >[   60.647099] microcode: CPU2: patch_level=0x1000065
>> >[   60.647218] microcode: CPU3: patch_level=0x1000065
>> >
>> >Note the time, it kills quite close to a whole minute there, which at
>> > first would appear to be because there is not yet a mounted /lib
>> > filesystem to suck it from.  I didn't build an rc1, but rc2 also
>> > suffers from this. 2.6.32.2 does not do this although its firmware
>> > request takes place at the same point. So it doesn't look like it is
>> > the lack of a mounted filesystem after all.
>> >
>> >FWIW, because it was a hot reboot, the patch_level reported is the
>> > correct level.
>> >
>> >I am also seeing some complaints about my Audigy2 sound card, but what I
>> > saw during the boot, never made it to the messages log.  Something
>> > about guessing at the proper config, but I did hear kde sign on when x
>> > started.
>> >
>> >Thanks Linus.
>>
>> Update, I edited the .config by hand and added the full path in
>> CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware/"
>> which was just 'firmware', and rebuilt.  No difference.  I still get the
>> 60 second hang.  FWIW, this particular setting isn't visible in a make
>> xconfig.
>
>As this is already at the stage when userspace exists and init has been
>started, it might well be delay of some userspace stuff, not directly
>kernel.
>
>Does alt-sysrq-t at the time it is stuck give any clue?
>
I will try that when I next reboot, thanks Jiri

-- 
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)

"Just the facts, Ma'am"
-- Joe Friday
--
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/