Hi,
Works fine for me with 9.0-p3 with the same controller, slight firmware
differences:
mfi0: 2709 (boot + 4s/0x0020/info) - Firmware version 2.120.244-1482
mfi0: 2710 (boot + 5s/0x0020/info) - Package version 20.10.1-0077
mfi0: 2711 (boot + 5s/0x0020/info) - Board Revision 04A
I will be tryin
Hi all,
Suddenly I am facing a problem on a new PC, using a configuration that I
have been using on more than 10 servers for the last few years. The only
thing that I find that differs from my other configuratinos is the NIC
of the PC. If not, I must be missing something very trivial.
I have
schrieb Pavel Polyakov am 06.03.2012 11:20 (localtime):
>>> mount -t unionfs -o noatime /usr /mnt
>>>
>>> insmntque: mp-safe fs and non-locked vp: 0xfe01d96704f0 is not
>>> exclusive locked but should be
>>> KDB: enter: lock violation
>>
>> Pavel,
>> can you give a spin to this patch?:
>> http
On 8/8/12, Harald Schmalzbauer wrote:
> schrieb Pavel Polyakov am 06.03.2012 11:20 (localtime):
mount -t unionfs -o noatime /usr /mnt
insmntque: mp-safe fs and non-locked vp: 0xfe01d96704f0 is not
exclusive locked but should be
KDB: enter: lock violation
>>>
>>> Pavel
On Wed, Aug 8, 2012 at 10:05 AM, Jan Mikkelsen wrote:
> Hi,
>
> Works fine for me with 9.0-p3 with the same controller, slight firmware
> differences:
>
> mfi0: 2709 (boot + 4s/0x0020/info) - Firmware version 2.120.244-1482
> mfi0: 2710 (boot + 5s/0x0020/info) - Package version 20.10.1-0077
> mfi
Good afternoon friends,
I wanna install zabbix 2.0 on a Freebsd 9 but using ports.
I read about that the ports (1.8.3) would be updated to 2.0
any news? Any one install from source without problems?
tks
___
freebsd-stable@freebsd.org mailing list
htt
Hi,
On 09/08/2012, at 4:18 AM, George Kontostanos wrote:
> On Wed, Aug 8, 2012 at 10:05 AM, Jan Mikkelsen
> wrote:
>> Hi,
>>
>> Works fine for me with 9.0-p3 with the same controller, slight firmware
>> differences:
>>
>> ...
> Hi can you clarify if this was done using gpart and gnop?
>
g
I finally have some time to take a closer look at this issue. Yes, it
is caused by SMI#. DragonflyBSD has tried to fix the similar problem
(see
http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/bb467734fc407e2c2de7f8314c63dd9f708f4df4)
But Windows and Linux don't cause such problem on my ma
On Wed, Aug 08, 2012 at 02:33:25PM +0300, George Mamalakis wrote:
> Hi all,
>
> Suddenly I am facing a problem on a new PC, using a configuration that I
> have been using on more than 10 servers for the last few years. The only
> thing that I find that differs from my other configuratinos is the