Date: Tue, 16 Jun 1998 17:07:20 +0200 (MET DST) From: Cejka Rudolf <xcejka00@dcse.fee.vutbr.cz> To: dwhite@resnet.uoregon.edu Cc: freebsd-questions@FreeBSD.ORG Subject: Re: DISKLESS and fxp0 problems Message-ID: <199806161507.PAA03499@sts.dcse.fee.vutbr.cz> In-Reply-To: <Pine.BSF.3.96.980615205243.2150J-100000@gdi.uoregon.edu> from Doug White at "Jun 15, 98 08:53:00 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> On Fri, 12 Jun 1998, Cejka Rudolf wrote:
>
> > I have big problem with DISKLESS box with "Intel EtherExpress Pro 10/100B
> > Ethernet" cards. Does anybody use (successfully) this configuration?
> >
> > I have one compiled kernel (2.2.X or -CURRENT: all is the same) for both
> > SMC cards (ed0) and EtherExpress cards (fxp0). And if I try to boot this
> > kernel on computer with SMC card, everything is ok. But if I try to boot
> > exactly the same kernel on computer with EtherExpress card, kernel stops
> > in BOOTP stage:
> >
> > bootpc_init: using network interface 'fxp0'
> > Bootpc testing starting
> > bootpc hw address is 0:aa:0:bc:af:59
> >
> > and after this, I see only repeated error messages:
> >
> > BOOTP timeout for server 0xffffffff
> > fxp0: device timeout
> >
> > (It is possible no BOOTP packet was sent - it looks like that there is bug
> > in kernel in initialization stage for fxp0.)
> Doug White wrote:
>
> Are the Intel and SMC cards using the same IRQ? Do you know that the
> Intel works otherwise?
Thanks for your interest!
At this time, I have much more information - and more important (I hope):
We tried to measure network traffic. On fxp0 in diskless BOOTP stage,
good BOOTP packet is sent (so fxp0 broadcasting works) and good reply
from BOOTP server is sent too. But kernel still waits and writes
"fxp0: device timeout" (so fxp0 receiving doesn't work).
On the same box with Intel EtherExpress Pro 10/100B card, I have installed
FreeBSD-CURRENT. When I'm trying local boot (directly from EasyBoot, before
any EEPro/100B configuration - I think), everything is OK.
Here are the boot messages:
--------------------------------------------------------------------------
Copyright (c) 1992-1998 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 3.0-CURRENT #7: Wed May 27 09:58:35 CEST 1998
xcejka00@pccejkar.dcse.fee.vutbr.cz:/usr/src/sys/compile/USER
Calibrating clock(s) ... TSC clock: 119744920 Hz, i8254 clock: 1193113 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter "i8254" frequency 1193182 Hz cost 2844 ns
CLK_USE_TSC_CALIBRATION not specified - using old calibration method
Timecounter "TSC" frequency 119752561 Hz cost 206 ns
CPU: Pentium/P54C (119.75-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)
Physical memory chunk(s):
0x00001000 - 0x0009ffff, 651264 bytes (159 pages)
0x0026a000 - 0x01ffdfff, 31014912 bytes (7572 pages)
avail memory = 30179328 (29472K bytes)
Found BIOS32 Service Directory header at 0xf00fb370
Entry = 0xfb850 (0xf00fb850) Rev = 0 Len = 1
PCI BIOS entry at 0xb880
Other BIOS signatures found:
ACPI: 00000000
$PnP: 000fc160
pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c
pci_open(1a): mode1res=0x80000000 (0x80000000)
pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=122d8086)
Probing for devices on PCI bus 0:
found-> vendor=0x8086, dev=0x122d, revid=0x02
class=06-00-00, hdrtype=0x00, mfdev=0
chip0: <Intel 82437FX PCI cache memory controller> rev 0x02 on pci0.0.0
CPU Inactivity timer: clocks
Peer Concurrency: enabled
CPU-to-PCI Write Bursting: enabled
PCI Streaming: enabled
Bus Concurrency: enabled
Cache: 256K asynchronous secondary; L1 enabled
DRAM: no memory hole, 60 MHz refresh
Read burst timing: x-2-2-2/x-3-3-3
Write burst timing: x-3-3-3
RAS-CAS delay: 3 clocks
found-> vendor=0x8086, dev=0x122e, revid=0x02
class=06-01-00, hdrtype=0x00, mfdev=1
chip1: <Intel 82371FB PCI to ISA bridge> rev 0x02 on pci0.7.0
I/O Recovery Timing: 8-bit 3.5 clocks, 16-bit 3.5 clocks
Extended BIOS: disabled
Lower BIOS: enabled
Coprocessor IRQ13: enabled
Mouse IRQ12: disabled
Interrupt Routing: A: IRQ11, B: IRQ10, C: disabled, D: disabled
MB0: IRQ15, MB1: disabled
found-> vendor=0x8086, dev=0x1230, revid=0x02
class=01-01-80, hdrtype=0x00, mfdev=0
ide_pci0: <Intel PIIX Bus-master IDE controller> rev 0x02 on pci0.7.1
intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1
intel_piix_status: primary master fastDMAonly disabled, pre/post enabled,
intel_piix_status: IORDY sampling enabled,
intel_piix_status: fast PIO enabled
intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1
intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled,
intel_piix_status: IORDY sampling disabled,
intel_piix_status: fast PIO disabled
ide_pci: busmaster 0 status: 04 from port: 0000e802
intel_piix_status: secondary master/slave sample = 4, master/slave recovery = 2
intel_piix_status: secondary master fastDMAonly disabled, pre/post enabled,
intel_piix_status: IORDY sampling enabled,
intel_piix_status: fast PIO enabled
intel_piix_status: secondary master/slave sample = 4, master/slave recovery = 2
intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled,
intel_piix_status: IORDY sampling disabled,
intel_piix_status: fast PIO disabled
ide_pci: busmaster 1 status: 04 from port: 0000e80a
found-> vendor=0x5333, dev=0x5631, revid=0x05
class=03-00-00, hdrtype=0x00, mfdev=0
intpin=a, irq=10
map[0]: type 1, range 32, base f4000000, size 26
vga0: <S3 ViRGE graphics accelerator> rev 0x05 int a irq 10 on pci0.11.0
found-> vendor=0x8086, dev=0x1229, revid=0x01
class=02-00-00, hdrtype=0x00, mfdev=0
intpin=a, irq=11
map[0]: type 3, range 32, base fbfef000, size 12
map[1]: type 4, range 32, base 0000e400, size 5
map[2]: type 1, range 32, base f3f00000, size 20
fxp0: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x01 int a irq 11 on pci0.12.0
fxp0: Ethernet address 00:aa:00:bc:af:59
bpf: fxp0 attached
Probing for devices on the ISA bus:
sc0: the current keyboard controller command byte 0047
kbdio: DIAGNOSE status:0055
kbdio: TEST_KBD_PORT status:0000
kbdio: RESET_KBD return code:00fa
kbdio: RESET_KBD status:00aa
sc0 at 0x60-0x6f irq 1 on motherboard
sc0: BIOS video mode:3
sc0: VGA registers upon power-up
50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81
bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96
b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c
3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff
sc0: video mode:24
sc0: VGA registers in BIOS for mode:24
50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81
bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96
b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c
3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff
sc0: VGA registers to be used for mode:24
50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81
bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96
b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c
3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff
sc0: rows_offset:1
sc0: VGA color <8 virtual consoles, flags=0x0>
sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
sio2: disabled, not probed.
sio3: disabled, not probed.
lpt0 at 0x378-0x37f irq 7 on isa
lpt0: Interrupt-driven port
lp0: TCP/IP capable interface
bpf: lp0 attached
lpt1 not found
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1.44MB 3.5in
wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ff on isa
wdc0: unit 0 (wd0): <QUANTUM FIREBALL1080A>, 32-bit, multi-block-8
wd0: 1039MB (2128896 sectors), 2112 cyls, 16 heads, 63 S/T, 512 B/S
wd0: ATA INQUIRE valid = 0003, dmamword = 0407, apio = 0003, udma = 0000
wdc1 at 0x170-0x177 irq 15 flags 0xa0ff on isa
wdc1: unit 0 (wd2): <WDC AC2420H>, 32-bit, multi-block-16
wd2: 405MB (830760 sectors), 989 cyls, 15 heads, 56 S/T, 512 B/S
wd2: ATA INQUIRE valid = 0003, dmamword = 0003, apio = 0001, udma = 0000
npx0 on motherboard
npx0: INT 16 interface
i586_bzero() bandwidth = 94984802 bytes/sec
bzero() bandwidth = 47693995 bytes/sec
apm0: disabled, not probed.
imasks: bio c008c040, tty c007089a, net c007089a
BIOS Geometries:
0:020e3f3f 0..526=527 cylinders, 0..63=64 heads, 1..63=63 sectors
1:03db0e38 0..987=988 cylinders, 0..14=15 heads, 1..56=56 sectors
0 accounted for
Device configuration finished.
Intel Pentium F00F detected, installing workaround
bpf: tun0 attached
bpf: sl0 attached
bpf: ppp0 attached
new masks: bio c008c040, tty c007089a, net c007089a
bpf: lo0 attached
ccd0-3: Concatenated disk drivers
Considering FFS root f/s.
wd0s1: type 0x6, start 63, end = 1024127, size 1024065 : OK
wd0s2: type 0xa5, start 1024128, end = 2128895, size 1104768 : OK
Start pid=2 <pagedaemon>
Start pid=3 <vmdaemon>
Start pid=4 <syncer>
wd2s1: type 0x6, start 56, end = 829919, size 829864 : OK
--------------------------------------------------------------------------
And good "netstat -I fxp0" output:
--------------------------------------------------------------------------
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
fxp0 1500 <Link> 00.aa.00.bc.af.59 20358 0 63 0 2
fxp0 1500 147.229.9/24 pccejkar 20358 0 63 0 2
--------------------------------------------------------------------------
But if I'm trying to boot via "fbsdboot.exe -v" after EEPro/100B BootROM
configuration, problems are the same as DISKLESS: "fxp0: device timeout"...
Strickly speaking: After computer reboot, I can select, if I want to
use network or local boot. If I use local boot, results are as above.
If I use network boot, I can change EEPro/100B configuration:
--------------------------------------------------------------------------
BootWare/Intel Ethernet Adapter Configuration Utility
Adapter: EtherExpress PRO/100B Version: 1.00
Node Adress: 00AA00BCAF59 Bus: PCI
IOBase: E400h
IRQ: 11
RomBase: C800h
Media: AutoSelect
Boot Protocol: NetWare_802.2
Default Boot: Local
Local Boot: Enabled
ROMShield: Disabled
--------------------------------------------------------------------------
After this, computer boots DOS from Novell NetWare. And after
DOS boot, I write:
--------------------------------------------------------------------------
fbsdboot.exe -v
--------------------------------------------------------------------------
And problems are the same - kernel repeatedly (and all the time)
writes "fxp0: device timeout" and network interface is totally unusable.
During starting "routed" and "sendmail", delays are too big.
Here is message from /var/log/messages:
--------------------------------------------------------------------------
Jun 16 15:56:19 pccejkar routed[64]: sendto(fxp0, 224.0.0.2): No route to host
--------------------------------------------------------------------------
And still "fxp0: device timeout"...
Here is diff between good (local) and bad (fbsdboot.exe) boot:
--------------------------------------------------------------------------
16c16
< 0x00001000 - 0x0009ffff, 651264 bytes (159 pages)
---
> 0x00001000 - 0x0009efff, 647168 bytes (158 pages)
18c18
< avail memory = 30179328 (29472K bytes)
---
> avail memory = 30175232 (29468K bytes)
25c25
< pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c
---
> pci_open(1): mode 1 addr port (0x0cf8) is 0x80006018
123c123
< lpt1 not found
---
> lpt1 at 0x4e57-0x4e5e on isa
--------------------------------------------------------------------------
The most interesting is difference on line 25: 0x8000005c -> 0x80006018.
And here is "netstat -I fxp0" output after "fbsdboot.exe -v" boot:
--------------------------------------------------------------------------
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
fxp0 1500 <Link> 00.aa.00.bc.af.59 2766 0 2047 22 151
fxp0: device timeout
fxp0: device timeout
...
--------------------------------------------------------------------------
--------------------------------------------------------------------------
Rudolf Cejka E-mail: xcejka00@dcse.fee.vutbr.cz
Technical University of Brno, Faculty of El. Engineering and Comp. Science
Bozetechova 2, 612 66 Brno, Czech Republic
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?199806161507.PAA03499>