"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 <andrey@xxxxxxxxxxx>: > 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 <keirlawson@xxxxxxxxx> 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 <andrey@xxxxxxxxxxx>: >>> 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 <keirlawson@xxxxxxxxx> 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@xxxxxxxxxxxxxxx >>>> More majordomo info at http://vger.kernel.org/majordomo-info.html >>>> >>> >> > -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
