Received: by 2002:a05:6a10:eb17:0:0:0:0 with SMTP id hx23csp77375pxb; Wed, 8 Sep 2021 18:02:30 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzjLe4gAWHGmQjwa4ary75TL64S5kEokpqz5q+yMz9tVTOujjU3NqS2pP3H6azsQvieD9IC X-Received: by 2002:a05:6e02:1bc5:: with SMTP id x5mr247623ilv.83.1631149349934; Wed, 08 Sep 2021 18:02:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1631149349; cv=none; d=google.com; s=arc-20160816; b=Io8z9xdrc380I3zOcU8Rj3CVD1ke52QC6Nb5/STk6K9hKHyZ4l9dWiwcwX6bSJ3cb6 o17CvrN7wjvBdJk1jGSmwh7B+6Mr9hk/XrBMi/DHnYW1+A5U9VOq/NOxcqXSI5iJZaAg t/HPLxLLaBpcLHvbBHO2ahj2pD5W0nJYqOGyU2FSG4PH0Ld/wGmZp5PS2kRmwS6oyT1f W0q3tUFOwAOFSCFBeG+5tNUswzUbgiKhiooYQUFjMLwkKlbBVmfXtxNw18ohX2zxlwuV /bo+blSVf628xRvZKpBTYz6OzNv8LVwJybX/S1l364n2+M6jixsVnWY1lvCkh/LcAVdc jmow== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:reply-to:message-id:subject:cc:to:from:date; bh=BxOKwfXEyYQH1j8eoLIapZ/TB+ACJPZfkj4KsFSe2II=; b=qzF/szw/Bi77LgiUkiGklDAL0vvKEcDB0gySzGEo2y5UkrrxeHuoZmdWX9wLa1w661 lu8twg7mbGjGuQz0FmN3lSa3n7E9kHPaJJksCnECFEae4ygoR/pwPp+9igFUFWaKz0+0 q+OXuwcBn35Wg/tmss/4tjc3Y4tCdDDNRtTKfgYDQ9wX5haHYhM2h+vEumVAdcnlg+L3 4TjOR8MpLeSsuSccqx7EkclYYI3i4kgbInZfAphhngD+3sVOsJKvzhyXt1hI3MsGDulL tkG0iTFYfmnWaBJVKlEx1EHny3VAiMuWET8Na8ormKLeqRrQwniMtCc4eU/zpbf9UQ+o aMvw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=tudelft.nl Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id p8si249648ilh.169.2021.09.08.18.02.15; Wed, 08 Sep 2021 18:02:29 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=tudelft.nl Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1349038AbhIIA5k (ORCPT + 99 others); Wed, 8 Sep 2021 20:57:40 -0400 Received: from x127130.tudelft.net ([131.180.127.130]:54186 "EHLO djo.tudelft.nl" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1348847AbhIIA5k (ORCPT ); Wed, 8 Sep 2021 20:57:40 -0400 Received: by djo.tudelft.nl (Postfix, from userid 2001) id EC4DD1C42C2; Thu, 9 Sep 2021 02:57:48 +0200 (CEST) Date: Thu, 9 Sep 2021 02:57:48 +0200 From: wim To: Greg KH Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org, wim Subject: Re: kernel-4.9.270 crash Message-ID: <20210909005748.GA8236@djo.tudelft.nl> Reply-To: wim@djo.tudelft.nl References: <20210904235231.GA31607@djo.tudelft.nl> <20210905190045.GA10991@djo.tudelft.nl> <20210906093611.GA20123@djo.tudelft.nl> <20210908015139.GA26272@djo.tudelft.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.2 (2019-01-07) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Sep 08, 2021 at 07:30:49AM +0200, Greg KH wrote: > > > > ... > > > > Aug 1 20:51:24 djo kernel: [] ? 0xf8bc4ef7 > > > > > > > > > > > > These aren't going to help us much, can you turn on debugging symbols > > > for these crashes for us to see the symbol names? > > > > ERROR: not enough memory to load nouveau.ko > > That's the only error? Maybe you don't have enough memory? Nouveau.ko with symbols is really huge. I see only 2GB RAM in that machine, so I'm not amazed. > > i915.ko is smaller and my laptop is bigger. Identical crash, no symbols. > > Odd. I've had that before, some years ago. The devs were very reluctant to start investigating. After a while the bug just vanished. Bugs come and go was their remark. This time the bug doesn't vanish spontaneously. > > > > > Can you use 'git bisect' to track down the offending commit? > > and that brought me reasonably fast to this: > > > > 3bd3a8ca5a7b1530f463b6e1cc811c085e6ffa01 is the first bad commit > > commit 3bd3a8ca5a7b1530f463b6e1cc811c085e6ffa01 > > Author: Maciej W. Rozycki > > Date: Thu May 13 11:51:50 2021 +0200 > > ... > > That is a vt change that handles an issue with a console driver, so this > feels like a false failure. > > If you revert this change on a newer kernel release, does it work? No false failure. git checkout v4.9.282 git revert Lo and behold, no crash on modprobe i915 !!! > And what about showing us the symbols of that traceback? What symbols of what traceback? It does not crash! And when it crashes (the previous case) there are no symbols, despite debugging set to on. Just the same log. Apparently it ran invalid code. What does the 'Divide Error: 0000' mean? A divide by zero error? Regards, Wim.