Merge branch 'ixp4xx' of git://git.kernel.org/pub/scm/linux/kernel/git/chris/linux-2.6 into devel

    seriously wrong while debugging, it will most often be the case

    that you want to enable gdb to be verbose about its target

    communications.  You do this prior to issuing the <constant>target

    remote</constant> command by typing in: <constant>set remote debug 1</constant>

    remote</constant> command by typing in: <constant>set debug remote 1</constant>

    </para>

  </chapter>

  <chapter id="KGDBTestSuite">

	usbcore.blinkenlights=1

Hyphens (dashes) and underscores are equivalent in parameter names, so

	log_buf_len=1M print-fatal-signals=1

can also be entered as

	log-buf-len=1M print_fatal_signals=1

This document may not be entirely up to date and comprehensive. The command

"modinfo -p ${modulename}" shows a current list of all parameters of a loadable

module. Loadable modules, after being loaded into the running kernel, also

			not play well with APC CPU idle - disable it if you have

			APC and your system crashes randomly.

	apic=		[APIC,i386] Advanced Programmable Interrupt Controller

	apic=		[APIC,X86-32] Advanced Programmable Interrupt Controller

			Change the output verbosity whilst booting

			Format: { quiet (default) | verbose | debug }

			Change the amount of debugging information output

			to discrete, to make X server driver able to add WB

			entry later. This parameter enables that.

	enable_timer_pin_1 [i386,x86-64]

	enable_timer_pin_1 [X86]

			Enable PIN 1 of APIC timer

			Can be useful to work around chipset bugs

			(in particular on some ATI chipsets).

	hashdist=	[KNL,NUMA] Large hashes allocated during boot

			are distributed across NUMA nodes.  Defaults on

			for IA-64, off otherwise.

			for 64bit NUMA, off otherwise.

			Format: 0 | 1 (for off | on)

	hcl=		[IA-64] SGI's Hardware Graph compatibility layer

The bit position indicates STATE, STATE-read, for each of the states listed

above, and the character displayed in each indicates:

   '.'  acquired while irqs disabled

   '+'  acquired in irq context

   '-'  acquired with irqs enabled

   '.'  acquired while irqs disabled and not in irq context

   '-'  acquired in irq context

   '+'  acquired with irqs enabled

   '?'  acquired in irq context with irqs enabled.

Unused mutexes cannot be part of the cause of an error.

- nr_hugepages

- nr_overcommit_hugepages

- nr_pdflush_threads

- nr_pdflush_threads_min

- nr_pdflush_threads_max

- nr_trim_pages         (only if CONFIG_MMU=n)

- numa_zonelist_order

- oom_dump_tasks

==============================================================

nr_pdflush_threads_min

This value controls the minimum number of pdflush threads.

At boot time, the kernel will create and maintain 'nr_pdflush_threads_min'

threads for the kernel's lifetime.

The default value is 2.  The minimum value you can specify is 1, and

the maximum value is the current setting of 'nr_pdflush_threads_max'.

See 'nr_pdflush_threads_max' below for more information.

==============================================================

nr_pdflush_threads_max

This value controls the maximum number of pdflush threads that can be

created.  The pdflush algorithm will create a new pdflush thread (up to

this maximum) if no pdflush threads have been available for >= 1 second.

The default value is 8.  The minimum value you can specify is the

current value of 'nr_pdflush_threads_min' and the

maximum is 1000.

==============================================================

overcommit_memory:

This value contains a flag that enables memory overcommitment.

  "devices" directory at /sys/subsystem/<name>/devices.

  If /sys/subsystem exists, /sys/bus, /sys/class and /sys/block can be

  ignored. If it does not exist, you have always to scan all three

  ignored. If it does not exist, you always have to scan all three

  places, as the kernel is free to move a subsystem from one place to

  the other, as long as the devices are still reachable by the same

  subsystem name.