From owner-freebsd-current@freebsd.org Sun Aug 26 03:51:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 82A3810A0C37 for ; Sun, 26 Aug 2018 03:51:24 +0000 (UTC) (envelope-from theron.tarigo@gmail.com) Received: from mail-pg1-x536.google.com (mail-pg1-x536.google.com [IPv6:2607:f8b0:4864:20::536]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1487E8EC83 for ; Sun, 26 Aug 2018 03:51:23 +0000 (UTC) (envelope-from theron.tarigo@gmail.com) Received: by mail-pg1-x536.google.com with SMTP id s15-v6so5944103pgv.8 for ; Sat, 25 Aug 2018 20:51:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:subject:to:cc:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=M7a828qNyiKXmIXySBtnuK79lnuNGQ58zMAi6qWVqrw=; b=syO/BU+qJCHb+a4pYEjTYPq4I9W6ZzMMCODRzlljjANVKmookL4wejHKdAzNFILldc l4szXXliQanYX2OvmV4086TAfbTTjoWKOG3YiiuWFWGuK2ACMLwTfbsMG+8xvWAEO20u Ve9OIm6UdqcUmL3BHqOuD1lp9pefYLXXWkYcRAREg65d8aYpA17nKra/tQOiXXXY2jku TGi0anJXjVyym5m4a7VnWwXeJZ2Pheot965wljW1aPK6ekozpirutqyTPh0X4RST17Rn /QlchW5Q1DKc1ToBFmaE9S++PhrdzqsQv1/28T3fi7rd+DcTyNpF0UPd25sUiLBqoH7d Q/NA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:subject:to:cc:message-id:date :user-agent:mime-version:content-transfer-encoding:content-language; bh=M7a828qNyiKXmIXySBtnuK79lnuNGQ58zMAi6qWVqrw=; b=dw6ou9CR2ihV0CISjq1zBwqiZs1aqA4Y8Y848l06GERhg39JhVkf1LZlUJqoO/aCEO 0oOL+9P3pwUQtYeZy2IB/jhxVKBClm4VFNUGRtlZCYHMd5hbKC5sELTLkLVPZ90Vsxn2 i7Z8r1EKWzHa/FfEjpoYHZan9EV8Sz6vgswQjQsvMPJimdjc0HRgNpNynxBNhkgEz6Rh v0C+tyI3wV4aenmvzDTudy8Mr6oZkJEk5YHzweLWam2+UZAy4Lpw9BMuK3V4Mz7DQB38 Ryv5m+Nf4ralypz5D83rJM2++76awEM86pv0D9wEI79m1t4P3WnEnyc+rm01O/tTCDwB 4KWA== X-Gm-Message-State: APzg51DImdZdGZBoxeT+TC480lWdX3LQDQZeNZHrJhZPMLioNz8OqWdc fgGRPSCgDFI0xJ/h7cte1/A= X-Google-Smtp-Source: ANB0Vda3h7/gaV03gwnk9kXrkNDeEuxfAQlMac8KkEGbBSF3i8WvKK/49pDc5ao5KRUzKochCZrXnA== X-Received: by 2002:a62:25c5:: with SMTP id l188-v6mr8358161pfl.179.1535255483088; Sat, 25 Aug 2018 20:51:23 -0700 (PDT) Received: from [192.168.1.24] (c-73-170-47-221.hsd1.ca.comcast.net. [73.170.47.221]) by smtp.gmail.com with ESMTPSA id i25-v6sm21247566pfi.150.2018.08.25.20.51.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 25 Aug 2018 20:51:22 -0700 (PDT) Sender: Theron Tarigo From: Theron Subject: r336876 breaks sysutils/acpi_call To: FreeBSD Current Cc: gelraen.ua@gmail.com Message-ID: <72380894-6f0c-30e9-b755-d79a8a38a1eb@gmail.com> Date: Sat, 25 Aug 2018 23:51:21 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Aug 2018 03:51:24 -0000 A recent change in CURRENT has sysutils/acpi_call reliably cause a kernel panic when run on a Dell XPS laptop system.  I bisected this to r336876: Use SMAP on amd64.  I would have thought that this is a simple compatibility problem requiring only a port update, except that the same kernel and acpi_call on different hardware are not affected.  On the problematic system, the kernel module loads without incident; it is when executing ACPI commands, even normally harmless operations such as requesting read-only constants, that the system freeze occurs.  ACPI functionality seems otherwise unaffected. Kernel debugging console and crash dumps are also broken on this system (I suspect due to Intel graphics) however it is an unrelated problem, and is only an excuse for my inability to provide any further crash information. Having already bisected to the breaking commit, is there anything else I should do to improve the chances this problem gets fixed, or are there any hardware compatibility notes I may have missed? Theron