CAM Target Layer (LUN masking)

2014-01-23 Thread Сергей Тарасов
Hi I found that Kenneth D. Merry ken at FreeBSD.org Thu Jan 5 04:51:03 UTC 2012 wrote: Configuring and Running CTL: === . Note that all CTL LUNs are presented to all frontends. There is no LUN masking, or separate, per-port configuration. . Are there any pl

Re: Freebsd 11 current testing ndis / kldload: bcmwl564_sys.ko PANIC

2014-01-23 Thread Miguel Clara
Pity this is not an old laptop... I7 processor sadly a bad wifi card, gave all kinds of problems on Windows to be honest! No point on applying the patch then if it will stop working anyway! I think I might be able to substitute the card with one from another asus, unless BIOS doesn't allow me too!

Re: Freebsd 11 current testing ndis / kldload: bcmwl564_sys.ko PANIC

2014-01-23 Thread Adrian Chadd
Hi, yes. I'm going to deprecate NDIS and yes, this means that people using hardware that doesn't have a driver will have to go without. It sucks, but noone has stepped up to maintain NDIS and it can't work for later NDIS APIs. -a On 23 January 2014 16:54, Miguel Clara wrote: > Hi Adrian, when

Re: Freebsd 11 current testing ndis / kldload: bcmwl564_sys.ko PANIC

2014-01-23 Thread Miguel Clara
*sorry "mean there a change" --> "mean there's a chance" On Fri, Jan 24, 2014 at 12:54 AM, Miguel Clara wrote: > Hi Adrian, when you say "I'm going to deprecate NDIS", does this also > mean there a change to have this driver working without ndis in > freebsd? > > I tried > kldload if_bwi > kldlo

Re: Freebsd 11 current testing ndis / kldload: bcmwl564_sys.ko PANIC

2014-01-23 Thread Miguel Clara
Hi Adrian, when you say "I'm going to deprecate NDIS", does this also mean there a change to have this driver working without ndis in freebsd? I tried kldload if_bwi kldload if_bwn But none of them work for 4313 it seems! :( On Thu, Jan 23, 2014 at 7:21 AM, Adrian Chadd wrote: > It's actually f

Re: possible selrecord optimization ?

2014-01-23 Thread Luigi Rizzo
On Thu, Jan 23, 2014 at 02:52:41PM -0500, John Baldwin wrote: > On Wednesday, January 22, 2014 7:39:48 pm Luigi Rizzo wrote: ... > > 2. am i correct that we do need to protect concurrent invocations > >of selrecord() on the same selinfo because mtx_pool_find() > >return the same mutex for a

Re: Freebsd 11 current testing ndis / kldload: bcmwl564_sys.ko PANIC

2014-01-23 Thread Vlad Movchan
I've just tested second patch from kern/165622 - it still applies clean and runs good on recent current. If after applying this patch you trigger some other kind of panic/problem you might also want to take a look on https://github.com/NDISulator/ndisulator. Ndis module version from github differs

port hyperic-sigar - marked broken, is anybody fixing this port?

2014-01-23 Thread Werner Thie
Hi Java is probably not the first programming language which comes to mind, when working with FreeBSD. But still I sadly had to forgive to deploy OpenKM because it can't start LibreOffice as service due to the fact, that the author used hyperic-sigar for this functionality. My question: Is a

Re: possible selrecord optimization ?

2014-01-23 Thread John Baldwin
On Wednesday, January 22, 2014 7:39:48 pm Luigi Rizzo wrote: > On Wed, Jan 22, 2014 at 02:29:56PM -0500, John Baldwin wrote: > > On Tuesday, January 21, 2014 9:25:27 pm Luigi Rizzo wrote: > > > Looking at how selrecord() / selwakeup() and their Linux counterparts > > > poll_wait() and wake_up() are

Re: Fw: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.

2014-01-23 Thread Thomas Hoffmann
On Thu, Jan 23, 2014 at 2:15 PM, Matthew Rezny wrote: > Forwarded because my attempt to reply on list was rejected by > heavy-handed and oblivious moderation: > > "The freebsd-current mailing list is for issues involving > FreeBSD-CURRENT, not FreeBSD-STABLE. Neither FreeBSD 9.x nor 10.x is > "c

Re: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.

2014-01-23 Thread Thomas Hoffmann
On Thu, Jan 23, 2014 at 11:52 AM, Warren Block wrote: > On Thu, 23 Jan 2014, Kevin Oberman wrote: > > On Thu, Jan 23, 2014 at 7:47 AM, Thomas Hoffmann >> wrote: >> On Thu, Jan 23, 2014 at 9:56 AM, Warren Block >> wrote: >> > >> > >> > Using -DNOCLEAN with an existing /u

RE: lock order reversals w/ backtrace

2014-01-23 Thread Hans Petter Selasky
Hi, Can you see if you can snap some keywords of the backtraces, like usb_xxx usbdx_xxx cam scsi or something like that. Else I believe there are some sysctl options to prevent the final reboot somehow so that you can write down the messages. --HPS -Original message- > From:Thomas Ho

Re: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.

2014-01-23 Thread Warren Block
On Thu, 23 Jan 2014, Kevin Oberman wrote: On Thu, Jan 23, 2014 at 7:47 AM, Thomas Hoffmann wrote: On Thu, Jan 23, 2014 at 9:56 AM, Warren Block wrote: > > > Using -DNOCLEAN with an existing /usr/obj can go even faster than ccache: > less than two minutes for a bu

Re: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.

2014-01-23 Thread Kevin Oberman
On Thu, Jan 23, 2014 at 7:47 AM, Thomas Hoffmann wrote: > On Thu, Jan 23, 2014 at 9:56 AM, Warren Block wrote: > > > > > > Using -DNOCLEAN with an existing /usr/obj can go even faster than ccache: > > less than two minutes for a buildworld on my frequently updated i5/SSD > > system, sometimes le

lock order reversals w/ backtrace

2014-01-23 Thread Thomas Hoffmann
A few days ago I started running 11.0-CURRENT at r260971 for the first time. The last couple of times I shutdown my system I noticed 2 or 3 short "lock order reversal" messages with accompanying backtraces scroll by. Do these messages represent a problem that I should report or can I ignore them a

Re: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.

2014-01-23 Thread Thomas Hoffmann
On Thu, Jan 23, 2014 at 9:56 AM, Warren Block wrote: > > > Using -DNOCLEAN with an existing /usr/obj can go even faster than ccache: > less than two minutes for a buildworld on my frequently updated i5/SSD > system, sometimes less than one minute. Can you elaborate on this, please? I always clea

Re: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.

2014-01-23 Thread Dimitry Andric
On 23 Jan 2014, at 05:49, Robert Burmeister wrote: > Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD > i386 10.0 Release. > > A) > Clang is needed to compile FreeBSD 10 due to use of the updated libstdc++ in > world. Ehrm, no? You should be able to run stock 9-sta

Re: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.

2014-01-23 Thread Warren Block
On Thu, 23 Jan 2014, Jakub Lach wrote: I plan to stay some time on 9.2-STABLE (already pkgng and clangfied) waiting maybe till next release from 10-STABLE tree, however 10-STABLE will be where I will be eventually heading, so notes in this spirit are valuable reminders at least, I appreciate it.

Re: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.

2014-01-23 Thread Jakub Lach
I plan to stay some time on 9.2-STABLE (already pkgng and clangfied) waiting maybe till next release from 10-STABLE tree, however 10-STABLE will be where I will be eventually heading, so notes in this spirit are valuable reminders at least, I appreciate it. -- View this message in context: http

Re: Freebsd 11 current testing ndis / kldload: bcmwl564_sys.ko PANIC

2014-01-23 Thread Mike C.
hum... the driver I need is for broadcom 4313 wireless, It seems the modules available don't work for that one... wonder of they ever will? I would definitely prefer that to using ndis. Adrian Chadd wrote: >It's actually fpu code in ndis drivers. I'm going to deprecate NDIS >this year, so .. >