Lock order reversal
Dear colleagues, === lock order reversal 1st 0xc2f4b128 vm object (vm object) @ vm/vm_object.c:432 2nd 0xc082f110 system map (system map) @ vm/vm_kern.c:325 Stack backtrace: backtrace(c04eacec,c082f110,c04fb2fa,c04fb2fa,c04fb1a2) at backtrace+0x17 witness_lock(c082f110,8,c04fb1a2,145,c082f0b0) at witness_lock+0x692 _mtx_lock_flags(c082f110,0,c04fb199,145,101) at _mtx_lock_flags+0xb1 _vm_map_lock(c082f0b0,c04fb199,145,0,c05b4600) at _vm_map_lock+0x36 kmem_malloc(c082f0b0,1000,101,d258fac4,c044c7df) at kmem_malloc+0x3a page_alloc(c083a1c0,1000,d258fab7,101,c05ae0e0) at page_alloc+0x27 slab_zalloc(c083a1c0,101,8,c04fcb37,664) at slab_zalloc+0x14f uma_zone_slab(c083a1c0,101,c04fcb2e,664,0) at uma_zone_slab+0xcb uma_zalloc_internal(c083a1c0,0,101,6e8,0) at uma_zalloc_internal+0x55 uma_zfree_arg(c268aa80,d1c77e04,0,1,0) at uma_zfree_arg+0x2bf swp_pager_meta_free_all(c2f4b128,c04faaf9,c04faa91,1b2) at swp_pager_meta_free_all+0x18f swap_pager_dealloc(c2f4b128,1,c04fca3d,10c,0) at swap_pager_dealloc+0x113 vm_pager_deallocate(c2f4b128,0,c04fbc2b,25f,1b0) at vm_pager_deallocate+0x3d vm_object_terminate(c2f4b128,0,c04fbc2b,1b0,d258fc14) at vm_object_terminate+0x1e8 vm_object_deallocate(c2f4b128,c2b9bd20,c2f4b128,c2b9bd20,d258fc68) at vm_object_deallocate+0x35f vm_map_entry_delete(c2ab2a00,c2b9bd20,c04fb368,8bc,0) at vm_map_entry_delete+000,0,bfc0,c2ab2a00,c26fc700) at vm_map_delete+0x3d3 vm_map_remove(c2ab2a00,0,bfc0,11d,65) at vm_map_remove+0x55 exit1(c2aa15f0,0,c04e5b6a,65,d258fd40) at exit1+0x60d sys_exit(c2aa15f0,d258fd14,c0500c6f,3fd,1) at sys_exit+0x41 syscall(2f,2f,2f,0,) at syscall+0x251 Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (1), eip = 0x280d159f, esp = 0xbfbff42c, ebp = 0xbfbff448 --- === 5.1-CURRENT from July, 6, 2003. GENERIC kernel. --- Yours Andrew Kolchoogin. [DREW-RIPE, AKOL-RIPN] ... Contrary to popular belief, UNIX is user-friendly. It just happens to be very selective about who it decides to make friends with. A. Haiut. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: About 5.0 and Nvidia drivers
Hi! On Sat, Aug 03, 2002 at 06:38:11PM -0400, Matthew N. Dodd wrote: ugh, sounds like the lip-service I was getting. I'll look into that :/ No, they're working on it, and actually have GL running in the lab. Well, and, as under Linux, there will be an a closed-source library and a kernel module permamently takes kernel to the hell of core dumps? I'm starting to ponder the legality and challenge involved in reverse engineering the card and building a driver from scratch... maybe something that works with X the X way (dri/drm) You're a funny guy. There is another FreeBSD/NVidia Initiative to develop DRI-capable driver for FreeBSD. Did you contact him? You'd be better off working with ATI or the PowerVR people. You want to say me that there is an ATI graphics card that is more powerful than NVidia GeForce? Sorry, but FreeBSD is really good operating system. Good enough for use it on servers. As a system programmer, I wish to have a copy of it on my home desktop. And my son/daughter wish to play games on same desktop. What should I do? Change video cards every day? Whatever? Or use ancient 16-bit NVidia drivers not capable to use even 1152x864x110 Hz? Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Comments on Release Building for -current
David, On Fri, Aug 02, 2002 at 12:39:55AM -0700, David O'Brien wrote: The rest of the GCC using world can use -O2 on their code. We are the only ones that have so much trouble with it. It is probably due to our bugs, not GCC's. sorry, but some time ago I read here that gcc -O2 breaks our printf() in libc. I haven't find any assembler code in /usr/src/lib/libc/stdio/vfprintf.c, as such, if some C compiler can't handle VALID and STANDARDS-COMPLIANT C code, this compiler is broken. Isn't it? Indeed, all of FreeBSD users could help to catch such a bug in gcc optimizer code. :) Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: portmap
Hi! On Tue, Jul 30, 2002 at 09:52:26PM +0200, Radko Keves wrote: i upgrade from 4.5 to 5.0 and portmap haven't found new, and source for portmap haven't found too RPC-to-TCP/UDP port mapper now called 'rpcbind'. i need your help You really should run 'mergemaster' after such an upgrade. Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: where's perl???
Karl, On Thu, Jul 25, 2002 at 11:09:05PM -0700, karl agee wrote: on my box perl is located su-2.05a# whereis perl perl: /usr/bin/perl /usr/share/man/man1/perl.1.gz /usr/src/usr.bin/perl it is a wrapper. Perl now isn't in a base system. I checked various files to see if I could edit anything but there was nothing obvious. Should I make a link to /usr/bin/perl? Say as root use.perl port after installing /usr/ports/lang/perl. Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5.0-DP2 coming up..
Hi! On Wed, Jul 17, 2002 at 07:40:47PM -0400, Garance A Drosihn wrote: Hey all (ab)users of -current. Please try to work on getting -current as stabilized as possible in the next few days and hold off on any large changes until after re@ creates the Perforce branch for DP2 on Friday. Well a working XFree86-4 would be just great to have in DP2 ;) It seems to be working for me, thanks to all the recent work from Eric Anholt [EMAIL PROTECTED]. When I built it (on the 14th) there was still the issue of Wraphelp.c not ending up in the right place, but that is being worked on. And that was trivial enough for me to figure out, that I was up-and-running with it. Yesterday I built XFree86-4-libraries port on my Alpha (-current from July, 15) -- everything is O.K., including xc/lib/Xdmcp, where the Wraphelp.c file is used. Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
freetype2 doesn't build on -current/alpha.
Hi! It's very surprising for me, but /usr/ports/print/freetype2 doesn't build on -current on my Alpha box because GNU make dumps core after signal 11 after GNU configure has finished. Stack trace given by gdb shows the following: (gdb) set heuristic-fence-post 10 (gdb) bt #0 0x120034e8c in getopt () #1 0x16021c5f0 in qsort () from /usr/lib/libc.so.5 #2 0x120034cb0 in getopt () warning: Hit heuristic-fence-post without finding warning: enclosing function for address 0x75e (gdb) GNU make uses it's own version of getopt(), AFAIK, and the last core dump I got even after rebuilding gmake with -mcpu=ev5 -O0. Any suggestions? Return stack is polluted? Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Still no XFree86-4?
John, On Tue, Jul 16, 2002 at 12:04:53PM +0200, John Angelmo wrote: I erased my /usr/ports just to be sure that all the diffrent patches out, then cvsuped to get the latest version, to my disepointment XFree86-4 Still dosn't build under Current, I still got the same perl error in fonts, the perl port is installed. Try to say as root use.perl port. Does anyone have a working patch? It doesn't seem to me that moving perl executable from /usr/bin to /usr/local/bin can affect executing of perl scripts. Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: VOP_GETATTR panic on Alpha
Hi! On Tue, Jul 16, 2002 at 02:45:11PM +0200, Dag-Erling Smorgrav wrote: The following panic is 100% reproducable - it happens whenever I boot a recent kernel on Alpha, just before init(8) starts getty(8) on the console: sorry, kernel from today's sources at 17:38 works just fine. Yet another question about kernel core dumps: what should I do to get one?-) Why panic from debugger on i386 gives core dump and reboots the system and panic from debugger on Alpha does not? Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: VOP_GETATTR panic on Alpha
Hi! On Tue, Jul 16, 2002 at 05:59:16PM +0200, Dag-Erling Smorgrav wrote: sorry, kernel from today's sources at 17:38 works just fine. Try with DEBUG_VFS_LOCKS. Well. Say that me is the lamest programmer at the world. :) My Alpha DOESN'T go to debugger. Instead it hungs in the internals of the kernel. Break on serial console brings me to debugger. Instead of that it doesn't respond neither to the network nor the serial console. Andrew. P.S. Well, I'll try to get kernel core dump and analyse it using debugger. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: VOP_GETATTR panic on Alpha
Andrew, On Tue, Jul 16, 2002 at 01:46:16PM -0400, Andrew Gallatin wrote: PS: I was trying to make crashdumps fail on x86 by increasing HZ. But I cannot. I have no idea why this only happens on alpha. have you any ideas what we should to test?-) Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Bruce, On Thu, Jul 11, 2002 at 08:23:06AM +1000, Bruce Evans wrote: The extra verboseness is fine, and I was almost finished posting a note that mentioned it. But I didn't thinking that the __printf0like bugs will never be fixed if we hide them by patching chmod. It was fixed more than a month ago: sorry, -current from July, 10: === roadstone# cd /usr/src/bin/chmod/ roadstone# ls CVS Makefilechmod.1 chmod.c roadstone# make clean rm -f chmod chmod.o chmod.1.gz chmod.1.cat.gz roadstone# make cc -O -pipe -mcpu=ev5 -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wformat=2 -Wno-format-extra-args -Werror -c /net/storage/FreeBSD/src/bin/chmod/chmod.c cc1: warnings being treated as errors /net/storage/FreeBSD/src/bin/chmod/chmod.c: In function `main': /net/storage/FreeBSD/src/bin/chmod/chmod.c:174: warning: null format string *** Error code 1 Stop in /net/storage/FreeBSD/src/bin/chmod. roadstone# === Road Stone is Alpha AXP EV6 DECChip 21264 machine. The printf0 part always worked on i386's and doesn't seem to have any machine dependencies. I hope you are right. :) Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
