Date: Thu, 21 Mar 1996 10:09:35 -0800 From: Paul Traina <pst@shockwave.com> To: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi) Cc: bde@freebsd.org, hackers@freebsd.org, bugs@freebsd.org, jmz@freebsd.org Subject: Re: dev_attach after boot (Re: modloaded block/char device drivers) Message-ID: <199603211809.KAA02061@precipice.shockwave.com> In-Reply-To: Your message of "Thu, 21 Mar 1996 23:43:22 %2B0900." <199603211443.XAA08476@frig.mt.cs.keio.ac.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
Not all dynamic dev_attach() causes panic(). For example, if_ed NE2000 compatible PCMCIA Ethernet OK if_nep 3C589x PCMCIA Ethernet OK if_fe Fujitsu PCMCIA Ethernet OK wdc/wd Flash ATA / Type 3 ATA disk NG sio PCMCIA Modem OK aic/cd SCSI CDROM w/ SlimSCSI PCMCIA NG aic/sd SCSI HDD w/ SlimSCSI PCMCIA NG So, I think adding the controllers dynamically causes this panic(), but I was confused by reading that qcam has the same problem. Apparently, qcam is not controller/disk type device. Of course I read dev_attach() in kern_devconf.c and it seems to have no problem which causes such panic()'s. No, but the one common thread is that all of the ones that are OK register no character/block devices.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603211809.KAA02061>