Re: new problem?
On Sunday, April 09, 2017 06:08:04 PM Jeffrey Bouquet wrote: > i386_set_ldt: start=-1 num=1 descs=0x38449fac This message is a harmless debug printf. Somehow you compiled sys/i386/i386/sys_machdep.c with 'DEBUG' defined to enable it though. (The message is not enabled by default.) > Tons of those, eight at a time, newly spamming /var/log/messages, maybe after > a > fsck_ffs -y the partitions after a crash, that fixed it, > > as in > df > df output, then eight of the above line with the hex values varying only > ls > ls output, then eight of the above line with the hex values varying only > .. > 2nd problem > persistent LOR in [several] > > nvidia_os:c:662, 824 > > [dmesg only, above, ] > > vfs_mount.c:1277 > ffs_softdep.c:1908 > vfs_subr.c:2600, 2150, > ffs_vnops.c:280 > vfs_bio.c:3500 > ufs_dirhash.c:281 > vfs_syscalls.c:3364 > > [some above also in dmesg, most in /var/log/messages... There are several known LORs in the VFS/UFS code that are either false positives or ones that have effectively been harmless. -- John Baldwin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
new problem?
i386_set_ldt: start=-1 num=1 descs=0x38449fac Tons of those, eight at a time, newly spamming /var/log/messages, maybe after a fsck_ffs -y the partitions after a crash, that fixed it, as in df df output, then eight of the above line with the hex values varying only ls ls output, then eight of the above line with the hex values varying only .. 2nd problem persistent LOR in [several] nvidia_os:c:662, 824 [dmesg only, above, ] vfs_mount.c:1277 ffs_softdep.c:1908 vfs_subr.c:2600, 2150, ffs_vnops.c:280 vfs_bio.c:3500 ufs_dirhash.c:281 vfs_syscalls.c:3364 [some above also in dmesg, most in /var/log/messages... and another one or two I've wrote down but lost, gfvs_* I think. but that line above may be the cause of the i386 line at the top. ? New one to me. Sorry. ! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
new problem with X (was problem with X)
Well... I added the line -fno-merge-constants to CFLAGS in XFree86-4-Server's Makefile. The error 'Symbol from module /usr/X11R6/lib/modules/fonts/libbitmap.a is unresolved' seems fixed. However, now I'm getting the error: XFree86 Version 4.2.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 3 September 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: FreeBSD 5.0-RELEASE i386 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Thu Jan 30 12:44:38 2003 (==) Using config file: /etc/X11/XF86Config Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! /usr/libexec/ld-elf.so.1: /usr/lib/libc_r.so.5: Undefined symbol __thr_jtable waiting for X server to shut down For now I'm re-building each and every XFree86 bit individually (a very time consuming process by the way). If anyone has a suggustion as to what I should try at this point I'd appriate it... Regards, Kirk Kirk R. Wythers email: [EMAIL PROTECTED] University of Minnesota tel: 612.625.2261 Department of Forest Resources fax: 612.625.5212 Saint Paul, MN 55108 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
