From: Samuel O. <sa...@so...> - 2006-09-14 01:45:20
|
Hi Alan, On Wed, Sep 13, 2006 at 09:15:48PM +0100, Alan J. McFarlane wrote: > In article news:200...@so..., Samuel Ortiz wrote: > > On Tue, Sep 12, 2006 at 10:58:36PM +0000, surfzoid surfzoid wrote: > >> [root@surfzoidPC eric]# > >> with the mitsubishi : > >> [root@surfzoidPC eric]# obexftp -i -l / > >> Connecting...done > >> Receiving "/"... Sending ""... failed: / > >> failed: / > >> Disconnecting...done > > Oh, that's different. It's not only irdadump that's crashing, but also > > obexftp... > > Ok, so please do the following: > > 1) As root: "echo 5 > /proc/sys/net/irda/debug". > > 2) run "obexftp -i -l /" with your Mitsubishi phone. > > 3) send us the full output of the "dmesg" command. > > > It may or may not be useful, and I don't want to interfere with the > investigation that is ongoing, but I'd like to see the raw bytes in the > frames. :-) Human parsing of the frame may show some oddity that's > causing the fault... Makes a lot of sense. Getting the kernel debugs would also give use some useful information, but parsing the raw frames manually is definitely a good idea, if irdadump doesn't crash before being able to dump the frame. Let see... Cheers, Samuel. |