I saw the exact same error today (just happened to be scanning this mailing list) with
4.1-STABLE after a panic.
Original message from: Matthew Jacob
>> panic: lockmgr: pid 1, not exlusive lock holder 0 unlocking
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current
On Fri, Apr 14, 2000 at 05:21:24PM -0500, Joe Greco wrote:
> While it is fantastic that FreeBSD comes out of the box so fully
> functional, it does make it a bit of a pain for those of us who intend
> to build servers - we have to disable the original before installing a
> new package. :-/
man m
On Wed, Mar 22, 2000 at 12:22:42AM +, Richard Wendland wrote:
> Any views gratefully received. A fix would be much better :-)
Not sure if my meager setup helps any, but in the interests in providing
results to help the cause so-to-speak, I ran the test on my own machine
(followed the instruc
On Sat, Mar 11, 2000 at 04:10:26PM -0500, Ted Sikora wrote:
> My problem is a little different. XFree86-4.0 loads
> fine looks great but the mouse does not work. There
> are no errors. I tried PS/2 , serial, etc same with
> them all. The pointer appears then moves to the upper
> right and dissa
On Fri, Mar 10, 2000 at 06:13:14PM +, [EMAIL PROTECTED] wrote:
> I am currently experiencing problems with the 0307 -CURRENT snapshot, and
> the dc driver. I previously have had no problems with the pn driver I had
[snip]
Yes, I'm using a LinkSys card with -CURRENT:
dc0: port 0xd400-0xd4f
I was just watching a buildworld happen when I noticed (specifically in
gcc, and a few other places) the following warning several times:
warning: mktemp() possibly used unsafely; consider using mkstemp()
I'm not sure if it's a big deal or not, but in the interests of satisfying
my own interests
On Sun, Mar 05, 2000 at 09:09:02PM -0500, Jim Bloom wrote:
> The only minor problem I see is that your game port is detected twice. Other
> than that, the hardware is detected correctly. You have asked for help, but
> what problem(s) are you seeing?
Yeah, I realized that after the fact, thanks
Hi all, hate to post something this insignificant to the mailing list, but
I've search the entire src tree with no luck in resolving this myself
(well, grepping for awe64,wavetable,game .. found the AWE64 define in
/usr/src/sys/dev/sound/isa/sbc.c easily enough) .. I'm sure it's due to
some braind
On Thu, Feb 24, 2000 at 07:48:35PM +0100, Dieter Rothacker wrote:
> No, it is not. It is 100Mbps upstream and 100Mbps downstream. You cannot get
> 200Mbps in one direction. FDX (Full Duplex) simply means that the RX and TX
> cables are used simultaneous. Due to the small ethernet frame size, it is
On Thu, Feb 24, 2000 at 12:04:38PM +0100, Pascal Hofstee wrote:
> media: autoselect (100baseTX )
>
> Downloading an 128 MB-file from the network to /dev/null results in speeds
> like 9.8 MB/s (close to the theoretical maximum for a 100 Mbps network)
The theoretical maximum for 100BaseT-FDX
On Sun, 9 Jan 2000 02:11:49 +0100, you wrote:
>After removing IPFILTER_LKM, I ran the bench again and got following
>results.
What benchmark utility are you using to measure these results with?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of th
11 matches
Mail list logo
