Jiri Slaby <[EMAIL PROTECTED]> writes: >> Jiri Slaby <[EMAIL PROTECTED]> writes: >> >> > Could you test the patch below, if something changes? >> >> Just tested with low_latency commented out. Still oopses: >> >> BUG: unable to handle kernel NULL pointer dereference at virtual address >> 00000008 >> printing eip: >> f8f1730f >> *pde = 00000000 >> Oops: 0000 [#1] >> SMP >> Modules linked in: ... >> CPU: 0 >> EIP: 0060:[<f8f1730f>] Tainted: P VLI >> EFLAGS: 00010046 (2.6.18-3-686 #1) >> EIP is at mxser_receive_chars+0x21b/0x249 [mxser_new] > > Yes, port->tty still somewhere becomes NULL -- does this patch help?
Hi, Jiri! I'm so sorry, I don't know what I smoked yesterday, but the latest version you've sent me does not have this problem anymore! I think I copied compiled module to modules directory for different kernel and thus tested old code all the time. BTW, should you tell me that the ports are now called /dev/ttyMIx instead of /dev/ttyMx, I think I'd notice my mistake earlier. Yes, in fact I didn't test any version where ports are called /dev/ttyMIx until now! In particular, it means that maybe some of the recent changes you've made yesterday based on my wrong reports are not in fact required. Anyway, the only mxser-specific problem that currently remains for me and that I didn't see before, is the following: # rmmod mxser_new Trying to free already-free IRQ 58 Trying to free nonexistent resource <0000000000009000-000000000000903f> Trying to free nonexistent resource <0000000000008800-0000000000008800> # -- Sergei. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/