From nobody Sat Apr 2 20:10:56 2022 X-Original-To: freebsd-stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 0CC891A43592 for ; Sat, 2 Apr 2022 20:11:09 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ua1-x92d.google.com (mail-ua1-x92d.google.com [IPv6:2607:f8b0:4864:20::92d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KW7TS1dRgz4rMG for ; Sat, 2 Apr 2022 20:11:08 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-ua1-x92d.google.com with SMTP id a20so2294585uaq.11 for ; Sat, 02 Apr 2022 13:11:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=E3/iHmzeLXp/68jBvLYJMyHWShiLFjfAxDaE2WubtXw=; b=tInOHdosd3c48Ox57lcZDBNIA3oqo50PpqDRw2QEFDFHME2QumS1HsI73l4qPeFprS F7/pP9NE2mKrSnvcJ4XWguNHBMm47CFGmKwS8PfYRBZeeqA8nlLao0NVUFWKRBjAAv8J BIa199kmNts1eM/RwH04JhDH6cUCicHxHzhcFpchw9c8Xd/dlH+uMRi/02hY/My9L59A 60NrLwM8cHUw3bAE+o06bPCzM0X9zJvgpg2TDdycYeOPUj/alkc4Ws1aXNNftXl9LwWX B3GfR532muDDe7wAR0CjjyargIIV2qkpjItVRMelJG0es2QNVd8WQ6m6nsP5pSIVFQX2 Z+/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=E3/iHmzeLXp/68jBvLYJMyHWShiLFjfAxDaE2WubtXw=; b=oNCJWfeMw7gkbH+BurBIUz8lfKPaIhPioR5gjWhOyryjsqiabikK1clp2BK3gEKEhO yVrKvrVg09gOWfTmXsBNtGg15+k8zMMg3hiSaNVSYU+eIo59ckUPunfeKXZ67vVUdaP6 T/j6r2fEF47OYDsmmZRHFHQ1W9BnM5DdLApTr2Tx9q9O4GYAXb2QkprhJsD3E9+uf9ao 9aw5eDWX1Lz7pxAGewCtjmLhf28uo5J9jG+sayOruQgjrZI7tMlYMZi3WZKgdoLZ3qh2 5EMzaWf8lij6Be685T3QdZmqrycU1NsxwFiw1xLJPONExHESkdg4IaTUmawg/W94oogb qOuw== X-Gm-Message-State: AOAM532Rdb3sJfeVzS8xy5bnXKd799wEmjLtXG6LimrTuZLprACDmQhQ 5Y7rJAqFQIhiS+bKlsCMu7Hjk04hDDqpAzOL9d6dZvRrGpHwwA== X-Google-Smtp-Source: ABdhPJyMJB3cB5VNfsUxcbUlYt9WjPLs0dC3oLSeDi75umdR2kLIFz217OX3UGhOy1uzrbGkh+hmuZezdgasAsv+Er4= X-Received: by 2002:ab0:6804:0:b0:33c:6fe1:3266 with SMTP id z4-20020ab06804000000b0033c6fe13266mr5267399uar.91.1648930267500; Sat, 02 Apr 2022 13:11:07 -0700 (PDT) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Sat, 2 Apr 2022 14:10:56 -0600 Message-ID: Subject: Re: Odd messages on recent 13/stable To: Jonathan Chen Cc: FreeBSD-STABLE Mailing List Content-Type: multipart/alternative; boundary="000000000000daa3ab05dbb17e17" X-Rspamd-Queue-Id: 4KW7TS1dRgz4rMG X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20210112.gappssmtp.com header.s=20210112 header.b=tInOHdos; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::92d) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-3.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20210112.gappssmtp.com:s=20210112]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20210112.gappssmtp.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::92d:from]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MLMMJ_DEST(0.00)[freebsd-stable]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; R_SPF_NA(0.00)[no SPF record]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N --000000000000daa3ab05dbb17e17 Content-Type: text/plain; charset="UTF-8" On Sat, Apr 2, 2022 at 1:27 PM Jonathan Chen wrote: > Hi, > > I recently updated 13/stable (stable/13-n250195-26e8bb3a4e1), and I'm > now seeing the following messages on boot: > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > ahcich5: AHCI reset: device not ready after 31000ms (tfd = 0000ff7f) > (aprobe3:ahcich5:0:15:0): NOP FLUSHQUEUE. ACB: 00 00 00 00 00 00 00 00 > 00 00 00 00 > (aprobe3:ahcich5:0:15:0): CAM status: ATA Status Error > (aprobe3:ahcich5:0:15:0): ATA status: f7 (BSY DRDY DF SERV CORR IDX > ERR), error: ff (ICRC UNC MC IDNF MCR ABRT NM ILI) > (aprobe3:ahcich5:0:15:0): RES: f7 ff ff ff ff ff ff ff ff ff ff > (aprobe3:ahcich5:0:15:0): Error 5, Retries exhausted > (aprobe0:ahcich5:0:0:0): NOP FLUSHQUEUE. ACB: 00 00 00 00 00 00 00 00 > 00 00 00 00 > (aprobe0:ahcich5:0:0:0): CAM status: ATA Status Error > (aprobe0:ahcich5:0:0:0): ATA status: f7 (BSY DRDY DF SERV CORR IDX > ERR), error: ff (ICRC UNC MC IDNF MCR ABRT NM ILI) > (aprobe0:ahcich5:0:0:0): RES: f7 ff ff ff ff ff ff ff ff ff ff > (aprobe0:ahcich5:0:0:0): Error 5, Retries exhausted > > The system boots up fine after this. > > Is this a regression, or an indication that my hardware is failing? > If this was after a power on, maybe it indicates your drive on channel 5 of the ahci controller took too long to spin up? If this was a normal reboot, then it may suggest trouble the drive is having. Or this is a new bug that I've not seen a similar failure before like this... If you reboot your old kernel, do you see this too? Warner --000000000000daa3ab05dbb17e17 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sat, Apr 2, 2022 at 1:27 PM Jonath= an Chen <jonc@chen.org.nz> wr= ote:
Hi,

I recently updated 13/stable (stable/13-n250195-26e8bb3a4e1), and I'm now seeing the following messages on boot:
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
ahcich5: AHCI reset: device not ready after 31000ms (tfd =3D 0000ff7f)
(aprobe3:ahcich5:0:15:0): NOP FLUSHQUEUE. ACB: 00 00 00 00 00 00 00 00
00 00 00 00
(aprobe3:ahcich5:0:15:0): CAM status: ATA Status Error
(aprobe3:ahcich5:0:15:0): ATA status: f7 (BSY DRDY DF SERV CORR IDX
ERR), error: ff (ICRC UNC MC IDNF MCR ABRT NM ILI)
(aprobe3:ahcich5:0:15:0): RES: f7 ff ff ff ff ff ff ff ff ff ff
(aprobe3:ahcich5:0:15:0): Error 5, Retries exhausted
(aprobe0:ahcich5:0:0:0): NOP FLUSHQUEUE. ACB: 00 00 00 00 00 00 00 00
00 00 00 00
(aprobe0:ahcich5:0:0:0): CAM status: ATA Status Error
(aprobe0:ahcich5:0:0:0): ATA status: f7 (BSY DRDY DF SERV CORR IDX
ERR), error: ff (ICRC UNC MC IDNF MCR ABRT NM ILI)
(aprobe0:ahcich5:0:0:0): RES: f7 ff ff ff ff ff ff ff ff ff ff
(aprobe0:ahcich5:0:0:0): Error 5, Retries exhausted

The system boots up fine after this.

Is this a regression, or an indication that my hardware is failing?

If this was after a power on, maybe it indicat= es your drive on channel 5 of the ahci controller took too long to spin up?= If this was a normal reboot, then it may suggest trouble the drive is havi= ng.

Or this is a new bug that I've not seen a = similar failure before like this... If you reboot your old kernel, do you s= ee this too?

Warner
--000000000000daa3ab05dbb17e17--