Hello Charly On Thu, 2010-07-29 at 12:25 +0800, Charly Liu wrote: > Hi, > > I have a intel 6250 and I wanted to patch the kernel 2.6.32.1 to use it. I > don't really know which files I have to patch to make it work. I don't want to > use the kernel 2.6.35. Just want to patch the necessary files. Not very advisable ... it is possible, but you have to know what you are doing. I lack the time to support these things ... > I tried the attached patch but I encountered the problem that after loading > wimax, i2400m and i2400m-usb the callstack.log says: So this is the user space daemon who is failing, not the kernel Which version are you using? Which distribution and architecture? > ---------------------------- callstack.log --------------------------- > > Thu Jul 29 11:44:24 GMT 2010 > ================================================================================== > If Faulty address is in wimaxd excution segment > Use addr2line to decode the address info into file name and line no > For Example > $> sudo addr2line -e /usr/bin/wimaxd 806f5fe > If Faulty address is in shared object file > $> sudo objdump -l -d -M intel /usr/lib/libWmxInstrument.so.0 > > ./libinstru_dis > Use the function name and offset to function and search file above for the line > no > ================================================================================== > > Got signal 11, faulty address is (nil), from (nil) > [bt] Execution path: > [bt] [(nil)] > [bt] [0xffffe40c] > [bt] /usr/lib/libdl.so.2(dlopen+0x41) [0xb77b5da1] > [bt] /usr/bin/wimaxd(OSAL_load_lib+0x25) [0x80f2f12] > [bt] /usr/bin/wimaxd(LoadInstrumentationModule+0x59) [0x807a3f9] > [bt] /usr/bin/wimaxd(Act_Start+0x223) [0x806f42e] > [bt] /usr/bin/wimaxd(Act_FullRestart+0xd4) [0x807052d] > [bt] /usr/bin/wimaxd(Act_HandlingThreadFunc+0x257) [0x806ec8a] > [bt] /lib/libpthread.so.0 [0xb77bdfda] > [bt] /lib/libc.so.6(clone+0x5e) [0xb774193e] could you disable the instrumentation module in /etc/wimax/config.xml? <EnableInstrumentation>0</EnableInstrumentation> I don't know how did it enable in the first place, it shouldn't :) If the daemon isn't throwing a core dump, try to get one: $ ulimit -c unlimited $ wimaxd -i wmx0 -d blah blah crashes and writes a core dump $ gdb /usr/sbin/wimaxd corefile gdb> i s if you built the daemon in your machine, it will provide a clean dump with C files and line numbers. Please send that. Thank you!
