I did the following in my serial console: root@kyp:/home/keir/Desktop/iw-0.9.6# echo 8 > /proc/sys/kernel/printk root@kyp:/home/keir/Desktop/iw-0.9.6# ping -I mesh0 10.0.0.2 PING 10.0.0.2 (10.0.0.2) from 10.0.0.3 mesh0: 56(84) bytes of data. 64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=2.67 ms 64 bytes from 10.0.0.2: icmp_seq=2 ttl=64 time=0.550 ms 64 bytes from 10.0.0.2: icmp_seq=3 ttl=64 time=0.445 ms 64 bytes from 10.0.0.2: icmp_seq=4 ttl=64 time=6.28 ms 64 bytes from 10.0.0.2: icmp_seq=5 ttl=64 time=2.19 ms At which point the console freezes with no further output. Any ideas? Cheers Keir 2009/1/28 Andrey Yurovsky <andrey@xxxxxxxxxxx> > > 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 <keirlawson@xxxxxxxxx> 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 <keirlawson@xxxxxxxxx>: > >> "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
