From owner-freebsd-bugs@freebsd.org Wed Feb 26 18:03:10 2020 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 05AB925F737 for ; Wed, 26 Feb 2020 18:03:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 48SNvK6T0pz42pk for ; Wed, 26 Feb 2020 18:03:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id DE03C25F736; Wed, 26 Feb 2020 18:03:09 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DDC3C25F735 for ; Wed, 26 Feb 2020 18:03:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48SNvK5gCZz42pf for ; Wed, 26 Feb 2020 18:03:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id BC2273782 for ; Wed, 26 Feb 2020 18:03:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 01QI39v7059321 for ; Wed, 26 Feb 2020 18:03:09 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 01QI39aG059319 for bugs@FreeBSD.org; Wed, 26 Feb 2020 18:03:09 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 237463] aacraid(4) doesn't work on powerpc64 Date: Wed, 26 Feb 2020 18:03:09 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: luporl@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Feb 2020 18:03:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237463 --- Comment #5 from Leandro Lupori --- I've noticed that the AIF interrupts always occur about 5 minutes after a reboot. Luckily, they occur on Petitboot too, which made it possible to collect the following information about the remaining issue: / # dmesg | tail -20 [ 40.494002] sd 1:2:23:0: [sdi] 4096-byte physical blocks [ 40.494004] scsi 1:3:123:0: Enclosure ADAPTEC Smart Adapter = 4.02 PQ: 0 ANSI: 5 [ 40.495376] sd 1:2:23:0: [sdi] Write Protect is off [ 40.495379] sd 1:2:23:0: [sdi] Mode Sense: 46 00 10 08 [ 40.495520] scsi 1:3:123:0: Attached scsi generic sg11 type 13 [ 40.498220] sd 1:2:23:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 40.533826] udevd[2649]: inotify_add_watch(6, /dev/dm-8, 10) failed: No = such file or directory [ 40.585006] sd 1:2:23:0: [sdi] Attached SCSI disk [ 41.437318] udevd[2688]: inotify_add_watch(6, /dev/dm-11, 10) failed: No such file or directory [ 321.101655] sd 1:2:16:0: [sdb] Synchronizing SCSI cache [ 321.102364] sd 1:2:16:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=3DDID_NO_CONNECT driverbyte=3DDRIVER_OK [ 334.245061] scsi 1:2:16:0: Direct-Access ATA ST4000NM0115-1YZ S= N04 PQ: 0 ANSI: 6 [ 334.250710] sd 1:2:16:0: Attached scsi generic sg2 type 0 [ 334.260739] sd 1:2:16:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) [ 334.260742] sd 1:2:16:0: [sdb] 4096-byte physical blocks [ 334.261614] sd 1:2:16:0: [sdb] Write Protect is off [ 334.261616] sd 1:2:16:0: [sdb] Mode Sense: 46 00 10 08 [ 334.264430] sd 1:2:16:0: [sdb] Write cache: disabled, read cache: enable= d, supports DPO and FUA [ 334.325386] sdb: sdb1 sdb2 sdb3 [ 334.349896] sd 1:2:16:0: [sdb] Attached SCSI disk /var/petitboot/mnt/dev/sda2/bsd # ./arcconf getlogs 1 event Controllers found: 1 So, the AIFs are about the drive being removed and then re-inserted after a= few seconds, which explains the "Target Selection Timeout" errors that were bei= ng seen right after the AIF interrupts occurred. However, further investigation is needed to understand why the drive is bei= ng removed. It could be due to a bad HDD/SAS expander cable, a write cache iss= ue, or maybe a setup issue with the 2 SAS controllers/cabling on the machine, or maybe something else. --=20 You are receiving this mail because: You are the assignee for the bug.=