Return-path: Received: from fg-out-1718.google.com ([72.14.220.154]:49901 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754551AbZA1Ryi (ORCPT ); Wed, 28 Jan 2009 12:54:38 -0500 Received: by fg-out-1718.google.com with SMTP id 13so639386fge.17 for ; Wed, 28 Jan 2009 09:54:35 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <45e8e6c40901231106t481c823ag3bbac67d8205ef7a@mail.gmail.com> <45e8e6c40901240956g68a5364tdbacc1e49410c9cc@mail.gmail.com> Date: Wed, 28 Jan 2009 09:54:35 -0800 Message-ID: <45e8e6c40901280954l42bbe788y8723141d673bb7b3@mail.gmail.com> (sfid-20090128_185457_325229_F0491ADE) Subject: Re: Crashing on ping? From: Andrey Yurovsky To: Keir Cc: linux-wireless@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: Hi Keir. If the system really crashes, you should have some output. Can you please set: echo 8 > /proc/sys/kernel/printk ...and use your serial console and try to reproduce this? Thanks, -Andrey On Mon, Jan 26, 2009 at 9:56 AM, Keir wrote: > Right, managed to set up a serial terminal, ran cat /proc/kmsg, but > still no output of interest (just mesh plink stuff leading up to the > connection being established), what should I do next? > > Cheers > > Keir > > 2009/1/26 Keir : >> "sudo cat /proc/kmsg > log" doesnt produce anything of interest. >> >> Will look into the serial console thing, never done it before. >> >> Keir >> >> 2009/1/24 Andrey Yurovsky : >>> Can you post logs of the crash (dmesg output)? You may need to >>> connect a serial console to the PC in question to get them if the >>> machine is really hard-locking, otherwise see if you can capture the >>> output of dmesg >>> >>> On Sat, Jan 24, 2009 at 8:04 AM, Keir wrote: >>>> Tried that commit, still no luck :( It consistently freezes up on >>>> ping, though sometimes it's the machine doing the pining, and other >>>> times it's the machine being pinged. Wondering what I can do to help >>>> debug this? >>>> >>>> Keir >>>> >>>> 2009/1/23 Andrey Yurovsky : >>>>> Hi Keir. Incidentally, we're using ath5k mesh right now at commit >>>>> 93bd2ac7301b0879821e584991f82de372d62bf6 (that's just after the >>>>> 2.6.29-rc1 tag but before -rc2) an things work fine. I haven't had a >>>>> chance to try head of wireless-testing this week. >>>>> >>>>> -Andrey >>>>> >>>>> On Fri, Jan 23, 2009 at 8:03 AM, Keir wrote: >>>>>> I just pulled the latest wireless-testing kernel, however, much like >>>>>> the previous wireless-testing kernel I was working on, when attempting >>>>>> to ping one node from another on a mesh, using ath5k, the node >>>>>> attempting to ping completely freezes after about 7 pings are >>>>>> (succesfully) sent. Anyone have any idea what is going wrong here? >>>>>> >>>>>> Cheers >>>>>> >>>>>> Keir >>>>>> -- >>>>>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in >>>>>> the body of a message to majordomo@vger.kernel.org >>>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html >>>>>> >>>>> >>>> >>> >> >