From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Roskin Date: Wed, 17 Feb 2010 12:47:08 -0500 Subject: [ath9k-devel] AR5008 hanging computer In-Reply-To: <167ae39b1002161554k6769c7a4v21c3782c03126476@mail.gmail.com> References: <824572.10530.qm@web57904.mail.re3.yahoo.com> <1266217402.28738.19.camel@mj> <167ae39b1002152030s170128a0j362e7e9c61a4af42@mail.gmail.com> <1266296860.17808.2.camel@mj> <167ae39b1002161554k6769c7a4v21c3782c03126476@mail.gmail.com> Message-ID: <1266428828.9050.13.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 Tue, 2010-02-16 at 17:54 -0600, James Grossmann wrote: > I would just like to get some ideas of what I can debug to get some > answers. Out of curiosity, is there a way to do a continuous > recording of dmesg to a serial console? These hangs occur regularly, > but very unpredictably and at fairly long intervals. What's really needed is what happens immediately before the hang, so the history is not really interesting. I would try to enable more debugging options in the kernel. It could help detect the problem earlier if it's a software problem, such as memory corruption. -- Regards, Pavel Roskin