Re: [start_kernel] Suggest to move parse_args() before trap_init()

[Dave Jones]

On Mon, Mar 01, 2004 at 09:46:38PM +0100, Andi Kleen wrote:

 > > I think the only problem with this is if we get a fault during
 > > parse_args(), the kernel flies off into outer space.  So you lose some
 > > debuggability when using an early console.
 > > 
 > > But 2.4 does trap_init() after parse_args() and nobody has complained, as
 > > did 2.6 until recently.  So the change is probably OK.
 > 
 > The standard way to fix this is to add an explicit check for lapic
 > to the early argument parsing in setup.c (but keep the __setup so that
 > no unknown argument is reported).

This just got me thinking of a sort-of related problem.
Some laptops hang when local apic is enabled, and we couldn't
blacklist them in 2.4 due to us not doing the dmi scan early enough.

Did that get fixed in 2.6 ?

		Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/