Date: Thu, 21 Mar 1996 23:43:22 +0900 From: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi) To: pst@shockwave.com, bde@freebsd.org, hackers@freebsd.org, bugs@freebsd.org, jmz@freebsd.org Cc: hosokawa@mt.cs.keio.ac.jp Subject: Re: dev_attach after boot (Re: modloaded block/char device drivers) Message-ID: <199603211443.XAA08476@frig.mt.cs.keio.ac.jp> In-Reply-To: Your message of Thu, 21 Mar 1996 22:44:16 %2B0900. <199603211344.WAA08147@frig.mt.cs.keio.ac.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
Sorry! I forgot to write about important experiences. In article <199603211344.WAA08147@frig.mt.cs.keio.ac.jp> hosokawa@mt.cs.keio.ac.jp writes: >> When I try to enable (hotplug) Flash ATA (wdc and wd) driver or SCSI >> devices (cd, sd, etc.), the kernel panic()'s by kernel page fault. >> >> I found it never panics when I commented out the calls of dev_attach() >> in those drivers. 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. Currently, I'm planning to write a quick hack patch that PCMCIA dynamic device enabler never calls dev_attach() if this problem can't solved for long. Does any can guess the reason of this fatal problem? Thanks. -- HOSOKAWA, Tatsumi E-mail: hosokawa@mt.cs.keio.ac.jp WWW homepage: http://www.mt.cs.keio.ac.jp/person/hosokawa.html Department of Computer Science, Keio University, Yokohama, Japan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603211443.XAA08476>