On Wed, Dec 01, 2010 at 05:25:54PM +0100, Sedat Dilek wrote: > On Mon, Nov 29, 2010 at 2:55 PM, Nick Piggin <npiggin@xxxxxxxxx> wrote: > > On Mon, Nov 29, 2010 at 02:36:41PM +0100, Sedat Dilek wrote: > >> On Mon, Nov 29, 2010 at 1:55 PM, Sedat Dilek <sedat.dilek@xxxxxxxxxxxxxx> wrote: > >> > Hi, > >> > > >> > I have tried the vfs-scale-working patch-set from [1] (GIT tree see [2]). > >> > Unfortunately, I cannot boot my Debian/sid i386 system with systemd > >> > (system freezes) but with sysvinit. > >> > I have attached a screenshot of the Call-trace, hope this helps. > >> > > >> > What I tried to get things worjing is: > >> > * Downgrade systemd from v15 down to v12 > >> > * Remove "mtab hackz" [3] > >> > * Remove native mount feature [4] (also in combination with "mtab hackz") > >> > * Mask systemd-remount-api-vfs.service (for testing purposes) > >> > > >> > Not sure what the real problem is (as it is very early), but sysvinit is fine. > >> > > >> > # cat /proc/cmdline > >> > BOOT_IMAGE=/boot/vmlinuz-2.6.37-rc3-686 > >> > root=UUID=1ceb69a7-ecf4-47e9-a231-b74e0f0a9b62 ro radeon.modeset=1 > >> > lapic 3 init=/sbin/init.sysvinit > >> > > >> > How can I protocol very early messages (I don't think it makes any > >> > sense to activate systemd debugging [5] right now)? > >> > Any advices for this? > >> > > >> > Any idea on the Call-trace or digging into the problem? > >> > Any help appreciated. > > > > Thanks for this, it definitely looks like a bug in vfs scale patches. > > > > I wonder if you can run with frame pointers turned on to get a more > > reliable back trace, and then also try to capture the information > > surrounding the oops. > > > > Thanks, > > Nick > > 2nd screenshot from a kbd-session. OK, thanks. Can you send a disasm of fs/namei.o, please? -- 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
