, 0, 0, 0}, dc_pad = '\000' ,
> :dc_tx_prod = 10, dc_tx_cons = 10, dc_tx_cnt = 0, dc_rx_prod = 4},
> : dc_stat_ch = {callout = 0xcd6a56c0}}
> :
> :
> :FYI, the machine in general is staying up a bit longer, so maybe you
> :nailed one bug and there are just a few more
nue, or q to quit---
#10 0x80899ae in ?? ()
#11 0x8075ae2 in ?? ()
#12 0x8058813 in ?? ()
#13 0x80749e3 in ?? ()
#14 0x805874b in ?? ()
#15 0x8056120 in ?? ()
#16 0x80552d6 in ?? ()
#17 0x805001d in ?? ()
#18 0x804f9e5 in ?? ()
(kgdb)
---
Howard Leadmon - [EMAIL PROTECTED] - http://www.abs.net
A
<[EMAIL PROTECTED]>
FYI, the machine in general is staying up a bit longer, so maybe you
nailed one bug and there are just a few more that also need to be
caught. :)
Anyway thinks for trying to help me track this one down as it's very
much appreicated, and if you need any other info just let me know...
---
Howard Leadmon - [EMAIL PROTECTED] - http://www.abs.net
ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
p = -1071900421, tf_cs = 8, tf_eflags = 582,
tf_esp = -1059161408, tf_ss = 1074266112}) at ../../i386/i386/trap.c:586
#14 0xc01c18fb in dc_intr (arg=0xc0de6000) at machine/cpufunc.h:331
#15 0xc0230953 in intr_mux (arg=0xc0de7b20)
at ../../i386/isa/intr_machdep.c:569
(kgdb) q
#
---
3, tf_cs = 8, tf_eflags = 66178,
tf_esp = -1071902645, tf_ss = -1059168256}) at ../../i386/i386/trap.c:423
#15 0xc017246b in bpfioctl (dev=0xc0c0de60, cmd=12639866,
addr=0xff400800 , flags=16777215,
p=0xacc0de60) at ../../net/bpf.c:683
#16 0xc01c19 in ?? ()
cannot read proc at 0
(kgd
you need symbols in your kernel in order
> to find out any more information. Build a kernel with the -g option
> and try again.
>
> Greg
Umm, the kernel was built with the -g option, as I knew I needed to be
able to debug it when it crashed. I looked at the handbook, but I don&
fxp related. If fxp is getting device
> timeouts its probably due to the machine or network being attacked.
>
> It's also possible that bad network cabling or a bad switch port
> is to blame.
>
> -Matt
---
Howard Leadmon - [E
0 u2 /kernel: fxp0: device timeout
>
> S_ren and I are trying to find out what is causing some weird Vinum
> problems. He stated that the problem happened more frequently when
> an fxp board was in the system. I don't believe him, and I've found
> at least one bug in
for now, and hopefully someone can give me some
pointers, or lend a hand in trying to get this issue resolved as it's
driving me nutz.. :)
---
Howard Leadmon - [EMAIL PROTECTED] - http://www.abs.net
ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
e list has any ideas, I would sure love to
hear them, as it would be nice to get to the bottom of this issue...
---
Howard Leadmon - [EMAIL PROTECTED] - http://www.abs.net
ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
on ppbus0
APIC_IO: Testing 8254 interrupt delivery
APIC_IO: routing 8254 via IOAPIC #0 intpin 2
SMP: AP CPU #1 Launched!
ad0: 8693MB [17662/16/63] at ata0-master using UDMA33
Mounting root from ufs:/dev/ad0s1a
---
Howard Leadmon - [EMAIL PROTECTED] - http://www.abs.net
ABSnet Internet Services -
tulip cards were one of
> the few that had drivers that supported full-duplex.
>
> Charles
>
> -Original Message-
> From: Howard Leadmon [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, March 12, 2000 4:24 PM
> To: Alfred Perlstein
> Cc: [EMAIL PROTECTED]
> Su
ught Intel had dropped that card, but maybe I am
wrong. I used the DEC based cards as I had seen so many people raving
about them, and at least under Solaris they claim the DEC tulip based
boards are the hot ticket. Do you think the Intel board would really work
that much better under FBSD, as I c
: on ppbus0
lpt0: on ppbus0
lpt0: Interrupt-driven port
plip0: on ppbus0
APIC_IO: Testing 8254 interrupt delivery
APIC_IO: routing 8254 via IOAPIC #0 intpin 2
SMP: AP CPU #1 Launched!
ad0: 8693MB [17662/16/63] at ata0-master using UDMA33
Mounting root from ufs:/dev/ad0s1a
WARNING: / was not prope
ut when I tried to apply them to FBSD
it bitched about them being unknown so I just left them out. Was also
going to move NMBCLUSTERS up to 20480, not sure if thats the solution or
not. I can post the whole config if desired, but really it's very close
to the GENERIC except I added SOFTUPDA
this type of setup with so many
active connections I would love to hear about it..
---
Howard Leadmon - [EMAIL PROTECTED] - http://www.abs.net
ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-ha
16 matches
Mail list logo
