From nobody Sun Jun 5 15:18:51 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 89A731BEEEB7 for ; Sun, 5 Jun 2022 15:18:54 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [202.12.127.228]) (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 (2048 bits) client-digest SHA256) (Client CN "mail.protected-networks.net", Issuer "R3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4LGKyj3dfBz4b9S; Sun, 5 Jun 2022 15:18:53 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding:content-type :content-type:in-reply-to:from:from:references:content-language :subject:subject:user-agent:mime-version:date:date:message-id; s=201508; t=1654442331; bh=cB2LjijFcpuFLVonBiBvvuwhVBp42x8FQcwf 5buul8k=; b=X7AeR854mQvdkGFleqIm7iB0uPX33wtWJ6bLK80ABk61t2nPfdPa sc4eGG/FRoAbS4F8u7oRd9i/YIXmC83AuzPcl6ojUhlmm+ur/if/DxMGd1WHiSga gxfi7DyfLIk3e6xBNYv9bEdU7AeL2tdbMO7m7Kxlvx0kedMUQV966NA= Received: from [IPV6:2001:470:8d59:2:f21f:afff:fe66:957e] (toshi.auburn.protected-networks.net [IPv6:2001:470:8d59:2:f21f:afff:fe66:957e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id D61A8CD70; Sun, 5 Jun 2022 11:18:51 -0400 (EDT) Message-ID: <98704176-952f-56ee-5d16-9a0ba75d58e3@protected-networks.net> Date: Sun, 5 Jun 2022 11:18:51 -0400 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 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 Subject: Re: commit 99902b1 causes kernel panics Content-Language: en-NZ To: Hans Petter Selasky , freebsd-current Cc: manu@freebsd.org References: <4cff718d-6f0f-bde8-2077-c83f4adc84df@protected-networks.net> <70f3adee-a0a4-3fca-8b12-3911782cf449@selasky.org> From: Michael Butler In-Reply-To: <70f3adee-a0a4-3fca-8b12-3911782cf449@selasky.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4LGKyj3dfBz4b9S X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=protected-networks.net header.s=201508 header.b=X7AeR854; dmarc=pass (policy=reject) header.from=protected-networks.net; spf=pass (mx1.freebsd.org: domain of imb@protected-networks.net designates 202.12.127.228 as permitted sender) smtp.mailfrom=imb@protected-networks.net X-Spamd-Result: default: False [-4.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[protected-networks.net:s=201508]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_LONG(-1.00)[-1.000]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[protected-networks.net:+]; DMARC_POLICY_ALLOW(-0.50)[protected-networks.net,reject]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; MLMMJ_DEST(0.00)[freebsd-current]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:5716, ipnet:202.12.127.0/24, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On 6/5/22 02:09, Hans Petter Selasky wrote: > On 6/4/22 23:21, Michael Butler wrote: >> On a Dell E6430 laptop with an i5-3340M CPU on-board but no additional >> video adapter, this commit causes a panic when i915kms is loaded :-( >> This adapter does not use any additional firmware. >> > > Does the attached patch fix this problem? It does - thanks! Michael