RE: /dev/cuau* ports hang after a while
Hi, With 'hang' I mean the stop of the data flow. There's a measurement device connected to the serial port, which sends every minute data to our computer. The line is never closed but after a while data is no longer received. Tried already building kernel without uart, and the ports really came out as sio's, but the devicefile numbering was still odd, now they were /dev/cuad0-3, the cuad0 used to be the motherboard-serialport devicefile (is now /dev/cuad4) and for this reason (perhaps?) cuad0 does not work. Hardware is identical, only changed thing is the BSD-version. Regards, Timo -Original Message- From: Ulrich Spörlein [mailto:uspoerl...@gmail.com] Sent: 29. tammikuuta 2009 22:24 To: Timo Rikkonen Cc: freebsd-stable@freebsd.org; Ed Schouten; Marcel Moolenaar Subject: 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"
Puzzling change in performance
Hello, The attached graphs are from a server running FreeBSD 7.1-i386 (now) with the typical Apache2+MySQL with forums, Joomla... I just cannot explain this. Disk I/O bandwidth was suffering a lot, and after the update the disks are almost idle. Any ideas? I cannot imagine a change between versions to justify this. The latest update to 7-STABLE had been done in August. Maybe it was just degradation due to not being rebooted since August? But it's strange anyway, and I had restarted MySQL and Apache some times during this period. ___ 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
Hi list, after upgrading to Xorg 7.4 from the FreebSD ports tree I've got my USB stack completely unusable. If Xorg is started (manually or via xdm) my USB printer and external HDD become unreachable (timeouts). It is not enough to kill Xorg to restore the USB functionality. FreeBSD has to be restarted. I use FreeBSD 7.1-STABLE (amd64) compiled from fresh sources. Any tips? Regards, Serguey. ___ 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
Am 30.01.2009 um 10:16 schrieb S.N.Grigoriev: after upgrading to Xorg 7.4 from the FreebSD ports tree I've got my USB stack completely unusable. If Xorg is started (manually or via xdm) my USB printer and external HDD become unreachable (timeouts). It is not enough to kill Xorg to restore the USB functionality. FreeBSD has to be restarted. I use FreeBSD 7.1-STABLE (amd64) compiled from fresh sources. Any tips? One way is to look for patches in the PR database and simply try them, for example: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/130957 (shameless plug) This could help you and, if you find something helpful, add a chance to get a PR fixed. MarKus - - - - - - - - - - - - - - - - - - - Dipl. Ing. Markus Hitter http://www.jump-ing.de/ ___ 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: Puzzling change in performance
On Jan 30, 2009, at 10:12 AM, Borja Marcos wrote: Hello, The attached graphs are from a server running FreeBSD 7.1-i386 (now) with the typical Apache2+MySQL with forums, Joomla... I see that the attachments didn't make it. Disk I/O bandwidth was an average 40 - 60 % before the update and reboot. After the update and reboot it's now less than 10 %. Most of the I/O activity was on the /var filesystem. It houses the MySQL database and system logs, mostly. So, either: 1- there's an important improvement on file caching from 7.0-STABLE- August to 7.1-RELEASE? 2- Something was rotten since the last reboot in August 3- Something was malfunctioning in the "amr" array controller? (It's a Dell server, and it has two hard disks in mirror) Apache and MySQL had been restarted some times last week, trying to tune some parameters and it made no difference. Any ideas? It's quite weird. Same kernel configuration, same hardware... Borja. ___ 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
Hi, The speed is 9600. Actually I already tried with 7.1-RELEASE, with same results. I'll try the device.hints-changes, thanks. -Timo -Original Message- From: Mike Tancsa [mailto:m...@sentex.net] Sent: 29. tammikuuta 2009 22:34 To: Timo Rikkonen; freebsd-stable@freebsd.org Subject: 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: Replace Cisco IOS/CBOS with freebsd - possible?
Chris H wrote: ... 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). IMHO pfSense beats the pants off OpenWRT from a user/deployment point of view, and often that is ultimately what counts. Thing is, it's "only" for x86-based PCs. I had the foresight to purchase some relatively quiet 1U boxes, but they're still too noisy to have in a room where people sleep live or socialise -- they belong to the computer nook at the front of the apartment (I have a very odd C-shaped apartment). I believe something that could really make pfSense fly, would be a viable port to mass-market, low-power consumer hardware. Then again, old Ciscos "sort of" fit the bill. Repurposing old vendor hardware is just as subject to engineering process as anything else, in some cases, the varying Bill-of-Materials may make the economic cost too high to do things on a mass scale. If people would be reasonably expected to use such a system, they should not have to understand the mechanisms, in great detail, of how firmware is loaded onto a device. This is one of the main stumbling blocks behind mass uptake -- we can't just say "fire up this tool and click this 1 button" to extend/build new network infrastructure. Given the current economic and ecological situation, though, devising systems which allow people to do this might be something worth investigating, and funding to that effect may be available "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: /dev/cuau* ports hang after a while
At 05:50 AM 1/30/2009, Timo Rikkonen wrote: Hi, The speed is 9600. Actually I already tried with 7.1-RELEASE, with same results. I'll try the device.hints-changes, thanks. Not sure if the code is in 7.0, so make sure you try it with 7.1-RELEASE ---Mike -Timo -Original Message- From: Mike Tancsa [mailto:m...@sentex.net] Sent: 29. tammikuuta 2009 22:34 To: Timo Rikkonen; freebsd-stable@freebsd.org Subject: 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: Unhappy Xorg upgrade
30.01.09, 12:59, "Markus Hitter" : > Am 30.01.2009 um 10:16 schrieb S.N.Grigoriev: > > after upgrading to Xorg 7.4 from the FreebSD ports tree > > I've got my USB stack completely unusable. If Xorg is started > > (manually or via xdm) my USB printer and external HDD become > > unreachable (timeouts). It is not enough to kill Xorg to restore > > the USB functionality. FreeBSD has to be restarted. > > I use FreeBSD 7.1-STABLE (amd64) compiled from fresh sources. > > Any tips? > One way is to look for patches in the PR database and simply try > them, for example: > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/130957 (shameless > plug) > This could help you and, if you find something helpful, add a chance > to get a PR fixed. Markus, I thank you for your response. I've applied the patch to pci.c from kern/130957. Unfortunately there are no positive results. USB is still unreachable with X. Regards, Serguey. ___ 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
I have to agree with you that this latest update was most problematic for me. I keep my system very up-to-date, usually every 3-5 days. FreeBSD 7.1 RELENG (Which is stable at the moment) on Toshiba X200-AX1 Two major problems both noted in UPDATING but still cause of a huge number of problems were my xorg conf file settings (had to make several changes to x11 config to get X to start and mouse to move besides the ones noted in UPDATNG), my start is still riddled with errors. One problem is that i'm using amd64 but have an nVidia card. My laptop has dual cards for driving the single screen, and this no longer works - now card(0) is driving both sides of the screen, and card(1) is unloaded. There are a number of other problems related to video that i'm not very worried about, i only have an interest in one game - and i play it about once every 6 months at most. (flightgear) bigger problem with libxcb, first - i don't have portsupdate installed, only portmaster. now - the fist confession is that i had no idea what libxcb is, or why i might need it, so i just ignored that bit of UPDATING. After portmaster -a failed with a reference to libxcb and i rebuilt 5 or 6 ports manually to get past that, then rescanned UPDATING for libscb, i tried: portmaster -rf libxcb that ran overnight, and didn't do a single scrap of good. finally - i installed and ran libchk -V /list of folders/ (most problems identified in /usr/local ) recommend piping that into a log so you can search throught it for libxcb dependent ports - my output is huge, and i had to keep pausing and writing down ports as fast as my little fingers could move. on a lof of folders, to discover that a whole list of programs were all linked to libxcb.so.1 including metacity, nautilus, cups, policykit, etc. that didn't get updated by -rf libxcb, i started with metacity; portmaster metacity portmaster cups* portmaster policykit etc... and worked throgh the list of about 25 ports. startx finally works but i still had no windows manager (metacity) which i had to rebuild again to make it finally work. Now i have a working system, but there is still no Gnome-splash-screen. so far everything else is working, but it's taken me a good 24 hours to make my X system usable. ken. On Thu, 29 Jan 2009 Robert Noland wrote > 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" > > > > > > > ___ 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" : Chris H wrote: ... 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). IMHO pfSense beats the pants off OpenWRT from a user/deployment point of view, and often that is ultimately what counts. I guess I'd have to agree, except if it weren't for the fact I always have a zillion things going simultaneously, I wouldn't even know what X was - I can't get enough VC's (virtual consoles), so I'm forced to use X. But, of course for most "end users" /convenience/ is everything, and most don't want to any more that how to turn it on. :) Thing is, it's "only" for x86-based PCs. I had the foresight to purchase some relatively quiet 1U boxes, but they're still too noisy to have in a room where people sleep live or socialise -- they belong to the computer nook at the front of the apartment (I have a very odd C-shaped apartment). Yes, the (older) cisco's CPU's were MIPS - aka - Motorola, and ran AUX. I've got the latest version of AUX, which is a newer version than they ran. In fact, it wouldn't be a bit surprised if I could load AIX on it. I believe something that could really make pfSense fly, would be a viable port to mass-market, low-power consumer hardware. Then again, old Ciscos "sort of" fit the bill. Funny you bring that up. I was thinking the very same. As a matter of fact I have been contemplating whipping something up myself, and doing just that. While psSense initially seems appealing. The more I look into it, the more I find it's laking - where a simple roll-out is concerned. There isn't anything in the way of documentation. What's there is /horribly/ unorganized. It's scattered all over the place. What's more, the front page of the wiki suggests that reading the m0n0wall documentation would probabl;y be a better choice. Make no mistake, I know how daunting and hectic an opensource project can be, and am grateful to /anyone/ whom is willing to share the fruits of their labor at no cost. But I think I could do better, that's all. Repurposing old vendor hardware is just as subject to engineering process as anything else, in some cases, the varying Bill-of-Materials may make the economic cost too high to do things on a mass scale. I think I have a solution for that. I'll elaborate further when I can confirm that. If people would be reasonably expected to use such a system, they should not have to understand the mechanisms, in great detail, of how firmware is loaded onto a device. This is one of the main stumbling blocks behind mass uptake -- we can't just say "fire up this tool and click this 1 button" to extend/build new network infrastructure. Given the current economic and ecological situation, though, devising systems which allow people to do this might be something worth investigating, and funding to that effect may be available "out there". I /quite/ agree, and intend to persue just that. I've already commissioned the artwork - and it looks GREAT. :) I'll elaborate further as things firm up. Thanks again Bruce, for taking the time to respond. --Chris 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?
Chris H presented these words - circa 1/30/09 7:03 AM-> Hello Bruce, and thank you for your reply. Quoting "Bruce M. Simpson" : Chris H wrote: ... 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). IMHO pfSense beats the pants off OpenWRT from a user/deployment point of view, and often that is ultimately what counts. I guess I'd have to agree, except if it weren't for the fact I always have a zillion things going simultaneously, I wouldn't even know what X was - I can't get enough VC's (virtual consoles), so I'm forced to use X. But, of course for most "end users" /convenience/ is everything, and most don't want to any more that how to turn it on. :) Thing is, it's "only" for x86-based PCs. I had the foresight to purchase some relatively quiet 1U boxes, but they're still too noisy to have in a room where people sleep live or socialise -- they belong to the computer nook at the front of the apartment (I have a very odd C-shaped apartment). Yes, the (older) cisco's CPU's were MIPS - aka - Motorola, and ran AUX. I've got the latest version of AUX, which is a newer version than they ran. In fact, it wouldn't be a bit surprised if I could load AIX on it. Yes, most of the core CPU's used by Cisco were MIPS, however, they were not made by Motorola and didn't run AUX (if by AUX you mean Apples Unix OS). Instead they ran Cisco's own IOS kernel/software. Patrick Mahan I believe something that could really make pfSense fly, would be a viable port to mass-market, low-power consumer hardware. Then again, old Ciscos "sort of" fit the bill. Funny you bring that up. I was thinking the very same. As a matter of fact I have been contemplating whipping something up myself, and doing just that. While psSense initially seems appealing. The more I look into it, the more I find it's laking - where a simple roll-out is concerned. There isn't anything in the way of documentation. What's there is /horribly/ unorganized. It's scattered all over the place. What's more, the front page of the wiki suggests that reading the m0n0wall documentation would probabl;y be a better choice. Make no mistake, I know how daunting and hectic an opensource project can be, and am grateful to /anyone/ whom is willing to share the fruits of their labor at no cost. But I think I could do better, that's all. Repurposing old vendor hardware is just as subject to engineering process as anything else, in some cases, the varying Bill-of-Materials may make the economic cost too high to do things on a mass scale. I think I have a solution for that. I'll elaborate further when I can confirm that. If people would be reasonably expected to use such a system, they should not have to understand the mechanisms, in great detail, of how firmware is loaded onto a device. This is one of the main stumbling blocks behind mass uptake -- we can't just say "fire up this tool and click this 1 button" to extend/build new network infrastructure. Given the current economic and ecological situation, though, devising systems which allow people to do this might be something worth investigating, and funding to that effect may be available "out there". I /quite/ agree, and intend to persue just that. I've already commissioned the artwork - and it looks GREAT. :) I'll elaborate further as things firm up. Thanks again Bruce, for taking the time to respond. --Chris 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" ___ 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
As a general note, this is the second time in a row that an X.org upgrade broke X for a significant number of people. IMO, this suggests that our approach to X.org upgrades needs significant changes (see below). X11 is a critical component for anyone who is using FreeBSD as a desktop and having upgrades fail or come with significant POLA violations and regressions for significant numbers of people is not acceptable. On 2009-Jan-29 08:40:11 -0500, Robert Noland wrote: >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. I didn't recall seeing any reference to patches so I went looking. All I could find is a couple of references to a patchset existing buried inside threads discussing specific problems with X. The majority of people who didn't have those specific problems probably skipped the thread and never saw that a patchset was available. When the X.org 7.0 upgrade was planned, a heads-up went out on a number of mailing lists, together with a pointer to the patchset and upgrade instructions and the upgrade did not proceed until both a reasonable number of people reported success and reported problems had been ironed out. Given the ongoing problems with code provided by X.org, I suggest that this approach needs to be followed for every future release of X.org until (if) the X.org Project demonstrates that they can provide release-quality code. > This update also brings in support for a >lot of people who are running newer hardware. And breaks support for lots of people who used to have functional X servers. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. pgpAB3vRB9EJK.pgp Description: PGP signature
Re: Unhappy Xorg upgrade
On Sat, Jan 31, 2009 at 06:53:11AM +1100, Peter Jeremy wrote: > As a general note, this is the second time in a row that an X.org > upgrade broke X for a significant number of people. IMO, this > suggests that our approach to X.org upgrades needs significant changes > (see below). X11 is a critical component for anyone who is using > FreeBSD as a desktop and having upgrades fail or come with significant > POLA violations and regressions for significant numbers of people is > not acceptable. > > On 2009-Jan-29 08:40:11 -0500, Robert Noland wrote: > >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. > > I didn't recall seeing any reference to patches so I went looking. > All I could find is a couple of references to a patchset existing > buried inside threads discussing specific problems with X. The > majority of people who didn't have those specific problems probably > skipped the thread and never saw that a patchset was available. > > When the X.org 7.0 upgrade was planned, a heads-up went out on a > number of mailing lists, together with a pointer to the patchset and > upgrade instructions and the upgrade did not proceed until both a > reasonable number of people reported success and reported problems had > been ironed out. Given the ongoing problems with code provided by > X.org, I suggest that this approach needs to be followed for every > future release of X.org until (if) the X.org Project demonstrates that > they can provide release-quality code. > > > This update also brings in support for a > >lot of people who are running newer hardware. > > And breaks support for lots of people who used to have functional > X servers. Just to give a different view on *this* update. I have exactly opposing experience. Both my workstations (job/home) have different kinds of Radeons, during the time from R200 to R600. X server 1.4.x was a complete disaster; I had to turn off dri to get rid of the constant hangs caused by X server looping somewhere in kernel. Robert' attempts to diagnose the cause of the issue, including consultation with upstream developers resulted in nothing. Moreover, at work I have two panels connected to Radeon; xrandr became absolutely impossible to configure without DRI. In contrast, 1.5.3 upgraded and I observed two issues, one was the Xorg sleeping in "ttyin", that was promptly fixed. Second was actually pretty good documented in updating, and it was my fault to not follow advise about recompiling libxcb dependencies. The libxcb issue is easily diagnosted by any user, BTW, using ldd XXX | grep compat. So far 1.5.3 + updated DRM works good on all my Radeons. And, I did not have a problem with i945GM on 1.4.2 and 1.5.3. pgpUdADWoAUHl.pgp Description: PGP signature
Re: Unhappy Xorg upgrade
,--- You/Peter (Sat, 31 Jan 2009 06:53:11 +1100) * | X11 is a critical component for anyone who is using FreeBSD as a | desktop and having upgrades fail or come with significant POLA | violations and regressions for significant numbers of people is not | acceptable. Fully agree with this. | I suggest that this approach needs to be followed for every future | release of X.org until (if) the X.org Project demonstrates that they | can provide release-quality code. And agree with this, as far as the future is concerned -- but this leaves out the issue of what is going to be done for people whose systems became practically incapacitated in a matter of one day. Screw us? I realize that personally I haven't contributed much (hey, a simple port's maintainer!) to FreeBSD, so a disregard to my situation may be well deserved. But "you" (whoever this "you" is: the "ports manager", the X port maintainers) have to be aware that leaving the things in the state they are now, you are screwing somebody. | > This update also brings in support for a lot of people who are | >running newer hardware. | | And breaks support for lots of people who used to have functional X | servers. Just so. ,--- Kostik Belousov (Fri, 30 Jan 2009 22:25:09 +0200) * | Just to give a different view on *this* update. I have exactly opposing | experience. | | So far 1.5.3 + updated DRM works good on all my Radeons. | And, I did not have a problem with i945GM on 1.4.2 and 1.5.3. `--* Well, glad for you -- meanwhile I will be reverting my desktop to the old X this weekend: the garbage on the screen is ugly, but the fact that in the new X "opera" can grab a pointer for about a minute makes the combined use of the browser and xterms/Emacses plain intolerable. After I do this, as I did with my laptop already, I think I am completely cut off from the ports automated upgrade cycle. -- 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?
On Thu, 29 Jan 2009 01:50:34 -0800 Chris H wrote: > 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 On topic: shouldn't this discussion be on another mailing list? For eaxmple -questions or -net, or even -arch? -- Regards, Torfinn Ingolfsen, Norway ___ 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: Puzzling change in performance
On Fri, 30 Jan 2009 11:50:05 +0100 Borja Marcos wrote: > I see that the attachments didn't make it. Well, it would be quite easy for you to just put them on the web somewhere and then link to them, perhaps? > 1- there's an important improvement on file caching from 7.0-STABLE- > August to 7.1-RELEASE? Have you checked the release notes for 7.1? Perhaps they contain clues that explain the performace improvements? HTH -- Regards, Torfinn Ingolfsen ___ 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
On Thu, Jan 29, 2009 at 3:02 PM, Alfred Perlstein wrote:
> 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?
I tested with a 6MB text file, and a 2GB binary file. Text file would
go ~1MB/sec, issuing FSYNCs for every block write size (32KB default)
One thing I found that another FreeBSD user discovered exactly
explains my situation:
In bin/cp/utils.c (source) there is a check, if the file is less than
8MB or so, it uses mmap, if the file is larger, it will use write()
I modified the source and recompiled to -never- use mmap, only to use
write(), and my performance increased about 100 fold (from 1MB/sec
over NFS, to over 100MB/sec).
Changed line 143:
original:
fs->st_size <= 8 * 1048576) {
New:
fs->st_size <= 8 * 8) {
It will use mmap still if the file is larger than 64bytes (if it uses
bytes there, pretty sure it does).
But is much faster for files ~1KB to 8MB now.
Regards
> 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
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"
Re: Replace Cisco IOS/CBOS with freebsd - possible?
Hello Patrick, and thank you for your reply. Quoting Patrick Mahan : Chris H presented these words - circa 1/30/09 7:03 AM-> Hello Bruce, and thank you for your reply. Quoting "Bruce M. Simpson" : Chris H wrote: ... 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). IMHO pfSense beats the pants off OpenWRT from a user/deployment point of view, and often that is ultimately what counts. I guess I'd have to agree, except if it weren't for the fact I always have a zillion things going simultaneously, I wouldn't even know what X was - I can't get enough VC's (virtual consoles), so I'm forced to use X. But, of course for most "end users" /convenience/ is everything, and most don't want to any more that how to turn it on. :) Thing is, it's "only" for x86-based PCs. I had the foresight to purchase some relatively quiet 1U boxes, but they're still too noisy to have in a room where people sleep live or socialise -- they belong to the computer nook at the front of the apartment (I have a very odd C-shaped apartment). Yes, the (older) cisco's CPU's were MIPS - aka - Motorola, and ran AUX. I've got the latest version of AUX, which is a newer version than they ran. In fact, it wouldn't be a bit surprised if I could load AIX on it. Yes, most of the core CPU's used by Cisco were MIPS, however, they were not made by Motorola Please take no offense. But as I look inside, the CPU does, in fact say Motorola. The documentation for it also confirms that most of (if not all) of the 800 series also used the Motorola RISC. and didn't run AUX (if by AUX you mean Apples Unix OS). I probably stand corrected on this. :) But I'll bet - given the CPU, it wouldn't be much of a streatch to run either AUX, or AIX on it. Thanks again for your response. --Chris Instead they ran Cisco's own IOS kernel/software. Patrick Mahan I believe something that could really make pfSense fly, would be a viable port to mass-market, low-power consumer hardware. Then again, old Ciscos "sort of" fit the bill. Funny you bring that up. I was thinking the very same. As a matter of fact I have been contemplating whipping something up myself, and doing just that. While psSense initially seems appealing. The more I look into it, the more I find it's laking - where a simple roll-out is concerned. There isn't anything in the way of documentation. What's there is /horribly/ unorganized. It's scattered all over the place. What's more, the front page of the wiki suggests that reading the m0n0wall documentation would probabl;y be a better choice. Make no mistake, I know how daunting and hectic an opensource project can be, and am grateful to /anyone/ whom is willing to share the fruits of their labor at no cost. But I think I could do better, that's all. Repurposing old vendor hardware is just as subject to engineering process as anything else, in some cases, the varying Bill-of-Materials may make the economic cost too high to do things on a mass scale. I think I have a solution for that. I'll elaborate further when I can confirm that. If people would be reasonably expected to use such a system, they should not have to understand the mechanisms, in great detail, of how firmware is loaded onto a device. This is one of the main stumbling blocks behind mass uptake -- we can't just say "fire up this tool and click this 1 button" to extend/build new network infrastructure. Given the current economic and ecological situation, though, devising systems which allow people to do this might be something worth investigating, and funding to that effect may be available "out there". I /quite/ agree, and intend to persue just that. I've already commissioned the artwork - and it looks GREAT. :) I'll elaborate further as things firm up. Thanks again Bruce, for taking the time to respond. --Chris 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" ___ 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-stab
Re: Unhappy Xorg upgrade
S.N.Grigoriev wrote: I thank you for your response. I've applied the patch to pci.c from kern/130957. Unfortunately there are no positive results. USB is still unreachable with X. Just following up to confirm that you are seeing exactly the same symptoms with USB and Xorg 7.4 as I see on my amd64 desktop running 7-STABLE from 00:00 UTC on this Wednesday. 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: Replace Cisco IOS/CBOS with freebsd - possible?
On Fri, 30 Jan 2009, Chris H wrote: Please take no offense. But as I look inside, the CPU does, in fact say Motorola. The documentation for it also confirms that most of (if not all) of the 800 series also used the Motorola RISC. Cisco's used several CPU architectures in their IOS routers over the years. The very very earliest routers used Motorola m68K processors. Later high-end routers used MIPS processors from various vendors (like Broadcom and IDT, but never Motorola). Most of their models from the last decade, including the entire 800 series, are Motorola/Freescale PowerPC based. You can see that by running "show version" at the Cisco's command prompt; it'll probably say it's got a MPC85x or MPC86x PowerQUICC in it. What are you trying to do that the Cisco can't do, anyway? (reply off-list to that maybe) It might just be a matter of getting a different feature set on the thing... IOS can do a LOT of really weird stuff. :) ___ 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?
On Jan 29, 2009, at 1: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 Good luck on that. Probably not to be honest because Cisco does a great deal of corporate IP protection on their images, etc. I know because I work for Cisco :). All I can really say (based on my little knowledge) is that it's no doubt a PPC based embedded processor, so if you need to look further, I'd first explore and PPC ports to that specific chipset, and definitely make sure to check with the NetBSD folks and see if anyone has ported to that platform. Cheers, -Garrett ___ 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 Fri, 30 Jan 2009, Gary Palmer wrote: 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 ..." Cool, it works then. Why was the info removed from the sysctl mib? mpt0: Enabling SATA WC on phy 0 mpt0: Enabling SATA WC on phy 1 Bonnie++ is showing me about 24MB/s writes and 70MB/s reads. Is any of this verbose stuff problematic? mpt0: No Handlers For Any Event Notify Frames. Event 0xa (ACK not required). mpt0: No Handlers For Any Event Notify Frames. Event 0x16 (ACK not required). mpt0: No Handlers For Any Event Notify Frames. Event 0x12 (ACK not required). mpt0: No Handlers For Any Event Notify Frames. Event 0x12 (ACK not required). mpt0: No Handlers For Any Event Notify Frames. Event 0x16 (ACK not required). mpt0: No Handlers For Any Event Notify Frames. Event 0xb (ACK not required). And is any of this info found at boot-time accessible while the system is running? mpt0:vol0(mpt0:0:0): Settings ( Hot-Plug-Spares High-Priority-ReSync ) mpt0:vol0(mpt0:0:0): Using Spare Pool: 0 mpt0:vol0(mpt0:0:0): 2 Members: (mpt0:1:32:0): Primary Online (mpt0:1:1:0): Secondary Online mpt0:vol0(mpt0:0:0): RAID-1 - Optimal mpt0:vol0(mpt0:0:0): Status ( Enabled ) (mpt0:vol0:1): Physical (mpt0:0:1:0), Pass-thru (mpt0:1:0:0) (mpt0:vol0:1): Online (mpt0:vol0:0): Physical (mpt0:0:32:0), Pass-thru (mpt0:1:1:0) (mpt0:vol0:0): Online Thanks, Charles ps - would it kill Dell to make a damn ISO of a bootable media for RAID controller firmware upgrades??? I don't even own anything with a floppy drive anymore. 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" ___ 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"
