Date: Mon, 18 Jan 2021 22:03:38 +0100 From: Hans Petter Selasky <hps@selasky.org> To: Steve Kargl <sgk@troutmask.apl.washington.edu>, freebsd-current@freebsd.org, Konstantin Belousov <kib@FreeBSD.org> Subject: Re: bus_dmamem_alloc failed to align memory properly Message-ID: <6cc7ae53-5898-3802-469b-6b55613519f7@selasky.org> In-Reply-To: <20210118175133.GA49553@troutmask.apl.washington.edu> References: <20210118175133.GA49553@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6cc7ae53-5898-3802-469b-6b55613519f7>