Blaisorblade wrote: > On Thursday 25 November 2004 19:21, Bodo Stroesser wrote: > >>Have started to test with the new 2.6.10-rc2-mm3 + incrementals tree. >> >>First, it didn't compile, because there are inconsistent definitions >>for __pgd_alloc in include/linux/mm.h and arch/um/kernel/mem.c. >>I added "fastcall" in arch/um/kernel/mem.c, then the build succeeded. >> >>But now the kernel crashes on startup. Please ignore the error messages >>regarding ext3.ko. For the "first shot" I didn't update the initrd. >>But the kernel should handle the fs in ext2-mode anyway. >> >>Bodo > > It seems (I've just read it in the ML, not very clearly) that this is > addressed by: Yes. That caker pointed out on #uml. But there is another crash, that happens sometimes only, since it's dependend on timing. To fix this other one, you need the appended patch too. > > http://marc.theaimsgroup.com/?l=linux-kernel&m=110117212115156&w=2 > > I.e. it's a host kernel bug with quotas and DevFS (or whatever). The marked > portion of the traces match. > >>Error messages from SKAS: > > >>Call Trace: > > [...] > >> [] invalidate_bh_lru+0x19/0x40 >> [] invalidate_bh_lrus+0xa/0x10 > > ** > >> [] vfs_quota_off+0xa8/0x220 >> [] do_umount+0x1b1/0x1d0 >> [] sys_umount+0x67/0x90 > > ** > >> [] handle_page_fault+0x16b/0x1f0 >> [] segv+0x85/0x1e0 >> [] execute_syscall_skas+0xda/0x120 >> [] record_syscall_start+0x4c/0x60 >> [] handle_syscall+0x30/0x60 >> [] handle_trap+0x30/0x130 >> [] userspace+0x188/0x1e0 >> [] fork_handler+0x0/0x80 >> [] __restore+0x0/0x8 >> [] fork_handler+0x0/0x80 >> [] __kill+0x11/0x20 >> >> >> >>Error messages from TT: > > >>Call Trace: > > [...] > ** > >> [] vfs_quota_off+0xa8/0x220 >> [] do_umount+0x1b1/0x1d0 >> [] sys_umount+0x67/0x90 > > ** > >> [] sys_execve+0x3f/0x50 >> [] sigemptyset+0x24/0x40 >> [] execute_syscall_tt+0xda/0x120 >> [] record_syscall_start+0x4c/0x60 >> [] syscall_handler_tt+0x3f/0x70 >> [] sig_handler_common_tt+0x8d/0x110 >> [] sig_handler+0x1e/0x40 >> [] __restore+0x0/0x8 > > >