From owner-freebsd-questions Wed Jul 30 00:00:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA14320 for questions-outgoing; Wed, 30 Jul 1997 00:00:15 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA14272; Wed, 30 Jul 1997 00:00:03 -0700 (PDT) Received: (grog@localhost) by freebie.lemis.com (8.8.6/8.6.12) id QAA00658; Wed, 30 Jul 1997 16:29:31 +0930 (CST) From: grog@FreeBSD.ORG Message-Id: <199707300659.QAA00658@freebie.lemis.com> Subject: Re: can't get panic dump In-Reply-To: <5rmm46$1b5@twwells.com> from "T. William Wells" at "Jul 30, 97 02:15:31 am" To: bill@twwells.com (T. William Wells) Date: Wed, 30 Jul 1997 16:29:31 +0930 (CST) Cc: questions@FreeBSD.ORG (FreeBSD Questions), scsi@FreeBSD.ORG Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk T. William Wells writes: > I'm running 2.2.2-RELEASE. I have 32M of RAM. I have bounce > buffers in my config. The SCSI controller is an Adaptec 1540. It > dumps 16M and then at the 16M boundary complains about DMA beyond > end of ISA and stops dumping. Any ideas? I think you've hit a bug. > Config and boot messages appended (from a run with 16M, where I > can get a complete dump). > > machine "i386" > cpu "I486_CPU" > ident TWWELLS > maxusers 16 > config kernel root on sd0 > > options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] > options BOUNCE_BUFFERS This is the option that *should* prevent the "DMA beyond end of ISA" message. But I'm getting it too. One minor nit: obviously you are running beyond the 16 MB boundary. But your dmesg output shows only 16 MB. I'm guessing that you've disabled the other half in order to get the machine to run. Is there anything else in the dmesg output which is less obvious? I'm forwarding this to the SCSI mailing list, where I just sent a similar message describing my own problems. If there's anybody else out there on -questions who are having this problem, please let us know. Greg > options UCONSOLE #Allow users to grab the console > options SYSVSHM > options SYSVSEM > options SYSVMSG > > options INET #InterNETworking > options IPFIREWALL #firewall > options IPDIVERT #divert sockets > > options FFS #Fast filesystem > options "CD9660" #ISO 9660 filesystem > options PROCFS #Process filesystem > > options DDB > options DDB_UNATTENDED > options KTRACE #kernel tracing > options USERCONFIG #boot -c editor > options VISUAL_USERCONFIG #visual boot -c editor > options MAXCONS=16 # number of virtual consoles > options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device > options CHILD_MAX=128 > > controller isa0 > device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr > device npx0 at isa? port "IO_NPX" iosiz 0x0 flags 0x0 irq 13 vector npxintr > device pca0 at isa? port IO_TIMER1 tty > > device lpt0 at isa? port? tty irq 7 vector lptintr > device sio0 at isa? port 0x3F8 tty irq 4 vector siointr > device sio1 at isa? port 0x2F8 tty irq 3 vector siointr > device sio2 at isa? port 0x3E8 tty irq 9 vector siointr > device sio3 at isa? port 0x2E8 tty irq 5 vector siointr > device ed0 at isa? port 0x220 net irq 15 iomem 0xd8000 vector edintr > device mcd0 at isa? port 0x300 bio irq 10 drq 6 vector mcdintr > > controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr > disk fd0 at fdc0 drive 0 > disk fd1 at fdc0 drive 1 > > controller scbus0 #base SCSI code > device sd0 #SCSI disks > device st0 #SCSI tapes > > controller aha0 at isa? port "IO_AHA0" bio irq 11 drq 5 vector ahaintr > > pseudo-device ether #Generic Ethernet > pseudo-device loop #Network loopback device > pseudo-device bpfilter 4 #Berkeley packet filter > pseudo-device disc #Discard device > pseudo-device tun 4 #Tunnel driver (user process ppp) > > pseudo-device pty 64 #Pseudo ttys - can go as high as 256 > pseudo-device speaker #Play IBM BASIC-style noises out your speaker > pseudo-device log #Kernel syslog interface (/dev/klog) > pseudo-device gzip #Exec gzipped a.out's > pseudo-device vn #Vnode driver (turns a file into a device) > pseudo-device snp 4 #Snoop device - to look at pty/vty/etc.. > > FreeBSD 2.2.2-RELEASE #0: Fri Jun 27 13:29:01 EDT 1997 > root@twwells.com:/usr/src/sys/compile/TWWELLS > CPU: i486DX (486-class CPU) > real memory = 16777216 (16384K bytes) > avail memory = 14819328 (14472K bytes) > Probing for devices on the ISA bus: > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: VGA color <16 virtual consoles, flags=0x0> > ed0 at 0x220-0x23f irq 15 on isa > ed0: address 00:50:4e:03:9d:8f, type NE2000 (16 bit) > 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 16450 > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16450 > sio2 at 0x3e8-0x3ef irq 9 on isa > sio2: type 16550A > sio3 at 0x2e8-0x2ef irq 5 on isa > sio3: type 16550A > pca0 on motherboard > pca0: PC speaker audio driver > mcd0: type Mitsumi FX001D, version info: D 2 > mcd0 at 0x300-0x303 irq 10 drq 6 on isa > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: NEC 765 > fd0: 1.44MB 3.5in > fd1: 1.2MB 5.25in > aha0 at 0x330-0x333 irq 11 drq 5 on isa > aha0 waiting for scsi devices to settle > (aha0:0:0): "QUANTUM FIREBALL_TM2110S 300X" type 0 fixed SCSI 2 > sd0(aha0:0:0): Direct-Access 2014MB (4124736 512 byte sectors) > (aha0:1:0): "CONNER CP30540 545MB3.5 B0BD" type 0 fixed SCSI 2 > sd1(aha0:1:0): Direct-Access 520MB (1065912 512 byte sectors) > npx0 on motherboard > npx0: INT 16 interface > IP packet filtering initialized, divert enabled, logging disabled