Re: System deadlock when using mksnap_ffs
I'll just chime in briefly. I contacted Jeremy off the list about this issue a few days ago. I have one spare box i386 sitting here that I can happily test patches against; if I can be of help, let me know. uname -a FreeBSD localhost.localdomain 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Tue Nov 11 21:40:27 CST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 ident /boot/kernel/kernel | grep sleepqueue $FreeBSD: src/sys/kern/subr_sleepqueue.c,v 1.39.2.5 2008/09/16 20:01:57 jhb Exp $ Suffers from the description given by Jeremy: the box is not deadlocked during snapshot but I might as well walk away from it because I can't use it. I'd really like to see this get fixed; I rely on dump for backups. Regards, Pat -- Jesus, can't I count on you people!? --Oh Brother, Where Art Thou, George Clooney ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.2 nvidia x11 driver: weird 16bpp/24bpp colorspace damage
Update: after some research I've determined natre of this color distortion. It seems like card interpretes each RGB8 value (24 bits, 8 for each color component) as RBG4 (12 bits, 4 bits for each component, red-blue-green order). Thus, color which is 0xFF (red) looks like magenta onscreen (red = 0xF, green = 0x0, blue = 0xF) and so on. Doesn't anyone have any problems with nvidia driver on 6.2-RELEASE? Yes but my problem with the nvidia driver is because the new version in ports no longer supports the card in my laptop (GForce4 440 go). X log says to use the old 96xx version of the driver. Wishful thinking: Too bad there isn't an nvidia-driver-legacy port. PS. Here's related thread on nvidia's forum: http://www.nvnews.net/vbulletin/showthread.php?t=84323 Pat ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
