<div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><div>Hi,</div><div> I'm so sorry for not giving you more details, I'm a freshman here, but I'll try to do better in the future.</div><div>I will give the answers under each of the questions .</div><pre><br>At 2015-06-16 18:54:23, "David Herrmann" <<a href="mailto:dh.herrmann@gmail.com">dh.herrmann@gmail.com</a>> wrote: >Hi > >On Tue, Jun 16, 2015 at 12:07 PM, eshark <<a href="mailto:eshark77@163.com">eshark77@163.com</a>> wrote: >> At 2015-06-16 15:54:10, "David Herrmann" <<a href="mailto:dh.herrmann@gmail.com">dh.herrmann@gmail.com</a>> wrote: >>>Can you be more specific, please? What do you mean by "network module >>>of our systemd cannot work OK"? >> >> Sorry. Acctually our network module cannot get ip by DHCP. Our network >> module is >> connman, which depends on libdbus. And the connman will connect to KDBus >> through the bus-proxyd, which is implemented in the libsystemd. > >Can you please be more specific! > <div>>Does this only happen with kdbus?</div><div>Yes. It's OK with DBus.</div><div><span style="line-height: 1.7;">>Does this only happen with you kdbus-patch to make broadcasts being</span></div><div>>sent to oneself?</div><div>Yes. Without modifying kdbus_bus_broadcast(), I can always get the ip.</div><div>>Or does it happen with unmodified kdbus, too?</div><div>Never.</div><div>>What exactly changes?</div><div>I just commented out the following two lines in the kdbus_bus_broadc</div><div>// if (conn_dst->id == kmsg->msg.src_id)</div><div>// continue;</div><div><br></div><div>>Does everything work perfectly well without kdbus?</div><div>As for network, it did work well without my patch.</div><div><br></div><div>>Is the missing DHCP connectivity the only difference you see with kdbus?</div><div>Acctually, I cannot connet to the device by "adb". But I did run "netcfg" in the terminal, and eth0 didn't get ip as before.</div><div><br></div><div>>What kdbus version do you run?</div><div>kdbus-4.1-rc1</div><div>>What kdbus tree do you use?</div><div><a href="https://git.kernel.org/cgit/linux/kernel/git/gregkh/char-misc.git/" _src="https://git.kernel.org/cgit/linux/kernel/git/gregkh/char-misc.git/">https://git.kernel.org/cgit/linux/kernel/git/gregkh/char-misc.git/</a></div><div> </div><div>>What systemd version do you use? (in case of git: which commit?<span style="line-height: 1.7;">)</span></div><div><span style="line-height: 1.7;">systemd v219 </span></div><div>commit: d736e4f3e76daca4ab1b1fc444737e5ee20a27cd</div><div><br></div><div>>Did you pass --enable-kdbus to systemd?</div><div>Yes , I did.</div><div>>What upstream kernel version do you use?</div><div>3.10.33, we back-ported the kdbus to our kernel.</div><div><br></div><div>>Any obscure messages in the system-log that you didn't see before? </div><div>Em, without my kdbus patch, logcat about ethernet are something like</div><div> "D/EthernetService( 810): EthernetNative.isEthDeviceAdded(eth0) return true</div>I/EthernetStateTracker( 810): trigger dhcp for device eth0 D/EthernetStateTracker( 810): DhcpHandler: DHCP request started I/dhcpcd ( 1298): dhcpcd: /system/bin/dhcpcd -ABKL -f/system/etc/dhcpcd/dhcpcd.conf -f /system/etc/dhcpcd/dhcpcd.conf -h MagicBox1s_Plus-4f107e212611c512 eth0 E/dhcpcd ( 1298): disable closefrom(), else no log output D/dhcpcd ( 1298): read global config/options from file /system/etc/dhcpcd/dhcpcd.conf I/dhcpcd ( 1298): ARP | GATEWAY | IPV4LL | DAEMONISE | LINK | IPV6RS | D/dhcpcd ( 1298): Add options from command line I/dhcpcd ( 1298): GATEWAY | HOSTNAME | IPV6RS | I/dhcpcd ( 1298): version 5.5.6 starting <div>.....</div><div>I/dhcpcd ( 1298): eth0: Router Advertisement from fe80::cd2:d5a:f02f:351c D/dhcpcd ( 1298): eth0: executing `/system/etc/dhcpcd/dhcpcd-run-hooks', reason ROUTERADVERT I/dhcpcd ( 1298): eth0: fe80::cd2:d5a:f02f:351c: expired Router Advertisement D/dhcpcd ( 1298): eth0: executing `/system/etc/dhcpcd/dhcpcd-run-hooks', reason ROUTERADVERT</div><div>"</div><div>But with my kdbus patch , logcat related to ethernet are only one line</div><div> "I/ethernet( 559): Loading ethernet jni class" </div><div>which doesn't occur when the system can get ip. </div><div><br></div><div>I also attach the two logcat files , which are clear by their file names.</div><div>(Note: I've abbreviated the logcat files by removing <span style="color: rgb(50, 50, 50); white-space: nowrap; font-family: Arial, 宋体, 微软雅黑; line-height: 16px;">irrelative lines, otherwise they are too large to be accepted</span><span style="line-height: 1.7;"> )</span></div><div><br></div><div>Thanks!</div><div>Li Cheng </div>>... > >Please try to paste as much information as possible. Otherwise, it's >really a hassle to ask for each piece of information separately. > >Thanks >David </pre></div><br><br><span title="neteasefooter"><span id="netease_mail_footer"></span></span></div><br><br><span title="neteasefooter"><span id="netease_mail_footer"></span></span></div><br><br><span title="neteasefooter"><span id="netease_mail_footer"></span></span>