Date: Tue, 20 Nov 2001 14:17:42 -0500 (EST) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: Jake Burkholder <jake@locore.ca> Cc: sparc@FreeBSD.org Subject: Re: cvs commit: src/sys/sparc64/sparc64 tick.c Message-ID: <200111201917.fAKJHg037790@khavrinen.lcs.mit.edu> In-Reply-To: <20011119205100.D12724@locore.ca> References: <200111180347.fAI3lU882795@freefall.freebsd.org> <200111180349.fAI3nqE74701@khavrinen.lcs.mit.edu> <20011118163306.A12724@locore.ca> <200111190028.fAJ0SEa10262@khavrinen.lcs.mit.edu> <20011119013640.C12724@locore.ca> <200111191829.fAJITqi21292@khavrinen.lcs.mit.edu> <20011119205100.D12724@locore.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Mon, 19 Nov 2001 20:51:00 -0500, Jake Burkholder <jake@locore.ca> said: > I've updated main_sym.gz, please try it again. Latest results: it finds the symbios controller (using the sym driver) and then panics: panic: iommo_dvmamap_load: boundary could not be maintained: boundary 16777216 (2048), offset 2042, start 393222, end 393222 (Yes, that message really does say `iommo'.) Traceback is: iommu_dvmamap_load+0x178 psycho_dmamap_load+0x28 sym_setup_data_and_start+0x88 sym_action1+0x410 sym_action+0x8 xpt_run_dev_sendq+0x208 xpt_release_devq_device+0xdc xpt_release_devq_timeout+0xc softclock+0x1a0 ithread_loop+0x1f8 fork_exit+0x5c fork_trampoline+0xa4 The sym driver makes some other noises earlier in the boot, but there seems to be no way to stop the probe (or show msgbuf in ddb) to actually see what it says. (It's rather inconvenient to hook up a serial console at the moment, assuming a VT340 would make this any easier.) I'm rather puzzled by the panic; I don't think it should be possible given the way the resource manager is supposed to work. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-sparc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200111201917.fAKJHg037790>