I have 128+16 memory in my Qube. 128 is in the first slot and 16 is in 
the second. The memory is good as I had no problems with 1.6.2 at all. I 
purchased this memory from a good source. I deal with them all the time 
and they always sold me an excellent memory. I can give a reference if
someone is interested.

I hope this works out for you because for me it is hit and miss.

Regards,
Alex

Daniel Ouellet wrote:
> All servers are running one applications each, but in productions and 
> have a good amount of load.
> 
> Some run qmail, others djbdns, some ftp, some web service, some many 
> perl scripts, some mrtg, one nagio, I even have one running MySQL, but 
> that took for ever to compile it, two days!
> 
> All of them are making it to 3.0, obviously, they are not all there yet 
> for sure. Does take time to do so.
> 
> Are you sure your memory is good? It will panic with bad one.
> 
> But I will make sure to put some under a very good load and report back 
> on the outcome.
> 
> One thing to be said, all my Cobalt are RaQ 2, however. I had issue with 
> one before that only had 16 Mb and crash, but putting only 32Mb took 
> care of it and is not running for well over a year none stop.
> 
> 
> 
> Alex Pelts wrote:
> 
>> I do not have PF or SCSI or RIDFrame. This is the last panic I got:
>>
>> "panic: lockmgr: no context".
>>
>> I am not even sure what was going on as it happened at night. It is 
>> kindof annoying for the box to panic out of the blue. Don't get me 
>> wrong, I am not complaining but IMHO 3.0 is not ready to be a release 
>> at least on the qube.
>>
>> What are you running on your qubes? I am running apache with php and 
>> ssh . That is basically it. I also ftp sometimes in to the qube to 
>> upload pictures and such and download backups. Under 2.1 ftp downloads 
>> caused panic. Under 3.0 http server is causing panic. I am not so sure 
>> what the "lockmgr" is.
>>
>> The load of my server is very light. I have maybe 200 hits on a good 
>> day. Mostly it is idle.
>>
>> Regards,
>> Alex
>>
>>
>> Daniel Ouellet wrote:
>>
>>> So far I can't say I have any issues.
>>>
>>> But again, on all my boxes and for years, I never do any upgrades.
>>>
>>> I always do a clean install and it takes care of any problems I have 
>>> seen otherwise.
>>>
>>> In a few weeks, I can report more success or failures and I will have 
>>> more then about 30 boxes of various ages running 3.0 with PF enable 
>>> in kernel and without the RAIDFrame and SCSI stuff. So far every time 
>>> I took that out, it resulted in increase stability.
>>>
>>> YMMV, but that's from my side and not only one one box, but many of 
>>> them!
>>>
>>> Daniel
>>>
>>> Alex Pelts wrote:
>>>
>>>> I installed 3.0 from the working qube by unpacking, not from restore 
>>>> cd. I have random crashes when http server is accessed by more than 
>>>> 1 client at the same time. Kernel is custom compiled to remove the 
>>>> things that I don't use.
>>>>
>>>> I am thinking of going back to 1.6.2 which was a very stable version 
>>>> at least for me. 2.1 was even less stable than 3.0 and I do not see 
>>>> any benefits as far as performance goes. I will probably wait until 
>>>> 3.0 matures to move my qube to it again.
>>>>
>>>> Regards,
>>>> Alex
>>>>
>>>>
>>>> Claudio Leiva S wrote:
>>>>
>>>>> Hi:
>>>>>
>>>>> Any issue installing 3.0 on a Qube 2, I have the process with the 
>>>>> CD done but when it restart it get stuck on "Starting Up".
>>>>>
>>>>> Any ideas, the specs of my box are.
>>>>>
>>>>> 256 mb
>>>>> 120 Gb hard drive
>>>>>
>>>>> Unfortunatelly I dont have a serial connection with the box..
>>>>>
>>>>>
>>>>>
>>>>> Claudio Leiva S.
>>>>> Las Vegas, Nevada.
>>>>> USA
>>>>> http://cleiva.no-ip.org
>>>>> (Powered by NetBSD for Cobalt)
>>>>>
>>>>>
>>>>> ----- Original Message ----- From: "Daniel Ouellet" 
>>>>> <daniel@presscom.net>
>>>>> To: <port-cobalt@netbsd.org>
>>>>> Sent: Friday, January 06, 2006 12:06 AM
>>>>> Subject: Compile PF in kernel on Cobalt is no go on 3.0
>>>>>
>>>>>
>>>>>> I tried a few times to enable PF and so far, I can't even compile 
>>>>>> the kernel with it enable.
>>>>>>
>>>>>> As far as I can see, only these needs to be commented out:
>>>>>>
>>>>>> pseudo-device   pf                      # PF packet filter
>>>>>> pseudo-device   pflog                   # PF log if
>>>>>>
>>>>>> as by default it is not in the GENERIC kernel.
>>>>>>
>>>>>> I have no problem making any changes to the kernel and get it to 
>>>>>> compile, but this two line to turn it up as far as I can see, 
>>>>>> result in no go.
>>>>>>
>>>>>> I wish I had the error to put here, but as it takes a long time to 
>>>>>> compile, I did it in the background and sing off, so, I didn't see 
>>>>>> the errors the last time, but no matter what variation I do, still 
>>>>>> no go.
>>>>>>
>>>>>> Anyone able to do so yet? Am I forgetting to do something else as 
>>>>>> well.
>>>>>>
>>>>>> Also, in default there isn't a PF device in the /dev, so I use 
>>>>>> makedev to create it, not sure that it is the proper way for this 
>>>>>> one however.
>>>>>>
>>>>>> Any clue to offer?
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>
> 
> 
>