From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Roskin Date: Fri, 12 Feb 2010 17:53:28 -0500 Subject: [ath9k-devel] AR5008 hanging computer In-Reply-To: <167ae39b1002120725i6e518c27r8016e89bf372bce9@mail.gmail.com> References: <167ae39b1002120725i6e518c27r8016e89bf372bce9@mail.gmail.com> Message-ID: <1266015208.25535.18.camel@mj> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org 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