Re: [Gphoto-user] nikon coolpix 4500

[Marcus M. <mei...@su...>]

On Mon, Jan 21, 2008 at 12:29:01PM -0800, darethehair wrote:
> 
> Followup to my intermittent problems using a Coolpix 4500 on gphoto2 2.4.0. 
> Today, I managed to 'capture' a bunch of pics successfully in-a-row, but
> eventually the camera did lock up.
> 
> Here is the debug messages common to both success and failure that are the
> same (immediately before they deviate from each other):
> 
> ...
> 0.827817 ptp2(2): maxpacketsize 64
> 0.827930 gphoto2-port(2): Setting timeout to 8000 millisecond(s)...
> 0.827960 ptp(2): PTP: Opening session
> 0.827985 gphoto2-port(2): Writing 16=0x10 byte(s) to port...
> 0.828009 gphoto2-port(3): Hexdump of 16 = 0x10 bytes follows:
> 0000  10 00 00 00 01 00 02 10-00 00 00 00 01 00 00 00  ................
> 
> Here is how the successful one continues (a bit) from that point:
> 
> 0.829624 ptp2/ptp_usb_getresp(2): reading response
> 0.829649 ptp2/ptp_usb_getpacket(2): getting next ptp packet
> 0.829669 gphoto2-port(2): Reading 4096=0x1000 bytes from port...
> 1.156636 gphoto2-port(2): Could only read 12 out of 4096 byte(s)
> 1.156700 gphoto2-port(3): Hexdump of 12 = 0xc bytes follows:
> 0000  0c 00 00 00 03 00 01 20-00 00 00 00              ....... ....    
> ...
> 
> Here is how the un-successful one continues (a bit) from that point:
> 
> 8.935489 ptp2/usb_sendreq(2): request code 0x1002 sending req result -35
> 8.935570 ptp2/camera_init(0): ptp_opensession returns 2ff
> ...
> 
> Of course, this is meaningless to me, but perhaps those of you that
> understand the debug diagnostics will be able to make something of it.

The second one (the hanging one) is usually caused by the *previous*
call not correctly terminating or hanging the protocol stack.

This previous trace would be interesting.

Ciao, Marcus