Date: Sat, 6 Feb 2016 12:48:09 -0800 From: Adrian Chadd <adrian.chadd@gmail.com> To: Rob Mixer <rob.mixer@ni.com> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: Bus Errors on Cubox i4pro with snapshot 20160127 Message-ID: <CAJ-Vmo=Z-6KLP_cMTPjHm5q4%2BAW1Uy7e8qAN97mRzrTHSfhP5w@mail.gmail.com> In-Reply-To: <95FB6DD8-FBD6-468A-B553-C5B363A4D9DB@ni.com>
index | next in thread | previous in thread | raw e-mail
Hi, So just to be clear, you're getting sig10 errors in your userland programs, right? -a On 5 February 2016 at 17:31, Rob Mixer <rob.mixer@ni.com> wrote: > Hi! > > Is there a known solution to bus errors associated with Snort and Suricata on Cubox i4pro? I’ve seen it both the 20160121 and 20160127 snapshots of FreeBSD11-arm-armv6. > > Under heavy I/O load, I keep getting bus errors (signal 10). The I/O load occurs when I start Snort (pkg) or Suricata (from ports). The bus error occurs within about 10 seconds of these applications starting to read from the ffec0 Gig-E interface. It typically results in a core dump. Occurs regardless of whether I have PF enabled or not. Could this be a pcap issue? > > I’ve also experienced this with pfctl -sa, but I see that there is a patch in the works for that. > > BTW, I’ve been able to get up an running with FreeBSD 11 snapshots with a Cubox i4Pro with few issues. So far, it’s a huge improvement over 10.2 on Cubox! > > > Rob > _______________________________________________ > 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"help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=Z-6KLP_cMTPjHm5q4%2BAW1Uy7e8qAN97mRzrTHSfhP5w>