From owner-freebsd-usb@freebsd.org Sat Oct 22 20:12:57 2016 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A2178C1C948 for ; Sat, 22 Oct 2016 20:12:57 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6C98ADDF for ; Sat, 22 Oct 2016 20:12:57 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 473951FE023; Sat, 22 Oct 2016 22:12:54 +0200 (CEST) Subject: Re: Facing serious problems after hardware upgrade with FreeBSD 10.3 To: Manish Jain , "freebsd-usb@freebsd.org" References: From: Hans Petter Selasky Message-ID: <60d785ff-56f5-a63b-ab80-b92fa6eb1c5d@selasky.org> Date: Sat, 22 Oct 2016 22:17:54 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Oct 2016 20:12:57 -0000 On 10/22/16 20:08, Manish Jain wrote: > > Hi, > > I am running FreeBSD 10.3 amd64. > > Over the last couple of months, I have made a major upgrade of my > computer - an upgrade which has knocked out virtually everything except > the CPU (AMD Athlon X2 270). > > In phase 1 (about 2 months ago), I moved the motherboard to a new > Gigabyte SB970 based board (paired with the the old Athlon CPU) and the > hard disk to a Samsung EVO 850 SSD > > In phase 2 (yesterday), I upgraded other components (new components > listed) : PSU (Corsair RM650x), RAM (Kingston HyperX, 8 GB, single > piece), DVD drive (Asus DRW-24D5MT), cabinet (Circle 821). > > The USB peripherals remain the same ; mouse, keyboard, printer, scanner. > > The USB scanner (Canon MG 2470 Pixma; multi-function device serving > purely as scanner) is the one that is of most interest. > > After phase 2 of the upgrade was over, I have been facing this situation > (since yesterday) : > > If I run 'scanimage -L' as root on the console at ttyv4 (no X), most of > the times it returns with a listing of the Canon scanner. At the same > time, on ttyv0, I also get the following diagnostics : > > ata0: FAILURE - odd-sized DMA transfer attempt 5 % 2 > ata0: setting up DMA failed > > Once in about 2-3 tries, the command actually gets totally stuck. Not > even Control-C wakes it up. In such cases, the system usually has to be > rebooted - sometimes forcibly by hard-pressing the switch on the cabinet. > > Further, at the time I boot, I sometimes also see the following > diagnostics on ttyv0 : > > (ada0:ata0:0:1:0): READ_DMA48. ACB: 25 00 df ea ff 40 33 00 00 00 01 00 > (ada0:ata0:0:1:0): CAM status: Command timeout > (ada0:ata0:0:1:0): Retrying command > > The last time I spotted the above error ("CAM status: Command timeout") > was in a single user shell running fsck after an unclean shutdown. No > other command except fsck and reboot was given to the system during that > session. > > I am trying to determine whether the errors I am facing are a problem > with the hardware; with the kernel; or with the USB code. The only other > thing notable I can add is the USB scanner works seamlessly under > Windows XP (which serves as my second OS on my dual-boot machine). > > If anybody can help me determine what is wrong with the system, I shall > be highly grateful - I feel practically paralysed after investing so > much time, money and energy upgrading the hardware, only to be feeling > as if now I am stuck in no man's land. > Hi, Did you try an 10-stable kernel? About the USB scanner we need some more information. Did you set the permissions on /dev/ugenX.Y correctly? --HPS