Date: Mon, 26 Jun 1995 13:35:28 +0200 From: Stefan Petri <petri@ibr.cs.tu-bs.de> To: jan@todonix.ping.de Cc: rgrimes@gndrsh.aac.dev.com, bugs@FreeBSD.org Subject: re: 2.05R reboot hangs - BROKEN_KEYBOARD_RESET solved it for me Message-ID: <199506261135.NAA04299@achill.ibr.cs.tu-bs.de> In-Reply-To: Jan Wedekind's message of Sun, 25 Jun 1995 15:11:00 %2B0200 (MET DST) <m0sPrSo-00076UC@todonix.ping.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi!
Well , I did a diff between the 950412-SNAP and the 2.0.5 sources
This shows that the ``BROKEN_KEYBOARD_RESET'' option got a meaning in
2.0.5 butnot in the previous SNAP (i386/i386/vm_machdep.c::cpu_reset()).
That explains well the different reboot-behaviour. I have added the
option to my kernel, and now could reboot several times in a row w/o
problem :-)
OTOH: changing the ISA-GAT or the Cache-Update-Policy in the
BIOS-setup did not alter the reboot behaviour in any deterministic
way.
(How would I recognize an ISA bus master if I had one?)
(Cache-Update was default set to write-back, though apparently
there is no TAG-RAM-Chip on the board - but I did not get any
unexplanable SIGSEGs ;-)
My SCSI-bus is triple-terminated, because I inherited some antique
Sun3-shoeboxes that would need to be disassembled completely to remove
the terminators, and FreeBSD, Linux and DOS/Windoze work ok with it.
for the records:
Inscription on motherboard: PCI/I-486 SP3G Rev 1.8
Intel 486/DX4 SL at 100MHz
Award BIOS V4.50G
NCR PCI-3.06.00
NCR SDMS(TM) V3.0 V2 pl21
BIOS revision string from bottom of screen: 10/21/94-Saturn-II-P/I-SP3G-00
Output from dmesg after booting:
FreeBSD 2.0.5-RELEASE #2: Mon Jun 26 12:58:34 MET DST 1995
root@jupiter:/usr/src/sys/compile/JUPITER
CPU: i486 DX4 (486-class CPU)
Origin = "GenuineIntel" Id = 0x480 Stepping=0
Features=0x3<FPU,VME>
real memory = 16384000 (4000 pages)
avail memory = 14995456 (3661 pages)
Probing for devices on the ISA bus:
ed0 at 0x300-0x31f irq 10 maddr 0xcc000 msize 8192 on isa
ed0: address 00:00:c0:1a:d0:a0, type SMC8416C/SMC8416BT (16 bit)
bpf: ed0 attached
vt0 at 0x60-0x6f irq 1 on motherboard
vt0: unkown s3, 80 col, color, 8 scr, mf2-kbd, [R3.20-b24]
lpt0 at 0x378-0x37f irq 7 on isa
lpt0: Interrupt-driven port
lp0: TCP/IP capable interface
sio0 at 0x3f8-0x3ff irq 4 on isa
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
pca0 on motherboard
pca0: PC speaker audio driver
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: NEC 72065B
fd0: 1.44MB 3.5in
el0 at 0x280 irq 5 on isa
el0: 3c501 address 02:60:8c:92:75:30
bpf: el0 attached
npx0 on motherboard
npx0: INT 16 interface
Probing for devices on the pci0 bus:
configuration mode 2 allows 16 devices.
chip0 <Intel 82424ZX cache DRAM controller> rev 4 on pci0:0
ncr0 <ncr 53c810 scsi> rev 1 int a irq 9 on pci0:1
reg20: virtual=0xf2a58000 physical=0xfbfef000 size=0x100
ncr0: restart (scsi reset).
ncr0 scanning for targets 0..6 (V2 pl21 95/03/21)
(ncr0:1:0): "QUANTUM LIGHTNING 730S 241E" type 0 fixed SCSI 2
sd0(ncr0:1:0): Direct-Access
sd0(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8.
699MB (1431760 512 byte sectors)
sd0(ncr0:1:0): with 3658 cyls, 4 heads, and an average 97
sectors/track
chip1 <Intel 82378IB PCI-ISA bridge> rev 132 on pci0:2
vga0 <Display device> rev 0 on pci0:4
pci0: uses 8388864 bytes of memory from fb000000 upto fbfef0ff.
pci0: uses 256 bytes of I/O space from e800 upto e8ff.
bpf: lo0 attached
well , now that rebooting seems to work properly, remains the question
why such an odd the disk geometry is reported (Linux and the
previous SNAP release both get the correct geometry ...)
Stefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506261135.NAA04299>