Re: SATA vs SCSI ...
Artem Kuchin wrote: Marc G. Fournier <[EMAIL PROTECTED]> wrote: For the last 6 month i really think that if you don't need something high-end scsi then you should go for SATA. Fair enough if you don't need high-end yoy shuld go lowend. But read on.. There are test on sites such as Tom's hardware guide and ixbt.com. They show then on sequrncial read there is no difference between scsi and sata. That is a well known fact. It is also a totally useless parameter for server use. Acatuallty, modern hdds use the same mechanics for sata and scsi > versions of them. The brains This is simply not true. There were a couple of drives about 10yrs ago where this was true eg. Quantum Lightning which were available in both IDE and SCSI Todays SCSI drives have _nothing_ in common with SATA/ATA drives. However, when it comes to random read/writesscsi wins because of > command queueing. And faster accesstime and higher rotational speed (lower latency) you simply can't compare a 7200rpm drive to a 15000rpm drive no matter what interface it has. Recently SATA with NCQ became widly available. Test show that some of those SATA disks with NCW ***WIN*** over scsi 320. To use NCQ drive, controller and OS needs to support it, only a few controllers supports NCQ and FreeBSD have no support at all! The test envolve artificialy randomread/write tests as well as > real application benchmarking. I din't rememeber where excatly i saw the tests on those site, but you could search. The tests on tomshardware are windows single user centric, they never test server workloads, their audience are kids who plays games... So, my opinion, workstation never needs SCSI and every server MUST be on mirror or RAID5 and there you should use SATA with NCQ drivers unless, your applicaton is really weird and needs something extremely speedy. Then, however, you could go for RAID 0+1 and get perfomance that SCSI will never get you. Want something cheap with lots of space? SATA Want something that works and is fast? SCSI Using SATA for databases and mailservers is going to give you bad performance. Regards, Martin -- Martin Nilsson, CTO & Founder, Mullet Scandinavia AB, Malmö, SWEDEN E-mail: [EMAIL PROTECTED], Phone: +46-(0)708-606170, Web: www.mullet.se Our business is well engineered servers optimised for FreeBSD & Linux ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ICP Vortex GDT8546RZ vs 3Ware 9500S-4LP ... ?
Hi. On Sun, Jun 26, 2005 at 11:26:55PM -0300, Marc G. Fournier wrote: > Just curious as to if ppl consider one better then the other, or are they > about the same? Both are quite fast, both bring software. We replaced our 3ware controllers since we had what seems a compatibility problem between the controller and out harddisks (Western Digital 74 GB 10krpm Raptors): Occasionally on the 3ware a random disk dropped out of our RAID 10. You had to remove power from the disk(!) first, to get it acknowledged again by the controller and then do a rebuild. This seems to occur only on very high I/O loads and we could not explicitly trigger it. Sometimes it happened twice a week in one machine, sometime it did not happen several weeks on all 5 machines with this setup. We have no problem with the 3ware and other disks. We have no problems with these disks on the ICP Vortex. For the software: 3ware gives you a cli, which is quite handy when it comes to writing a nagios plugin or doing the usual maintenance stuff. The commands are not straight forward in the first view, but it's easy to understand the concept behind. The big pro here is, that you can handle everything even in Shell scripts (you can just call the cli with the right commands, the output is somewhat parseable). There's no generic way for SNMP access, though. ICP comes with a management console (it's a curses interface, it's exactly the same as going into the controller BIOS on boot) and a management daemon. The management console (icpcon) is pretty straight forward, you can get a lot of information (like watching io rates on all the subsystems down to disk level, getting S.M.A.R.T. info and so on). This interface is not usable in a batch (like getting a status for a nagios plugin or so), you can write out an info file, which is hardly machine parseable. You have the daemon (srcd) to do the monitoring. The daemon can be connected by management consoles (so you don't need to logon the host to monitor or write the info file from), it can send SNMP traps and it can start commands in case of events. It cannot be queried by SNMP. We're very comfortable with the ICPs now, but exchanging the slightly cheaper 3wares was mainly done because of the drive problems mentioned before. - Oliver -- | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA vs SCSI ...
Hi! > As an result: If you need to have FAST disk subsystem - buy SCSI. If you need > large storage or you don't want to pay to much money - buy SATA. Seconded. SATA offers larger capacity per buck. If price/performance is important, I'd seriously consider the ICP SATA cards. Another note: if you need the fastest disk subsystem you can buy, don't even think about implementing RAID5. Go for 1+0 instead. And buy an ICP card ;-) Another big plus for SCSI: unattended "auto" hot plug. If you have a RAID1+0 with 6 disks and without a hot spare (as we do - we needed "fast" and "as much as we can cram in the box") and if your hot plug backplane ist "SAFE-TE" compliant (another one of those beloved standards), then the cleaning staff could change a broken disk drive. The ICP card will automatically start the necessary rebuild if you exchange a broken disk with a factory new one. This could be important if you need 24x7 and don't have a qualified operator on site all the time. No need to start the RAID config utility. HTH, Patrick M. Hausen Leiter Netzwerke und Sicherheit -- punkt.de GmbH Internet - Dienstleistungen - Beratung Vorholzstr. 25Tel. 0721 9109 -0 Fax: -100 76137 Karlsruhe http://punkt.de ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA vs SCSI ...
Marc G. Fournier <[EMAIL PROTECTED]> wrote: looking at the specs between two cards, the SATA card(s) seem to rate ~100-150MB/s on each channel (if I'm reading right), with both the 3Ware and ICP cards having 4 individual channels ... looking at the SCSI cards, they are rated at 320MB/s, but that is total for the SCSI bus itself, right? So, if I have three drives on a SCSI bus, each 'maxing out evenly', I'd be cap'd at about the same 100MB/s per drive, no? In fact, looking at the SATA 2.x specs, each chanell there is rated at 300MB/s, which, again, if I could 'max out evenly', could seriously blow away the SCSI bus itself ... *If* I'm reading this right ... ? For the last 6 month i really think that if you don't need something high-end scsi then you should go for SATA. There are test on sites such as Tom's hardware guide and ixbt.com. They show then on sequrncial read there is no difference between scsi and sata. Acatuallty, modern hdds use the same mechanics for sata and scsi versions of them. The brains (electronics) on the hdds are different of course. However, when it comes to random read/writes scsi wins because of command queueing. This was an issue until recently, Recently SATA with NCQ became widly available. Test show that some of those SATA disks with NCW ***WIN*** over scsi 320. The test envolve artificialy random read/write tests as well as real application benchmarking. I din't rememeber where excatly i saw the tests on those site, but you could search. So, my opinion, workstation never needs SCSI and every server MUST be on mirror or RAID5 and there you should use SATA with NCQ drivers unless, your applicaton is really weird and needs something extremely speedy. Then, however, you could go for RAID 0+1 and get perfomance that SCSI will never get you. -- Regards, Artem Kuchin IT Legion Ltd. Moscow, Russia www.itlegion.ru [EMAIL PROTECTED] +7 095 232-0338 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD -STABLE servers repeatedly crashing.
Hello all, About three weeks ago, I upgraded my 5.3-RELEASE boxes to 5.4-RELEASE. I also turned on procmail globally on our mail server. Here is our current FreeBSD server setup: URANUS - primary ldap CALIBAN - secondary ldap ORION - primary mail Orion was the first one to crash, about three weeks ago. Orion is constantly talking to uranus, because uranus is our primary ldap server (we have a planet scheme), and caliban is our secondary ldap server. I ran an email flood test on orion to see if I could crash it again. This time, the high requests on Uranus caused Uranus to crash. With two different servers on two different hardware setups crashing, I had to start thinking of what could be causing the problem. Memory tests on both servers came back OK. Orion had some ECC errors which it was able to fix. I wasn't able to catch orion's first crash, but I was able to catch uranus's first crash: http://paste.atopia.net/126 I have the other crashes written down in pencil at my work. They all say mostly the same thing. I assume Caliban would also experience this behavior, but because it does not receive much load at all (only does anything when uranus dies), I am not able to confirm this. The only thing similar between the boxes is that all three have two processors in them, and are running SMP. Orion had hyperthreading turned on but I disabled this in the bios, to no avail. Someone with similar experiences running SMP informed to upgrade to -STABLE as of last week. For almost a week, Orion ran fine. This evening; however, Orion once again crashed, its fourth time in three weeks. Uranus has been stable for a few days but I am expecting it to crash again any day now (they usually take between 4-6 days). So now I am stuck. I have two -STABLE machines which continue to cause kernel traps. Tomorrow, I am going to compile a debugging kernel on orion and try to let it crash again to see what kind of errors it reports, but I was wondering if anyone else is experiencing these problems. Thanks in advance, Matt Juszczak ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA vs SCSI ...
One other point worth mentioning is that on SATA all transactions are host generated, while with SCSI devices any device can start a transaction. Transactions can be interleaved better resulting in a higher average throughput. On Mon, 27 Jun 2005 01:19 pm, [EMAIL PROTECTED] wrote: > On Sun, Jun 26, 2005 at 11:34:22PM -0300, Marc G. Fournier wrote: > > looking at the specs between two cards, the SATA card(s) seem to rate > > ~100-150MB/s on each channel (if I'm reading right), with both the 3Ware > > and ICP cards having 4 individual channels ... looking at the SCSI cards, > > they are rated at 320MB/s, but that is total for the SCSI bus itself, > > right? > > It is dependant of the card too. You can get a 3 channel Ultra320 card for > 3 drive RAID 5... > > > So, if I have three drives on a SCSI bus, each 'maxing out evenly', I'd > > be cap'd at about the same 100MB/s per drive, no? > > > > In fact, looking at the SATA 2.x specs, each chanell there is rated at > > 300MB/s, which, again, if I could 'max out evenly', could seriously blow > > away the SCSI bus itself ... > > That is a theory... > > > *If* I'm reading this right ... ? > > And now from my practice: > > 1) You CAN'T get maximal throuput from 150/160 MB/s bus - the is no such > drives today at the market. > > 2) Avg. seek and access time of 7200 SATA drives are FAR BELOW such of old > Seagate Cheetah/Maxtor Athlas 10K. So is a situation with a WD Raptor 10K > SATA too - they are SLOWER! (I'm not shure why, but from my test: > > 2xPIII-1.4/1G RAM/2x36G Cheeta 10K in RAID 1 (AMR Express; One U160 > channel) ws. > 2xXeon 3.0/2G RAM/2x72G Raptor in RAID 1 (Intel SRCS16; Separate SATA-150 > channel for each drive) > > Ports three checkout is about 20% faster on the first comp. > > As an result: If you need to have FAST disk subsystem - buy SCSI. If you > need large storage or you don't want to pay to much money - buy SATA. > > Best Ragards, > > Serg N. Voronkov, > Sibitex JSC. > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- --- Brett Wildermoth BEng(ME) MPhil Lecturer / PhD Student School of Microelectronic Engineering Faculty of Engineering and Info. Tech. Ph. +61 7 3875 5063, Fax. +61 7 3875 5384 Email. [EMAIL PROTECTED] --- pgpTEhplqe4Gs.pgp Description: PGP signature
Re: SATA vs SCSI ...
On Sun, Jun 26, 2005 at 11:34:22PM -0300, Marc G. Fournier wrote: > > looking at the specs between two cards, the SATA card(s) seem to rate > ~100-150MB/s on each channel (if I'm reading right), with both the 3Ware > and ICP cards having 4 individual channels ... looking at the SCSI cards, > they are rated at 320MB/s, but that is total for the SCSI bus itself, > right? It is dependant of the card too. You can get a 3 channel Ultra320 card for 3 drive RAID 5... > So, if I have three drives on a SCSI bus, each 'maxing out evenly', I'd > be cap'd at about the same 100MB/s per drive, no? > > In fact, looking at the SATA 2.x specs, each chanell there is rated at > 300MB/s, which, again, if I could 'max out evenly', could seriously blow > away the SCSI bus itself ... That is a theory... > *If* I'm reading this right ... ? And now from my practice: 1) You CAN'T get maximal throuput from 150/160 MB/s bus - the is no such drives today at the market. 2) Avg. seek and access time of 7200 SATA drives are FAR BELOW such of old Seagate Cheetah/Maxtor Athlas 10K. So is a situation with a WD Raptor 10K SATA too - they are SLOWER! (I'm not shure why, but from my test: 2xPIII-1.4/1G RAM/2x36G Cheeta 10K in RAID 1 (AMR Express; One U160 channel) ws. 2xXeon 3.0/2G RAM/2x72G Raptor in RAID 1 (Intel SRCS16; Separate SATA-150 channel for each drive) Ports three checkout is about 20% faster on the first comp. As an result: If you need to have FAST disk subsystem - buy SCSI. If you need large storage or you don't want to pay to much money - buy SATA. Best Ragards, Serg N. Voronkov, Sibitex JSC. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA vs SCSI ...
On Jun 26, 2005, at 22:34, Marc G. Fournier wrote: In fact, looking at the SATA 2.x specs, each chanell there is rated at 300MB/s, which, again, if I could 'max out evenly', could seriously blow away the SCSI bus itself ... *If* I'm reading this right ... ? Bus speed does not equal drive speed. And while yes, SATA is now approaching SCSI in bus speed, it doesn't mean that SCSI isn't standing still. A 640 MB/s bus was standardized in 2003 (though SATA is planned to go to 600MB/s in 2007): http://en.wikipedia.org/wiki/SCSI#Ultra-640 This has been hashed out many times over the years in comp.periph.scsi (it used to be IDE versus SCSI, not it's (S)ATA versus SCSI). A search through the archives would probably return many results. The SCSI FAQ [1] would also probably be useful. Specifically the questions: QUESTION: What are the pros and cons regarding SCSI vs IDE/ATA ? http://home.comcast.net/~SCSIguy/SCSI_FAQ/scsifaq.html#_Hlk407004722 QUESTION:Should I spend the extra money on SCSI or just get IDE? http://home.comcast.net/~SCSIguy/SCSI_FAQ/scsifaq.html#_Hlk407091459 QUESTION:Why do SCSI disks cost so much more than IDE/ATA disks? http://home.comcast.net/~SCSIguy/SCSI_FAQ/scsifaq.html#_SCSI_Cost002 [1] http://www.scsifaq.org/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
SATA vs SCSI ...
looking at the specs between two cards, the SATA card(s) seem to rate ~100-150MB/s on each channel (if I'm reading right), with both the 3Ware and ICP cards having 4 individual channels ... looking at the SCSI cards, they are rated at 320MB/s, but that is total for the SCSI bus itself, right? So, if I have three drives on a SCSI bus, each 'maxing out evenly', I'd be cap'd at about the same 100MB/s per drive, no? In fact, looking at the SATA 2.x specs, each chanell there is rated at 300MB/s, which, again, if I could 'max out evenly', could seriously blow away the SCSI bus itself ... *If* I'm reading this right ... ? Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ICP Vortex GDT8546RZ vs 3Ware 9500S-4LP ... ?
Just curious as to if ppl consider one better then the other, or are they about the same? Thanks ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup from 4.11-RELEASE to 4.11-RELEASE-p1 28,000 errors
>- Original Message - >From: Andreas Rudisch <[EMAIL PROTECTED]> >Sent: Saturday, June 25, 2005 2:49 AM >Subject: Re: cvsup from 4.11-RELEASE to 4.11-RELEASE-p1 28,000 errors > > security-supfile: > > #cvsupfile for 5.4-security > *default host=cvsup.no.FreeBSD.org > *default base=/var/db > *default prefix=/usr > *default release=cvs tag=RELENG_5_4 > *default delete use-rel-suffix > *default compress > src-all > >If you really want to get FreeBSD 4.11-p1, then adding the date was correct. >*default date=2005.03.28.15.57.00 (with RELENG_4_11 of course). I thought the '-p1' would have the least number of changes to test cvsup. Changed my 'base' and 'prefix' to match your cvs-supfile, thanks. Using a fresh 4.11 installed all, running the following cvs-supfile still gets 28988 "C " entries in the checkouts.cvs:RELENG_4_11 file. # cvsup -g -L 2 cvs-supfile-src # *default host=cvsup9.us.FreeBSD.org *default base=/var/cvsup *default prefix=/usr/local/etc/cvsup *default release=cvs tag=RELENG_4_11 *default date=2005.03.28.15.57.00 *default delete use-rel-suffix *default compress src-all ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portinstall .vs. make install clean
On 6/27/05, Dominic Marks <[EMAIL PROTECTED]> wrote: > On Sunday 26 June 2005 19:32, Sergey Spivak wrote: > > Hi! > > > > > portinstall is a ruby program which comes with portupgrade > > > > "portinstall" = "portupgrade -N" > > Oh. Makes me wonder why 'portinstall' exists at all. > > -- > Dominic It is a bit more intuitive than "portupgrade -N" IMO. Jiawei Ye -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: EHCI: mtools stuck in state 'physrd' or panic
Hi, Ian Dowse, 26.06.05, 18:42h CEST: > OpenBSD have a workaround for problems with VIA EHCI controllers > that can cause the hanging symptoms you describe. Below is a patch > that implements their change in FreeBSD's driver. Could you try it > to see if it helps? I just tried, but unfortunately it didn't help. I have exactly the same symptoms with the patch applied. Thanks anyway, Stefan pgpdEwMgsAYdh.pgp Description: PGP signature
Re: portinstall .vs. make install clean
On Sunday 26 June 2005 19:32, Sergey Spivak wrote: > Hi! > > > portinstall is a ruby program which comes with portupgrade > > "portinstall" = "portupgrade -N" Oh. Makes me wonder why 'portinstall' exists at all. -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portinstall .vs. make install clean
Hi! > > portinstall is a ruby program which comes with portupgrade > "portinstall" = "portupgrade -N" -- wbr, sergey v. spivak sergey#spivak.kiev.ua zlob-uanic/eunic/ripe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: auto cvsup
Maher Mohamed wrote: how can i upgrade my cvsup weekly with an auto way? You should use crondaemon. Place the following line to the end of /etc/crontab: 15 4 * * 6 rootcvsup /some/path/to/supfile The number six represents the sixth day of the week, the 15 is the minute number and the second is the hour, thus this will run on every Friday (if I remember correctly, I'm not sure the numbering starts with Sunday) at 4:15. Cheers, Gábor Kövesdán ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portinstall .vs. make install clean
On Sunday 26 June 2005 19:12, Maher Mohamed wrote: > can some tell me what is the difference bitween portinstall and make > install clean, and in which way should one portupgrade its ports? portinstall is a ruby program which comes with portupgrade which you can use to build and install ports. It can do some things which you can't do with a simple 'make install'. For example, I often use portinstall to create packages for a port and its dependancies. See the portupgrade manual page for details about how to use it. You should also look at /usr/local/etc/pkgtools.conf for how to set more advanced configurations for your system. > thnk you in advanced -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: auto cvsup
just add this line to your /etc/crontab 0 0 * * 5 root/usr/local/bin/cvsup -g -L 0 /usr/share/examples/cvsup/your_Cvsupfile this will run every friday midnight and update your files. Maher Mohamed wrote: how can i upgrade my cvsup weekly with an auto way? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: auto cvsup
On Sun, Jun 26, 2005 at 09:17:50PM +0300, Maher Mohamed wrote.. > how can i upgrade my cvsup weekly with an auto way? cron? -- Wilko Bulte [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: auto cvsup
Hi! > > how can i upgrade my cvsup weekly with an auto way? > cron it. -- wbr, sergey v. spivak sergey#spivak.kiev.ua zlob-uanic/eunic/ripe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: auto cvsup
Hi Maher, Sunday, June 26, 2005, 8:17:50 PM, you typed: > how can i upgrade my cvsup weekly with an auto way? use cron -- Best regards DanGer, ICQ: 261701668 | e-mail protecting at: http://www.2pu.net/ http://danger.rulez.sk | proxy list at:http://www.proxy-web.com/ | FreeBSD - The Power to Serve! [ I am being followed by a pair of boxer shorts. ] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portinstall .vs. make install clean
portinstall and portupgrade are scripts to do 'make install clean' in an easy way :) Maher Mohamed wrote: can some tell me what is the difference bitween portinstall and make install clean, and in which way should one portupgrade its ports? thnk you in advanced ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: index.php
If you run apache just add index.php to DirectoryIndex directive at the httpd.conf and it should work fine. example: DirectoryIndex index.html index.wml index.cgi index.shtml index.jsp index.js index.jp index.php4 index.php3 index.php index.phtml index.htm default.htm default.html home.htm you can have any file name for example maher.php too and it will load as the first page. Best Regards, Maher Mohamed wrote: how can i make my server link to be redirected to the index.php i hve a web page at http://150.140.210.79:2005/~mahmoh the thing is that if i make the index.html to index.php the whenever i go to the url above i have to add the extra /index.php can i get rid of that? is there a way? -- Mohamed M. Maher ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: index.php
Maher Mohamed wrote: how can i make my server link to be redirected to the index.php i hve a web page at http://150.140.210.79:2005/~mahmoh the thing is that if i make the index.html to index.php the whenever i go to the url above i have to add the extra /index.php can i get rid of that? is there a way? -- Mohamed M. Maher ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" You should modify your DirectoryIndex line in httpd.conf in such way: DirectoryIndex index.html index.html.var index.php index.phtml According to that, the webserver firstly looks for index.html, if it doesn't exist, then for index.html.var... The index.php is the third in this example, but You can use a different order. Cheers, Gábor Kövesdán ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: index.php
Maher Mohamed wrote: how can i make my server link to be redirected to the index.php i hve a web page at http://150.140.210.79:2005/~mahmoh the thing is that if i make the index.html to index.php the whenever i go to the url above i have to add the extra /index.php can i get rid of that? is there a way? -- Mohamed M. Maher ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" this goes into the ~public_html/index.php file to the home folder of the user mahmoh. Owe Jørgensen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: index.php
Hi! Offtopic. :-\ > i hve a web page at http://150.140.210.79:2005/~mahmoh > the thing is that if i make the index.html to index.php the > whenever i go to the url above. i have to add the extra /index.php > can i get rid of that? is there a way? add "index.php" to DirectoryIndex directive in apache config. -- wbr, sergey v. spivak sergey#spivak.kiev.ua zlob-uanic/eunic/ripe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
auto cvsup
how can i upgrade my cvsup weekly with an auto way? -- Mohamed M. Maher ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
index.php
how can i make my server link to be redirected to the index.php i hve a web page at http://150.140.210.79:2005/~mahmoh the thing is that if i make the index.html to index.php the whenever i go to the url above i have to add the extra /index.php can i get rid of that? is there a way? -- Mohamed M. Maher ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
portinstall .vs. make install clean
can some tell me what is the difference bitween portinstall and make install clean, and in which way should one portupgrade its ports? thnk you in advanced -- Mohamed M. Maher ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: EHCI: mtools stuck in state 'physrd' or panic
In message <[EMAIL PROTECTED]>, Stefan Walter write
s:
>FYI: I have just sent a PR for this problem.
>
>http://www.freebsd.org/cgi/query-pr.cgi?pr=82660
OpenBSD have a workaround for problems with VIA EHCI controllers
that can cause the hanging symptoms you describe. Below is a patch
that implements their change in FreeBSD's driver. Could you try it
to see if it helps?
Thanks,
Ian
Index: sys/dev/usb/ehci.c
===
RCS file: /dump/FreeBSD-CVS/src/sys/dev/usb/ehci.c,v
retrieving revision 1.14.2.9
diff -u -r1.14.2.9 ehci.c
--- sys/dev/usb/ehci.c 31 Mar 2005 19:47:11 - 1.14.2.9
+++ sys/dev/usb/ehci.c 26 Jun 2005 16:21:11 -
@@ -155,6 +155,7 @@
Static voidehci_idone(struct ehci_xfer *);
Static voidehci_timeout(void *);
Static voidehci_timeout_task(void *);
+Static voidehci_intrlist_timeout(void *);
Static usbd_status ehci_allocm(struct usbd_bus *, usb_dma_t *, u_int32_t);
Static voidehci_freem(struct usbd_bus *, usb_dma_t *);
@@ -491,6 +492,7 @@
EOWRITE4(sc, EHCI_ASYNCLISTADDR, sqh->physaddr | EHCI_LINK_QH);
usb_callout_init(sc->sc_tmo_pcd);
+ usb_callout_init(sc->sc_tmo_intrlist);
lockinit(&sc->sc_doorbell_lock, PZERO, "ehcidb", 0, 0);
@@ -694,6 +696,11 @@
ehci_check_intr(sc, ex);
}
+ /* Schedule a callout to catch any dropped transactions. */
+ if ((sc->sc_flags & EHCI_SCFLG_LOSTINTRBUG) &&
+ !LIST_EMPTY(&sc->sc_intrhead))
+ usb_callout(sc->sc_tmo_intrlist, hz, ehci_intrlist_timeout, sc);
+
#ifdef USB_USE_SOFTINTR
if (sc->sc_softwake) {
sc->sc_softwake = 0;
@@ -942,6 +949,7 @@
EOWRITE4(sc, EHCI_USBINTR, sc->sc_eintrs);
EOWRITE4(sc, EHCI_USBCMD, 0);
EOWRITE4(sc, EHCI_USBCMD, EHCI_CMD_HCRESET);
+ usb_uncallout(sc->sc_tmo_intrlist, ehci_intrlist_timeout, sc);
usb_uncallout(sc->sc_tmo_pcd, ehci_pcd_enable, sc);
#if defined(__NetBSD__) || defined(__OpenBSD__)
@@ -2701,6 +2708,30 @@
splx(s);
}
+
+/*
+ * Some EHCI chips from VIA seem to trigger interrupts before writing back the
+ * qTD status, or miss signalling occasionally under heavy load. If the host
+ * machine is too fast, we we can miss transaction completion - when we scan
+ * the active list the transaction still seems to be active. This generally
+ * exhibits itself as a umass stall that never recovers.
+ *
+ * We work around this behaviour by setting up this callback after any softintr
+ * that completes with transactions still pending, giving us another chance to
+ * check for completion after the writeback has taken place.
+ */
+void
+ehci_intrlist_timeout(void *arg)
+{
+ ehci_softc_t *sc = arg;
+ int s = splusb();
+
+ DPRINTFN(3, ("ehci_intrlist_timeout\n"));
+ usb_schedsoftintr(&sc->sc_bus);
+
+ splx(s);
+}
+
//
Static usbd_status
Index: sys/dev/usb/ehci_pci.c
===
RCS file: /dump/FreeBSD-CVS/src/sys/dev/usb/ehci_pci.c,v
retrieving revision 1.14.2.2
diff -u -r1.14.2.2 ehci_pci.c
--- sys/dev/usb/ehci_pci.c 13 Jun 2005 09:00:19 - 1.14.2.2
+++ sys/dev/usb/ehci_pci.c 26 Jun 2005 16:21:11 -
@@ -303,6 +303,10 @@
return ENXIO;
}
+ /* Enable workaround for dropped interrupts as required */
+ if (pci_get_vendor(self) == PCI_EHCI_VENDORID_VIA)
+ sc->sc_flags |= EHCI_SCFLG_LOSTINTRBUG;
+
/*
* Find companion controllers. According to the spec they always
* have lower function numbers so they should be enumerated already.
Index: sys/dev/usb/ehcivar.h
===
RCS file: /dump/FreeBSD-CVS/src/sys/dev/usb/ehcivar.h,v
retrieving revision 1.4.2.4
diff -u -r1.4.2.4 ehcivar.h
--- sys/dev/usb/ehcivar.h 22 Mar 2005 00:56:54 - 1.4.2.4
+++ sys/dev/usb/ehcivar.h 26 Jun 2005 16:21:11 -
@@ -93,6 +93,7 @@
#define EHCI_COMPANION_MAX 8
#define EHCI_SCFLG_DONEINIT0x0001 /* ehci_init() has been called. */
+#define EHCI_SCFLG_LOSTINTRBUG 0x0002 /* workaround for VIA chipsets */
typedef struct ehci_softc {
struct usbd_bus sc_bus; /* base device */
@@ -149,6 +150,7 @@
struct lock sc_doorbell_lock;
usb_callout_t sc_tmo_pcd;
+ usb_callout_t sc_tmo_intrlist;
device_ptr_t sc_child; /* /dev/usb# device */
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: syslogd: Logging subprocess ... exited with status 126
On Sun, 2005-06-26 at 12:16 +0300, Nikolay Pavlov wrote: > On Sunday, 26 June 2005 at 9:20:54 +0100, David Malone wrote: > > On Sun, Jun 26, 2005 at 11:05:17AM +0300, Nikolay Pavlov wrote: > > > local3.info | /var/run/nmd.log > > > > > syslogd: Logging subprocess s 1358 ( /var/run/nmd.log) exited with status > > > 126. > > > > If you say "| /var/run/nmd.log" it means "run the program > > /var/run/nmd.log and feed the log messages to stdin of that program". > > I'm guessing that /var/run/nmd.log is a logfile and not a program, > > thus you're getting an error because it is not executable. > Thanks, David for fast response. > It's not a simple log file, but FIFO and I thought that this should working. Nope, a FIFO is still not an executable. If you can't just list the FIFO as a file, maybe try "| cat >/var/run/nmd.log" ? Alternately, you should do away with the FIFO entirely and invoke the program that you currently have on the read end of the FIFO in syslog.conf. -- brandon s. allbery [linux,solaris,freebsd,perl] [EMAIL PROTECTED] system administrator [WAY too many hats][EMAIL PROTECTED] electrical and computer engineering, carnegie mellon univ. KF8NH ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ATA_INTERRUPT error (5-stable)
Hi folks, i`ve today upgraded my PC to board ABIT IS7-E2 with intel 865PE chipset.I`ve IBM 120GXP drive. If i tried to boot my freebsd 5-stable (from 18.6.2005), i got (after IPF initialization): ATA_INTERRUPT was seen but timeout fired out with LBA=0. This message appears infinetly. Bios in the mobo is newest since buy(so no reflashing by me). Sometimes freebsd boots correctly (don`t know what it will cause - it`s unpredictible), but then after let`s say 5 minutes freezes (no kbd && mouse response). Any ideas about how to get it boot correctly?! tnx, Jan Sebosik ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Portupgrade in Xfree86 pkg failed
On Sunday, 26. June 2005 01:18, Ted Mittelstaedt wrote: > If there was significant "product differentiation" between xfree86 and > xorg, then there would be a reason to keep both. Right now there is > not and with the difficulty in X development, there won't soon be. There's already quite a delta on the video driver level. > Here's the litmus test - would you pull a popular port if it breaks on 4 > but not on 5? 'nuff said. What does that prove? It wouldn't get pulled if it would break the other way around either, but be marked BROKEN for the appropriate branch. > The FreeBSD project agrees with me, if they did not then they would > have rewritten the installer to make it optional which one to pick. If it were possible to run software from binary packages built against Xorg on XFree86 (or vice-versa) hassle-free, that would be an option. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpe7lpvWQDSc.pgp Description: PGP signature
Re: dmesg queries
> > > > kernel: Interrupt storm detected on "irq19: uhci0 uhci2"; > > throttling interrupt source > > kernel: Interrupt storm detected on "irq18: bge0 uhci1+"; > > throttling interrupt source > > I get this as well. I don't use USB so I turned that off at the BIOS > and removed it from my kernel, but I still get "interrupt storm" on > my bge0 device. No idea why. I had a similar problem on an itx board, enabling DEVICE_POLLING fixed it. I found on this system around 8-10% of CPU time - when idle was used for interrupts alone without this change. That was achieved without disabling USB, which I also need. > Performance is not all that great on this box disk-wise, but CPU wise > it is acceptably fast. I run FreeBSD/amd64 on it rather than > FreeBSD/ i386. > > > Vivek Khera, Ph.D. > +1-301-869-4449 x806 -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buffalo WLI-PCI-G54
On Friday 24 June 2005 03:13, Balgansuren.B wrote: > Hello, > > I have driver disk for the Windows 98/Me/2000/XP of the Buffalo > WLI-PCI-G54 wireless NIC. > > If possible I want to know "ndiscvt" command convert Windows driver > to FreeBSD driver module. > These two links explain what you need to do. http://caia.swin.edu.au/reports/041221A/ http://www.FreeBSD.org/cgi/man.cgi?ndiscvt > Thanks, > Balgaa > HTH, -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: EHCI: mtools stuck in state 'physrd' or panic
FYI: I have just sent a PR for this problem. http://www.freebsd.org/cgi/query-pr.cgi?pr=82660 Stefan -- No reading beyond this point pgpnIhmnGEEx6.pgp Description: PGP signature
Re: syslogd: Logging subprocess ... exited with status 126
> It's not a simple log file, but FIFO and I thought that this should working. > If I misunderstood something is there any chance to send syslog output to FIFO > file or pipe, because the query-log from named that I'm going to handle is > very extensive. If I remember correctly, to send data to a FIFO, you can specify the FIFO as a regular file in /etc/syslogd.conf. However, you will have to be careful to make sure that there is a program reading the FIFO at all times, if you are to avoid syslogd getting confused. Instead of using a named FIFO, you can directly run your log handling program by using the pipe in syslogd.conf, so if your program to handle messages is in /usr/local/libexec/log_crunch.pl you can then use the "| /usr/local/libexec/log_crunch.pl" in syslogd.conf. David. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: syslogd: Logging subprocess ... exited with status 126
On Sunday, 26 June 2005 at 9:20:54 +0100, David Malone wrote: > On Sun, Jun 26, 2005 at 11:05:17AM +0300, Nikolay Pavlov wrote: > > local3.info | /var/run/nmd.log > > > syslogd: Logging subprocess s 1358 ( /var/run/nmd.log) exited with status > > 126. > > If you say "| /var/run/nmd.log" it means "run the program > /var/run/nmd.log and feed the log messages to stdin of that program". > I'm guessing that /var/run/nmd.log is a logfile and not a program, > thus you're getting an error because it is not executable. > > David. Thanks, David for fast response. It's not a simple log file, but FIFO and I thought that this should working. If I misunderstood something is there any chance to send syslog output to FIFO file or pipe, because the query-log from named that I'm going to handle is very extensive. Best regards, Nikolay Pavlov. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: syslogd: Logging subprocess ... exited with status 126
On Sun, Jun 26, 2005 at 11:05:17AM +0300, Nikolay Pavlov wrote: > local3.info | /var/run/nmd.log > syslogd: Logging subprocess s 1358 ( /var/run/nmd.log) exited with status 126. If you say "| /var/run/nmd.log" it means "run the program /var/run/nmd.log and feed the log messages to stdin of that program". I'm guessing that /var/run/nmd.log is a logfile and not a program, thus you're getting an error because it is not executable. David. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dmesg queries
On Sat, 25 Jun 2005 01:39 am, Chris Phillips wrote: > Hi All, > > ... > Finally, is it considered "bad form", to ask multiple > questions like I have, or should I have separated them & sent > them in multiple emails? I don't know about "bad form"; but human nature being what it is many potential respondents won't reply unless they can answer all. So you reduce your chances of obtaining what you want! Malcolm ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Strange SCSI behavior after upgrading from 5.2.1 to 5.4 (and a panic)
Hello, on Thurday we upgraded one of our last 5.2.1 servers to 5.4. Tonight the server panicked, crashed and I had to power it off and on. Here are the logs before the panic: Jun 26 03:45:50 patroklos kernel: (da0:ahc0:0:0:0): lost device Jun 26 03:45:50 patroklos kernel: (da0:ahc0:0:0:0): Invalidating pack Jun 26 03:46:00 patroklos last message repeated 2 times Jun 26 03:46:06 patroklos kernel: initiate_write_filepage: already started Jun 26 03:46:07 patroklos last message repeated 9 times Jun 26 03:46:07 patroklos kernel: (da0:ahc0:0:0:0): READ(10). CDB: 28 0 72 f 16 0 0 0 80 0 Jun 26 03:46:07 patroklos kernel: (da0:ahc0:0:0:0): CAM Status: SCSI Status Error Jun 26 03:46:07 patroklos kernel: (da0:ahc0:0:0:0): SCSI Status: Check Condition Jun 26 03:46:07 patroklos kernel: (da0:ahc0:0:0:0): UNIT ATTENTION asc:29,0 Jun 26 03:46:07 patroklos kernel: (da0:ahc0:0:0:0): Power on, reset, or bus device reset occurred Jun 26 03:46:07 patroklos kernel: (da0:ahc0:0:0:0): Retries Exhausted Jun 26 03:46:07 patroklos kernel: (da0:ahc0:0:0:0): Invalidating pack Jun 26 03:46:31 patroklos kernel: initiate_write_filepage: already started Jun 26 03:46:43 patroklos kernel: panic: initiate_write_inodeblock_ufs2: already started As I said the machine could not recover from the panic so there ais no crashdump. The 5.4 version of the dmesg output is available at: http://noc.ntua.gr/~christia/tmp/dmesg-5.4.txt The 5.2.1 version of the dmesg output is available at: http://noc.ntua.gr/~christia/tmp/dmesg-5.2.1.txt da0 is an 1302GB external IDE to SCSI RAID (8x200GB IDE drives in RAID5 configuration and a SCSI U160 interface). FreeBSD 5.4 connects to da0 at 80MB/s (40.000MHz, offset 31, 16bit, Tagged Queueing Enabled), while FreeBSD 2.5.1 (and FreeBSD 5.3 - just tried to boot with the 5.3-RELEASE-i386-miniinst.iso) connects happily at 160MB/s (80.000MHz, offset 62, 16bit, Tagged Queueing Enabled) which is the transfer rate supported by the RAID device and the SCSI card (Adaptec 3960D Ultra160 SCSI adapter/aic7899). Any ideas what could be or where could be the problem? What has changed in 5.4? We had preserved the 5.2.1 system disks and after the crash we moved back to 5.2.1 until further notice. Now I'm thinking of trying 5.3 which seems to have the same behavior as 5.2.1 and will be still supported for a year or so. Thanks, Panagiotis ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
syslogd: Logging subprocess ... exited with status 126
Hi, all.
I have an error when try to use pipes with syslog to log queries
from bind. There is a very simple configuration:
/etc/namedb/named.conf:
===CUT===
logging {
channel query_log {
syslog local3;
severity info;
print-category yes;
print-time yes;
};
category queries { query_log; };
};
===CUT===
# mkfifo /var/run/nmd.log
/etc/syslog.conf:
===CUT===
local3.info | /var/run/nmd.log
===CUT===
After that I just dig something:
dig @localhost google.com
And get this errors:
syslogd: Logging subprocess s 1358 ( /var/run/nmd.log) exited with status 126.
et cetera
When i use file instead of pipe it's logging just fine.
Best regards,
Nikolay Pavlov.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.4-STABLE #4 VMWare crash
Hello, I try to start vmware from an user Account, new Version is compiled and i followed the Instructions in pkg-message. ACPI is disabled. When i run vmware i see the following via serial Line: linux(1677): sendsig(0x8083bdc, 11, 0xc1f63834, 30) linux(1676): real select returns 0 linux(1676): outgoing timeout (0/0) linux(1676): select_out -> 0 linux(1676): select(8, 0xbfbfe928, 0xbfbfe8a8, 0, 0xbfbfe89c) linux(1676): incoming timeout (1/0) linux(1678): stat64(/tmp/.vmware/user/1676, *) linux(1677): rt_sigprocmask(2, 0x81ed1ec, 0, 8) linux(1678): open(/dev/null, 0x10800, 0xbfbfaab4) linux(1678): open returns error 0 linux(1677): open(/dev/vmmon, 0x2, 0x0) kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode fault virtual address = 0x6c fault code = supervisor read, page not present instruction pointer = 0x8:0xc0651ab5 stack pointer = 0x10:0xd895e934 frame pointer = 0x10:0xd895e938 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 3 current process = 1677 (vmware-ui) [thread pid 1677 tid 100135 ] Stopped at turnstile_setowner+0xd: movl0x6c(%ecx),%eax db> db> tr Tracing pid 1677 tid 100135 td 0xc1f63780 turnstile_setowner(c1f60800,0) at turnstile_setowner+0xd turnstile_wait(c1f60800,c1fea128,0) at turnstile_wait+0xb7 _mtx_lock_sleep(c1fea128,c1f63780,0,c203a603,18f) at _mtx_lock_sleep+0xad _mtx_lock_flags(c1fea128,0,c203a603,18f,c1ef9c7c) at _mtx_lock_flags+0x30 vmmon_clone(c1fcd100,3,c2169900,c1f63780,c2169944) at vmmon_clone+0x90 FreeBSD_Driver_Open(c1fcd100,3,2000,c1f63780,c203b020) at FreeBSD_Driver_Open+0x79 spec_open(d895ea58,d895eb14,c0694fd9,d895ea58,180) at spec_open+0x226 spec_vnoperate(d895ea58) at spec_vnoperate+0x13 vn_open_cred(d895ebbc,d895ecbc,0,c2203a80,8) at vn_open_cred+0x419 vn_open(d895ebbc,d895ecbc,0,8,0) at vn_open+0x1e kern_open(c1f63780,c1a6d400,1,3,0) at kern_open+0xe7 linux_open(c1f63780,d895ed04,3,12cf,3246) at linux_open+0x10d syscall(2f,2f,2f,81a7648,8199688) at syscall+0x2ab Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (5, Linux ELF, linux_open), eip = 0x284865a8, esp = 0xbfbfeb90, ebp = 0xbfbfebac --- db> Changes from the GENERIC KERNCONF are: options IPFIREWALL options IPFIREWALL_DEFAULT_TO_ACCEPT options IPDIVERT options DUMMYNET options IPFILTER options IPFILTER_LOG options IPSTEALTH options PERFMON options NETGRAPH options NETGRAPH_ETHER
