On Mon, 21 Mar 2011 23:40:56 +0800 wu zhangjin <wuzhang...@gmail.com> wrote: > Thanks very much, can you tell me the steps of reproducing this problem?
What I have found so far: - It is not related to X.org or siliconmotion, because it also occured without X.org running. - It is not related to a specific kernel version: occurs on 2.6.37 from and 2.6.38 from anheng.com.cn, also on 2.6.32, 2.6.37 and 2.6.38 from linux-libre (I did not test 2.6.32 extensively, however it did lock up once in the same way on it). - I suspect it may be related to the use of built-in rtl8187b wifi (with WPA2 AES), or perhaps to a high interrupt rate in general, since according to 'powertop' the rtl8187b generates more than 5000 interrupts/sec to transmit at 1.2 MByte/sec. I have ran the system for quite some time on a wired connection with no wifi usage, and had no lock-ups. However given their erratic nature, it may be too early to say for sure. > On my YeeLoong laptop, 2.6.38 runs well without any problem(30 minutes > now, and I think Shiwei may have used it for several hours). The > kernel config I used is arch/mips/configs/lemote2f_defconfig, and > please ensure the right compiler and binutils (>2.21?) are used to > compile the kernel. Please make sure BFS scheduler is disabled for it > is not stable. I am not sure which binutils are used for compiling the above-mentioned kernels, but for my own test kernels I used "binutils-mipsel-linux-gnu 2.20.1-16" (and those locked up too). I do not use BFS. > And also, please take notice of the nop problem we have mentioned in > the home page[1] of linux-loongson-community project. If you know the > software which is specific to your system hang, then, fix its nops at > first(with the fix-nop tool from [1]). My distro seems to be compiled without the NOP fix (it is the stock Debian Wheezy). However it is hard to pinpoint the lock-up to the exact binary to apply the fix-nop, if anything, it might be something basic like glibc. If I will not find the exact cause of lock-ups, I plan to try a whole different distribution on this device, e.g. Gentoo for n32, or Parabola GNU/Linux, which I suppose will have all the included software compiled with the NOP fix. > And what's the version of your PMON and EC(cat /proc/cmdline) and > which external devices are you using? # cat /proc/cmdline console=tty no_auto_cmd root=/dev/sda2 PMON_VER=LM8089-1.4.9 EC_VER=PQ1D28 machtype=lemote-yeeloong-2f-8.9inches I use no external devices; the Yeeloong is always plugged into the power supply that came with it, I didn't test much while running from battery. -- With respect, Roman
signature.asc
Description: PGP signature
