Date: Thu, 10 Sep 1998 21:55:26 +0200 (CEST) From: Wilko Bulte <wilko@yedi.iaf.nl> To: FreeBSD-hackers@FreeBSD.ORG (FreeBSD hackers list) Subject: alignment error in de driver Message-ID: <199809101955.VAA09032@yedi.iaf.nl>
next in thread | raw e-mail | index | archive | help
I'm currently evaluating an interesting (I think) PCI card that I borrowed
for that purpose. It is a card that houses a pair of NCR875 Ultra SCSI
chips and a DEC 21140A 10/100 mbit ethernet chip. To glue all of this
together there is also a DEC pci bridge chip.
I like this card because it has the potential to free some of my precious
PCI slots.
Initial tests indicate that FreeBSD 2.2.6 recognises everything just fine.
I tested one of the SCSI channels and it looks just fine with bonnie etc.
First need some SCSI devices to populate the second channel.
The ethernet also looks fine, although I can only test it with 10mbit
(no 100mbit at home yet). There is one phenomenon I don't get:
de0: receive: 00:00:24:06:32:56: alignment error
de0: receive: 00:00:24:06:32:56: alignment error
de0: receive: 00:00:24:06:32:56: alignment error
de0: receive: 00:00:24:06:32:56: alignment error
de0: receive: 00:00:24:06:32:56: alignment error
de0: receive: 00:00:24:06:32:56: alignment error
is displayed on the console. Just every now and then, it is currently
compile a kernel via NFS. Works just fine, save for the messages.
>From the source I find in if_de.c:
if (eop->d_status & TULIP_DSTS_RxBADCRC) {
if (eop->d_status & TULIP_DSTS_RxDRBBLBIT) {
sc->tulip_dot3stats.dot3StatsAlignmentErrors++;
error = "alignment error";
} else {
sc->tulip_dot3stats.dot3StatsFCSErrors++;
error = "bad crc";
}
Which is interesting but does not tell me why it happens. And what can be
done to fix it.
The bootmessages are:
FreeBSD 2.2.6-RELEASE #1: Thu Sep 10 19:19:24 CEST 1998
root@dac.iaf.nl:/usr/src.226/sys/compile/DAC
CPU: Pentium (99.47-MHz 586-class CPU)
Origin = "GenuineIntel" Id = 0x525 Stepping=5
Features=0x1bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8>
real memory = 33554432 (32768K bytes)
FreeBSD Kernel Configuration Utility - Version 1.1
Type "help" for help or "visual" to go to the visual
configuration interface (requires MGA/VGA display or
serial terminal capable of displaying ANSI graphics).
config> dis ed0
config> q
avail memory = 30752768 (30032K bytes)
Probing for devices on PCI bus 0:
chip0 <Intel 82437FX PCI cache memory controller> rev 1 on pci0:0:0
chip1 <Intel 82371FB PCI-ISA bridge> rev 2 on pci0:7:0
chip2 <Intel 82371FB IDE interface> rev 2 on pci0:7:1
chip3 <generic PCI bridge (vendor=1011 device=0024 subclass=4)> rev 2 on pci0:10:0
Probing for devices on PCI bus 1:
ncr0 <ncr 53c875 fast20 wide scsi> rev 4 int a irq 12 on pci1:0:0
ncr0 waiting for scsi devices to settle
(ncr0:0:0): "HITACHI DK517C-37 G5H3" type 0 fixed SCSI 2
sd1(ncr0:0:0): Direct-Access
sd1(ncr0:0:0): 10.0 MB/s (100 ns, offset 15)
2740MB (5611599 512 byte sectors)
ncr1 <ncr 53c875 fast20 wide scsi> rev 4 int a irq 9 on pci1:1:0
ncr1 waiting for scsi devices to settle
de0 <Digital 21140A Fast Ethernet> rev 34 int a irq 10 on pci1:2:0
de0: 21140A [10-100Mb/s] pass 2.2
de0: address 00:06:2b:00:16:c6
Probing for devices on the ISA bus:
sc0 at 0x60-0x6f irq 1 on motherboard
sc0: VGA color <16 virtual consoles, flags=0x0>
sio0 at 0x3f8-0x3ff irq 4 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
aha0 at 0x330-0x333 irq 11 drq 5 on isa
aha0 waiting for scsi devices to settle
(aha0:0:0): "DEC RZ28 (C) DEC 442C" type 0 fixed SCSI 2
sd0(aha0:0:0): Direct-Access 2007MB (4110480 512 byte sectors)
(aha0:4:0): "TOSHIBA CD-ROM XM-5301TA 0436" type 5 removable SCSI 2
cd0(aha0:4:0): CD-ROM can't get the size
npx0 flags 0x1 on motherboard
npx0: INT 16 interface
Intel Pentium F00F detected, installing workaround
de0: enabling 10baseT port
de0: link down: cable problem?
de0: link down: cable problem?
de0: autosense failed: cable problem?
de0: link down: cable problem?
de0: receive: 00:00:24:06:32:56: alignment error
de0: receive: 00:00:24:06:32:56: alignment error
In case anyone wonders: the cable problem message was indeed a bad cable.
This has been fixed in the meantime (the alignment errors persist after
the cable swap.
Matt, if you're listening: I'm talking about a Digital ^H^H^H^H^H^H^H Compaq
KZPCM adapter.
Insight appreciated,
Wilko
_ ______________________________________________________________________
| / o / / _ Bulte email: wilko@yedi.iaf.nl
|/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl
______________________________________________ Powered by FreeBSD __________
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809101955.VAA09032>