Re: Freebsd 11 current testing ndis / kldload: bcmwl564_sys.ko PANIC
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 adr...@freebsd.org wrote: It's actually fpu code in ndis drivers. I'm going to deprecate NDIS this year, so .. OTOH, the FPU save support would be cool. -a On 22 January 2014 20:10, Miguel Clara miguelmcl...@gmail.com wrote: Getting a panic: Unregistered use of FPU in kernel There seems to be a patch for FreeBSD 10, but not sure if it wold apply http://www.freebsd.org/cgi/query-pr.cgi?pr=165622sourceid=opensearch Thanks ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.
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://freebsd.1045724.n5.nabble.com/Lessons-learned-from-source-upgrade-from-FreeBSD-i386-9-2-Stable-to-FreeBSD-i386-10-0-Release-tp5878896p5879039.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.
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. My experiences converting a couple of systems from 9-STABLE to 10-STABLE over the last couple of months were really pretty easy. These were source updates for both base and ports. Despite changing from pkg_* to pkg and KMS X drivers at the same time, it was surprisingly smooth. If you have devel/ccache installed, remove it before starting, though, it has problems with clang. 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. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.
On 23 Jan 2014, at 05:49, Robert Burmeister robert.burmeis...@utoledo.edu 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-stable, which has gcc as the default compiler, and build 10.0 release without any trouble. Can you please explain which problems you encountered with libstdc++? -Dimitry signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.
On Thu, Jan 23, 2014 at 9:56 AM, Warren Block wbl...@wonkity.com 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 clear my /usr/obj before starting a buildworld, which takes 2 hours to run on my system. Are you saying if I do make -DNOCLEAN buildworld I do not have to clear /usr/obj first AND my buildworld will run faster (AND with no downside)? Thanks. -Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
lock order reversals w/ backtrace
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 as debug in nature? If I should report them, how or where do these messages get logged? I can find no reference to them in syslog or anywhere else upon my subsequent reboot. I also had a couple of these messages pop up the other day while mounting/umounting USB thumb drives. I did not think anything of them at the time as the mounts/umounts completed successfully. Please advise. Thanks. -Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.
On Thu, Jan 23, 2014 at 7:47 AM, Thomas Hoffmann trh...@gmail.com wrote: On Thu, Jan 23, 2014 at 9:56 AM, Warren Block wbl...@wonkity.com 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 clear my /usr/obj before starting a buildworld, which takes 2 hours to run on my system. Are you saying if I do make -DNOCLEAN buildworld I do not have to clear /usr/obj first AND my buildworld will run faster (AND with no downside)? Thanks. -Tom I moved to pkg after the upgrade from 9.2 to 10.0 and had no real problems. Of course, I did have to install pkg and run pkg2ng, but I would have had to run those at some point, anyway. Exactly what problems did you hit? -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.
On Thu, 23 Jan 2014, Kevin Oberman wrote: On Thu, Jan 23, 2014 at 7:47 AM, Thomas Hoffmann trh...@gmail.com wrote: On Thu, Jan 23, 2014 at 9:56 AM, Warren Block wbl...@wonkity.com 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 clear my /usr/obj before starting a buildworld, which takes 2 hours to run on my system. Are you saying if I do make -DNOCLEAN buildworld I do not have to clear /usr/obj first Yes. Removing /usr/obj is a faster way of doing 'make clean', mostly. AND my buildworld will run faster Yes, because make will see that many/most files have already been built. (AND with no downside)? Well... mostly. :) I noticed that after 10.0-RELEASE, uname on my system still said PRERELEASE. That code had not been rebuilt because make did not see it as needing a rebuild. You can still delete /usr/obj and run a full buildworld from scratch every so often. I should give credit to bdrewery@ for reminding me about -DNOCLEAN when I was whining about ccache not working on 10.0. It turned out to be a better solution. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
RE: lock order reversals w/ backtrace
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 Hoffmann trh...@gmail.com mailto:trh...@gmail.com Sent: Thursday 23rd January 2014 17:15 To: freebsd-current freebsd-current@freebsd.org mailto:freebsd-current@freebsd.org Subject: lock order reversals w/ backtrace 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 as debug in nature? If I should report them, how or where do these messages get logged? I can find no reference to them in syslog or anywhere else upon my subsequent reboot. I also had a couple of these messages pop up the other day while mounting/umounting USB thumb drives. I did not think anything of them at the time as the mounts/umounts completed successfully. Please advise. Thanks. -Tom ___ freebsd-current@freebsd.org mailto:freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org mailto:freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.
On Thu, Jan 23, 2014 at 11:52 AM, Warren Block wbl...@wonkity.com wrote: On Thu, 23 Jan 2014, Kevin Oberman wrote: On Thu, Jan 23, 2014 at 7:47 AM, Thomas Hoffmann trh...@gmail.com wrote: On Thu, Jan 23, 2014 at 9:56 AM, Warren Block wbl...@wonkity.com 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 clear my /usr/obj before starting a buildworld, which takes 2 hours to run on my system. Are you saying if I do make -DNOCLEAN buildworld I do not have to clear /usr/obj first Yes. Removing /usr/obj is a faster way of doing 'make clean', mostly. AND my buildworld will run faster Yes, because make will see that many/most files have already been built. (AND with no downside)? Well... mostly. :) I noticed that after 10.0-RELEASE, uname on my system still said PRERELEASE. That code had not been rebuilt because make did not see it as needing a rebuild. You can still delete /usr/obj and run a full buildworld from scratch every so often. I should give credit to bdrewery@ for reminding me about -DNOCLEAN when I was whining about ccache not working on 10.0. It turned out to be a better solution. Hmm, I particularly like your suggestion of running a full buildworld periodically. With two hour buildworlds (from scratch) I was planning on rebuilding every couple of weeks. If using -DNOCLEAN can significantly reduce my buildworld time, I'll rebuild weekly and do a full build every fourth week. I'm anxious to give this approach a go and see how much time I can save on the buildworlds. Thanks for the info and tips. -Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Fw: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.
On Thu, Jan 23, 2014 at 2:15 PM, Matthew Rezny matt...@reztek.cz 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 current -- CURRENT became FreeBSD 11.x as of Thu Oct 10 18:05:13 2013 UTC. Feel free to forward on to the list if you feel this is valuable to others. Apparently list owner looked only at the topic, ignore the fact it's a reply several levels deep, and did NOT look at the content. Begin forwarded message: Date: Thu, 23 Jan 2014 18:22:50 +0100 From: Matthew Rezny matt...@reztek.cz To: freebsd-current@freebsd.org Subject: Re: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release. On Thu, Jan 23, 2014 at 9:56 AM, Warren Block wblock at wonkity.com 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 clear my /usr/obj before starting a buildworld, which takes 2 hours to run on my system. Are you saying if I do make -DNOCLEAN buildworld I do not have to clear /usr/obj first AND my buildworld will run faster (AND with no downside)? Thanks. -Tom If you always clear your /usr/obj, you can safely add -DNOCLEAN to the build and it will shave off a minute or two (depending on drive speed) that would have been spent attempting to delete thousands of non- existent files and directories. I've never actually benchmarked, but rm -rf /usr/obj followed by make -DNOCLEAN buildworld should take slightly less time than a regular buildworld (unless perhaps you use a tmpfs backed /usr/obj). Yes, you can safely do a make -DNOCLEAN bulidworld without first clearing out /usr/obj iff conditions are right. If you change anything in src.conf or make.conf, then you must clean. If you switch what branch you are checking out from then you must clean. If you are tracking -STABLE or -CURRENT with regularity (as Warren does) then you can usually get away with not cleaning. If you go too long between updates to your /usr/src then you might have to clean. If there is a disruptive commit, you might have to clean. Sometimes it will be obvious because the buildworld won't complete without error, but sometimes it will finish with apparent success however some binaries will be bad. So, if you get some rather strange behavior shortly after installworld, go clean it and build again. If you are doing your own local development, then you can safely use -DNOCLEAN throughout the process. Only if you make a disruptive change yourself or possibly if you merge changes from svn would you need to clean the build. This is good to know, especially the info on when using -DNOCLEAN might cause problems and how they might manifest themselves. Thanks. -Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: possible selrecord optimization ?
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 used, i noticed the following: I wonder if we could use the same optimization as Linux: as soon as pollscan/selscan detects a non-blocking fd, make selrecord a no-op (which is probably as simple as setting SELTD_RESCAN; and since it only goes up we do not need to lock to check it). Yes, I think this would work fine. I think setting SELTD_RESCAN as a way to do it is fine as well. excellent, thanks. I also have two related questions: 1. why isn't the struct mtx part of the struct selinfo instead of being grabbed from the mtxpool_select ? I think this is because there is no selinfo_init() and no selinfo_destroy(), so there is no way to manage the lifetime of the mutex were it embedded into the structure. Also, if there are a lot of these structures, but only a subset of them are ever accessed, then a smaller set of locks that are hashed onto the structures may work just fine without introducing extra contention (but with the benefit of saving space in the structures). 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 given struct selinfo ? If you mean 'do not need', yes. mtx_pool_find() does a hash on the address, so it will always return the same lock for a given selinfo, and no external locking should be needed by callers. However, callers often need to check other state for which they need to hold a lock anyway. OTOH, if, for example, socket buffer locks were reader/writer locks, sopoll_generic() could use read locks on the socket buffers even while calling selrecord(). In case, any objections if i add some comments to the code to explain the above ? Not from me. :) -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
port hyperic-sigar - marked broken, is anybody fixing this port?
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 anybody working on this problem, that instead of using utmp.h and diddling with the related files directly, one should rely on utmpx.h and its db manipulating functionality. I could give it a try for FreeBSD9, but I'm mostly a noob, be it Java or Java extensions and also for ports. Maybe some kindred soul could fill me in such, that this itch can be scratched. Werner ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Freebsd 11 current testing ndis / kldload: bcmwl564_sys.ko PANIC
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 a bit and it has several fixes which are not present in the base tree. On Thu, Jan 23, 2014 at 11:39 AM, Mike C. miguelmcl...@gmail.com wrote: 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 adr...@freebsd.org wrote: It's actually fpu code in ndis drivers. I'm going to deprecate NDIS this year, so .. OTOH, the FPU save support would be cool. -a On 22 January 2014 20:10, Miguel Clara miguelmcl...@gmail.com wrote: Getting a panic: Unregistered use of FPU in kernel There seems to be a patch for FreeBSD 10, but not sure if it wold apply http://www.freebsd.org/cgi/query-pr.cgi?pr=165622sourceid=opensearch Thanks ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org -- Have a nice day, Vlad Movchan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: possible selrecord optimization ?
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 given struct selinfo ? If you mean 'do not need', yes. mtx_pool_find() does a hash on the address, yes, i meant do not need. thanks luigi ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Freebsd 11 current testing ndis / kldload: bcmwl564_sys.ko PANIC
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 adr...@freebsd.org wrote: It's actually fpu code in ndis drivers. I'm going to deprecate NDIS this year, so .. OTOH, the FPU save support would be cool. -a On 22 January 2014 20:10, Miguel Clara miguelmcl...@gmail.com wrote: Getting a panic: Unregistered use of FPU in kernel There seems to be a patch for FreeBSD 10, but not sure if it wold apply http://www.freebsd.org/cgi/query-pr.cgi?pr=165622sourceid=opensearch Thanks ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Freebsd 11 current testing ndis / kldload: bcmwl564_sys.ko PANIC
*sorry mean there a change -- mean there's a chance On Fri, Jan 24, 2014 at 12:54 AM, Miguel Clara miguelmcl...@gmail.com 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 kldload if_bwn But none of them work for 4313 it seems! :( On Thu, Jan 23, 2014 at 7:21 AM, Adrian Chadd adr...@freebsd.org wrote: It's actually fpu code in ndis drivers. I'm going to deprecate NDIS this year, so .. OTOH, the FPU save support would be cool. -a On 22 January 2014 20:10, Miguel Clara miguelmcl...@gmail.com wrote: Getting a panic: Unregistered use of FPU in kernel There seems to be a patch for FreeBSD 10, but not sure if it wold apply http://www.freebsd.org/cgi/query-pr.cgi?pr=165622sourceid=opensearch Thanks ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Freebsd 11 current testing ndis / kldload: bcmwl564_sys.ko PANIC
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 miguelmcl...@gmail.com 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 kldload if_bwn But none of them work for 4313 it seems! :( On Thu, Jan 23, 2014 at 7:21 AM, Adrian Chadd adr...@freebsd.org wrote: It's actually fpu code in ndis drivers. I'm going to deprecate NDIS this year, so .. OTOH, the FPU save support would be cool. -a On 22 January 2014 20:10, Miguel Clara miguelmcl...@gmail.com wrote: Getting a panic: Unregistered use of FPU in kernel There seems to be a patch for FreeBSD 10, but not sure if it wold apply http://www.freebsd.org/cgi/query-pr.cgi?pr=165622sourceid=opensearch Thanks ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Freebsd 11 current testing ndis / kldload: bcmwl564_sys.ko PANIC
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! thanks for clarifying! On Fri, Jan 24, 2014 at 2:18 AM, Adrian Chadd adr...@freebsd.org wrote: 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 miguelmcl...@gmail.com 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 kldload if_bwn But none of them work for 4313 it seems! :( On Thu, Jan 23, 2014 at 7:21 AM, Adrian Chadd adr...@freebsd.org wrote: It's actually fpu code in ndis drivers. I'm going to deprecate NDIS this year, so .. OTOH, the FPU save support would be cool. -a On 22 January 2014 20:10, Miguel Clara miguelmcl...@gmail.com wrote: Getting a panic: Unregistered use of FPU in kernel There seems to be a patch for FreeBSD 10, but not sure if it wold apply http://www.freebsd.org/cgi/query-pr.cgi?pr=165622sourceid=opensearch Thanks ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
CAM Target Layer (LUN masking)
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 plans to implement any kind of zoning or lun masking? It is very desirable feature for the project I'm working on now. Now I'm surfing isp's sources trying to get its architecture. I'd like to contribute in this filed (development, testing, whatever) if possible. Please let me know if I can help or if someone has beta-versions to try and fix. Thanks Sergey ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
