From nobody Sat Jun 17 21:07:48 2023 X-Original-To: freebsd-ppc@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 4Qk7sl0hBmz4dvHw for ; Sat, 17 Jun 2023 21:08:11 +0000 (UTC) (envelope-from bdragon@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Qk7sl05yRz44qf for ; Sat, 17 Jun 2023 21:08:11 +0000 (UTC) (envelope-from bdragon@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1687036091; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=oLTunhhqYUMp2TdmiY338wZLEemhe0j29BR/lmnGpHc=; b=jbYhGfOCrxG+L7mJ6mN3d2781XbyAtUDtlK44c8t2d0CRYpk+l092zT7jUrLO1Mhu+thkW 7JwmcYi2EVC5hVnWh5zmjWpdKOQp9pXBVt9s8HxfxSN3QDXZMqCFl81U2W5YTJ3Nv0j1EY Bg7rhuw9EWSv6jo0gzLV8FU0nZQrbmCnoXolrUBXhoMWVe4e1KOAOglXkOlJoE/r0CyOGi AZf4bBf8377an8LS/TkAxezPbglHStLW2lOqOYr0k+SJUL2ffedS5KKclId5FeNRg5eT3R bPdaG27oSvRRDi0RgcMind0YV3RjIRDNmdOhPypEhc0D7w+y7dQPneOESa0YRw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1687036091; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=oLTunhhqYUMp2TdmiY338wZLEemhe0j29BR/lmnGpHc=; b=rVZmYIvlMo9CLiKBHjUcuTc1amLZlQhP7RWQmL0VBYgBYVY6VL7hHevEdMzU13PKlR10+u LHDscNotFuPTATcsI8psPJnrsWhgG2Cs3ZerJc2OgoEq1Qs58/jMS+ZUyr7Ia8JMBuZHGA 8XI5r1TRLQjpUDXtsje4q7wA6CmPBfjwl2oz7jpN0tZsxW9kPv3FTxZzsTr0rCRALjtZLi wBVVuMW6nGqmbT1OJhn7wf9eZWN+ATWWny2DbSOTS/ROAd5tP0kT5jRNV65M0FFtgPOTbI pRL0O4rtUpQtEByHj5loEzSPfCeXLYIJIIDk8MJZHu/IG89GvwJz8hf+0C9wZQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1687036091; a=rsa-sha256; cv=none; b=f3ejRk0msGJlaBUswF0ywmPpEBBTXkwBeSqMagVxBwjlZ4BlfHe5WsGHjuMffIOH0k21QV jtD8RX4dXzQCQoGcR8LJW4MCa9cHXt5elkKLwS3hsZgZAlv/6tar1b5kwT9ugKU2VAwoSu WLzDYK1tpgbo0Kw1w+zvM4HNFtvyizImBe1krD3W7gEJNnoIQHihhrs49O41MSAldYZzOP 5ZpVvbqFTOx4mnpwLy9wOVoOxIqqzh1zBiVO84svatmYiH+v82AmLUEERdXTFV0u9yeqUE dDKt9gw3Pl3QBVZlMyIdUFw+PnNxL2OSCQQ2sWG+tfS09np2Ap6HMbnTh21lfw== Received: from auth1-smtp.messagingengine.com (auth1-smtp.messagingengine.com [66.111.4.227]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: bdragon/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Qk7sk65kKzynR for ; Sat, 17 Jun 2023 21:08:10 +0000 (UTC) (envelope-from bdragon@FreeBSD.org) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailauth.nyi.internal (Postfix) with ESMTP id 519AA27C0054 for ; Sat, 17 Jun 2023 17:08:10 -0400 (EDT) Received: from imap42 ([10.202.2.92]) by compute3.internal (MEProxy); Sat, 17 Jun 2023 17:08:10 -0400 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrgedvjedgudehjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecufghrlhcuvffnffculdejmdenucfjughrpefofg ggkfffhffvufgtgfesthhqredtreerjeenucfhrhhomhepfdeurhgrnhguohhnuceuvghr ghhrvghnfdcuoegsughrrghgohhnsefhrhgvvgeuufffrdhorhhgqeenucggtffrrghtth gvrhhnpeeftdfhfedvjeethfdtleeludeltdeuhedtgfeuteeuudeggfdtledtgfeuleet keenucffohhmrghinheprhgrphhtohhrtghsrdgtohhmnecuvehluhhsthgvrhfuihiivg eptdenucfrrghrrghmpehmrghilhhfrhhomhepsggurhgrghhonhdomhgvshhmthhprghu thhhphgvrhhsohhnrghlihhthidquddtgedvfeehkeeigedqudekuddtkeehuddqsggurh grghhonheppefhrhgvvgeuufffrdhorhhgsehimhgrphdrtggt X-ME-Proxy: Feedback-ID: ib6814798:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 22F36BC0078; Sat, 17 Jun 2023 17:08:10 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.9.0-alpha0-496-g8c46984af0-fm-20230615.001-g8c46984a List-Id: Porting FreeBSD to the PowerPC List-Archive: https://lists.freebsd.org/archives/freebsd-ppc List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org Mime-Version: 1.0 x-forwarded-message-id: <9fc5ca46-cb92-4221-84ce-ca27d0c50b6f@app.fastmail.com> Message-Id: Date: Sat, 17 Jun 2023 16:07:48 -0500 From: "Brandon Bergren" To: "FreeBSD PowerPC ML" Subject: Fwd: Re: POWER9 Blackbird Powerup Issue Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable X-ThisMailContainsUnwantedMimeParts: N Forwarding, as I used the wrong mail alias by mistake and it bounced. ----- Original message ----- From: Brandon Bergren To: Curtis Hamilton , FreeBSD PowerPC ML Subject: Re: POWER9 Blackbird Powerup Issue Date: Saturday, June 17, 2023 3:27 PM You have a BMC serial port hooked up already, correct? (not to be confus= ed with the host serial port.) Here are the procedures to fix OpenBMC after mishaps. https://wiki.raptorcs.com/wiki/Debricking_the_BMC If those don't work, I would inspect the board carefully for damage. As = long as there isn't physical damage, there is always the option of refla= shing the BMC. On Sat, Jun 17, 2023, at 2:29 PM, Curtis Hamilton wrote: > I=E2=80=99m have an issue with my blackbird and can=E2=80=99t get supp= ort from RaptorCS > because it=E2=80=99s out of warranty. So I wanted to see if anyone el= se has > experienced the same or similar issue. > > The blackbird refuses to boot into OpenBMC after being powered off to > install a discrete GPU. The OpenBMC led ( ) continues to flash rapidly > with a momentary pause, then continues to flash rapidly. The power led > stays orange. > > I=E2=80=99ve checked raptors wiki, forums and the how-to guides, but d= on=E2=80=99t see > anything similar to my issue. I=E2=80=99ve tried leaving it completely= powered off > for several days but the problem still remains. > > Any suggestions/help would really be appreciated. > > Regards --=20 Brandon Bergren Technical Generalist --=20 Brandon Bergren bdragon@FreeBSD.org From nobody Tue Jun 27 19:15:42 2023 X-Original-To: freebsd-ppc@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 4QrDvb4yDkz4jKHC for ; Tue, 27 Jun 2023 19:15:55 +0000 (UTC) (envelope-from clhamilto@gmail.com) Received: from mail-oa1-x2c.google.com (mail-oa1-x2c.google.com [IPv6:2001:4860:4864:20::2c]) (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 4QrDvZ5nF5z3QFR for ; Tue, 27 Jun 2023 19:15:54 +0000 (UTC) (envelope-from clhamilto@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=I44AcUXI; spf=pass (mx1.freebsd.org: domain of clhamilto@gmail.com designates 2001:4860:4864:20::2c as permitted sender) smtp.mailfrom=clhamilto@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-oa1-x2c.google.com with SMTP id 586e51a60fabf-1a9a2724a62so4124337fac.2 for ; Tue, 27 Jun 2023 12:15:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687893353; x=1690485353; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=9WDXksvE6xodTTEiQ/kOCLSvHX2Qp6/cWVf/PkaAfEo=; b=I44AcUXI6BWZ+g+cw4uMEwRCBuLoX18ZbWiuiQwkZwot5dVUqK4svPk7rHK8dGHUDa +Xfp1i3LAnervYSTC3slwfW3yV5tzW3I0DjPNRc2L/MUoa3NMGQ5Nmi4Y/LLLWU7xBM2 Pq8S0J+qSWa4XhEKeBi3JM00D8/zGiysJ64q9BwlTJ/E2e/XBJkK6haNUgmJp+HS5laM ld6hMuiSAyFBf+kqcaZnwlebGWpJQX8/tDVJTBU4hLlxobQHjE1ndmacVg0TDPR9H/ca W7cWmfTJv+ISrU1kSO8XTXxaoJNYzDxv87Fd1rJftsd/5ydvrWFYg1w754iSduGZfLPE vuFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687893353; x=1690485353; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=9WDXksvE6xodTTEiQ/kOCLSvHX2Qp6/cWVf/PkaAfEo=; b=FdOzxPDehVCmZLnZ6h0MefXi9YdLy7CSNG139jqHn452LpK4mGO71OKhnbydhL+HHh ZGGAynvamO4qlLqXL7cbo9VdFYA8MiaoOxgIgyX+QYvQps1fC/IMGzIwyA8uPw4I0+++ cT72kskWl6DGiCDMzJQGSM2sDVu7wNtaP4MZcNqXXjxSO+tesjL2dAowYGrfJ+/ZwLXN 9/0EVzuCENGhRYRJqIjWSjw7SwFZ1jDy1mEPAt3SL2xT7XcyaF9JB7OCkJ20x7hIHpu6 z8sbF5DaR/JYUNG192pyRfA+vwj5JP1T9jyJPj80jo9SeusqEw28fCvq148ZRXpoiIkY h/Qg== X-Gm-Message-State: AC+VfDw4obxKQh7XFQ9Wa/3s2QbvLz2q5OVjUoF/429oU3czmDxr/NfE IYL4lQYqT4hYV25tZwGrg0XjhNhDOrWISMqWVPt+mU6IuOY= X-Google-Smtp-Source: ACHHUZ4rUs6QUOY1l8fcq+itNBk+q0zEVb+SrFEqMdsxeCumf18xfYcMes7VXMCIS8vSguOeM4oUU8LUlVGDjsTV1xY= X-Received: by 2002:a05:6870:c7b1:b0:1b0:2f70:15a5 with SMTP id dy49-20020a056870c7b100b001b02f7015a5mr6863716oab.52.1687893352740; Tue, 27 Jun 2023 12:15:52 -0700 (PDT) List-Id: Porting FreeBSD to the PowerPC List-Archive: https://lists.freebsd.org/archives/freebsd-ppc List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org MIME-Version: 1.0 References: <9fc5ca46-cb92-4221-84ce-ca27d0c50b6f@app.fastmail.com> In-Reply-To: <9fc5ca46-cb92-4221-84ce-ca27d0c50b6f@app.fastmail.com> From: Curtis Hamilton Date: Tue, 27 Jun 2023 15:15:42 -0400 Message-ID: Subject: Re: POWER9 Blackbird Powerup Issue To: Brandon Bergren Cc: FreeBSD PowerPC ML Content-Type: multipart/alternative; boundary="000000000000b59e8305ff214b27" X-Spamd-Result: default: False [-1.33 / 15.00]; NEURAL_HAM_LONG(-0.91)[-0.908]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_SPAM_SHORT(0.41)[0.412]; R_SPF_ALLOW(-0.20)[+ip6:2001:4860:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; NEURAL_SPAM_MEDIUM(0.16)[0.164]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; MLMMJ_DEST(0.00)[freebsd-ppc@freebsd.org]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MID_RHS_MATCH_FROMTLD(0.00)[]; ASN(0.00)[asn:15169, ipnet:2001:4860:4864::/48, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_IN_DNSWL_NONE(0.00)[2001:4860:4864:20::2c:from]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FREEMAIL_FROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-ppc@freebsd.org]; RCVD_COUNT_TWO(0.00)[2]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-Rspamd-Queue-Id: 4QrDvZ5nF5z3QFR X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N --000000000000b59e8305ff214b27 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks for the advice. Unfortunately I don=E2=80=99t have a BMC serial port hooked up. Will have = to work on getting that done for the future. However, I did hear back from Raptor Support and I'm sending them the board for non-warranty evaluation/repair. Hopefully, it's a simple fix of debricking a corrupted BMC. Regards On Sat, Jun 17, 2023 at 4:27 PM Brandon Bergren wrote: > You have a BMC serial port hooked up already, correct? (not to be confuse= d > with the host serial port.) > > Here are the procedures to fix OpenBMC after mishaps. > > https://wiki.raptorcs.com/wiki/Debricking_the_BMC > > If those don't work, I would inspect the board carefully for damage. As > long as there isn't physical damage, there is always the option of > reflashing the BMC. > > On Sat, Jun 17, 2023, at 2:29 PM, Curtis Hamilton wrote: > > I=E2=80=99m have an issue with my blackbird and can=E2=80=99t get suppo= rt from RaptorCS > > because it=E2=80=99s out of warranty. So I wanted to see if anyone els= e has > > experienced the same or similar issue. > > > > The blackbird refuses to boot into OpenBMC after being powered off to > > install a discrete GPU. The OpenBMC led ( ) continues to flash rapidly > > with a momentary pause, then continues to flash rapidly. The power led > > stays orange. > > > > I=E2=80=99ve checked raptors wiki, forums and the how-to guides, but do= n=E2=80=99t see > > anything similar to my issue. I=E2=80=99ve tried leaving it completely = powered > off > > for several days but the problem still remains. > > > > Any suggestions/help would really be appreciated. > > > > Regards > > -- > Brandon Bergren > Technical Generalist > --000000000000b59e8305ff214b27 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks for the advice.=C2=A0

Unfortunately I don=E2=80=99t have = a BMC serial port hooked up.=C2=A0 Will have to work on getting that done f= or=C2=A0the=C2=A0future.

However, I d= id hear back from Raptor Support and I'm sending them the board for non= -warranty evaluation/repair. =C2=A0

Hopefully, it&= #39;s a simple fix of debricking a corrupted BMC.

= Regards


On Sat, Jun 17, 2023 at 4:27 PM Brandon Be= rgren <fre= ebsd@bdragon.rtk0.net> wrote:
You have a B= MC serial port hooked up already, correct? (not to be confused with the hos= t serial port.)

Here are the procedures to fix OpenBMC after mishaps.

https://wiki.raptorcs.com/wiki/Debricking_the_BMC

If those don't work, I would inspect the board carefully for damage. As= long as there isn't physical damage, there is always the option of ref= lashing the BMC.

On Sat, Jun 17, 2023, at 2:29 PM, Curtis Hamilton wrote:
> I=E2=80=99m have an issue with my blackbird and can=E2=80=99t get supp= ort from RaptorCS
> because it=E2=80=99s out of warranty.=C2=A0 So I wanted to see if anyo= ne else has
> experienced the same or similar issue.
>
> The blackbird refuses to boot into OpenBMC after being powered off to<= br> > install a discrete GPU.=C2=A0 The OpenBMC led ( ) continues to flash r= apidly
> with a momentary pause, then continues to flash rapidly.=C2=A0 The pow= er led
> stays orange.
>
> I=E2=80=99ve checked raptors wiki, forums and the how-to guides, but d= on=E2=80=99t see
> anything similar to my issue. I=E2=80=99ve tried leaving it completely= powered off
> for several days but the problem still remains.
>
> Any suggestions/help would really be appreciated.
>
> Regards

--
=C2=A0 Brandon Bergren
Technical Generalist
--000000000000b59e8305ff214b27--