Richard Weinberger wrote: > Am Montag 04 Juli 2011, 16:59:32 schrieb Richard Weinberger: > > Here the second boot log: > > http://userweb.kernel.org/~rw/boot2.log > > > > The interesting part is: > > ---cut--- > > VFS: Mounted root (ext2 filesystem) readonly on device 98:0. > > Calling request_module() swapper 1 /sbin/init 1 3 > > Calling request_module() kworker/u:0 211 /sbin/modprobe 4 3 > > ... > > Calling request_module() kworker/u:0 8741 /sbin/modprobe 4 3 > > ---cut--- > > > > After the last "Calling request_module..." message no more messages appear > > and the kernel seems to loop for ever. > > > > Please ignore this. > The "Calling request_module..." messages continue for ever. > In the first case my terminal locked up... > current->pid also wraps around. > Please note that the each PID is printed for twice. This means that each thread within the loop tries to create a thread. Therefore, it will repeat for (1 << MAX_KMOD_CONCURRENT) times. It is large enough to wrap the PID. Well, try with smaller MAX_KMOD_CONCURRENT (e.g. 3). Calling request_module() kworker/u:0 299 /sbin/modprobe 4 3 Calling request_module() kworker/u:0 301 /sbin/modprobe 4 3 **** 301 1st loop Calling request_module() kworker/u:0 303 /sbin/modprobe 4 3 **** 303 1st loop Calling request_module() kworker/u:0 305 /sbin/modprobe 4 3 **** 305 1st loop Calling request_module() kworker/u:0 307 /sbin/modprobe 4 3 **** 307 1st loop Calling request_module() kworker/u:0 309 /sbin/modprobe 4 3 **** 309 1st loop request_module: runaway loop modprobe binfmt-464c Calling request_module() kworker/u:0 309 /sbin/modprobe 4 3 **** 309 2nd loop request_module: runaway loop modprobe binfmt-464c Calling request_module() kworker/u:0 307 /sbin/modprobe 4 3 **** 307 2nd loop Calling request_module() kworker/u:0 311 /sbin/modprobe 4 3 **** 311 1st loop request_module: runaway loop modprobe binfmt-464c Calling request_module() kworker/u:0 311 /sbin/modprobe 4 3 **** 311 2nd loop request_module: runaway loop modprobe binfmt-464c Calling request_module() kworker/u:0 305 /sbin/modprobe 4 3 **** 305 2nd loop Calling request_module() kworker/u:0 313 /sbin/modprobe 4 3 **** 313 1st loop Calling request_module() kworker/u:0 315 /sbin/modprobe 4 3 **** 315 1st loop request_module: runaway loop modprobe binfmt-464c Calling request_module() kworker/u:0 315 /sbin/modprobe 4 3 **** 315 2nd loop Calling request_module() kworker/u:0 313 /sbin/modprobe 4 3 **** 313 2nd loop Calling request_module() kworker/u:0 317 /sbin/modprobe 4 3 **** 317 1st loop Calling request_module() kworker/u:0 317 /sbin/modprobe 4 3 **** 317 2nd loop Calling request_module() kworker/u:0 303 /sbin/modprobe 4 3 **** 303 2nd loop Calling request_module() kworker/u:0 319 /sbin/modprobe 4 3 Calling request_module() kworker/u:0 321 /sbin/modprobe 4 3 Calling request_module() kworker/u:0 323 /sbin/modprobe 4 3 Calling request_module() kworker/u:0 323 /sbin/modprobe 4 3 Calling request_module() kworker/u:0 321 /sbin/modprobe 4 3 Calling request_module() kworker/u:0 325 /sbin/modprobe 4 3 Calling request_module() kworker/u:0 325 /sbin/modprobe 4 3 Calling request_module() kworker/u:0 319 /sbin/modprobe 4 3 Calling request_module() kworker/u:0 327 /sbin/modprobe 4 3 Calling request_module() kworker/u:0 329 /sbin/modprobe 4 3 Calling request_module() kworker/u:0 329 /sbin/modprobe 4 3 Calling request_module() kworker/u:0 327 /sbin/modprobe 4 3 Calling request_module() kworker/u:0 331 /sbin/modprobe 4 3 Calling request_module() kworker/u:0 331 /sbin/modprobe 4 3 Calling request_module() kworker/u:0 301 /sbin/modprobe 4 3 **** 301 2nd loop Calling request_module() kworker/u:0 333 /sbin/modprobe 4 3 -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
