I managed to follow, with a number of debug statements, a problem that appears to be in parport_pc that causes the following lockup on a dual P3 500 with modprobe: NMI Watchdog detected LOCKUP on CPU0, registers: CPU: 0 EIP: 0010:[<c01deec3>] EFLAGS: 00000086 eax: 00000301 ebx: 00000216 ecx: 00000001 edx: 000816a1 esi: 00000301 edi: 0000000c ebp: 00034a4e esp: df91fe98 ds: 0018 es: 0018 ss: 0018 Process modprobe (pid: 79, stackpage=df91f000) Stack: df8f3f20 00000001 c0162cea 00000301 df8f3f20 00000000 00000000 df91ff0c c0162ea1 00000000 df8f3f20 df8f3f20 00000004 0000000a 00000400 c0134492 00000000 00000004 df91ff0c c196ea04 c18620e0 df9b385c 00000000 00001000 Call Trace: [<c0162cea>] [<c0162ea1>] [<c0134492>] [<c012dd73>] [<c01527d3>] [<c 0152108>] [<c0125f96>] [<c012628f>] [<c01261e0>] [<c0131827>] [<c010abf7>] [<c01e002b>] Code: 80 3d 64 4d 22 c0 00 f3 90 7e f5 e9 e6 31 f8 ff 80 3d ac f6 console shuts up ... I don't if this is specifically a problem in the module or with modprobe (2.3.17), but it doesn't happen with any other module. Unfortunately parport_pc.c was as far as I traced before my work life sucked me back in. If more information is needed, please tell me what you need and I'll try to provide it. John - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/