linux-kernel - Re: how to get the kernel to be more "verbose"?

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

Date:	Fri, 6 Oct 2006 09:22:28 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Uwe Zeisberger <zeisberg@...ormatik.uni-freiburg.de>
Cc:	Witold Władysław Wojciech Wilk 
	<witold.wilk@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: how to get the kernel to be more "verbose"?

On Fri, 6 Oct 2006 09:33:03 +0200 Uwe Zeisberger wrote:

> Hello Witold,
> 
> Witold Władysław Wojciech Wilk wrote:
> > I've tried using the /proc/config.gz provided by the default kernel,
> > but to no avail.
> Does this mean, you cannot find the config because /proc/config.gz
> doesn't exist?  Then try /boot/config-2.6.8.  Maybe I misunderstood you?
>  
> > The next step of loading the kernel I have seen in various logs is the
> > TCP/IP stack, am I right? 
> I think offically the initcalls are in no particular order, but in
> practice in depends on the linking order.  For my kernel the next line
> is
> 
> 	IP route cache hash table entries: 32768 (order: 5, 131072 bytes)

They are in initcall section order and within those sections they
are in link order.  From include/linux/init.h:

/* initcalls are now grouped by functionality into separate 
 * subsections. Ordering inside the subsections is determined
 * by link order. 
 * For backwards compatibility, initcall() puts the call in 
 * the device init subsection.
 */

#define __define_initcall(level,fn) \
	static initcall_t __initcall_##fn __attribute_used__ \
	__attribute__((__section__(".initcall" level ".init"))) = fn

#define core_initcall(fn)		__define_initcall("1",fn)
#define postcore_initcall(fn)		__define_initcall("2",fn)
#define arch_initcall(fn)		__define_initcall("3",fn)
#define subsys_initcall(fn)		__define_initcall("4",fn)
#define fs_initcall(fn)			__define_initcall("5",fn)
#define device_initcall(fn)		__define_initcall("6",fn)
#define late_initcall(fn)		__define_initcall("7",fn)

> > Any help? Please point me at something, I am trying for two weeks
> > already, and I cannot find any problems like mine. Thanks a lot for
> > any help.
> You can try the "initcall_debug" kernel parameter to see which init
> functions are called.

You can also add "debug" to the boot options.  That will make the
kernel more verbose, but beware, some distro's init scripts
change the loglevel during bootup, so it may not have effect for
very long.

And if you have a second machine, you can use netconsole or serial
console (depending on hardware) to capture boot messages.
The "earlyprintk" option could help here.  Even without a second
machine, using "earlyprintk=vga" might help.

---
~Randy
-
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/