Initcall Debug - Revision history

Tghs: Updated kernel config option for current kernel.

2012-11-12T16:08:07Z

Updated kernel config option for current kernel.

Jsujjava: Add Category Boot Time, Kernel

2011-05-09T14:53:07Z

Add Category Boot Time, Kernel

Andrewmurray at 10:51, 22 July 2010

2010-07-22T10:51:43Z

Tim Bird: /* Introduction */ fix typo in sed command

2009-09-15T22:31:19Z

‎Introduction: fix typo in sed command

Tim Bird: /* Introduction */ improve readability of option

2009-09-15T21:57:01Z

‎Introduction: improve readability of option

Tim Bird: /* Notes */ fix typo in config name

2009-09-15T21:56:13Z

‎Notes: fix typo in config name

Tim Bird: /* Introduction */

2009-09-15T21:55:40Z

‎Introduction

Tim Bird: /* Introduction */ remove extra wording

2008-11-20T00:02:01Z

‎Introduction: remove extra wording

Tim Bird: add sample (processed) output

2008-11-20T00:01:35Z

add sample (processed) output

Tim Bird: /* Introduction */ fix typo

2008-11-19T23:54:52Z

‎Introduction: fix typo

@@ Line 40: / Line 40: @@
 the kernel during system boot.  It's a good idea to increase the printk log
 buffer size to avoid overflowing the log buffer.  To do this, increase the
-value of CONFIG_LOGBUF_SHIFT from 14 to 18.  This increases the log buffer
+value of CONFIG_LOG_BUF_SHIFT from 14 to 18.  This increases the log buffer
 from the default size of 16k to 256K.

← Older revision		Revision as of 14:53, 9 May 2011
Line 44:		Line 44:

	You will need to enable CONFIG_PRINTK_TIME and CONFIG_KALLSYMS in your kernel configuration for this to work correctly. The first option displays printk timings and the second option ensures that function names are printed rather than memory addresses.		You will need to enable CONFIG_PRINTK_TIME and CONFIG_KALLSYMS in your kernel configuration for this to work correctly. The first option displays printk timings and the second option ensures that function names are printed rather than memory addresses.
		+	[[Category:Boot Time]]
		+	[[Category:Kernel]]

← Older revision		Revision as of 10:51, 22 July 2010
Line 42:		Line 42:
	value of CONFIG_LOGBUF_SHIFT from 14 to 18. This increases the log buffer		value of CONFIG_LOGBUF_SHIFT from 14 to 18. This increases the log buffer
	from the default size of 16k to 256K.		from the default size of 16k to 256K.
		+
		+	You will need to enable CONFIG_PRINTK_TIME and CONFIG_KALLSYMS in your kernel configuration for this to work correctly. The first option displays printk timings and the second option ensures that function names are printed rather than memory addresses.

@@ Line 13: / Line 13: @@
 initcalls numerically by duration.  Here is a command to do this:
-  dmesg -s 128000 | grep "initcall" | sed "s/(.*\)after\(.*\)/\2 \1/g" | sort -n
+  dmesg -s 128000 | grep "initcall" | sed "s/\(.*\)after\(.*\)/\2 \1/g" | sort -n
 == Sample output ==

@@ Line 1: / Line 1: @@
 == Introduction ==
-Passing the initcall_debug option on the kernel command line will cause timing information to be printed to the console for each initcall. initcalls are used to initialize statically linked kernel drivers and subsystems and contribute a significant amount of time to the Linux boot process. The output looks like this:
+Passing the option "initcall_debug" on the kernel command line will cause timing information to be printed to the console for each initcall. initcalls are used to initialize statically linked kernel drivers and subsystems and contribute a significant amount of time to the Linux boot process. The output looks like this:
 <pre>

@@ Line 10: / Line 10: @@
 You can use 'dmesg' to see the messages after the kernel has booted.
-With a sort 'sed' script, you can reorder the final 'timing' line, and short the
+With a short 'sed' script, you can reorder the final 'timing' line, and sort the
 initcalls numerically by duration.  Here is a command to do this:

← Older revision		Revision as of 00:01, 20 November 2008
Line 14:		Line 14:

	dmesg -s 128000 \| grep "initcall" \| sed "s/(.\)after\(.\)/\2 \1/g" \| sort -n		dmesg -s 128000 \| grep "initcall" \| sed "s/(.\)after\(.\)/\2 \1/g" \| sort -n
		+
		+	== Sample output ==
		+	Here is some sample output from the above command sequence.
		+	This was on an old X86-based desktop system. [[Printk Times]] was turned on (hence the
		+	extra timestamp on each line.)
		+
		+	<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0 1em 1em 1em; background-color:#ffffcc; align:right; ">
		+	24 msecs [ 2.237177] initcall acpi_button_init+0x0/0x51 returned 0
		+	<br>28 msecs [ 0.763503] initcall init_acpi_pm_clocksource+0x0/0x16c returned 0
		+	<br>32 msecs [ 0.348241] initcall acpi_pci_link_init+0x0/0x43 returned 0
		+	<br>33 msecs [ 0.919004] initcall inet_init+0x0/0x1c7 returned 0
		+	<br>33 msecs [ 5.282722] initcall psmouse_init+0x0/0x5e returned 0
		+	<br>54 msecs [ 2.979825] initcall e100_init_module+0x0/0x4d returned 0
		+	<br>71 msecs [ 0.650325] initcall pnp_system_init+0x0/0xf returned 0
		+	<br>91 msecs [ 0.872402] initcall pcibios_assign_resources+0x0/0x85 returned 0
		+	<br>187 msecs [ 4.369187] initcall ehci_hcd_init+0x0/0x70 returned 0
		+	<br>245 msecs [ 2.777161] initcall serial8250_init+0x0/0x100 returned 0
		+	<br>673 msecs [ 5.098052] initcall uhci_hcd_init+0x0/0xc1 returned 0
		+	<br>830 msecs [ 4.067279] initcall piix_init+0x0/0x27 returned 0
		+	<br>1490 msecs [ 8.290606] initcall ip_auto_config+0x0/0xd70 returned 0
		+	</div>

	== Notes ==		== Notes ==