Re: [Bugme-new] [Bug 9217] New: CONFIG_CMDLINE doesn't pass to kernel

[Richard Purdie <rpurdie@rpsys.net>]

On Thu, 2007-10-25 at 13:02 -0700, Andrew Morton wrote:
> On Thu, 25 Oct 2007 14:43:36 +0100
> Richard Purdie <rpurdie@rpsys.net> wrote: 
> > Could the original bug reporter please report what commandline the
> > kernel actually uses please? In theory it can only be either:
> > 
> > * the one being compiled in with CONFIG_CMDLINE
> > * the one hardcoded into the bootloader
> > 
> > but I'd be surprised it boots at all with the latter!
> 
> It was in the inital report, at
> http://bugzilla.kernel.org/show_bug.cgi?id=9217 :

No it wasn't, I'd looked.

> : I try to upgrade kernel from 2.6.22.9 to 2.6.23.
> : 2.6.22.9 works correct. Kernel 2.6.23 doesn't use  CONFIG_CMDLINE and doesn't
> : pass bootparams:
> : CONFIG_CMDLINE="console=ttyS0,115200n8 console=tty1 noinitrd
> : root=/dev/mmcblk0p1 rootfstype=ext3 rw rootdelay=5"
> : But kernel still try to mount /dev/mtdblock2 using jffs2.
> : Steps to reproduce:
> : Compile kernel with CONFIG_CMDLINE and try to boot.

This is the commandline they wanted to use, not the one that was
actually used. The one that was used should appear on the console, on
the serial console if they have the lead or in dmesg when the device
boots. We know it probably contained root=/dev/mtdblock2 but thats it.

I'd like to confirm which commandline is appearing since if we know
which one it is we might stand a chance of knowing where it came from,
until then this is just a guessing game.

Cheers,

Richard