From nobody Tue Sep 3 07:42:33 2024 X-Original-To: bugs@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 4WyczJ5LjQz5MT3p for ; Tue, 03 Sep 2024 07:42:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 "mxrelay.nyi.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WyczJ44pdz4bPV for ; Tue, 3 Sep 2024 07:42:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1725349356; a=rsa-sha256; cv=none; b=DQcbId9qgXB950KG1bIkGUQOJKq/SxxXV/RLdIDqd/VhAkoIdoozga2LhZpY9rTsah6PYC 5p+fzTVeGe+cbuOmNDVCckWRQHQRXyROrQTvNmNZ6jN7yZufuLehl5qBWuhVaGcfcuRr1V Q+BCx+/aAoALNz1/mifofgUxFJQJX9NjJoA9fWlqGX58fgqPyY2JEIWsHpzUkUoQxnHwmO SOyPAw44i/prkslzD07AyN2pYokgf6ESpTking5rg+afnZSqyM/BEqIfh+K60+92Veh3jW IOs3a3NIYZ37Yz5utpPymHABihXhDCVZ+AHQJJU+8ol2aoQlbv9GmkIVVUF9dQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1725349356; 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: in-reply-to:in-reply-to:references:references; bh=W/SdhpRK9MOerKnB62kQuits/hC0qJaFOrZID2cwOsg=; b=C3JuLI+y/r3wzOOFaM5/L7YmJFr4rx0wGr6gCD2dSj4cX4tHI6J9Y87JPds9MYHM9x43Cf KR07C47f5EqVtTXW1uZWswLHPdCZxsjneu2lU6aLpj/FvDc9aZJmbJGJ94XuF7U2bmPvLt i3iFKmSXzkoBA3k23JPhnFZPigacVttcvknaax+Eg++9Vkb7+/G5MSlXxiBguXDwmVYrju ipd3TwfS/4GvDwe8rlA2d0oJrDtqM0VG4fP6SaPTwtsPyAX5DMqHH5hlUpQsGbA13MQ8xT S22Q+zX6e4TaJQWtRpz42X5SxczS7FoVlaGq0AAdwykI33NdJV4hcvn2XeIVfg== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4WyczJ3hrlzXY7 for ; Tue, 3 Sep 2024 07:42:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 4837gaMr087300 for ; Tue, 3 Sep 2024 07:42:36 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 4837ga8K087286 for bugs@FreeBSD.org; Tue, 3 Sep 2024 07:42:36 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 276985] crash in LinuxKPI/drm Date: Tue, 03 Sep 2024 07:42:33 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 14.1-RELEASE X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: olce@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: mfc-stable14? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D276985 --- Comment #26 from Olivier Certner --- (In reply to Tomasz "CeDeROM" CEDRO from comment #24) Do you prefer "not able to test"? But to me, your own reactions so far, besides what you expressly wrote, border on "not willing to test". > There are various problems with AMDGPU / DRM / LinuxKPI that are reported= by various people Yes, but... > so I am not alone Well, judging by your stack traces and those reported by other users, it currently looks like you're alone, yes. > and those problems are disqualifying FreeBSD 14+ from a production use in= that setup Please stop spreading this FUD. Lots of people use FreeBSD 14 in production with DRM. I personally have several machines with AMD and Intel GPUs using stacks with 14 (and DRM 5.10, 5.15 and 6.1) and am really happy with them. And, at the risk of sounding repetitive, I also have a RX 580 like you, but contrary to you never saw a single crash on 14 (last ones were around 2 years ago... on 13-STABLE). There are some problems, more or less annoying, which I (and others) have reported in some bugs, but none are critical and more importantly they all = can be worked around. Some people are also reporting crashes, part of which seem to happen in very specific situations (unlike what you're reporting). I have not seen any pr= oof so far that these behaviors are regressions compared to an older stack (e.g= ., involving 13) or that the bug isn't present in a comparable Linux stack (sa= me DRM version, and ideally same libraries). To my current knowledge, you're absolutely the only one claiming a regression from 13. If you don't have the time or will to test newer stacks, it's perfectly fin= e, and in any case you're responsible for your own strategy going forward. But you're also: - Spreading FUD by over-generalizing your own case. - Mixing problems by dumping your reports, traces and related advice in some bugs without having any evidence that these are really related (besides "my= RX 580 crashes with amdgpu and 14"). Actually, a simple examination of stack traces in the various bugs could have lead you to see that on your own. Wh= en in doubt, create a new bug anyway, we can always mark it as a duplicate afterwards. This attitude is actively hampering, or even harming, problem reporting and resolution for *everyone*. So please stop it. --=20 You are receiving this mail because: You are the assignee for the bug.=