Date: Sun, 8 May 2011 22:36:34 +0200 From: Joerg Wunsch <freebsd-scsi@uriah.heep.sax.de> To: freebsd-scsi@freebsd.org Subject: Re: Panic when removing a SCSI device entry Message-ID: <20110508203634.GE5364@uriah.heep.sax.de> In-Reply-To: <20110508113332.GX48734@deviant.kiev.zoral.com.ua> References: <20110508085314.GA5364@uriah.heep.sax.de> <20110508094509.GT48734@deviant.kiev.zoral.com.ua> <20110508104543.GB5364@uriah.heep.sax.de> <20110508113332.GX48734@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
As Kostik Belousov wrote: > > I could perhaps setup a serial console, so to get at least DDB > > functioning if you'd like to see more details. ... > Serial console is fine, I do want to see a backtrace. > There is also "show cdev" command in ddb, that might provide some > useful information. OK, I'm setting up a DDB kernel right now, and attached an old laptop as the console terminal. I also applied your suggested patch. > INVARIANTS may be also useful, since the kernel might catch the > corruption earlier. As INVARIANTS has a performance impact, I'd like to avoid that by now. Let's see first whether an analysis is possible without that. If not, would it suffice to just compile kern_conf.c with INVARIANTS? -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110508203634.GE5364>