Re: About amd64 dualcore problems with two SATA disks and nforce4

2006-03-12 Thread Daniel Valencia
Hi, Well... Hopeful with your mailings, I updated the kernel (cvsup) and rebuilt it... the problem's still there... detects one SATA disk (ad4) and crashes before acknowledging the second (ad6)... - Daniel S�ren Schmidt <[EMAIL PROTECTED]> wrote: Daniel Valencia wrote: > Hi, > > So, what's

freebsd-hackers@freebsd.org

2006-03-12 Thread prime
Date: Sun, 12 Mar 2006 16:25:07 +0530 > From: "Pranav Peshwe" <[EMAIL PROTECTED]> > Subject: Doubts about PICKUP_GIANT() and mtx_lock(&Giant). > To: freebsd-hackers@freebsd.org > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1 > > Hello, > What is

freebsd-hackers@freebsd.org

2006-03-12 Thread Bernd Walter
On Sun, Mar 12, 2006 at 04:25:07PM +0530, Pranav Peshwe wrote: > Hello, > What is effectively the difference between PICKUP/DROP_GIANT and > mtx_lock/unlock(&Giant) ? From the macro expansion, i surmise that > PICKUP/DROP_GIANT deals with recursion in Giant locking.Is this correct ? is >

freebsd-hackers@freebsd.org

2006-03-12 Thread Pranav Peshwe
Hello, What is effectively the difference between PICKUP/DROP_GIANT and mtx_lock/unlock(&Giant) ? From the macro expansion, i surmise that PICKUP/DROP_GIANT deals with recursion in Giant locking.Is this correct ? is this the only difference ? What will happen if i mix the usage of PICKUP