Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 5 Feb 2000 19:51:19 -0800 (PST)
From:      wellsian <wellsian@caffeine.com>
To:        Chris Johnson <cjohnson@palomine.net>
Cc:        questions@FreeBSD.ORG
Subject:   Re: BT-958 timeouts
Message-ID:  <Pine.BSF.4.21.0002051929020.1795-100000@boris.netgate.net>
In-Reply-To: <20000205163107.A89996@palomine.net>

next in thread | previous in thread | raw e-mail | index | archive | help
We used a number of those cards in BSDI boxes and experienced the same
symptoms. What made it particularly annoying was the way it stopped the
world for all users everytime it happened. People don't seem to appreciate
their telnet sessions going away. Sometimes for as long as 30 seconds. :/
Those systems were eventually upgraded past the problems (new cards) and
we never knew the actual cause besides it only happening under significant
disk I/O load. (log processing and/or backups, etc.) We spent many hours
investigating termination, cabling, and drives among the different configs
but no joy. It may have been a driver issue. I _think_ the BSDI driver
(like many things) is derived from fbsd code. You might ask Buslogic
(mylex) if they know anything new.

Good luck,
Dave

On Sat, 5 Feb 2000, Chris Johnson wrote:

> I just installed 3.4-RELEASE (and subsequently updated it to 3.4-STABLE), and I
> get lots of this kind of thing:
> 
> Feb  5 15:49:44 buddy /kernel: bt0: No longer in timeout
> Feb  5 15:56:40 buddy /kernel: (da0:bt0:0:6:0): CCB 0xc4968e40 - timed out
> Feb  5 15:56:54 buddy /kernel: (da0:bt0:0:6:0): CCB 0xc4968e40 - timed out
> Feb  5 15:56:54 buddy /kernel: bt0: No longer in timeout
> Feb  5 16:01:41 buddy /kernel: (da0:bt0:0:6:0): CCB 0xc4966880 - timed out
> Feb  5 16:01:55 buddy /kernel: (da0:bt0:0:6:0): CCB 0xc4966880 - timed out
> Feb  5 16:01:55 buddy /kernel: bt0: No longer in timeout
> Feb  5 16:05:48 buddy /kernel: (da0:bt0:0:6:0): CCB 0xc4967680 - timed out
> Feb  5 16:06:02 buddy /kernel: (da0:bt0:0:6:0): CCB 0xc4967680 - timed out
> Feb  5 16:06:02 buddy /kernel: bt0: No longer in timeout
> 
> The SCSI controller is a PCI Buslogic BT-948, with ISA compatibility mode (or
> whatever it's called) turned on (which was suggested in an archive message).
> The system seems to recover just fine from this, and I've successfully built
> world twice. When it does occur, though, the system seems to hang for a bit and
> then just pick up where it left off. I don't think that there are any hardware
> problems--this same box recently had an uptime of 460 days running Linux, with
> no apparent SCSI issues.
> 
> I found a message in the archives in which someone else posted the same
> symptoms, but there hasn't been a response to it.
> 
> Are there any known issues with the bt0 driver? Are there SCSI options I need
> to enable or disable? Should I just replace the card with another, better
> supported one?
> 
> Below are the contents of dmesg.boot. Thanks in advance. 
> 
> Chris
> 
> Timecounter "i8254"  frequency 1193182 Hz
> Timecounter "TSC"  frequency 232669895 Hz
> CPU: AMD-K6tm w/ multimedia extensions (232.67-MHz 586-class CPU)
>   Origin = "AuthenticAMD"  Id = 0x562  Stepping = 2
>   Features=0x8001bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX>
>   AMD Features=0x400<<b10>>
> real memory  = 67108864 (65536K bytes)
> avail memory = 62857216 (61384K bytes)
> Bad DMI table checksum!
> Preloaded elf kernel "kernel" at 0xc0245000.
> Preloaded userconfig_script "/boot/kernel.conf" at 0xc024509c.
> Probing for devices on PCI bus 0:
> chip0: <Intel 82439HX PCI cache memory controller> rev 0x03 on pci0.0.0
> chip1: <Intel 82371SB PCI to ISA bridge> rev 0x01 on pci0.7.0
> bt0: <Buslogic Multi-Master SCSI Host Adapter> rev 0x08 int a irq 12 on pci0.18.0
> bt0: BT-948 FW Rev. 5.07B Ultra Narrow SCSI Host Adapter, SCSI ID 7, 192 CCBs
> vga0: <Trident model 9660 VGA-compatible display device> rev 0xd3 int a irq 9 on pci0.19.0
> fxp0: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x05 int a irq 10 on pci0.20.0
> fxp0: Ethernet address 00:a0:c9:cc:88:02
> Probing for PnP devices:
> Probing for devices on the ISA bus:
> sc0 on isa
> sc0: VGA color <16 virtual consoles, flags=0x0>
> atkbdc0 at 0x60-0x6f on motherboard
> atkbd0 irq 1 on isa
> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
> sio0: type 16550A
> sio1 at 0x2f8-0x2ff irq 3 on isa
> sio1: type 16550A
> fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
> fdc0: FIFO enabled, 8 bytes threshold
> fd0: 1.44MB 3.5in
> ppc0 at 0x378 irq 7 flags 0x40 on isa
> ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
> bt: unit number (1) too high
> bt1 not found at 0x330
> vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa
> npx0 on motherboard
> npx0: INT 16 interface
> IP packet filtering initialized, divert disabled, rule-based forwarding disabled, logging limite
> d to 100 packets/entry by default
> Waiting 10 seconds for SCSI devices to settle
> changing root device to da0s1a
> da0 at bt0 bus 0 target 6 lun 0
> da0: <QUANTUM FIREBALL SE4.3S PJ0A> Fixed Direct Access SCSI-2 device
> da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled
> da0: 4110MB (8418816 512 byte sectors: 255H 63S/T 524C)



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0002051929020.1795-100000>