From: Nick Piggin <npiggin@kernel.dk>
To: sedat.dilek@gmail.com
Cc: Nick Piggin <npiggin@kernel.dk>,
systemd-devel@lists.freedesktop.org,
linux-fsdevel@vger.kernel.org
Subject: Re: systemd failing with vfs-scale-working patch-set (kdb-2/2)
Date: Sat, 4 Dec 2010 04:31:01 +1100 [thread overview]
Message-ID: <20101203173101.GB11943@amd> (raw)
In-Reply-To: <AANLkTim1-x4O_fvmbxBXj2yLsM8kX81nqfkc1ApPQRqs@mail.gmail.com>
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@kernel.dk> 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@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
>
> 2nd screenshot from a kbd-session.
OK, thanks. Can you send a disasm of fs/namei.o, please?
next prev parent reply other threads:[~2010-12-03 17:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 16:25 systemd failing with vfs-scale-working patch-set (kdb-2/2) Sedat Dilek
2010-12-03 17:31 ` Nick Piggin [this message]
2010-12-03 19:57 ` Sedat Dilek
2010-12-04 17:14 ` Sedat Dilek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101203173101.GB11943@amd \
--to=npiggin@kernel.dk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=systemd-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.