Date: Sat, 30 Sep 2000 23:35:37 +0200 From: Bernd Walter <ticso@cicely8.cicely.de> To: freebsd-alpha@freebsd.org Subject: I still have problems booting into su-mode with ithread patches Message-ID: <20000930233536.A83846@cicely8.cicely.de>
next in thread | raw e-mail | index | archive | help
Since the first version I tested current with the ithread patches on my PC164 I can see it hanging during boot and if I press the halt button I catch it always with the pointer after the call pal operation of alpha_pal_swpipl(). First it was an spl call now that they are removed I catch it within mtx_exit of the sched_lock resource. I even set it explicitly to ALPHA_PSL_IPL_0 when releasing a mutex. I asume that I catch it always at these point because it's spending most time there and not because the call pal itself is hanging. During the boot process the hanging is always during scsi-bus probing. With an earlier version of the patches it sometime made it to adding the devices to the kernel tables. Is anyone who got it running using a system with multiple scsi channels and/or multiple devices and/or seriel console? As I'm catching it in releasing sched_lock after calling mi_switch the scheduler still seems to work. The only debugging functionality I know of is the objdump -S output from the kernel and the halt-button. Does anyone know more I can try - I can't enter ddb with a break. Is there any way to look into the witness output using SRM? -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000930233536.A83846>