kevin wrote:
> 
> Right, I should have used cut and paste. Here is my pencam_set_camera
> function at present (I have cut out all but the first of the vendor
> specific codes, since the crash occurs there):
> 
> ----------------  cut  ----------------------------
> 
[snip]

>  pipe = usb_rcvctrlpipe(dev->udev,0);
>  info("Pipe Set");
> 
>  if ((i = usb_control_msg(dev->udev, pipe,
>          0x8a, 0xc1, 0, 0, buf, 0x02, PENCAM_TIMEOUT)) < 0)
>          return i;
> 
> 
[snip]

> ------------------------------   cut --------------------------
> 
> In the dmesg output I get the "Set configuration OK", "Set interface
> OK", "Setting pipe" messages and then the "invalid operand: 0000".

I don't see how it could be the line:
>  pipe = usb_rcvctrlpipe(dev->udev,0);

so I expect that "Pipe Set" is just not showing up in the log
before the Oops happens.

> Now the oops file. I am using the stock Mandrake 8.0 distribution,
> kernel 2.4.3-20mdk, with the ksymoops rpm that came with it. Apparently
> I am missing some debugging package, or the kernel is not built with
> some debugging info. This is the output of
> "ksymoops -v /boot/vmlinuz-2.4.3-20mdk -m System.map-2.4.3-20mdk -LK
> oops.file > logoops.txt" :

"-v filename" requires an uncompressed vmlinux file, not a "vmlinuz"
file.  Guess you'll have to compile a kernel for testing.

> -----------------------------------------------------
> ksymoops 2.3.7 on i586 2.4.3-20mdk.  Options used

Please get the current version of ksymoops from
http://www.kernel.org/pub/linux/utils/kernel/ksymoops/v2.4/
(now version 2.4.3).

>      -v /boot/vmlinuz-2.4.3-20mdk (specified)
>      -K (specified)
>      -L (specified)
>      -o /lib/modules/2.4.3-20mdk/ (default)
>      -m /boot/System.map-2.4.3-20mdk (specified)
> 
> Error (pclose_local): read_nm_symbols pclose failed 0x100
> Warning (read_vmlinux): no kernel symbols in vmlinux, is
> /boot/vmlinuz-2.4.3-20mdk a valid vmlinux file?

No, it's not.

[snip]
> ------------------------------------------------------
> 
> >From the "Warning (read_vmlinux): no kernel symbols in vmlinux, is
> /boot/vmlinuz-2.4.3-20mdk a valid vmlinux file?" (must be valid; it's
> the only one there and the system boots) I assume that the kernel is not
> built with the necessary kernel symbols. I will have to recompile the
> kernel, but I am not sure what option to enable in "make menuconfig" to
> do this; I looked through the options and couldn't find that particular
> one. "code maturity level support, loadable module support, processor
> type features, general setup" have nearly all options either compiled in
> or marked as M). Where do I look for that? Or am I just missing some
> package?  Thanks,

No, that's not a config option.

~Randy

_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to