On Tue, 22 Mar 2011 22:47:11 +0800 wu zhangjin <wuzhang...@gmail.com> wrote:
> To get the kernel log, you can use SysRq and netconsole together, the > kernel log will be sent out to another machine, then, you can access > it. another potential debugging method is kexec+kdump, but currently, > kdump doesn't work for Loongson. Thank you, I will look into setting up netconsole. > Before the system hang, did you find any weird kernel log? for > example, Call Trace? Before it hang I did not check dmesg, also I was in X.org, and after the hang could not switch by the SysRq keys from a frozen X.org graphical screen to a text console to see any messages. > Where did you get your source code? > http://dev.lemote.com/code/linux-loongson-community? or another place? I tried both the kernels and kernel sources taken from these repositories: http://www.anheng.com.cn/loongson2f/wheezy/kernel/ http://www.fsfla.org/download/linux-libre/lemote/gnewsense/pool/ I suppose they are based on the linux-loongson-community. > Please note, all of my replies are based on the source code from > http://dev.lemote.com/code/linux-loongson-community, and with the > mainline 2.6.38 or 2.6.37, rtl8187b doesn't work and it may crash the > whole kernel. the known problem is a mainline update, I just reverted > that update and didn't look into it. Please get more from this commit: > http://dev.lemote.com/cgit/linux-loongson-community.git/commit/?id=edd2adaaac2cbe6d4f27ccc79c91284e3fdbae40 Thanks. -- With respect, Roman
signature.asc
Description: PGP signature
