From owner-freebsd-hardware@FreeBSD.ORG Wed Nov 16 00:52:19 2011 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A6DE41065746 for ; Wed, 16 Nov 2011 00:52:19 +0000 (UTC) (envelope-from amijaresp@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 673678FC14 for ; Wed, 16 Nov 2011 00:52:19 +0000 (UTC) Received: by yenl11 with SMTP id l11so4237444yen.13 for ; Tue, 15 Nov 2011 16:52:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Pa6AOvYcmM0vXWBvBD9mG9d97iO9hgWoaMCEuUvP3AI=; b=a0a359ZtvCu+YXEhYmcjfZIJhJFvcz8dep4CG1jkeON6X+SqGc/Obczf2sKmzRZxZ9 BpAy3vqpkAGgRmQxly5LMUQtt8Hw9/rRIygJnoLKKloQ1nWx4pX4rj28nQ87j2ovRmc+ oa6jtmrFUVgYkWkhdEHl/w7LYxXjplMmHxm88= MIME-Version: 1.0 Received: by 10.100.53.21 with SMTP id b21mr5405923ana.17.1321404738630; Tue, 15 Nov 2011 16:52:18 -0800 (PST) Received: by 10.100.60.11 with HTTP; Tue, 15 Nov 2011 16:52:18 -0800 (PST) In-Reply-To: <201111051539.49068.hselasky@c2i.net> References: <201111040941.28413.hselasky@c2i.net> <201111051539.49068.hselasky@c2i.net> Date: Tue, 15 Nov 2011 20:22:18 -0430 Message-ID: From: Alberto Mijares To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 Cc: freebsd-hardware@freebsd.org Subject: Re: How to debug USB hardware issues X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2011 00:52:19 -0000 >> > >> > I would start turn on debugging in the modem driver, compile kernel with >> > options USB_DEBUG, and then see what is printed at the time of failure. >> Hi list, I read usb_debug.c and found that I had to turn on debugging with # sysctl hw.usb.debug=1 So, I did it. Then, I started the application (the service is still down since my first post in this thread) and many messages showed in dmesg and /var/log/messages. Tha app didn't work, so I opened one terminal with tail -f /var/log/messages and from another terminal tried to connect to the modem with cu -l /dev/cuaU0 -s 115200. This was the output: Jan 6 10:19:59 kannel kernel: usbd_transfer_submit: xfer=0xc48bb968, endpoint=0xc4b5e800, nframes=1, dir=read Jan 6 10:19:59 kannel kernel: usb_dump_endpoint: endpoint=0xc4b5e800 edesc=0xc42f9032 isoc_next=0 toggle_next=1 bEndpointAddress=0x81 Jan 6 10:19:59 kannel kernel: usb_dump_queue: endpoint=0xc4b5e800 xfer: Jan 6 10:19:59 kannel kernel: usbd_transfer_submit: open Jan 6 10:19:59 kannel kernel: usbd_pipe_enter: enter Jan 6 10:19:59 kannel kernel: usbd_pipe_start: start Jan 6 10:20:00 kannel kernel: usbd_do_request_flags: Handle Request function is set Jan 6 10:20:32 kannel last message repeated 96 times Jan 6 10:22:33 kannel last message repeated 366 times Even so, the modem is still dead. No response. Finally, after a while, I killed the cu process and this message showed usbd_do_request_flags: Handle Request function is set usbd_transfer_stop: close usbd_transfer_done: err=USB_ERR_CANCELLED usbd_transfer_done: err=USB_ERR_NORMAL_COMPLETION usbd_callback_wrapper_sub: xfer=0xc48bb968 endpoint=0xc4b5e800 sts=5 alen=0, slen=2048, afrm=0, nfrm=1 usbd_do_request_flags: Handle Request function is set u3g debug is on and no message appears. Any hint about this? I'm about to buy a PCI->USB card, unless anyone can say there's no problem with USB hardware. So I have to bye another modem. Thank you very mucho in advance. Regards Alberto Mijares