Re: stable/10: high load average when box is idle
On Tue, Nov 3, 2015 at 5:47 PM, Ian Smith wrote: > Like yourself, I think this is far from 'cosmetic' as is oft suggested, > especially in some fairly ill-informed forum posts but also various list > posts. I've been watching load averages since OS/2 through FreeBSD 2.2 > till present and some Linux systems, and have never before seen anything > like this, especially on virtually entirely idle systems. While the LAs > reported during (say) make -j4 buildworld appear more same, who knows? > > I'm not suggesting that I think there's any sort of performance hit from > this; so far I don't, but 'cosmetic' suggests that it doesn't matter .. > Have you read mav's explanation on the PR? It certainly seems a valid explanation of why it is probably a cosmetic issue - that is, we could wake up more to get a truly perfect load average, but why bother? ISTM, the problem reports are of the form "My server is idle and it is reporting a non-idle load average below 1", and not "My server is supposedly idle, but is doing actual work causing the load average to be higher than it should be". Is there any evidence that we have the latter and not the former? Cheers Tom ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: There has to be a better way of merging /etc during a major freebsd-update
On Tue, Mar 10, 2015 at 1:58 PM, Chris H wrote: > Hello, Peter. > This has probably been answered by now. But just in case. > I believe what you're looking for is: > mergemaster -vF > > This is my [chosen] default. I also find it helpful, > as a "safety net" to > cp _Rp /etc /eetc > > prior to the mergemaster(8) step. I use these steps after new kernel boots OK with old world: zfs set readonly=off zroot zfs mount -a adjkerntz -i mergemaster -piF cd /usr/src make installworld mergemaster -iFPU make delete-old I get very few questions asked of me by mergemaster. Cheers Tom ___ 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: Bind in FreeBSD, security advisories
On Tue, Jul 30, 2013 at 8:55 AM, David Demelier wrote: > Hi, > > For years, a lot of security advisories have been present for bind. > I'm just guessing if it's not a good idea to remove bind from base? > > This will probably free by half the number of FreeBSD SA's in the future. > Sure, but no bind in base also implies no dig, nslookup or host. Cheers Tom ___ 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: Where's the docs for FreeBSD maintenance with Subversion?
On Thu, Jul 4, 2013 at 4:31 PM, Fabian Wenk wrote: > If there is an easier solution to > upgrade an existing svn checkout from e.g. 8.4 to 8.5, please tell me. cd /usr/src ; svn switch http://svn.freebsd.org/base/releng/8.5 Cheers Tom ___ 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: zpool labelclear destroys GPT data
On Fri, Jun 14, 2013 at 4:49 PM, John Baldwin wrote: > Well, you could have zpool check if there is a valid ZFS label and prompt/warn > if it doesn't find one on whatever device it's about to wipe. That doesn't > fix the gmirror/gpt case, but it might make zpool more intuitive to use. One of the uses of zpool labelclear is to completely wipe the portions of the disk that ZFS will look at for label information. There is no pre-condition, the post-condition is that the label areas of the supplied device will be cleared. The aim of the command is that the relevant parts of the device are cleared, regardless of its content, such that they are ready to use as pristine disks in a vdev. I suppose if labelclear was made to check for the existence of a pre-existing ZFS label, the force flag could be used to force the change… I still don't like it, the command is not called labelclear-only-if-the-label-area-already-has-sane-data. Cheers Tom ___ 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: How to get pkgng work through a proxy?
On Tue, May 14, 2013 at 3:58 PM, Lars Engels wrote: > On Tue, May 14, 2013 at 12:36:44PM +0200, Rainer Duffner wrote: >> Hi, >> >> I have this host (a cloned VM, FreeBSD 9.1 AMD64) behind an Astaro >> Web-Proxy: >> >> >> (blahost ) 70 # pkg >> update >> [12:00] Updating repository catalogue >> repo.txz3% >> 10KB 0.5KB/s 0.0KB/s - stalled -pkg: >> http://pkgng.our.repo/91amd64-91patch/repo.txz: Operation timed out >> >> >> It's a proxy with authentication. >> >> I'm not sure if it's a fetch(3) problem in general. >> Because a single fetch from the same server of a small and large file >> does work, though a bit slow. >> >> pkg is 1.0.2 > > It's working here with these env vars set: > > http_proxy=http://:@:8080 > ftp_proxy=http://:@:8080 > HTTP_PROXY=http://:@:8080 > FTP_PROXY=http://:@:8080 > HTTP_PROXY_AUTH=basic:*:: > > > But I can't tell which one get's pulled in. My work require proxy authentication also, with the annoying requirement that the username is my email address, which ultimately means that I cannot insert username/pass into http_proxy or variants. libfetch is smart enough to pull these out of HTTP_PROXY_AUTH, but very few other applications are. Eventually, I gave up trying to convince all these disparate applications to discover my proxy auth, and instead I set up a local copy of squid on my laptop, which I point at my upstream proxy and provide with authentication details. I can then use this unauthenticated proxy on localhost to access my corporate proxy fully authenticated. It's a bit of hassle in the short term, but all proxy setup becomes much simpler with it in place. IIRC, the only lines I added to squid.conf's defaults were these: http_port 127.0.0.1:3128 cache_peer parent 3128 0 proxy-only default login=: Cheers Tom ___ 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: recommended memory for zfs
On Thu, May 9, 2013 at 2:18 PM, Benjamin Adams wrote: > Hello zfs question about memory. > I heard zfs is very ram hungry. > Service looking to run: > - nginx > - postgres > - php-fpm > - python > > I have a machine with two quad core cpus but only 4 G Memory > > I'm looking to buy more ram now. > What would be the recommend amount of memory for zfs across 6 drives on this > setup? > There is no right answer to this question. ZFS does not use a lot of RAM, but it will use as much as you allow as cache (in the ARC). How much data is your working set? How much of your working set do you need to keep in cache? You need that much memory (plus whatever to run your applications). > > Also can 9.1 now boot to zfs from the installer? > (no tricks for post install) > Can you clarify? The installer still cannot setup zfs pools, you must do so manually (but then can return to the installer). Cheers Tom ___ 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: buildworld fails for stable/9
On Fri, Apr 26, 2013 at 12:52 PM, Rick Miller wrote: > Hi all, > > I checked out stable/9 this morning to generate a release. buildworld > fails with the following: > > /usr/src/lib/libc/gen/stringlist.c:108: error: conflicting types for > 'sl_find' > /usr/src/lib/libc/../../include/stringlist.h:54: error: previous > declaration of 'sl_find' was here > *** [stringlist.o] Error code 1 > > Stop in /usr/src/lib/libc. > *** [lib/libc__L] Error code 1 > > Stop in /usr/src. > *** [libraries] Error code 1 > > Stop in /usr/src. > *** [_libraries] Error code 1 > > Stop in /usr/src. > *** [buildworld] Error code 1 > > Stop in /usr/src. > > > Is this an indication of conflicting libraries? > This was the result of a bad MFC, Glen Barber just mailed the list to say he has corrected this so perhaps up and try again. Cheers Tom ___ 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: ada(4) and ahci(4) quirk printing
On Tue, Apr 23, 2013 at 1:51 PM, Jeremy Chadwick wrote: > On Tue, Apr 23, 2013 at 01:20:31PM +0100, Steven Hartland wrote: >> >4) camcontrol wouldn't address the need/interest for ahci(4) quirks to >> >be made available. >> >> Why? > > Because camcontrol is for CAM. ahci(4) is not part of CAM. The last > place I'd look for "poking at AHCI" (as in *actual AHCI*) is camcontrol. > > This is one of the reasons sysctl exists -- it's a sort of "covers > everything" tree, on a per-device basis. Just on this point, these quirks aren't actually quirks of ahci(4) are they? They are quirks of the disks that are attached to ahci(4), and presumably should apply regardless of whether the disk in question is hooked up to ahci(4), siis(4) or even mps(4). To my mind, this means the quirks should belong to da(4), or at the very least ada(4). ada(4) and da(4) are both manipulated by CAM, so having this in camcontrol seems logical to me. To clarify, my mind is completely oblivious of how all this is implemented in software, so perhaps my mind needs to be changed rather than the code! Cheers Tom ___ 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"
auditdistd user preventing installkernel
Hi all I was updating a newly installed FreeBSD 9.1 RELEASE box to 9-STABLE, and was preparing to install the kernel in order to reboot to test it. However I was immediately hit with this: > # make installkernel DESTDIR=/ROOT/9-STABLE-2013-04-13 ERROR: Required auditdistd user is missing, see /usr/src/UPDATING. *** [installcheck_UGID] Error code 1 I did see UPDATING... 20121218: With the addition of auditdistd(8), a new auditdistd user is now depended on during installworld. "mergemaster -p" can be used to add the user prior to installworld, as documented in the handbook. It instructed me to run "mergemaster -p" prior to installworld (this should always be done anyway, according to updating). But I'm not installing world yet, just the kernel. Should UPDATING be corrected? Cheers Tom ___ 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: Ghosted logins in w/who
On Wed, Apr 10, 2013 at 3:09 PM, wrote: > If I wipe the utmp file all the w/who content goes away, resets if you > will. But in a matter of moments the problem reappears.. is this > something that needs to be submitted as a bug report do you think? > Thanks! > Damon > Hi Damon Fabian was explaining to you that utmp was replaced by utmpx. All programs in base that wrote to utmp now write to utmpx instead. If you still have programs not from base that write to utmp, you will get incorrect/crazy values reported - you must rebuild all tools that currently write to utmp so that they no longer do so. Cheers Tom ___ 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: RFC: Suggesting ZFS "best practices" in FreeBSD
On Thu, Jan 24, 2013 at 5:40 PM, Jeremy Chadwick wrote: >>> #1. Map the physical drive slots to how they show up in FBSD so if a >>> disk is removed and the machine is rebooted all the disks after that >>> removed one do not have an 'off by one error'. i.e. if you have >>> ada0-ada14 and remove ada8 then reboot - normally FBSD skips that >>> missing ada8 drive and the next drive (that used to be ada9) is now >>> called ada8 and so on... >> >>How do you do that? If I'm in that situation, I think I could find the >>bad drive, or at least the good ones, with diskinfo and the drive serial >>number. One suggestion I saw somewhere was to use disk serial numbers >>for label values. > > The term FreeBSD uses for this is called "wiring down" or "wired down", > and is documented in CAM(4). It's come up repeatedly over the years but > for whatever reason people overlook it or can't find it. Here's how you > do it for Intel AHCI (and probably others like AMD), taken directly from > my /boot/loader.conf -- > > # "Wire down" device names (ada[0-5]) to each individual port > # on the SATA/AHCI controller. This ensures that if we reboot > # with a disk missing, the device names stay the same, and stay > # attached to the same SATA/AHCI controller. > # http://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html > # > hint.scbus.0.at="ahcich0" > hint.scbus.1.at="ahcich1" > hint.scbus.2.at="ahcich2" > hint.scbus.3.at="ahcich3" > hint.scbus.4.at="ahcich4" > hint.scbus.5.at="ahcich5" > hint.ada.0.at="scbus0" > hint.ada.1.at="scbus1" > hint.ada.2.at="scbus2" > hint.ada.3.at="scbus3" > hint.ada.4.at="scbus4" > hint.ada.5.at="scbus5" > > IMPORTANT: The device names/busses/etc. are going to vary depending on > each person's setup, controller, etc.. Proof of this is in a post from > Randy Bush, where I helped him off-list with this task and he figured > out the remaining bits by himself for his hptrr(4) controller: > > http://lists.freebsd.org/pipermail/freebsd-fs/2012-June/014522.html > This wiring down is not sufficient to address all the problems with drive renumbering. For instance, add an additional ahci controller, and potentially all your drive names change again. Or not, depending on how the devices are enumerated. This is not the only problem. Take all the disks out, put them all back in, do they all have the same names? Unlikely, since their name is now derived from the controller and port they are plugged in to. Any changes, and the device name changes. Using GPT labels is easy to do, and provides a cast iron guarantee that your disk will not EVER be mistaken for a different drive. I put a GPT label on the drive, and then write it in permanent marker on the top of the drive and on a sticky label that is stuck on the front of the chassis. The disk label never changes in its lifetime, so you only get issues if you insert a drive without labelling it first. Cheers Tom ___ 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: Using dhclient on WAN if on a box serving DHCP to LAN if
On Fri, Dec 7, 2012 at 12:25 PM, Ronald Klop
wrote:
> On Fri, 07 Dec 2012 12:38:45 +0100, Tom Evans
>
> What is in dhcpd.conf?
>
> Ronald.
>
dhcpd.conf is straightforward:
option domain-name "x.com";
option subnet-mask 255.255.255.0;
default-lease-time 3600;
max-lease-time 86400;
ddns-update-style none;
subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.200 192.168.1.253;
option domain-name-servers 192.168.1.1;
option routers 192.168.1.1;
}
Ian: I had already specified dhcpd_ifaces to be just the internal
interface, which is why it had confused me! I haven't yet got any
complaints from dhcpd about the subnet on the extif, so far as I can
see.
For clarity, this is my pf.conf, which again is very simple:
ext_if="ale0"
int_if="{ em0 }"
antispoof_if="{ lo0 em0 }"
tcp_services="{ 22 443 }"
icmp_types="{ echoreq echorep unreach }"
# options
set block-policy return
set loginterface $ext_if
set skip on lo0
# tables
table persist
# scrub
#match in all scrub (no-df)
# nat/rdr
nat on $ext_if from !($ext_if) -> ($ext_if:0)
nat-anchor "ftp-proxy/*"
rdr-anchor "ftp-proxy/*"
# filter rules
block in
pass out keep state
anchor "ftp-proxy/*"
antispoof quick for $antispoof_if
block in quick on $ext_if from label "ssh bruteforce"
pass in on $ext_if inet proto tcp from any to ($ext_if) port
$tcp_services flags S/SA keep state
pass in inet proto icmp all icmp-type $icmp_types keep state
pass in quick on $int_if
Ideally, I would like the configuration to not specify the details of
the configuration. Eg, if I instead had a dynamic IP, how could I
configure that, as I would not know IP, netmask, broadcast and router
addresses beforehand.
Cheers
Tom
___
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"
Using dhclient on WAN if on a box serving DHCP to LAN if
Hi all Using 9.0-STABLE #1 r230946 - I found it out as I rebooted to prepare for 9.1, but I think it should be largely irrelevant of version. I have a freebsd router that provides all the things a soho router should on its LAN iface - DNS, DHCP, NAT (via pf). The WAN iface connects to a ADSL modem operating in bridge mode. My ISP has recently forced a change on to me, in order to get service I have to connect via DHCP, in order for them to give me my static IP. Apparently this makes their lives a lot easier. Even knowing the IP, netmask, broadcast and router is not enough, no service will flow unless a DHCP request has been registered. Relevant rc.conf, ale0 is the WAN, em0 is the LAN ifconfig_ale0="DHCP" ifconfig_em0="inet 192.168.1.1 netmask 255.255.255.0" gateway_enable="YES" dhcpd_enable="YES" dhcpd_flags="-q" dhcpd_ifaces="em0" dhcpd_conf="/usr/local/etc/dhcpd.conf" With this configuration, the default route is over the LAN iface. This causes the dhclient for ale0 to get a response from the local dhcpd server, not the ISP dhcpd server. This drove me potty! Can anyone explain why dhcpd, having been told only to listen for DHCP on em0, responds to ale0? Could this be related to my pf rules, or is it down to the default route being incorrect? Changing rc.conf to this allows the network to come up correctly: ifconfig_ale0="inet xx.xx.110.172 netmask 255.255.255.0 broadcast xx.xx.110.255 DHCP" defaultrouter="xx.xx.110.1" This relies on me knowing that these are the values that dhclient on the WAN iface will receive from my ISP's DHCP server. How would I achieve this setup if this information was dynamic or otherwise unknowable? My ISP could easily change my gateway IP, the only guarantee I have is that my allocated IP is static. So: 1) Why does the LAN dhcpd respond to the WAN dhclient? 2) Is there a better way of specifying this setup, so that it does not have hard coded addresses in there? Thanks in advance for any pointers. Tom ___ 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: simple patch for portsnap to use wget
On Tue, Nov 27, 2012 at 12:16 PM, Luca Ferrari wrote: > I did a little review and now it is possible to specify to use wget or > not using the portsnap.conf file, as well as the option to ingore > certificate checking even if I don't believe this is correct. > Therefore portsnap with this patch could work with either wget or > phttpget, even if I'm not able to test if the laminating is still > correct for phttpget (someone could test please?). > Why wget and not fetch(1)? Cheers Tom ___ 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: Node conflicts in SVN
On Wed, Nov 21, 2012 at 8:44 AM, Frank Seltzer wrote: > Following that with 'grep -A1 C\ stat' shows 217 lines similar to these: > > D C accessibility > > local unversioned, incoming add upon update This says that svn has an entry for a file/directory named 'accessibility', but that a file/directory named 'accessibility' already exists on disk, and did not come from a svn checkout - ie, 'accessibility' is in /usr/ports/.svn/entries, but there is no /usr/ports/accessibility/.svn . When you do an 'svn up' now, there is a conflict - an unversioned resource is in the way of checking out a versioned resource, and the unversioned one should be deleted, so this is why it says "D" and "C". Something has trashed your ports tree, re-check it out. You were pretty adamant that you didn't check out ports over an existing tree, which would explain this, I wonder what else it could be. Do you (or did you) run portsnap? I wonder if that could trash a working copy like this. Cheers Tom ___ 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: [stable-9] Touchpad mouse stopped working
On Thu, May 17, 2012 at 3:29 PM, Warren Block wrote: > On Thu, 17 May 2012, Tom Evans wrote: >> This doesn't work for me, I need working hald as I plug and unplug >> keyboards and mice each time I take my laptop out of its dock, > > > There might be some hardware thing in your setup that requires hald, but I > do manage to hot-connect external USB mice without HAL installed. One > notebook needed moused_enable, but that's all. Can't recall whether that > one even has InputDevice sections in xorg.conf. I'll post the config in a > bit. Yes, moused is exceptional in that regard, but my main issue is attaching/detaching keyboards. Most of my time, I use a PS/2 Model M, connected to a laptop dock with a USB<->PS/2 adaptor. I need that when I undock, I can use the laptop keyboard, and when I redock, that I get back my external keyboard. I suppose the equivalent to sysmouse/moused is kbdmux, but with hald and older Xorg, this did just DTRT. Cheers Tom PS: I just read to the end of the thread, Warren your config looks interesting if it can handle hotplugging keyboards. I will give this a try this evening, I also want to do some testing to see if the state in hald changes between xorg restarts. ___ 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: [stable-9] Touchpad mouse stopped working
On Thu, May 17, 2012 at 12:01 PM, A.J. "Fonz" van Werven wrote: > After moving from 9.0-RELEASE to 9-STABLE yesterday, the touchpad mouse on > my netbook stopped working. When I do > # /etc/rc.d/moused onestart > the pointer appears and can be moved for a second or two, then it stops > responding. Any thoughts? > > $ uname -a > FreeBSD ace.skysmurf.nl 9.0-STABLE FreeBSD 9.0-STABLE #0: Thu May 17 10:49:00 > CEST 2012 r...@ace.skysmurf.nl:/usr/obj/usr/src/sys/GENERIC i386 > > Fonz > Did you mean the mouse doesn't move in xorg, or on the console? If in xorg, have you seen this thread on x11@? http://lists.freebsd.org/pipermail/freebsd-x11/2012-April/011756.html http://lists.freebsd.org/pipermail/freebsd-x11/2012-May/011851.html The proposed solution is to set AutoAddDevices off, so that hald is not used to enumerate mice/keyboards, and instead rely on explicitly configuring them in your xorg.conf. This doesn't work for me, I need working hald as I plug and unplug keyboards and mice each time I take my laptop out of its dock, so instead I boot to console, and run this ugly hack: /usr/local/etc/rc.d/gdm onestart ; sleep 20 ; /usr/local/etc/rc.d/gdm onerestart Normally after it has restarted once, X can finally talk to hald and find the mice and keyboards. Cheers Tom ___ 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: /var getting full
On Fri, Apr 27, 2012 at 4:19 PM, Damien Fleuriot wrote: > Type: > sync > > > Then: > df -h > > Then: > cd /var && du -hd 1 > > > Post results. > As well as this, any unlinked files that have file handles open by running processes will not be accounted for in du, but will be counted in df. You could try restarting services that write to /var. Cheers Tom ___ 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: Text relocations in kernel modules
On Mon, Apr 2, 2012 at 5:49 PM, Richard Yao wrote: > On 04/02/12 05:56, Tom Evans wrote: >> On Sat, Mar 31, 2012 at 3:42 AM, Richard Yao wrote: >>>> There are no security implications, no system resources to be wasted. >>>> >>>> And if you think there are security implications, then lets see a >>>> proof-of-concept. >>> >>> If I find time to write a proof-of-concept, I promise to publish it >>> publicly. Your security team will find out when everyone else does. >> >> Richard, I'm not sure what you are trying to accomplish here. You have >> had a clear explanation of why certain things are done in a certain >> way in the FreeBSD codebase, and a confirmation that they do not think >> it causes any security issues in FreeBSD. >> >> Your response is to threaten to write an exploit against FreeBSD, and >> distribute it publicly before disclosing to security@. > > Some people believe that projects that do not take proper > countermeasures against security vulnerabilities do not deserve to have > special notification of issues. I happen to be one of them. This is a straw man argument - FreeBSD does take proper countermeasures against security vulnerabilities - and so your conclusion that you can blithely fully disclose vulnerabilities with no moral concerns is a logical fallacy. You have posited that this is a vulnerability to FreeBSD (based upon checks put in place for a Linux project) whilst many FreeBSD committers have said that you are mistaken, and it does not do so. If you disagree with them, then show them by example or argument that they are wrong. If you think they are wrong and that it is a vulnerability to FreeBSD, you should be discussing this off list in detail with the sec team - security-offi...@freebsd.org Threatening to jeopardise FreeBSD's security by public disclosure, with no discussion with the FreeBSD security team is a puerile way of acting, and does neither you, your university nor Gentoo any favours. > I suggest that you look at things from my perspective. I asked a simple > question on your mailing list. I then received several private emails > from various FreeBSD developers insulting my intelligence for the act of > asking a question. Who is the "ass" here? > I can't comment as to what people said to you off-list, I'm not party to that. What you said on-list: > If I find time to write a proof-of-concept, I promise to publish it > publicly. Your security team will find out when everyone else does. that is "ass" territory. Cheers Tom ___ 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: Text relocations in kernel modules
On Sat, Mar 31, 2012 at 3:42 AM, Richard Yao wrote: >> There are no security implications, no system resources to be wasted. >> >> And if you think there are security implications, then lets see a >> proof-of-concept. > > If I find time to write a proof-of-concept, I promise to publish it > publicly. Your security team will find out when everyone else does. Richard, I'm not sure what you are trying to accomplish here. You have had a clear explanation of why certain things are done in a certain way in the FreeBSD codebase, and a confirmation that they do not think it causes any security issues in FreeBSD. Your response is to threaten to write an exploit against FreeBSD, and distribute it publicly before disclosing to security@. Are you trying to be an ass? Someone disagrees with you on the internet, so you throw all the toys out the pram? Tom ___ 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: About kern.ipc.semmap on FreeBSD 9
On Thu, Mar 22, 2012 at 5:36 PM, Efraín Déctor wrote: > Sorry about posting to @current. > > Yep, kern.ipc.semmap does exists on FreeBSD 8.2 (I have configured it on > sysctl.conf) but on FreeBSD 9.0 its gone, Volodymyr Kostyrko pointed out > that this options need to be configured now on /boot/loader.conf (file that > on 9.0 I had to create it manually unlike 8.2). > > > Where can I find this type of changes that were made on 9.0?. > > Thank you. > http://www.freebsd.org/releases/9.0R/relnotes-detailed.html should have all changes in it; this seems to have been missed. This is the change: r224016 | bz | 2011-07-14 14:18:14 + (Thu, 14 Jul 2011) | 10 lines Remove semaphore map entry count "semmap" field and its tuning option that is highly recommended to be adjusted in too much documentation while doing nothing in FreeBSD since r2729 (rev 1.1). ipcs(1) needs to be recompiled as it is accessing _KERNEL private variables. Reviewed by:jhb (before comment change on linux code) Sponsored by: Sandvine Incorporated which suggests that the option has not done anything for a very long time. Cheers Tom ___ 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: About kern.ipc.semmap on FreeBSD 9
On Thu, Mar 22, 2012 at 4:02 PM, Efraín Déctor wrote: > Hello. I’m currently testing FreeBSD 9.0, I want to use it as a OS for > a PostgreSQL Server. However, it is recommended to modified > some paramerts such as semaphores > (http://www.postgresql.org/docs/9.1/static/kernel-resources.html ): > > kern.ipc.semmap=256 > > But when I tried to change the value on FreeBSD this pops up: > > sysctl: unknown oid 'kern.ipc.semmap' > > What Can I do to resolve this issue?. > > Thank you. (9.0 discussions should go to stable@, not current@) I don't think that kern.ipc.semmap exists on 9.0 - at least, it is present on my 8-STABLE box, and not present on my 9-STABLE box (whilst other oids, eg kern.ipc.semmni exist on both) Cheers Tom ___ 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: Request for flowtable testers and actionable feedback RE: flowtable usable or not
On Mon, Mar 5, 2012 at 4:37 PM, H wrote: > If you are curious about something, ask, right away ... clear and straight I'm curious about when you will stop trolling one of the last few fora on the internet where the SNR is actually high. This topic is discussing how users can help Kip can make flowtables more acceptable/without strange side-effects. If you're not discussing that, please don't discuss other things*. Start a new thread if you want to discuss the state of ports, whether you can't install KDE, ad infinitum. Cheers Tom * I'm well aware that I'm doing that also. I'm sorry. ___ 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: FreeBSD9 and the sheer number of problem reports
On Thu, Feb 23, 2012 at 9:21 PM, Peter Maloney wrote: > I suggest these concepts should be tested: > > Perhaps the testers tested beta1 and beta2, but there were so many > changes after beta2, that bugs appeared in release that did not exist in > beta2. Test this by reproducing things reported in release also in beta1 > or 2. > > Perhaps the people who know the rule about running .0 releases (such as > myself) never bothered to test beta1, beta2, or even release .0 (true in > my case). If so, then this rule is a very bad one. Test this with a poll. > At $JOB, we never install a N.0 release either, but only because the .0 release has such a brief life. The N.1 and N.3 releases have extended lifetimes, and so we tend to only use those versions. Cheers Tom ___ 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: problems with AHCI on FreeBSD 8.2
On Wed, Feb 15, 2012 at 10:52 AM, Jeremy Chadwick wrote: > Sorry, I missed the in-line part of your post at the top where you said: > >> > Interesting. I have 9 SAMSUNG HD154UI 1AG01118 in my raidz setup, >> > haven't had a problem with any of them yet (touch wood). > > So that would be you using the same firmware (or so I'd like to believe, > but see my previous explanations) as others. > Yes, that draws my ire too - how can you update the firmware and not change the firmware revision, it is crazy. It's possible that even amongst my drives there are different revisions, as not all drives were bought at the same time. Cheers Tom ___ 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: problems with AHCI on FreeBSD 8.2
On Tue, Feb 14, 2012 at 7:52 PM, Jeremy Chadwick wrote: > On Tue, Feb 14, 2012 at 08:31:23PM +0100, Oscar Prieto wrote: >> I used to had tons of ahci errors in my 4 disk raidz1 worth of >> HD154UIs when the rig was built a year ago or so (with 8.0 Release), >> but they dissapeared after tuning ZFS. >> >> Sadly i also got a new timeout days ago followed with smartcl erros i >> still keep unchecked but i guess they cold be legit, i still have to >> test/swap cables and give it a try. Interesting. I have 9 SAMSUNG HD154UI 1AG01118 in my raidz setup, haven't had a problem with any of them yet (touch wood). > Further details which pertain to Samsung drives: > > In your case, you run smartd(8), which periodically hits the drive with > SMART requests, pulling attribute data down and parsing it. I believe > your model is fine for this, but for similar Samsung models, I must > strongly advise against this. There are well-documented problems with > Samsung firmwares and SMART behaviour which can result in data loss (yes > you read that right). Please see smartmontools' Wiki page on the matter > for full details. Just make sure you're running a fixed firmware: > > http://sourceforge.net/apps/trac/smartmontools/wiki/SamsungF4EGBadBlocks > Yikes, I have just this week installed a HD204UI. From that page, drives manufactured after December 2010 should not be affected, which is fortunate as the linked firmware page doesn't seem to exist anymore, Samsung no longer seem to offer support for their drives and point you at Seagate, whose site (of course!) only has downloads for current Seagate drives. Hmm reading later on in the thread there is a patch to mark certain drives as having flaky NCQ - in the patch it is for the SAMSUNG HD154UI. As I mentioned before, I have 9 SAMSUNG HD154UI, all of which use ahci(4) and NCQ, and all work perfectly, no timeouts. This is using 9-STABLE. I suspect that there may be more going on than 'flaky NCQ', and that perhaps disabling NCQ masks the real issue. Cheers Tom ___ 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: Strange 'hangs' with RELENG_9
On Thu, Jan 19, 2012 at 3:00 PM, László KÁROLYI wrote: > Moreover, I couldn't set SCHED_BSD in the kernel config, it said that > it's an illegal option. Maybe it does not exist in RELENG_9. > options SCHED_4BSD Cheers Tom ___ 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 / zpool size
On Tue, Jan 17, 2012 at 4:00 PM, Christer Solskogen wrote: > A overhead of almost 300GB? That seems a bit to much, don't you think? > The pool consist of one vdev with two 1,5TB disks and one 3TB in raidz1. > Confused about your disks - can you show the output of zpool status. If you have a raidz of N disks with a minimum size of Y GB, you can expect ``zpool list'' to show a size of N*Y and ``zfs list'' to show a size of roughly (N-1)*Y. So, on my box with 2 x 6 x 1.5 TB drives in raidz, I see a zpool size of 16.3 TB, and a zfs size of 13.3 TB. Cheers Tom ___ 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: SVN checkout
On Fri, Jan 13, 2012 at 1:53 PM, Julian Kennedy wrote: > Hi All > > Im just joined the list. Im not sure if this is the right place to ask > svn questions. I want to checkout the freebsd code to play with it a > bit. What should I do and which part of the repo should I checkout? I > want the 9.0 code. > > Thx > Julian For release 9.0: http://svn.freebsd.org/base/release/9.0.0 You probably actually want what would be referred to as RELENG_9 in CVS: http://svn.freebsd.org/base/stable/9 They should be checked out as /usr/src/ Cheers Tom ___ 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: SCHED_ULE should not be the default
On Thu, Dec 15, 2011 at 12:42 AM, Jeremy Chadwick wrote: > On Thu, Dec 15, 2011 at 12:39:50AM +0100, O. Hartmann wrote: >> On 12/14/11 18:54, Tom Evans wrote: >> > I believe the correct thing to do is to put some extra documentation >> > into the handbook about scheduler choice, noting the potential issues >> > with loading NCPU+1 CPU bound processes. Perhaps making it easier to >> > switch scheduler would also help? > > Replying to Tom's comment here: > > It is already easy to switch schedulers. You change the option in your > kernel config, rebuild kernel (world isn't necessary as long as you > haven't csup'd between your last rebuild and now), make installkernel, > shutdown -r now, done. Your definition of 'easy' differs wildly from mine. How is that in any way 'easy' to do across 200 servers? > > If what you're proposing is to make the scheduler changeable in > real-time? I think that would require a **lot** of work for something > that very few people would benefit from (please stop for a moment and > think about the majority of the userbase, not just niche environments; I > say this politely, not with any condescension BTW). Sure, it'd be > "nice to have", but should be extremely low on the priority list (IMO). Real time scheduler changing would be insane! I was thinking that both/any/all schedulers could be compiled into the kernel, and the choice of which one to use becomes a boot time configuration. You don't have to recompile the kernel to change timecounter. Cheers Tom ___ 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: SCHED_ULE should not be the default
On Wed, Dec 14, 2011 at 11:06 AM, George Mitchell wrote: > > Dear Secret Masters of FreeBSD: Can we have a decision on whether to > change back to SCHED_4BSD while SCHED_ULE gets properly fixed? > Please do not do this. This thread has shown that ULE performs poorly in very specific scenarios where the server is loaded with NCPU+1 CPU bound processes, and brought forward more complaints about interactivity in X (I've never noticed this, and use a FreeBSD desktop daily). On the other hand, we have very many benchmarks showing how poorly 4BSD scales on things like postgresql. We get much more load out of our 8.1 ULE DB and web servers than we do out of our 7.0 ones. It's easy to look at what you do and say "well, what suits my environment is clearly the best default", but I think there are probably more users typically running IO bound processes than CPU bound processes. I believe the correct thing to do is to put some extra documentation into the handbook about scheduler choice, noting the potential issues with loading NCPU+1 CPU bound processes. Perhaps making it easier to switch scheduler would also help? Cheers Tom References: http://people.freebsd.org/~kris/scaling/mysql-freebsd.png http://suckit.blog.hu/2009/10/05/freebsd_8_is_it_worth_to_upgrade ___ 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: www/Apache22 fails to build when configured for LDAP and AUTHNZ_LDAP
On Wed, Nov 30, 2011 at 4:44 PM, Shaun Meyer wrote: > Hello, > > I have already built apache22 successfully on FreeBSD 8.2-RELEASE-p3 > amd64. I realized that I wanted authnz_ldap which wasn't turned on by > default so I went into www/apache22 and did the following: > > # make clean > # make config > # make showconfig | grep LDAP > LDAP=on "Enable mod_ldap" > AUTHNZ_LDAP=on "Enable mod_authnz_ldap" > # make > > LDAP and AUTHNZ_LDAP are the only adjusted knobs from the defaults. > > The operative build error is "mod_authnz_ldap.c:41:2: error: #error > mod_authnz_ldap requires APR-util to have LDAP support built in. To > fix add --with-ldap to ./configure." > > I have also tried removing and cleaning for the apr package. I see no > other apache-related files installed and all this has been done > against the latest, greatest ports collection using `portsnap`. > > This symptoms are identical to > http://www.freebsd.org/cgi/query-pr.cgi?pr=124651 except, obviously, > they have fixed that cause. > > Any advice is greatly appreciated, > > Shaun Meyer Apache from ports no longer builds against the included APR, instead it builds against the system APR, so you must rebuild devel/apr1 with LDAP support. This makes it easier to fix problems with other libraries being built with a different version of APR, and then linked into apache (eg, mod_authz_svn). This is the problem that PR is describing, and the fix in that PR no longer seems to be in the Makefile. Cheers Tom ___ 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: 8.2 + apache == a LOT of sigprocmask
On Thu, Nov 17, 2011 at 10:18 AM, Jeremy Chadwick wrote: > I don't use worker MPM on any of our boxes, we actually use ITK MPM > solely because of the hosting nature of what we do. I've actually never > seen worker MPM in use on any *IX machine I've been on or administrated, > only prefork. The Apache documentation even mentions that "if you want > stability or compatibility, prefork is the choice", while "if you want > scalability, worker is a better choice"[1]. These sorts of quotes often > shock me given what year it is. :-) > I've used both worker and event MPMs in production on high volume sites for > 4 years now, running on FreeBSD 7, with no problems. I think you are cherry picking the quotes from httpd's 2.0 documentation, which is actually an old bit of software now - it has just been voted EOL. The current stable (2.2) docs actually say: "sites that need a great deal of scalability can choose to use a threaded MPM like worker or event, while sites requiring stability or compatibility with older software can use a prefork" Event and worker have no issues unless you run non thread safe modules, or modules which use libraries which are not thread safe, eg PHP (more commonly, a PHP extension). Cheers Tom ___ 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: R: make installworld fails (touch not found)
On Fri, Sep 16, 2011 at 7:18 AM, Jason Hellenthal wrote: > > Don't get why all these references for time are popping up here and why > everyone seems to think that would make the PATH variable get cut short > from the environment that newvers.sh is running in, but see the post I > made to the real thread a few moments earlier. > Its also a FAQ in the handbook: http://www.freebsd.org/doc/en/books/faq/troubleshoot.html#TOUCH-NOT-FOUND Cheers Tom ___ 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: FreeBSD 8.2r amd 64 problem when compiling 32bit applications
On Thu, Aug 25, 2011 at 2:28 PM, noel beck wrote: > I installed FreeBSD 8.2 release on a 64-bit machine (amd64) and it has gcc > 4.2.1 built in. The library directories are lib, lib32 and lib64. When I > compiled for 64-bit the compilation was successful. > > However, the problem is when I am compiling for 32-bit on this 64-bit > machine. We are getting an error stating that libstdc++.so.6 is missing. > Other forums state that if you install compact6x or compact7x, the missing > libraries will be installed. I installed these but it did not solve my > problem. Didn't you ask the precise same question yesterday? My reply to that question, and Kostik's explanation of why even that will not work properly are relevant here. Cheers Tom ___ 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: -m32 on freeBSD 8.2r amd64
On Wed, Aug 24, 2011 at 12:11 PM, Michael Hoffmann wrote:
> Maybe off topic?
>
> 1: echo "int main(void) { return 0; }" > t.c
>
> 2: setenv LDEMULATION elf_i386_fbsd
>
> 3: gcc -c -m32 -o t.o t.c
>
> 4: gcc -nostartfiles -o a.out
> t.o -L/usr/lib32 /usr/lib32/crt1.o /usr/lib32/crti.o
>
> 5: file a.out
> a.out: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD),
> dynamically linked (uses shared libs), for FreeBSD 8.2, not stripped
>
> 6: uname -m
> amd64
>
> 2: q.v. info binutils -> Selecting The Target System
>
> Maybe there is a more comfortable way.
> Michael
>
You don't need to go to all that effort:
$ uname -m
amd64
$ echo "int main(void) { return 0; }" > t.c
$ gcc -c -m32 -o t.o t.c
$ gcc -m32 -o t t.o -B/usr/lib32
$ file t
t: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD),
dynamically linked (uses shared libs), for FreeBSD 8.2 (802510), not
stripped
Cheers
Tom
___
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: SATA 6g 4-port non-RAID controller ?
On Tue, Jul 26, 2011 at 11:55 PM, Jeremy Chadwick wrote: > > And before someone asks: in most cases you *cannot* use this card in a > PCIe x16 connector on a motherboard. Most generic motherboard > manufacturers at this point have special one-offs that assume their PCIe > x16 slots are for video cards only. If you aren't sure, you'll need to > ask your motherboard manufacturer/vendor if you can use a > non-VGA-adapter in their PCIe x16 slot. Some Supermicro boards do have > PCIe x16 slots that can be used by non-VGA adapters, but I haven't seen > this on, say, Asus/Gigabyte/Dell/Intel motherboards. > Jeremy may not have seen PCI express x16 HBAs working on consumer boards, but I have, plenty of times. I don't know why the FUD, but I have had no problems with an Intel SASUC8I (LSI 1068 based) running on an Asus P5Q Pro, a simple consumer P45 chipset. I'm not unique, many people have success doing this. Cheers Tom ___ 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: recommendations for laptop and desktop
On Thu, Jul 14, 2011 at 9:44 PM, Jim Bryant wrote: > stay away from newer hp laptops. > HP also like to lock-down which wifi cards you can use from BIOS - the machines won't complete POST with a 'bad' wifi card, so that's another strike as far as I am concerned. I've never had problems from modern dell laptops with nvidia graphics. I'm typing this on a Dell Latitude E6410 - Core i5, iwn wifi, em lan, nvidia graphics, webcam supported by webcamd... Cheers Tom ___ 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: watchdog timeout for pwait/rc.shutdown
2011/7/14 Subbsd : > Hi > > Tell me please, is it possible to change the behavior of shutdown > sequence to avoid work of kill process (or increase timeout). > > Тot always process can not react to signals and stop - for example, > heavy MySQL server databases or databases/redis - can not keep up with > 30 seconds to correct shutdown. > In my example noSQL product - redis holds a 10 GB RAM memory and when > stop it just did not have time to reset the state to disk when i stop > process or jail with redis. > As result ive have in /var/db/redis "dump.tmp.XX" - broken DB about ~3 > Gb instead of 10 GB. > > > Waiting for PIDS: 47924 > 30 second watchdog timeout expired. Shutdown terminated. > Thu Jul 14 16:24:30 MSD 2011 > Killed > > PS: I may be mistaken but I think this problem did not exist before > PS2: i have RELENG_8 and HEAD version of FreeBSD > PS3: Thanks in advance I have roughly the same problem when I shut down my laptop, squid takes at least 1 minute to shut down, so if I shutdown or restart without stopping squid first, then all my processes just get killed rather than shutdown cleanly by their rc script. An option to vary/disable the timeout would be welcome. Cheers Tom ___ 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: Crashes with Promise controller
On Thu, Jun 30, 2011 at 6:31 PM, Christian Baer wrote: > A serial console is easy enough to set up on a Sun for example, but in > this case, I am running a simple AthlonXP, which has nothing for that > sort of help. I would need a special card for that and those cose quite > a bit. :-( > Not that special - you just need a serial port on two computers. If your computers don't have serial ports, USB serial adapters work fine, and are cheap, as are (single port) PCI serial cards. Alternatively, if both computers have firewire ports, you can use dcons, and all you need is a cable. Cheers Tom ___ 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: correct way to setup gmirror on 7.4?
On Thu, Apr 28, 2011 at 4:43 PM, Pete French wrote: > Is not the problem here that you are trying to GPT label a gmirrored disc ? > If you instead gmirror two GPT partitions then the problem goes away > doesnt it ? Thats how I set things up - use parititoning on the ohysical > drives, and then put the mirroring into the partitions thus created. > Works fine, and doesnt suffer from any of the afforementioned problems. > > -pete. Is this simple to do? When I setup my home ZFS server, I couldn't get it to boot from ZFS, so I configured 2 disks as 'boot' discs: =>34 2930277101 ada5 GPT (1.4T) 34 128 1 (null) (64K) 16212582912 2 root (6.0G) 12583074 2917694061 3 samsung15-1 (1.4T) The other 'boot' disc is configured the same, except it has altroot/samsung15-2 labels on the UFS/ZFS GPT partitions (the other 4 discs have a corresponding 6 GB partition for swap/dumps). However, this is as far as I got. I currently have vfs.root.mountfrom="ufs:/dev/gpt/root", and I'd like to gmirror 'root' onto 'altroot', without overwriting GPT labels or anything dangerous! Cheers Tom ___ 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: genassym.c:1: error: CPU you selected does not support x86-64 instruction set
On Fri, Mar 18, 2011 at 3:36 PM, Randy Bush wrote: > FreeBSD rip0.psg.com 8.2-RC3 FreeBSD 8.2-RC3 #0: Sun Jan 30 06:28:31 UTC 2011 > r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > > CPU: Intel(R) Xeon(R) CPU E5405 @ 2.00GHz (1999.78-MHz K8-class > CPU) > Origin = "GenuineIntel" Id = 0x1067a Family = 6 Model = 17 Stepping = 10 > Features=0xfe3fbff > Features2=0x80082201> > AMD Features=0x20100800 > AMD Features2=0x1 > TSC: P-state invariant > > it is on a vm under vmware esxi 4.1 > > fresh csup and generic kernel in amd64 > > cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -march=i686 -std=c99 > -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef > -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys > -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter > -I/usr/src/sys/contrib/pf -I/usr/src/sys/dev/ath > -I/usr/src/sys/dev/ath/ath_hal -I/usr/src/sys/contrib/ngatm > -I/usr/src/sys/dev/twa -I/usr/src/sys/gnu/fs/xfs/FreeBSD > -I/usr/src/sys/gnu/fs/xfs/FreeBSD/support -I/usr/src/sys/gnu/fs/xfs > -I/usr/src/sys/dev/cxgb -I/usr/src/sys/dev/cxgbe -D_KERNEL > -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -finline-limit=8000 > --param inline-unit-growth=100 --param large-function-growth=1000 > -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse > -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float > -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector > /usr/src/sys/amd64/amd64/genassy > m.c > /usr/src/sys/amd64/amd64/genassym.c:1: error: CPU you selected does not > support x86-64 instruction set > *** Error code 1 > > randy Is -march=i686 coming from make.conf? Cheers Tom ___ 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 performance as the FS fills up?
On Wed, Mar 9, 2011 at 12:51 PM, Jeremy Chadwick wrote: > > Otherwise, I can imagine that prefetching could cause what you describe, > which is enabled by default in 8.0 and 8.1 and auto-disables in 8.2 if > the amount of available memory is less than 4GB. > I don't think this is accurate. Prefetch was certainly disabled by default on 8.0 if you had 4GB of RAM or less, requiring the sysctl vfs.zfs.prefetch_disable=0 to be set if you wanted prefetch and had 4GB of RAM or less. Cheers Tom ___ 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: Disable probing of bge1?
On Mon, Mar 7, 2011 at 12:26 PM, Patrick M. Hausen wrote: > Hi, all, > > I just discovered a minor problem when updating some rather dated > systems from FreeBSD 6.x to 7.x or 8.x. > > The servers are Fujitsu Technology Solutions (former Fujitsu-Siemens) > RX100 S4. The current generation of the same system is RX100 S6, so this > is two generations old. Some of them still run fine in our datacenter, though. > > While the S5 and S6 series features two gigabit ports and an additional > network interface for out of band management (called iRMC, similar to HP's > iLO), > the S4 has only two gigabit ports and the iRMC interface is piggybacked to > one of them. > > In our standard setup we disable the first interface in the BIOS. If you do > this, > the physical port is available as a dedicated management interface to the iRMC > and only the second IF is probed by FreeBSD 6.x as bge0. > > Now I try to PXE boot an identically configured system via the remote serial > console with FreeBSD 7. Everything runs fine, until the kernel probes the > network interfaces. The last thing I see are messages about successful > probing of both bge0 and bge1 and then my remote management connection > and my console are gone. > > I have to reset the BMC by literally pulling the power to get the iRMC back. > > Is it possible to use some device.hints entry to prohibit the probing of bge1? > I think that would be the easiest solution to the problem? Other suggestions > are of course welcome. I can provide more config details and dmesg output > if needed. > > Thanks, > Patrick Maybe this loader tunable will help: hw.bge.allow_asf Allow the ASF feature for cooperating with IPMI. Can cause sys‐ tem lockup problems on a small number of systems. Disabled by default. Cheers Tom ___ 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: LSI SAS 2008 (mfi) on SuperMicro X8SI6-F
On Thu, Feb 17, 2011 at 12:11 PM, Damien Fleuriot wrote: > What is sad is that these controllers are becoming very mainstream now, > we're getting them more and more on Dell servers , and the fbsd project > still struggles with them (for reasons I don't know, might be LSI's > fault, might be a lack of resources or interest...) > > I'm having a very hard time defending the use of fbsd for firewalls at > work, with the recent release of debian kfreebsd. > Forgive my naïveté, but surely kfreebsd would have precisely the same issues with the same controllers, since it uses FreeBSD's kernel. Am I missing something? Cheers Tom ___ 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: ATI Radeon LW RV200 Mobility 7500 M7 locks up on X exit
On Wed, Feb 16, 2011 at 12:19 AM, Chris H wrote: > Well, the box I'm writing this message from is running a > G98 [GeForce 8400 GS] + 3Gb videoram, while not the "latest and greatest", it > isn't really "legacy" either. I was /sure/ it'd be a "snap" to setup, but > while "functional", it isn't the optimal experience I had hoped for. > > I guess that's the price one pays for choosing a "closed source" piece of > hardware. :( > > --Chris > I've used this card for 2 years with FreeBSD + hald, never had the slightest issues, truly plug and play. nvidia0: on vgapci0 nvidia-driver-256.53 NVidia graphics card binary drivers Cheers Tom ___ 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: 8.1 amd64 lockup (maybe zfs or disk related)
On Tue, Feb 8, 2011 at 2:52 PM, Patrick M. Hausen wrote: > Hello, Jeremy, > > Am 07.02.2011 um 09:55 schrieb Jeremy Chadwick: >> The Wiki is outdated, I'm sorry to say. Given that you have 8GB RAM, I >> would recommend these settings. >> ... > > Thank you very much for the insight. A current summary of recommended > settings is very much appreciated. > > Could you add values for amd64 machines with 4 and 16 GB of memory? > That would help me a lot. Storage around 4 and 11 TB, respectively. > Access pattern: backup storage. > > Kind regards, > Patrick My home file server is similar in spec to that - Core 2 Duo, 4 GB RAM and running 8.2-RC3/amd64, with a pool with two 6 x 1.5 TB raidz arrays, for a total capacity of ~16 TB. The only ZFS settings I have changed from default are: # Allow prefetch (normally disabled for 4GB or less RAM) vfs.zfs.prefetch_disable=0 # Don't let ZFS use UMA, restricts available memory vfs.zfs.zio.use_uma=0 I think vfs.zfs.zio.use_uma defaults to 0 now anyway. I've never had a crash related to memory pressure or any other ZFS issue - it doesn't get that stressed. YMMV! Cheers Tom ___ 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: www/chromium ignores proxy settings [SEC=UNCLASSIFIED]
On Wed, Nov 24, 2010 at 11:37 AM, Jeremy Chadwick wrote: > Correct. You need to reference a PAC file for the browser to > read/parse: http://en.wikipedia.org/wiki/Proxy_auto-config > > I can show you an example .pac file if you want; I use one to define > what domain names my browser visits should be siphoned through a proxy > (SSH tunnel to work) or directly via the Internet. Interesting; I'm trying to give up using firefox (which for me leaks memory like a sieve; I have approximately 30 tabs open, RES is > 1 GB :/), but was having difficulties finding something to replace FoxyProxy, which allows me to route different sites to different proxies. This looks like it would be suitable. > > If what you're looking for is an HTTP or HTTPS-based proxy, you should > be using --proxy-server, specifying the FQDN or local hostname of the > server and what TCP port the proxy daemon is configured to accept > requests from (e.g. port 80, or port 3128 in most cases, ex. squid). > >> printenv | grep -i proxy >> http_proxy=http://gate.js.berklix.net:80 >> all_proxy=http://gate.js.berklix.net >> My proxy env vars are not being imported properly, >> & setting on command line is ugly, but no time for more now, >> possibly a bug/feature in chrome ? I never tried chrome before. > > There is a very bad assumption being made here (so far by two people). > > There is absolutely nothing that requires or guarantees a piece of > software will import or make use of *_proxy environment variables. The > software has to explicitly state it honours and respects these, and > provide documentation stating what it expects the syntax to be. I think you are assuming that people are making that assumption. I certainly wasn't, I was simply showing my proxy environment settings to give a clear indication of how my proxies are configured for other software. On the other hand, though Chrome professes that it *will* infer proxy settings from the environment: http://code.google.com/p/chromium/wiki/LinuxProxyConfig It's documentation is lacking, and doesn't mention what environment variables it uses. Secondly, once you have chrome running (and have not specified --proxy-* on the command line), chrome has a configurable dialog which allows you to set proxy settings. Anything you place in this is ignored, utterly and completely. > > The only two pieces of software I've encountered which honours these is > perl's LWP::UserAgent (and friends), and curl. + Firefox, libfetch, google-cli, skype, wine, py-httplib2 ... TBH I'm more surprised when software doesn't these days. > > I imagine lynx and some other software honours them as well, but again, > assuming software honours them (or properly parses them for that matter) > isn't reasonable. > > Is there any confirmed documentation that Google Chrome honours and > makes use of *_proxy environment variables? I see some random Linux > user forum posts claiming it does, but there's caveats to their use > apparently (see post from "disciple"; X users will probably want to read > this post): > > http://www.murga-linux.com/puppy/viewtopic.php?t=50196 > > -- > | Jeremy Chadwick j...@parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > ___ 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: www/chromium ignores proxy settings
On Mon, Nov 22, 2010 at 2:00 PM, Alexander Logvinov wrote: > Hello! > > Use chrome --proxy-server="http://proxy:3128/"; :) > Hi Alexander That didn't work either, it would not even make any connections then. With '--proxy-server=proxy:3128' though, it works correctly! It would still be nice to be able to set these options in the right place in the gui, and have them work :) Cheers Tom ___ 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"
www/chromium ignores proxy settings
Hi all I have installed chromium from ports: > # pkg_info | grep chrom chromium-6.0.472.63 A mostly BSD-licensed web browser based on WebKit and Gtk+ and I have proxy settings configured in my environment, up to my eyeballs: > $ env | grep -i oxy NO_PROXY=localhost,127.0.0.0/8,10.0.0.0/8 http_proxy=http://proxy:3128/ ftp_proxy=http://proxy:3128/ FTP_PROXY=ftp://proxy:3128/ all_proxy=socks://proxy:3128/ ALL_PROXY=socks://proxy:3128/ HTTP_PROXY_AUTH=basic:*:f...@bar.com:redacted HTTPS_PROXY=https://proxy:3128/ https_proxy=https://proxy:3128/ no_proxy=localhost,127.0.0.0/8,10.0.0.0/8 HTTP_PROXY=proxy:3128 and I have added identical settings in the Tools -> Options -> Change proxy settings in chrome itself, including proxy auth credentials. However, if I try to browse to a webpage, eg www.google.com, chromium ignores all these settings and attempts to connect directly, which I can observe using sockstat: > $ sockstat -4 | grep chrome tom chrome 14280 60 tcp4 10.0.11.202:62295 173.194.37.104:80 tom chrome 14280 61 tcp4 10.0.11.202:62795 173.194.37.104:80 > $ host www.google.com www.google.com is an alias for www.l.google.com. www.l.google.com has address 173.194.37.104 This of course times out. Any hints or pointers etc Cheers Tom ___ 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: ISDN4BSD removal (was: FreeBSD 6.4 and 8.0 EoLs coming soon)
On Thu, Oct 7, 2010 at 1:35 PM, Peter Much wrote: > aka Vadim Goncharov schrieb > mit Datum Wed, 08 Sep 2010 04:31:46 +0700 in m2n.fbsd.stable: > > |You do not understand the problem. It is not in notices & volunteers, but > |rather in the Project's policy - delete something which could still work. > |Personally, I don't use ISDN, so didn't said anything that time, but now, > > Hi all, > > at this point I would like to speak up, because I am practically > using ISDN4BSD. > > I just decided to upgrade to RELENG-8, and found out that I cannot. > So now I have 1 1/2 years (until 7.3 EOL) to figure out a solution. > http://www.selasky.org/hans_petter/isdn4bsd/ HTH Tom ___ 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: SuperMicro i7 (UP) - very slow performance
On Wed, Sep 22, 2010 at 2:50 PM, Ian Smith wrote: > It seems far more than just CPU performance is awry. Adam's data from > his i7 shows 2.7 times Bryce's speed for the md5 -t, maybe a lower EST > rate? - but that could no way account for buildworld taking 22.5 hours. > > Recent buildworld (albeit i386) on my Thinkpad T23 ran just shy of 3.5 > hours, without -j on an 1133MHz P3-M, 768MB of 133MHz RAM, 5400rpm UFS > disk - with X/KDE running meanwhile (~5-7% CPU penalty). > > cheers, Ian md5 -t is quite a small benchmark, even with his misfunctioning CPU it took <6 seconds to complete. If his problem is a misapplied heatsink/fan, then his CPU could be throttling when it gets hot, the hotter it gets the more it throttles, which could explain his massive buildworld walltime. Perhaps running something like: apply -0 "md5 -t" `jot 10` would display a notable difference. Intel chips are quite good at running without much cooling and not dieing, using thermal throttling to preserve the CPU. Cheers Tom ___ 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: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon
On Tue, Sep 21, 2010 at 3:20 PM, Vadim Goncharov wrote: > I give up. > Thank $DEITY. Cheers Tom ___ 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: kernel MCA messages
On Tue, Aug 24, 2010 at 4:06 PM, John Baldwin wrote: > On Monday, August 23, 2010 5:35:40 pm Matthew D. Fuller wrote: >> On Mon, Aug 23, 2010 at 08:20:35AM -0400 I heard the voice of >> John Baldwin, and lo! it spake thus: >> > >> > It is not private, it is in //depot/projects/mcelog/... in p4. >> >> Which may as well be Siberia for us lowly non-developers. Any chance >> you could stick a tarball or a patch against upstream mcelog >> somewhere? > > It is actually public at perforce.freebsd.org. :) However, it is tedious to > download the files. It really should be a port perhaps, though Someone (tm) > should try to get the patches integrated upstream. > > You can find a patch at www.freebsd.org/~jhb/mcelog/. You will also need to > download the memstream.c file from there as well and put that in the extracted > mcelog tarball. > I wrote a small script a while back to extract a tree from perforce using the web interface, might be handy: http://www.clearchain.com/~benjsc/downloads/FreeBSD/P4fetch.rb Cheers Tom ___ 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: Using GTP and glabel for ZFS arrays
On Thu, Jul 22, 2010 at 8:22 PM, Pawel Tyll wrote: >> I do not think I can adjust the existing zpool on the fly. I think I >> need to copy everything elsewhere (i.e the 2 empty drives). Then start >> the new zpool from scratch. > You can, and you should (for educational purposes if not for fun :>), > unless you wish to change raidz1 to raidz2. Replace, wait for > resilver, if redoing used disk then offline it, wipe magic with dd > (16KB at the beginning and end of disk/partition will do), carry on > with GPT, rinse and repeat with next disk. When last vdev's replace > finishes, your pool will grow automagically. > If you do do it like this, be sure to leave the drive you are replacing attached to the array. Otherwise, in a raidz, if you were to suffer a disk failure on one of the other disks whilst replacing/growing the array, your raidz would be badly broken. Other than that, I can thoroughly recommend this method, I had data on 2 x 1.5 TB drives, and set up my raidz initially with 4 x 1.5 TB, 2 x 0.5 TB, copying data off the 1.5 TB drives onto the array and replacing each 0.5 TB drive when done. Cheers Tom ___ 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: kernel issues with 8 STABLE
On Wed, Jun 30, 2010 at 1:16 PM, Free BSD wrote: > Dear List Members > Also, even though I have custom keyboard in my kernel configuration, > whenever I boot into single user mode I get US layout (it works fine when in > multi-user mode). Does it work correctly if you run kbdmap and choose the correct layout? If so, set keymap in /etc/rc.conf so it is always configured correctly. Cheers Tom ___ 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: if_wpi is all kinds of broken
On Mon, May 17, 2010 at 4:01 PM, Jan Henrik Sylvester wrote: > On 01/-10/63 19:59, Dominic Fandrey wrote: >> >> The if_wpi driver is all kinds of broken. The reported problems > > I have had trouble with all Intel drivers, ipw, iwi, wpi, and iwn. (As an > exception, recently, iwn was very stable on 8-STABLE.) For most notebooks, I > bought Atheros based MiniPCI(e) cards and everything was fine. > >> Where do I have to put my cash to make somebody fix this? > > 5 to 10 Euros on Ebay including shipping. Initially, I was hesitant, too, > because I wanted the hardware I already got to work, but eventually I > decided that it is not worse it. ath simply works. (I have had wi, ral, > ural, rum, and zyd, too. Over the years, nothing was as unproblematic as > ath.) > > For most notebooks, the wireless MiniPCI(e) card is very easy to replace. > > Cheers, > Jan Henrik Note that not all laptops will play nicely with different wifi cards. My old HP laptop would not boot up past the BIOS if you replaced the wifi card with one not in its magic list, which I found out after I had bought an ath based mini pci-e card to replace it (which is still spare if anyone wants it). Cheers Tom ___ 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: Enabling watchdog
On Fri, May 14, 2010 at 3:15 PM, Jeremy Chadwick wrote: > > I'm a bit confused at this point, Doug. At what point did the OP state > he has IPMI support or IPMI cards in his system? > He said he had a Dell PowerEdge 2950 - iirc these all have IPMI. Cheers Tom ___ 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: Different sizes between zfs list and zpool list
On Wed, May 5, 2010 at 4:56 PM, Freddie Cash wrote: > On Wed, May 5, 2010 at 8:44 AM, Tom Evans wrote: > >> When looking at the size of a pool, this information can be got from >> both zpool list and zfs list: >> >> > $ zfs list >> NAME USED AVAIL REFER MOUNTPOINT >> tank 5.69T 982G 36.5K /tank >> >> > $ zpool list >> NAME SIZE USED AVAIL CAP HEALTH ALTROOT >> tank 8.14T 6.86T 1.28T 84% ONLINE - >> >> Why the different sizes? >> The pool is a raidz of 6 x 1.5 TB drives. >> > > zpool lists the raw storage available to the pool. Every single bit of > every single drive is listed here. This will be 6 x 1 TB. > > zfs lists only the amount of storage available to be used, after all > redundancy is taken into account. This will be 5 x 1 TB. > > -- > Freddie Cash > fjwc...@gmail.com Ah, that makes sense - also explains why the df output matches up precisely with the zfs list output. Thanks Tom ___ 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"
Different sizes between zfs list and zpool list
Hi all When looking at the size of a pool, this information can be got from both zpool list and zfs list: > $ zfs list NAME USED AVAIL REFER MOUNTPOINT tank 5.69T 982G 36.5K /tank > $ zpool list NAME SIZE USED AVAILCAP HEALTH ALTROOT tank 8.14T 6.86T 1.28T84% ONLINE - Why the different sizes? The pool is a raidz of 6 x 1.5 TB drives. Cheers Tom ___ 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.2-p7 -> 8-STABLE mergemaster core dump
On Thu, Mar 18, 2010 at 5:27 PM, Jorge Biquez wrote: > Hello all. > With all respect Doug, users that have remote machines and do not have > access to it to boot single user like the manual says.. what can we do? I > understand that step is to be sure that no user will modify something while > we are doing those process. In my case I do that step after midnight when > our users are not in the server. > > Can others with remote systems comment about what they do in this step? > > Thanks in advance > > Jorge Biquez > > Hi Jorge As I mentioned in my email, the critical thing is that you must be running your new kernel before installing your new world. The single-user phase is simply to ensure that nothing is running that would interfere with the installworld/mergemaster steps. Therefore, an appropriate workaround if you cannot go to single user mode remotely would be to install the kernel, reboot into the new kernel, install world, reboot into the new world. However, if you have no remote access at all (remote power would be better than nothing!) this would be quite risky. Judicious use of nextboot, and having someone on standby who can find the power button is recommended. Cheers Tom ___ 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.2-p7 -> 8-STABLE mergemaster core dump
On Wed, Mar 17, 2010 at 2:37 PM, Cristiano Deana wrote: > On Wed, Mar 17, 2010 at 3:32 PM, Tom Evans wrote: > >>> make update >>> make buildworld && make kernel && make installworld >>> mergemaster >>> and i got a "bad system call (core dumped)". > >> You can't always run new userland on an old kernel, but you can always >> run old userland on a new kernel, which is why the process you went >> through is not the canonical way. See the handbook or >> /usr/src/UPDATING: > > yes, i knew. > but i was updating via ssh, so forget "run in single user". i also > know the exact procedure, but i upgrade hundreds of times before today > making this procedure and always went fine. > > i was just wondering if was a "one at a time" upgrade failure OR if > THIS upgrade (7.2 -> 8) have this problem. > > thanks all. > > btw, reboot without mergmaster and system was on again. mergemaster, > reboot and it's ready. > lucky me and thanks to freebsd > It will happen whenever you upgrade incorrectly and the newly installed userland requires syscalls that aren't present in your kernel. You need to be running your new kernel when you install your new world. What can go wrong if you don't do this order? Well, as you can see, you couldn't run mergemaster (and probably many other programs) until running your new kernel. If your new kernel did not boot successfully, you would be left with a kernel.old that boots but cant run the userland and a kernel that does not boot that can run the userland - in other words, you would be screwed. When switching major versions, there is always the chance that something major changes, so I'd try to avoid risky behaviour. YMMV. Cheers Tom ___ 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.2-p7 -> 8-STABLE mergemaster core dump
On Wed, Mar 17, 2010 at 2:25 PM, Cristiano Deana wrote: > Hi, > > anyone else tried to update (todas's cvsup) 7.3-p7 to 8-STABLE? > > make update > make buildworld && make kernel && make installworld > mergemaster > and i got a "bad system call (core dumped)". > > reboot, mergemaster again and it was allright. > > i use freebsd from 3.3 (maybe) and this is the first time i had to > reboot with new kernel/world to make a mergemaster (very dangerous, i > was remote). > > anyone else? > You can't always run new userland on an old kernel, but you can always run old userland on a new kernel, which is why the process you went through is not the canonical way. See the handbook or /usr/src/UPDATING: To rebuild everything and install it on the current system. --- # Note: sometimes if you are running current you gotta do more than # is listed here if you are upgrading from a really old current. make buildworld make kernel KERNCONF=YOUR_KERNEL_HERE [1] [3] mergemaster -p [5] make installworld make delete-old mergemaster [4] Cheers Tom ___ 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: stable-8 regression: time stands still
On Wed, Mar 3, 2010 at 11:09 AM, Jeremy Chadwick wrote: > On Wed, Mar 03, 2010 at 09:09:56AM +0100, Ruben de Groot wrote: >> > > I'm going to get this kern.timecounter sysctl from the system booted >> > > with a 7.x livecd >> > > this evening. But really, I think this is a regression. Even if this >> > > system is the only >> > > one known to be affected (which I sincerely doubt). >> > >> > You can force a timecounter choice by setting it in /boot/loader.conf. >> > I would recommend choosing ACPI-safe on your system to see if that >> > improves things: >> > >> > kern.timecounter.hardware=ACPI-safe >> >> Thanks, that solved my issue. Allthough for correctness I must add that this >> line >> must be put in /etc/sysctl.conf; it does nothing in loader.conf. >> Also the sysctl can be run in multiuser and immediately fixed the problem. > > Ah, I thought it was a loader tunable, not a sysctl tunable. My > apologies! Yes, sysctl.conf is the correct place for this. > >> One question remains: why did this suddenly become a problem in FreeBSD 8 >> and not >> in FreeBSD 7. > > That would be a question for the people who decided upon the timecounter > priorities in FreeBSD, since they're hard-coded (meaning: why HPET is > chosen above ACPI-safe). This may have changed between RELENG_7 and > RELENG_8; I simply don't know. It would be easy to verify on your > system of course (just boot a FreeBSD 7 LiveCD and provide the output > from sysctl kern.timecounter). > Another possibility could be that RELENG_7 was finding ACPI-fast, which is rated above HPET. I'm not sure why some machines get ACPI-fast and some get ACPI-safe - I think ACPI-fast is tested at boot up, and if the measurements are not consistent, it disables ACPI-fast and uses ACPI-safe instead, which is then ignored when HPET is available. Cheers Tom ___ 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: hardware for home use large storage
On Tue, Feb 9, 2010 at 3:01 PM, Dan Langille wrote: > > On Tue, February 9, 2010 9:09 am, Tom Evans wrote: >> On Tue, Feb 9, 2010 at 1:45 PM, Dan Langille wrote: >> One thing to point out about using a PM like this: you won't get >> fantastic bandwidth out of it. For my needs (home storage server), >> this really doesn't matter, I just want oodles of online storage, with >> redundancy and reliability. > > > A PM? What's that? > > Yes, my priority is reliable storage. Speed is secondary. > > What bandwidth are you getting? > PM = Port Multiplier I'm getting disk speed, as I only have one device behind the PM currently (just making sure it works properly :). The limits are that the link from siis to the PM is SATA (3Gb/s, 375MB/s), and the siis sits on a PCIe 1x bus (2Gb/s, 250 MB/s), so the bandwidth from that is shared amongst the up-to 5 disks behind the PM. Writing from /dev/zero to the pool, I get around 120MB/s. Reading from the pool, and writing to /dev/null, I get around 170 MB/s. Cheers Tom ___ 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: hardware for home use large storage
On Tue, Feb 9, 2010 at 1:45 PM, Dan Langille wrote: > > On Tue, February 9, 2010 7:51 am, Tom Evans wrote: >> On Tue, Feb 9, 2010 at 6:15 AM, Charles Sprickman wrote: >>> >>> Here's the list: >>> >>> http://secure.newegg.com/WishList/PublicWishDetail.aspx?WishListNumber=8441629 >>> >>> Just over $1K, and I've got 4 nice drives, ECC memory, and a server >>> board. >>> Going with the celeron saved a ton of cash with no impact on ZFS that I >>> can >>> discern, and again, going with a cheap tower case slashed the cost as >>> well. >>> That whole combo works great. Now when I use up those 6 SATA ports, >>> I >>> don't know how to get more cheaply, but I'll worry about that later... >>> >>> Charles >>> >> >> As long as those SATA ports are AHCI compliant, should work quite >> nicely with a SiI port multiplier. Failing that, a simple 2 port SiI >> PCI-E SATA card (supported by siis(4) driver) + 2 x SiI port >> multiplier would give you 10 extra SATA ports. >> >> My SiI PCI-E card cost £15, and the PM about £50, so it is about >> £13/port, or ~$20/port. Probably can get the components cheaper in the >> US actually. I also found some nice simple drive racks for £20/4 >> drives - not completely hotswappable, but much easier to replace than >> screwed into the case. > > Now there's an idea. Drive racks? Got a URL? > > These aren't the exact racks I bought, they seem to be discontinued (glad I bought 3 at once!), slightly more expensive, but same idea: http://www.scan.co.uk/Products/Silverstone-SST-CFP51B-Aluminum-Bay-converter-3x525-to-4x35-in-Black-with-120mm-Fan-RoHS I got the SiI add-in card and port multiplier from the same place: http://www.scan.co.uk/Products/Lycom-PE-103-x2-Port-SATAII-3Gbps-PCI-E-Controller-Card-with-NCQ-PC-MAC-Linux http://www.scan.co.uk/Products/Lycom-ST-126RM-SATA-II-3Gbps-1-To-5-Port-Multiplier-bridge-board-(for-Rack-Mount) For fixing the portmultiplier into the case, I recommend No More Nails :) I bought one of those cases that has 5.25" bays all down the front - 10 bays on mine, 1 with a DVD recorder, 9 filled with three of those drive racks, which gives me 12 'easily accessible' drive bays, 2 internal ones. With 6 SATA ports on the motherboard, together with the SiI controller + one portmultiplier, I have 12 bays and 12 SATA ports for not too much. I currently have 6 of them filled with 1.5Tb SATA drives in a raidz pool, and can expand the pool by adding another 6 as I run out of space. Works very nicely for my needs :) One thing to point out about using a PM like this: you won't get fantastic bandwidth out of it. For my needs (home storage server), this really doesn't matter, I just want oodles of online storage, with redundancy and reliability. Cheers Tom ___ 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: hardware for home use large storage
On Tue, Feb 9, 2010 at 6:15 AM, Charles Sprickman wrote: > > Here's the list: > > http://secure.newegg.com/WishList/PublicWishDetail.aspx?WishListNumber=8441629 > > Just over $1K, and I've got 4 nice drives, ECC memory, and a server board. > Going with the celeron saved a ton of cash with no impact on ZFS that I can > discern, and again, going with a cheap tower case slashed the cost as well. > That whole combo works great. Now when I use up those 6 SATA ports, I > don't know how to get more cheaply, but I'll worry about that later... > > Charles > As long as those SATA ports are AHCI compliant, should work quite nicely with a SiI port multiplier. Failing that, a simple 2 port SiI PCI-E SATA card (supported by siis(4) driver) + 2 x SiI port multiplier would give you 10 extra SATA ports. My SiI PCI-E card cost £15, and the PM about £50, so it is about £13/port, or ~$20/port. Probably can get the components cheaper in the US actually. I also found some nice simple drive racks for £20/4 drives - not completely hotswappable, but much easier to replace than screwed into the case. Cheers Tom ___ 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: Error upgrading 7.0 to 7.2 (buildword in gnu/usr.bin/binutils/libopcodes setp)
On Wed, Dec 16, 2009 at 4:32 PM, Lowell Gilbert wrote: > Jordi Espasa Clofent writes: >> Lowell Gilbert escribió: >> Wonderful. I've used times the same command (1) without -j flag >> and... it works perfectly! >> It's curious, because of I always use the -j flag in buildworld with >> successs. It has been the first time that I've experienced this >> problem > > buildworld is supposed to work with -j, but I've never used a value that > large. Unless you have 8 or more CPU cores available, I would expect > builds to be faster if you reduced that value. > Running more concurrent processes will use more CPU and more memory (you'd hope, anyways). This could lead it to use bits of hardware with -j 8 that it wouldn't use without it, potentially exposing hardware flaws. Cheers Tom ___ 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: FreeBSD 8 GPT install, how?
On Thu, Dec 3, 2009 at 2:15 PM, Ollivier Robert wrote: > According to Steven Hartland: >> >> I've found a number things articles on how to achieve this on previous >> versions, but they are all quite complex and was hoping there was a nice >> easy way on 8.0 given the improvements listed in the release notes. >> >> Any pointers? > > A plug for my ZFS-on-ROOT howto here: > http://www.keltia.net/howtos/zfsboot > This, like other howtos I've seen, seems to delight in making gpart as difficult and cumbersome to use as possible. This one is better than the ones on the wiki, who seem to think we should calculate the size of a partition in 512k blocks. Eg: gpart add -b 34 -s 128 -t freebsd-boot da0..da164 KB boot gpart add -b 162 -s 1G -t freebsd-swap -l swapN da0..da1 1 GB swap gpart add -t freebsd-zfs da0..da1 7.5 GB rest Most of these arguments are unnecessary. gpart generally already knows where to put a partition (computers apparently are quite good at adding 2 numbers together), so specifying offsets just isn't necessary. This boils down to: gpart add -s 64K -t freebsd-boot $dev gpart add -s 1G -t freebsd-swap -l swapN $dev gpart add -t freebsd-zfs $dev Cheers Tom ___ 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: Can't use gpt labels re-importing pool
On Thu, Nov 26, 2009 at 8:50 AM, Jeremy Chadwick wrote: > I'm a bit curious about something, so maybe someone can help me > understand: > > Why are people bothering with GPT labels (or in some cases, glabels) > when AHCI (whether it be ataahci.ko or ahci.ko) is in use? Under what > circumstance would the device name change dynamically in this situation? > > I've never witnessed this happening with AHCI, at least on Intel > systems, and I've hot-swapped hard disks many times over. > > My home server has 6 x ICH10 SATA ports using ahci(4), and 2 x SiL 3128 SATA ports using siis(4). When I first set it up, I created a raidz pool using MBR/BSD slices/partitions on the drives on the ahci controllers, (ie zpool create tank raidz ada[0-5]s1d). I then shutdown, connected a couple of drives to the siis controller, and booted up again. This caused the pool to fail to be imported, as the drives on siis came up as ada0 and ada1. I then wiped out the pool, and restarted the install, but this time using GPT partitioning and labelling each partition that I use. Now I can connect my drives on any interface, any order and it works correctly, always. I also get a nice label for each drive that I can scribble on the drive cage, and I can tell exactly what physical device is referred to by a label. The only cost to this was having to remember to label the drives - well worth it imo. Cheers Tom ___ 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: pthread.h: typo in #define pthread_cleanup_push/pthread_cleanup_pop
On Tue, Nov 24, 2009 at 3:18 PM, Mikolaj Golub wrote: > > So, I don't know what these macros actually were supposed to be. They were > introduced in r179662: > > Revision 1.43: download - view: text, markup, annotated - select for diffs > Mon Jun 9 01:14:10 2008 UTC (17 months, 2 weeks ago) by davidxu > Branches: MAIN > Diff to: previous 1.42: preferred, colored > Changes since revision 1.42: +21 -2 lines > > SVN rev 179662 on 2008-06-09 01:14:10Z by davidxu > > Make pthread_cleanup_push() and pthread_cleanup_pop() as a pair of macros, > use stack space to keep cleanup information, this eliminates overhead of > calling malloc() and free() in thread library. > > Discussed on: thread@ > http://lists.freebsd.org/pipermail/freebsd-threads/2008-May/004299.html Cheers Tom ___ 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: whats best pracfive for ZFS on a whole disc these days ?
On Thu, Nov 19, 2009 at 12:35 PM, Daniel O'Connor wrote: > On Thu, 19 Nov 2009, Marius Nünnerich wrote: > > > operator0, 164 Oct 21 15:34 > > > /dev/gptid/6866d8b0-a8ac-11de-8e07-00241dd192cc > > > > Have you tried naming the GPT partitions and using /dev/gpt/* ? > > Nope, how would I do that? > > I'd be surprised if it worked TBH.. > > Use the -l flag to gpart when creating the partitions. I'm not sure if there is a way to label them after the fact. I found it led to a much more descriptive/reliable pool, as I can plug the disks in anywhere and get the same results: pool: tank state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 raidz1 ONLINE 0 0 0 gpt/samsung15-1 ONLINE 0 0 0 gpt/samsung15-2 ONLINE 0 0 0 gpt/samsung15-3 ONLINE 0 0 0 gpt/samsung15-4 ONLINE 0 0 0 gpt/seagate15-1 ONLINE 0 0 0 gpt/seagate15-2 ONLINE 0 0 0 I use the geom name 'gpt/foo' when referring to the disks in zpool. All works perfectly. Cheers Tom ___ 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"
8.0-RC1 ZFS loader extremely slow
Hi all I just installed 8.0-RC1 amd64 on a 6 gpt disk ZFS raidz1 (following the guide on the wiki), but have problems on reboot with the newly installed ZFS aware loader. The loader runs correctly, but incredibly slowly. It takes about 2 hours to get to the point where it enumerates the BIOS disks, although when it gets to that point, it does not take a long time to enumerate each disk. It takes about 2 minutes for each character change of the spinner! Fully completing the loader takes somewhere between 2 and 8 hours (I got bored watching it), and works correctly. The loader from the memstick image works normally. Daichi GOTO experienced something similar back in January [1], but there didn't seem to be any resolution to that problem. Disabling AHCI has no effect. Interestingly, we both have P45 based motherboards. I will try installing 8.0-RC2 tonight, and try to save verbose boot logs, dmidecode etc. If there is any other information I should be looking at, please let me know. Cheers Tom [1] http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2009-02/msg00108.html ___ 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: SCSI device not created upon a CF card plug in
On Wed, 2009-07-22 at 11:52 +0800, Sagara Wijetunga wrote: > Hi Milan, thanks for the reply. > > Yep, your suggestion works but it simply unacceptable for end users. We are > the makers of the Tomahawk Desktop (http://www.tomahawkcomputers.com/). > > Anybody in the FreeBSD community care to develop a patch to make it possible > to use multi-card readers under FreeBSD? > > Best regards > Sagara Perhaps that could be what the Tomahawk Desktop contributes back to FreeBSD? Seems to be your itch... Regards Tom ___ 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: upgrading ports without recompiling
On Mon, 2009-07-06 at 11:04 -0500, Ishmael F.E. wrote: > Hi there > . > ¿How can I upgrade my ports without having to recompile everything? > . > I allready did > # freebsd-update -r 7.2-RELEASE upgrade install > # reboot > # freebsd-update install > . > But it didn'nt upgrade the ports, so I tryed > # portupgrade -af > but it tried to compile everything > . > I also tried > # portsnap fetch > # portsnap extract > # portsnap fetch update > # portupgrade -a --batch -u -P > . > but it also tried to compile everything > . > so, ¿how can I upgrade the ports? > unfortunatley I don't have time to compile my 64bit system > . > . portupgrade will use packages where available with the -P flag, and will only use packages with the -PP flag. However, since you say it failed to find packages with -P, falling back to recompiling, then it will probably fail even more with -PP. man portupgrade for more details. Cheers Tom ___ 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: support quality (Re: dump | restore fails: unknown tape headertype 1853384566)
On Thu, 2009-03-26 at 14:45 +, Jake Scott wrote: .. > Absolutely. You really must use a tool that interacts with the database > to perform the backup. Most commercial DBs have hooks that allow the > backup routines to call out to custom snapshot facilities. One would > usually request a backup through the database, which would then freeze IO > to its data files and maybe log files, deal with flushing caches etc and > then call your snapshot routine. I'm not aware that MySQL and Postgres do > though so the best you can do is a dump. > > > Jake > Just to add, mysql has a utility (mysqlhotcopy) to allow you to directly copy MyISAM databases with a guarentee of consistency (thus avoiding the conversion from MyISAM data -> SQL, and no need to reimport when recovering). It isn't exactly online though, any writes will be blocked until the hotcopy finishes. Still, it is only MyISAM, and not much call for that these days.. Cheers Tom ___ 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: HEADS UP: Major CAM performance regression
On Fri, 2009-02-13 at 03:55 -0700, Scott Long wrote: > All, > > A major performance regression was introduced to the CAM subsystem in > FreeBSD 7.1. The following configurations are known to be affected: > > VMWare ESX > VMWare Fusion > (using bt or lsilogic controller options) > HP CISS RAID > Some MPT-SAS combinations with SATA drives attached > (Includes Dell SAS5/ir, but not PERC5/PERC6). > > Pure SCSI and SAS subsystems likely are NOT affected. Any hardware > that uses the 'ata' driver is also definitely NOT affected. To > determine if your installation is affected, run the following command as > root: > > camcontrol tags da0 > > Substitute 'da0' with another appropriate drive device number, if > needed. Note that this ONLY AFFECTS 'da' DEVICES. If your disks are > 'ad' devices, they are NOT affected. > > The result from running this command should be an output similar to the > following: > > (pass0:mpt0:0:8:0): device openings: 255 > > If, instead, it reports a value of '1', you are likely affected. Note > that it may be normal for USB memory devices to report a low number. > Also, many legacy SCSI disks, and devices that are not disks, may also > be expected to report a low number. > > The effect of this problem is that only one I/O command will be issued > to the controller and disk at a time, instead of overlapping multiple > commands in parallel. This causes significantly higher latency in > servicing moderate and heavy I/O workloads, leading to very poor > performance. Performance can be easily compared by downgrading to > FreeBSD 7.0. > > I have committed a fix for this problem for FreeBSD 8-CURRENT as of SVN > revision 188570. FreeBSD 7-STABLE will be updated with the fix in a few > days once I've gotten confirmation that the fix works and doesn't cause > any adverse side-effects. Anyone wanting to help in this validation > effort should apply the attached patch to their kernel source tree and > recompile. Please contact me directly by email to report if the problem > is fixed for you. > > If the validation process goes smoothly, I will work with the release > engineering team to turn this fix into an official errata update for > FreeBSD 7.1. > > Thanks in advance for your help. > > Scott > Hi Scott I have one da0 device, a USB attached hard disk: umass0: on uhub6 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: 238475MB (488397168 512 byte sectors: 255H 63S/T 30401C) camcontrol shows: > $ sudo camcontrol tags da0 (pass0:umass-sim0:0:0:0): device openings: 1 Is that to be expected? This is RELENG_7 from October '08: FreeBSD strangepork.mintel.co.uk 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Wed Oct 22 02:25:56 BST 2008 r...@sweetpork.pc.mintel.co.uk:/usr/FreeBSD/RELENG_7/obj/usr/FreeBSD/RELENG_7/src/sys/STRANGEPORK i386 Thanks Tom ___ 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"
Page fault while in kernel mode
Hi all.
I got this panic when our SMB server moved hostname. I still had the
drives mounted, so I wondered what would happen if I ls'ed the mount
point ('Doctor it hurts when I do this' 'Dont do that then..').
I'm running i386 RELENG_7 from mid October, so it is more than possible
that this has already been fixed, but best to report it as well. I still
have the vmcore if anyone wants more info from it.
Cheers
Tom
FreeBSD strangepork.mintel.co.uk 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE
#0: Wed Oct 22 02:25:56 BST 2008
r...@strangepork.mintel.co.uk:/usr/FreeBSD/RELENG_7/obj/usr/FreeBSD/RELENG_7/src/sys/STRANGEPORK
i386
> # kgdb /usr/obj/usr/FreeBSD/RELENG_7/src/sys/STRANGEPORK/kernel.debug
> /var/crash/vmcore.1
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd"...
Unread portion of the kernel message buffer:
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x18
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0817385
stack pointer = 0x28:0xe8276adc
frame pointer = 0x28:0xe8276af8
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= resume, IOPL = 0
current process = 1032 (smbiod0)
trap number = 12
panic: page fault
cpuid = 0
Uptime: 20d23h21m41s
Physical memory: 1992 MB
Dumping 314 MB: 299 283 267 251 235 219 203 187 171 155 139 123 107 91 75 59 43
27 11
Reading symbols from /boot/kernel/snd_hda.ko...done.
Loaded symbols for /boot/kernel/snd_hda.ko
Reading symbols from /boot/kernel/sound.ko...Reading symbols from
/boot/kernel/sound.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/sound.ko
Reading symbols from /boot/modules/nvidia.ko...done.
Loaded symbols for /boot/modules/nvidia.ko
Reading symbols from /boot/kernel/linux.ko...Reading symbols from
/boot/kernel/linux.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/linux.ko
Reading symbols from /boot/kernel/acpi.ko...Reading symbols from
/boot/kernel/acpi.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/acpi.ko
Reading symbols from /boot/kernel/linprocfs.ko...Reading symbols from
/boot/kernel/linprocfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/linprocfs.ko
Reading symbols from /boot/kernel/smbfs.ko...Reading symbols from
/boot/kernel/smbfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/smbfs.ko
Reading symbols from /boot/kernel/libiconv.ko...Reading symbols from
/boot/kernel/libiconv.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/libiconv.ko
Reading symbols from /boot/kernel/libmchain.ko...Reading symbols from
/boot/kernel/libmchain.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/libmchain.ko
Reading symbols from /boot/kernel/nullfs.ko...Reading symbols from
/boot/kernel/nullfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/nullfs.ko
Reading symbols from /boot/kernel/fdescfs.ko...Reading symbols from
/boot/kernel/fdescfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/fdescfs.ko
#0 doadump () at pcpu.h:196
196 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) bt full
#0 doadump () at pcpu.h:196
No locals.
#1 0xc07e2047 in boot (howto=260) at
/usr/FreeBSD/RELENG_7/src/sys/kern/kern_shutdown.c:418
_giantcnt = Variable "_giantcnt" is not available.
(kgdb) bt
#0 doadump () at pcpu.h:196
#1 0xc07e2047 in boot (howto=260) at
/usr/FreeBSD/RELENG_7/src/sys/kern/kern_shutdown.c:418
#2 0xc07e2319 in panic (fmt=Variable "fmt" is not available.
) at /usr/FreeBSD/RELENG_7/src/sys/kern/kern_shutdown.c:574
#3 0xc0b1b45c in trap_fatal (frame=0xe8276a9c, eva=24) at
/usr/FreeBSD/RELENG_7/src/sys/i386/i386/trap.c:939
#4 0xc0b1bdcf in trap (frame=0xe8276a9c) at
/usr/FreeBSD/RELENG_7/src/sys/i386/i386/trap.c:320
#5 0xc0b028fb in calltrap () at
/usr/FreeBSD/RELENG_7/src/sys/i386/i386/exception.s:159
#6 0xc0817385 in turnstile_broadcast (ts=0x0, queue=0) at
/usr/FreeBSD/RELENG_7/src/sys/kern/subr_turnstile.c:836
#7 0xc07d4b12 in _mtx_unlock_sleep (m=0xc6457494, opts=0, file=0xc631c718
"/usr/FreeBSD/RELENG_7/src/sys/modules/smbfs/../../netsmb/smb_iod.c", line=97)
at /usr/FreeBSD/RELENG_7/src/sys/kern/kern_mutex.c:619
#8 0xc07d4e72 in _mtx_unlock_flags (m=0xc6457494, opts=0, file=0xc631c718
"/usr/FreeBSD/RELENG_7/src/sys/modules/smbfs/../../netsmb/smb_iod.c", line=97)
at /usr/FreeBSD/RELENG_7/src/sys/kern/kern_mutex.c:210
#9 0xc630fb73 in smb_iod_invrq (iod=Variable "iod" is not available.
) at /usr/FreeBSD/RELENG_7/src/sys/modules/s
Re: Free memory after upgrade to 7.1
On Wed, 2009-02-04 at 18:42 +0100, Tomas Randa wrote: > Yes, I do portupgrade -Rrfia after upgrade of course. > I don`t think it is some "new" PHP bug, because my friend have same > problem with memory and he do not upgraded ports. But his box do not > free memory after apache reload, my yes > > Any other suggestions ? > > Thanks TR > > > > Tom Evans napsal(a): > > On Wed, 2009-02-04 at 17:08 +0100, Tomas Randa wrote: > > > >> Hello, > >> > >> I have i386/PAE system (php, apache22, mysql) running on 7-STABLE and I > >> can see strange behavior after upgrade from 7.0: Apache does not free > >> memory, for example: > >> > >> CPU: 31.2% user, 0.0% nice, 12.8% system, 0.7% interrupt, 55.3% idle > >> Mem: 3520M Active, 3705M Inact, 465M Wired, 314M Cache, 112M Buf, 12M Free > >> Swap: 4096M Total, 105M Used, 3991M Free, 2% Inuse > >> > >> then apachectl graceful > >> > >> CPU: 28.3% user, 0.0% nice, 8.6% system, 0.0% interrupt, 63.1% idle > >> Mem: 631M Active, 3126M Inact, 353M Wired, 213M Cache, 112M Buf, 3693M Free > >> Swap: 4096M Total, 1844K Used, 4094M Free > >> > >> Some graph: http://max.af.czu.cz/memoryload.png > >> > >> I know before upgrade was memory using about 2,5GB, now much more, > >> apache sometimes crash. > >> > >> Thanks for some help > >> > >> Tomas Randa > >> > > > > What is apache doing to use so much memory? This looks more like a > > memory leak in PHP, which is reclaimed after apache restarts its > > children. > > > > When you upgraded the OS, did you also upgrade ports? Could a new > > version of PHP be at fault here? > > > > Cheers > > > > Tom > > Well, apache + its regular modules dont tend to leak memory, which is what is happening. Can you run tests, eg by running your application on apache with valgrind, to determine exactly where the leak occurs. Tom ___ 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: Free memory after upgrade to 7.1
On Wed, 2009-02-04 at 17:08 +0100, Tomas Randa wrote: > Hello, > > I have i386/PAE system (php, apache22, mysql) running on 7-STABLE and I > can see strange behavior after upgrade from 7.0: Apache does not free > memory, for example: > > CPU: 31.2% user, 0.0% nice, 12.8% system, 0.7% interrupt, 55.3% idle > Mem: 3520M Active, 3705M Inact, 465M Wired, 314M Cache, 112M Buf, 12M Free > Swap: 4096M Total, 105M Used, 3991M Free, 2% Inuse > > then apachectl graceful > > CPU: 28.3% user, 0.0% nice, 8.6% system, 0.0% interrupt, 63.1% idle > Mem: 631M Active, 3126M Inact, 353M Wired, 213M Cache, 112M Buf, 3693M Free > Swap: 4096M Total, 1844K Used, 4094M Free > > Some graph: http://max.af.czu.cz/memoryload.png > > I know before upgrade was memory using about 2,5GB, now much more, > apache sometimes crash. > > Thanks for some help > > Tomas Randa What is apache doing to use so much memory? This looks more like a memory leak in PHP, which is reclaimed after apache restarts its children. When you upgraded the OS, did you also upgrade ports? Could a new version of PHP be at fault here? Cheers Tom ___ 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: DL360 G3 w/ AMD64 Cant boot from CD
On Tue, 2008-11-04 at 11:18 -0500, Kevin wrote: > > > I tried 7.1-BETA2 , but unfortunately the same problem happened. I > > tried > > > (for the sake of argument) Debian debian-40r5-amd64 , and it wouldn't > > boot > > > either -- it said "Your CPU does not support long mode, please use a > > 32bit > > > distribution". > > > > This means your processor does not support 64-bit mode. > > > > > How would I support over 4GB of ram with only i386 distributions? > > > > There is only one option: use PAE mode, which has drawbacks. You can > > read about what PAE is on Wikipedia. > > > > Note that not all drivers are PAE mode compatible on FreeBSD. You > > should be able to install i386 FreeBSD with success, then rebuild your > > kernel with PAE enabled. Look at /sys/i386/conf/PAE for an example > > configuration -- you'll see all of the drivers you have to disable for > > PAE to work successfully. If your system uses any of these drivers, > > PAE > > mode will not work for you, in which case you should upgrade your > > hardware. > > > > -- > > | Jeremy Chadwickjdc at parodius.com | > > | Parodius Networking http://www.parodius.com/ | > > | UNIX Systems Administrator Mountain View, CA, USA | > > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > > Is my issue related to non-supporting of 64bit mode (2x Dual Xeons in the > DL360 G3) , or perhaps due to a boot loader bug? > > I found this PR : > > 91492 freebsd- amd64feedback serious medium current-us [boot] BTX > halted > > > In any case , the latest 6.4/7.1 Snapshot produced the same BTX Halt error. > I'll just use i386 w/ PAE for now I suppose. I haven't tested AMD64 with > DL360 G4's or DL360 G5's , but I'd appreciate if anyone has tested those > generations w/ FreeBSD AMD64 , to let me know if the problem persists in > some form. > > > Thank you. If your CPUs don't support LM (long mode, aka amd64), then booting an amd64 image wont get very far. Judging from the ubuntu message, your CPUs dont. If you have installed/booted FreeBSD, you can find out what your CPU supports by looking at the Features mentioned in dmesg: > $ grep Features /var/run/dmesg.boot Features=0xbfebfbff Features2=0xe3fd AMD Features=0x2010 AMD Features2=0x1 Iif your CPU supported amd64, it would be mentioned in AMD Features (as LM). Tom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Correct downgrade procedure
Hi all I've been having increasingly annoying Xorg crashes with 7.1, on a previously very reliable laptop[1], and am now trying to go back to how it used to work, starting off by downgrading kernel + world to 7.0-RELEASE, which used to work quite nicely. If that fails to make any huge strides, I guess I'll have to rollback the ports tree as well. I was wondering if there was a best-practise way of downgrading? I guess I will also have to rebuild all/most ports; that's what weekends are for :) Cheers Tom [1] http://lists.freebsd.org/pipermail/freebsd-x11/2008-October/006822.html signature.asc Description: This is a digitally signed message part
Re: am2 MBs - 4g + SCSI wipes out root partition
On Mon, 2008-10-13 at 09:37 -0200, JoaoBR wrote: > On Saturday 11 October 2008 13:26:29 Adam McDougall wrote: > > Jeremy Chadwick wrote: > > > On Sat, Oct 11, 2008 at 04:45:29PM +0200, Gary Jennejohn wrote: > > >> On Sat, 11 Oct 2008 03:13:16 -0700 > > >> > > >> Jeremy Chadwick <[EMAIL PROTECTED]> wrote: > > >>> On Sat, Oct 11, 2008 at 11:30:57AM +0200, Gary Jennejohn wrote: > > On Fri, 10 Oct 2008 14:29:37 -0300 > > > > JoaoBR <[EMAIL PROTECTED]> wrote: > > > I tried MBs as Asus, Abit and Gigabyte all same result > > > > > > Same hardware with SATA works perfect > > > > > > Same hardware with scsi up to 3.5Gigs installed works perfect > > > > > > what calls my attention that all this MBs do not have the memroy hole > > > remapping feature so the complete 4gigs are available what normally > > > was not the case with amd64 Mbs for the Athlon 64 CPUs > > > > > > some has an opinion if this is a freebsd issue or MB falure or scsi > > > drv problem? > > > > It's a driver problem. If you want to use SCSI then you'll have to > > limit memory to 3.5 GB. > > >>> > > >>> What you're saying is that Adaptec and LSI Logic SCSI controllers > > >>> behave badly (and can cause data loss) on amd64 systems which contain > > >>> more than 3.5GB of RAM. This is a very big claim. > > >>> > > >>> Have you talked to Scott Long about this? > > >>> > > >>> Please expand on this, and provide evidence or references. I need to > > >>> document this in my Wiki if it is indeed true. > > >> > > >> See the freebsd-scsi thread with Subject "data corruption with ahc > > >> driver and 4GB of memory using a FBSD-8 64-bit installation?" from Wed, > > >> 30 Jan 2008. > > >> > > >> This was for ahc, but the bit-rot which Scott mentions in his reply > > >> might also apply to the LSI Logic controllers. > > >> > > >> Basically the driver doesn't correctly handle DMA above 4GB. Since the > > >> PCI hole gets mapped above 4GB it causes problems. the (S)ATA drivers > > >> don't seem to have this problem. > > > > > > Thank you -- this is the exact information I was looking for. > > > > > > I will update my Wiki page to reflect this quite major problem. > > > > I am using some LSI (mpt driver) ultra4 (U320 scsi) and LSI SAS > > controllers in FreeBSD 7.x amd64 with 20G of ram, and Adaptec (aac > > driver) with a 5th generation RAID card with 8G of ram, both have no > > such corruption problems. Providing this as a counter-example just to > > document some evidence of which products seem to work fine. > > ___ > > > well this for sure is NOT a AM2 MB but any server MB which indeed run fine as > Tyans, SMs and others I guess > It sounds like your issue is specific to certain motherboards and BIOS, which would be non driver specific. Unless this is something that can be worked around, I think the 'solution' is that with this hardware, you are limited to 3.5 GB RAM. Perhaps different SoHo boards would provide different behaviour... Cheers Tom signature.asc Description: This is a digitally signed message part
Re: proposed change to support policy for FreeBSD Releases
On Tue, 2008-09-23 at 13:37 -0700, Jo Rhett wrote: > Some quite lively offline discussion has come to conclusion with the > following suggestions to change the support policy. Obviously, this > is what we feel would be a good idea, but it's obviously open to > discussion and there's nobody demanding anything here. It just seems > "better". > > Old text: > > Each branch is supported by the Security Officer for a limited time > > only, and is designated as one of `Early adopter', `Normal', or > > `Extended'. The designation is used as a guideline for determining > > the lifetime of the branch as follows. > > > > Early adopter > > Releases which are published from the -CURRENT branch will be > > supported by the Security Officer for a minimum of 6 months after > > the release. > > Normal > > Releases which are published from a -STABLE branch will be > > supported by the Security Officer for a minimum of 12 months after > > the release. > > Extended > > Selected releases will be supported by the Security Officer for > > a minimum of 24 months after the release. > > Proposed (starting point for discussion for) new text: > > Each branch is supported by the Security Officer for a limited time > only, and is designated as one of `Early adopter', `Normal', or > 'Final'. The designation is used as a guideline for determining the > lifetime of the branch as follows. > > Early adopter > Releases which are published from the -CURRENT branch will be > supported by the Security Officer for a minimum of 6 months after the > release. > > > Normal > Releases which are published from a -STABLE branch will be > supported by the Security Officer for a minimum of 12 months after the > release. > A release which is not the final minor release of a branch will > be additionally supported by a minimum of 6 months past the release > date of the succeeding version. For example X.1 will be supported for > 12 months or until 6 months past the release date of X.2, whichever > comes later. > > Final > The final minor release on a given branch will be supported by > the Security Officer for a minimum of 24 months after the release. > > > OBSERVATIONS: > > 1. This avoids the need for the well-documented chicken-and-egg > problem of trying to guess which release is the final release. > > 2. This is a consistent policy in line with many other vendor policies. > > 3. This rewards forward movement in the branch. > > And finally, as I've done the match carefully, > > 4. It would appear to *reduce* rather than enlarge the support > requirements for the security team. Unless a minor release comes out > less than 6 months after a previous release, only two versions would > ever be supported at the same time. In recent history 3 minor > releases in the same branch have been supported more often than not. > > Example under current policy: > > 6.5 comes out in July of 2009. For July -> October the security team > will need to support 3 releases: 6.3, 6.4 and 6.5. From November > 2009 through January 2010 the security team will need to support 6.3 > and 6.5, but not 6.4. > > Revised under the existing policy: > > Support for 6.3 expires in April of 2009. (more than 12 months past > release and 6 months after the release of 6.4). Support for 6.4 > expires in January of 2010. Support for 6.5 would expire in July of > 2011 or 6 months after the release of 6.6. > > ^NOTE: this example is probably unfeasible since 6.3 already has a > published support period ended in January 2010, but this will prevent > a similar occurrence happening in future releases. > > Note2: This new policy would not change the support period for 6.4 if > it is the final release, but it does completely resolve the need to > "guess" whether or not it will be the final release. > > The notable change that I believe will encourage business > participation in the testing/evaluation process is that 6.4 is > guaranteed to be supported either 24 months, or at least 6 months past > the release date of 6.5. (recent history suggests this would be > 15-19 months). This encourages businesses to test and evaluate 6.4 > NOW, rather than waiting until a decision about the support policy is > made. > > Repeat from the top: nobody is demanding anything. I think this > policy would make a lot more sense, and would promote forward > movement. Feel free to correct me if we overlooked anything. Thanks. > Isn't this a non-pragmatic way of looking at this? Currently, as long as there are no serious issues with 6.4, 6.4 will be supported for 24 months from release. This is abundantly clear from both prior history and what secteam say. If there are serious issues, then 6.5 will be cut to address these issues, and it would be a release to address these issues. In this case, the 'only 12 month support' is irrelevant; one would want to migra
Re: FreeBSD 7.1 Content
On Thu, 2008-09-04 at 08:45 -0600, Dan Allen wrote: > On 4 Sep 2008, at 12:20 AM, Jeremy Chadwick wrote: ... > It was using Ubuntu that caused me to realize how far behind FreeBSD > is on the desktop side, and how, with a SMALL AMOUNT of work and > changes, it could make a big jump forward by this proposed simple > addition. Heck, if nothing else the installer could simply say in a > help screen, "if you want a web browser on your system, type 'pkg_add - > r firefox' on your system and edit blah blah .conf blah". As it > stands right now, however, there is very little in the install process > which helps a user get X up and going with a browser. > > Thanks to everyone else for their comments. > > Dan (this isn't meant to be a flame :) For me, part of the install process was reading the handbook, which details quite clearly how to go from sysinstall to desktop. Projects driven by billionaire South Africans can target their paid developers at whatever tasks they think are important. It seems very few FreeBSD devs are interested enough to attack this 'small amount' of work, and that is their (valid) choice*. In a volunteer project, volunteers work on what interests them, not what someone else thinks is important. Cheers Tom * although check out finstall.sf.net, which looks as though it will be very good. signature.asc Description: This is a digitally signed message part
Re: Intel G33 & FreeBSD 7.x
On Mon, 2008-08-18 at 09:06 +0100, Oliver Peter wrote: > On Mon, 18 Aug 2008 17:16:36 +0930 > "Daniel O'Connor" <[EMAIL PROTECTED]> wrote: > > > Does anyone have a G33 chipset system working in 7.x? > ... > Unfortunately, the drm module does not recognize my chipset > (so I don't have DRI support under X.ORG) - could be a problem with > my hardware. I would like to discuss that later this week on the > list with more information. > > Cheers. Robert Noland posted last Wednesday on x11@ [1] that he had prepared an update to FreeBSD's drm kernel modules, which includes support for the G33 [2]. Cheers Tom [1] http://docs.freebsd.org/cgi/getmsg.cgi?fetch=36408+0 +archive/2008/freebsd-x11/20080817.freebsd-x11 [2] http://people.freebsd.org/~rnoland signature.asc Description: This is a digitally signed message part
Re: umtxn and Apache 2.2
On Wed, 2008-08-13 at 16:56 +0200, Borja Marcos wrote: > > Doesn't seem stripped to me... > > %file /usr/local/sbin/httpd > /usr/local/sbin/httpd: ELF 32-bit LSB executable, Intel 80386, version > 1 (FreeBSD), for FreeBSD 7.0 (700110), dynamically linked (uses shared > libs), FreeBSD-style, not stripped Ok, so thats the httpd binary - what about libapr, libapr-util, PHP and all your PHP extensions - are they compiled with debug and not stripped? :) Personally, I find PHP far too troublesome to run threaded. These days, I use an event MPM based front-end apache 2.2, which reverse proxies to either a prefork MPM apache 2.2 with mod_, or directly connect to a fastcgi instance. Serve all your static content from the front-end, and it's all quite fast - plus you can scale out much much more simply. Cheers Tom signature.asc Description: This is a digitally signed message part
Re: challenge: end of life for 6.2 is premature with buggy 6.3
On Thu, 2008-06-05 at 11:14 -0500, Paul Schmehl wrote: > --On Thursday, June 05, 2008 10:23:55 -0400 John Baldwin <[EMAIL PROTECTED]> > wrote: > > > > FWIW, at Y! 6.3 is more stable than 6.2 (I had a list of about 10 patches > > for > > known deadlocks and kernel panics that were errata candidates for 6.2 that > > never made it into RELENG_6_2 but all of them are in 6.3). We also have > > many > > machines with bge(4) and from our perspective 6.3 has less issues with bge0 > > devices than 6.2. > > > > I'm glad to hear that. I have a server that uses bce, and it was completely > non-functional until I hunted down some beta code that made it usable. I'd > like to upgrade, but this is a critical server with no redundancy (and it's a > hobby site with no money to pay for expensive support), and I'm not about to > upgrade unless I know for certain the problems won't reoccur, because I have > to > upgrade remotely and pay money if the system goes down. > > The problems with that driver were bad enough when the server was being > configured in my study. (The system would lock up, and only a hard reboot > would restore networking.) It would be hell trying to troubleshoot problems > if > I had to drive the 45 miles to the hosting site and spend a night there > trying > to get the server back up, then go to work the next day. > > # uname -a > FreeBSD www.stovebolt.com 6.1-RELEASE-p10 FreeBSD 6.1-RELEASE-p10 #2: Mon Oct > 16 15:38:02 CDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC > i386 > > # grep bce /var/run/dmesg.boot > bce0: mem > 0xf400-0xf5ff irq 16 at device 0.0 on pci9 > bce0: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz > miibus0: on bce0 > bce0: Ethernet address: 00:13:72:fb:2a:ad > bce1: mem > 0xf800-0xf9ff irq 16 at device 0.0 on pci5 > bce1: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz > miibus1: on bce1 > bce1: Ethernet address: 00:13:72:fb:2a:ab > > # grep bce0 /var/log/messages > May 2 09:10:31 www kernel: bce0: link state changed to DOWN > May 2 09:10:39 www kernel: bce0: link state changed to UP > May 25 07:49:49 www kernel: bce0: link state changed to DOWN > May 25 07:50:31 www kernel: bce0: link state changed to UP > May 26 21:28:36 www kernel: bce0: link state changed to DOWN > May 26 21:28:40 www kernel: bce0: link state changed to UP > May 27 13:13:21 www kernel: bce0: link state changed to DOWN > May 27 13:13:31 www kernel: bce0: link state changed to UP > > It's been like that since the server was installed. > > So, if I upgrade to 6.3 or 7.0, am I still going to experience these > problems? > Is the server going to stop working entirely? How can I know that for sure > before starting an upgrade? > > Because, I have a 7.0 STABLE workstation (I'm sending this email from it) > with > a serious problem with umass, and no fix seems to be forthcoming. On a > workstation, I can work around problems. On a critical server, not so much. > > Look, I know this is open source, all volunteer (hell, I'm a port maintainer > myself) and guys' time is extremely valuable (whose isn't?), but it seems to > me > there needs to be better communication between the folks who know the code > and > those who only run boxes. You might be able to read diffs and say, "Aha, > they've fixed the problem", but I can't. I don't know, if I upgrade to 6.3, > if > the server will stop passing packets or not. And I can't take the chance > that > it will. > > Saying put up or shut up isn't going to win many friends. I can't use the > server for testing. It's a website with 5 to 7 million hits per month. > > MInd you, I haven't complained about this and I'm not complaining now. I'm > simply saying it would be more productive if folks *listened* to what people > say about a particular problem and gave it some thought before firing salvos > at > the "complainers" and demanding that they contribute to solving the problem > somehow. > > -- > Paul Schmehl I think that, especially with open source products, there is a large emphasis on testing in your own environments, and choosing the 'correct' version of a particular software package is important. For example, at $JOB, we had a lot of servers running 6.1 as it was an extended lifetime release, so no point jumping to 6.2, instead we waited for 6.3 to pass our integration testing. We buy usually the same chassis for all our servers, and test extensively before deploying to a new chassis/OS/anything. This is the definition of change management, which is expensive, takes lots of time and planning, and doesn't guarantee zaroo bugs - just a high likelihood of not hitting them. It also isn't smooth, when we tested 6.1, we found a multitude of bugs in bce(4), which we worked with net@ and David Christensen of Broadcom to get fixed (they work lovely now :). If you don't want to do this sort of work, then yes, things may fail unexpectedly (sort of unexpectedly, I would c
Re: Release Schedule 7.1
On Thu, 2008-05-08 at 20:07 -0700, Jason C. Wells wrote: > What are the hoped for release dates for 7.1? (plus or minus a month) > I'm debating on running 7.0 vs 7.1 and timing is a consideration. > > Regards, > Jason Scheduled releases are listed on the release engineering page. http://www.freebsd.org/releng/index.html You might notice there aren't any. RELENG_7 / 7-STABLE is as close as you will get to 7.1 for a long while. Tom signature.asc Description: This is a digitally signed message part
Re: panics on 6.3-RELEASE in IP stack
On Mon, 2008-04-21 at 11:27 -0400, Michael Proto wrote: > Robert Watson wrote: > > > > On Fri, 18 Apr 2008, Bruce M. Simpson wrote: > > > >>> I concur, this fix should really be MFCed. The problem went away in > >>> 7.x due to a total rewrite. I am distracted by other stuff at the > >>> moment, so, starter's orders... > >> > >> This just bit me. The fix is in RELENG_6, but it is not present after > >> the -p1 tag. So updating to STABLE should fix the problem for Petr. > >> > >> Whilst 6 is no longer the STABLE branch, I think this really should go > >> onto 6 in case any other releases happen from that branch. > > > > There are (tentative) plans to release a 6.4-RELEASE, but I don't think > > there's a schedule yet. Developers should plan on continuing to merge > > changes, especially bug fixes, to RELENG_6. > > > > Robert N M Watson > > Computer Laboratory > > University of Cambridge > > ___ > > Just a note that I'd really like it for a 6.4-RELEASE to be made > available if possible. I still have some hosts on 6-STABLE for a variety > of reasons (including one very nasty problem with 7-STABLE, pf, and > IPSec with NAT traversal that I'm trying to troubleshoot in preparation > for a possible PR, once I find out exactly where the problem is). > > > Thanks, > Proto Remember that 6.3-RELEASE is an extended support release, and will be maintained by the Security Team until (estimated) Jan 31, 2010 - as will 6-STABLE. http://www.freebsd.org/security/ Cheers Tom signature.asc Description: This is a digitally signed message part
Re: umass causes panic on 7 amd64
On Sat, 2008-04-19 at 08:46 +1000, Peter Jeremy wrote: > On Thu, Apr 17, 2008 at 07:13:17PM -0400, Garrett Wollman wrote: > >In my experience, umass over EHCI has never worked on any machine > >ever, going back to 5.x and over multiple kinds of umass devices. (I > >never saw panics, only triple-fault CPU resets.) > > OTOH, I've had mixed results, though I haven't seen panics caused by > EHCI. umass has a tendency to panic when it trips over an interface > bug between bus_dmamem_alloc(9) and contigmalloc(9) which has been > present since at least 4.x, though the work-arounds have improved and > this is less of a problem than it was 3 years ago. > > On my laptop (HP nx6125, ATI SB400 chipset), I haven't had any problems > with EHCI in 6.x or 7.0 (both amd64 - I can't recall if I've tried ECHI > whilst running i386). > > My son's laptop (HP V6107au, nVIDIA MCP51 chipset, 6.x/amd64) gives > varying results (sometimes it works, sometimes it doesn't) and he's > found that plugging flashdisks into the USB hub on his keyboard gives > better results than plugging them into the system (which doesn't make > sense to me - they still show a attached to EHCI). > > My work desktop (Dell OptiPlex GX620, Intel ICH7 chipset 7.0/amd64) > refuses to acknowledge EHCI devices - it just reports timeouts and > disables that USB port. [See my recent posting to -amd64]. > Is the keyboard hub self powered? Maybe some devices draw more current than expected, causing fragile bus powered ports to fail (which would quickly cause a panic). Tom signature.asc Description: This is a digitally signed message part
Re: INET6 required for SCTP in 7.0?
On Wed, 2008-03-05 at 15:46 +0100, Ruben van Staveren wrote: > On 5 Mar 2008, at 15:32, Mark Andrews wrote: > > >> - IPv6 provides almost no technological upgrades beyond additional > >> address > >> space. DHCP addressed the auto configuration feature, VPNs addressed > >> IPsec. > > > > That extra address space really is a big advantage. It > > really is so much better to be able to get to machines you > > need to without have to manually setup application relays > > because you couldn't get enough address space to be able > > to globally address everything want to. > > Please see http://www.youtube.com/watch?v=_y36fG2Oba0 > > This song exactly explains why you should care about IPv6 :) > > I don't get this "anti IPv6" behaviour. If people are not willing to > adopt it, it will not get tested which in turn will make other people > hesitating to jump on the bandwagon. Having it compiled in your system > does not cause harm if you don't configure it and for everything else > there are traffic filters. Just like IPv4. > > - Ruben Sorry to stir a hornets nest, but this[1] is why people have a distrust of IPv6. This clearly is not a failing of IPv6, but it would still catch people out who do not use IPv6, but have it enabled as part of a 'default' configuration. If you don't use something at all, the chance of it having or exposing some semi-related bug is not worth the risk. [1] http://docs.freebsd.org/cgi/getmsg.cgi?fetch=5422+0 +current/freebsd-announce signature.asc Description: This is a digitally signed message part
Re: sched_ule performance on single CPU
On Wed, 2008-04-16 at 00:20 -0700, Unga wrote: > > Sorry for my late reply. > > What I mentioned is a fact, that I always do. Yep, the > music listening is not affected at all when building > world on both 4BSD and ULE. > > Please note my processor is 3Ghz, may be it can take > such a load. > > Second, I run the buildworld lessor priority than the > music player and the browser. > > Third, have sufficient RAM so that it doesn't swap. > > Unga > Just my 2p worth. I run musicpd, streaming via icecast with 4-5 clients, on a not crazy fast 1.8 GHz Core Duo (*not* Core 2 Duo :), which is also a desktop system and running a number of development web servers in C++, python, ruby. I've only got a GB of RAM, so I am perennially swapping. With SCHED_4BSD, running a make world would result in the music stopping lots. With SCHED_ULE it never skips or pauses, and, with acceptable waits for processes to get swapped back in, the desktop remains very usable. I don't build world with a reduced priority either. ULE is a very, very good scheduler IMHO :) Now, if only I could stop Firefox leaking insane amounts of memory, I wouldn't even need a RAM upgrade :) Tom signature.asc Description: This is a digitally signed message part
Re: The Design and Implementation of the FreeBSD Operating System
On Fri, 2008-03-14 at 07:41 -0700, Unga wrote: > Hi all > > Is the following book still relevant to FreeBSD 7.X > and upcoming FreeBSD 8.X? Is there a 2nd edition > coming soon? > > The Design and Implementation of the FreeBSD Operating > System > By Marshall Kirk McKusick, George V. Neville-Neil > Published Aug 2, 2004 by Addison Wesley Professional. > 1st. Edition > ISBN-10: 0-201-70245-2 > http://www.informit.com/title/0201702452 > > Many thanks in advance. > > Kind regards > Unga > > It isn't completely up-to date, as it covers FreeBSD 5, but 5 marked the introduction of the smp-ng code, so it is not hugely incorrect. I recently acquired it and am finding it very useful and informative. Cheers Tom signature.asc Description: This is a digitally signed message part
Re: musicpd segfaults on run - was advised that it's an issue with the system
On Mon, 2008-03-10 at 11:06 -0600, Ross Penner wrote: > On Mon, Mar 10, 2008 at 4:40 AM, Tom Evans <[EMAIL PROTECTED]> wrote: > > > > musicpd doesn't really like playing with libthr. I find remapping libthr > > using /etc/libmap.conf is an adequate workaround on 7.0. > > > > [/usr/local/bin/mpd] > > libthr.so.3 libpthread.so.2 > > > > FYI, with this setup, mpd plays nicely with icecast on 7.0 > > > > Tom > > > > I'm trying this and I'm getting a problem with libmap. > > rosbox# /usr/local/etc/rc.d/musicpd start > Starting musicpd. > /libexec/ld-elf.so.1: /lib/libpthread.so.2: version FBSD_1.0 required > by /usr/local/bin/mpd not found > > I'm not sure how to proceed to fix this problem. > > Thanks for the help, > > Ross Ah lovely, I guess this is non-supported behaviour I am relying on! I'm still running 7.0-PRERELEASE, having tracked CURRENT and RELENG_7 since it's branch, so it is possible this library is different on my system than it is supposed to be -or possibly vice versa - my /lib/libpthread.so.2 certainly does have version FBSD_1.0 (tested with the ever reliable strings and grep..). Can anyone advise here? Who has the wrong libs? :) Tom signature.asc Description: This is a digitally signed message part
Re: musicpd segfaults on run - was advised that it's an issue with the system
On Fri, 2008-03-07 at 23:07 -0700, Ross Penner wrote: > Hi, > > I've recently run the upgrade gamut and moved from 6.3 to 7.0. I've > had a few hick ups but this one I can't resolve. I used musicpd > (http://www.freshports.org/audio/musicpd/) on 6.3 to stream to a > shoutcast server. When I start mpd on 7.0, it immediately has a > segmentation fault and dumps its core. > > I discussed the issue in the musicpd irc channel and I was advised > that it seemed like it was an issue with the system, not with musicpd. > Since upgrading to 7.0, I've reinstalled all my ports and since > discovering the problem, I've reinstalled musicpd specifically. The > backtrace from gdb is as follows: > > #0 0x28140b15 in pthread_setcancelstate () from /lib/libthr.so.3 > #1 0x281388ac in open () from /lib/libthr.so.3 > #2 0x286ac269 in __stack_chk_fail () from /lib/libssp.so.0 > #3 0x in ?? () > #4 0xbfbfe6a8 in ?? () > #5 0x28084ead in _rtld_thread_init () from /libexec/ld-elf.so.1 > Previous frame inner to this frame (corrupt stack?) > > > Any help or direction I can get to finding the solution to this > problem would be greatly appreciated. musicpd doesn't really like playing with libthr. I find remapping libthr using /etc/libmap.conf is an adequate workaround on 7.0. [/usr/local/bin/mpd] libthr.so.3 libpthread.so.2 FYI, with this setup, mpd plays nicely with icecast on 7.0 Tom signature.asc Description: This is a digitally signed message part
Re: What's new on the 127.0.0/24 block in 7?
On Tue, 2008-03-04 at 00:03 -0800, Chris H. wrote: > Hello Mark. Thank you for your thoughtful reply. > FWIW I'm hosting my own zone, out of my domain's address using a > different host name. I'm simply forwarding the requests to a different > port, so as to prevent port collision with the BIND. The zones are > answered our of 127.0.0.2 || 3. > I have absolutely no idea why FBSD v7 (on 2 machines) will only > dole out 127.0.0.1, while all my other servers running RELENG_6 all > dole out a /minimum/ of 127.0.0.1/8 by default. This makes absolutely no sense. My FreeBSD 7 laptop has lo0 configured as 127.0.0.1/8 - THAT IS TO SAY, it has an IP address of 127.0.0.1 and a netmask of 255.0.0.0 . All other 7 boxes I test have the same, as do all the 6.1, 6.2 and 6.3 boxes. Pray, what netmask does your lo0 have, given that you insist it has 127.0.0.1/32 ? This would show up in ``ifconfig lo0'' as inet 127.0.0.1 netmask 0x I very much doubt it is. Tom signature.asc Description: This is a digitally signed message part
Re: I tried to install 7.0 today and had problems.
On Fri, 2008-02-29 at 07:43 -0800, Jeremy Chadwick wrote: > On Fri, Feb 29, 2008 at 12:06:28AM -0700, geek wrote: > > I tried to install 7.0 on a computer with an ABIT AV8 motherboard. This > > board > > has an integrated NIC and the installer didn't find it. > > The board uses a native VIA NIC (never seen this one before myself): > > http://www.uabit.com/index.php?option=com_content&task=view&id=32&Itemid=48&page=1&model=175 > http://www.legitreviews.com/images/reviews/116/vialan.jpg > > > This same machine works just fine with 6.2. > > What driver (interface name, e.g. vge, vr, etc.) gets loaded on 6.2? > This could help determine where the regression is. > I used to use this board (well, AV-8 Deluxe) with 7-CURRENT (its sitting in a cardboard box now), its a VIA VT6122, and worked fine with vge(4). I'd have to cannibalise a number of systems to test it now though. geek: does ``kldload if_vge; ifconfig vge0''not work for you? If not, what does /var/log/messages say? Tom signature.asc Description: This is a digitally signed message part
Re: Re:more than 4gb of RAM (configurations)
On Wed, 2008-02-20 at 13:41 -0500, Zaphod Beeblebrox wrote: > On Feb 19, 2008 5:10 PM, Kevin K <[EMAIL PROTECTED]> wrote: > > > I have a box that we recently installed 16GB of RAM on. The box is i386 > > FreeBSD 6.2. It only recognizes 4gb. > > > Siding with most of the group (go amd64), I'll add my own comment: > > Using PAE to access 4G of RAM (because 4G shows up as 2.5 to 3.5 gig, > depending on the motherboard) under i386 is a reasonable solution, IMHO. > Maybe even 6 gig or 8 gig... if you're trying to extend the life of an ia32 > server. > > But with amd64 supporting ia32 binaries well, it seems the only reason left > might be drivers --- except ... are there _any_ drivers that support PAE and > _not_ amd64? > We use this system while we slowly port our 32 bit code to 64 bit. There are some outstanding unresolved issues running 32 bit binaries on 64 bit (or at least, on 6.2-RELEASE-p8). http://www.mail-archive.com/freebsd-stable@freebsd.org/msg94092.html This should be fixed, although I've not tested whether 7.0 (and the change to gcc 4.2.1) might fix this anyway. Tom signature.asc Description: This is a digitally signed message part
