From owner-freebsd-alpha Wed Jan 24 10:30:49 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from pike.osd.bsdi.com (unknown [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id DA45337B699 for ; Wed, 24 Jan 2001 10:30:30 -0800 (PST) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0OIUNx28319; Wed, 24 Jan 2001 10:30:23 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.1) id f0OITvv81355; Wed, 24 Jan 2001 10:29:57 -0800 (PST) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <14958.63910.53261.732597@grasshopper.cs.duke.edu> Date: Wed, 24 Jan 2001 10:29:57 -0800 (PST) Organization: BSD, Inc. From: John Baldwin To: Andrew Gallatin Subject: RE: -current failing on PC164 Cc: freebsd-alpha@FreeBSD.ORG Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 24-Jan-01 Andrew Gallatin wrote: > > 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?? It could be a bug. :-P Can you add ddb and get a backtrace? > Drew -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message