stable-digest V5 #791

[owner-freebsd...@freebsd.org]

stable-digest Tuesday, February 11 2003 Volume 05 : Number 791

In this issue:
RE: PCI oddity
Re: Netscape 4.76 & MGA DRI
Re: Odd "hanging" behavior with -STABLE ...
Re: ng_fec && pseudo-device vlan
SMP problems post Jan 28th
Re: ipfw traffic shaping
Re: PCI oddity
Re: PCI oddity
subscribe freebsd-stable
Re: libc_r seems to be broken in 4.7-STABLE as of Jan 27
Work-Around for 'BTX Halted' issue ... does one exist?

----------------------------------------------------------------------

Date: Mon, 10 Feb 2003 21:29:38 -0700
From: "Steven" <magu...@digitalbastards.net>
Subject: RE: PCI oddity

I have an abit bx133 board with a similar problem. The box runs linux, but
experienced the same problem in the same place, when it was probing the
drives. I narrowed the problem down to lack of IRQ's. Here's what I did to
work around this:

Go into the BIOS, disable the Serial and Parallel if you don't need them.
You may also need to set IRQs 3,4,7 to PCI instead of ISA on that board.
Look under the PCI section, if it exists. You should be able to specify
IRQ's for several of the PCI slots, try playing with those. Turn off
Plug'n'Play OS Installed, give it a whirl, or turn it on (I've some some
luck with this on other boxes). I had to turn off PnP OS, specify different
IRQ's for each PCI slot to force them not to share, and have all unused
hardware disabled to free up IRQ's.

Hopefully this will be of some use to you :)

Steven

"exitus acta probat"
"fide, sed cui vide"

- -----Original Message-----
From: owner-free...@FreeBSD.ORG
[mailto:owner-free...@FreeBSD.ORG] On Behalf Of Jason Andresen
Sent: Monday, February 10, 2003 8:23 AM
To: Phil Reynolds; freebsd...@freebsd.org
Subject: Re: PCI oddity

My manual doesn't tell me squat about the interrupts on the board. My
guess what that the two slots share an IRQ, because PCI only has IIRC 4
IRQ lines to go around. That's why I was worried it might be an issue
with FreeBSD being unable to support shared cards.

It is the bottom two PCI slots that give me problems though (one of
which is the shared PCI/ISA slot, but that doesn't seem to matter).

------------------------------

Date: Mon, 10 Feb 2003 22:35:14 -0800 (PST)
From: Rhett Monteg Hollander <victory...@yahoo.com>
Subject: Re: Netscape 4.76 & MGA DRI

Scott Long wrote:
>
> Rhett Monteg Hollander wrote:
>
> > Hello gentlemen,
> >
> > several days ago I've installed 5.0-RELEASE onto
one
> > of my machines, which already carried 4.7-RC1. To
> > avoid possible compatibility problems, I did a
clean
> > install onto another hard drive, and later
recompiled
> > everything. Here I have a couple of annoying
issues.
> >
> > Shell refuses to start Netscape Communicator 4.76
(for
> > FreeBSD) saying "binary file is not executable",
but
> > it was (and is) running fine under 4.7. Since it
was
> > compiled under FreeBSD 2.2.x, I have compat22
> > installed (together with compat3x and compat4x).
No
> > help.
>
> Recompile your kernel with COMPAT_AOUT, or load the
aout.ko kernel module.
Floating exception (core dumped), ~2 megs

>
> >
> > Second issue comes to be about
hardware-accelerated
> > OpenGL under XFree86 4.2.0, using Matrox G400
> > hardware. Simply, there is no hardware
acceleration at
> > all. DRM kernel modules that come with 4.2.0 are
> > intended for use with FreeBSD 4.x, and they don't
even
> > compile under 5.x. I built kernel with "device
mgadrm"
> > and "options DRM_LINUX", as well as "options
> > COMPAT_LINUX". After launching glxgears system
hangs
> > up completely. Problem seems to be within libdrm.
So
> > far I have no DRI, but software OpenGL, and 162fps
> > compared to 368fps under 4.7.
>
> FreeBSD 5.0 comes with the DRM kernel modules in the
base system, as it
> looks like you discovered. Can you enable a serial
console and capture
> the crash?
Fixed. Problem was in XF86Config, which was set up
improperly. Not sure what exactly led to that point,
because I've overwritten it with a substitute from
4.7. Now glxgears run fine, at 357fps; interesting, I
supposed 5.0 to be faster than 4.7 in this case, at
least in honour of gcc-3.2.1

>
> Scott
>
> >
> > ---
> > Regards,
> > Rhett
> >

__________________________________________________
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day
http://shopping.yahoo.com

------------------------------

Date: Mon, 10 Feb 2003 22:10:35 -0400 (AST)
From: The Hermit Hacker <scr...@hub.org>
Subject: Re: Odd "hanging" behavior with -STABLE ...

On Mon, 10 Feb 2003, David Schultz wrote:

> Does it seem to be basically responsive (e.g. you can switch
> virtual consoles), but processes hang when they try to do I/O? If
> you can run top while you see this problem, it should tell you
> what state processes are getting stuck in. You can get the same
> information by breaking into the debugger and typing 'ps'. I had
> a problem like this that involved the SCSI controller randomly
> timing out. Decreasing the tag queue length solved the problem.

I don't think taht the amr driver is part of cam yet? :(

jupiter# df -t ufs
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/amrd0s1a 127023 113135 3727 97% /
/dev/amrd0s1e 508143 12 467480 0% /tmp
/dev/amrd0s1g 6528346 3019785 2986294 50% /usr
/dev/amrd0s1f 1016303 389998 545001 42% /var
/dev/amrd1s1a 66972328 45747954 17206035 73% /v1
jupiter# !cam
camcontrol devlist -v
scbus0 on amr0 bus 0:
scbus-1 on xpt0 bus 0:
< > at scbus-1 target -1 lun -1 (xpt0)

------------------------------

Date: Tue, 11 Feb 2003 12:23:06 +0100 (CET)
From: Attila Nagy <b...@fsn.hu>
Subject: Re: ng_fec && pseudo-device vlan

Hello,

> Why don't ng_fec (Cisco FastEtherChannel netgraph module) and
> `pseudo-device vlan' (802.1q trunking) work together?
Don't worry. If you will ever upgrade to 5.0, not only VLANs on FEC
interfaces, but FEC itself won't work.

> Cisco Switch FreeBSD
>
> /Port 4/1--------------fxp0\ /vlan0
> dot1q Trunk - EtherChannel< >--fec0---<
> \Port 4/2--------------fxp1/ \vlan1
> \vlan2
> \vlanN
Nice ASCII art. You can safely s/FreeBSD/Linux/g to get this work :~-(
(BTW, is it working under Linux? I don't use Linux)

> I am not skilled enough to diagnose the kernel internals to discern why
> this doesn't work. I am willing to test any patches that may turn up.
ng_fec is in FreeBSD's tree starting from 5.0, but not yet connected to
the build. I assume it won't ever... :(

If anyone willing to fix it and can understand what's going on in the
kernel, I will gladly provide console (serial) access to a machine which
has two fxp NICs and is connected to a FEC aware switch.

Any takers?

- ----------[ Free Software ISOs - http://www.fsn.hu/?f=download ]----------
Attila Nagy e-mail: Attil...@fsn.hu
Free Software Network (FSN.HU) phone @work: +361 210 1415 (194)
cell.: +3630 306 6758

------------------------------

Date: Tue, 11 Feb 2003 06:48:29 -0500
From: Mike Tancsa <mi...@sentex.net>
Subject: SMP problems post Jan 28th

The previous kernel had been running fine for some time, and now at night
around the running of periodic, the box will 'periodically' crash. It does
not seem to do it each night, but almost every other night and always just
after 3am when periodic runs. I can never get a crash dump, and I had to
hook up a serial console to capture this at night. Also, I cant seem to
force the issue by running periodic by hand. But, like I said, it always
seems to happen a few minutes after 3am. (No, nothing else is scheduled to
run then and no other boxes do anything to it at that time either)

Fatal trap 12: page fault while in kernel mode
mp_lock = 01000002; cpuid = 1; lapic.id = 00000000
fault virtual address = 0x65b046a5
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc0174830
stack pointer = 0x10:0xde174c4c
frame pointer = 0x10:0xde174c58
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 4203 (find)
interrupt mask = none <- SMP: XXX
trap number = 12
panic: page fault
mp_lock = 01000002; cpuid = 1; lapic.id = 00000000
boot() called on cpu#1

syncing disks... 4 2
done
Uptime: 1d15h8m8s
Automatic reboot in 15 seconds - press a key on the console to abort
Rebooting...
cpu_reset called on cpu#1
cpu_reset: Stopping other CPUs
cpu_reset: Restarting BSP
tpu_reset_proxy: Grabbed mp lock cfpour_reSsPe
: BSP did not grab mp lock
Console: serial port
BIOS drive A: is disk0
BIOS drive C: is disk1
BIOS 629kB/785396kB available memory

Any ideas how best to track this down ? There seem to been some commits on
the 30th that might have had an effect.

4.7-STABLE FreeBSD 4.7-STABLE #0: Thu Feb 6 06:04:02 EST 2003

ns4# dmesg
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 4.7-STABLE #0: Thu Feb 6 06:04:02 EST 2003
mdta...@ns4.recycle.net:/usr/obj/usr/src/sys/smp
Timecounter "i8254" frequency 1193182 Hz
CPU: Intel Pentium III (801.82-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x683 Stepping = 3
Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
real memory = 805294080 (786420K bytes)
config> q
avail memory = 779272192 (761008K bytes)
Programming 24 pins in IOAPIC #0
IOAPIC #0 intpin 2 -> irq 0
IOAPIC #0 intpin 17 -> irq 11
IOAPIC #0 intpin 18 -> irq 10
IOAPIC #0 intpin 19 -> irq 12
FreeBSD/SMP: Multiprocessor motherboard
cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000
cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000
io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000
Preloaded elf kernel "kernel" at 0xc03b5000.
Preloaded userconfig_script "/boot/kernel.conf" at 0xc03b509c.
Pentium Pro MTRR support enabled
md0: Malloc disk
Using $PIR table, 6 entries at 0xc00f0d20
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Intel 82443BX (440 BX) host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
pcib1: <Intel 82443BX (440 BX) PCI-PCI (AGP) bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
pci1: <ATI Mach64-GB graphics accelerator> at 0.0
isab0: <Intel 82371AB PCI to ISA bridge> at device 4.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel PIIX4 ATA33 controller> port 0xb800-0xb80f at device 4.1 on
pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
pci0: <Intel 82371AB/EB (PIIX4) USB controller> at 4.2
Timecounter "PIIX" frequency 3579545 Hz
chip1: <Intel 82371AB Power management controller> port 0xe800-0xe80f at
device 4.3 on pci0
fxp0: <Intel Pro 10/100B/100+ Ethernet> port 0xb000-0xb03f mem
0xe3800000-0xe38fffff,0xe4000000-0xe4000fff irq 12 at device 9.0 on pci0
fxp0: Ethernet address 00:02:b3:07:fd:8d
inphy0: <i82555 10/100 media interface> on miibus0
inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp1: <Intel Pro 10/100B/100+ Ethernet> port 0xa800-0xa81f mem
0xe3000000-0xe30fffff,0xe6800000-0xe6800fff irq 10 at device 10.0 on pci0
fxp1: Ethernet address 00:a0:c9:e7:a6:e6
inphy1: <i82555 10/100 media interface> on miibus1
inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
twe0: <3ware Storage Controller> port 0xa400-0xa40f irq 11 at device 11.0
on pci0
twe0: 2 ports, Firmware FE6X 1.02.00.029, BIOS BEXX 1.07.00.009
orm0: <Option ROMs> at iomem
0xc0000-0xc7fff,0xc8000-0xc8fff,0xcc000-0xccfff on isa0
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
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x100>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A, console
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/9 bytes threshold
ppi0: <Parallel I/O> on ppbus0
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
APIC_IO: Testing 8254 interrupt delivery
APIC_IO: routing 8254 via IOAPIC #0 intpin 2
DUMMYNET initialized (011031)
ipfw2 initialized, divert enabled, rule-based forwarding enabled, default
to accept, logging limited to 34100 packets/entry by default
IPv6 packet filtering initialized, default to accept, logging limited to
100 packets/entry
twed0: <TwinStor, Normal> on twe0
twed0: 76318MB (156299440 sectors)
Mounting root from ufs:/dev/twed0a
SMP: AP CPU #1 Launched!
WARNING: / was not properly dismounted
ns4#

config is pretty simple

grep -v ^# smp | strings
machine i386
cpu I586_CPU
cpu I686_CPU
ident smp
maxusers 0
makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols
options MATH_EMULATE #Support for x87 emulation
options INET #InterNETworking
options INET6 #IPv6 communications protocols
options FFS #Berkeley Fast Filesystem
options FFS_ROOT #FFS usable as root device [keep this!]
options SOFTUPDATES #Enable FFS soft updates support
options UFS_DIRHASH #Improve performance on big directories
options MFS #Memory Filesystem
options MD_ROOT #MD is a potential root device
options NFS #Network Filesystem
options NFS_ROOT #NFS usable as root device, NFS
required
options PROCFS #Process filesystem
options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!]
options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI
options UCONSOLE #Allow users to grab the console
options USERCONFIG #boot -c editor
options VISUAL_USERCONFIG #visual boot -c editor
options KTRACE #ktrace(1) support
options SYSVSHM #SYSV-style shared memory
options SYSVMSG #SYSV-style message queues
options SYSVSEM #SYSV-style semaphores
options P1003_1B #Posix P1003_1B real-time extensions
options _KPOSIX_PRIORITY_SCHEDULING
options ICMP_BANDLIM #Rate limit bad replies
options KBD_INSTALL_CDEV # install a CDEV entry in /dev
# output. Adds ~128k to driver.
# output. Adds ~215k to driver.
options SMP # Symmetric MultiProcessor Kernel
options APIC_IO # Symmetric (APIC) I/O
device isa
device pci
device fdc0 at isa? port IO_FD1 irq 6 drq 2
device fd0 at fdc0 drive 0
device ata
device atadisk # ATA disk drives
device atapicd # ATAPI CDROM drives
device atapist # ATAPI tape drives
options ATA_STATIC_ID #Static device numbering
device ahc # AHA2940 and onboard AIC7xxx devices
# Allow ncr to attach legacy NCR devices when
# both sym and ncr are configured
device scbus # SCSI bus (required)
device da # Direct Access (disks)
device sa # Sequential Access (tape etc)
device cd # CD
device pass # Passthrough device (direct SCSI access)
device twe # 3ware Escalade
device atkbdc0 at isa? port IO_KBD
device atkbd0 at atkbdc? irq 1 flags 0x1
device psm0 at atkbdc? irq 12
device vga0 at isa?
pseudo-device splash
device sc0 at isa? flags 0x100
device npx0 at nexus? port IO_NPX irq 13
device apm0 at nexus? disable flags 0x20 # Advanced Power
Management
device sio0 at isa? port IO_COM1 flags 0x10 irq 4
device sio1 at isa? port IO_COM2 irq 3
device ppc0 at isa? irq 7
device ppbus # Parallel port bus (required)
device lpt # Printer
device plip # TCP/IP over parallel
device ppi # Parallel port interface device
device miibus # MII bus support
device dc # DEC/Intel 21143 and various workalikes
device fxp # Intel EtherExpress PRO/100B (82557, 82558)
device rl # RealTek 8129/8139
pseudo-device loop # Network loopback
pseudo-device ether # Ethernet support
pseudo-device ppp 1 # Kernel PPP
pseudo-device tun # Packet tunnel.
pseudo-device pty # Pseudo-ttys (telnet etc)
pseudo-device md # Memory "disks"
pseudo-device disc # Memory "disks"
pseudo-device gif # IPv6 and IPv4 tunneling
pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation)
pseudo-device bpf #Berkeley packet filter
options IPFW2
options IPFIREWALL #firewall
options IPFIREWALL_VERBOSE #enable logging to syslogd(8)
options IPFIREWALL_FORWARD #enable transparent proxy support
options IPFIREWALL_VERBOSE_LIMIT=34100 #limit verbosity
options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default
options IPV6FIREWALL #firewall for IPv6
options IPV6FIREWALL_VERBOSE
options IPV6FIREWALL_VERBOSE_LIMIT=100
options IPV6FIREWALL_DEFAULT_TO_ACCEPT
options DUMMYNET
options IPDIVERT #divert sockets
options NETGRAPH #netgraph(4) system
options NETGRAPH_ASYNC
options NETGRAPH_BPF
options NETGRAPH_ECHO
options NETGRAPH_ETHER
options NETGRAPH_HOLE
options NETGRAPH_IFACE
options NETGRAPH_KSOCKET
options NETGRAPH_L2TP
options NETGRAPH_LMI
options NETGRAPH_MPPC_ENCRYPTION
options NETGRAPH_ONE2MANY
options NETGRAPH_PPP
options NETGRAPH_PPPOE
options NETGRAPH_PPTPGRE
options NETGRAPH_RFC1490
options NETGRAPH_SOCKET
options NETGRAPH_TEE
options NETGRAPH_TTY
options NETGRAPH_UI
options NETGRAPH_VJC
- --------------------------------------------------------------------
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, mi...@sentex.net
Providing Internet since 1994 www.sentex.net
Cambridge, Ontario Canada www.sentex.net/mike

------------------------------

Date: Tue, 11 Feb 2003 07:46:28 -0600
From: Greg Panula <greg....@dolaninformation.com>
Subject: Re: ipfw traffic shaping

Martin Hudec wrote:
>
> Hello,
>
> I have question regarding ipfw traffic shaping:
>
> This were default settings:
> 00004: 2.000 Mbit/s 0 ms 30 sl. 1 queues (1 buckets) droptail
> mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000
> BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes Pkt/Byte
> Drp
> 0 tcp 192.168.x.x/1037 y.y.y.y/80 299073 117448216 0 0 1
>
> New settings are the same but with 50 sl. instead of former 30.
> Is this number of slots in queue?
> How can I change it to former settings?
> Can anyone help me please?
>

You should probably take a gander at the man page for ipfw.
http://www.freebsd.org/cgi/man.cgi?query=ipfw&apropos=0&sektion=0&manpath=FreeBSD+4.7-stable&format=html

50 slots is the default.

`ipfw pipe config 4 bw 2 Mbit/s queue 50` should "reset" your current
pipe.

good luck,
greg

------------------------------

Date: Tue, 11 Feb 2003 11:03:19 -0500
From: Jason Andresen <jand...@mitre.org>
Subject: Re: PCI oddity

Steven wrote:
> I have an abit bx133 board with a similar problem. The box runs linux, but
> experienced the same problem in the same place, when it was probing the
> drives. I narrowed the problem down to lack of IRQ's. Here's what I did to
> work around this:
>
> Go into the BIOS, disable the Serial and Parallel if you don't need them.
> You may also need to set IRQs 3,4,7 to PCI instead of ISA on that board.
> Look under the PCI section, if it exists. You should be able to specify
> IRQ's for several of the PCI slots, try playing with those. Turn off
> Plug'n'Play OS Installed, give it a whirl, or turn it on (I've some some
> luck with this on other boxes). I had to turn off PnP OS, specify different
> IRQ's for each PCI slot to force them not to share, and have all unused
> hardware disabled to free up IRQ's.
>
> Hopefully this will be of some use to you :)

Thanks for the tip, but I've already tried that. I turned off both
serial ports and the parallel port and hardwired all of the IRQs down.
It didn't help. If there was a card in both the fourth and fifth slot
it crashed on probe anyway.

Plus I got a lot of stray IRQ7s. This machine isn't all that tight for
IRQ space anyway because it has no soundcard or ISA hardware. I think I
still have a couple of free IRQs. IIRC, PCI only specifies 4 IRQ lines
for the cards though, so you have to share if you have more than 4 PCI
slots. Is this correct?

I'm still curious if this is a problem with FreeBSD, with my
motherboard, or with the Cards themselves. Is it unusual for a card to
share nicely? Not one manual for any of my cards even mentions IRQ
sharing.

- --
\ |_ _|__ __|_ \ __| Jason Andresen jand...@mitre.org
|\/ | | | / _| Network and Distributed Systems Engineer
_| _|___| _| _|_\___| Office: 703-883-7755

------------------------------

Date: Tue, 11 Feb 2003 11:28:28 -0500
From: Bill Moran <wmo...@potentialtech.com>
Subject: Re: PCI oddity

Jason Andresen wrote:
> I'm still curious if this is a problem with FreeBSD, with my
> motherboard, or with the Cards themselves. Is it unusual for a card to
> share nicely? Not one manual for any of my cards even mentions IRQ
> sharing.

Then they probably don't. IRQ sharing is one of those things that cards
usually brag about if they support.

If you have non-sharing cards trying to use a shared interrupt, it won't
work. Crashes don't surprise me under these circumstances.

- --
Bill Moran
Potential Technologies
http://www.potentialtech.com

------------------------------

Date: Tue, 11 Feb 2003 18:24:25 +0000
From: Mathias K.Straede. <se...@unifix.org>
Subject: subscribe freebsd-stable

------------------------------

Date: Wed, 12 Feb 2003 07:53:56 +0600
From: Max Khon <fj...@iclub.nsu.ru>
Subject: Re: libc_r seems to be broken in 4.7-STABLE as of Jan 27

hi, there!

On Mon, Feb 03, 2003 at 04:19:50PM +0100, Jonas Bulow wrote:

> There seems to be a problem in libc_r causing processes to hang
> (spinning) during startup of the process.
>
> It happens when the box is very busy. I got the back trace below using
> gcore on such a spinning process. The process consumed like 70% CPU.
>
> Has this been seen before? What more can I do to help solve the problem?
>
> The is a diskless box without swap. It's likely it went out of memory.

hmm, I've never seen such behaviour.
Can you try to make a simple program which will reproduce this weird
behaviour?

/fjoe

------------------------------

Date: Wed, 12 Feb 2003 02:47:12 -0400 (AST)
From: The Hermit Hacker <scr...@hub.org>
Subject: Work-Around for 'BTX Halted' issue ... does one exist?

G'day all ...

I have a server (Tyan L-ET MB, Adaptec 2000s controller, FreeBSD
4.7-STABLE) that started to give me a BTX Halted error message ... so far,
I haven't been able to find a solution to the problem ... is there some
way of booting the server off of floppies, maybe? I'm going to keep it
inhouse, as I don't mind having to do a little work to get it rebooted,
but would really prefer to keep FreeBSD on it if I can ... ?

Help?

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scr...@hub.org secondary: scrappy@{freebsd|postgresql}.org

------------------------------

End of stable-digest V5 #791
****************************

To Unsubscribe: send mail to majo...@FreeBSD.org
with unsubscribe freebsd-stable-digest in the body of the message