Re: Kernel Panic immediately after boot with CARP

2010-10-20 Thread Steve W
Could this be indicative of something with my problem? I can't seem to list a "re" interface with ifconfig. # uptime 8:51PM up 1 day, 8:09, 1 user, load averages: 0.12, 0.09, 0.08 # ifconfig lo0: flags=8049 mtu 33200 priority: 0 groups: lo inet 127.0.0.1 netmask 0xff000

Re: Kernel Panic immediately after boot with CARP

2010-10-03 Thread Steve W
On Sun, 3 Oct 2010 22:24:18 +0200, you wrote: >well, it is easy enough to verify - use something else but re. if it's >stable, we have the guilty party, at least. Yea, I'm sort of stuck with re. Here's a few quick images of these boxes. It's a Jetway NF76 board with a daughter card with 3 RTL8110

Re: Kernel Panic immediately after boot with CARP

2010-10-03 Thread Steve W
On Sun, 3 Oct 2010 22:41:50 +0200, you wrote: >err... reading the trace first helps. this is actually pretty clearly a >problem in re. I don't feel responsible for re tho :) Is there something else I should do before submitting something to bugs? Both of these source files haven't been modified

Re: Kernel Panic immediately after boot with CARP

2010-10-03 Thread Henning Brauer
* Henning Brauer [2010-10-03 22:28]: > * Steve W [2010-10-03 22:16]: > > On Wed, 29 Sep 2010 11:57:10 +0200, you wrote: > > >sigh. use-after-free (most likely, at least) somewhere. unlikely to be > > >carp itself. might be re (wild guess). > > > > I think your "somewhere near re" theory might ha

Re: Kernel Panic immediately after boot with CARP

2010-10-03 Thread Henning Brauer
* Steve W [2010-10-03 22:16]: > On Wed, 29 Sep 2010 11:57:10 +0200, you wrote: > >sigh. use-after-free (most likely, at least) somewhere. unlikely to be > >carp itself. might be re (wild guess). > > I think your "somewhere near re" theory might have some merrit to it. :) well, it is easy enough

Re: Kernel Panic immediately after boot with CARP

2010-10-03 Thread Steve W
On Wed, 29 Sep 2010 11:57:10 +0200, you wrote: >sigh. use-after-free (most likely, at least) somewhere. unlikely to be >carp itself. might be re (wild guess). I think your "somewhere near re" theory might have some merrit to it. :) I've had a number of crashes over the past couple days, but this

Re: Kernel Panic immediately after boot with CARP

2010-09-29 Thread Henning Brauer
* Steve W [2010-09-26 18:46]: > login: panic: pool_do_get(mcl2k): free list modified: page 0xd68bc000;; item > addr 0xd68bc800; offset 0x0=0x2d304436 sigh. use-after-free (most likely, at least) somewhere. unlikely to be carp itself. might be re (wild guess). -- Henning Brauer, h...@bsws.de, he