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 gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (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 9CAF2C3DA61 for ; Wed, 24 Jul 2024 16:02:35 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 30F7D10E121; Wed, 24 Jul 2024 16:02:35 +0000 (UTC) Authentication-Results: gabe.freedesktop.org; dkim=pass (2048-bit key; unprotected) header.d=intel.com header.i=@intel.com header.b="RCZc7UKb"; dkim-atps=neutral Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.19]) by gabe.freedesktop.org (Postfix) with ESMTPS id F10FF10E121 for ; Wed, 24 Jul 2024 16:02:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1721836952; x=1753372952; h=from:to:cc:subject:in-reply-to:references:date: message-id:mime-version; bh=FB/NQES9xdDLtZWyVEjsPvnyR9vBD/U1pB78qFte/ew=; b=RCZc7UKbsIrMO32ohKm+4VGERfkBIEdKtnpWwEppfqN9NlxnCfrVwnl4 HilS+MbnCw44nzUDwHmYRwnkzJUxVfJNlvkBk0Ey+pnFU6vDMT7Y1K282 4iRTgOzc/JhczrnOCzq3SGAzGF0Y/es4dH6XvZgzA6OxidQq/cJXDnAhO M7PRTieBH0MG8rE21623gtf3l5GUh62TGM86cUW4xSiAkWvicBp8D16Nz i4i09nv4EDMUQwwNW9xGmM+MqQgQivuPupO39nzy5WIR7p38FD1UdxPr5 voaJRli6ko93L0alqqFVmL/3JQGTQ7j/NeZBpBTGHhl4JKwvIfnvwy5Na g==; X-CSE-ConnectionGUID: PYhmunLYQymYtzlI7CBcKQ== X-CSE-MsgGUID: d5Z4/BZvTC6IYw7D2HqKAA== X-IronPort-AV: E=McAfee;i="6700,10204,11143"; a="19380001" X-IronPort-AV: E=Sophos;i="6.09,233,1716274800"; d="scan'208";a="19380001" Received: from fmviesa001.fm.intel.com ([10.60.135.141]) by orvoesa111.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 Jul 2024 09:02:32 -0700 X-CSE-ConnectionGUID: khtGNgfRQeOI0Rls/Mmydw== X-CSE-MsgGUID: vrv463CrTZe+jFmzRLb1Ww== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.09,233,1716274800"; d="scan'208";a="83638504" Received: from bergbenj-mobl1.ger.corp.intel.com (HELO localhost) ([10.245.246.197]) by smtpauth.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 Jul 2024 09:02:30 -0700 From: Jani Nikula To: Francesco Poli , Intel GFX list Cc: 1075770@bugs.debian.org Subject: Re: [bug report] adlp_tc_phy_connect [i915] floods logs with drm_WARN_ON(tc->mode == TC_PORT_LEGACY) call traces In-Reply-To: <20240715203543.63b40a68931fdc45332ba9f8@paranoici.org> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <20240715203543.63b40a68931fdc45332ba9f8@paranoici.org> Date: Wed, 24 Jul 2024 19:02:16 +0300 Message-ID: <8734nykcc7.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: intel-gfx@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Intel graphics driver community testing & development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" On Mon, 15 Jul 2024, Francesco Poli wrote: > Hi all, > on a laptop where I installed Debian testing some 6 months ago, > I noticed that the logs are continuously flooded with call traces > like the attached snippet (taken from /var/log/kern.log ). > > It seems to me that it also used to happen with previous versions > of the Linux kernel, but I am under the impression that, with Linux > kernel 6.9.7, it got worse. I have recently upgraded to Linux kernel > version 6.9.8 (provided by the distro, Debian testing, as I said), but > the bug is still reproducible: > > $ uname -srvmo > Linux 6.9.8-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.9.8-1 (2024-07-07) x86_64 GNU/Linux > > I see at least 12 of these call traces just after boot, before even > starting X (with 'startx'). > More of these call traces are sent to the logs after starting X, or > after invoking 'xrandr', or after locking the X session (with > XScreenSaver), ... > I always see these call traces (I mean the bug is always reproducible: > each time I boot, each time I call xrandr, ...). > > They seem to correspond to no actual issue, as far as I can tell, > but they are flooding the logs with a significant flow of text... > which is worrying by itself. > > > What's wrong? > How can I stop this log-filling flood? > Should I black-list some module, for instance? > > > The outputs of > > # lspci -vnn -d :*:0300 > > and of > > # dmidecode > > are attached. > Also, I booted with kernel parameters > 'drm.debug=0xe log_buf_len=4M ignore_loglevel' and > logged in as root right after the boot. > The output of > > # dmesg > > is attached. > > Some additional information may be found on the [Debian bug] report I had previously filed. > > [Debian bug]: > > > N.B.: > Please Cc me and the Debian bug address <1075770@bugs.debian.org> > on replies, so that the interested parties (including me!) are kept > in the loop. > Thanks a lot for your time and for any help you may provide! Please file i915 bugs at fdo gitlab as described at [1]. BR, Jani. [1] https://drm.pages.freedesktop.org/intel-docs/how-to-file-i915-bugs.html -- Jani Nikula, Intel