From nobody Tue Apr 19 08:49:23 2022 X-Original-To: freebsd-current@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 72BB911DE2AD for ; Tue, 19 Apr 2022 08:49:35 +0000 (UTC) (envelope-from michaelsprivate@gmail.com) Received: from mail-il1-x133.google.com (mail-il1-x133.google.com [IPv6:2607:f8b0:4864:20::133]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KjHYB3XhYz4dGF for ; Tue, 19 Apr 2022 08:49:34 +0000 (UTC) (envelope-from michaelsprivate@gmail.com) Received: by mail-il1-x133.google.com with SMTP id i8so5061725ila.5 for ; Tue, 19 Apr 2022 01:49:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=SQhNkqHThB5H1n7WwqIg7oFqZZcziXly1z77daE6oec=; b=kuH6AvGx0L7BezXIJzBTaam+lNGF/sqGUkh2uYQw42DO3VF5buLdDG2YGR6855TuHm YdXdqx2ornliwj8jBOheS7pZoVv1cMNrfQ3IAh1xNihLvCT3y9hAHVs5+m0c8aKJR3jZ GdKIVSzZo+jKxUknfEUuDMfvJ85aTBODhzY+nMfs1Yrl0gNzfuBZrvJlERif4KxWBuFW 003Co3ZrIZpoQyCsvnXUywF2z6NVAhCxCl6gRbzpbd/iSa1BQBUIwnR7H4x3/w5BGPTs XqUzL7djCrq/xXga4RQYsL0TCxumznt/lsBF2FtgLM/jaXDgTrs5Q63HNmZhWPynGtEq +d6A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=SQhNkqHThB5H1n7WwqIg7oFqZZcziXly1z77daE6oec=; b=RmXKwf5ZKY/fzoXmNwgxRjB17x1kbjG4DD26jSOCmA3HlDOBUdQiaMGOk6Sd3iON9P OWC3scziw0ErmU70XzAYd899bbLJ6zFzFdKVDDFLEYp9bu+OmqjHxw0DloNvzjNssZfw O7maY0pBZKZIQTW9bVxho4k0u77qvm1D67hWe7/Q8k0iF18RkSJWcQWhQlq7tRrl+uId 4rdvpWYYZznW4eeQNYvajefrLgZjt0xbfwDGPfFiL9cuxjrf3hUPV39qgdurHbhsH5cF bvWc7Owj5gSE4VC6jeO7ZjZMy+km1nxjvu/IB4F8xkMROXED8OeuexxPs8y2oHVvER4v Dk/Q== X-Gm-Message-State: AOAM530X7k830EqzUN9z7SX7V99FnZYua+MTP+8tGvHOgiR6PuaZSF1D hM+xCTPRIinluSzwDeOdqv5EOlkWm/1SNuPo2T82wrLzcF0HvA== X-Google-Smtp-Source: ABdhPJwaCnPmYDsKQWU1VFSWGkfsqCATxzuRxfuXeg3XSw4PogKQhTx/nFUv/KqKm5OGdSTho80XVP6TFKhFC6hO/b8= X-Received: by 2002:a05:6e02:14c2:b0:2ca:b671:dea3 with SMTP id o2-20020a056e0214c200b002cab671dea3mr6125765ilk.63.1650358173503; Tue, 19 Apr 2022 01:49:33 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <0c1b4885-dd0f-b48f-2ffe-12ccfd2ec118@filis.org> <3b85072c-eb07-6a74-fae3-258c99756c11@nomadlogic.org> In-Reply-To: <3b85072c-eb07-6a74-fae3-258c99756c11@nomadlogic.org> From: Michael Schuster Date: Tue, 19 Apr 2022 10:49:23 +0200 Message-ID: Subject: advice sought: workflow with -CURRENT and amd GPU [Re: -CURRENT hangs since at least 2022-04-04] To: FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4KjHYB3XhYz4dGF X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=kuH6AvGx; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of michaelsprivate@gmail.com designates 2607:f8b0:4864:20::133 as permitted sender) smtp.mailfrom=michaelsprivate@gmail.com X-Spamd-Result: default: False [-3.98 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.98)[-0.982]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::133:from]; NEURAL_HAM_SHORT(-0.99)[-0.995]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-ThisMailContainsUnwantedMimeParts: N Hi, I'm highjacking and re-purposing the previous thread, I hope that's OK (I did change the subject ;-)) - I'm keeping some of the previous contents for reference. I have similar HW to OP (Ryzen 7 4700 w. Renoir Graphics), and have been using a similar approach to keep the machine up to date - or so I suspect. Still, after a while (several months), I end up with one or more of these: - I get some sort of panic in DRM (at startup or, currently, at shutdown) - when I boot into to a previous BE to attempt a fix and then again reboot into the current one, I get tons of messages like this "... kernel: KLD iic.ko: depends on kernel - not available or version mismatch ... kernel: linker_load_file: /boot/kernel/iic.ko - unsupported file type" and computer refuses to accept input (let alone start X) and some others I don't recall right now. Before I ask for advice (see below), let me explain the approaches I've taken so far. I install with ZFS from the beginning, current boot env is "N". These are outlines, not exact commands: I) never touch the current BE, always update a new one: 1) given current BE N, I create a new BE N+1 and mount it on /mnt, 2) 'cd /usr/src; git pull; sudo make DESTDIR=/mnt ... (build, install, etc)' 3) 'cd usr/ports/graphics/drm-devel-kmod; sudo make DESTDIR=/mnt install' 4) beadm activate BE N+1; reboot II) keep a "new" BE as backup/fallback, update current BE: 1) given current BE N, I create a new BE N+1 (mounting not required) (this is the intended 'fallback') 2) 'cd /usr/src; git pull"; then "make" as described in the Handbook "24.6. Updating FreeBSD from Source" 3) 'cd usr/ports/graphics/drm-devel-kmod; sudo make install' 4) reboot in both scenarios(sp?), I do "pkg update; pkg upgrade" from time to time (also following the resp. approach shown above). I suspect that I'm missing something fundamental in my approaches - does anyone have a (for them) foolproof approach along these lines, or can someone show me what I'm missing in either of mine (in private, if you prefer)? TIA for all and any advice Michael On Mon, Apr 18, 2022 at 9:33 PM Pete Wright wrote: > > > > On 4/18/22 12:23, filis+fbsdcurrent@filis.org wrote: > > Hi, > > > > I'm running -CURRENT on this one desktop box which is a "Ryzen 7 4800U > > with Radeon Graphics", since it didn't work on 13R. > > I use Boot environments and on 2022-04-04 I updated it and it started > > to completely freeze under X (I haven't tried letting it run without > > X) after a few dozen minutes. > [...] > > > After updating your CURRENT environment did you rebuild the drm-kmod > package? that's usually required as the LKPI is much more of a moving > target on that branch compared to STABLE or RELEASE. i have a pretty > much identical setup and building/installing drm-devel-kmod has been > working flawlessly for quite a while. > > after building/installing my latest world i do following (this is from a > local script i use when rebuilding): > > cd $PORTS/graphics/drm-devel-kmod > sudo pkg unlock -y drm-devel-kmod > sudo make package > sudo pkg upgrade -y work/pkg/*.pkg > sudo pkg lock -y drm-devel-kmod > > -pete > > -- > Pete Wright > pete@nomadlogic.org > @nomadlogicLA > > -- Michael Schuster http://recursiveramblings.wordpress.com/ recursion, n: see 'recursion'