-----BEGIN PGP SIGNED MESSAGE-----


  1. running
	NetBSD 1.3H (SSW) #5: Fri Sep 11 23:19:07 EDT 1998

  on my file server seems to have cured it of the problems with very large
	and growing numbers for 
	                0 discarded for bad header offset fields

  [this was reported on tech-net]

  2. I still have:
	                27782 discarded for bad checksums
                3460137 discarded for bad header offset fields

  on my XTERM, which is:
	NetBSD 1.3F (XTERM) #2: Sat Jul 25 19:26:58 EDT 1998

  and has been:
	11:42PM  up 28 mins, 3 users, load averages: 1.14, 0.57, 0.38

  3. I would like to therefore upgrade my XTERM to 1.3H, except that
	when I boot a kernel built Sept. 11, I get:

	ym0 at isapnp0:...
	ym0: IPL3
	db> 

  doing a trace gives me (transcribed onto the back of an envelope, dump
was broken with the IDE patches I was running before, I forgot that it was 
not broken in -current):
	(null)
	ym_attach()
	ym_isapnp_attach()...

  I.e. ym_attach is jumping through null. Is isa_intr_establish a macro? I
think so... so line 111 of ym.c is the offending one, probably ym_isapnp.c
didn't setup the ym_softc right.

  4. I've supped again, but I now get:
	/v/netbsd/src/sys/arch/i386/i386/locore.s: Assembler messages:
	/v/netbsd/src/sys/arch/i386/i386/locore.s:190: Error: Unknown expression
	/v/netbsd/src/sys/arch/i386/i386/locore.s:191: Error: Unknown expression
	/v/netbsd/src/sys/arch/i386/i386/locore.s:192: Error: Unknown expression
	/v/netbsd/src/sys/arch/i386/i386/locore.s:205: Error: Unknown expression
	/v/netbsd/src/sys/arch/i386/i386/locore.s:206: Error: Unknown expression
	/v/netbsd/src/sys/arch/i386/i386/locore.s:207: Error: Unknown expression
	/v/netbsd/src/sys/arch/i386/i386/locore.s:641: Error: Unimplemented segment type 0 in parse_operand
	/v/netbsd/src/sys/arch/i386/i386/locore.s:651: Error: Unimplemented segment type 0 in parse_operand

  Probably I need a new AS. However, I ran into missing vasprintf() [I
sure don't like that function, btw.]. I suspect I may run into the same
thing building the rest of the toolchain without a new libc.... which 
brings me to my real question:
	what's happening to libc?
  would someone be able to give a functioning libc that has vasprintf() and
whatever else is needed to build a -current toolchain?

  ...whew.

   :!mcr!:            |  Network and security consulting/contract programming
   Michael Richardson |         Firewalls, TCP/IP and Unix administration
 Personal: http://www.sandelman.ottawa.on.ca/People/Michael_Richardson/Bio.html
 Corporate: http://www.sandelman.ottawa.on.ca/SSW/
	ON HUMILITY: To err is human, to moo bovine.


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQB1AwUBNgsSqdiXVu0RiA21AQHN+AL/QyQPTeKPoh8/uQhKakg0OAmRUV+7jxBd
aGeOcJawJoZpef7//8BkoUtXPG8J42zEShZybXAAumLQNHZZD/pZfU1siRQEJzCp
q5Cj469MJCC8sh/yUdmvWy9h7rvEpsdW
=j1DH
-----END PGP SIGNATURE-----