Re: Panic on kldload/kldunload in/near callout

From: hiren panchasara <hiren_at_strugglingcoder.info>
Date: Sun, 13 Sep 2015 04:06:20 -0700
On 09/13/15 at 01:56P, hiren panchasara wrote:
> On 09/13/15 at 08:51P, Alexander V. Chernikov wrote:
> > 
> > 
> > 12.09.2015, 20:30, "hiren panchasara" <hiren_at_strugglingcoder.info>:
> > > On 09/12/15 at 03:32P, Alexander V. Chernikov wrote:
> > >> ?12.09.2015, 02:22, "hiren panchasara" <hiren_at_strugglingcoder.info>:
> > >> ?> On 09/11/15 at 09:06P, Hans Petter Selasky wrote:
> > >
> > > [skip]
> > >> ?> I'll try to get it. Meanwhile I am getting another panic on idle box:
> > >> ?> http://pastebin.com/9qJTFMik
> > >> ?The easiest explanation could be lack of lla_create() result check, fixed in r286945.
> > >> ?This panic is triggered by fast interface down-up (or just up), when ARP packet is received but there are no (matching) IPv4 prefix on the interface.
> > >> ?If this is not the case (e.g. it paniced w/o any interface changes and there were no other subnets in given L2 segment) I'd be happy to debug this further.
> > >
> > > Just hit another last night. (Box goes to db> ; let me know if you want
> > > to debug anything when that happens.)
> > Would you mind showing full backtrace for that core? (e.g. situation has to be different for newer -current).

Apparently I was using an older current than r286945. :-(
Apologies for the false alarm. I'll update again if I see any issues.

Hiren

Received on Sun Sep 13 2015 - 09:06:21 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:59 UTC