Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 21 Mar 1996 22:44:16 +0900
From:      hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi)
To:        pst@shockwave.com
Cc:        bde@freebsd.org, hackers@freebsd.org, bugs@freebsd.org, jmz@freebsd.org, hosokawa@mt.cs.keio.ac.jp
Subject:   dev_attach after boot (Re: modloaded block/char device drivers)
Message-ID:  <199603211344.WAA08147@frig.mt.cs.keio.ac.jp>
In-Reply-To: Your message of Thu, 21 Mar 1996 00:37:51 -0800. <199603210837.AAA00354@precipice.shockwave.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi.

I'm working on PC-card driver package of FreeBSD.

In article <199603210837.AAA00354@precipice.shockwave.com>
pst@shockwave.com writes:

>> (a) calling dev_attach() from a modloaded device panics the system.
>>     I have not even attempted to mess with this yet,  but it can be
>>     trivially reproduced by removing the #ifndef ACTUALL_LKM_NOT_KERNEL
>>     wrappers around the call in qcam.c.  It panics with a kernel page
>>     fault, but the current calling chain did /not/ include any of the
>>     qcam routines in the stack frame.  I just found this by scratching
>>     my head and looking to see what I did that the joystick routine
>>     didn't do.

I'm facing the same problem with pccard drivers on 2.2.

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.

I think that dev_attach() of 2.2 has serious bug in dynamic
reconfiguration of devices (dev_attach() of 2.1 has no problem in
these operations).

--
	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?199603211344.WAA08147>