Re: FreeBSD 7.2-STABLE boot freeze
On Fri, 2 Oct 2009, kama wrote: Do you get this message in all cases? That is, every time you tried? Or only with ACPI_DEBUG defined? I cant recall. I have tried so many things lately. But I believe I get it on a verbose boot without ACPI_DEBUG. Im currently rebuilding the system to 8.0. Just upgrading to 8.0 did not help regarding the freezes. I ran into the bge freeze bug too when disabling acpi. I then read the acpi-manpage abit more carefully. With ACPI_DEBUG and debug.acpi.disabled=timer in loader.conf and verbose boot seems to help against the freeze and freezes again if I dont run it in verbose mode. But thats just after 5 starts. Anyhow its better. loader.conf: debug.acpi.disabled=timer debug.acpi.layer=ACPI_ALL_COMPONENTS debug.acpi.level=ACPI_LV_VERBOSE,ACPI_LV_VERBOSITY3,ACPI_LV_VERBOSITY1,ACPI_LV_ALL_EXCEPTIONS I just wanted to bump this. After the checkout yesterday and installation today I still get these freezes. # cat /boot/loader.conf hw.bge.allow_asf=0 hw.acpi.verbose=1 debug.acpi.max_threads=1 debug.acpi.disabled=timer debug.acpi.layer=ACPI_ALL_COMPONENTS debug.acpi.level=ACPI_LV_VERBOSE,ACPI_LV_VERBOSITY3,ACPI_LV_VERBOSITY1,ACPI_LV_ALL_EXCEPTIONS # With this setup and with an GENERIC kernel I am able to boot if I choose a verbose boot. I dont know why it should work with these. If I only use debug.acpi.disabled=timer it will freeze. Is there anyway for me to get more info when it exactly freezes. Like having it print out to the screen when it enters and leaves functions or something. Im not to familiar with where to put these and its quite a large project for me to start to understand where everything goes. If someone wants to give me patches or specify which files to alter and how I print to the screen during boot I might be able to pinpoint where it freezes and mail in the results. /Bjorn ___ 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: Extreme console latency during disk IO (8.0-RC1, previous releases also affected according to others)
Ivan Voras wrote: Another data point - the OS in the VM in question hanged today sometime after 5 AM in the following way: * console nonresponsive (also to ctrl-alt-del) * ssh login nonresponsive (timeout) * ping works (!) Judging by the last seen timestamp, the machine should have been in the process of receiving rsync backups - so IO-bound. It looks like something really could be fishy in this area, at least with VMWare. The same thing happened again, and I have an additional data point: I left 'top' running on the console and when I attached the VMWare console to the VM, the top was still running ok, but as soon as I hit a key on the keyboard, the OS console locked up. All other symptoms were as I enumerated above. ___ 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: bootless!
On Fri, 2009-10-16 at 21:13 -0400, Randy Bush wrote: i386 running 7.2 as of aug 29 twe, gmirrored boot partition, zfs universe cvsupped 24 hours ago new kernel world will not boot. get beastie but stops at first twirly can boot old kernel -s, but not new kernel can not use old kernel with new world, hangs if i try to /etc/rc.d/zfs start A few questions: Have you cvsupped to 7-STABLE or 8? Are you using ZFS root? Do you get anything extra with boot -v? Have you tried your old loader (/boot/loader.old)? Gavin ___ 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: Make release process for 7.2-STABLE @ r198084
On Sunday 18 October 2009 7:16:41 pm jhell wrote: I have just been setting up a release cycle for making some iso's of my own for a modified revision of the source that I am going to be using for offline use and run into a repetitive copy that I am hoping someone could shed some light on. Output from a make release run. Portion in question - [...] cd /usr/obj/RELENG/usr cp -R -H /usr/src src rm -rf /usr/obj/RELENG/usr/ports cd /usr/obj/RELENG/usr cp -R -H /usr/ports ports # If there are distfiles downloaded removing them rm -rf ports/distfiles/* rm -rf /usr/obj/RELENG/usr/doc cd /usr/obj/RELENG/usr cp -R -H /usr/doc doc if [ -d /usr/src/release/../../ports/distfiles/ ]; then cp -rp /usr/src/release/../../ports/distfiles /usr/obj/RELENG/usr/ports/distfiles; else mkdir -p /usr/obj/RELENG/usr/ports/distfiles; fi From the above output and what happened my ports tree was copied over along with the distfiles the first time cp was issued on the ports directory. Then shortly after that it removes the copied distfiles and issues the next command to copy the docs over. After it does a test for ../../ports/distfiles from the release directory which happens to be the same directory it previously copied over and then removed and is now issuing a command to copy over again?. Is there a problem with the layout of directories from which I started this process maybe? Fault in the script for make release possibly ? Did I miss some tunable for the make release ? From this setup for a make release everything is a default type of structure/setup/layout for ports and source and doc from a install. If I have to do this again I don't want to copy over 4+ GiB of distfiles twice. Thanks. I think this is a property of using EXTPORTSDIR. Generally releases are built against a CVS repo and the ports tree is checked out from that. I would suggestion changing the 'cp' of ports from EXTPORTSDIR to instead do something fancier that excludes copying distfiles in the first place. -- John Baldwin ___ 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
Regression in dhclient?
I just noticed that my dhclient.conf file seems to be ignored in
8.0. Worked fine in 7.2.
interface ath0 {
send host-name slan.XXX.YYY;
prepend domain-name XXX.YYY ;
append domain-name-servers 198.128.W.ZZ;
}
When I look at /etc/resolv.conf, neither the domain-name is added nor te
dns-server. No errors or anything else in the logs.
Anyone else see this or do I have a local problem?
--
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: ober...@es.net Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751
___
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: Regression in dhclient?
Date: Mon, 19 Oct 2009 19:49:33 +
From: Tom Judge t...@tomjudge.com
Kevin Oberman wrote:
I just noticed that my dhclient.conf file seems to be ignored in
8.0. Worked fine in 7.2.
interface ath0 {
send host-name slan.XXX.YYY;
prepend domain-name XXX.YYY ;
append domain-name-servers 198.128.W.ZZ;
}
Your interface is wrong, it should be wlanX not athX
When I look at /etc/resolv.conf, neither the domain-name is added nor te
dns-server. No errors or anything else in the logs.
Anyone else see this or do I have a local problem?
/me hangs head in shame.
This change to the use of wlan0 has bitten me several places, but this
is the first time I did not eventually spot it myself.
Thanks, Tom.
--
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: ober...@es.net Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751
___
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: Regression in dhclient?
Kevin Oberman wrote:
I just noticed that my dhclient.conf file seems to be ignored in
8.0. Worked fine in 7.2.
interface ath0 {
send host-name slan.XXX.YYY;
prepend domain-name XXX.YYY ;
append domain-name-servers 198.128.W.ZZ;
}
Your interface is wrong, it should be wlanX not athX
When I look at /etc/resolv.conf, neither the domain-name is added nor te
dns-server. No errors or anything else in the logs.
Anyone else see this or do I have a local problem?
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: bootless!
i386 running 7.2 as of aug 29 twe, gmirrored boot partition, zfs universe cvsupped 24 hours ago new kernel world will not boot. get beastie but stops at first twirly can boot old kernel -s, but not new kernel can not use old kernel with new world, hangs if i try to /etc/rc.d/zfs start A few questions: Have you cvsupped to 7-STABLE or 8? Are you using ZFS root? Do you get anything extra with boot -v? Have you tried your old loader (/boot/loader.old)? really dead ended with old systems. no, root not zfs. the post mortem by a friend: friday morning, while trying to solve some other problem (i no longer remember what), randy did a make installworld that broke psg.com's ability to use its zfs filesystems. obvious answer was to revert, but that turns out to be easier to say than to do with /usr offline. friday's attempts to roll back via net and remote hands failed, so randy diverted to seattle. after further whackiness on saturday with randy in the westin with a crash cart, it became clear that, even using the pre-zfs filesystems that had been sitting idle since the move to zfs, the machine was too messed up to be able to run make world. many programs (eg, ln) were failing with sigsys errors due to some kind of mismatch between userland and kernel. so we installed freebsd 7.2 from distro media onto a blank usb hard drive, whacked the bios with a club until it admitted to being able to boot from usb, and used that disk as a stable build platform capable of running csup and make world. this didn't solve the problem, but got us far enough that randy could check out of the westin. after further antics, gyrations, sacrifices of rubber chickens, and some sleep, we finally got zfs back up, installed new world and kernel, fixed all the things we had broken (well, that we could remember or had logged), and got the machine back up and running on its filesystems, with just enough time left for randy to eat dinner and head for the ferry to catch a red eye bound for nanog. so that's where we are now: randy's in transit and everything seems back to normal. initially exim was groaning under the load of a weekend's mail backlog, but that looks to be calming down. -30- ___ 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
