Re: Process stuck in STOP state
Hi, Full back-trace is located here: http://aqua.pixnet.tw/~jnlin/textdump/event3/1226/ On Fri, Dec 26, 2008 at 11:34 AM, Lin Jui-Nan Eric wrote: > Hi, > > No, NFS is not working (df hangs, and cd /nfs/vol hangs, too). we have > run fstat and see some NFS file is opened. > I will do a full back-trace while this happened again. (It happens > very frequentlyabout 10 times/day now) > > On Fri, Dec 26, 2008 at 11:26 AM, Alfred Perlstein wrote: >> * Lin Jui-Nan Eric [081225 02:44] wrote: >>> Hi, >>> >>> We have done a textdump, located here: >>> http://aqua.pixnet.tw/~jnlin/textdump/ >>> Thank you! >> >> Is NFS working when this happens? >> >> Can you run lsof too? >> >> It would be really good to get a backtrace from all processes, there's >> a ddb command to do this. >> >> -Alfred >> >>> >>> On Wed, Dec 24, 2008 at 11:07 AM, Alfred Perlstein >>> wrote: >>> > * Lin Jui-Nan Eric [081223 09:17] wrote: >>> >> > Dear listers, >>> >> > >>> >> > Our FreeBSD Server uses NFS to access PHP files on NetApp, then serve >>> >> > them with apache 2.2 (worker MPM + php fastcgi mode). >>> >> Sorry. we use -STABLE now. >>> >> >>> >> event# uname -a >>> >> FreeBSD event 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #1: Thu Dec 4 >>> >> 01:45:42 CST 2008 r...@event:/usr/obj/usr/src/sys/KERNEL amd64 >>> >> ___ >>> >> 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" >>> > >>> > It'd be good if you could get to ddb and do a "show all" >>> > or "threads" and get all threads backtrace to see what's happening. >>> > >>> > thank you, >>> > -- >>> > - Alfred Perlstein >>> > >>> ___ >>> freebsd-stable@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" >> >> -- >> - Alfred Perlstein >> > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Process stuck in STOP state
Hi, No, NFS is not working (df hangs, and cd /nfs/vol hangs, too). we have run fstat and see some NFS file is opened. I will do a full back-trace while this happened again. (It happens very frequentlyabout 10 times/day now) On Fri, Dec 26, 2008 at 11:26 AM, Alfred Perlstein wrote: > * Lin Jui-Nan Eric [081225 02:44] wrote: >> Hi, >> >> We have done a textdump, located here: http://aqua.pixnet.tw/~jnlin/textdump/ >> Thank you! > > Is NFS working when this happens? > > Can you run lsof too? > > It would be really good to get a backtrace from all processes, there's > a ddb command to do this. > > -Alfred > >> >> On Wed, Dec 24, 2008 at 11:07 AM, Alfred Perlstein >> wrote: >> > * Lin Jui-Nan Eric [081223 09:17] wrote: >> >> > Dear listers, >> >> > >> >> > Our FreeBSD Server uses NFS to access PHP files on NetApp, then serve >> >> > them with apache 2.2 (worker MPM + php fastcgi mode). >> >> Sorry. we use -STABLE now. >> >> >> >> event# uname -a >> >> FreeBSD event 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #1: Thu Dec 4 >> >> 01:45:42 CST 2008 r...@event:/usr/obj/usr/src/sys/KERNEL amd64 >> >> ___ >> >> 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" >> > >> > It'd be good if you could get to ddb and do a "show all" >> > or "threads" and get all threads backtrace to see what's happening. >> > >> > thank you, >> > -- >> > - Alfred Perlstein >> > >> ___ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > > -- > - Alfred Perlstein > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Process stuck in STOP state
* Lin Jui-Nan Eric [081225 02:44] wrote: > Hi, > > We have done a textdump, located here: http://aqua.pixnet.tw/~jnlin/textdump/ > Thank you! Is NFS working when this happens? Can you run lsof too? It would be really good to get a backtrace from all processes, there's a ddb command to do this. -Alfred > > On Wed, Dec 24, 2008 at 11:07 AM, Alfred Perlstein wrote: > > * Lin Jui-Nan Eric [081223 09:17] wrote: > >> > Dear listers, > >> > > >> > Our FreeBSD Server uses NFS to access PHP files on NetApp, then serve > >> > them with apache 2.2 (worker MPM + php fastcgi mode). > >> Sorry. we use -STABLE now. > >> > >> event# uname -a > >> FreeBSD event 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #1: Thu Dec 4 > >> 01:45:42 CST 2008 r...@event:/usr/obj/usr/src/sys/KERNEL amd64 > >> ___ > >> 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" > > > > It'd be good if you could get to ddb and do a "show all" > > or "threads" and get all threads backtrace to see what's happening. > > > > thank you, > > -- > > - Alfred Perlstein > > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" -- - Alfred Perlstein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 7.1-RC2: link_elf: symbol cp_time undefined
Garrett Cooper wrote: On Dec 25, 2008, at 3:44, Jan Henrik Sylvester wrote: During boot I see: link_elf: symbol cp_time undefined I have realized it now with RC2, but looking at my logs, I have had that message during boot since upgrading this machine from 7.0-RELEASE to 7.1-RC1 via freebsd-update a at Dec-8. (I did recompile kernel modules from ports: fusefs-kmod and kqemu-kmod.) What is the easiest way to find out what tried to link to the unknown symbol? The context in which the messages appear is: savecore: no dumps found Initial i386 initialization:. Additional ABI support: linux. Starting local daemons:kldload: can't load ntfs: File exists link_elf: symbol cp_time undefined kldload: can't load linprocfs: No such file or directory link_elf: symbol cp_time undefined mount: linprocfs : Operation not supported by device . Updating motd. Starting fusefs. fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 Mounting late file systems:. In my rc.local, I have kldload ntfs kldload linprocfs mount -t linprocfs linprocfs /usr/compat/linux/proc which used to work (I think). /boot/kernel/linprocfs.ko does exist. Cheers, Jan Henrik Did you compile your kernel from scratch? -Garrett No, it came with freebsd-update (every possible freebsd-update since the install from the 7.0-BETA4 CD). Outside /etc, the IDS function of freebsd-update only reports a mismatch for /boot/kernel/linker.hints -- can this be the problem? (I will try to replace it tomorrow.) Cheers, Jan Henrik ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 7.1-RC2: link_elf: symbol cp_time undefined
On Dec 25, 2008, at 3:44, Jan Henrik Sylvester wrote: During boot I see: link_elf: symbol cp_time undefined I have realized it now with RC2, but looking at my logs, I have had that message during boot since upgrading this machine from 7.0- RELEASE to 7.1-RC1 via freebsd-update a at Dec-8. (I did recompile kernel modules from ports: fusefs-kmod and kqemu-kmod.) What is the easiest way to find out what tried to link to the unknown symbol? The context in which the messages appear is: savecore: no dumps found Initial i386 initialization:. Additional ABI support: linux. Starting local daemons:kldload: can't load ntfs: File exists link_elf: symbol cp_time undefined kldload: can't load linprocfs: No such file or directory link_elf: symbol cp_time undefined mount: linprocfs : Operation not supported by device . Updating motd. Starting fusefs. fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 Mounting late file systems:. In my rc.local, I have kldload ntfs kldload linprocfs mount -t linprocfs linprocfs /usr/compat/linux/proc which used to work (I think). /boot/kernel/linprocfs.ko does exist. Cheers, Jan Henrik Did you compile your kernel from scratch? -Garrett ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: amd(8) cores dump when load high
On Tue, 23.12.2008 at 00:44:53 +0800, Lin Jui-Nan Eric wrote: > Dear listers, > > We currently found that amd frequently cores dump while loading is > high (about 4~5) after we upgrade world & kernel from 7.0-RELEASE to > 7.1-PRERELEASE. > > I have read -stable and svn log of 7-STABLE, but can not found a > report or a solution. Did anyone have the same issue? Thank you very > much. Ever since I switched from file-based NSS to LDAP, amd(8) has been crashing on me almost every day, especially if there's no LDAP server available during boot (ie. the laptop is not on the home network). It looks like the error handling in NSS requests could be improved, but I've yet to investigate the whole matter. Load plays no role in amd(8) crashing (at least for me). Cheers, Ulrich Spoerlein -- It is better to remain silent and be thought a fool, than to speak, and remove all doubt. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD 7.1-RC2 Available...
FreeBSD 7.1-RC2 is now available, the second of the Release Candidates.
Unless an as yet undiscovered show-stopper comes along the release
itself will be anywhere from a week to two weeks from now. We *might*
be doing it next week since the release test cycle has gone on for quite
a while now and the latest thing that delayed the release was a Security
Advisory (SAs don't typically get or need much in the way of public
testing). The traffic we're seeing on the lists and in Gnats is
certainly stuff we'll pay attention to and deal with but isn't quite
severe enough to warrant further delaying an already severely delayed
release.
NOTE: If updating from a 7.0 or earlier system due to a change in the
Vendor's drivers certain Intel NICs will now come up as igb(4) instead
of em(4). We normally try to avoid changes like that in stable branches
but the vendor felt it necessary in order to support the new adapters.
See the UPDATING entry dated 20080811 for details. There are only 3 PCI
ID's that should have their name changed from em(4) to igb(4): 0x10A7,
0x10A9, and 0x10D6. You should be able to determine if your card will
change names by running the command "pciconf -l", and for the line
representing your NIC (should be named em on older systems, e.g. em0 or
em1, etc) check the fourth column. If it says "chip=0x10a7" (or one of
the other two IDs given above) you will have the adapter's name change.
The ISO images and FTP install trees are available on the FreeBSD Mirror
sites. Using the primary site as an example:
ftp://ftp.freebsd.org/pub/FreeBSD/releases/${arch}/ISO-IMAGES/7.1/
where ${arch} is one of amd64, i386, ia64, pc98, or sparc64. The
powerpc architecture builds haven't completed quite yet.
The ISOs for amd64, i386, and sparc64 include what is expected to be the
final package set. For all architectures the ISOs with "disc" in their
names are CDROM-sized, if you intend to install a variety of packages
during installation you will need all three. For amd64 and i386 there
is a gzip-ed iso with "dvd" in its name which is DVD-sized. It contains
everything (install bits, livefs, docs, and packages) and can be used if
your machine has a DVD drive in it.
If you would like to do a source-based update to 7.1-RC2 from an already
installed machine you can update your tree to RELENG_7_1 using normal
cvsup/csup methods. Note that due to an unfortunate side-effect of the
"real" source code repository now being in SVN it will look like all
files have a new version so mergemaster may be a bit tedious.
The freebsd-update(8) utility supports binary upgrades of i386 and amd64
systems running earlier FreeBSD releases. Systems running 7.0-RELEASE,
7.1-BETA, 7.1-BETA2, or 7.1-RC1 can upgrade as follows:
# freebsd-update upgrade -r 7.1-RC2
During this process, FreeBSD Update may ask the user to help by merging
some configuration files or by confirming that the automatically performed
merging was done correctly.
# freebsd-update install
The system must be rebooted with the newly installed kernel before continuing.
# shutdown -r now
After rebooting, freebsd-update needs to be run again to install the new
userland components, and the system needs to be rebooted again:
# freebsd-update install
# shutdown -r now
Users of Intel network interfaces which are changing their name from "em" to
"igb" should make necessary changes to configuration files BEFORE running
freebsd-update, since otherwise the network interface will not be configured
appropriately after rebooting for the first time.
Users of earlier FreeBSD releases (FreeBSD 6.x) can also use freebsd-update to
upgrade to FreeBSD 7.1, but will be prompted to rebuild all third-party
applications (e.g., anything installed from the ports tree) after the second
invocation of "freebsd-update install", in order to handle differences in the
system libraries between FreeBSD 6.x and FreeBSD 7.x.
Checksums:
MD5 (7.1-RC2-amd64-bootonly.iso) = 5eae06e1a07402dc31ccda6414c4c480
MD5 (7.1-RC2-amd64-disc1.iso) = 4635c72b9b37f7df6697f6e06a020949
MD5 (7.1-RC2-amd64-disc2.iso) = 53eefb2082bb123b831b8637eca7e22d
MD5 (7.1-RC2-amd64-disc3.iso) = 62ed3347923bb094f8070c01f171e215
MD5 (7.1-RC2-amd64-docs.iso) = 5942546ada3aa9e8d4bd3fe70add61e3
MD5 (7.1-RC2-amd64-dvd1.iso) = 42a33c01cea05f4507743cf04ec50dbe
MD5 (7.1-RC2-amd64-livefs.iso) = 200acb39f0fa76dc5f655480ce18ea43
MD5 (7.1-RC2-i386-bootonly.iso) = 5b0234a090009c575fece7c0009aa616
MD5 (7.1-RC2-i386-disc1.iso) = 90c6c1d1fa46ce6ca79d4e9c210b5a4a
MD5 (7.1-RC2-i386-disc2.iso) = d28477d9679ee9af1da17db97ea6f4ec
MD5 (7.1-RC2-i386-disc3.iso) = 90f79ed26697cdb1492e86bbb8169508
MD5 (7.1-RC2-i386-docs.iso) = eb4ab4b087d73a8e72ca836c14067baa
MD5 (7.1-RC2-i386-dvd1.iso) = 74cd8c4a5a1c1dc33389018c152feb71
MD5 (7.1-RC2-i386-livefs.iso) = b72de0770b9d35e051f99cf21ef67f6e
MD5 (7.1-RC2-ia64-bootonly.iso) = aeccc0ef9e82d89dc2ce391ed8d6de41
MD5 (7.1-RC2-ia64-disc1.iso) = 401dddb2a02d1270921a9b8b23a248c1
MD5 (7.1-RC2-ia64-dis
7.1-RC2: link_elf: symbol cp_time undefined
During boot I see: link_elf: symbol cp_time undefined I have realized it now with RC2, but looking at my logs, I have had that message during boot since upgrading this machine from 7.0-RELEASE to 7.1-RC1 via freebsd-update a at Dec-8. (I did recompile kernel modules from ports: fusefs-kmod and kqemu-kmod.) What is the easiest way to find out what tried to link to the unknown symbol? The context in which the messages appear is: savecore: no dumps found Initial i386 initialization:. Additional ABI support: linux. Starting local daemons:kldload: can't load ntfs: File exists link_elf: symbol cp_time undefined kldload: can't load linprocfs: No such file or directory link_elf: symbol cp_time undefined mount: linprocfs : Operation not supported by device . Updating motd. Starting fusefs. fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 Mounting late file systems:. In my rc.local, I have kldload ntfs kldload linprocfs mount -t linprocfs linprocfs /usr/compat/linux/proc which used to work (I think). /boot/kernel/linprocfs.ko does exist. Cheers, Jan Henrik ___ 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: Process stuck in STOP state
Hi, We have done a textdump, located here: http://aqua.pixnet.tw/~jnlin/textdump/ Thank you! On Wed, Dec 24, 2008 at 11:07 AM, Alfred Perlstein wrote: > * Lin Jui-Nan Eric [081223 09:17] wrote: >> > Dear listers, >> > >> > Our FreeBSD Server uses NFS to access PHP files on NetApp, then serve >> > them with apache 2.2 (worker MPM + php fastcgi mode). >> Sorry. we use -STABLE now. >> >> event# uname -a >> FreeBSD event 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #1: Thu Dec 4 >> 01:45:42 CST 2008 r...@event:/usr/obj/usr/src/sys/KERNEL amd64 >> ___ >> 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" > > It'd be good if you could get to ddb and do a "show all" > or "threads" and get all threads backtrace to see what's happening. > > thank you, > -- > - Alfred Perlstein > ___ 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"
