From girgen@partitur.se Fri Aug  6 05:43:43 1999
Return-Path: <girgen@partitur.se>
Received: from bastuba.partitur.se (bastuba.partitur.se [193.219.246.194])
	by hub.freebsd.org (Postfix) with ESMTP id F02AC14A2E
	for <FreeBSD-gnats-submit@freebsd.org>; Fri,  6 Aug 1999 05:43:33 -0700 (PDT)
	(envelope-from girgen@partitur.se)
Received: from elbas.partitur.se (elbas.partitur.se [193.219.246.222])
	by bastuba.partitur.se (8.8.8/8.8.8) with ESMTP id OAA24154
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 6 Aug 1999 14:43:30 +0200 (CEST)
	(envelope-from girgen@partitur.se)
Received: (from girgen@localhost)
	by elbas.partitur.se (8.9.3/8.9.3) id OAA00871;
	Fri, 6 Aug 1999 14:43:30 +0200 (CEST)
	(envelope-from girgen@partitur.se)
Message-Id: <199908061243.OAA00871@elbas.partitur.se>
Date: Fri, 6 Aug 1999 14:43:30 +0200 (CEST)
From: Palle Girgensohn <girgen@partitur.se>
Reply-To: girgen@partitur.se
To: FreeBSD-gnats-submit@freebsd.org
Subject: still inetd junk pointer too low to make sense 
X-Send-Pr-Version: 3.2

>Number:         12998
>Category:       bin
>Synopsis:       still inetd junk pointer too low to make sense
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    des
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Aug  6 05:50:01 PDT 1999
>Closed-Date:    Fri Dec 1 03:26:51 PST 2000
>Last-Modified:  Fri Dec 01 03:27:47 PST 2000
>Originator:     Palle Girgensohn
>Release:        FreeBSD 3.2-STABLE i386
>Organization:
Partitur 
>Environment:
FreeBSD sources from July 7th (STABLE). I've seen this occasionally on 
all our machines (at least ten different hardware confiurations) ever
since updating our worksataions to 3.x.

We run nfs and nis/yp, if that matters...

>Description:
$ rlogin tb303
netd in free(): warning: junk pointer, too low to make sense.
$ telnet tb303
Trying 193.219.246.230...
Connected to tb303.partitur.se.
Escape character is '^]'.
inetd in free(): warning: junk pointer, too low to make sense.
inetd in free(): warning: junk pointer, too high to make sense.
inetd in free(): warning: junk pointer, too high to make sense.
inetd in free(): warning: junk pointer, too high to make sense.
inetd in free(): warning: junk pointer, too low to make sense.
inetd in free(): warning: junk pointer, too high to make sense.
inetd in free(): warning: junk pointer, too high to make sense.
inetd in free(): warning: junk pointer, too high to make sense.
inetd in free(): warning: junk pointer, too low to make sense.
inetd in free(): warning: junk pointer, too high to make sense.
inetd in free(): warning: junk pointer, too high to make sense.
inetd in free(): warning: junk pointer, too high to make sense.
inetd in free(): warning: junk pointer, too low to make sense.
inetd in free(): warning: junk pointer, too high to make sense.
inetd in free(): warning: junk pointer, too low to make sense.
inetd in realloc(): warning: junk pointer, too high to make sense.
inetd in free(): warning: junk pointer, too high to make sense.
Connection closed by foreign host.

I though this was fixed a long time ago
(mentioned in PR-kern/6858 and prposedly fixed in PR-bin/8183).
Lately, the frequency of this problem showing up has decreased,
but it still exists.

>How-To-Repeat:
It happens occasionally. I can't figure out if there's anything special
that tiggers it.
	

>Fix:
kill and restart inetd :-(	
	


>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->des 
Responsible-Changed-By: des 
Responsible-Changed-When: Tue Aug 10 00:59:09 PDT 1999 
Responsible-Changed-Why:  
inetd is mine. 

From: Palle Girgensohn <girgen@partitur.se>
To: freebsd-gnats-submit@freebsd.org, girgen@partitur.se
Cc:  
Subject: Re: bin/12998: still inetd junk pointer too low to make sense
Date: Fri, 24 Sep 1999 02:27:20 +0200

 Hi!
 
 Just to follow-up, this happens occasionally with the new release 3.3 of
 FreeBSD also. Can this be sort of hardware related? I haven't seen it on
 more than a few machines recently; always the same machines. Or maybe it
 has something to do with the way the users use the machine - they might
 load them harder...?
 
 /Palle
 

From: Borja Marcos <borjamar@sarenet.es>
To: freebsd-gnats-submit@freebsd.org, girgen@partitur.se
Cc:  
Subject: Re: bin/12998: still inetd junk pointer too low to make sense
Date: Thu, 14 Oct 1999 09:44:43 +0200

 	Nothing to do with NIS, I guess (I'm not using NIS). I have
 3.3-RELEASE with PAO3. 
 
 
 	Borja.
 

From: Borja Marcos <borjamar@sarenet.es>
To: freebsd-gnats-submit@freebsd.org, girgen@partitur.se
Cc:  
Subject: Re: bin/12998: still inetd junk pointer too low to make sense
Date: Fri, 22 Oct 1999 13:18:32 +0200

 	This has happened to me... (I'm not sending all of them, but think
 about
 the typical PID inetd uses to have, and the pids it reached before I
 killed it)
 
 	All I did was an "rup".
 
 	My uname -a, and kernel config file follows. This is a laptop with 
 PAO patches installed in the kernel.
 
 
 	Borja.
 Oct 22 13:07:53 zaphod /kernel: pid 3886 (inetd), uid 0: exited on
 signal 11
 Oct 22 13:07:53 zaphod inetd[168]: /usr/libexec/rpc.rstatd[3886]: exit
 status 0x
 b
 Oct 22 13:07:53 zaphod /kernel: pid 3887 (inetd), uid 0: exited on
 signal 11
 Oct 22 13:07:53 zaphod inetd[168]: /usr/libexec/rpc.rstatd[3887]: exit
 status 0x
 b
 Oct 22 13:07:53 zaphod /kernel: pid 3888 (inetd), uid 0: exited on
 signal 11
 Oct 22 13:07:53 zaphod inetd[168]: /usr/libexec/rpc.rstatd[3888]: exit
 status 0x
 b
 Oct 22 13:07:54 zaphod /kernel: pid 3889 (inetd), uid 0: exited on
 signal 11
 Oct 22 13:07:54 zaphod inetd[168]: /usr/libexec/rpc.rstatd[3889]: exit
 status 0x
 b
 Oct 22 13:07:54 zaphod /kernel: pid 3890 (inetd), uid 0: exited on
 signal 11
 Oct 22 13:07:54 zaphod inetd[168]: /usr/libexec/rpc.rstatd[3890]: exit
 status 0x
 b
 Oct 22 13:07:54 zaphod /kernel: pid 3891 (inetd), uid 0: exited on
 signal 11 
 Oct 22 13:07:54 zaphod inetd[168]: /usr/libexec/rpc.rstatd[3891]: exit
 status 0x
 b
 Oct 22 13:07:54 zaphod /kernel: pid 3893 (inetd), uid 0: exited on
 signal 11
 Oct 22 13:07:54 zaphod inetd[168]: /usr/libexec/rpc.rstatd[3893]: exit
 status 0x
 b
 Oct 22 13:07:54 zaphod /kernel: pid 3894 (inetd), uid 0: exited on
 signal 11
 Oct 22 13:07:54 zaphod inetd[168]: /usr/libexec/rpc.rstatd[3894]: exit
 status 0x
 b
 Oct 22 13:07:54 zaphod /kernel: pid 3895 (inetd), uid 0: exited on
 signal 11 
 Oct 22 13:07:54 zaphod inetd[168]: /usr/libexec/rpc.rstatd[3895]: exit
 status 0x
 b
 Oct 22 13:07:54 zaphod /kernel: pid 3896 (inetd), uid 0: exited on
 signal 11
 
 The boot messages are:
 
 Oct 22 09:23:45 zaphod /kernel: Copyright (c) 1992-1999 FreeBSD Inc.
 Oct 22 09:23:45 zaphod /kernel: Copyright (c) 1982, 1986, 1989, 1991,
 1993  
 Oct 22 09:23:45 zaphod /kernel: The Regents of the University of
 California. All
  rights reserved.
 Oct 22 09:23:45 zaphod /kernel: FreeBSD 3.3-RELEASE #0: Tue Oct 19
 14:00:01 CEST
  1999
 Oct 22 09:23:45 zaphod /kernel:
 borjam@zaphod.arnor.es:/usr/src/sys/compile/ZAPH
 OD
 Oct 22 09:23:45 zaphod /kernel: Timecounter "i8254"  frequency 1193182
 Hz
 Oct 22 09:23:45 zaphod /kernel: CPU: Pentium/P54C (132.63-MHz 586-class
 CPU)
 Oct 22 09:23:45 zaphod /kernel: Origin = "GenuineIntel"  Id = 0x52c 
 Stepping =
 12
 Oct 22 09:23:45 zaphod /kernel:
 Features=0x1bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8>
 Oct 22 09:23:45 zaphod /kernel: real memory  = 50462720 (49280K bytes)
 Oct 22 09:23:45 zaphod /kernel: avail memory = 46243840 (45160K bytes) 
 Oct 22 09:23:45 zaphod /kernel: Preloaded elf kernel "kernel" at
 0xc02ca000.
 Oct 22 09:23:45 zaphod /kernel: Probing for devices on PCI bus 0:
 Oct 22 09:23:45 zaphod /kernel: chip0: <Host to PCI bridge (vendor=1179
 device=0
 601)> rev 0xa7 on pci0.0.0
 Oct 22 09:23:45 zaphod /kernel: vga0: <Chips & Technologies model 00e4
 VGA-compa
 tible display device> rev 0xc2 on pci0.4.0
 Oct 22 09:23:45 zaphod /kernel: ohci0: <OHCI USB Host Controller
 (generic)> rev
 0x01 int a irq 11 on pci0.11.0
 Oct 22 09:23:45 zaphod /kernel: usb0: OHCI version 1.0
 Oct 22 09:23:45 zaphod /kernel: (New OHCI DeviceId=0x00351033)
 Oct 22 09:23:45 zaphod /kernel: Probing for devices on the ISA bus:
 Oct 22 09:23:45 zaphod /kernel: sc0 on isa
 Oct 22 09:23:45 zaphod /kernel: sc0: VGA color <16 virtual consoles,
 flags=0x0>
 Oct 22 09:23:45 zaphod /kernel: atkbdc0 at 0x60-0x6f on motherboard
 Oct 22 09:23:45 zaphod /kernel: atkbd0 irq 1 on isa
 Oct 22 09:23:45 zaphod /kernel: psm0 irq 12 on isa
 Oct 22 09:23:45 zaphod /kernel: psm0: model Generic PS/2 mouse, device
 ID 0 
 Oct 22 09:23:45 zaphod /kernel: sio0: configured irq 4 not in bitmap of
 probed i
 rqs 0
 Oct 22 09:23:46 zaphod /kernel: sio0 not found at 0x3f8
 Oct 22 09:23:46 zaphod /kernel: sio1 at 0x2f8-0x2ff irq 3 flags 0x10 on
 isa
 Oct 22 09:23:46 zaphod /kernel: sio1: type 16550A
 Oct 22 09:23:46 zaphod /kernel: ... try to identify the yamaha
 Oct 22 09:23:46 zaphod /kernel: pcm0 at 0x530 irq 5 drq 1 flags 0xc110
 on isa
 Oct 22 09:23:46 zaphod /kernel: mss_attach <mss>0 at 0x530 irq 5 dma 1:0
 flags 0
 xc110
 Oct 22 09:23:46 zaphod /kernel: setting up yamaha registers
 Oct 22 09:23:46 zaphod /kernel: set yamaha master volume to max
 Oct 22 09:23:46 zaphod /kerneOct 22 09:23:46 zaphod /kernel: ppi0:
 <generic parallel i/o> on ppbus 0
 Oct 22 09:23:46 zaphod /kernel: plip0: <PLIP network interface> on ppbus
 0
 Oct 22 09:23:46 zaphod /kernel: ep0 not found at 0x300
 Oct 22 09:23:46 zaphod /kernel: pcic0 at 0x3e0-0x3e1 irq 11 on isa
 Oct 22 09:23:46 zaphod /kernel: PC-Card ctlr(0) Intel 82365A/B (5 mem &
 2 I/O wi
 ndows)
 Oct 22 09:23:46 zaphod /kernel: pcic0: slot 0 controller I/O address
 0x3e0
 Oct 22 09:23:46 zaphod /kernel: pcic0: slot 1 controller I/O address
 0x3e0  
 Oct 22 09:23:46 zaphod /kernel: vga0 at 0x3b0-0x3df maddr 0xa0000 msize
 131072 o
 n isa
 Oct 22 09:23:47 zaphod /kernel: npx0 on motherboard
 Oct 22 09:23:47 zaphod /kernel: npx0: INT 16 interface
 Oct 22 09:23:47 zaphod /kernel: apm0 on isa
 Oct 22 09:23:47 zaphod /kernel: apm: found APM BIOS version 1.2
 Oct 22 09:23:47 zaphod /kernel: usb0: <OHCI USB Host Controller
 (generic)>
 Oct 22 09:23:47 zaphod /kernel: uhub0 at usb0
 Oct 22 09:23:47 zaphod /kernel: uhub0: (0x1033) OHCI root hub, class
 9/0, rev 1.
 00/1.00, addr 1 
 Oct 22 09:23:47 zaphod /kernel: uhub0: 2 ports with 2 removable, self
 powered
 Oct 22 09:23:47 zaphod /kernel: Initializing PC-card drivers: ep sio wdc
 Oct 22 09:23:47 zaphod /kernel: Intel Pentium detected, installing
 workaround fo
 r F00F bug
 Oct 22 09:23:47 zaphod /kernel: IP packet filtering initialized, divert
 disabled
 , rule-based forwarding disabled, unlimited logging 
 Oct 22 09:23:47 zaphod /kernel: DUMMYNET initialized (990504)
 Oct 22 09:23:47 zaphod /kernel: changing root device to wd0s1a
 Oct 22 09:23:47 zaphod /kernel: Card inserted, slot 0
 Oct 22 09:23:47 zaphod /kernel: Card inserted, slot 1
 l: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
 Oct 22 09:23:46 zaphod /kernel: fd0: 1.44MB 3.5in
 Oct 22 09:23:46 zaphod /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa
 Oct 22 09:23:46 zaphod /kernel: wdc0: unit 0 (wd0): <TOSHIBA MK2103MAV>
 Oct 22 09:23:46 zaphod /kernel: wd0: 2067MB (4233600 sectors), 4200
 cyls, 16 hea
 ds, 63 S/T, 512 B/S
 Oct 22 09:23:46 zaphod /kernel: ppc0 at 0x378 irq 7 flags 0x40 on isa
 Oct 22 09:23:46 zaphod /kernel: ppc0: Generic chipset (ECP/PS2/NIBBLE)
 in COMPAT
 IBLE mode
 Oct 22 09:23:46 zaphod /kernel: ppc0: FIFO with 16/16/16 bytes threshold
 Oct 22 09:23:46 zaphod /kernel: lpt0: <generic printer> on ppbus 0
 Oct 22 09:23:46 zaphod /kernel: lpt0: Interrupt-driven port
 
 borjam@zaphod% uname -a
 FreeBSD zaphod.arnor.es 3.3-RELEASE FreeBSD 3.3-RELEASE #0: Tue Oct 19
 14:00:01 CEST 1999    
 borjam@zaphod.arnor.es:/usr/src/sys/compile/ZAPHOD  i386
 
 
 
 -- 
 ***********************************************************************
 Borja Marcos                    * Internet: borjam@we.lc.ehu.es
 Alangoeta, 11 1 izq             *           borjamar@sarenet.es
 48990 - Algorta (Vizcaya)       *           borjam@uninet.edu
 SPAIN                           *           borjam@well.com
 ***********************************************************************
 --- FreeBSD, turning PCs into workstations
 
State-Changed-From-To: open->closed 
State-Changed-By: des 
State-Changed-When: Fri Dec 1 03:26:51 PST 2000 
State-Changed-Why:  
No reports of this bug in -CURRENT or -STABLE in over a year. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=12998 
>Unformatted:
