In 9.x ( can't check -current, but teh mailing list has a better
readership)
I'm still seeing this and have still not found any solution:
possible reasons for the change may be:
1/ change to kgdb?
2/ change to the compiling toolset?
3/ change to the .mk files for compiling modules?
any guidance
On 02/04/12 18:50, Alberto Villa wrote:
> On Saturday 04 February 2012 09:06:21 O. Hartmann wrote:
>> Mea culpa, mea culpa, mea maxima culpa!
>>
>> I'm under pressure with my work and I guess I missed something.
>> Yes, of course, I'll give you the requested, as attached. I hope this is
>> satisfyi
On Fri, Feb 03, 2012 at 04:01:46PM -0800, Dmitry Mikulin wrote:
>
> >Please provide more details, I am looking forward for the panic
> >message and backtrace.
>
> I can't seem to get the panic with the latest source base, but tracing
> doesn't appear to work with vfork(). I attached a modified t
* Gary Jennejohn [120204 06:24]:
> On Fri, 3 Feb 2012 13:50:53 -0500
> Derek Tattersall wrote:
>
> > * Ryan Stone [120203 13:41]:
> > > On Fri, Feb 3, 2012 at 9:34 AM, Derek Tattersall wrote:
> > > > I have two drives in a x86-64 machine. ?Drive ada2 has current on it,
> > > > and
> > > > dri
On Saturday 04 February 2012 09:06:21 O. Hartmann wrote:
> Mea culpa, mea culpa, mea maxima culpa!
>
> I'm under pressure with my work and I guess I missed something.
> Yes, of course, I'll give you the requested, as attached. I hope this is
> satisfying, if any request remains, please send me an
Hi Baptiste,
On Jan 30, 2012, at 7:39 AM, Baptiste Daroussin wrote:
Hi,
pkgng has just reached the beta phase, and has now found its way to
the
ports tree (disabled by default).
I'll file an issue on github as well, but wanted to note it here,
too. Seems pkgng segfaults reproducibly
On 2/3/12 11:55 PM, Julian Elischer wrote:
so We upgraded our development machines from 8 stable to 9 stable.
and now kgdb can't debug inside modules.
instead of getting anything useful, we just get:
(kgdb) bt
#0 0x81814600 in ?? () from /boot/kernel/netgraph.ko
#1 0x81812d80
