From owner-freebsd-bugs@FreeBSD.ORG Wed Dec 31 06:14:19 2014 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 693E783D for ; Wed, 31 Dec 2014 06:14:19 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 4A7541056 for ; Wed, 31 Dec 2014 06:14:19 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sBV6EJFj064417 for ; Wed, 31 Dec 2014 06:14:19 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 196392] New: [cam] tape pwr-off then pwr-on: cam_periph_alloc: attempt to re-allocate valid device Date: Wed, 31 Dec 2014 06:14:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: p-fbsd-bugs@ziemba.us X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Dec 2014 06:14:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196392 Bug ID: 196392 Summary: [cam] tape pwr-off then pwr-on: cam_periph_alloc: attempt to re-allocate valid device Product: Base System Version: 10.1-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: p-fbsd-bugs@ziemba.us % uname -m -v FreeBSD 10.1-STABLE #2 r274721M: Wed Dec 10 22:45:35 PST 2014 root@hairball:/usr/obj/usr/src/sys/GPZ-274721 amd64 Something seems to be wrong in the bookkeeping of "sa" devices, although it might not be specific to sa. Scsi tape changer is attached via "ahc0: " When I perform this sequence: - power on scsi tape changer - camcontrol rescan all - power off tape changer - camcontrol rescan all my system gets into a state where 1) /dev/sa2 does not exist; 2) /dev/sa2.[123] exist; and 3) further attempts to power on the tape changer + "camcontrol rescan all" yield the following in /var/log/messages: Dec 30 21:29:34 hairball kernel: cam_periph_alloc: attempt to re-allocate valid device sa2 rejected flags 0x198 refcount 0 Dec 30 21:29:34 hairball kernel: saasync: Unable to probe new device due to status 0x6 Dec 30 21:29:34 hairball kernel: ch0 at ahc0 bus 0 scbus5 target 3 lun 0 Dec 30 21:29:34 hairball kernel: ch0: Removable Changer SCSI-2 device Dec 30 21:29:34 hairball kernel: ch0: Serial Number 0000000000 Dec 30 21:29:34 hairball kernel: ch0: 3.300MB/s transfers Dec 30 21:29:34 hairball kernel: ch0: 8 slots, 1 drive, 1 picker, 0 portals Dec 30 21:29:34 hairball kernel: ch0: quirks=0x2 I can pretty reliably get the system into this state. For what its worth, the appearance of this problem sometime between late 2013 and mid-2014 in 9-STABLE vs. 10-STABLE seemed to coincide with another occasional problem: power-on tape changer, and then system would lock up hard (with the motherboard beeper on solid) while executing either "camcontrol rescan all" or "camcontrol devlist". I have not been able to reproduce that behavior at will, but it's happened several times across several 10-STABLE versions I tried since July 2014. -- You are receiving this mail because: You are the assignee for the bug.