linux-kernel - hex code shown 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-next>] [day] [month] [year] [list]

Message-Id: <200810191630.43517.roa@libero.it>
Date:	Sun, 19 Oct 2008 16:30:43 +0200
From:	ROASCIO Paolo <roa@...ero.it>
To:	linux-kernel@...r.kernel.org
Subject: hex code shown at boot

Hello, first of all sorry for my bad english...

I write here because, this case, google wasn't my friend, then i think this 
question will be answered only by kernel gurus.

I need to know something about the strange boot output i obtain in console 
after a (mm and others patched, but the vanilla give me the same results) 
2.6.22.1 compile. Yes. i know this is a very old version, but it's the last i 
can patch to recognize my Flydvb Trio multiple frontends.

Attached (because are very long) are both my relevant part of kern.log, the 
dmesg output and the .config i used.

My question is: the hex code shown at the beginning of my output is a 
system.map dump, a kernel dump, or simply a wrong .config setting?

Please CC me as i'm not subscribed to this mailing list.

Thanks.

ROASCIO Paolo

View attachment "dmesg.txt" of type "text/plain" (130196 bytes)

View attachment "kern.log" of type "text/x-log" (141928 bytes)

View attachment "config" of type "text/plain" (49386 bytes)