On Sat, 05 Jan 2013 20:04:14 +0000 Ian Campbell <i...@hellion.org.uk> wrote: > Hanno, I'm afraid don't know what is causing your boot failures but I > don't think it is related to the new qcontrol package :-( No, it's not related to qcontrol:
> A few things I tried while diagnosing this today:
>
> netconsole, add the following to /etc/initramfs-tools/modules:
> mv643xx_eth
> netconsole netconsole=@<TS-IP>/eth0,@<TGT-IP>/<TGT-MAC>
[...]
> The other thing I tried was to edit /usr/share/initramfs-tools/init like
> so:
> # Parse command line options
> -for x in $(cat /proc/cmdline); do
> +for x in $(cat /proc/cmdline) debug; do
[...]
> So then I edited /usr/share/initramfs-tools/init again and changed it
> like this (under the handling of the debug option):
> debug)
> debug=y
> quiet=n
> - exec >/run/initramfs/initramfs.debug 2>&1
> + exec >/dev/kmsg 2>&1
> set -x
> ;;
>
> IOW I redirected the initramfs debugging to the kernel log, i.e. to
> netconsole. Now you should get pretty verbose debugging on the netcat on
> the other machine. At least for me it starts around local-premount. I
> hope this helps!
OK, done that. Now I can confirm that it's not qcontrol related:
[ 27.774712] + /scripts/init-bottom/qcontrol
[ 27.791290] Error opening
/dev/input/by-path/platform-gpio-keys-event: No such file or
directory
[ 27.805451] + [ -e /conf/param.conf ]
[ 27.805780] + . /conf/param.conf
[ 27.806024] +
ROOT=/dev/disk/by-uuid/de81f811-fbe8-4d12-b969-f5c71e1fecfb
[ 27.806196] + /scripts/init-bottom/udev
... full boot log is attached, there you can see it stops while / after
installing knfsd. After that, nothing happens for >= 10 minutes (and
then I rebootet).
On a normal boot, the only messages after "Installing knfsd" are:
[ 39.285206] Installing knfsd (copyright (C) 1996 o...@monad.swb.de).
[ 42.878783] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state
recovery directory
[ 42.890269] NFSD: starting 90-second grace period
But two things remain:
* why does this only happen while I use the wheezy2 package? I've
rebuilt the initramfs now ~10 times with this, with the wheezy1 and
the sid version this never happened (and those were always generated,
I've used the deb installer for recvovery).
* should udev start before qcontrol and should evdev.ko be in the
modules list? or does qcontrol switch the watchdog off w/o it? it
seems like it works without it...
Hanno
qcontrol-wheezy2.boot.log.gz
Description: GNU Zip compressed data
qcontrol-sid.boot.log.gz
Description: GNU Zip compressed data
