On Sat, May 24, 2008 at 01:35:41PM +0200, Thomas Kunze wrote: > Some logs: Thanks! > hostap_cs: Registered netdevice wifi0 > Unable to handle kernel NULL pointer dereference at virtual address 00000028 > pgd = c0004000 > [00000028] *pgd=00000000 > PC is at prism2_interrupt+0x64/0x8ec It does indeed look like the interrupt handler is not prepared for something at this point. However, I cannot reproduce this in my tests on x86 for some reason.. I have even test code that ends up calling the interrupt handler at the point when it is registered, i.e., when a real interrupt could actually hit it. prism2_interrupt does not crash in this case and I see no problems there. The interrupt handler is installed only after the data structures have been initialized, so the pointers should be valid at this point. Unfortunately, I do not have an ARM-based system for testing something closer to your configuration. It would be useful to figure out what exactly is NULL in the case where this crash happens. Based on that PC location, I would assume it is something that is being used close to the beginning of prism2_interrupt(), but since I don't have the object file used here, I cannot be sure. I would appreciate it if you could either take a look at the hostap_cs code and see if you can find this location or alternatively add some printk calls in the beginning of prism2_interrupt() to figure out which pointer is NULL. -- Jouni Malinen PGP id EFC895FA -- 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
