HEADSUP!!! USB MFC committed..

[Yoshihiko Sarumaru]

Hi akiyama san,

unfortunately, It couldn't help me.

With KMODDEPS, DDB said:
Stopped at usbd_get_string+0x15: movl 0(%eax), %eax)
db> trace
usbd_get_string(.....)
usbd_devinfo_vp(.....)
usbd_devinfo(.....)
ugen_attach(.....)
DEVICE_ATTACH(.....)
device_probe_and_attach(.....) at ...
usbd_probe_and_attach(.....) at ...
usbd_new_device(.....) at ...
(snip)

Without KMODEPS, I had been seen:
Stopped at usbd_get_interface_descriptor+0x6: movl 0x4(%eax),%eax
db> trace
usbd_get_interface_descriptor(1,6,....) at usbd_get_interface_descriptor+0x6
umodem_match(.....) at umodem_match+0x24
DEVICE_PROBE(.....) at DEVICE_PROBE+0x2e
device_probe_child(.....) at ...
device_probe_and_attach(.....) at ...
usbd_probe_and_attach(.....) at ...
usbd_new_device(.....) at ...
(snip)

I don't know what is different between two above situation.

By the way, I found it would always panic with latter panic
message  when I load kernel-without-usb + usb.ko + ucom.ko +
umodem.ko then boot although I didn't plugged any umodem devices.

akiyama san wrote:

> Hi, Sarumaru-san.
> 
> At Mon, 8 Mar 2004 01:38:07 +0900,
> Yoshihiko Sarumaru wrote:
> 
> > I report you about a USB problem that would be occur with my
> > laptop after you MFC'ed USB stuff.
> > 
> > With GENERIC kernel, it is fine and there are no changes from
> > before, but with no usb kernel + usb.ko + umass.ko, it would be
> > panic everytime on boot.
> > 
> > It is not depend on umass. The panic would be happen when I
> > didn't load umass.ko but ucom.ko + umodem.ko and plug USB modem
> > (PHS phone).
> 
> I reproduced this panic, and tracked this down.
> This is a kernel module dependency problem.
> 
> Please try attached patch, and let me know the result.
> If this patch fix your problem, I'll commit this.
> -- 
> Shunsuke Akiyama
> akiyama at jp.FreeBSD.org
> akiyama at FreeBSD.org
--
Yoshihiko Sarumaru
mail: mistral at imasy.or.jp       web: http://www.imasy.or.jp/~mistral/