From owner-freebsd-amd64@FreeBSD.ORG Wed May 19 02:55:50 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB1B016A4CE; Wed, 19 May 2004 02:55:50 -0700 (PDT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3886743D53; Wed, 19 May 2004 02:55:49 -0700 (PDT) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with SMTP id i4J9pc67086381; Wed, 19 May 2004 11:51:39 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <0def01c43d86$f35f7d50$471b3dd4@dual> From: "Willem Jan Withagen" To: References: <0c5901c43d2a$0d0b9480$471b3dd4@dual> Date: Wed, 19 May 2004 11:52:08 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 cc: freebsd-current@freebsd.org Subject: Re: Panic at line 602 in file ffs_vnops.c X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 May 2004 09:55:51 -0000 ----- Original Message ----- From: "Willem Jan Withagen" > In an attempt to port some compiler tools, I'm testing its memory allocator. > And that does not really work, it is a shure way to crash my dual opteron. > > panic: ffs_write: uio -> uio_resid < 0 > at line 602 in file /home2/src/sys/ufs/ffs/ffs_vnop.c > > If I then type 'cont' I'd exepct to get coredump. > But it just gives up on 708 buffers, prints the uptime > and sits quitely in a corner until I hard-reset it. > No other keys will get it back.... > > Before it crashes I first get the inocent LOR on ....swap...:1313 > The program usually get an invalid pointer allocated with calloc. > And as far as I can tell, then crashes on free-ing with this pointer. > > Any takers on this?? > Looks to me there are 2 problems: > I'm able to upset allocator with this program. > (If I write the same program, in shorthand, it stays alive) > The system does not want to dump/reboot To follow up on myself: 'where' after the crash gives: (copied via paper) ffs_write() at ... +0x64e vn_rdwr() at ... +0xf1 vn_rdwr_inchuncks() at ... +0x77 elf64_coredump() at ... +0x1222 coredump() at ... +0x5da sigexit() at ... +0x71 postsig() at ... +0x30e ast() at ... +0x297 Xfas_syscall() at ... +0xdd ------ syscall(0, FreeBSD ELF64, nosys) rip = 0x20067b8ec rsp = 0x7fffffffe678 rbp = 0x2006de6c0 So it looks like the systems want to write a dump, but does not really get to write it.... What more can I do?? --WjW