Just mention it, Peter wrote a patch(<a href="https://groups.google.com/d/msg/linux-kernel-proxy/-eAPuf_OcmI/mD81JdSzxckJ">https://groups.google.com/d/msg/linux-kernel-proxy/-eAPuf_OcmI/mD81JdSzxckJ</a>), and it works for me.<br> <br><div class="gmail_quote">2010/12/23 <a href="mailto:fykcee1@gmail.com">fykcee1@gmail.com</a> <span dir="ltr"><<a href="mailto:fykcee1@gmail.com">fykcee1@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> Hi all,<div><br></div><div>I encountered kernel panic with systemd too, but not sure is related with this thread. The Call Trace mentions pick_next_task_fair: <a href="http://dev.lemote.com/files/upload/people/%7Echenj/systemd-crash/DSC00163.JPG" target="_blank">http://dev.lemote.com/files/upload/people/~chenj/systemd-crash/DSC00163.JPG</a></div> <div><br></div><div><a href="http://dev.lemote.com/files/upload/people/%7Echenj/systemd-crash/DSC00163.JPG" target="_blank"></a>It was a debian sequeeze installed a vanilla kernel 2.6.36.2 and systemd (v15 with sysv-compat disabled), running on Fuloong 2f box(<a href="http://www.linux-mips.org/wiki/Fuloong" target="_blank">http://www.linux-mips.org/wiki/Fuloong</a>). When start up finished, I pressed a key, then kernel panic. It was not produceable each time.</div> <div><br></div><div>----</div><div>config: <a href="http://dev.lemote.com/files/upload/people/%7Echenj/systemd-crash/config-2.6.36.2" target="_blank">http://dev.lemote.com/files/upload/people/~chenj/systemd-crash/config-2.6.36.2</a></div> <div> systemd-debs: <a href="http://dev.lemote.com/files/upload/people/%7Echenj/systemd-crash/debs/" target="_blank">http://dev.lemote.com/files/upload/people/~chenj/systemd-crash/debs/</a></div><div>Howto deploy systemd on debian: <a href="http://dev.lemote.com/files/upload/people/%7Echenj/systemd-crash/README" target="_blank">http://dev.lemote.com/files/upload/people/~chenj/systemd-crash/README</a></div> <div><br><br><div class="gmail_quote">2010/12/22 Mike Galbraith <span dir="ltr"><<a href="mailto:efault@gmx.de" target="_blank">efault@gmx.de</a>></span><div><div></div><div class="h5"><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <div>On Wed, 2010-12-22 at 09:29 +0100, Peter Zijlstra wrote:<br> > On Wed, 2010-12-22 at 01:22 +0100, Miklos Vajna wrote:<br> > > Please let me know if you need more info.<br> ><br> > What distro are you using? it looks like systemd is involved and I'm<br> > actively avoiding anything using that crap.<br> <br> </div>Heh, gearing up to hunt a bug it triggers, just doing all I had to do to<br> get the thing built and installed blew my box _all up_. I still have<br> smoldering bits lying about a week later.<br> <font color="#888888"><br> -Mike<br> </font><div><div></div><div><br> _______________________________________________<br> systemd-devel mailing list<br> <a href="mailto:systemd-devel@lists.freedesktop.org" target="_blank">systemd-devel@lists.freedesktop.org</a><br> <a href="http://lists.freedesktop.org/mailman/listinfo/systemd-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/systemd-devel</a><br> </div></div></blockquote></div></div></div><br></div><br clear="all"><br>-- <br>Regards,<div><br><div>- cee1</div></div><br> </blockquote></div><br><br clear="all"><br>-- <br>Regards,<div><br><div>- cee1</div></div><br>