I was hoping you could provide possible debug options I could look at, with all the debug options on, I was filling dmesg's buffer in less than 1 sec, not enough time to catch it when it stopped and I had to intervene. Kubuntu 9.10 is using the ubuntu 2.6.31-19-generic and the 2.6.31-20-generic kernels. Thanks! James
On Fri, Feb 12, 2010 at 4:53 PM, Pavel Roskin <[email protected]> wrote: > On Fri, 2010-02-12 at 09:25 -0600, James Grossmann wrote: >> I have a linksys wpc100, which contains the ar5008 chipset. After a >> little while of use, It hangs the computer so that almost nothing >> responds. I have found that if I hold the power button down until >> just before it would force a poweroff, I can usually get it to >> respond. I have it installed in a thinkpad x24 (pentium III, so >> there's no multi-core/processor), and using ndiswrapper when I'm not >> trying to overcome this problem. I have also had the same problem >> when I had it installed in a t23, a very similar pentium III laptop. >> I am running kubuntu 9.10 with the backports modules installed, I know >> they aren't the newest, but I've tried the >> I have followed the instructions to debug the problem, but I could use >> some more specific ideas of what to debug, because with all debug >> options on, over a couple of days, I produced a 1.2 gb debug file. > > I suggest that you give the exact kernel version, as a courtesy to those > not running kubuntu 9.10. > >> In >> perusing the file, I found a few anomalies that were obvious to the >> casual observer...me, but which may or may not tell us anything, I >> will post them below. I also note that there seems to be a lot of >> authenticating/deauthenticating going on, although that could have >> been from the ndiswrapper driver. > > You can use "dmesg -c" to erase the kernel log. > >> Feb 8 13:00:04 Pneuma kernel: [ 5223.147647] ath9k: new IMR 0x918414b4 > > Getting kernel log from /var/log is not a good idea. Please use the > dmesg command. > > You can use less debug options to get something of manageable size. You > can use sed to remove the timestamps (I don't think they are very useful > for this particular problem) and use lzma to compress the log: > > dmesg | sed 's/^[^]]*] //' | lzma >kernel.log.lzma > > -- > Regards, > Pavel Roskin > _______________________________________________ ath9k-devel mailing list [email protected] https://lists.ath9k.org/mailman/listinfo/ath9k-devel
