On Thu, Mar 19, 2009 at 12:34:56AM +0100, Raphael Becker wrote:
> info.0 says:
> Dump header from device /dev/label/TOPSWAP
> Architecture: i386
> Architecture Version: 2
> Dump Length: 246185984B (234 MB)
> Blocksize: 512
> Dumptime: Sat Mar 14 22:43:46 2009
> Hostname: top.uugrn.org
>
On Mon, Mar 16, 2009 at 11:59:25AM -0600, Dan Allen wrote:
> I saw that someone else had this happen last week... It is not a
> hardware failure.
>
> While building the latest GCC 4.4 from /usr/ports/lang/gcc44 I got a
> core dump with the message
>
> vm_page_insert: page already inser
On 18 Mar 2009, at 10:02 AM, John Baldwin wrote:
On Monday 16 March 2009 1:59:25 pm Dan Allen wrote:
I saw that someone else had this happen last week... It is not a
hardware failure.
While building the latest GCC 4.4 from /usr/ports/lang/gcc44 I got a
core dump with the message
vm_
On Monday 16 March 2009 1:59:25 pm Dan Allen wrote:
> I saw that someone else had this happen last week... It is not a
> hardware failure.
>
> While building the latest GCC 4.4 from /usr/ports/lang/gcc44 I got a
> core dump with the message
>
> vm_page_insert: page already inserted
>
On Mon, 16 Mar 2009 17:23:09 -0600
Dan Allen wrote:
> It turns out that one must have a debug kernel around. I use STABLE
> as a production system. There is no "kernel.debug" on my system. I
> guess I therefore cannot provide a stack trace.
Have you disbled building of the kernel.debug th
On Mon, Mar 16, 2009 at 5:47 PM, Dan Allen wrote:
>
> On 16 Mar 2009, at 1:01 PM, Alan Cox wrote:
>
>> For now, can you just provide the stack trace?
>
> As I mentioned, I am unable to do so - I have no kernel.debug.
>
> However, I am trying to reproduce the bug again. (It takes a while.)
> Alth
On 16 Mar 2009, at 1:01 PM, Alan Cox wrote:
For now, can you just provide the stack trace?
As I mentioned, I am unable to do so - I have no kernel.debug.
However, I am trying to reproduce the bug again. (It takes a while.)
Although it has not yet crashed, I noticed another unusual behavi
On 16 Mar 2009, at 3:42 PM, Patrick Lamaizière wrote:
Le Mon, 16 Mar 2009 14:49:43 -0600,
Dan Allen :
For now, can you just provide the stack trace?
How do I do this? Is there a tool that I run against the core dump?
See
http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug
Le Mon, 16 Mar 2009 14:49:43 -0600,
Dan Allen :
> > For now, can you just provide the stack trace?
>
> How do I do this? Is there a tool that I run against the core dump?
See
http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html
Regards.
_
On 16 Mar 2009, at 1:01 PM, Alan Cox wrote:
For now, can you just provide the stack trace?
How do I do this? Is there a tool that I run against the core dump?
BTW, I just did the same gcc-4.4 build on my Mac and it built fine
without any core dumps...
Dan
__
On Mon, Mar 16, 2009 at 12:59 PM, Dan Allen wrote:
> I saw that someone else had this happen last week... It is not a hardware
> failure.
>
I have not seen that. I have only seen an assertion failure that would have
nothing to do with your reported panic.
>
> While building the latest GCC 4.
I saw that someone else had this happen last week... It is not a
hardware failure.
While building the latest GCC 4.4 from /usr/ports/lang/gcc44 I got a
core dump with the message
vm_page_insert: page already inserted
I build this port every week on a Toshiba laptop (1.8GHz Core 2
12 matches
Mail list logo
