Menu
▾
▴
Re: [tipc-discussion] Kernel Panic on insmod of tipc.ko (tipc_lin ux)
|
From: Jon M. <jon...@er...> - 2005-04-06 19:03:56
|
Hi, I just uploaded a tipc-linux-1.5.01 where a number of issues are corrected. It is still based on the "unstable" branch, but is probably just as stable as the stable line, and executes well on 2.6.10 with all flags set. I think this should be the better base for your evaluation. Regards /jon Beese Zachary-QA6374 wrote: > Thanks for the quick reply! > > From what you said, here's what I'll try now: > I'll grab kernel source for 2.6.8 and build it w/o any of the DEBUG_ > flags. > I'll boot into 2.6.8, and then I'll build the latest TIPC on sourceforge > against that 2.6.8 and see if insmod works a bit better :-) > > --Zach > > > -----Original Message----- > From: tip...@li... > [mailto:tip...@li...] On Behalf Of Jon > Maloy > Sent: Monday, March 28, 2005 4:51 PM > To: Beese Zachary-QA6374 > Cc: tip...@li...; Siebenberg Steve-QA2962 > Subject: Re: [tipc-discussion] Kernel Panic on insmod of tipc.ko > (tipc_linux) > > > Hi, > There is a known issue, which has been solved in the unstable branch > (only in CVS), but > not yet in the stable one, since I never heard about anybody running > into this > problem. If your kernel is compiled with some DEBUG_-flags (I haven't > found > out exactly which one trigged the problem, since I had several of them > set I when > I ran into the problem), kmalloc() starts to behave differently; It > consistently refuses > to allocate the 64k block of memory to be used for the port registry. > (See reg.c, line > 139 and line 161) . When I replaced kmalloc/kfree with vmalloc/vfree > (and removed > the locks around vfree()) everything worked fine. > Also, I just discovered that if you activate an interface on 2.6.10, and > do rmmod on > tipc, we have a kernel crash (or deadlock). This worked well on 2.6.8, > so something has > obviously changed in the kernel between these versions. If you need to > test inter-processor > communication, use the older kernel, or don't do rmmod, until I have > found out what it is. > > Regards /jon > > > Beese Zachary-QA6374 wrote: > > > Hi, > > > > I just joined the list. I'm evaluating using TIPC for some things at > > Motorola, to try it out I decided to put Linux on my laptop (PIII) and > > build/insmod TIPC. I've tried various 2.6 kernels .7 .9 .10; each > > time I rebuild TIPC (pointing to the correct KINCLUDE dir). When I > > try to insmod tipc.ko, I always get a kernel panic. This happens for > > different versions > > of TIPC and different 2.6 kernels. I must be doing something > wrong! Any > > ideas? > > > > Here's some output I copied from my dead laptop (retyped into this > > email on > > a different computer). This kernel panic was from 2.6.10 with the > latest > > tipc_linux: > > > > > > EIP: 0060 [<e0a5649a>] Tainted: GF VLI > > EFLAGS: 00010246 (2.6.10-prep) > > EIP is at ref_table_init+0x4a/0x190 [tipc] > > eax: 00000000 ebx: c88490000 ecx: 00040000 edx: c03a541c > > esi: 00000001 edi: 00000083 ebp: c8849f6c esp: c8849f34 > > ds: 007b es: 007b ss: 0068 > > Process insmod (pid: 17750, threadinfo=c8849000 task=d7da59b0) > > > > Stack: 00040000 00000220 00002000 00008246 00000286 e8a6a5a4 c8849000 > > e0a6a300 > > 00000083 c8849f6c e0a33d70 c8849000 e0a6a300 00000083 c8849f7c > > e0a57a2a > > 00001fff 0ca1d699 c8849f8c e0a5b2a5 e0a6a0e0 00000004 c8849fbc > > c014a812 > > > > Call Trace: > > [<c0104d6f>] show_stack+0x7f/0xa0 > > [<c0104f06>] show_registers+0x156/0x1d0 > > [<c010522c>] die+0x1ec/0x300 > > [<c011b49e>] do_page_fault+0x35e/0x6c9 > > [<c0104893>] error_code+0x2b/0x30 > > [<e0a57a2a>] tipc_start_node+0x3a/0x80 [tipc] > > [<e0a5b2a5>] start_node+0x25/0x50 [tipc] > > [<c014a812>] sys_init_module+0x282/0x400 > > [<c0103e7f>] syscall_call+0x7/0xb > > > > Code: f0 ff ff 21 e0 8a 40 14 00 01 00 00 ff 40 14 8b 45 d0 b9 20 02 > > 00 00 > > be 01 00 00 00 89 4c 24 04 c1 e0 05 89 04 24 e8 f6 a4 70 df <c7> 00 00 > > 00 00 > > 00 89 c1 c7 45 d8 00 00 00 00 c7 45 dc 0a 00 00 <0>Kernel panic - not > > syncing: Fatal exception in interrupt > > > > > > --Zach > > Zac...@mo... > > > > > > ------------------------------------------------------- > > SF email is sponsored by - The IT Product Guide > > Read honest & candid reviews on hundreds of IT Products from real > > users. Discover which products truly live up to the hype. Start > > reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > <http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click> > > <http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > <http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click>> > > _______________________________________________ > > tipc-discussion mailing list tip...@li... > > https://lists.sourceforge.net/lists/listinfo/tipc-discussion > > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > <http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click> > _______________________________________________ > tipc-discussion mailing list > tip...@li... > https://lists.sourceforge.net/lists/listinfo/tipc-discussion > |
