4 messages in org.freebsd.freebsd-bugsRe: dev_attach after boot (Re: modloa...| From | Sent On | Attachments |
|---|---|---|
| HOSOKAWA Tatsumi | Mar 21, 1996 5:43 am | |
| HOSOKAWA Tatsumi | Mar 21, 1996 6:43 am | |
| Paul Traina | Mar 21, 1996 10:09 am | |
| Garrett A. Wollman | Mar 21, 1996 12:14 pm |
| Subject: | Re: dev_attach after boot (Re: modloaded block/char device drivers) | |
|---|---|---|
| From: | HOSOKAWA Tatsumi (hoso...@mt.cs.keio.ac.jp) | |
| Date: | Mar 21, 1996 6:43:02 am | |
| List: | org.freebsd.freebsd-bugs | |
Sorry! I forgot to write about important experiences.
In article <1996...@frig.mt.cs.keio.ac.jp> hoso...@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: hoso...@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