I grepped for the port number 17398, so there might be some unrelated packets in there.
server log: After the last TCP Retransmission the connection timed out causing write(2) to return ETIMEDOUT which caused the server to issue a close(2) on the socket.
This triggered no new packets (at least not on the server side). Then I shutdown the server, but that didn't trigger anything either, the client was still blocked in read(2).
When I killed the client (Ctrl-C), the remaining entries (FIN etc) appeared in the server log.
I said earlier that this worked when the server was run on a SunOS computer, this is not correct, it fails in the same way.
For these tests the following computers was used:
server> uname -a
Linux server-name 2.6.34-gentoo-r12 #5 SMP Tue Apr 5 12:56:20 CEST 2011 x86_64 Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz GenuineIntel GNU/Linux
client> uname -a
Linux client-name 2.6.18-194.26.1.el5 #1 SMP Tue Nov 9 12:54:20 EST 2010 x86_64 x86_64 x86_64 GNU/Linux
We're having problems getting disconnected from AIX with our telnet sessions.
I can't ping the server when this happens, either. Other serves can be pinged at the same time.
This happens both at unix and within the database. Database locks remain when editing files. unix logins remain after... (0 Replies)
Hi,
I was porting ipv4 application to ipv6; i was done with TCP transports. Now i am facing problem with SCTp transport at runtime.
To test SCTP transport I am using following server and client socket programs. Server program runs fine, but client program fails giving Invalid Arguments for... (0 Replies)
i am using Putty to do ssh to all the unix nodes that we have in our work environment. it is very strange that all my network connections will timeout quickly in 10 mins, it can either be a putty connection, sqlplus or toad. is there some setting that can help to prevent this. please let me know... (3 Replies)
Hello everyone. Thanks for reading. I am using Ubuntu 7.04 to experience this problem:
I have written my own programs that communicate to eachother and I am having a hard time detecting a TCP socket disconnect when the remote side's computer has a power-failure (for example).
On the computer... (6 Replies)
I need clarification on whether it is okay to set socket options on a listening socket
simultaneously when it is being used in an accept() call?
Following is the scenario:-
-- Task 1 - is executing in a loop - polling a listen socket, lets call it 'fd', (whose file descriptor is global)... (2 Replies)
Hi , My redhat 5 frequently disconnects from network. Once rebooted , network is working for one day or two. After that the NIC suddently stops working. Even if i give "#service network restart" or ifup eth0 commands it won't come up. I even tried reconfigure the network card. but no use. Only... (6 Replies)
Is there a way to have persistent terminal windows to redhat server across viewer disconnects? I can do that with the help of an extra MS Windows server and rdp, but is there a way of doing that without the Windows server?
Here's the scenario. I have multiple redhat servers (VMs) which have no... (3 Replies)
I have inherited and SCO OpenServer Release 6 server. The clients connect using telnet to get to a proprietary database application for Service tickets. The issue I am currently having is that the connection just stops abruptly and you can see "telnet session terminated" on the terminal emulation... (22 Replies)
Discussion started by: sean6605
22 Replies
LEARN ABOUT SUSE
usb_ep_queue
USB_EP_QUEUE(9) Kernel Mode Gadget API USB_EP_QUEUE(9)NAME
usb_ep_queue - queues (submits) an I/O request to an endpoint.
SYNOPSIS
int usb_ep_queue(struct usb_ep * ep, struct usb_request * req, gfp_t gfp_flags);
ARGUMENTS
ep
the endpoint associated with the request
req
the request being submitted
gfp_flags
GFP_* flags to use in case the lower level driver couldn't pre-allocate all necessary memory with the request.
DESCRIPTION
This tells the device controller to perform the specified request through that endpoint (reading or writing a buffer). When the request
completes, including being canceled by usb_ep_dequeue, the request's completion routine is called to return the request to the driver. Any
endpoint (except control endpoints like ep0) may have more than one transfer request queued; they complete in FIFO order. Once a gadget
driver submits a request, that request may not be examined or modified until it is given back to that driver through the completion
callback.
Each request is turned into one or more packets. The controller driver never merges adjacent requests into the same packet. OUT transfers
will sometimes use data that's already buffered in the hardware. Drivers can rely on the fact that the first byte of the request's buffer
always corresponds to the first byte of some USB packet, for both IN and OUT transfers.
Bulk endpoints can queue any amount of data; the transfer is packetized automatically. The last packet will be short if the request doesn't
fill it out completely. Zero length packets (ZLPs) should be avoided in portable protocols since not all usb hardware can successfully
handle zero length packets. (ZLPs may be explicitly written, and may be implicitly written if the request 'zero' flag is set.) Bulk
endpoints may also be used for interrupt transfers; but the reverse is not true, and some endpoints won't support every interrupt transfer.
(Such as 768 byte packets.)
Interrupt-only endpoints are less functional than bulk endpoints, for example by not supporting queueing or not handling buffers that are
larger than the endpoint's maxpacket size. They may also treat data toggle differently.
Control endpoints ... after getting a setup callback, the driver queues one response (even if it would be zero length). That enables the
status ack, after transfering data as specified in the response. Setup functions may return negative error codes to generate protocol
stalls. (Note that some USB device controllers disallow protocol stall responses in some cases.) When control responses are deferred (the
response is written after the setup callback returns), then usb_ep_set_halt may be used on ep0 to trigger protocol stalls. Depending on the
controller, it may not be possible to trigger a status-stage protocol stall when the data stage is over, that is, from within the
response's completion routine.
For periodic endpoints, like interrupt or isochronous ones, the usb host arranges to poll once per interval, and the gadget driver usually
will have queued some data to transfer at that time.
Returns zero, or a negative error code. Endpoints that are not enabled report errors; errors will also be reported when the usb peripheral
is disconnected.
AUTHOR
David Brownell <dbrownell@users.sourceforge.net>
Author.
COPYRIGHT Kernel Hackers Manual 2.6. July 2010 USB_EP_QUEUE(9)