From owner-freebsd-current@freebsd.org Sat Jul 15 19:32:49 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3DA92B7A766 for ; Sat, 15 Jul 2017 19:32:49 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 1E6F182430 for ; Sat, 15 Jul 2017 19:32:49 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: by mailman.ysv.freebsd.org (Postfix) id 1AD2DB7A765; Sat, 15 Jul 2017 19:32:49 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 18922B7A764 for ; Sat, 15 Jul 2017 19:32:49 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [202.12.127.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C9B968242F for ; Sat, 15 Jul 2017 19:32:48 +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-language:content-type:content-type:in-reply-to :mime-version:user-agent:date:date:message-id:references:from :from:subject:subject; s=201508; t=1500147159; bh=f8VWXoRTaDvEjP M/A3QF32Z2M0p/R/3lYjgF6kar20g=; b=DDXVlZx9L0zraQJvo9zXWXUkYono5t wXd7y7UNcUUwXCTii966b+MMKz6tHGfxhdKtIDwfUZpT9HNB8iXllMBGVN54aHMI xPnHlk/WLjr66Mnud07emQersivYf3PiSUkLuELBxUKDqIJckZI3IiXdHjDNEaPh UwEuQvUaACMNI= Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id 84158F0A5; Sat, 15 Jul 2017 15:32:39 -0400 (EDT) Subject: Re: Panic on boot after upgrade from r320827 -> r320869 From: Michael Butler To: Warner Losh Cc: FreeBSD Current References: <20170710115109.GD1177@albert.catwhisker.org> <20170711121311.GI1177@albert.catwhisker.org> <954e8793-7e17-8ae4-8449-39c742e0d432@protected-networks.net> Message-ID: <405f9924-5354-c6ba-0fc1-c4acf3eebcda@protected-networks.net> Date: Sat, 15 Jul 2017 15:32:38 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Sat, 15 Jul 2017 19:32:49 -0000 On 07/11/17 19:53, Michael Butler wrote: > On 07/11/17 13:13, I wrote: >>> Take sdhci out of the kernel and try again. If that works, it tells >>> us one >>> thing (need to troubleshoot sdhci stuff more). If not it tells us >>> another >>> (need to troubleshoot CAM more), do we get errors with the ATA_IDENTIFY >>> command? Does it try multiple times per AHCI port? What AHCI device >>> do you >>> have? You may need to scroll back with the screen-lock / pageup keys >>> to see >>> these messages. > > [ .. snip .. ] > >> I'll try this tonight when I'm back at home. The laptop concerned uses >> the ICH-7M part in "legacy mode" so it doesn't do AHCI at all :-( > > Without sdhci and mmc, it actually boots but everything KDE aborts with > signal 6 :-( > > I'm not prepared to rebuild the ~1900 ports on this box to pursue this > further, Something about SVN r320844 causes almost all KDE applications to fail on a signal 6. I've recompiled KDE and other components obviously dependent on kernel structures (e.g. everything dbus-related). I still get core-files with a back-trace that looks like: (gdb) bt #0 0x0000000804232f6a in thr_kill () from /lib/libc.so.7 #1 0x0000000804232f34 in raise () from /lib/libc.so.7 #2 0x0000000804232ea9 in abort () from /lib/libc.so.7 #3 0x00000008188597af in ?? () from /usr/local/lib/libdbus-1.so.3 #4 0x000000081884ef2c in _dbus_warn_check_failed () from /usr/local/lib/libdbus-1.so.3 #5 0x000000081883f539 in dbus_message_new_method_call () from /usr/local/lib/libdbus-1.so.3 #6 0x0000000801bddfe8 in ?? () from /usr/local/lib/qt4/libQtDBus.so.4 #7 0x0000000801bd591e in ?? () from /usr/local/lib/qt4/libQtDBus.so.4 #8 0x0000000801bd9af6 in ?? () from /usr/local/lib/qt4/libQtDBus.so.4 #9 0x0000000801be656d in ?? () from /usr/local/lib/qt4/libQtDBus.so.4 #10 0x0000000801be6807 in QDBusInterface::QDBusInterface(QString const&, QString const&, QString const&, QDBusConnection const&, QObject*) () from /usr/local/lib/qt4/libQtDBus.so.4 #11 0x000000080d12728e in ?? () from /usr/local/lib/libsolid.so.4 #12 0x000000080d11e68c in ?? () from /usr/local/lib/libsolid.so.4 #13 0x000000080d12a525 in ?? () from /usr/local/lib/libsolid.so.4 #14 0x000000080d0e7aac in Solid::Device::listFromType(Solid::DeviceInterface::Type const&, QString const&) () from /usr/local/lib/libsolid.so.4 #15 0x000000080e7e889a in ?? () from /usr/local/lib/libplasma.so.3 #16 0x000000080e7e6094 in Plasma::RunnerManager::RunnerManager(QObject*) () from /usr/local/lib/libplasma.so.3 #17 0x00000008172fab42 in ?? () from /usr/local/lib/libkdeinit4_krunner.so #18 0x00000008172fa9b4 in ?? () from /usr/local/lib/libkdeinit4_krunner.so #19 0x00000008172fd303 in kdemain () from /usr/local/lib/libkdeinit4_krunner.so #20 0x000000000040a015 in ?? () #21 0x000000000040aec0 in ?? () SVN r320843 works, r320844 doesn't :-( imb