Re: livelocks and deadlocks on 8.0BETA2
Kevin Oberman wrote: Then it got worse. The second time this happened, I inserted an erased DVD while the system was in POST. The system started to boot, but, shortly after probing acd0, while the boot was waiting for: usbus7 usbus6 usbus5 usbus4 usbus3 usbus2 usbus1 usbus0, and about the time it should have probed for cd0 (atapicam), the system locked up and would not finish the boot. This is prior to mounting root. After several repeats of this, I ejected the disk from the drive and it booted just fine. Clearly something with ATAPI is not happy. Should I not be using atapicam with 8.0? This one is old one. I get it sometimes since 7.0 (perhaps, 6.x affected too) on my desktop and it sometimes repeats with 8.0-BETA2 too (GENERIC kernel). It's some kind of race condition because it does not always hang, but often enough to be annoying. There should be a media in drive to make it happen, blank or written. Eugene Grosbein ___ 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
Quick 8.0 update: BETA3 builds in progress
For those tracking the 8.0 release process, BETA3 builds have now started. They were held up for a few days while a few critical issues were resolved: - Changes to make newbus MPSAFE were reverted as they lead to reports of a number of WITNESS warnings and panics during device driver attach/detach. - Another nit in the Subversion-CVS updater was resolved. - The flowtable crash at boot reported by several users has been resolved. - A boot-time hang for users of the htprr driver has been resolved. - ZFS zpool import was fixed. - freebsd-update now backs up the old kernel before installing a new one. You can find a regularly updated release status, the above information, and much more, on the 8.0 release engineering wiki page: http://wiki.freebsd.org/8.0TODO I don't have a specific ETA on BETA3 going out the door, except to say that so far several architectures have reported back on successful builds, so probably quite soon. Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Upgrade FreeBSD 7.1 to 7.2
On Fri, 21 Aug 2009, Miroslav Lachman wrote: I would like to do a binary upgrade from 7.1 to 7.2. I've seen the instructions here: http://www.freebsd.org/releases/7.2R/announce.html I've heard that it's safest to start the machine in single user mode when doing upgrades, but I see no notice about it in the announcement. So my question is: Is it ok to do this binary upgrade without start single user mode first? If no, must I reboot my machine to enter single user mode? I always did upgrade in multiuser for minimalising the downtime of servers. I always do it this way, but accept the risk involved. I actually did my 7.x - 8.x upgrade on my web/shell server this way, with users logged in, but I think that's probably only for the brave of heart. FWIW, the main problem I ran into with my 8.0 upgrade is that 8.0 uses the uart(4) driver for serial ports, and sio(4), 7.2's default, has been removed. They require mutually exclusive lines in device.hints and different /etc/ttys lines. If you rely on a serial console, I would recommend first switching 7.2 to using uart, pausing for a bit, and then switching forward to 8 so that you separate the risks associated with changing console drivers from those associated with sliding a major kernel version. Robert ___ 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
RELENG_8: buildworld stops on usr.bin/rpcgen
Good day!
I'm want to build the system from RELENG_8 (BETA3 for now) tree to give
it a try.
# mv /usr/src /usr/src.old
# csup stable-supfile
{ *default host=cvsup.FreeBSD.org,
*default release=cvs tag=RELENG_8
}
# cat /etc/make.conf
WITH_GECKO=libxul
WITH_PYTHON=yes
WITHOUT_JAVA=yes
PERL_VERSION=5.10.0
WITH_APACHE=2.2+
MALLOC_PRODUCTION=yes
# ls -l /etc/malloc.conf
lrwxr-xr-x 1 root wheel 2 21 авг 15:45 /etc/malloc.conf - aj
# uname -srp
FreeBSD 7.2-STABLE i386
# sysctl kern.osreldate
kern.osreldate: 702104
# cd /usr/src
# make clean rm -rf /usr/obj/*
# make buildworld make kernel KERNCONF=BEST8
...
=== usr.bin/rpcgen (obj,depend,all,install)
/usr/obj/usr/src/tmp/usr/src/usr.bin/rpcgen created for
/usr/src/usr.bin/rpcgen
rm -f .depend
mkdep -f .depend -a-I/usr/obj/usr/src/tmp/legacy/usr/include
/usr/src/usr.bin/rpcgen/rpc_main.c /usr/src/usr.bin/rpcgen/rpc_clntout.c
/usr/src/usr.bin/rpcgen/rpc_cout.c /usr/src/usr.bin/rpcgen/rpc_hout.c
/usr/src/usr.bin/rpcgen/rpc_parse.c /usr/src/usr.bin/rpcgen/rpc_sample.c
/usr/src/usr.bin/rpcgen/rpc_scan.c /usr/src/usr.bin/rpcgen/rpc_svcout.c
/usr/src/usr.bin/rpcgen/rpc_tblout.c /usr/src/usr.bin/rpcgen/rpc_util.c
/usr/src/usr.bin/rpcgen/rpc_clntout.c:46:23: error: rpc/types.h: No such
file or directory
/usr/src/usr.bin/rpcgen/rpc_parse.c:46:23: error: rpc/types.h: No such
file or directory
mkdep: compile failed
*** Error code 1
Stop in /usr/src/usr.bin/rpcgen.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
# grep \$FreeBSD /usr/src/sys/rpc/types.h
* $FreeBSD: src/sys/rpc/types.h,v 1.13.4.1 2009/08/03 08:13:06 kensmith
Exp $
# grep \$FreeBSD /usr/src/include/rpc/types.h
grep: /usr/src/include/rpc/types.h: No such file or directory
Can anybody confirm this or it's some my local problem?
Thanks in advance,
Ruslan
___
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: Blocked process
On Fri, 21 Aug 2009, CmdLnKid wrote: came back or the machine was rebooted. I continued for a while using /var/mail over NFS while setting or unset mail variables for the shell. You may also want to check into whether something is trying to acquire a lock on a file over that NFS mount which could accrue some extra time making it seem like a process is hung. We don't have any NFS mounts so I don't think that's it :( -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
Re: Quick 8.0 update: BETA3 builds in progress
At 06:04 AM 8/22/2009, Robert Watson wrote: I don't have a specific ETA on BETA3 going out the door, except to say that so far several architectures have reported back on successful builds, so probably quite soon. Just an FYI about builds, the HEAD tinderbox after getting a hardware update is now building RELENG_8 as well http://tinderbox.freebsd.org/ ---Mike Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Quick 8.0 update: BETA3 builds in progress
I don't have a specific ETA on BETA3 going out the door, except to say that so far several architectures have reported back on successful builds, so probably quite soon. Is there any point in making bug reports for BETA2 at this point ? I only got to try it a coupleof days ago, and had a big issue with installing (had to use 7.2 to partition the drive) but I am thinkingthat maybe just waiting and re-doing the test with BETA3 is better ? cheers, -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Quick 8.0 update: BETA3 builds in progress
On Sat, 22 Aug 2009, Pete French wrote: I don't have a specific ETA on BETA3 going out the door, except to say that so far several architectures have reported back on successful builds, so probably quite soon. Is there any point in making bug reports for BETA2 at this point ? I only got to try it a coupleof days ago, and had a big issue with installing (had to use 7.2 to partition the drive) but I am thinkingthat maybe just waiting and re-doing the test with BETA3 is better ? I think it's probably more useful to wait a day and retry with BETA3. I don't know that the issue you're experiencing has been fixed, but given that there were some partitioning-related fixes (see the wiki page for a complete list) it's possible that something like it was. Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Blocked process
On Sat, 22 Aug 2009, Daniel O'Connor wrote: On Fri, 21 Aug 2009, CmdLnKid wrote: came back or the machine was rebooted. I continued for a while using /var/mail over NFS while setting or unset mail variables for the shell. You may also want to check into whether something is trying to acquire a lock on a file over that NFS mount which could accrue some extra time making it seem like a process is hung. We don't have any NFS mounts so I don't think that's it :( Hi Daniel-- A number of issues were corrected over the course of the 6.x life span involving scheduing, including some relating to lost wakeups. Many bug fixes relating to threading were also introduced (not sure if that's relevant to your workload). While it's never a particularly fun recommendation, I think I'd suggest sliding forward to the most recent 6.x kernel (but otherwise identical configuration), perhaps sticking with your current userspace, and seeing if that resolves the issue. Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Blocked process
On Sat, 22 Aug 2009, Robert Watson wrote: On Sat, 22 Aug 2009, Daniel O'Connor wrote: On Fri, 21 Aug 2009, CmdLnKid wrote: came back or the machine was rebooted. I continued for a while using /var/mail over NFS while setting or unset mail variables for the shell. You may also want to check into whether something is trying to acquire a lock on a file over that NFS mount which could accrue some extra time making it seem like a process is hung. We don't have any NFS mounts so I don't think that's it :( A number of issues were corrected over the course of the 6.x life span involving scheduing, including some relating to lost wakeups. Many bug fixes relating to threading were also introduced (not sure if that's relevant to your workload). While it's never a particularly fun recommendation, I think I'd suggest sliding forward to the most recent 6.x kernel (but otherwise identical configuration), perhaps sticking with your current userspace, and seeing if that resolves the issue. OK, should be feasible to do that I think. Luckily people at this site don't need to drive for a few hours to fix the PC :) Thanks. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
