Messages in this thread |  | | Date | Thu, 28 Sep 2000 12:55:04 +0200 | From | Petr Vandrovec <> | Subject | Re: OOPS on booting 2.4.0-test9pre7 during Novell server mounting |
| |
> Petr! > I think, it's you topic
Unfortunately, it is not. ipx is maintained by Jay Schulist, jschlst@turbolinux.com. I tried to do some changes in ipx year ago (removing kernel lock), but after I saw ipx interface autocreation from incoming packet notification routine, I gave up (not that it works now, when it is guarded by big kernel lock ;-) )
> Sep 28 11:48:39 sh kernel: Unable to handle kernel NULL pointer > dereference at virtual address 00000019 Sep 28 11:48:39 sh kernel: > printing eip: Sep 28 11:48:39 sh kernel: c01d5a40 > Sep 28 11:48:39 sh kernel: *pde = 00000000 > Sep 28 11:48:39 sh kernel: Oops: 0000 > Sep 28 11:48:39 sh kernel: CPU: 0 > Sep 28 11:48:39 sh kernel: EIP: 0010:[ipx_remove_socket+24/80] > Sep 28 11:48:39 sh kernel: EFLAGS: 00010002 > Sep 28 11:48:39 sh kernel: eax: c01d7601 ebx: 00000202 ecx: 00000001 edx: c88f5078 > Sep 28 11:48:39 sh kernel: esi: c88f5040 edi: c885c9a0 ebp: c83f2c40 esp: c8367f34
ecx contains sk->protinfo.af_ipx.intrfc. It is pointer. It contains 1...
I have no idea how it can happen, except... did not you change kernel configuration between compilation of kernel and modules? I can't think any reason except that you changed one of CONFIG_IPV6, CONFIG_INET, CONFIG_SPX or CONFIG_FILTER during compile.
Sorry, but I do not have better news for you... Best regards, Petr Vandrovec vandrove@vc.cvut.cz
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |