>
>The person who followed up with a list of things that *may* have made
>the
problem go away mentioned one of the things was disabling powerd.
>Do you have
that enable, and if yes would you mind disabling it to see
>if that's the
culprit?
>
>Thanks for the report.
Hi, it's the person speaking
>> About kgdb...
>> I never used freebsd-update, so sorry if I'm saying
something
>> stupid, but could it be the case that the kernel has been
built
>> without debugging symbols or something like that? Does freebsd-
>>
update provide a kernel.debug?
>
>I haven't had to use a the kernel.debu
On 2008-11-23, at 18:36 , Barbara wrote:
About kgdb...
I never used freebsd-update, so sorry if I'm saying
something
stupid, but could it be the case that the kernel has been
built
without debugging symbols or something like that? Does freebsd-
update provide a kernel.debug?
I haven't h
Ken,
I built a GENERIC debug kernel, and now have a backtrace that I can
provide related to this problem on 6.4-RC2:
surfer# kgdb /sys/i386/compile/GENERIC/kernel.debug /var/crash/vmcore.1
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by
About kgdb...
I never used freebsd-update, so sorry if I'm saying
>>
something
stupid, but could it be the case that the kernel has been
>>
built
without debugging symbols or something like that? Does freebsd-
>> update provide a kernel.debug?
>>>
>>> I haven't had to us
On 2008-11-24, at 1:51 , Barbara wrote:
About kgdb...
I never used freebsd-update, so sorry if I'm saying
something
stupid, but could it be the case that the kernel has been
built
without debugging symbols or something like that? Does freebsd-
update provide a kernel.debug?
I have
