[systemd-devel] systemd failing with vfs-scale-working patch-set (kdb-1/2)

[Sedat Dilek]

On Mon, Nov 29, 2010 at 2:55 PM, Nick Piggin <npiggin at 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 at 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

OK, now I have played with kdb [0..3] and I have now some "backtrace" for you.
I will split the screenshots in kbd-1/2 and kbd-2/2 (see subject).

While copying the pics from my digicam to hdd I discovered also a NULL
derefence in vfat_cmpi (will send as a separate post to
linux-fsdevel).

Hope this helps getting thing fixed.

- Sedat -

P.S.: Note to myself cmdline + kernel-config

[ cmdline ] kdb with kernel mode setting: kgdboc=kms,kbd

[ debian/config/i386/none/config.686 ]
...
##
## file: lib/Kconfig.debug
##
CONFIG_DEBUG_INFO=y <--- Let this explode build-dir from 1.4G up to 4.5G :-)?
# CONFIG_DEBUG_RODATA is not set
CONFIG_FRAME_POINTER=y

##
## file: lib/Kconfig.kgdb
##
CONFIG_KGDB=y
CONFIG_KGDB_SERIAL_CONSOLE=y
CONFIG_KGDB_KDB=y
CONFIG_KDB_KEYBOARD=y
- EOF -

[ References ]

[0] http://kernel.org/pub/linux/kernel/people/jwessel/kdb/
[1] http://kernel.org/pub/linux/kernel/people/jwessel/kdb/CompileKDB.html
[2] http://kernel.org/pub/linux/kernel/people/jwessel/kdb/kgdbKernelArgs.html#kgdboc
[3] http://kernel.org/pub/linux/kernel/people/jwessel/kdb/kgdbKernelArgs.html#kgdbocArgs3
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DSCN2321_resized.jpg
Type: image/jpeg
Size: 296628 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20101201/b052b4b8/attachment-0001.jpg>