Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 21 Jun 2016 06:33:58 -0400 (EDT)
From:      Keith White <kwhite@site.uottawa.ca>
To:        Mark Millard <markmi@dsl-only.net>
Cc:        otacilio.neto@bsd.com.br, freebsd-arm <freebsd-arm@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: (beagleboneblack/urtwn) Kernel page fault with the following non-sleepable locks held [ssh on rpi2 comparison]
Message-ID:  <alpine.BSF.2.20.1606210626320.52002@localhost.my.domain>
In-Reply-To: <99277FB6-77EB-4D8B-8A55-FBD622D29AC3@dsl-only.net>
References:  <99277FB6-77EB-4D8B-8A55-FBD622D29AC3@dsl-only.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 21 Jun 2016, Mark Millard wrote:

> OtacĂ­lio otacilio.neto at bsd.com.br wrote on Tue Jun 21 00:06:39 UTC 2016 :
>
>> > The kernel panic is totally reproducible. I need only do a ssh in the
>> > beaglebone using ptty on windows or ssh on freebsd and the kernel 
>> > panic is raised.
> . . .
>> FreeBSD11-ALPHA4 shows the same behavior. The only thing that I need to 
>> raise the fault is ssh in the beaglebone.
>
> (After this quotes are command input/output from my test activity.)
>
> Under 11.0 -r310975 on a rpi2 I can ssh out of the rpi2 just fine. . .
>
>> # uname -apKU
>> FreeBSD rpi2 11.0-ALPHA4 FreeBSD 11.0-ALPHA4 #1 r301975M: Thu Jun 16 18:12:02 PDT 2016     markmi@FreeBSDx64:/usr/obj/clang/arm.armv6/usr/src/sys/RPI2-NODBG  arm armv6 1100117 1100117
>
>
> This is a no-debug kernel build (but with symbols). Details are given later below.
>
>> # ssh markmi@192.168.0.105
>> Password:
>> Last login: Tue Jun 21 01:04:46 2016
>> markmi$ 
>
> Similarly I can ssh into the rpi2 from outside, here using new remote connection in Mac OS X terminal: ssh 192.168.0.119 resulted in. . .
>
>> Password for markmi@rpi2:
>> Last login: Mon May  9 19:27:33 2016 from 192.168.2.1
>> FreeBSD 11.0-ALPHA4 (RPI2-NODBG) #1 r301975M: Thu Jun 16 18:12:02 PDT 2016
>> 
>> Welcome to FreeBSD!
>> 
>> Release Notes, Errata: https://www.FreeBSD.org/releases/
>> Security Advisories:   https://www.FreeBSD.org/security/
>> FreeBSD Handbook:      https://www.FreeBSD.org/handbook/
>> FreeBSD FAQ:           https://www.FreeBSD.org/faq/
>> Questions List: https://lists.FreeBSD.org/mailman/listinfo/freebsd-questions/
>> FreeBSD Forums:        https://forums.FreeBSD.org/
>> 
>> Documents installed with the system are in the /usr/local/share/doc/freebsd/
>> directory, or can be installed later with:  pkg install en-freebsd-doc
>> For other languages, replace "en" with a language code like de or fr.
>> 
>> Show the version of FreeBSD installed:  freebsd-version ; uname -a
>> Please include that output and any error messages when posting questions.
>> Introduction to manual pages:  man man
>> FreeBSD directory layout:      man hier
>> 
>> Edit /etc/motd to change this login announcement.
>> To determine whether a file is a text file, executable, or some other type
>> of file, use
>>
>> 	file filename
>> 		-- Dru <genesis@istar.ca>
>> $ 
>
> No panics or other odd notices.
>
> The problem is apparently not general to all armv6 contexts.
>
> Various context details follow. . .
>
>> # more ~/src.configs/src.conf.rpi2-clang-bootstrap.rpi2-host 
>> TO_TYPE=armv6
>> #
>> KERNCONF=RPI2-NODBG
>> TARGET=arm
>> .if ${.MAKE.LEVEL} == 0
>> TARGET_ARCH=${TO_TYPE}
>> .export TARGET_ARCH
>> .endif
>> #
>> #WITH_CROSS_COMPILER=
>> WITH_SYSTEM_COMPILER=
>> #
>> #CPUTYPE=soft
>> WITH_LIBSOFT=
>> WITH_LIBCPLUSPLUS=
>> WITH_BINUTILS_BOOTSTRAP=
>> #WITHOUT_CLANG_BOOTSTRAP=
>> WITH_CLANG=
>> WITH_CLANG_IS_CC=
>> WITH_CLANG_FULL=
>> WITH_CLANG_EXTRAS=
>> WITH_LLDB=
>> #
>> WITH_BOOT=
>> WITHOUT_LIB32=
>> #
>> WITHOUT_ELFTOOLCHAIN_BOOTSTRAP=
>> WITHOUT_GCC_BOOTSTRAP=
>> WITHOUT_GCC=
>> WITHOUT_GCC_IS_CC=
>> WITHOUT_GNUCXX=
>> #
>> NO_WERROR=
>> #WERROR=
>> MALLOC_PRODUCTION=
>> #
>> WITH_DEBUG_FILES=
>> #
>> XCFLAGS+= -march=armv7-a -mcpu=cortex-a7
>> XCXXFLAGS+= -march=armv7-a -mcpu=cortex-a7
>> # There is no XCPPFLAGS but XCPP ets XCFLAGS content.
>
> ~/src.configs/make.conf was empty.
>
>> # more /usr/src/sys/arm/conf/RPI2-NODBG
>> #
>> # RPI2 -- Custom configuration for the Raspberry Pi 2
>> #
>> # For more information on this file, please read the config(5) manual page,
>> # and/or the handbook section on Kernel Configuration Files:
>> #
>> #    http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
>> #
>> # The handbook is also available locally in /usr/share/doc/handbook
>> # if you've installed the doc distribution, otherwise always see the
>> # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
>> # latest information.
>> #
>> # An exhaustive list of options and more detailed explanations of the
>> # device lines is also present in the ../../conf/NOTES and NOTES files.
>> # If you are in doubt as to the purpose or necessity of a line, check first
>> # in NOTES.
>> #
>> 
>> ident           RPI2-NODBG
>> 
>> include         "RPI2"
>> 
>> makeoptions     DEBUG=-g                # Build kernel with gdb(1) debug symbols
>> options         ALT_BREAK_TO_DEBUGGER
>> #options        VERBOSE_SYSINIT         # Enable verbose sysinit messages
>> 
>> options         KDB                     # Enable kernel debugger support
>> 
>> # For minimum debugger support (stable branch) use:
>> #options        KDB_TRACE               # Print a stack trace for a panic
>> options         DDB                     # Enable the kernel debugger
>> 
>> nooptions       INVARIANTS              # Enable calls of extra sanity checking
>> nooptions       INVARIANT_SUPPORT       # Extra sanity checks of internal structures, required by INVARIANTS
>> nooptions       WITNESS                 # Enable checks to detect deadlocks and cycles
>> nooptions       WITNESS_SKIPSPIN        # Don't run witness on spinlocks for speed
>> nooptions       DIAGNOSTIC
>
>
> My /usr/src tree has some changes/additions --but mostly for powerpc64 and powerpc issues:
>
>> # svnlite status /usr/src/
>> M       /usr/src/contrib/llvm/lib/CodeGen/SelectionDAG/SelectionDAGBuilder.cpp
>> M       /usr/src/lib/csu/powerpc64/Makefile
>> ?       /usr/src/sys/amd64/include/include
>> ?       /usr/src/sys/arm/conf/RPI2-NODBG
>> ?       /usr/src/sys/arm/include/include
>> M       /usr/src/sys/boot/ofw/Makefile.inc
>> M       /usr/src/sys/boot/powerpc/Makefile
>> M       /usr/src/sys/boot/powerpc/Makefile.inc
>> M       /usr/src/sys/boot/uboot/Makefile.inc
>> M       /usr/src/sys/conf/Makefile.powerpc
>> M       /usr/src/sys/conf/kern.mk
>> M       /usr/src/sys/conf/kmod.mk
>> M       /usr/src/sys/dev/cxgb/ulp/tom/cxgb_listen.c
>> M       /usr/src/sys/dev/cxgbe/tom/t4_listen.c
>> ?       /usr/src/sys/powerpc/conf/GENERIC64-NODBG
>> ?       /usr/src/sys/powerpc/conf/GENERIC64vtsc
>> ?       /usr/src/sys/powerpc/conf/GENERIC64vtsc-NODEBUG
>> ?       /usr/src/sys/powerpc/conf/GENERICvtsc
>> ?       /usr/src/sys/powerpc/conf/GENERICvtsc-NODEBUG
>> ?       /usr/src/sys/powerpc/include/include
>> M       /usr/src/sys/powerpc/ofw/ofw_machdep.c
>> M       /usr/src/sys/powerpc/powerpc/exec_machdep.c
>> ?       /usr/src/sys/x86/include/include
>
> (The include/include ones are from something making links pointing back up to the parent include/ . I did not explicitly create these.)
>
> (The cxbg and cxbge ones were from trying to have amd64 target amd64 via xtoolchain (devel/amd64-gcc). But other places also stopped it and I quit trying that for now.)
>
>> # more /etc/rc.conf
>> hostname="rpi2"
>> ifconfig_ue0="DHCP"
>> sshd_enable="YES"
>> 
>> powerd_enable="YES"
>> 
>> # Nice if you have a network, else annoying.
>> ntpd_enable="YES"
>> ntpd_sync_on_start="YES"
>> 
>> # Uncomment to disable common services (more memory)
>> #cron_enable="NO"
>> #syslogd_enable="NO"
>> sendmail_enable="NONE"
>> sendmail_submit_enable="NO"
>> sendmail_outbound_enable="NO"
>> sendmail_msp_queue_enable="NO"
>> #
>> # Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable
>> dumpdev="AUTO"
>> #
>> dbus_enable="YES"
>> hald_enable="YES"
>> #
>> rpcbind_enable="YES"
>> nfs_server_enable="YES"
>> mountd_flags="-r"
>> #
>> nfs_client_enable="YES"
>
>> # more /etc/sysctl.conf 
>> # $FreeBSD: head/etc/sysctl.conf 112200 2003-03-13 18:43:50Z mux $
>> #
>> #  This file is read when going to multi-user and its contents piped thru
>> #  ``sysctl'' to adjust kernel values.  ``man 5 sysctl.conf'' for details.
>> #
>> 
>> # Uncomment this to prevent users from seeing information about processes that
>> # are being run under another UID.
>> #security.bsd.see_other_uids=0
>> 
>> kern.nodump_coredump=1
>> kern.capmode_coredump=1
>> kern.sugid_coredump=1
>> kern.corefile=/var/crash/%N.%P.core
>
>
> /etc/fstab , /etc/exports , /etc/resolv.conf are very simple but non-default. Other than password files and the like the rest of /etc/. . . is just defaults.
>
>> # more /boot/loader.conf 
>> kern.cam.boot_delay="10000"
>
>
>
>
> ===
> Mark Millard
> markmi at dsl-only.net
>
> _______________________________________________
> freebsd-arm@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"

I'm using an RPI-B rather than RPI2, but my symptoms are similar.

Did you use the wired or wireless interface on the RPI2?  I only
get the panic on the RPI-B when using wireless.  Wired works fine.

In an earlier message Ian said that he thought he knew what the
problem was...

...keith
From owner-freebsd-arm@freebsd.org  Tue Jun 21 11:11:31 2016
Return-Path: <owner-freebsd-arm@freebsd.org>
Delivered-To: freebsd-arm@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 9A4BCAC4761
 for <freebsd-arm@mailman.ysv.freebsd.org>;
 Tue, 21 Jun 2016 11:11:31 +0000 (UTC)
 (envelope-from otacilio.neto@bsd.com.br)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com
 [IPv6:2607:f8b0:400d:c09::22e])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 53BC61A3A
 for <freebsd-arm@freebsd.org>; Tue, 21 Jun 2016 11:11:31 +0000 (UTC)
 (envelope-from otacilio.neto@bsd.com.br)
Received: by mail-qk0-x22e.google.com with SMTP id a186so15336777qkf.0
 for <freebsd-arm@freebsd.org>; Tue, 21 Jun 2016 04:11:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta;
 h=subject:to:references:cc:from:message-id:date:user-agent
 :mime-version:in-reply-to:content-transfer-encoding;
 bh=7+yyYS0H/RCGAjBzJ/j/Cwrd6JwfVwpcLdMnm+8zR/I=;
 b=EXi5mPXVEplIo6Yz28vEYT1sh6mDhtDN73ZT8IQKKnans/HLAlERzin/2j2Qea+POg
 AgBzO+8YuN5IwzhkO1c+B8VLwLDo/iM04JVhWt1XmPyKwwW20tyGCS930b+/RJBPhc16
 wfX52s/b6LKssSGVaDsuhmFp9Udq9/UlZPAXA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:subject:to:references:cc:from:message-id:date
 :user-agent:mime-version:in-reply-to:content-transfer-encoding;
 bh=7+yyYS0H/RCGAjBzJ/j/Cwrd6JwfVwpcLdMnm+8zR/I=;
 b=hQ+XcDxi9BbsRs1duvyPTlZDnHvWps5FTAj2Ct2D5p1AJsxtTNk8eR+BVme+62jngf
 1N9EsJ6M3EfgZqAaJs3fx56KScxSVonaMOi/BK7A1LqQXaich3Xy2U3HxFoqBm8iMJEb
 fv0+9WRnY32hJqaduwjm2bK+Vt901ST7t22GXAQpluY83OhSJmYlMsVe+uaLJrJJhi4z
 O068NNOL4tstPzS3/ppMuO0T6p7UbCvoauuqtvMuqG76HKdKnGN/mnneAUNuxV1e0f1L
 V5dpXLjnrGNsXpJUVwuVv9fhiLdCK0awzO+R6hsT6rV21yIqTjhLudq1u/pU8fHSv5NI
 EsEQ==
X-Gm-Message-State: ALyK8tILXSPqUW/xfHE+j47lB2K563iBwHZSC0lNCFCQAGiOLaFOhGlW9Tjcvanu3FkIHA==
X-Received: by 10.200.37.150 with SMTP id e22mr28331867qte.37.1466507490246;
 Tue, 21 Jun 2016 04:11:30 -0700 (PDT)
Received: from [192.168.0.18] ([187.60.94.34])
 by smtp.googlemail.com with ESMTPSA id j62sm9981934qtb.35.2016.06.21.04.11.28
 (version=TLSv1/SSLv3 cipher=OTHER);
 Tue, 21 Jun 2016 04:11:29 -0700 (PDT)
Subject: Re: (beagleboneblack/urtwn) Kernel page fault with the following
 non-sleepable locks held [ssh on rpi2 comparison]
To: Keith White <kwhite@site.uottawa.ca>, Mark Millard <markmi@dsl-only.net>
References: <99277FB6-77EB-4D8B-8A55-FBD622D29AC3@dsl-only.net>
 <alpine.BSF.2.20.1606210626320.52002@localhost.my.domain>
Cc: freebsd-arm <freebsd-arm@freebsd.org>,
 FreeBSD Current <freebsd-current@freebsd.org>
From: =?UTF-8?B?T3RhY8OtbGlv?= <otacilio.neto@bsd.com.br>
Message-ID: <22fe5f7f-6153-e092-c410-eddb1431a78a@bsd.com.br>
Date: Tue, 21 Jun 2016 08:11:07 -0300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <alpine.BSF.2.20.1606210626320.52002@localhost.my.domain>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>;
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2016 11:11:31 -0000

Em 21/06/2016 07:33, Keith White escreveu:
> In an earlier message Ian said that he thought he knew what the
> problem was... 

Here the problem occurs  when using wifi. I do not have tested wired 
because I don't have a cable here.


[]'s

-Otacilio




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1606210626320.52002>