From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nick Piggin <npiggin@kernel.dk>
Subject: Re: systemd failing with vfs-scale-working patch-set
Date: Tue, 30 Nov 2010 00:55:26 +1100
Message-ID: <20101129135526.GA3149@amd>
References: <AANLkTiku116GCiLJcEa9KcQeLJq+LM8qsBJZdMC7iCrO@mail.gmail.com>
 <AANLkTikXAiX5JBJeFiS5LxN=RDN9L7-Wyfm5yOm-e7Nc@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: systemd-devel@lists.freedesktop.org, linux-fsdevel@vger.kernel.org,
	Nick Piggin <npiggin@kernel.dk>
To: sedat.dilek@gmail.com
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from ipmail07.adl2.internode.on.net ([150.101.137.131]:29065 "EHLO
	ipmail07.adl2.internode.on.net" rhost-flags-OK-OK-OK-OK)
	by vger.kernel.org with ESMTP id S1754023Ab0K2Nze (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Mon, 29 Nov 2010 08:55:34 -0500
Content-Disposition: inline
In-Reply-To: <AANLkTikXAiX5JBJeFiS5LxN=RDN9L7-Wyfm5yOm-e7Nc@mail.gmail.com>
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

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@googlemail.com> 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