From owner-freebsd-alpha Wed Jan 24 11:16:56 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 6657737B402; Wed, 24 Jan 2001 11:16:37 -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 OAA22312; Wed, 24 Jan 2001 14:16:36 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id f0OJGaa18132; Wed, 24 Jan 2001 14:16:36 -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 14:16:36 -0500 (EST) To: John Baldwin Cc: freebsd-alpha@FreeBSD.ORG Subject: RE: -current failing on PC164 In-Reply-To: References: <14959.8051.714883.875583@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14959.10557.921381.576255@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: > > > > John Baldwin writes: > > > > > > > > So, are serial console's hosed?? > > > > > > It could be a bug. :-P Can you add ddb and get a backtrace? > > > > > > > I'd like to.. but... I just CVSupp'ed and the same config no longer > > builds after your recent commits: > > Did you rerun config on your config file? mp_machdep.c is now no > longer needed for UP kernels. I will sit down and mkae sure I didn't > break SMP kernel builds for the alpha. OK.. After a re-configure, I get this: 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 panic Stopped at Debugger+0x2c: ldq ra,0(sp) <0xfffffe00062c3d00> db> tr Debugger() at Debugger+0x2c panic() at panic+0x100 witness_enter() at witness_enter+0x158 _mtx_enter() at _mtx_enter+0x278 siopoll() at siopoll+0x198 sithd_loop() at sithd_loop+0x8c exception_return() at exception_return db> The context for siopoll is: (gdb) l *siopoll+0x198 0xfffffc000064d7d8 is in siopoll (../../isa/sio.c:2287). 2282 mtx_exit(&sio_lock, MTX_SPIN); 2283 } 2284 if (com->state & CS_CHECKMSR) { 2285 u_char delta_modem_status; 2286 2287 mtx_enter(&sio_lock, MTX_SPIN); 2288 delta_modem_status = com->last_modem_status 2289 ^ com->prev_modem_status; 2290 com->prev_modem_status = com->last_modem_status; 2291 com_events -= LOTS_OF_EVENTS; And for sithd_loop+0x8c: (gdb) l *sithd_loop+0x8c 0xfffffc000042102c is in sithd_loop (../../kern/kern_intr.c:227). 222 (void *)ih->ih_handler, ih->ih_argument, 223 ih->ih_flags); 224 225 if ((ih->ih_flags & INTR_MPSAFE) == 0) 226 mtx_enter(&Giant, MTX_DEF); 227 ih->ih_handler(ih->ih_argument); 228 if ((ih->ih_flags & INTR_MPSAFE) == 0) 229 mtx_exit(&Giant, MTX_DEF); 230 } 231 } I don't understand the panic message -- why is it talking about sched lock when the mtx_enter is on sio_lock?? Cheers, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message