From owner-freebsd-hackers Thu Jun 20 10:20:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA25914 for hackers-outgoing; Thu, 20 Jun 1996 10:20:38 -0700 (PDT) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA25908 for ; Thu, 20 Jun 1996 10:20:35 -0700 (PDT) Received: from gemini.sdsp.mc.xerox.com ([13.231.132.20]) by alpha.xerox.com with SMTP id <19133(11)>; Thu, 20 Jun 1996 10:14:45 PDT Received: from gnu.mc.xerox.com (gnu.sdsp.mc.xerox.com) by gemini.sdsp.mc.xerox.com (4.1/SMI-4.1-TB) id AA12366; Thu, 20 Jun 96 13:14:12 EDT Received: by gnu.mc.xerox.com (4.1/SMI-4.1) id AA05479; Thu, 20 Jun 96 13:14:10 EDT Message-Id: <9606201714.AA05479@gnu.mc.xerox.com> To: hackers@freebsd.org Subject: panics using Pioneer 624/adaptac 1522 Date: Thu, 20 Jun 1996 10:14:09 PDT From: "Marty Leisner" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is my combination of adaptec 1522/Pioneer 624 supposed to be reliable with 5/1/96? With linux I get very fast failures. (and panics). With freebsd, I get sparser failures (but also get panics) How do I save/find what was printed out in the panic? This seems to be happening when I try an mount an empty slot: WARNING: / was not properly dismounted. cd1(aic0:2:1): timed out aic: invalid reselect (idbit=0x 4) aic at line 2077: identify failed # And after that, the next mount fails with a panic (fata trap 12) This seems like a consistent sequence: mount some slots (works fine) mount an empty slot (mount fails with the above error) mount another slot (panic...) Is there a way to not have automatic reboots after panic? Or what do I use to get to the cause of the panic after a reboot (if I can). Linux has a utility (ksymoops) which I found useful...its takes the output of the panic and figures out where it is in the current kernel... Another problem is after this my / file system seemed to have major problems (fsck failed, I did an fsck -y and fixed about 30 errors). After, I was missing /usr and /dev/ttyp[0-9] had strange ownership/permissions [along with other problems I probably haven't found yet]. When I tried to rsh into the machine (everything else appeared to be working) I got: "not enough ptys" So I removed ttyp[0-9], did mknod (looking at anouther freebsd 2.1 system) [MAKEDEVICE ttyp0 appear to work), rebooted, and -- the same thing... marty leisner@sdsp.mc.xerox.com Member of the League for Programming Freedom (http://www.lpf.org) Any sufficiently advanced technology is indistinguishable from magic Arthur C. Clarke, The Lost Worlds of 2001