Date: Tue, 12 Nov 2013 07:21:13 -0800 (PST) From: Unga <unga888@yahoo.com> To: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: KDE4 crashed, how to recover? Message-ID: <1384269673.7565.YahooMailNeo@web161901.mail.bf1.yahoo.com> In-Reply-To: <20131112144104.a1034dd1.freebsd@edvax.de> References: <1384262588.31259.YahooMailNeo@web161905.mail.bf1.yahoo.com> <20131112144104.a1034dd1.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- > From: Polytropon <freebsd@edvax.de> > To: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> > Cc: Unga <unga888@yahoo.com> > Sent: Tuesday, November 12, 2013 1:41 PM > Subject: Re: KDE4 crashed, how to recover? > > 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... > Hi Polytropon and Julian Thanks for replies. File system dirty was indeed the case. I rebooted with a liveCD and ran fsck with -f, and it solved the problem. Thanks again. Unga
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1384269673.7565.YahooMailNeo>