From owner-freebsd-current@FreeBSD.ORG Sat Nov 6 13:43:23 2004 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 B7DEF16A4CE for ; Sat, 6 Nov 2004 13:43:23 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 172DA43D54 for ; Sat, 6 Nov 2004 13:43:23 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iA6DhKTG002324; Sat, 6 Nov 2004 14:43:20 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Stefan Ehmann From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sat, 06 Nov 2004 13:51:17 +0100." <1099745477.809.4.camel@taxman> Date: Sat, 06 Nov 2004 14:43:20 +0100 Message-ID: <2323.1099748600@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@freebsd.org Subject: Re: ext2fs related panic 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: Sat, 06 Nov 2004 13:43:23 -0000 Ok, then try this patch: Index: ext2_vfsops.c =================================================================== RCS file: /home/ncvs/src/sys/gnu/ext2fs/ext2_vfsops.c,v retrieving revision 1.130 diff -u -r1.130 ext2_vfsops.c --- ext2_vfsops.c 29 Oct 2004 10:42:30 -0000 1.130 +++ ext2_vfsops.c 6 Nov 2004 13:42:52 -0000 @@ -732,6 +732,8 @@ ump->um_mountp = mp; ump->um_dev = dev; ump->um_devvp = devvp; + ump->um_bo = &devvp->v_bufobj; + ump->um_cp = cp; /* setting those two parameters allowed us to use ufs_bmap w/o changse ! */ In message <1099745477.809.4.camel@taxman>, Stefan Ehmann writes: >On Sat, 2004-11-06 at 13:29, Poul-Henning Kamp wrote: >> Can you try this patch ? > >Thanks, now I can access the partition again without any panic. > >But I just noticed a similar panic when unmounting the ext2fs: > >Fatal trap 12: page fault while in kernel mode >current process = 66 (umount) > >trace >g_wither_geom_close() >ext2_unmount() >do_unmount() >unmount() >syscall() >Xint0x80_syscall() > >> In message <1099742312.809.9.camel@taxman>, Stefan Ehmann writes: >> >With kernel sources from yesterday I get a panic as soon as I do this: >> > >> >mount /mnt/stuff >> >ls /mnt/stuff >> > >> >The correspoding line in fstab is this (I haven't checked yet if it also >> >happens on rw mounted ext2fs) >> >/dev/ad1s1 /mnt/stuff ext2fs ro >> > >> >Unfortunately I had problems when debugging the core with kgdb (maybe >> >because it couldn't find symbols for the modules or because I had to >> >call doadump by hand). >> > >> >Anyway, here is a (shortened) transcript from ddb output. >> > >> >Fatal trap 12: page fault while in kernel mode >> >... >> >current process = 815 (ls) >> > >> >trace >> >ext2_strategy() >> >bufstrategy() >> >breadn() >> >bread() >> >ext2_read() >> >ext2_readdir() >> >getdirentries() >> >Xint0x80_syscall() >> > >> >I can provide more info if needed. >> > >> >Thanks >> > >> >_______________________________________________ >> >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" >> > > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.