On Tue, 23 Sep, at 08:00:31AM, Nathan Whitehorn wrote:
Could you try adding -mno-avx2 to /sys/boot/amd64/Makefile.inc line 9?
Do you pull the -mno-redzone flag anywhere? I'm looking through the
loader sources now, and I see that switch in sys/conf/kern.mk, but it
doesn't look like that's being
On 9/17/2014 10:39 AM, Bryan Drewery wrote:
On 9/16/2014 9:28 PM, Bryan Drewery wrote:
I've been getting this quite frequently on head recently. I have dumps
if anyone is interested in more information.
Fatal trap 9: general protection fault while in kernel mode
cpuid = 10; Memory modified
On Wed, Sep 24, 2014 at 11:48 AM, Bryan Drewery bdrew...@freebsd.org wrote:
Another, with much more information here:
https://people.freebsd.org/~bdrewery/cam.panic.txt
This was with memguard (vm.memguard.desc=CAM CCB) and a KASSERT in
malloc(9) and uma_zalloc_arg() to prevent M_WAITOK in
This patch adds locking to wds(4) and marks it MPSAFE. It also includes
several other cleanups such as using bus_space instead of inb/outb. The patch
is against HEAD but probably applies to 9 and 10 as well.
http://people.freebsd.org/~jhb/patches/ncr_locking.patch
--
John Baldwin
I have three patches to convert various pc98 drivers from timeout() to
callout(). For the fdc driver I took a more drastic approach and have
attempted to port the PC98 support into the main fdc driver:
http://people.FreeBSD.org/~jhb/patches/pc98_fdc.patch
The pckbd driver needs a similar
This patch converts a few timers in isp(4) from timeout(9) to callout(9). It
already used callout(9) for normal command timeouts. The patch is against
HEAD but probably applies to 9 and 10 as well.
http://people.freebsd.org/~jhb/patches/isp_callout.patch
--
John Baldwin
On Tuesday, September 23, 2014 09:29:48 AM Marcel Moolenaar wrote:
What is going on here?
Are we still in some kind of flux and people aren't done yet or is
this the intended state by virtue of noone having anything left on
there TODO list?
Sorry to ask a dumb question, but are you sure you
On Sat, 13 Sep 2014, Benjamin Kaduk wrote:
On Sat, 13 Sep 2014, Marcin Cieslak wrote:
Hello,
I tried loading gallant.fnt which I did not
like and I was wondering how to come back to
the nice default font.
There does not seem to be the way to do this,
so please find below a simple patch to
On Sep 24, 2014, at 12:54 PM, John Baldwin j...@freebsd.org wrote:
On Tuesday, September 23, 2014 09:29:48 AM Marcel Moolenaar wrote:
What is going on here?
Are we still in some kind of flux and people aren't done yet or is
this the intended state by virtue of noone having anything left on
On Wed, 24 Sep 2014 16:33:46 -0700
Marcel Moolenaar mar...@xcllnt.net wrote:
On Sep 24, 2014, at 12:54 PM, John Baldwin j...@freebsd.org wrote:
On Tuesday, September 23, 2014 09:29:48 AM Marcel Moolenaar wrote:
What is going on here?
Are we still in some kind of flux and people aren't
On Sep 24, 2014, at 4:47 PM, Justin Hibbits chmeeed...@gmail.com wrote:
It should probably error out instead, since the build
environment isn't sane at this point. I ran into this probably a few
weeks back.
The only thing the FreeBSD build is good at, really, is
building in /usr/src for
On Sep 24, 2014, at 16:33, Marcel Moolenaar mar...@xcllnt.net wrote:
On Sep 24, 2014, at 12:54 PM, John Baldwin j...@freebsd.org wrote:
On Tuesday, September 23, 2014 09:29:48 AM Marcel Moolenaar wrote:
What is going on here?
Are we still in some kind of flux and people aren't done yet or
#11 0x80976e12 in vmem_xfree (vm=0x816d2200,
addr=18446741889258000384, size=0) at /usr/src/sys/kern/subr_vmem.c:1237
#12 0x80bafbe0 in memguard_free (ptr=value optimized out) at
/usr/src/sys/vm/memguard.c:421
#13 0x80904191 in free (addr=0xfe03648a9000,
13 matches
Mail list logo
