Subject: Compaq Proliant 1000 486DX2/66MHz
To: None <port-i386@netbsd.org>
From: Chris Tribo <t1345@hopi.dtcc.edu>
List: port-i386
Date: 06/05/2001 17:44:52
I wandered past an old Compaq EISA system and decided to try the
1.5 boot.fs on it. I booted it up, but, it only detected 16MB out of the
32MB on the motherboard (should they be interleaved?). Then when I tried
to mount the floppy disk to write a dmesg, it paniced the system.
Dmesg copied by hand:
cpu0: Intel 486DX2 (486-class)
total memory = 16000MB
avail memory = 9964 KB
uusing 225 buffers containing 900 KB of memory
mainbus0 (root)
eisa0 at mainbus0
ahc1 at eisa0 slot 2: Adaptec AHA-274x SCSI
ahc1: level sensitive interrupting at irq 10
ahc1: aic7770 >= Rev E, Single Channel A, SCSI Id=7, 4/255 SCBs
scsibus0 at ahc1 channel 0: 8 targets, 8 luns per target
device CPQ4410 at eisa0 slot 8 not configured
isa0 mainbus 0
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
isapnp0 atisa0 port 0x279: ISA Plug 'n Play device support
npx0 atisa0 port 0xf0-0xff: using exception 16
pc0 at isa0 port 0x60-0x6f irq 1: color
pc0: console
fdc0 at isa0 port 0x4f0-0x3f7 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
isapnp0: no ISA Plug 'n Play device found
biomask ffe5 netmask ffe5 ttymask ffe7
scsibus0: waiting 2 seconds for device to settle...
md0: internal 2048K image area
boot device: fd0
root on md0a dumps on md0b
root file system type: ffs
#
#disklabel fd0
fd0d: hard error reading fsbn 0 (st0 40<abnrml> st1 1<no_am> st2 0 cyl 0
head 0 sec 1>
fd0d: hard error reading fsbn 1 (st0 40<abnrml> st1 1<no_am> st2 0 cyl 0
head 0 sec 2>
disklabel: ioctl DIOCGDINFO: Invalid argument
# disklabel fd0
uvm_fault(0xc264e178, 0xbfefe000, 0, 1) -> 1
kernel: page fault trap, code=0
stopped in sh at 0xc0251c72: movl 0(%esi,%eax,4),%ebx
db> trace
(null)(c0637348) at 0xc0251c72
(null)(c124dd50) at 0xc023966e
(null)(c265b0c8,c265a480,0,0,c2662d90) at 0xc0238c4b
(null)(c265a480,0) at 0xc0237c75
(null)(c265a480,0,c264e178,c2662e18,c265a480) at 0xc023e9d1
(null)(c264e178,0,bfbfe000,827e58c,c2662e18) at 0xc023dd3b
(null)(c26497e4,c26497e4,c2662f80,c036549c,c2662df8) at 0xc0240459
(null)(c26497e4,c2662f88,c2662f80,827e590,827e564) at 0xc017e408
(null)(bfbf001f,1f,827e590,827e564,bfbfdb90) at 0xc02536f9
db>
Any operations relating the fd seem to cause a panic, but I have
only looked at it in passing.
Chris (not on the i386 list)