haveseen_isadev

[Brian Behlendorf]

I'm seeing the following at boot (from a world built Wednesday night):

...
chip0:  at device 0.0 on pci0
chip1:  at device 1.0 on pci0
isab0:  at device 4.0 on pci0
ide_pci0:  at device 4.1 on pci0
chip2:  at device 4.3 on pci0
ahc0:  at device 6.0 on pci0
ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs
ahc0: interrupting at irq 12
xl0: <3Com 3c905-TX Fast Etherlink XL> at device 9.0 on pci0
xl0: interrupting at irq 12
xl0: Ethernet address: 00:60:08:a3:51:e8
xl0: autoneg complete, link status good (half-duplex, 10Mbps)
ahc1:  at device 10.0 on pci0
ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
ahc1: interrupting at irq 10
xl1: <3Com 3c905B-TX Fast Etherlink XL> at device 12.0 on pci0
xl1: interrupting at irq 11
xl1: Ethernet address: 00:10:5a:a7:e5:45
xl1: autoneg complete, link status good (half-duplex, 10Mbps)
eisa0:  on motherboard
isa0:  on motherboard
fdc0: interrupting at irq 6
fdc0:  at port 0x3f0-0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> at fdc0 drive 0
wdc0 at port 0x1f0-0x1f7 irq 14 on isa0
wdc0: unit 0 (wd0): 
wd0: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S
wdc0: unit 1 (wd1): 
wd1: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S
wdc0: interrupting at irq 14
haveseen_isadev() called - FIXME!
haveseen_isadev() called - FIXME!
haveseen_isadev() called - FIXME!
haveseen_isadev() called - FIXME!
haveseen_isadev() called - FIXME!
haveseen_isadev() called - FIXME!
haveseen_isadev() called - FIXME!
haveseen_isadev() called - FIXME!
haveseen_isadev() called - FIXME!
haveseen_isadev() called - FIXME!
haveseen_isadev() called - FIXME!
bt_isa_probe: Probe failed for card at 0x330
bt_isa_probe: Probe failed for card at 0x334
bt_isa_probe: Probe failed for card at 0x230
bt_isa_probe: Probe failed for card at 0x234
bt_isa_probe: Probe failed for card at 0x130
bt_isa_probe: Probe failed for card at 0x134
haveseen_isadev() called - FIXME!
haveseen_isadev() called - FIXME!
haveseen_isadev() called - FIXME!
haveseen_isadev() called - FIXME!
haveseen_isadev() called - FIXME!
haveseen_isadev() called - FIXME!
atkbdc0:  at port 0x60 on isa0
atkbd0:  on atkbdc0
atkbd0: interrupting at irq 1
vga0:  on isa0
...


Here's a diff between my kernel and GENERIC:

21c21
< ident TURBO
---
> ident GENERIC
190c190
< pseudo-device pty 64
---
> pseudo-device pty 16
225,243d224
< 
<  custom additions!
< options MD5
< options PERFMON
< 
< # Network options. NMBCLUSTERS defines the number of mbuf clusters and
< # defaults to 256. This machine is a server that handles lots of traffic,
< # so we crank that value.
< options   NMBCLUSTERS=4096# mbuf clusters at 4096
< 
< #
< # Misc. options
< #
< pseudo-device   ccd 4   #Concatenated disk driver
< options   IPFIREWALL
< options   IPDIVERT
< options   ICMP_BANDLIM
< options   DUMMYNET
< options   BRIDGE


Am I missing a device or controller line somewhere?

Brian





To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: problem bootstrapping egcs

[Brian Behlendorf]

On Thu, 6 May 1999, David O'Brien wrote:
> > the build of egcs.  My understanding was that to bootstrap over the change
> > I should first (before the make world) do:
> 
> VERY wrong.  All you want to do is a normal ``make world'' (or ``make
> buildworld'')

Hup, you're right, sorry about the false alarm.  It all builds great.

Brian




To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

problem bootstrapping egcs

[Brian Behlendorf]

I'm doing a make world for the first time since the egcs cutover (yeah
yeah, keep the flames to yourselves) and I encountered a rough spot with
the build of egcs.  My understanding was that to bootstrap over the change
I should first (before the make world) do:

# cd /usr/src; make -DCLOBBER includes   
 [worked fine]
# cd /usr/src/gnu/usr.bin/cc; make clean; make obj
 [worked fine]
# make
===> cc_tools
===> cc_int
===> cc_drv
===> cpp
===> cc1
===> cc
cc -O -pipe -I/usr/src/gnu/usr.bin/cc/cc/../../../../contrib/egcs/gcc
-I/usr/src/gnu/usr.bin/cc/cc/../../../../contrib/egcs/gcc/config
-DFREEBSD_NATIVE -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"egcs-2.91.66\"
-DDEFAULT_TARGET_MACHINE=\"\"
-I/usr/obj/usr/src/gnu/usr.bin/cc/cc/../cc_tools
-I/usr/src/gnu/usr.bin/cc/cc/../cc_tools-o cc gcc.o
/usr/obj/usr/src/gnu/usr.bin/cc/cc/../cc_drv/libcc_drv.a
/usr/obj/usr/src/gnu/usr.bin/cc/cc/../cc_drv/libcc_drv.a(choose-temp.o):
In function `make_temp_file':
choose-temp.o(.text+0x284): undefined reference to `mkstemps'
*** Error code 1

Stop.
*** Error code 1

Stop.


Hmm.  Any ideas?

Brian






To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files)

[Brian Behlendorf]

On Sat, 1 May 1999, Jordan K. Hubbard wrote:
> My suggestion would be to wait and see how bitkeeper pans out.  Enough
> people in the Linux camp have already looked at CVSup and gone "ooh,
> sexy!"  that I think there will already be significant pressure to
> develop similar tools for the bitkeeper environment.  When that
> happens, we can start to look at this more seriously.

I think that's wise.

I'd also recommend people check out Bitkeeper's license before making any
final decisions.  It's not GPL, BSD, or any other Open Source license.  

Brian




To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message