From owner-freebsd-current@freebsd.org Mon Jan 18 21:03:58 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 610314F557A for ; Mon, 18 Jan 2021 21:03:58 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DKPR02sxtz3F8m; Mon, 18 Jan 2021 21:03:54 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2020.home.selasky.org (unknown [178.17.145.105]) (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) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id A0555260599; Mon, 18 Jan 2021 22:03:51 +0100 (CET) Subject: Re: bus_dmamem_alloc failed to align memory properly To: Steve Kargl , freebsd-current@freebsd.org, Konstantin Belousov References: <20210118175133.GA49553@troutmask.apl.washington.edu> From: Hans Petter Selasky Message-ID: <6cc7ae53-5898-3802-469b-6b55613519f7@selasky.org> Date: Mon, 18 Jan 2021 22:03:38 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0 MIME-Version: 1.0 In-Reply-To: <20210118175133.GA49553@troutmask.apl.washington.edu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4DKPR02sxtz3F8m X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.30 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+a:mail.turbocat.net:c]; MID_RHS_MATCH_FROM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[selasky.org]; RBL_DBL_DONT_QUERY_IPS(0.00)[88.99.82.50:from]; TO_DN_SOME(0.00)[]; SPAMHAUS_ZRD(0.00)[88.99.82.50:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:88.99.0.0/16, country:DE]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 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: Mon, 18 Jan 2021 21:03:58 -0000 On 1/18/21 6:51 PM, Steve Kargl wrote: > I've used a SCHED_BSD for a long time on my i586-*-freebsd > laptop. Recently, FreeBSD just locks up on this system. No > panic. No screen. No keyboard. Nothing. So, yesterday, while > trying to deal with the blank console problem, I switch to > SCHED_ULE to see if solved this lock-up issue. It doesn't. :-( > > I now have a number of messages during boot. > > % dmesg | grep align > bus_dmamem_alloc failed to align memory properly. > bus_dmamem_alloc failed to align memory properly. > bus_dmamem_alloc failed to align memory properly. > bus_dmamem_alloc failed to align memory properly. > bus_dmamem_alloc failed to align memory properly. > > I never seen these messages, so is this normal for SCHED_ULE. > > In addition, to the mystrey lock-up. It now seems that > wpa_supplicant is broken. The initial instances, started > at boot, is using 100% CPU. I need to kill that instance > along with openvpn (which of course needs the network). > The D-Link cardbud ath NIC is ejected, re-insert it, and > the network start up as normal. > Hi, This appears to be a known issue. I think kib@ is working on it. --HPS