Date: Sun, 22 Sep 2013 05:11:30 -0700 From: Davide Italiano <davide@freebsd.org> To: Lars Engels <lars.engels@0x20.net> Cc: Tim Kientzle <kientzle@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Panic in arptimer on r255764 Message-ID: <CACYV=-HhdAazWyy9yff8pfnMQ5xjqen7DytRDuNvAxHWR2EqQw@mail.gmail.com> In-Reply-To: <20130922092510.GA57847@e-new.0x20.net> References: <0BB63711-3DF7-42F4-AD23-F2767F41B808@freebsd.org> <20130922092510.GA57847@e-new.0x20.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 22, 2013 at 2:25 AM, Lars Engels <lars.engels@0x20.net> wrote: > On Sat, Sep 21, 2013 at 11:23:47PM -0700, Tim Kientzle wrote: >> I'm seeing this panic pretty consistently when I try to do a buildworld on r255764 (i386): >> >> http://people.freebsd.org/~kientzle/r255764%20panic%202013-09-21%20at%209.27.09%20PM.png >> >> I'm not seeing it on r255602, so I suspect it's a recent problem. >> >> Running on VMWare Fusion 6. This was about as vanilla a build as you >> can get: no local code changes, no custom config, no src.conf or >> make.conf, no ports installed, etc. >> > > +1 > > I also see this on yesterday's HEAD: > > http://bsd-geek.de/pics/IMG_20130922_100936.jpg > > The only difference is that I don''t need to run a buildworld, just > going into multi user and wait a few seconds. > I don't see this in single user mode, though. Try this: http://people.freebsd.org/~davide/review/lc_calloutfix.diff I'll commit as soon as I'll receive OK from re@. -- Davide "There are no solved problems; there are only problems that are more or less solved" -- Henri Poincare
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACYV=-HhdAazWyy9yff8pfnMQ5xjqen7DytRDuNvAxHWR2EqQw>