From owner-freebsd-questions@FreeBSD.ORG  Tue Nov 12 13:41:24 2013
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 24EDD399
 for <freebsd-questions@freebsd.org>; Tue, 12 Nov 2013 13:41:24 +0000 (UTC)
Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id DF8B12CDF
 for <freebsd-questions@freebsd.org>; Tue, 12 Nov 2013 13:41:23 +0000 (UTC)
Received: from r56.edvax.de (port-92-195-117-74.dynamic.qsc.de [92.195.117.74])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx02.qsc.de (Postfix) with ESMTPS id 625BA27908;
 Tue, 12 Nov 2013 14:41:16 +0100 (CET)
Received: from r56.edvax.de (localhost [127.0.0.1])
 by r56.edvax.de (8.14.5/8.14.5) with SMTP id rACDf4Xd002351;
 Tue, 12 Nov 2013 14:41:04 +0100 (CET)
 (envelope-from freebsd@edvax.de)
Date: Tue, 12 Nov 2013 14:41:04 +0100
From: Polytropon <freebsd@edvax.de>
To: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
Subject: Re: KDE4 crashed, how to recover?
Message-Id: <20131112144104.a1034dd1.freebsd@edvax.de>
In-Reply-To: <1384262588.31259.YahooMailNeo@web161905.mail.bf1.yahoo.com>
References: <1384262588.31259.YahooMailNeo@web161905.mail.bf1.yahoo.com>
Organization: EDVAX
X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: Unga <unga888@yahoo.com>
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.16
Precedence: list
Reply-To: Polytropon <freebsd@edvax.de>
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Nov 2013 13:41:24 -0000

On Tue, 12 Nov 2013 05:23:08 -0800 (PST), Unga wrote:
> [...]
> Computer hanged, had to force power down from the power button.
> 
> After that FreeBSD runs well but when try to start KDE, it prints
> following and immediately reboots:
> 
> Generating KDM configuration.
> panic: Bad effnlink fip 0x..., fdp 0x..., tdp 0x....
> cpuid = 2
> KDB: stack backtrace:
> #0 0x... at kdb_backtrace
> #1 0x... at panic
> #2 0x... at ufs_rename
> #3 0x... at VOP_RENAME_APV
> #4 0x... at kern_renameat
> #5 0x... at kern_rename
> #6 0x... at sys_rename
> #7 0x... at syscall
> #8 0x... at Xint0x80_syscall
> 
> How to recover from this issue?

Make sure your file systems have been successfully repaired.
It's useful to boot into single user mode and perform a fsck
of all partitions _prior_ to continuing the boot process.
Note that a background fsck could still be running while you
try to restart KDE with an underlying inconsistent filesystem.
To intendedly avoid booting into a possibly dirty filesystem
environment, put background_fsck="NO" into /etc/rc.conf, but
note that, depending on the size of your disks, startup time
will probably increase dramatically. :-)

Still it's hard to imagine how a file system defect could cause
that immediate kind of kernel panic...




-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...