From owner-freebsd-current@FreeBSD.ORG Thu Aug 28 10:04:07 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB79A16A4BF for ; Thu, 28 Aug 2003 10:04:07 -0700 (PDT) Received: from web11405.mail.yahoo.com (web11405.mail.yahoo.com [216.136.131.235]) by mx1.FreeBSD.org (Postfix) with SMTP id 433C943F93 for ; Thu, 28 Aug 2003 10:04:07 -0700 (PDT) (envelope-from shizukakudo_99@yahoo.com) Message-ID: <20030828170407.75338.qmail@web11405.mail.yahoo.com> Received: from [219.76.96.9] by web11405.mail.yahoo.com via HTTP; Thu, 28 Aug 2003 10:04:07 PDT Date: Thu, 28 Aug 2003 10:04:07 -0700 (PDT) From: Shizuka Kudo To: Shizuka Kudo , freebsd-current@freebsd.org In-Reply-To: <20030828154041.61076.qmail@web11405.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: ATAng panic with large file transfer to HighPoint RAID X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2003 17:04:08 -0000 To further test if this issue was really caused by ATAng, I have cvsupped src/sys/dev/ata, src/sys/conf/files, & src/sys/sys/ata.h back to the time just before ATAng committed. I then built/installed kernel and found that with this non-ATAng kernel, the "pax" command can run successfully on a directory of around 2.2GB. Hope that this additional data would help... Thanks. --- Shizuka Kudo wrote: > I think I have reported this two days ago, but look like it wasn't gone through. Here's my > problem > that I still suffer with build world/kernel about three hours ago (i.e. Aug 28 12:00 UTC) > > With the new world/kernel, I tried to "pax" a subdirectory to the RAID1 drive (two IBM > DLTA-307030 > attached to the two UDMA-100 interface of a HighPoint 370 controller) with the following command > and immediately with a DMA transfer error followed by a kernel panic. > > shizuka# pax -pe -r -w public /raid/ > ad6: FAILURE - oversized DMA transfer attempted 131072 > 65536 > ad6: Setting up DMA failed > ar0: WARNING - mirror lost > ad4: FAILURE - oversized DMA transfer attempted 131072 > 65536 > ad4: Setting up DMA failed > ar0: ERROR - array broken > panic: initiate_write_inodeblock_ufs2: already started > > Here's the backtrace from gdb > > panic: initiate_write_inodeblock_ufs2: already started > panic: from debugger > Uptime: 2m45s > Dumping 511 MB > 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368 384 400 > 416 > > 432 448 464 480 496 > > > --- > Reading symbols from > /usr/obj/usr/src/sys/SHIZUKA/modules/usr/src/sys/modules/acpi/acpi.ko.debug...done. > Loaded symbols for /usr/obj/usr/src/sys/SHIZUKA/modules/usr/src/sys/modules/acpi/acpi.ko.debug > Reading symbols from /boot/kernel/logo_saver.ko...done. > Loaded symbols for /boot/kernel/logo_saver.ko > #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240 > 240 dumping++; > (kgdb) where > #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240 > #1 0xc0254380 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:372 > #2 0xc0254768 in panic () at /usr/src/sys/kern/kern_shutdown.c:550 > #3 0xc014ba82 in db_panic () at /usr/src/sys/ddb/db_command.c:450 > #4 0xc014b9e2 in db_command (last_cmdp=0xc046c120, cmd_table=0x0, > aux_cmd_tablep=0xc0422284, aux_cmd_tablep_end=0xc0422288) > at /usr/src/sys/ddb/db_command.c:346 > #5 0xc014bb25 in db_command_loop () at /usr/src/sys/ddb/db_command.c:472 > #6 0xc014eb45 in db_trap (type=3, code=0) at /usr/src/sys/ddb/db_trap.c:73 > #7 0xc03b5d4c in kdb_trap (type=3, code=0, regs=0xdc39ea3c) > at /usr/src/sys/i386/i386/db_interface.c:171 > #8 0xc03c75aa in trap (frame= > {tf_fs = -831782888, tf_es = 16, tf_ds = 16, tf_edi = 1, tf_esi = -1069454141, tf_ebp = > -600184184, tf_isp = -600184216, tf_ebx = 0, tf_edx = 0, tf_ecx = -1068875680, tf_eax = 18, > tf_trapno = 3, tf_err = 0, tf_eip = -1069850620, tf_cs = 8, tf_eflags = 642, tf_esp = > -1069434333, > tf_ss = -1069505986}) > at /usr/src/sys/i386/i386/trap.c:577 > #9 0xc03b76f8 in calltrap () at {standard input}:102 > #10 0xc02546a5 in panic ( > fmt=0xc0416cc3 "initiate_write_inodeblock_ufs2: already started") > at /usr/src/sys/kern/kern_shutdown.c:534 > #11 0xc035e2e6 in initiate_write_inodeblock_ufs2 (inodedep=0xc42b6800, bp=0x0) > at /usr/src/sys/ufs/ffs/ffs_softdep.c:3893 > ---Type to continue, or q to quit--- > #12 0xc035d46d in softdep_disk_io_initiation (bp=0xce641830) > at /usr/src/sys/ufs/ffs/ffs_softdep.c:3459 > #13 0xc0214954 in spec_xstrategy (vp=0xc41dfdb0, bp=0xce641830) > at /usr/src/sys/sys/buf.h:413 > #14 0xc0214aab in spec_specstrategy (ap=0x0) > at /usr/src/sys/fs/specfs/spec_vnops.c:529 > #15 0xc0213c18 in spec_vnoperate (ap=0x0) > at /usr/src/sys/fs/specfs/spec_vnops.c:122 > #16 0xc029da9b in bwrite (bp=0xce641830) at vnode_if.h:1141 > #17 0xc029ffd9 in vfs_bio_awrite (bp=0xce641830) > at /usr/src/sys/kern/vfs_bio.c:1709 > #18 0xc02a0e16 in flushbufqueues (flushdeps=0) > at /usr/src/sys/kern/vfs_bio.c:2171 > #19 0xc02a097c in buf_daemon () at /usr/src/sys/kern/vfs_bio.c:2072 > #20 0xc023d091 in fork_exit (callout=0xc02a0840 , arg=0x0, > frame=0x0) at /usr/src/sys/kern/kern_fork.c:796 > > > > Is anyone found the same error > > __________________________________ > Do you Yahoo!? > Yahoo! SiteBuilder - Free, easy-to-use web site design software > http://sitebuilder.yahoo.com > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com