Hello Marc, According to your Call Trace, there is no aufs operation. The problem happend in VFS layer. I'd suggest you to check your kernel build or boot environment. If there is something wrong in your environment and you can fix it, you may also solve the other problem "/bin/sh: bad interpreter: Text file busy".
J. R. Okajima Marc Dirix: > I also get this "problem" while rebooting: > > BUG: unable to handle kernel NULL pointer dereference at 00000028 > IP: [<c0253093>] fs_may_remount_ro+0x12/0x46 > *pde = 00000000 > Oops: 0000 [#1] > last sysfs file: /sys/fs/aufs/si_d8543625/br1 > Modules linked in: ipt_LOG > > Pid: 1904, comm: mount Not tainted (2.6.32-00707-g1f5235c #1) > EIP: 0060:[<c0253093>] EFLAGS: 00010283 CPU: 0 > EIP is at fs_may_remount_ro+0x12/0x46 > EAX: 00000000 EBX: cf92b870 ECX: cb099700 EDX: cb0b0c80 > ESI: 00000000 EDI: 00000000 EBP: cfac9f20 ESP: cfac9f1c > DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068 > Process mount (pid: 1904, ti=cfac8000 task=cf8e10e0 task.ti=cfac8000) > Stack: > cf92b800 cfac9f38 c025388c 00000001 00000021 00000000 00000060 cfac9f88 > <0> c0263ae0 00000000 cf950120 cf950150 00000001 cfac51e0 cfac9f6c cf92b800 > <0> cf92b83c 00000021 00000009 00001000 cfac9f84 c0241f74 cf831080 cf405b00 > Call Trace: > [<c025388c>] ? do_remount_sb+0x67/0xab > [<c0263ae0>] ? do_mount+0x18c/0x58a > [<c0241f74>] ? strndup_user+0x48/0x67 > [<c0263f3f>] ? sys_mount+0x61/0x96 > [<c0202855>] ? syscall_call+0x7/0xb ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
