Messages in this thread | | | Subject | Re: Clue on 2.0.33 crashes | From | Camm Maguire <> | Date | 23 Feb 1998 10:10:45 -0500 |
| |
Greetings, and thanks for your work on xntpd! I think my message started this thread. Briefly, xntpd *works just fine here* under 2.0.33, except for when a modem poll to the NIST time server is made *and* the xntpd daemon is run with -d flags. Then, the console freezes, and all network connections to the machine cease to function, but routed connections through the machine continue. The kernel gets stuck in a loop.
Without the -d flags, xntpd dies at the same point with signal 1 (HANGUP). So 1) there seems to be some problem with xntpd in accessing NIST and the proper handling of its time data, and 2) there seems to be a problem in the kernel such that when a process attached to the console get signal 1, the machine hangs. This is entirely reproducible.
Any suggestions would be most appreciated! -- Camm Maguire camm@enhanced.com ========================================================================== "The earth is but one country, and mankind its citizens." -- Baha'u'llah
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |