Re: systemd failing with vfs-scale-working patch-set

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Nick,

after upgrading my toolchain and kernel-buildsystem I found some time
spending in getting some more infos on the systemd w/ vfs-scale
problem.
Eric reported in [1] same problems as I have seen.

My systemd is now v15+git20101210.8a9ef77 and Linux kernel is:

# cat /proc/version
Linux version 2.6.37-rc6-686 (Debian
2.6.37~rc6-5~next20101220.dileks.1) (sedat.dilek@xxxxxxxxx) (gcc
version 4.5.2 (Debian 4.5.2-1) ) #1 SMP Mon Dec 20 19:03:29 CET 2010

I could take some new pics [2].

[3] shows a kernel NULL pointer dereference (dmesg command in
kdb-console), but the address is not displayed, might be I need to set
some additional kernel-debug-options.

[4] shows the output of "btp 4" (backtrace PID #4 from kdb-console),
see also in [3] "*pde = 00000000" (8 zeroes) shows <4> (PID #4) at the
beginning of the line.

I have also a "btp 1" (systemd has PID #1).

Hope this helps to narrow down the problem.
If you need additional informations or (disasm-ed) files, please let me know.

Some pics are doubled, sorry for the bad quality, I won't be a surgery
(need a calm hand, turned off auto-flash of my digicam is the real
cause I guess ;-)).

Regards,
- Sedat -


[1] http://marc.info/?l=linux-fsdevel&m=129287321819101&w=2
[2] http://files.iniza.org/for_npiggin/2010-12-20/
[3] http://files.iniza.org/for_npiggin/2010-12-20/DSCN2344.JPG
[4] http://files.iniza.org/for_npiggin/2010-12-20/DSCN2353.JPG
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel]     [Linux USB Development]     [Yosemite News]     [Linux SCSI]

  Powered by Linux