device_set_ivars is always called (in usbd_probe_and_attach) with as an
argument a stack variable. Also, the ivar is not stored or anything in
the if_aue.c driver. So this problem sounds like a problem in revisions
of various files.
Please check that your kernel modules kernel are in sync. Do this by
rebuilding the kernel and the modules from scratch.
Also, after you've installed your kernel check that all your kernel
files have been updated. Do you by any chance have a stale /modules or
/boot/modules directory lying around? You should have only kernel
modules in /boot/kernel*/ and NOT in /modules* or /boot/modules*.
If the problem persists, please mail me the output of
find /modules /boot -type f -ls
On Sat, 13 Apr 2002, Will Andrews wrote:
> On Sat, Apr 13, 2002 at 12:44:36PM -0400, John Baldwin wrote:
> > Can you get a backtrace in ddb? It looks like a null pointer dereference, and
> > knowing where it happened would help. Finding the file and line of the
> > instruction pointer using addr2line on kernel.debug would be helpful as well.
> It *is* a null pointer deref. Joe and I looked at this problem,
> and it seems a function called device_get_ivars() isn't doing
> its job in sys/dev/usb/usb_port.h. So the variable is getting
> filled with a NULL pointer for the iface element and is later
> deref'd. That's the limit of my debugging, and Joe is looking
> into the problem actively.
[EMAIL PROTECTED] http://www.van-laarhoven.org/
[EMAIL PROTECTED] http://www.etla.net/~n_hibma/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message