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 X-Spam-Level: X-Spam-Status: No, score=-3.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 78848C4338F for ; Sat, 7 Aug 2021 04:08:48 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id 1791C6101C for ; Sat, 7 Aug 2021 04:08:47 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 1791C6101C Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linux-m68k.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=lists.ozlabs.org Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4GhTNs3d0Vz3d88 for ; Sat, 7 Aug 2021 14:08:45 +1000 (AEST) Authentication-Results: lists.ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=messagingengine.com header.i=@messagingengine.com header.a=rsa-sha256 header.s=fm3 header.b=SIe7dfEK; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.helo=wout1-smtp.messagingengine.com (client-ip=64.147.123.24; helo=wout1-smtp.messagingengine.com; envelope-from=fthain@linux-m68k.org; receiver=) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=messagingengine.com header.i=@messagingengine.com header.a=rsa-sha256 header.s=fm3 header.b=SIe7dfEK; dkim-atps=neutral Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4GhTNL5WZBz308G for ; Sat, 7 Aug 2021 14:08:16 +1000 (AEST) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id C0AC8320093E; Sat, 7 Aug 2021 00:08:13 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Sat, 07 Aug 2021 00:08:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=p5fqgZ FW/PCKi3209KBZ+VDyS35Wj51tuUmUgG58EWM=; b=SIe7dfEK7QfFr8q+cskWE0 wzFjTwm9DVqgQ5TGjQtf3sNcY9MkEkWuiqdYbTdjpTFydG1x1IrjqsHAip88grNq rWS1Qeh9EkWofHVXNxh1FKZYTz7Yk6ES8NlPipkBjjSlVq0bP4viViJNNBtlsbLj k0sRV7UcZSi1IbxxS6nrzHjUvpXPBWp1HIuWRazD8p3rOX8KWYewL8hxv7a7XuQy +MJNM0LY9GHqAjicCMlWSg5CeF2Gt8svYD0HdddYo07BWki296NZrvo0uJhWzLeH fsmmlyzpvF7xehigJWUJGSFP4ZfbfPkFSHo8YB6PmsHucN9bBIZFu73Ec7w0m07g == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrjedvgdejhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvufgjkfhfgggtsehttdertddttddvnecuhfhrohhmpefhihhnnhcuvfhh rghinhcuoehfthhhrghinheslhhinhhugidqmheikehkrdhorhhgqeenucggtffrrghtth gvrhhnpeffudfhgeefvdeitedugfelueegheekkeefveffhfeiveetledvhfdtveffteeu udenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehfth hhrghinheslhhinhhugidqmheikehkrdhorhhg X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 7 Aug 2021 00:08:09 -0400 (EDT) Date: Sat, 7 Aug 2021 14:08:06 +1000 (AEST) From: Finn Thain To: Stan Johnson Subject: Re: Debian SID kernel doesn't boot on PowerBook 3400c In-Reply-To: <06ddf5ab-b0c9-1c64-92ea-a9cfbfb9f3b0@yahoo.com> Message-ID: References: <60841a75-ed7c-8789-15db-272bf43055f5.ref@yahoo.com> <4ac28304-4519-fb8a-a868-e8c79cb5f9e4@yahoo.com> <7532219a-4fd0-416-6365-304033fa6abd@linux-m68k.org> <9659419d-da9e-5aa6-ffbb-758748e2d6e9@linux-m68k.org> <2eb2b452-51d5-c495-3ffe-896c62a1633f@yahoo.com> <6ea50cd7-84d3-5180-0430-1211aaf0e308@yahoo.com> <2619d78-e8f-334a-20c0-2a60c936a293@linux-m68k.org> <73921a8e-6d76-7ae9-1ba2-811966df5179@linux-m68k.org> <06ddf5ab-b0c9-1c64-92ea-a9cfbfb9f3b0@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII 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: , Cc: debian-powerpc@lists.debian.org, linuxppc-dev@lists.ozlabs.org, Nicholas Piggin Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On Fri, 6 Aug 2021, Stan Johnson wrote: > $ egrep '(CONFIG_PPC_KUAP|CONFIG_VMAP_STACK)' .config > CONFIG_PPC_KUAP=y > CONFIG_PPC_KUAP_DEBUG=y > CONFIG_VMAP_STACK=y > $ strings vmlinux | fgrep "Linux version" > Linux version 5.13.0-pmac-00004-g63e3756d1bd ... > $ cp vmlinux ../vmlinux-5.13.0-pmac-00004-g63e3756d1bd-1 > > 1) PB 3400c > vmlinux-5.13.0-pmac-00004-g63e3756d1bd-1 > Boots, no errors logging in at (text) fb console. Logging in via ssh and > running "ls -Rail /usr/include" generated errors (and a hung ssh > session). Once errors started, they repeated for almost every command. > See pb3400c-63e3756d1bdf-1.txt. > > 2) Wallstreet > vmlinux-5.13.0-pmac-00004-g63e3756d1bd-1 > X login failed, there were errors ("Oops: Kernel access of bad area", > "Oops: Exception in kernel mode"). Logging in via SSH, there were no > additional errors after running "ls -Rail /usr/include" -- the errors > did not escalate as they did on the PB 3400. > See Wallstreet-63e3756d1bdf-1.txt. > ... > $ egrep '(CONFIG_PPC_KUAP|CONFIG_VMAP_STACK)' .config > CONFIG_PPC_KUAP=y > CONFIG_PPC_KUAP_DEBUG=y > # CONFIG_VMAP_STACK is not set > $ strings vmlinux | fgrep "Linux version" > Linux version 5.13.0-pmac-00004-g63e3756d1bd ... > $ cp vmlinux ../vmlinux-5.13.0-pmac-00004-g63e3756d1bd-2 > > 3) PB 3400c > vmlinux-5.13.0-pmac-00004-g63e3756d1bd-2 > Filesystem was corrupt from the previous test (probably from all the > errors during shutdown). After fixing the filesystem: > Boots, no errors logging in at (text) fb console. Logging in via ssh and > running "ls -Rail /usr/include" generated a few errors. There didn't > seem to be as many errors as in the previous test, there were a few > errors during shutdown but the shutdown was otherwise normal. > See pb3400c-63e3756d1bdf-2.txt. > > 4) Wallstreet > vmlinux-5.13.0-pmac-00004-g63e3756d1bd-2 > X login worked, and there were no errors. There were no errors during > ssh access. > See Wallstreet-63e3756d1bdf-2.txt. > Thanks for collecting these results, Stan. Do you think that the successful result from test 4) could have been just chance? It appears that the bug affecting the Powerbook 3400 is unaffected by CONFIG_VMAP_STACK. Whereas the bug affecting the Powerbook G3 disappears when CONFIG_VMAP_STACK is disabled (assuming the result from 4 is reliable). Either way, these results reiterate that "Oops: Kernel access of bad area, sig: 11" was not entirely resolved by "powerpc/32s: Fix napping restore in data storage interrupt (DSI)".