Re: Unable to boot after upgrade to 7.0 or 7.1 STABLE
Thanks Phillip, > 1) you can have a boot hint in file /boot/loader.conf to say where the > system should take the root file system (and therefore /etc/fstab) from. This would work if the OS was able to detect the disk. In this case, after I boot the STABLE installation, i do not see any hard drive detected. With this entry, I dont think it would boot since FreeBSD cannot see the disk. I will give it a try and get back to you. -- Mike Of course, you might discount this possibility, but remember that one in a million chances happen 99% of the time. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Unable to boot after upgrade to 7.0 or 7.1 STABLE
Hi Wes, > Have you checked the jumper settings on the drive? There may be a jumper > forcing SATA150 mode on the drive. I'd reset everything to factory defaults > if possible. > It's the first thing I did and I did it for the sake of doing it since this is a brand new computer straight out of HP. The drive is in factory defaults. I have done all the basics; BIOS upgrade, drive settings, BIOS settings. > You might be able to use the ata driver from 7.0-R in -stable to boot your > system. If that works, try searching for the commit that breaks your > controller. > hmmm I did not want to go down this track... I was not sure what else i would break if I did this. -- Mike Of course, you might discount this possibility, but remember that one in a million chances happen 99% of the time. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Unable to boot after upgrade to 7.0 or 7.1 STABLE
On Thu, 29 Jan 2009, Mike Barnard wrote: Hi All, I have run into a problem that seem rather puzzling. I have upgraded an installation of FreeBSD from 7.0-RELEASE to 7.0-STABLE and 7.1-STABLE, but i fail to boot with either one of the STABLE upgrades. I end up at this point: Trying to mount root from ufs:/dev/ad0s1a Manual root filesystem specification: : Mount using filesystem eg. ufs:da0s1a ? List valid disk boot devices Abort manual input When i type ?, i get nothing. When i try to load all possible drives, from ad0s1a to ad9s1a, i get nothing. When i boot kernel.old, i see this: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfa00-0xfa0f mem 0xfdffe000-0xfdffe3ff at device 31.2 on pci0 ... ad0: 152627MB at ata0-master SATA150 It seems that FreeBSD recognises this drive as a SATA300 but later on refers to it as SATA150. Could this be the problem. Have you checked the jumper settings on the drive? There may be a jumper forcing SATA150 mode on the drive. I'd reset everything to factory defaults if possible. You might be able to use the ata driver from 7.0-R in -stable to boot your system. If that works, try searching for the commit that breaks your controller. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 7.1, mpt and slow writes
On Thu, Jan 29, 2009 at 11:43:11PM -0500, Charles Sprickman wrote: [ snip ] > Any idea what happened to the sysctl? Is there some other method to > verify the loader tunable took (other than testing the throughput)? Boot with -v. If the loader tunable took effect, you should see "Enabling SATA WC on phy " instead of "Disabling SATA ..." Regards, Gary ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 7.1, mpt and slow writes
On Thu, 29 Jan 2009, Richard Tector wrote: Charles Sprickman wrote: Hello, I think this needs a few more eyes: http://lists.freebsd.org/pipermail/freebsd-scsi/2009-January/003782.html In short, writes are slow, likely do to the write-cache being enabled on the controller. The sysctl used in 6.x to turn the cache off don't seem to be in 7.x. I have two Dell 860's here also running 7.1-REL. A simple dd on one shows roughly 60MB/s writes to a mirror of 2 320GB disks on what I'm assuming is the same LSI controller card (SAS5) rich...@moses:~# cat /boot/loader.conf hw.mpt.enable_sata_wc=1 Seems to work just fine for me. Well, now I'm puzzled. A "sysctl -a" shows no "hw.mpt." tree at all: # sysctl -a|grep hw.mpt # It's a poor test, but: # dd if=/dev/zero of=/jails/foo count=1M 1048576+0 records in 1048576+0 records out 536870912 bytes transferred in 144.830977 secs (3706879 bytes/sec) # dd if=/jails/foo of=/dev/null 1048576+0 records in 1048576+0 records out 536870912 bytes transferred in 4.136582 secs (129786112 bytes/sec) I added the tunable to loader.conf: $ cat /boot/loader.conf hw.mpt.enable_sata_wc=1 And still nothing in the sysctl output (there was on 6.4 on this same hardware, FWIW): $ sysctl -a |grep hw.mpt $ However, performance did improve: # dd if=/dev/zero of=/jails/foo count=16M 16777216+0 records in 16777216+0 records out 8589934592 bytes transferred in 276.332753 secs (31085474 bytes/sec) Any idea what happened to the sysctl? Is there some other method to verify the loader tunable took (other than testing the throughput)? I assume there's still no management tools for these controllers, right? Thanks, Charles Regards, Richard ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Replace Cisco IOS/CBOS with freebsd - possible?
Hello Bruce, and thank you for your reply. Quoting "Bruce M. Simpson" : SDH Support wrote: Seconded for Pfsense -- although I doubt the Cisco hardware would be compatible with FreeBSD, and even if it is , I wouldn't want to use it in a production environment without thorough testing. If someone can provide more detailed hardware specs, including the chipsets and processor details of the cisco hardware , im sure we could realistically evaluate the feasibility. Please see: https://bsdforge.net/cisco-data/ for a list of manuals I have available for download on these (and similar). I'm very, very happy with pfSense. It's a case of the folk behind it having followed an software appliance-style model and that's what makes it stable. I know Peter Grehan was looking at getting FreeBSD onto the Cisco 827 a while back. That's good news. I'll have to see if I can get more info on that. I just purchased a "lot" of cisco *DSL/routers on ebay, in an effort to push this project forward (I can experiment on these with less concern). So my list of HW now includes: * 3 - 802's * 2 - 1604's * 1 - 1721 * 2 - 837's Thank you again for your input. --Chris The PowerPC port has gone some way towards this, but I don't see folk installing it on old Cisco hardware yet... unless the knowledge gets out there. cheers BMS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Replace Cisco IOS/CBOS with freebsd - possible?
Hello, and thank you for your reply. Quoting Oliver Pinter : http://m0n0.ch/wall/ ? Good candidate. Thanks for mentioning it. On the up side - it's FreeBSD based. :) I guess my only disappointments would be that configuration is done by way of PHP. But of course I could fix that. Doesn't provide swap space - this seems like this could be a real liability under heavy load/outside abuse, even with a decent amount of RAM/Memory. Thanks again for the reply. --Chris On 1/29/09, Chris H wrote: Greetings, I'm RP for a fairly large chunk of IP real estate. I carved out a /27 segment for my home network. Which is currently running over a cisco 837 GW (adsl/router). I'm not really keen on it (the router/modem). So I thought to myself that it couldn't be /that/ hard to build a box with FBSD that could replace it - am I crazy? Wouldn't it be possible to upload a minimal build of FBSD to the modem, not unlike one would tftp a new version of cisco's IOS, or CBOS? I searched the projects area to see if anyone had tried it. But the only thing that came anywhere near was netperf. But the only similarity is that it is network related. Anyway, this seems quite feasable as far as I can tell. So I thought I'd ask in hopes someone might enlighten me further. Maybe someones already tried it? Thank you for all your time and consideration in this matter. --Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
RE: Replace Cisco IOS/CBOS with freebsd - possible?
Hello, and thank you for your reply. Quoting SDH Support : Pfsense sounds like exactly what you're looking for. It's a stripped down freeBSD with a fancy web interface (well, not too fancy, it's been incredibly stable for me). I've deployed it a couple times in pseudo production environments and it's been holding up well for the last 1.5years+. Seconded for Pfsense -- although I doubt the Cisco hardware would be compatible with FreeBSD, and even if it is , I wouldn't want to use it in a production environment without thorough testing. If someone can provide more detailed hardware specs, including the chipsets and processor details of the cisco hardware , im sure we could realistically evaluate the feasibility. Good call. I should have known better than to not provide that info. Here is all the data I have on these: https://bsdforge.net/cisco-data/ There are several to choose from. :) Thank you again for taking the time to respond - and for the thoughtful reminder to provide more information. ;) --Chris --- Kevin Systems Administrator www.stardothosting.com/linux-vps-hosting ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Replace Cisco IOS/CBOS with freebsd - possible?
Hello, and thank you for your reply. Quoting Chris Peterson : Pfsense sounds like exactly what you're looking for. It's a stripped down freeBSD Don't get me wrong, I think pfSense goes a long way to my intended goal - not the least of which, is pfDNS. I haven't written it off by any means. with a fancy web interface (well, not too fancy, To be honest - the first thing I'd do, is strip the (any) GUI stuff out. I have no issue with opening a terminal shell via cu - tip(1). In fact, for security reasons, I'd prefer to insure that the only access available is over a serial port (local). Not to mention the size/space savings gains. :) it's been incredibly stable for me). I've deployed it a couple times in pseudo production environments and it's been holding up well for the last 1.5years+. You can also check out http://www.netgate.com/product_info.php?cPath=60_84&products_id=492 for a nice PIX-sized chasis for pfsense if you need a small box. Looks intriguing. The only real advantage I see here, would be the amount of ram available. The 837 I propose to use, only supports 64Mb. Thanks again for your infoamative response. --Chris On Jan 29, 2009, at 6:02 AM, Chris H wrote: Hello, and thank you for your reply. Quoting Michael Grant : On Thu, Jan 29, 2009 at 2:15 PM, Chris H wrote: Hello, and thank you for your reply. While it's not /exactly/ what I was looking for - it's close. :) The "filtering" capability is my biggest gripe on the Cisco *DSL products. They're just not as /capable/ as is offered in FBSD. DNS is another plus (pfDNS). But I don't think I'd be modify pfDNS to accomodate BIND, or unbound. Although tinydns might be able to fit the bill. Oh well, it's close - thanks for the pointer. :) You can run iptables on openwrt. Actually, I was thinking more along the lines of pf(4). I think it's more efficient - especially combined with all the network tuning that has been done recently by Robert Watson, John Baldwin, Mohan Srinivasan, Peter Wemm, and others. Another reason I'm so inclined to be FBSD centric on this. :) You can compile most anything for it, you're only limited by it's memory and cpu. I'm not familiar with pfDNS. But if it runs on freebsd, it probably can be made to run on openwrt as well. Indeed, it's running a FreeBSD base. But like you said; CPU, and Memory are the only boundries here. Will need to do more research to compare limits against a /desired/ install base. Thanks again for the reply. --Chris Michael ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org " ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: NFS writes calling FSYNC and ASYNC not consistent
Apologies for being terse, in a hurry here. 1) -o async doesn't work with NFS, don't use that. 2) how big are the text versus binary files? 3) how are you copying them over nfs? I suspect, (could be wrong of course) that the ascii files are a lot smaller than the binary files, so what's happening is that for binary files, the client is issuing write-behind async, however for ascii files its issuing the writes at close time which will force the sync flag. -Alfred * Brent Jones [090128 19:38] wrote: > Hello FreeBSD users, > I am running into some performance problems with NFSv3/v4 mounts. > I have a Sun X4540 running OpenSolaris 2008.11 with ZFS exporting NFS shares > The NFS clients are a FreeBSD 6.3 32 bit, quad core xeon with 4GB ram > and a FreeBSD 7.1 32bit with same hardware. > > The issue I am seeing, is that for certain file types, the FreeBSD NFS > client will either issue an ASYNC write, or an FSYNC. > However, NFSv3 and v4 both support "safe" ASYNC writes in the TCP > versions of the protocol, so that should be the default. > Issuing FSYNC's for every compete block transmitted adds substantial > overhead and slows everything down. > > The two test files I have that can reproduce this data are a file > created by 'dump' which is just binary data: > > $ file testbinery > testbinery: data > > ASCII text file from a Maildir format: > > $ file ascittest > ascittest: ASCII mail text > > My NFS mount command lines I have tried to get all data to ASYNC write: > > $ mount_nfs -3T -o async 192.168.0.19:/pdxfilu01/obsmtp /mnt/obsmtp/ > $ mount_nfs -3T 192.168.0.19:/pdxfilu01/obsmtp /mnt/obsmtp/ > $ mount_nfs -4TL 192.168.0.19:/pdxfilu01/obsmtp /mnt/obsmtp/ > > Here is an excerpt from a snoop from the binary data file: > > $ snoop rpc nfs > > obsmtp02.local -> pdxfilu01NFS C ACCESS3 FH=57D3 > (read,lookup,modify,extend,delete,execute) >pdxfilu01 -> obsmtp02.local NFS R ACCESS3 OK (read,modify,extend) > obsmtp02.local -> pdxfilu01NFS C LOOKUP3 FH=BB85 testbinery >pdxfilu01 -> obsmtp02.local NFS R LOOKUP3 OK FH=57D3 > obsmtp02.local -> pdxfilu01NFS C ACCESS3 FH=57D3 > (read,lookup,modify,extend,delete,execute) >pdxfilu01 -> obsmtp02.local NFS R ACCESS3 OK (read,modify,extend) > obsmtp02.local -> pdxfilu01NFS C SETATTR3 FH=57D3 >pdxfilu01 -> obsmtp02.local NFS R SETATTR3 OK > obsmtp02.local -> pdxfilu01NFS C WRITE3 FH=57D3 at 0 for 32768 (ASYNC) >pdxfilu01 -> obsmtp02.local NFS R WRITE3 OK 32768 (ASYNC) > obsmtp02.local -> pdxfilu01NFS C WRITE3 FH=57D3 at 582647808 for > 32768 (ASYNC) >pdxfilu01 -> obsmtp02.local NFS R WRITE3 OK 32768 (ASYNC) > obsmtp02.local -> pdxfilu01NFS C WRITE3 FH=57D3 at 592871424 for > 32768 (ASYNC) >pdxfilu01 -> obsmtp02.local NFS R WRITE3 OK 32768 (ASYNC) > obsmtp02.local -> pdxfilu01NFS C WRITE3 FH=57D3 at 605421568 for > 32768 (ASYNC) >pdxfilu01 -> obsmtp02.local NFS R WRITE3 OK 32768 (ASYNC) > > > And on and on.. it will acheive near full wire-speed, about 110MB/sec > during the copy > > > Here is the same snoop, only copying the ASCII mail file: > > $ snoop rpc nfs > >obsmtp02.local -> pdxfilu01NFS C LOOKUP3 FH=BB85 ascittest >pdxfilu01 -> obsmtp02.local NFS R LOOKUP3 No such file or directory > obsmtp02.local -> pdxfilu01NFS C LOOKUP3 FH=BB85 ascittest >pdxfilu01 -> obsmtp02.local NFS R LOOKUP3 No such file or directory > obsmtp02.local -> pdxfilu01NFS C CREATE3 FH=BB85 (UNCHECKED) ascittest >pdxfilu01 -> obsmtp02.local NFS R CREATE3 OK FH=69D3 > obsmtp02.local -> pdxfilu01NFS C WRITE3 FH=69D3 at 0 for 32768 (FSYNC) >pdxfilu01 -> obsmtp02.local NFS R WRITE3 OK 32768 (FSYNC) > obsmtp02.local -> pdxfilu01NFS C WRITE3 FH=69D3 at 32768 for 32768 (FSYNC) >pdxfilu01 -> obsmtp02.local NFS R WRITE3 OK 32768 (FSYNC) > obsmtp02.local -> pdxfilu01NFS C WRITE3 FH=69D3 at 65536 for 32768 (FSYNC) >pdxfilu01 -> obsmtp02.local NFS R WRITE3 OK 32768 (FSYNC) > > > And so on. I've reproduced this with several files, and the only > difference between tests is the file type. > Is the FreeBSD NFS client requesting FSYNC or ASYNC depending on the > file type/contents? > If so, is there a tuneable setting to make all write ASYNC? > Otherwise, FSYNC'ing for every block written over NFS will cause so > many IOPS on the NFS server, that performance will degrade severely. > > Testing with an OpenSolaris 2008.11 client will issue ASYNC writes for > any file type, if mounted with NFSv3 of NFSv4 (TCP). > > Any ideas? > > Thanks in advance! > > -- > Brent Jones > br...@servuhome.net > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" -- - Alfred Perlstein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable
Re: Big problems with 7.1 locking up :-(
On Fri, 9 Jan 2009, Pete French wrote: I have a number of HP 1U servers, all of which were running 7.0 perfectly happily. I have been testing 7.1 in it's various incarnations for the last couple of months on our test server and it has performed perfectly. So the last two days I have been round upgrading all our servers, knowing that I had run the system stably on identical hardware for some time. For those following this other than Pete, who I've been in private correspondence with: it seems that he is running into two different deadlocks in the routing code. One of them (at least) is triggered by a lock order problem relating to the processing of ICMP redirects -- uncommon in most configurations, but quite a few on his network, which triggers quickly under load. Kip Macy has corrected at least one (both?) problems in head, and plans to MFC the fixes in the near future. We'll follow up further once the fixes are merged, and if any further problems transpire. Robert N M Watson Computer Laboratory University of Cambridge Since then I have starte seeing machines lock up. This always happens under heavy disc load. When I bring the machine back up then sometimes it fails to fsck due to a partialy truncated inode. The locksup appear to be disc related - on my mysql msater machine it will come back up with files somewhat shorted than those which ahve aready been transmitted to the slave (i.e. some data was in memory, and claimed to have been written to the drive, but never made it onto the disc). The only time I have seen anything useful on the screen was during one lockup where I got a message about a spin lock being held too long and some comment in parentheses about it being a turnstile lock. Help! :-( I am now downgrading all the machine to 7.0 as fast as I can - though the machine I am trying to compile it on has locked up once during the compile so I havent got anywhere so far. The machines are HP Proliant DL360 G5s - they have an embedded P400i RAID controller with a pair of mirrored drives connected. Each one has both ethernets connected, bundled using lagg and LACP. Advice ? -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Replace Cisco IOS/CBOS with freebsd - possible?
SDH Support wrote: Seconded for Pfsense -- although I doubt the Cisco hardware would be compatible with FreeBSD, and even if it is , I wouldn't want to use it in a production environment without thorough testing. If someone can provide more detailed hardware specs, including the chipsets and processor details of the cisco hardware , im sure we could realistically evaluate the feasibility. I'm very, very happy with pfSense. It's a case of the folk behind it having followed an software appliance-style model and that's what makes it stable. I know Peter Grehan was looking at getting FreeBSD onto the Cisco 827 a while back. The PowerPC port has gone some way towards this, but I don't see folk installing it on old Cisco hardware yet... unless the knowledge gets out there. cheers BMS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Unhappy Xorg upgrade
On Thu, 2009-01-29 at 16:45 -0500, Stephen Clark wrote: > Dan Allen wrote: > > Thanks to Robert for pointing out a few things to me. > > > > I have run > > > > portupgrade -rf libxcb > > > > I normally run portupgrade -WrRpPa > This is what I ran and it totally hosed my system. > I had to revert back to an earlier version to be able to > bring X back up. portmanager -u -p -l -y worked beautifully to upgrade gnome and X. I did pkg_delete -f gtkmm for gnome, but otherwise... Actually, I didn't have anything to do with writing it, I just keep it working since it DTRT... robert. > This should have compiled and built everything that was affected > by the new X stuff - but it obviously didn't. > > > and it rebuilt quite a few pieces that had not been rebuilt in the > > standard portupgrade that gave me X.org 7.4 in the first place. > > > > After rebuilding firefox and a bunch of smaller libraries, my keyboard > > and mouse work, and so does firefox and my other apps. > > > > Thanks to everyone else for emailing me with ideas and suggestions! > > > > Dan > > > > > > ___ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > > > > signature.asc Description: This is a digitally signed message part
Re: Unhappy Xorg upgrade
Dan Allen wrote: Thanks to Robert for pointing out a few things to me. I have run portupgrade -rf libxcb I normally run portupgrade -WrRpPa This is what I ran and it totally hosed my system. I had to revert back to an earlier version to be able to bring X back up. This should have compiled and built everything that was affected by the new X stuff - but it obviously didn't. and it rebuilt quite a few pieces that had not been rebuilt in the standard portupgrade that gave me X.org 7.4 in the first place. After rebuilding firefox and a bunch of smaller libraries, my keyboard and mouse work, and so does firefox and my other apps. Thanks to everyone else for emailing me with ideas and suggestions! Dan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Unhappy Xorg upgrade
Thanks to Robert for pointing out a few things to me. I have run portupgrade -rf libxcb and it rebuilt quite a few pieces that had not been rebuilt in the standard portupgrade that gave me X.org 7.4 in the first place. After rebuilding firefox and a bunch of smaller libraries, my keyboard and mouse work, and so does firefox and my other apps. Thanks to everyone else for emailing me with ideas and suggestions! Dan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: /dev/cuau* ports hang after a while
At 08:00 AM 1/26/2009, Timo Rikkonen wrote: Hi, We are using "VScom PCI-200L" and "Moxa Technologies, C168H/PCI" -cards for serial ports. After installing 7.0 the ports or the connection to the port hang after a while. A "while" could be half-a-day or 10 minutes. There is no error message to be seen anywhere. Not all ports hang at the same time, it could be just one or two of them. Earlier versions (6.2-RELEASE) work just fine. The ports have different devicenames after 7.0, in 6.2 they were /dev/cuad4-7, now they are /dev/cuau0-3 (uart?) Is the application fairly low speed (e.g. 9600bps or slower) ? If so, try with 7.1R, not 7 and add hint.uart.0.flags="0x100" hint.uart.1.flags="0x100" to /boot/device.hints http://www.freebsd.org/cgi/query-pr.cgi?pr=121421 has details ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: /dev/cuau* ports hang after a while
On Mon, 26.01.2009 at 15:00:11 +0200, Timo Rikkonen wrote: > Hi, > > We are using "VScom PCI-200L" and "Moxa Technologies, C168H/PCI" > -cards for serial ports. After installing 7.0 the ports or the > connection to the port hang after a while. A "while" could be > half-a-day or 10 minutes. There is no error message to be seen > anywhere. What exactly do you mean by "hang"? I discovered something odd, when I upgraded my 6.3 box to 7.1, namely, that the serial console (no matter if it's sio or uart) will not echo anything, once I "hang up" the line for the first time. To make this clear: I reboot with serial console attached, I see kernel console, then getty/login prompt. I can login fine, and do stuff. Once I exit tip(1) on the terminal, the port is "mostly" dead on the server. I say mostly, because I can still blindly enter the root login and confirm via separate ssh login, that I'm logged in to the machine on the serial getty port. So it seems to me, whenever sio/uart receive the first device close event, they get b0rked and receive only input, but can no longer send any output. > Not all ports hang at the same time, it could be just one or two of > them. Earlier versions (6.2-RELEASE) work just fine. The ports have > different devicenames after 7.0, in 6.2 they were /dev/cuad4-7, now > they are /dev/cuau0-3 (uart?) Try rebuilding a kernel without uart and see if they come up as sio ports again (and work?) > We have over 20 installations, now two of them have been upgraded to 7.0 with > mentioned side effects. Is this identical hardware? Cheers, Ulrich Spörlein -- None are more hopelessly enslaved than those who falsely believe they are free -- Johann Wolfgang von Goethe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS, NFS and Network tuning
On Thu, 29 Jan 2009, Brent Jones wrote: On Wed, Jan 28, 2009 at 11:21 PM, Brent Jones wrote: ... The issue I am seeing, is that for certain file types, the FreeBSD NFS client will either issue an ASYNC write, or an FSYNC. However, NFSv3 and v4 both support "safe" ASYNC writes in the TCP versions of the protocol, so that should be the default. Issuing FSYNC's for every compete block transmitted adds substantial overhead and slows everything down. I use some patches (mainly for nfs write clustering on the server) by Bjorn Gronwall and some local fixes (mainly for vfs write clustering on the server, and tuning off excessive nfs[io]d daemons which get in each other's way due to poor scheduling, and things that only help for lots of small files), and see reasonable performance in all cases (~90% of disk bandwidth with all-async mounts, and half that with the client mounted noasync on an old version of FreeBSD. The client in -current is faster.) Writing is actually faster than reading here. ... My NFS mount command lines I have tried to get all data to ASYNC write: $ mount_nfs -3T -o async 192.168.0.19:/pdxfilu01/obsmtp /mnt/obsmtp/ $ mount_nfs -3T 192.168.0.19:/pdxfilu01/obsmtp /mnt/obsmtp/ $ mount_nfs -4TL 192.168.0.19:/pdxfilu01/obsmtp /mnt/obsmtp/ Also try -r16384 -w16384, and udp, and async on the server. I think block sizes default to 8K for udp and 32K for tcp. 8K is too small, and 32K may be too large (it increases latency for little benefit if the server fs block size is 16K). udp gives lower latency. async on the server makes little difference provided the server block size is not too small. I have found a 4 year old bug, which may be related to this. cp uses mmap for small files (and I imagine lots of things use mmap for file operations) and causes slowdowns via NFS, due to the fsync data provided above. http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/87792 mmap apparently breaks the async mount preference in the following code: from vnode_pager.c: % /* %* pageouts are already clustered, use IO_ASYNC t o force a bawrite() % * rather then a bdwrite() to prevent paging I/O from saturating % * the buffer cache. Dummy-up the sequential heuristic to cause %* large ranges to cluster. If neither IO_SYNC or IO_ASYNC is set, %* the system decides how to cluster. %*/ % ioflags = IO_VMIO; % if (flags & (VM_PAGER_PUT_SYNC | VM_PAGER_PUT_INVAL)) % ioflags |= IO_SYNC; This apparently gives lots of sync writes. (Sync writes are the default for nfs, but we mount with async to try to get async writes.) % else if ((flags & VM_PAGER_CLUSTER_OK) == 0) % ioflags |= IO_ASYNC; nfs doesn't even support this flag. In fact, ffs is the only file system that supports it, and here is the only place that sets it. This might explain some slowness. One of the bugs in vfs clustering that I don't have is related to this. IIRC, mounting the server with -o async doesn't work as well as it should because the buffer cache becomes congested with i/o that should have been sent to the disk. Some writes must be done async as explained above, but one place in vfs_cache.c is too agressive in delaying async writes for file systems that are mounted async. This problem is more noticeable for nfs, at least with networks not much faster than disks, since it results in the client and server taking turns waiting for each other. (The names here are very confusing -- the async mount flag normally delays both sync and async writes for as long as possible, except for nfs it doesn't affect delays but asks for async writes instead of sync writes on the server, while the IO_ASYNC flag asks for async writes and thus often has the opposite sense to the async mount flag.) % ioflags |= (flags & VM_PAGER_PUT_INVAL) ? IO_INVAL: 0; % ioflags |= IO_SEQMAX << IO_SEQSHIFT; Bruce ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
RE: Replace Cisco IOS/CBOS with freebsd - possible?
> Pfsense sounds like exactly what you're looking for. It's a stripped > down freeBSD with a fancy web interface (well, not too fancy, it's > been incredibly stable for me). I've deployed it a couple times in > pseudo production environments and it's been holding up well for the > last 1.5years+. Seconded for Pfsense -- although I doubt the Cisco hardware would be compatible with FreeBSD, and even if it is , I wouldn't want to use it in a production environment without thorough testing. If someone can provide more detailed hardware specs, including the chipsets and processor details of the cisco hardware , im sure we could realistically evaluate the feasibility. --- Kevin Systems Administrator www.stardothosting.com/linux-vps-hosting ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Replace Cisco IOS/CBOS with freebsd - possible?
Pfsense sounds like exactly what you're looking for. It's a stripped down freeBSD with a fancy web interface (well, not too fancy, it's been incredibly stable for me). I've deployed it a couple times in pseudo production environments and it's been holding up well for the last 1.5years+. You can also check out http://www.netgate.com/product_info.php?cPath=60_84&products_id=492 for a nice PIX-sized chasis for pfsense if you need a small box. On Jan 29, 2009, at 6:02 AM, Chris H wrote: Hello, and thank you for your reply. Quoting Michael Grant : On Thu, Jan 29, 2009 at 2:15 PM, Chris H wrote: Hello, and thank you for your reply. While it's not /exactly/ what I was looking for - it's close. :) The "filtering" capability is my biggest gripe on the Cisco *DSL products. They're just not as /capable/ as is offered in FBSD. DNS is another plus (pfDNS). But I don't think I'd be modify pfDNS to accomodate BIND, or unbound. Although tinydns might be able to fit the bill. Oh well, it's close - thanks for the pointer. :) You can run iptables on openwrt. Actually, I was thinking more along the lines of pf(4). I think it's more efficient - especially combined with all the network tuning that has been done recently by Robert Watson, John Baldwin, Mohan Srinivasan, Peter Wemm, and others. Another reason I'm so inclined to be FBSD centric on this. :) You can compile most anything for it, you're only limited by it's memory and cpu. I'm not familiar with pfDNS. But if it runs on freebsd, it probably can be made to run on openwrt as well. Indeed, it's running a FreeBSD base. But like you said; CPU, and Memory are the only boundries here. Will need to do more research to compare limits against a /desired/ install base. Thanks again for the reply. --Chris Michael ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org " ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Unable to boot after upgrade to 7.0 or 7.1 STABLE
Thanks John On Thu, Jan 29, 2009 at 7:43 PM, wrote: > I entered ufs:ad7s1a and booted the kernel when I > recognized that the drive had been re-named from ad9 to ad7. After > booting, I changed /etc/fstab appropiately and have had no further > problems. I've never run into this with previous upgrades, very odd. > Unfortunately, this does not work for me. I tried this from the onset of the problem and ended up with nothing. I got as far as ad15s1a (yeah... pushing it as far as I could) with no results. I cannot seem to get any further than mountroot> how did you notice that the drive numbering had moved from ad9 to ad7? I have booted into single user mode with verbose logging and i see no reference to any adx devices. I do see ata entries which recognise the disk as a Intel ICH7 SATA300 and ata0 being reference at atapci0, but other than that, I see no references to any adx. When i boot the RELEASE kernel, i get this ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=40 wire ad0: 152627MB at ata0-master SATA150 ad0: 312581808 sectors [310101C/16H/63S] 16 sectors/interrupt 1 depth queue When i boot the 7.1 STABLE kernel, with verbose logging, i get this ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=40 wire ata1: reiniting channel ... ... and then the famous mountroot> Thanks -- Mike Of course, you might discount this possibility, but remember that one in a million chances happen 99% of the time. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Unhappy Xorg upgrade
On January 28, 2009 10:10 pm Larry Baird wrote: > Initially thought this upgrade was a mistake, until I found out about > "hald_enable" and "dbus_enable". Upgrade would have be a lot easier if > they were mentioned in /usr/ports/UPDATING. I would have found these > knobs more quickly if mentioned in HALD(8). or if they had default values > in /etc/rc/defaults/rc.conf. Did get a laugh out of HALD(8) telling me /etc/defaults/rc.conf only lists values for things that are started via /etc/rc.d/*, as that is all that ships with FreeBSD. Values that can be added to rc.conf to enable daemons installed via ports obviously can't be listed there, as the ports tree is constantly changing. Ports daemons are started via scripts in /usr/local/etc/rc.d/, so you should always check there for new scripts installed via ports, to see if there's anything you need to add to rc.conf. This is covered, I believe, in the rc(8) and/or the ports(7) man page, and the ports section of the Handbook. -- Freddie fjwc...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Unable to boot after upgrade to 7.0 or 7.1 STABLE
On Thu, Jan 29, 2009 at 6:14 PM, Ollivier Robert wrote: > According to Mike Barnard: > >no, i have this: > >options GEOM_PART_GPT # GUID Partition Tables. > >options GEOM_LABEL # Provides labelization > > Try adding GEOM_PART_BSD then. no change. I have added this and I still end up with mountroot> -- Mike Of course, you might discount this possibility, but remember that one in a million chances happen 99% of the time. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Unable to boot after upgrade to 7.0 or 7.1 STABLE
Mike, I ran into this very issue on a Mac Pro that I installed 7.1-RELEASE on and then cvsup'd, make buildworld to 7.1-STABLE. On my machine, 7.1-RELEASE named the drives ad8, ad9, and ad10 (I have 3 drives and installed 7.1-RELEASE on ad9). When I booted the STABLE keneral (GENERIC no tweaks), this kernel named the drives ad6, ad7, and ad8 and I was dropped into this "Manual root filesystem" prompt. ? did not list any drives however, I entered ufs:ad7s1a and booted the kernel when I recognized that the drive had been re-named from ad9 to ad7. After booting, I changed /etc/fstab appropiately and have had no further problems. I've never run into this with previous upgrades, very odd. regards John > Hi All, > > I have run into a problem that seem rather puzzling. I have upgraded an > installation of FreeBSD from 7.0-RELEASE to 7.0-STABLE and 7.1-STABLE, but > i > fail to boot with either one of the STABLE upgrades. I end up at this > point: > > > Trying to mount root from ufs:/dev/ad0s1a > Manual root filesystem specification: > : Mount using filesystem > eg. ufs:da0s1a > ? List valid disk boot devices > Abort manual input > > When i type ?, i get nothing. When i try to load all possible drives, from > ad0s1a to ad9s1a, i get nothing. When i boot kernel.old, i see this: > > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfa00-0xfa0f mem > 0xfdffe000-0xfdffe3ff > at device 31.2 on pci0 > ... > ad0: 152627MB at ata0-master SATA150 > > It seems that FreeBSD recognises this drive as a SATA300 but later on > refers > to it as SATA150. Could this be the problem. > > This is what i have about this disk when i boot the RELEASE version of > FreeBSD: > > #pciconf -lv > atap...@pci0:0:31:2:class=0x01018a card=0x73361462 chip=0x27c08086 > rev=0x01 hdr=0x00 > vendor = 'Intel Corporation' > device = '82801GB/GR/GH (ICH7 Family) Serial ATA Storage > Controller' > class = mass storage > subclass = ATA > > #atacontrol cap ad0 > > Protocol Serial ATA II > device model WDC WD1600AAJS-60PSA0 > serial number WD-WMAP96717073 > firmware revision 21.12M21 > cylinders 16383 > heads 16 > sectors/track 63 > lba supported 268435455 sectors > lba48 supported 312581808 sectors > dma supported > overlap not supported > > Feature Support EnableValue Vendor > write cacheyes yes > read ahead yes yes > Native Command Queuing (NCQ) yes - 31/0x1F > Tagged Command Queuing (TCQ) no no 31/0x1F > SMART yes yes > microcode download yes yes > security yes no > power management yes yes > advanced power management no no 0/0x00 > automatic acoustic management no no 0/0x00 0/0x00 > > # atacontrol mode ad0 > current mode = SATA150 > > > When i boot in verbose mode, i get this: > > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfa00-0xfa0f mem > 0xfdffe000-0xfdffe3ff > at device 31.2 on pci0 > atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xfa00 > pci0: child atapci0 requested type 4 for rid 0x24, but the BAR says it is > an > memio > ata0: on atapci0 > atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 > atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 > ata0: reset tp1 mask=03 ostat0=50 ostat1=00 > ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 > ata0: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 > ata0: reset tp2 stat0=50 stat1=00 devices=0x1 > ioapic0: routing intpin 14 (ISA IRQ 14) to vector 54 > ata0: [MPSAFE] > ata0: [ITHREAD] > ata1: on atapci0 > atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 > atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 > ata1: reset tp1 mask=03 ostat0=00 ostat1=00 > ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb > ata1: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb > ata1: reset tp2 stat0=00 stat1=00 devices=0xc > ioapic0: routing intpin 15 (ISA IRQ 15) to vector 55 > ata1: [MPSAFE] > ata1: [ITHREAD] > ... > ... > ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=40 wire > ad0: 152627MB at ata0-master SATA150 > ad0: 312581808 sectors [310101C/16H/63S] 16 sectors/interrupt 1 depth > queue > GEOM: new disk ad0 > ad0: Intel check1 failed > ad0: Adaptec check1 failed > ad0: LSI (v3) check1 failed > ad0: LSI (v2) check1 failed > ad0: FreeBSD check1 failed > ata1: reiniting channel .. > ata1: reset tp1 mask=03 ostat0=00 ostat1=00 > ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb > ata1: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb > ata1: reset tp2 stat0=00 stat1=00 devices=0xc > ata1: reinit done .. > ata1: reiniting channel .. > ata1: reset tp1 mask=03 ostat0=00 ostat1=00 > ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb > ata1: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb > ata1: reset tp2 stat0=00 stat1=00 devices=0xc > ata1: reinit done .. > ata1-master
Re: Unhappy Xorg upgrade
On Thu, 2009-01-29 at 09:25 -0500, Alex Goncharov wrote: > ,--- You/Robert (Thu, 29 Jan 2009 09:12:47 -0500) * > | Problem is, it isn't just the Xserver... All of the pieces are > | intertwined and so in many cases to update Xserver you also need to > | update some/several libraries as well as all of your drivers. Xorg is > | about 60 or 70 ports now. > > That can be handled, it seems to me. > > My current port upgrade problem is that I cannot csup the tree and get > the old X to rebuild dependent components. > > | FWIW, I have Xserver 1.6 and xrandr bits that are rc already... as well > | as a new intel driver that I don't want to update without xserver 1.6. > > I would be willing to test 1.6 on my many different machines, provided > there is a clear and inexpensive (< 2 hours) path to a rollback. I'll assemble a patch as soon as I can get to it. From where we are now in ports, the only thing that has to be updated that I can think of is the server, then rebuild your drivers. robert. > -- Alex -- alex-goncha...@comcast.net -- signature.asc Description: This is a digitally signed message part
Intel Mobo MARVEL RAID adapters and amd64 FreeBSD on QuadCore and i7 series Processors
These show up under Windows XP as if they are SCSI adapters (they're not, obviously.) Has there been any view towards supporting these on FreeBSD? They're on all the recent Intel motherboards for the last year and a half or so. Also, is there any particular benefit (or penalty) to running the amd64 build on Quad-Core or i7-series processors? I have an app that might benefit from access to more than 4GB of physical RAM as the working dataset grows but am hesitant to run the 64bit version on that processor (which I understand isn't REALLY a 64-bit chip) if I'm going to run into a penalty for doing so in terms of generalized performance. -- -- Karl Denninger k...@denninger.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
7.1-RELEASE growfs/fsck_ffs woes
Greetings, I have a hard time with file system access. Here's the story: I'd been unhappy about GEOM_JOURNAL within the same provider as my /usr and /var partitions (used JOURNAL on a fresh install), it would occasionally give up on fsync() for lock messups (FreeBSD 7.1-RELEASE-p2). Several weeks ago, I reverted my -o async journalled /var to softupdates without journal, with no ill effects. AFAIR, I installed with gjournal label with just one provider, and then newfs UFS2 with journal. Earlier today, I disabled the journal on /usr (shutdown to single user mode, dismount, gjournal sync, gjournal stop, gjournal clear, tunefs -J disable, kldunload geom_journal, fsck) - that worked, and fsck preen considered the FS clean. I tried to resize the partition to its full size with growfs; and it warned about being unable to allocate some 58,000 blocks, but performed the operation (i. e. I got a list of superblocks) - apparently it completed. A subsequent fsck -f however turned up with a gazillion of "DUP" blocks, in random places. I have no explanation for that; am currently running fsck -y. Accidentally, I ran growfs twice, but the second run didn't seem to do a lot - it just warned it couldn't allocate 58,600+ sectors and quit. I've also found that fsck_ffs's pass 1b is EXTREMELY slow, and from a cursory glance at pass1b.c, some none-scalable (as in O(n^2) or worse) effects seem to be at play. I'm currently away from the machine, but any insights on the growfs corruption and/or pass1b.c accelerators are welcome - ext2fsck is a lot faster when doing deep searches for duplicate blocks (pass 1b and pass 1c), but I haven't checked the code. The partition slice is several GB in size with default newfs settings, but not overly huge (<< 100 GB), and last time I checked, it had taken around 30 min for scanning 7 out of 78 (IIRC) cylinder groups. I hope fsck doesn't do more damage... ;-) This is an Athlon XP 2500+ (later "Barton" version with 512 kB L2 cache) with 1 GB of RAM and a reasonably fast Maxtor 250 GB SATA drive, with a reasonably fast fsck if pass1b isn't needed (perhaps two or three minutes). I've recompiled fsck_ffs with -O3 -march=athlon-xp to peep cycles, but compiler optimization cannot fix slow algorithms. Thanks in advance, Matthias ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 7.1, mpt and slow writes
Peter C. Lai wrote: I am guessing this is only related to SATA drives on SAS controllers? The only mpt hardware I have is LSILogic 1030 Ultra4 and it writes sustained 40MB/s to my LTO-2 drives out of the box without any tweaking. Correct. When SATA drives are used instead of SAS drives on this controller it disables the write cache resulting in poor performance. The tunable was added by Scott Long to solve the problem (though at the cost of greater risk to data). Richard smime.p7s Description: S/MIME Cryptographic Signature
Re: 7.1, mpt and slow writes
On 2009-01-29 11:43:46AM +, Richard Tector wrote: > Charles Sprickman wrote: >> Hello, >> >> I think this needs a few more eyes: >> >> http://lists.freebsd.org/pipermail/freebsd-scsi/2009-January/003782.html >> >> In short, writes are slow, likely do to the write-cache being enabled on >> the controller. The sysctl used in 6.x to turn the cache off don't seem >> to be in 7.x. > I am guessing this is only related to SATA drives on SAS controllers? The only mpt hardware I have is LSILogic 1030 Ultra4 and it writes sustained 40MB/s to my LTO-2 drives out of the box without any tweaking. -- === Peter C. Lai | Bard College at Simon's Rock Systems Administrator| 84 Alford Rd. Information Technology Svcs. | Gt. Barrington, MA 01230 USA peter AT simons-rock.edu | (413) 528-7428 === ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Unable to boot after upgrade to 7.0 or 7.1 STABLE
According to Mike Barnard: >no, i have this: >options GEOM_PART_GPT # GUID Partition Tables. >options GEOM_LABEL # Provides labelization Try adding GEOM_PART_BSD then. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr Dons / donation Ondine : http://ondine.keltia.net/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
GSSAPI support in bind
I'm having a problem enabling gssapi support in bind 9.5 under FreeBSD 7. I now think it may be something related to freebsd. Even if I force the path in the Makefile with the entry --with-gssapi=/usr/include/gssapi.h /usr/include/gssapi/gssapi.h, I still get configure:6359: checking for GSSAPI library configure:6385: result: disabled in config.log after I run make. If this is not the proper forum for this question, please let me know. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Unable to boot after upgrade to 7.0 or 7.1 STABLE
On Thu, Jan 29, 2009 at 5:54 PM, Ollivier Robert wrote: > According to Mike Barnard: > > Any one with any ideas? > > Do you have GEOM_BSD in your kernel configuration file? no, i have this: options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization -- Mike Of course, you might discount this possibility, but remember that one in a million chances happen 99% of the time. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Unable to boot after upgrade to 7.0 or 7.1 STABLE
According to Mike Barnard: > Any one with any ideas? Do you have GEOM_BSD in your kernel configuration file? -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr Dons / donation Ondine : http://ondine.keltia.net/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Unhappy Xorg upgrade
On Thu, 2009-01-29 at 08:16 -0500, Stephen Clark wrote: > Alex Goncharov wrote: > > ,--- You/Bruce (Thu, 29 Jan 2009 12:06:45 +) * > > | One theory is that somehow the mouse driver ioctls which are passed > > | to ums, are somehow hosing USB, although why that would be, I don't > > | understand. ums currently doesn't have driver instrumentation in that > > path. > > | > > | I pulled a fairly detailed IRC log of my collaborative debugging > > | session with Robert, please ping me if you need details of this. > > `* > > > > Thank you for the detailed write up! No help to me, though -- on my > > Latitude laptop, there was no problem with any mouse: USB or the > > built-in "pointing device". It was the keyboard -- and, trust me, I > > did try many variations of the machine configuration, and I did do a > > lot of reading on various relevant topics (writing, too, as you have > > seen :-() > > > > As I mentioned elsewhere, my way of resolving the problem after a > > one-and-a-half day's of struggle was to revert to the old X (on that > > laptop). > > > > On the topic of how this upgrade was introduced, I can't help but > > refer to my recent experience helping to fix TWM: > > > > ,--- Eeri Kask (Mon, 29 Sep 2008 12:21:17 +0200) * > > | > I have used the new version of TWM for five days, using it less > > | > intensively than usual. No problems in seen during my (light) use. > > | > > | Hello Alex, no problem at all! Improved solutions have priority over > > | promised deadlines. > > | > > | Thank you for your time helping to improve TWM, :-) > > | > > `* > > > > Eeri Kask and I worked together all past September on fixing TWM > > crashes: I was willingly trying his multiple versions of the code, but > > I knew what I was risking, could choose convenient times for building > > and trying every new version (we tried about 30 of them) -- and I > > could always go back to the previous version (or the original TWM from > > ports). > > > > I would be happy to try a new X on my machines, if it were labeled as > > experimental, with an easy way to revert to the old X (while being in > > the testing stage). As it is, this upgrade brought a lot of problems > > to unsuspecting people, at the time they don't quite choose, with > > potential dangers not disclosed. > > > > In honesty, this upgrade should have been presented this way, way > > before the code was placed in the ports source tree: > > > > * We'll have a new X in ports soon -- there are multiple reports of > >problems with it on Linux. > > > > * We want to try it on FreeBSD -- but nobody is forcing you to do the > >upgrade. > > > > * If you, of your own free will, choose to upgrade, you may have > >hours and days of problems -- but heck, it was your choice. > > > > * If your problems cannot be fixed, you'll have to figure out > >something yourself. > > > > * If you choose not to upgrade, you are frozen with the pre-existing > >ports collection: there may be no automated ways to upgrade your > >packages, with the old X in place. Of course, you can somehow get > >pieces on new ports, unrelated to X. > > > > * The choice is totally yours. > > > > -- Alex -- alex-goncha...@comcast.net -- > > > > > > ___ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > > > On my system the matrox driver quit working, when I tried using the built in > via > the via driver wouldn't compile so when I tried X -configure it generated > a config using vesa, but when I tried to start X with the xorg.conf.new with > the vesa driver X said it couldn't find any screens. I finally had to revert > back to an older version. This should not happen on a stable system. for Via hardware, you should be using openchrome. robert. > -- > > "They that give up essential liberty to obtain temporary safety, > deserve neither liberty nor safety." (Ben Franklin) > > "The course of history shows that as a government grows, liberty > decreases." (Thomas Jefferson) > > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" signature.asc Description: This is a digitally signed message part
Unable to boot after upgrade to 7.0 or 7.1 STABLE
Hi All, I have run into a problem that seem rather puzzling. I have upgraded an installation of FreeBSD from 7.0-RELEASE to 7.0-STABLE and 7.1-STABLE, but i fail to boot with either one of the STABLE upgrades. I end up at this point: Trying to mount root from ufs:/dev/ad0s1a Manual root filesystem specification: : Mount using filesystem eg. ufs:da0s1a ? List valid disk boot devices Abort manual input When i type ?, i get nothing. When i try to load all possible drives, from ad0s1a to ad9s1a, i get nothing. When i boot kernel.old, i see this: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfa00-0xfa0f mem 0xfdffe000-0xfdffe3ff at device 31.2 on pci0 ... ad0: 152627MB at ata0-master SATA150 It seems that FreeBSD recognises this drive as a SATA300 but later on refers to it as SATA150. Could this be the problem. This is what i have about this disk when i boot the RELEASE version of FreeBSD: #pciconf -lv atap...@pci0:0:31:2:class=0x01018a card=0x73361462 chip=0x27c08086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controller' class = mass storage subclass = ATA #atacontrol cap ad0 Protocol Serial ATA II device model WDC WD1600AAJS-60PSA0 serial number WD-WMAP96717073 firmware revision 21.12M21 cylinders 16383 heads 16 sectors/track 63 lba supported 268435455 sectors lba48 supported 312581808 sectors dma supported overlap not supported Feature Support EnableValue Vendor write cacheyes yes read ahead yes yes Native Command Queuing (NCQ) yes - 31/0x1F Tagged Command Queuing (TCQ) no no 31/0x1F SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management no no 0/0x00 automatic acoustic management no no 0/0x00 0/0x00 # atacontrol mode ad0 current mode = SATA150 When i boot in verbose mode, i get this: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfa00-0xfa0f mem 0xfdffe000-0xfdffe3ff at device 31.2 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xfa00 pci0: child atapci0 requested type 4 for rid 0x24, but the BAR says it is an memio ata0: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata0: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=50 stat1=00 devices=0x1 ioapic0: routing intpin 14 (ISA IRQ 14) to vector 54 ata0: [MPSAFE] ata0: [ITHREAD] ata1: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=03 ostat0=00 ostat1=00 ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: reset tp2 stat0=00 stat1=00 devices=0xc ioapic0: routing intpin 15 (ISA IRQ 15) to vector 55 ata1: [MPSAFE] ata1: [ITHREAD] ... ... ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=40 wire ad0: 152627MB at ata0-master SATA150 ad0: 312581808 sectors [310101C/16H/63S] 16 sectors/interrupt 1 depth queue GEOM: new disk ad0 ad0: Intel check1 failed ad0: Adaptec check1 failed ad0: LSI (v3) check1 failed ad0: LSI (v2) check1 failed ad0: FreeBSD check1 failed ata1: reiniting channel .. ata1: reset tp1 mask=03 ostat0=00 ostat1=00 ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: reset tp2 stat0=00 stat1=00 devices=0xc ata1: reinit done .. ata1: reiniting channel .. ata1: reset tp1 mask=03 ostat0=00 ostat1=00 ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: reset tp2 stat0=00 stat1=00 devices=0xc ata1: reinit done .. ata1-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=40 wire Any one with any ideas? -- Mike Of course, you might discount this possibility, but remember that one in a million chances happen 99% of the time. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Unhappy Xorg upgrade
,--- You/Robert (Thu, 29 Jan 2009 09:12:47 -0500) * | Problem is, it isn't just the Xserver... All of the pieces are | intertwined and so in many cases to update Xserver you also need to | update some/several libraries as well as all of your drivers. Xorg is | about 60 or 70 ports now. That can be handled, it seems to me. My current port upgrade problem is that I cannot csup the tree and get the old X to rebuild dependent components. | FWIW, I have Xserver 1.6 and xrandr bits that are rc already... as well | as a new intel driver that I don't want to update without xserver 1.6. I would be willing to test 1.6 on my many different machines, provided there is a clear and inexpensive (< 2 hours) path to a rollback. -- Alex -- alex-goncha...@comcast.net -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Unhappy Xorg upgrade
Alex Goncharov wrote: ,--- You/Bruce (Thu, 29 Jan 2009 12:06:45 +) * | One theory is that somehow the mouse driver ioctls which are passed | to ums, are somehow hosing USB, although why that would be, I don't | understand. ums currently doesn't have driver instrumentation in that path. | | I pulled a fairly detailed IRC log of my collaborative debugging | session with Robert, please ping me if you need details of this. `* Thank you for the detailed write up! No help to me, though -- on my Latitude laptop, there was no problem with any mouse: USB or the built-in "pointing device". It was the keyboard -- and, trust me, I did try many variations of the machine configuration, and I did do a lot of reading on various relevant topics (writing, too, as you have seen :-() As I mentioned elsewhere, my way of resolving the problem after a one-and-a-half day's of struggle was to revert to the old X (on that laptop). On the topic of how this upgrade was introduced, I can't help but refer to my recent experience helping to fix TWM: ,--- Eeri Kask (Mon, 29 Sep 2008 12:21:17 +0200) * | > I have used the new version of TWM for five days, using it less | > intensively than usual. No problems in seen during my (light) use. | | Hello Alex, no problem at all! Improved solutions have priority over | promised deadlines. | | Thank you for your time helping to improve TWM, :-) | `* Eeri Kask and I worked together all past September on fixing TWM crashes: I was willingly trying his multiple versions of the code, but I knew what I was risking, could choose convenient times for building and trying every new version (we tried about 30 of them) -- and I could always go back to the previous version (or the original TWM from ports). I would be happy to try a new X on my machines, if it were labeled as experimental, with an easy way to revert to the old X (while being in the testing stage). As it is, this upgrade brought a lot of problems to unsuspecting people, at the time they don't quite choose, with potential dangers not disclosed. In honesty, this upgrade should have been presented this way, way before the code was placed in the ports source tree: * We'll have a new X in ports soon -- there are multiple reports of problems with it on Linux. * We want to try it on FreeBSD -- but nobody is forcing you to do the upgrade. * If you, of your own free will, choose to upgrade, you may have hours and days of problems -- but heck, it was your choice. * If your problems cannot be fixed, you'll have to figure out something yourself. * If you choose not to upgrade, you are frozen with the pre-existing ports collection: there may be no automated ways to upgrade your packages, with the old X in place. Of course, you can somehow get pieces on new ports, unrelated to X. * The choice is totally yours. -- Alex -- alex-goncha...@comcast.net -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" On my system the matrox driver quit working, when I tried using the built in via the via driver wouldn't compile so when I tried X -configure it generated a config using vesa, but when I tried to start X with the xorg.conf.new with the vesa driver X said it couldn't find any screens. I finally had to revert back to an older version. This should not happen on a stable system. -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Unhappy Xorg upgrade
On Thu, 2009-01-29 at 08:58 -0500, Alex Goncharov wrote: > ,--- You/Robert (Thu, 29 Jan 2009 08:40:11 -0500) * > | I've had patches available for probably a couple of months now posted to > | freebsd-...@. For the few people who tested it, I had no real issues > | reported. We were stalled for a long time, While X kept moving, so the > | amount of change was large. This update also brings in support for a > | lot of people who are running newer hardware. > | > | I realize that there are some issues with the mouse driver... I'm > | trying to look at and resolve, but I don't really know input drivers, so > | I doing a lot of guess work. On top of that I do have a day job, so > | time is limited. > > Understood. > > Would you have spent more time if the new X was introduced as two (?) > new ports: xorg-server-devel and libxcb-devel. Is X less complicated, > less dangerous, less "user-binding" than firefox or emacs? Problem is, it isn't just the Xserver... All of the pieces are intertwined and so in many cases to update Xserver you also need to update some/several libraries as well as all of your drivers. Xorg is about 60 or 70 ports now. FWIW, I have Xserver 1.6 and xrandr bits that are rc already... as well as a new intel driver that I don't want to update without xserver 1.6. robert. > -- Alex -- alex-goncha...@comcast.net -- signature.asc Description: This is a digitally signed message part
Re: Replace Cisco IOS/CBOS with freebsd - possible?
Hello, and thank you for your reply. Quoting Michael Grant : On Thu, Jan 29, 2009 at 2:15 PM, Chris H wrote: Hello, and thank you for your reply. While it's not /exactly/ what I was looking for - it's close. :) The "filtering" capability is my biggest gripe on the Cisco *DSL products. They're just not as /capable/ as is offered in FBSD. DNS is another plus (pfDNS). But I don't think I'd be modify pfDNS to accomodate BIND, or unbound. Although tinydns might be able to fit the bill. Oh well, it's close - thanks for the pointer. :) You can run iptables on openwrt. Actually, I was thinking more along the lines of pf(4). I think it's more efficient - especially combined with all the network tuning that has been done recently by Robert Watson, John Baldwin, Mohan Srinivasan, Peter Wemm, and others. Another reason I'm so inclined to be FBSD centric on this. :) You can compile most anything for it, you're only limited by it's memory and cpu. I'm not familiar with pfDNS. But if it runs on freebsd, it probably can be made to run on openwrt as well. Indeed, it's running a FreeBSD base. But like you said; CPU, and Memory are the only boundries here. Will need to do more research to compare limits against a /desired/ install base. Thanks again for the reply. --Chris Michael ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Unhappy Xorg upgrade
,--- You/Robert (Thu, 29 Jan 2009 08:40:11 -0500) * | I've had patches available for probably a couple of months now posted to | freebsd-...@. For the few people who tested it, I had no real issues | reported. We were stalled for a long time, While X kept moving, so the | amount of change was large. This update also brings in support for a | lot of people who are running newer hardware. | | I realize that there are some issues with the mouse driver... I'm | trying to look at and resolve, but I don't really know input drivers, so | I doing a lot of guess work. On top of that I do have a day job, so | time is limited. Understood. Would you have spent more time if the new X was introduced as two (?) new ports: xorg-server-devel and libxcb-devel. Is X less complicated, less dangerous, less "user-binding" than firefox or emacs? -- Alex -- alex-goncha...@comcast.net -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Replace Cisco IOS/CBOS with freebsd - possible?
Hello Michael, and thank you for your reply. Yes, OpenWRT is pretty much was what I was asking about. Being /exclusively/ FBSD I hadn't run across it - thanks. :) Of course it doesn't support any Cisco products, but hey, like you said; I can just choose one that it /does/, or write a driver myself. I was also looking at Sangoma's (http://www.sangoma.com) wanpipe (ftp://ftp.sangoma.com/FreeBSD/wanpipe/) as a possible base point. It already supports BSD and works with nearly all HW. But now - in an effort to stay on a BSD platform, I'm thinking of using a combination of nanobsd, and OpenWRT as a framework to build a FreeBSD based equivalent (or better) version of OpenWRT. I think I'll fly a page now to announce the project - look for it in a ports section near you. ;) Thank you again for the reply. --Chris Quoting Michael Grant : Check out OpenWRT, this is essentially linux (busybox on a linux kernel I believe) that you can load on a router and it runs on more than a handfull of routers. It's not freebsd. Not sure if the Cisco 837 is supported though, but many other routers are. If not supported, just go out and buy a cheap router that is supported and replace your cisco. Michael Grant On Thu, Jan 29, 2009 at 10:50 AM, Chris H wrote: Greetings, I'm RP for a fairly large chunk of IP real estate. I carved out a /27 segment for my home network. Which is currently running over a cisco 837 GW (adsl/router). I'm not really keen on it (the router/modem). So I thought to myself that it couldn't be /that/ hard to build a box with FBSD that could replace it - am I crazy? Wouldn't it be possible to upload a minimal build of FBSD to the modem, not unlike one would tftp a new version of cisco's IOS, or CBOS? I searched the projects area to see if anyone had tried it. But the only thing that came anywhere near was netperf. But the only similarity is that it is network related. Anyway, this seems quite feasable as far as I can tell. So I thought I'd ask in hopes someone might enlighten me further. Maybe someones already tried it? Thank you for all your time and consideration in this matter. --Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Unhappy Xorg upgrade
On Thu, 2009-01-29 at 07:46 -0500, Alex Goncharov wrote: > ,--- You/Bruce (Thu, 29 Jan 2009 12:06:45 +) * > | One theory is that somehow the mouse driver ioctls which are passed > | to ums, are somehow hosing USB, although why that would be, I don't > | understand. ums currently doesn't have driver instrumentation in that path. > | > | I pulled a fairly detailed IRC log of my collaborative debugging > | session with Robert, please ping me if you need details of this. > `* > > Thank you for the detailed write up! No help to me, though -- on my > Latitude laptop, there was no problem with any mouse: USB or the > built-in "pointing device". It was the keyboard -- and, trust me, I > did try many variations of the machine configuration, and I did do a > lot of reading on various relevant topics (writing, too, as you have > seen :-() > > As I mentioned elsewhere, my way of resolving the problem after a > one-and-a-half day's of struggle was to revert to the old X (on that > laptop). > > On the topic of how this upgrade was introduced, I can't help but > refer to my recent experience helping to fix TWM: > > ,--- Eeri Kask (Mon, 29 Sep 2008 12:21:17 +0200) * > | > I have used the new version of TWM for five days, using it less > | > intensively than usual. No problems in seen during my (light) use. > | > | Hello Alex, no problem at all! Improved solutions have priority over > | promised deadlines. > | > | Thank you for your time helping to improve TWM, :-) > | > `* > > Eeri Kask and I worked together all past September on fixing TWM > crashes: I was willingly trying his multiple versions of the code, but > I knew what I was risking, could choose convenient times for building > and trying every new version (we tried about 30 of them) -- and I > could always go back to the previous version (or the original TWM from > ports). > > I would be happy to try a new X on my machines, if it were labeled as > experimental, with an easy way to revert to the old X (while being in > the testing stage). As it is, this upgrade brought a lot of problems > to unsuspecting people, at the time they don't quite choose, with > potential dangers not disclosed. > > In honesty, this upgrade should have been presented this way, way > before the code was placed in the ports source tree: > > * We'll have a new X in ports soon -- there are multiple reports of >problems with it on Linux. > > * We want to try it on FreeBSD -- but nobody is forcing you to do the >upgrade. > > * If you, of your own free will, choose to upgrade, you may have >hours and days of problems -- but heck, it was your choice. > > * If your problems cannot be fixed, you'll have to figure out >something yourself. > > * If you choose not to upgrade, you are frozen with the pre-existing >ports collection: there may be no automated ways to upgrade your >packages, with the old X in place. Of course, you can somehow get >pieces on new ports, unrelated to X. I've had patches available for probably a couple of months now posted to freebsd-...@. For the few people who tested it, I had no real issues reported. We were stalled for a long time, While X kept moving, so the amount of change was large. This update also brings in support for a lot of people who are running newer hardware. I realize that there are some issues with the mouse driver... I'm trying to look at and resolve, but I don't really know input drivers, so I doing a lot of guess work. On top of that I do have a day job, so time is limited. At this point, I seem to be pretty much responsible for at least intel agp, if not most all of agp, drm, and sharing a lot of the workload for the Mesa ports and Xorg. So, if anyone knows about input devices, feel free to jump in and help me out. robert. > * The choice is totally yours. > > -- Alex -- alex-goncha...@comcast.net -- > > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" signature.asc Description: This is a digitally signed message part
Re: Replace Cisco IOS/CBOS with freebsd - possible?
Check out OpenWRT, this is essentially linux (busybox on a linux kernel I believe) that you can load on a router and it runs on more than a handfull of routers. It's not freebsd. Not sure if the Cisco 837 is supported though, but many other routers are. If not supported, just go out and buy a cheap router that is supported and replace your cisco. Michael Grant On Thu, Jan 29, 2009 at 10:50 AM, Chris H wrote: > Greetings, > I'm RP for a fairly large chunk of IP real estate. I carved out > a /27 segment for my home network. Which is currently running over > a cisco 837 GW (adsl/router). I'm not really keen on it (the router/modem). > So I thought to myself that it couldn't be /that/ hard to build a > box with FBSD that could replace it - am I crazy? Wouldn't it > be possible to upload a minimal build of FBSD to the modem, not unlike > one would tftp a new version of cisco's IOS, or CBOS? I searched > the projects area to see if anyone had tried it. But the only thing > that came anywhere near was netperf. But the only similarity is that it > is network related. Anyway, this seems quite feasable as far as I can > tell. So I thought I'd ask in hopes someone might enlighten me further. > Maybe someones already tried it? > > Thank you for all your time and consideration in this matter. > > --Chris > > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
RE: Replace Cisco IOS/CBOS with freebsd - possible?
Hello, and thank you for your reply. While it's not /exactly/ what I was looking for - it's close. :) The "filtering" capability is my biggest gripe on the Cisco *DSL products. They're just not as /capable/ as is offered in FBSD. DNS is another plus (pfDNS). But I don't think I'd be modify pfDNS to accomodate BIND, or unbound. Although tinydns might be able to fit the bill. Oh well, it's close - thanks for the pointer. :) --Chris Quoting Lawrence Farr : Have a look at pfsense, don't think it's what you want tho. -Original Message- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd- sta...@freebsd.org] On Behalf Of Chris H Sent: 29 January 2009 09:51 To: freebsd-stable@freebsd.org Subject: Replace Cisco IOS/CBOS with freebsd - possible? Greetings, I'm RP for a fairly large chunk of IP real estate. I carved out a /27 segment for my home network. Which is currently running over a cisco 837 GW (adsl/router). I'm not really keen on it (the router/modem). So I thought to myself that it couldn't be /that/ hard to build a box with FBSD that could replace it - am I crazy? Wouldn't it be possible to upload a minimal build of FBSD to the modem, not unlike one would tftp a new version of cisco's IOS, or CBOS? I searched the projects area to see if anyone had tried it. But the only thing that came anywhere near was netperf. But the only similarity is that it is network related. Anyway, this seems quite feasable as far as I can tell. So I thought I'd ask in hopes someone might enlighten me further. Maybe someones already tried it? Thank you for all your time and consideration in this matter. --Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable- unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Unhappy Xorg upgrade
,--- You/Bruce (Thu, 29 Jan 2009 12:06:45 +) * | One theory is that somehow the mouse driver ioctls which are passed | to ums, are somehow hosing USB, although why that would be, I don't | understand. ums currently doesn't have driver instrumentation in that path. | | I pulled a fairly detailed IRC log of my collaborative debugging | session with Robert, please ping me if you need details of this. `* Thank you for the detailed write up! No help to me, though -- on my Latitude laptop, there was no problem with any mouse: USB or the built-in "pointing device". It was the keyboard -- and, trust me, I did try many variations of the machine configuration, and I did do a lot of reading on various relevant topics (writing, too, as you have seen :-() As I mentioned elsewhere, my way of resolving the problem after a one-and-a-half day's of struggle was to revert to the old X (on that laptop). On the topic of how this upgrade was introduced, I can't help but refer to my recent experience helping to fix TWM: ,--- Eeri Kask (Mon, 29 Sep 2008 12:21:17 +0200) * | > I have used the new version of TWM for five days, using it less | > intensively than usual. No problems in seen during my (light) use. | | Hello Alex, no problem at all! Improved solutions have priority over | promised deadlines. | | Thank you for your time helping to improve TWM, :-) | `* Eeri Kask and I worked together all past September on fixing TWM crashes: I was willingly trying his multiple versions of the code, but I knew what I was risking, could choose convenient times for building and trying every new version (we tried about 30 of them) -- and I could always go back to the previous version (or the original TWM from ports). I would be happy to try a new X on my machines, if it were labeled as experimental, with an easy way to revert to the old X (while being in the testing stage). As it is, this upgrade brought a lot of problems to unsuspecting people, at the time they don't quite choose, with potential dangers not disclosed. In honesty, this upgrade should have been presented this way, way before the code was placed in the ports source tree: * We'll have a new X in ports soon -- there are multiple reports of problems with it on Linux. * We want to try it on FreeBSD -- but nobody is forcing you to do the upgrade. * If you, of your own free will, choose to upgrade, you may have hours and days of problems -- but heck, it was your choice. * If your problems cannot be fixed, you'll have to figure out something yourself. * If you choose not to upgrade, you are frozen with the pre-existing ports collection: there may be no automated ways to upgrade your packages, with the old X in place. Of course, you can somehow get pieces on new ports, unrelated to X. * The choice is totally yours. -- Alex -- alex-goncha...@comcast.net -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Unhappy Xorg upgrade
Alex Goncharov wrote: I hate to say this, but the new X (as exists in the current FreeBSD ports) sucks and gets in the way of work big time. There are definitely issues with xorg-7.4 at the moment. The root issue seems to be that USB mice simply don't work for me, and running Xorg appears to destabilise the 7-STABLE USB stack in some way which I just don't understand. The condition isn't recoverable without a reboot. I am the only person who's reported these symptoms in any great detail yet. I spent a lot of time yesterday debugging with rnoland@ the USB problem I've been having. He sent me a patch, however, it doesn't solve the problem. My understanding is that a lot has changed in this Xorg release to do with input drivers, specifically mouse -- and that platform specific code got shuffled off out of the server itself, and into the drivers. Good from an academic software engineering point of view, but if this is the cause, not good from a regression point of view. Whilst bisecting all the conditions, and tracing it back to this upgrade is easy to do, I can't readily identify the causal relationship -- I don't know what's going on which has broken Xorg for me in this way, and haven't seen anything like this before. Since upgrading, I've seen stability problems with hald enabled. I have had to turn off hald mode on both my laptop and desktop 7-STABLE machines, as it can totally hang the machine, no DDB break, etc. Scanning SVN, nothing appears to have changed in the 7-STABLE train in terms of USB, moused, the ums driver, or anything else. A ktrace of the moused process bound to ums0 goes dead (no I/O, no syscalls) after X is started. One theory is that somehow the mouse driver ioctls which are passed to ums, are somehow hosing USB, although why that would be, I don't understand. ums currently doesn't have driver instrumentation in that path. I pulled a fairly detailed IRC log of my collaborative debugging session with Robert, please ping me if you need details of this. thanks BMS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 7.1, mpt and slow writes
Charles Sprickman wrote: Hello, I think this needs a few more eyes: http://lists.freebsd.org/pipermail/freebsd-scsi/2009-January/003782.html In short, writes are slow, likely do to the write-cache being enabled on the controller. The sysctl used in 6.x to turn the cache off don't seem to be in 7.x. I have two Dell 860's here also running 7.1-REL. A simple dd on one shows roughly 60MB/s writes to a mirror of 2 320GB disks on what I'm assuming is the same LSI controller card (SAS5) rich...@moses:~# cat /boot/loader.conf hw.mpt.enable_sata_wc=1 Seems to work just fine for me. Regards, Richard smime.p7s Description: S/MIME Cryptographic Signature
Replace Cisco IOS/CBOS with freebsd - possible?
Greetings, I'm RP for a fairly large chunk of IP real estate. I carved out a /27 segment for my home network. Which is currently running over a cisco 837 GW (adsl/router). I'm not really keen on it (the router/modem). So I thought to myself that it couldn't be /that/ hard to build a box with FBSD that could replace it - am I crazy? Wouldn't it be possible to upload a minimal build of FBSD to the modem, not unlike one would tftp a new version of cisco's IOS, or CBOS? I searched the projects area to see if anyone had tried it. But the only thing that came anywhere near was netperf. But the only similarity is that it is network related. Anyway, this seems quite feasable as far as I can tell. So I thought I'd ask in hopes someone might enlighten me further. Maybe someones already tried it? Thank you for all your time and consideration in this matter. --Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: jail: external and localhost distinction
On Thu, 29 Jan 2009, Robert Watson wrote: RW> > am I right concluding that under FreeBSD jail there is no way to attach RW> > two processes to the same port of external interface address and RW> > localhost? RW> > RW> > I tried to move rather standard two-tier nginx(ip:80)+apache(127.1:80) RW> > scheme into a jail and on apache start got RW> > RW> > [Thu Jan 29 00:09:32 2009] [crit] (48)Address already in use: make_sock: RW> > could not bind to address 127.0.0.1 port 80 RW> > RW> > (this is under RELENG_7 if it's relevant) RW> > RW> > Any thoughts? Thanks in advance. RW> RW> The way Jail is implemented is that the jail IP is silently substituted for RW> the loopback IP is used. This has some downsides, and this is one of them. RW> The virtual network stack (VIMAGE) project for FreeBSD 8.0 is intended to RW> address this, among many other things, by providing full virtualization of RW> all network stack data structures for jails. Thank you for clarification, now I see this is actually expected behaviour :) Would then starting second jail with the same root and, say, 127.10.0.1 as an address be a workaround? -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
7.1, mpt and slow writes
Hello, I think this needs a few more eyes: http://lists.freebsd.org/pipermail/freebsd-scsi/2009-January/003782.html In short, writes are slow, likely do to the write-cache being enabled on the controller. The sysctl used in 6.x to turn the cache off don't seem to be in 7.x. Thanks, Charles ___ Charles Sprickman NetEng/SysAdmin Bway.net - New York's Best Internet - www.bway.net sp...@bway.net - 212.655.9344 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: jail: external and localhost distinction
On Thu, 29 Jan 2009, Dmitry Morozovsky wrote: am I right concluding that under FreeBSD jail there is no way to attach two processes to the same port of external interface address and localhost? I tried to move rather standard two-tier nginx(ip:80)+apache(127.1:80) scheme into a jail and on apache start got [Thu Jan 29 00:09:32 2009] [crit] (48)Address already in use: make_sock: could not bind to address 127.0.0.1 port 80 (this is under RELENG_7 if it's relevant) Any thoughts? Thanks in advance. The way Jail is implemented is that the jail IP is silently substituted for the loopback IP is used. This has some downsides, and this is one of them. The virtual network stack (VIMAGE) project for FreeBSD 8.0 is intended to address this, among many other things, by providing full virtualization of all network stack data structures for jails. Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS, NFS and Network tuning
On Wed, Jan 28, 2009 at 11:21 PM, Brent Jones wrote: > I'm reviving this, as I too am seeing something eerily similar. I have > made my own thread under freebsd-stable, so I will hopefully move that > discussion to this list. > > I believe we are seeing performance problems when the FreeBSD NFS > client issues FSYNC NFS instead of ASYNC, sending performance to a > mere percentage of what disks and network links are capable of. > Further testing tonight demonstrates that other NFSv3 and v4 clients > do not issue FSYNC unless they modify attributed and close a file, or > append and close a file. > FreeBSD NFS client will issue FSYNCs anytime the write size (-w) is > reached, instead of when just closing the file. > This is not necessary, since NFSv3 and v4 TCP have provisions for safe > async writes that 'guarantee' state of NFS writes. > > Here is the contents of what I wrote there verbatim: > > http://lists.freebsd.org/pipermail/freebsd-stable/2009-January/048063.html > > --- > > > Hello FreeBSD users, > I am running into some performance problems with NFSv3/v4 mounts. > I have a Sun X4540 running OpenSolaris 2008.11 with ZFS exporting NFS shares > The NFS clients are a FreeBSD 6.3 32 bit, quad core xeon with 4GB ram > and a FreeBSD 7.1 32bit with same hardware. > > The issue I am seeing, is that for certain file types, the FreeBSD NFS > client will either issue an ASYNC write, or an FSYNC. > However, NFSv3 and v4 both support "safe" ASYNC writes in the TCP > versions of the protocol, so that should be the default. > Issuing FSYNC's for every compete block transmitted adds substantial > overhead and slows everything down. > > The two test files I have that can reproduce this data are a file > created by 'dump' which is just binary data: > > $ file testbinery > testbinery: data > > ASCII text file from a Maildir format: > > $ file ascittest > ascittest: ASCII mail text > > My NFS mount command lines I have tried to get all data to ASYNC write: > > $ mount_nfs -3T -o async 192.168.0.19:/pdxfilu01/obsmtp /mnt/obsmtp/ > $ mount_nfs -3T 192.168.0.19:/pdxfilu01/obsmtp /mnt/obsmtp/ > $ mount_nfs -4TL 192.168.0.19:/pdxfilu01/obsmtp /mnt/obsmtp/ > > Here is an excerpt from a snoop from the binary data file: > > $ snoop rpc nfs > > obsmtp02.local -> pdxfilu01NFS C ACCESS3 FH=57D3 > (read,lookup,modify,extend,delete,execute) > pdxfilu01 -> obsmtp02.local NFS R ACCESS3 OK (read,modify,extend) > obsmtp02.local -> pdxfilu01NFS C LOOKUP3 FH=BB85 testbinery > pdxfilu01 -> obsmtp02.local NFS R LOOKUP3 OK FH=57D3 > obsmtp02.local -> pdxfilu01NFS C ACCESS3 FH=57D3 > (read,lookup,modify,extend,delete,execute) > pdxfilu01 -> obsmtp02.local NFS R ACCESS3 OK (read,modify,extend) > obsmtp02.local -> pdxfilu01NFS C SETATTR3 FH=57D3 > pdxfilu01 -> obsmtp02.local NFS R SETATTR3 OK > obsmtp02.local -> pdxfilu01NFS C WRITE3 FH=57D3 at 0 for 32768 (ASYNC) > pdxfilu01 -> obsmtp02.local NFS R WRITE3 OK 32768 (ASYNC) > obsmtp02.local -> pdxfilu01NFS C WRITE3 FH=57D3 at 582647808 for > 32768 (ASYNC) > pdxfilu01 -> obsmtp02.local NFS R WRITE3 OK 32768 (ASYNC) > obsmtp02.local -> pdxfilu01NFS C WRITE3 FH=57D3 at 592871424 for > 32768 (ASYNC) > pdxfilu01 -> obsmtp02.local NFS R WRITE3 OK 32768 (ASYNC) > obsmtp02.local -> pdxfilu01NFS C WRITE3 FH=57D3 at 605421568 for > 32768 (ASYNC) > pdxfilu01 -> obsmtp02.local NFS R WRITE3 OK 32768 (ASYNC) > > > And on and on.. it will acheive near full wire-speed, about 110MB/sec > during the copy > > > Here is the same snoop, only copying the ASCII mail file: > > $ snoop rpc nfs > > obsmtp02.local -> pdxfilu01NFS C LOOKUP3 FH=BB85 ascittest > pdxfilu01 -> obsmtp02.local NFS R LOOKUP3 No such file or directory > obsmtp02.local -> pdxfilu01NFS C LOOKUP3 FH=BB85 ascittest > pdxfilu01 -> obsmtp02.local NFS R LOOKUP3 No such file or directory > obsmtp02.local -> pdxfilu01NFS C CREATE3 FH=BB85 (UNCHECKED) ascittest > pdxfilu01 -> obsmtp02.local NFS R CREATE3 OK FH=69D3 > obsmtp02.local -> pdxfilu01NFS C WRITE3 FH=69D3 at 0 for 32768 (FSYNC) > pdxfilu01 -> obsmtp02.local NFS R WRITE3 OK 32768 (FSYNC) > obsmtp02.local -> pdxfilu01NFS C WRITE3 FH=69D3 at 32768 for 32768 (FSYNC) > pdxfilu01 -> obsmtp02.local NFS R WRITE3 OK 32768 (FSYNC) > obsmtp02.local -> pdxfilu01NFS C WRITE3 FH=69D3 at 65536 for 32768 (FSYNC) > pdxfilu01 -> obsmtp02.local NFS R WRITE3 OK 32768 (FSYNC) > > > And so on. I've reproduced this with several files, and the only > difference between tests is the file type. > Is the FreeBSD NFS client requesting FSYNC or ASYNC depending on the > file type/contents? > If so, is there a tuneable setting to make all write ASYNC? > Otherwise, FSYNC'ing for every block written over NFS will cause so > many IOPS on the NFS server, that performance will degrade severely. > > Testing with an OpenSolaris 2008.11 client will issue ASYNC writes for > any file type, if mounted with NFSv3 of NFSv4 (TCP). > > Any ideas? > > Tha
reminder: bugathon upcoming this weekend
Starting this Friday, we are going to hold a bugathon to work through some of the network-related PRs. More details, and a list of resources, are available at http://wiki.freebsd.org/Bugathons/January2009. I have come up with a page that details a subset of those PRs as a set of suggested PRs: http://people.freebsd.org/~linimon/annotated_prs_bugathon.html Please join us to work through some PRs. Thanks! mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
