Bug 16515

Summary: Deadlock by ntpd
Product: Base System Reporter: dateck <dateck>
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.0-CURRENT   
Hardware: Any   
OS: Any   

Description dateck 2000-02-06 14:10:01 UTC
The computer totaly deadlocks, after the deadlock only the reset and the powerbutton works. The computer does not react to any other input from mouse, keyboard, or network.
The program that induces the deadlock is ntpd, and it have been like this since
beginning of january.

Fix: 

Kill ntpd process.
How-To-Repeat: 
Just run ntpd, everytime it deadlocks my computer after a random time.

My ntp parameters: -p /var/run/xntpd.pid

ntp.conf
server lunic.luth.se prefer
server eru.mt.luth.se
server news.luth.se
server samson.dc.luth.se


I hope i got all the info in here.
Comment 1 Szilveszter Adam 2000-02-06 14:34:10 UTC
Hi!

Are you sure you have the POSIX stuff in your kernel enabled? This looks
like it...

On Sun, Feb 06, 2000 at 03:05:32PM +0100, dateck@cyberspace.campus.luth.se wrote:
> 
> >Number:         16515
> >Category:       kern
> >Synopsis:       Deadlock by ntpd
> >Confidential:   no
> >Severity:       serious
> >Priority:       high
> >Responsible:    freebsd-bugs
> >State:          open
> >Quarter:        
> >Keywords:       
> >Date-Required:
> >Class:          sw-bug
> >Submitter-Id:   current-users
> >Arrival-Date:   Sun Feb  6 06:10:01 PST 2000
> >Closed-Date:
> >Last-Modified:
> >Originator:     Tomas Klockar
> >Release:        FreeBSD 4.0-CURRENT i386
> >Organization:
> Student at University of Luleå
> >Environment:
> 
> Here is the dmesg info from my computer.
> 
> avail memory = 159092736 (155364K bytes)
> Preloaded elf kernel "kernel" at 0xc033f000.
> npx0: <math processor> on motherboard
> npx0: INT 16 interface
> pcib0: <Host to PCI bridge> on motherboard
> pci0: <PCI bus> on pcib0
> isab0: <Intel 82371AB PCI to ISA bridge> at device 7.0 on pci0
> isa0: <ISA bus> on isab0
> ata-pci0: <Intel PIIX4 ATA-33 controller> port 0xf000-0xf00f at device 7.1 on pci0
> ata0 at 0x01f0 irq 14 on ata-pci0
> ata1 at 0x0170 irq 15 on ata-pci0
> pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2
> chip1: <Intel 82371AB Power management controller> port 0x5f00-0x5f0f at device 7.3 on pci0
> vr0: <VIA VT3043 Rhine I 10/100BaseTX> port 0x6800-0x687f mem 0xe3120000-0xe312007f irq 9 at device 9.0 on pci0
> vr0: Ethernet address: 00:80:c8:eb:a1:65
> miibus0: <MII bus> on vr0
> amphy0: <DM9101 10/100 media interface> on miibus0
> amphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> vr0: supplying EUI64: 00:80:c8:ff:fe:eb:a1:65
> vga-pci0: <VGA-compatible display device> mem 0xe2000000-0xe27fffff,0xe2800000-0xe2ffffff,0xe3100000-0xe311ffff irq 9 at device 10.0 on pci0
> pci0: unknown card (vendor=0x1105, dev=0x8300) at 11.0 irq 9
> ncr0: <ncr 53c810a fast10 scsi> port 0x6c00-0x6cff mem 0xe3121000-0xe31210ff irq 10 at device 12.0 on pci0
> ncr0: driver is using old-style compatability shims
> isa0: unexpected tag 14
> fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
> fdc0: FIFO enabled, 8 bytes threshold
> fd0: <1440-KB 3.5" drive> on fdc0 drive 0
> ata-isa0: already registered as ata0
> ata-isa1: already registered as ata1
> atkbdc0: <keyboard controller (i8042)> at port 0x60-0x6f on isa0
> atkbd0: <AT Keyboard> irq 1 on atkbdc0
> psm0: <PS/2 Mouse> irq 12 on atkbdc0
> psm0: model Generic PS/2 mouse, device ID 0
> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
> sc0: <System console> on isa0
> sc0: VGA <16 virtual consoles, flags=0x200>
> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
> sio0: type 16550A
> sio1 at port 0x2f8-0x2ff irq 3 on isa0
> sio1: type 16550A
> sio2: not probed (disabled)
> sio3: not probed (disabled)
> ppc0: <Parallel port> at port 0x378-0x37f irq 7 flags 0x40 on isa0
> ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
> ppc0: FIFO with 16/16/15 bytes threshold
> ppi0: <Parallel I/O> on ppbus0
> lpt0: <Printer> on ppbus0
> lpt0: Interrupt-driven port
> plip0: <PLIP network interface> on ppbus0
> ep0: not probed (disabled)
> joy0 at port 0x201 on isa0
> gusc0: <Gravis UltraSound Plug & Play PCM> at port 0x220-0x22f,0x320-0x327,0x32c-0x32f irq 11 drq 5,7 on isa0
> pcm0: <GUS CS4231> on gusc0
> unknown0: <Disabled Device> on isa0
> joy1: <Generic PnP Joystick> at port 0x200 on isa0
> unknown1: <SB Compatible Audio> at port 0x388-0x389 irq 5 drq 1 on isa0
> unknown2: <MPU-401 GM Music> at port 0x330-0x331 on isa0
> Waiting 5 seconds for SCSI devices to settle
> ad0: 13783MB <IBM-DTTA-371440> [28005/16/63] at ata0-master using UDMA33
> ad1: 2446MB <ST52520A> [4970/16/63] at ata0-slave  using WDMA2
> acd0: DVD-ROM <CREATIVEDVD-ROM DVD2240E 12/24/97> at ata1-master using BIOSPIO
> Mounting root from ufs:/dev/wd1s1a
> da0 at ncr0 bus 0 target 0 lun 0
> da0: <CDC 94171-9 8856> Fixed Direct Access SCSI-CCS device 
> da0: 3.300MB/s transfers
> da0: 312MB (640299 512 byte sectors: 64H 32S/T 312C)
> da2 at ncr0 bus 0 target 5 lun 0
> da2: <IOMEGA ZIP 100 N*32> Removable Direct Access SCSI-2 device 
> da2: 3.300MB/s transfers
> da2: 96MB (196608 512 byte sectors: 64H 32S/T 96C)
> da1 at ncr0 bus 0 target 3 lun 0
> da1: <CONNER CFP2105S  2.14GB 1524> Fixed Direct Access SCSI-2 device 
> da1: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled
> da1: 2048MB (4194304 512 byte sectors: 255H 63S/T 261C)
> WARNING: / was not properly dismounted
> vr0: starting DAD for fe80:0001::0280:c8ff:feeb:a165
> vr0: DAD complete for fe80:0001::0280:c8ff:feeb:a165 - no duplicates found
> cmd ntpd pid 77 tried to use non-present sched_get_priority_max
> cmd ntpd pid 77 tried to use non-present sched_setscheduler
> 
> Here is some earlier info that was written in messages one time when it didn't deadlock, usely however it always deadlock and usely within 20 min from startup.
> 
> Feb  6 04:01:13 cyberspace ntpd[77]: sched_setscheduler(): Function not implemen
> ted
> Feb  6 04:01:13 cyberspace ntpd[77]: using kernel phase-lock loop 2040
> Feb  6 04:02:02 cyberspace su: dateck to troot on /dev/ttyv0
> Feb  6 04:08:52 cyberspace ntpd[77]: time reset -3.782617 s
> Feb  6 04:08:52 cyberspace ntpd[77]: kernel pll status change 2041
> Feb  6 04:23:47 cyberspace syslogd: exiting on signal 15
> 
> >Description:
> 
> The computer totaly deadlocks, after the deadlock only the reset and the powerbutton works. The computer does not react to any other input from mouse, keyboard, or network.
> The program that induces the deadlock is ntpd, and it have been like this since
> beginning of january.
> 
> 
> >How-To-Repeat:
> 
> Just run ntpd, everytime it deadlocks my computer after a random time.
> 
> My ntp parameters: -p /var/run/xntpd.pid
> 
> ntp.conf
> server lunic.luth.se prefer
> server eru.mt.luth.se
> server news.luth.se
> server samson.dc.luth.se
> 
> 
> I hope i got all the info in here.
> 
> >Fix:
> 
> Kill ntpd process.
> 
> 
> >Release-Note:
> >Audit-Trail:
> >Unformatted:
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-bugs" in the body of the message

-- 
-------------------------------------------------------------------------------
* Szilveszter ADAM * JATE Szeged * email: sziszi@petra.hos.u-szeged.hu *
* Homepage : none * alternate email: cc@flanker.itl.net.ua *
* Finger sziszi@petra.hos.u-szeged.hu for PGP key. *
* I prefer using the door instead of Windows(tm)... *
Comment 2 Poul-Henning Kamp 2000-02-06 16:12:52 UTC
How can you tell for sure that ntpd is the culprit ?

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
Comment 3 dateck 2000-02-06 21:52:46 UTC
According to Poul-Henning Kamp:
> 
> How can you tell for sure that ntpd is the culprit ?
> 

When it is running my computer deadlocks, and when it is not running 
my computer can run for days.

It was right after xntpd changed name to ntpd that I discovered it, 
I noticed that xntpd wasn't running so I changed the rc files so it would use
ntpd instead of xntpd and to my suprise my computer started to die all the 
time.
So it is realy ntpd that casuses it, however it might need help of something 
else in the system, so if you have any suggestions or things you want me to 
try, I'll do it.

regards

/Tomas

-- 
Tomas Klockar can be found at the following adresses:

Kårhusvägen 4:23      |  Furuvägen 102         |  dateck@ludd.luth.se
977 54 Luleå          |  871 52 Härnösand      |  dateck@solace.mh.se
Tel: +46-920-231335   |  Tel: +46-611-13393    |  d94-tkl@sm.luth.se
Mob: +46-70-664 33 26 |  Mob: +46-70-374 0 347
Comment 4 Poul-Henning Kamp freebsd_committer freebsd_triage 2001-05-23 21:40:28 UTC
State Changed
From-To: open->closed

This has been fixed.  Ntpd elevated it's priority to max in every way  
it could and that is a bad idea if you program has "issues".