hi, Am 16.02.2012 um 15:09 schrieb Waldemar Brodkorb:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > just curious if there is no aufs support in your kernel? > cat /proc/filesystems shows what? arrgh .... aufs was compiled as module, but it seems, that the module can't load. "modprobe aufs" does nothing and /proc/filesystems doesn't show aufs. So I recompiled the kernel with aufs inside. Without boot=live, I can see aufs in /proc/filesystems. But with ...: [...] [ 90.065156] tg3 0000:09:04.1: BAR 2: set to [mem 0x7f904030000-0x7f90403ffff] (PCI address [0x4030000-0x403ffff]) [ 90.249835] tg3 0000:0c:04.0: BAR 0: set to [mem 0x7f904800000-0x7f9049fffff] (PCI address [0x4800000-0x49fffff]) [ 90.385147] tg3 0000:0c:04.0: BAR 2: set to [mem 0x7f904610000-0x7f90461ffff] (PCI address [0x4610000-0x461ffff]) [ 92.346912] Kernel panic - not syncing: Attempted to kill init! [ 92.425715] tg3 0000:09:04.0: eth0: Link is up at 1000 Mbps, full duplex [ 92.513952] tg3 0000:09:04.0: eth0: Flow control is on for TX and on for RX [ 92.605627] Call Trace: [ 92.637708] [000000000045b8f8] do_exit+0xa8/0x6bc [ 92.700718] [000000000045bfec] SyS_exit+0x10/0x1c [ 92.763746] [0000000000405fd4] linux_sparc_syscall32+0x34/0x40 what for a hell ... I can say, it does a bit more, than before (just a few lines, with raid, partitions etc. ...). the NFS mount was also done, what I can see from the fai server, but this was also working, before I recompiled the kernel. How can I debug this problem? I changed "/init" with "#!/bin/sh -x", but I don't get any messages on the screen. So, whatever going from, it happens after the NFS mount. cu denny
signature.asc
Description: Message signed with OpenPGP using GPGMail
