From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id EB21DC3DA41 for ; Tue, 9 Jul 2024 12:49:06 +0000 (UTC) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=ellerman.id.au header.i=@ellerman.id.au header.a=rsa-sha256 header.s=201909 header.b=cTf6Gnaa; dkim-atps=neutral Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4WJLQn4McMz3dBp for ; Tue, 9 Jul 2024 22:49:05 +1000 (AEST) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=ellerman.id.au Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=ellerman.id.au header.i=@ellerman.id.au header.a=rsa-sha256 header.s=201909 header.b=cTf6Gnaa; dkim-atps=neutral Received: from mail.ozlabs.org (gandalf.ozlabs.org [150.107.74.76]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4WJLQ02s3Zz3cdB for ; Tue, 9 Jul 2024 22:48:24 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ellerman.id.au; s=201909; t=1720529304; bh=tR/p3OVCCVxP1O40AG1XUapVdWpxiZNGVHuoNkO2YZw=; h=From:To:Subject:In-Reply-To:References:Date:From; b=cTf6GnaaV57ps0rTXSjTPCsRz1wVfBgf5rjEa/vW1v8DEPel6Z1pUqtC6Y/IRkMBL gdV1BuRk4xXMJ6bh7mIor2i/7KbXhHM6KpnZ/WmFT4pX3cuYOKwacP2yhqvVgzz76B L9dI84Jvf1I8RN1W3cif5EZuHcI7+7gs5ZVihGO5e7q6j17fxzp4X48ePeGOZxaeAP dZV7nrfMdBhA1r2J6bDkbnxGPM59ifXexJKK/tJR6FIw1cf7Obh4jJJ7774k2SVczg +EK5tCB0hzG1QOpMEJI7wZKCVMGElHN0UY0/z9OINTZ7MxFsWREMmJAqd66yEj0f5s xJZJOFp1eXu0g== Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (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) (No client certificate requested) by mail.ozlabs.org (Postfix) with ESMTPSA id 4WJLQ01Wzhz4x0w; Tue, 9 Jul 2024 22:48:23 +1000 (AEST) From: Michael Ellerman To: Damien Stewart , linuxppc-dev@lists.ozlabs.org Subject: Re: [PowerPC] [PASEMI] Issue with the identification of ATA drives after the of/irq updates 2024-05-29 In-Reply-To: References: <12665d67dcf74cd9a2cd8388d8106f8d@kernel.org> Date: Tue, 09 Jul 2024 22:48:23 +1000 Message-ID: <87plrm68a0.fsf@mail.lhotse> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" Damien Stewart writes: > Hello. > >> How does it fail? I've repeatedly asked for dmesg outputs >> for working and non-working configurations. > > I am the alleged tester. Attached are two dmesg logs. First one fails. > Second passes with 2nd IRQ patch. Also attached is device tree blob if > I've followed the correct command. > > The good log is direct from dmesg. But the bad log is collected live > over serial, since it ends up in kernel panic, with no where to save > it. Thanks. Which kernel is the bad log from? Just plain rc6 with no patches? What happened when you tried the patch from me? I think Christian called it vmlinux-6.10-17. Did you get any different output? Does anything appear before the "hash-mmu" lines? Those are from the kernel, we'd really like to see the output from firmware which runs before that. cheers