From owner-freebsd-amd64@FreeBSD.ORG Mon May 24 05:35:05 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 B6ACE16A4CE; Mon, 24 May 2004 05:35:05 -0700 (PDT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3490943D31; Mon, 24 May 2004 05:35:04 -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 i4OCUR67087260; Mon, 24 May 2004 14:30:27 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <005901c4418a$f0b5e000$471b3dd4@dual> From: "Willem Jan Withagen" To: "Willem Jan Withagen" , Date: Mon, 24 May 2004 14:30:46 +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: Not able to make coredumps... (Was: 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: Mon, 24 May 2004 12:35:05 -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.... > > And even more follow up: > I tried to just get a coredump by going crtl-alt-esc and go 'panic' in ddb. > But ended up with a freeze and: > > pmap_invalidate_range: interrupts disabled > at line 664 inf file /home2/src/sys/amd64/amd64/pmap.ccpuid=1 > > Where I think the last line should read: > pmap.c cpuid=1 > > I think I need this fixed before I can start looking at the other problem?? To continue this saga, I can reproduce this on i386 as well.... Completely the same effect. Dmesg included. The amd64 version was of sunday late. The i386 version is still somewhat older. > > > > What more can I do?? --WjW From owner-freebsd-amd64@FreeBSD.ORG Mon May 24 05:36:03 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 0483116A4CE; Mon, 24 May 2004 05:36:03 -0700 (PDT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDF9843D2D; Mon, 24 May 2004 05:36:01 -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 i4OCVn67087291; Mon, 24 May 2004 14:31:49 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <006201c4418b$217bfd50$471b3dd4@dual> From: "Willem Jan Withagen" To: "Willem Jan Withagen" , Date: Mon, 24 May 2004 14:32:08 +0200 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_005F_01C4419B.E4D77BC0" 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: Not able to make coredumps... (Was: 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: Mon, 24 May 2004 12:36:03 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_005F_01C4419B.E4D77BC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit This time with Dmesg.... > > > ----- 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.... > > > > And even more follow up: > > I tried to just get a coredump by going crtl-alt-esc and go 'panic' in ddb. > > But ended up with a freeze and: > > > > pmap_invalidate_range: interrupts disabled > > at line 664 inf file /home2/src/sys/amd64/amd64/pmap.ccpuid=1 > > > > Where I think the last line should read: > > pmap.c cpuid=1 > > > > I think I need this fixed before I can start looking at the other problem?? > > To continue this saga, I can reproduce this on i386 as well.... > Completely the same effect. > Dmesg included. The amd64 version was of sunday late. > The i386 version is still somewhat older. > > > > > > > What more can I do?? > > --WjW > ------=_NextPart_000_005F_01C4419B.E4D77BC0 Content-Type: application/octet-stream; name="dmesg.opteron" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="dmesg.opteron" Copyright (c) 1992-2004 The FreeBSD Project.=0A= Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994=0A= The Regents of the University of California. All rights reserved.=0A= FreeBSD 5.2-CURRENT #1: Sun May 23 22:03:51 CEST 2004=0A= wjw@opteron.digiware.nl:/usr/obj/home2/src/sys/OPTERON.amd64=0A= WARNING: WITNESS option enabled, expect reduced performance.=0A= Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff806ab000.=0A= Timecounter "i8254" frequency 1193182 Hz quality 0=0A= CPU: AMD Opteron(tm) Processor 242 (1603.65-MHz K8-class CPU)=0A= Origin =3D "AuthenticAMD" Id =3D 0xf51 Stepping =3D 1=0A= = Features=3D0x78bfbff=0A= AMD Features=3D0xe0500800=0A= real memory =3D 2146304000 (2046 MB)=0A= avail memory =3D 2062696448 (1967 MB)=0A= ACPI APIC Table: =0A= FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs=0A= cpu0 (BSP): APIC ID: 0=0A= cpu1 (AP): APIC ID: 1=0A= ioapic0: Changing APIC ID to 2=0A= ioapic0 irqs 0-23 on motherboard=0A= random: =0A= acpi0: on motherboard=0A= acpi0: [GIANT-LOCKED]=0A= acpi0: Power Button (fixed)=0A= Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000=0A= acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0=0A= cpu0: on acpi0=0A= cpu1: on acpi0=0A= acpi_tz0: on acpi0=0A= acpi_button0: on acpi0=0A= pcib0: port 0xcf8-0xcff on acpi0=0A= pci0: on pcib0=0A= pcib0: possible interrupts: 21=0A= pcib0: slot 16 INTA routed to irq 21 via \\_SB_.PCI0.ALKB=0A= pcib0: possible interrupts: 21=0A= pcib0: slot 16 INTA routed to irq 21 via \\_SB_.PCI0.ALKB=0A= pcib0: possible interrupts: 21=0A= pcib0: slot 16 INTB routed to irq 21 via \\_SB_.PCI0.ALKB=0A= pcib0: possible interrupts: 21=0A= pcib0: slot 16 INTC routed to irq 21 via \\_SB_.PCI0.ALKB=0A= pcib0: possible interrupts: 22=0A= pcib0: slot 17 INTC routed to irq 22 via \\_SB_.PCI0.ALKC=0A= pcib1: at device 1.0 on pci0=0A= pci1: on pcib1=0A= pcib1: slot 0 INTA is routed to irq 16=0A= pci1: at device 0.0 (no driver attached)=0A= pci1: at device 0.1 (no driver attached)=0A= de0: port 0xd000-0xd07f mem = 0xfb050000-0xfb05007f irq 18 at device 7.0 on pci0=0A= de0: [GIANT-LOCKED]=0A= de0: COMPEX unknown 21041 [10Mb/s] pass 1.1=0A= de0: Ethernet address: 00:80:48:ea:6c:8b=0A= em0: port = 0xd400-0xd43f mem 0xfb020000-0xfb03ffff,0xfb000000-0xfb01ffff irq 19 at = device 8.0 on pci0=0A= em0: [GIANT-LOCKED]=0A= em0: Ethernet address: 00:0e:0c:35:2b:f8=0A= em0: Speed:N/A Duplex:N/A=0A= bge0: mem = 0xfb040000-0xfb04ffff irq 16 at device 11.0 on pci0=0A= miibus0: on bge0=0A= brgphy0: on miibus0=0A= brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, = 1000baseTX-FDX, auto=0A= bge0: Ethernet address: 00:0c:76:ac:93:4a=0A= bge0: [GIANT-LOCKED]=0A= atapci0: port = 0xd800-0xd80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.0 on pci0=0A= ata0: at 0x1f0 irq 14 on atapci0=0A= ata1: at 0x170 irq 15 on atapci0=0A= uhci0: port 0xdc00-0xdc1f irq 21 at device = 16.0 on pci0=0A= uhci0: [GIANT-LOCKED]=0A= usb0: on uhci0=0A= usb0: USB revision 1.0=0A= uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1=0A= uhub0: 2 ports with 2 removable, self powered=0A= uhub0: port error, restarting port 1=0A= uhub0: port error, giving up port 1=0A= uhub0: port error, restarting port 2=0A= uhub0: port error, giving up port 2=0A= uhci1: port 0xe000-0xe01f irq 21 at device = 16.1 on pci0=0A= uhci1: [GIANT-LOCKED]=0A= usb1: on uhci1=0A= usb1: USB revision 1.0=0A= uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1=0A= uhub1: 2 ports with 2 removable, self powered=0A= uhub1: port error, restarting port 1=0A= uhub1: port error, giving up port 1=0A= uhub1: port error, restarting port 2=0A= uhub1: port error, giving up port 2=0A= uhci2: port 0xe400-0xe41f irq 21 at device = 16.2 on pci0=0A= uhci2: [GIANT-LOCKED]=0A= usb2: on uhci2=0A= usb2: USB revision 1.0=0A= uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1=0A= uhub2: 2 ports with 2 removable, self powered=0A= uhub2: port error, restarting port 1=0A= uhub2: port error, giving up port 1=0A= uhub2: port error, restarting port 2=0A= uhub2: port error, giving up port 2=0A= pci0: at device 16.4 (no driver attached)=0A= isab0: at device 17.0 on pci0=0A= isa0: on isab0=0A= pci0: at device 17.5 (no driver attached)=0A= fdc0: port = 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0=0A= fdc0: FIFO enabled, 8 bytes threshold=0A= fd0: <1440-KB 3.5" drive> on fdc0 drive 0=0A= sio0 port 0x3f8-0x3ff irq 4 on acpi0=0A= sio0: type 16550A=0A= sio1 port 0x2f8-0x2ff irq 3 on acpi0=0A= sio1: type 16550A=0A= ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0=0A= ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode=0A= ppc0: FIFO with 16/16/9 bytes threshold=0A= ppbus0: on ppc0=0A= lpt0: on ppbus0=0A= lpt0: Interrupt-driven port=0A= atkbdc0: port 0x64,0x60 irq 1 on acpi0=0A= atkbd0: flags 0x1 irq 1 on atkbdc0=0A= kbd0 at atkbd0=0A= atkbd0: [GIANT-LOCKED]=0A= psm0: irq 12 on atkbdc0=0A= psm0: [GIANT-LOCKED]=0A= psm0: model IntelliMouse Explorer, device ID 4=0A= orm0: