From owner-freebsd-alpha Wed Jan 24 7:52:48 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 3519C37B400; Wed, 24 Jan 2001 07:52:26 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA17470; Wed, 24 Jan 2001 10:52:25 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id f0OFqPM17479; Wed, 24 Jan 2001 10:52:25 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 24 Jan 2001 10:52:25 -0500 (EST) To: John Baldwin Cc: freebsd-alpha@FreeBSD.ORG Subject: RE: -current failing on PC164 In-Reply-To: References: <14958.59036.411197.382347@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14958.63910.53261.732597@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John Baldwin writes: > > On 24-Jan-01 Andrew Gallatin wrote: > > > > Bernd's problem was an unaligned access error, probably in the > > witness > > or mutex debug code. This (probably) has nothing to do with pmap > > problems. > > No, they were the fault of my own stupidity. :-P I bothced some > KASSERT()'s. *sigh* FWIW, I built a kernel this morning with the following debugging options to try to duplicate Bernd's problems: options DIAGNOSTIC options MUTEX_DEBUG options WITNESS options INVARIANTS options INVARIANT_SUPPORT options KTR options KTR_EXTEND options KTR_ENTRIES=1024 When booting, I see this: Timecounter "alpha" frequency 598973881 Hz dc0 XXX: driver didn't initialize queue mtx re-initing existing mutex dc fxp0 XXX: driver didn't initialize queue mtx re-initing existing mutex fxp lo0 XXX: driver didn't initialize queue mtx re-initing existing mutex lo ad0: 6149MB [12495/16/63] at ata0-master UDMA33 acd0: CDROM at ata1-master using PIO4 (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. Mounting root from ufs:/dev/da0a da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) panic: mutex_enter(sio:1, MTX_SPIN) out of order @ ../../isa/sio.c:2287 already holding sched lock:2 syncing disks... done Uptime: 6s So, are serial console's hosed?? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message