On Wed, Mar 11, 2015 at 04:15:21PM -0400, Stephen Beckwith wrote: > Greetings, > Please forgive the long-winded e-mail, but as a fellow developer, the > more you know, the easier/quicker you can reach some sort of conclusion > with my problem here. <snip> > This kernel seems to boot OK, to the point of starting up the init process: > > Linux version 3.18.4 ([email protected]) (gcc version 4.9.2 > 20150212 (Red Hat 4.9.2-6) (GCC) ) #2 SMP Mon Mar 9 16:48:10 EDT 2015 > I see the "Freeing kernel memory. . . . " line, then I get a kernel panic. > This is preceded by the following "help" message: > > Usage: init [options] [mask | cpu-list] [pid|cmd [args...]] > > > Options: > > -a, --all-tasks operate on all the tasks (threads) for a given pid > > -p, --pid operate on existing given pid > > -c, --cpu-list display and specify cpus in list format > > -h, --help display this help > > -V, --version output version information > > > The default behavior is to run a new command: > > init 03 sshd -b 1024 > > You can retrieve the mask of an exisSwitched to clocksource tsc > > ting task: > > init -p 700 > > Or set it: > > init -p 03 700 > > List format uses a comma-separated list instead of a mask: > > init -pc 0,3,7-11 700 > > Ranges in list format can take a stride argument: > > e.g. 0-31:2 is equivalent to mask 0x55555555 > > > For more information see taskset(1). > I assume this is from BusyBox. > taskset() is configured to be part of busy box, per the configuration I > generated.
> So my questions are: > 1) IS this Usage message coming from the busy box "init" ???? No. It's coming from util-linux taskset, printing argv[0] as the name. You can tell this by (1) the absence of the standard Busybox header: BusyBox v1.22.1 (Debian 1:1.22.0-9+b1) multi-call binary. (or similar) (2) the reference to taskset(1), which means "the taskset manpage" (3) it matches the output of taskset --help > 2) does busy box work with a 3.18.4 kernel? It should, though a lot of people aren't *quite* that up-to-date. > 3) what changed that now INIT requires parameters? Your scripts must be (correctly) linking taskset to busybox, and (incorrectly) overwriting that with a copy of the taskset binary. HTH, Isaac _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
