Re: [loongson-dev] Yeeloong lock-ups

2011-03-22 Thread wu zhangjin
Hi, > > I have switched my network from WPA2 AES to WPA1 TKIP, and managed to run > the > machine for a much longer period before the lock-up. > > Now it locked up -- and for the first time, not completely dead, but with > the > leftmost LED above the keyboard flashing! Is it possible to obtain de

Re: [loongson-dev] Yeeloong lock-ups

2011-03-22 Thread Roman Mamedov
On Tue, 22 Mar 2011 22:47:11 +0800 wu zhangjin 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 Loo

Re: [loongson-dev] Yeeloong lock-ups

2011-03-22 Thread wu zhangjin
> >> 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. > I mea

Re: [loongson-dev] Yeeloong lock-ups

2011-03-22 Thread Roman Mamedov
On Tue, 22 Mar 2011 23:50:07 +0800 wu zhangjin wrote: > > > >> 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.