[releng_8_2 tinderbox] failure on powerpc/powerpc
TB --- 2012-02-03 07:12:50 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-02-03 07:12:50 - starting RELENG_8_2 tinderbox run for powerpc/powerpc TB --- 2012-02-03 07:12:50 - cleaning the object tree TB --- 2012-02-03 07:13:21 - cvsupping the source tree TB --- 2012-02-03 07:13:21 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8_2/powerpc/powerpc/supfile TB --- 2012-02-03 07:14:41 - building world TB --- 2012-02-03 07:14:41 - CROSS_BUILD_TESTING=YES TB --- 2012-02-03 07:14:41 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-03 07:14:41 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-03 07:14:41 - SRCCONF=/dev/null TB --- 2012-02-03 07:14:41 - TARGET=powerpc TB --- 2012-02-03 07:14:41 - TARGET_ARCH=powerpc TB --- 2012-02-03 07:14:41 - TZ=UTC TB --- 2012-02-03 07:14:41 - __MAKE_CONF=/dev/null TB --- 2012-02-03 07:14:41 - cd /src TB --- 2012-02-03 07:14:41 - /usr/bin/make -B buildworld >>> World build started on Fri Feb 3 07:14:41 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri Feb 3 08:00:02 UTC 2012 TB --- 2012-02-03 08:00:02 - generating LINT kernel config TB --- 2012-02-03 08:00:02 - cd /src/sys/powerpc/conf TB --- 2012-02-03 08:00:02 - /usr/bin/make -B LINT TB --- 2012-02-03 08:00:02 - cd /src/sys/powerpc/conf TB --- 2012-02-03 08:00:02 - /usr/sbin/config -m LINT TB --- 2012-02-03 08:00:02 - building LINT kernel TB --- 2012-02-03 08:00:02 - CROSS_BUILD_TESTING=YES TB --- 2012-02-03 08:00:02 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-03 08:00:02 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-03 08:00:02 - SRCCONF=/dev/null TB --- 2012-02-03 08:00:02 - TARGET=powerpc TB --- 2012-02-03 08:00:02 - TARGET_ARCH=powerpc TB --- 2012-02-03 08:00:02 - TZ=UTC TB --- 2012-02-03 08:00:02 - __MAKE_CONF=/dev/null TB --- 2012-02-03 08:00:02 - cd /src TB --- 2012-02-03 08:00:02 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Feb 3 08:00:02 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Fri Feb 3 08:15:17 UTC 2012 TB --- 2012-02-03 08:15:17 - cd /src/sys/powerpc/conf TB --- 2012-02-03 08:15:17 - /usr/sbin/config -m GENERIC TB --- 2012-02-03 08:15:17 - building GENERIC kernel TB --- 2012-02-03 08:15:17 - CROSS_BUILD_TESTING=YES TB --- 2012-02-03 08:15:17 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-03 08:15:17 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-03 08:15:17 - SRCCONF=/dev/null TB --- 2012-02-03 08:15:17 - TARGET=powerpc TB --- 2012-02-03 08:15:17 - TARGET_ARCH=powerpc TB --- 2012-02-03 08:15:17 - TZ=UTC TB --- 2012-02-03 08:15:17 - __MAKE_CONF=/dev/null TB --- 2012-02-03 08:15:17 - cd /src TB --- 2012-02-03 08:15:17 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Feb 3 08:15:18 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Fri Feb 3 08:25:41 UTC 2012 TB --- 2012-02-03 08:25:41 - cd /src/sys/powerpc/conf TB --- 2012-02-03 08:25:41 - /usr/sbin/config -m MPC85XX TB --- 2012-02-03 08:25:41 - building MPC85XX kernel TB --- 2012-02-03 08:25:41 - CROSS_BUILD_TESTING=YES TB --- 2012-02-03 08:25:41 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-03 08:25:41 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-03 08:25:41 - SRCCONF=/dev/null TB --- 2012-02-03 08:25:41 - TARGET=powerpc TB --- 2012-02-03 08:25:41 - TARGET_ARCH=powerpc TB --- 2012-02-03 08:25:41 - TZ=UTC TB --- 2012-02-03 08:25:41 - __MAKE_CONF=/dev/null TB --- 2012-02-03 08:25:41 - cd /src TB --- 2012-02-03 08:25:41 - /usr/bin/make -B buildkernel KERNCONF=MPC85XX >>> Kernel build for MPC85XX started on Fri Feb 3 08:25:41 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O -pipe -std=c99 -Wa,-me500 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --pa
sentex tinderbox build cluster failures
Mike, For many days now (almost a week?) there have been tinderbox build mails coming from the sentex.ca build cluster, specific to powerpc, mips, and sparc64 platforms. The errors in question are strange and may indicate some kind of filesystem corruption or equivalent -- I'm really not sure. Breaking them down: powerpc/powerpc, RELENG_8_2 -- /src/sys/powerpc/booke/platform_bare.c:82: error: expected '}' before ';' token This file hasn't been touched in over 2 months: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/powerpc/booke/platform_bare.c mips/mips, RELENG_8_2 -- /src/sys/mips/alchemy/obio.c:513: warning: pointer type mismatch in conditional expression This file hasn't been touched in over 2 months: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/mips/alchemy/obio.c mips/mips, RELENG_8_1 -- In file included from /src/sys/mips/sentry5/siba_cc.c:58: /src/sys/dev/siba/sibavar.h:487: error: field 'sd_id' has incomplete type /src/sys/dev/siba/sibavar.h:526: error: 'SIBA_MAX_CORES' undeclared here (not in a function) src/sys/mips/sentry5/siba_cc.c has been Attic'd, and the last time it was touched was 14 months ago: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/mips/sentry5/Attic/siba_cc.c src/sys/dev/siba/sibavar.h hasn't been touched in over 2 months: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/siba/sibavar.h All recent tinderbox failures for RELENG_8 (for mips, ia64, and sparc64) appear to be related to a commit Jack did ~7 hours ago, and are almost certainly temporary/transient errors (e.g. csup/cvs pulldown didn't get the full commit). So we can ignore those. The others need to be investigated though. Users on the freebsd-stable lists have been complaining about these continual errors, so I was wondering if they're being investigated. I also got one off-list mail from someone personally asking me if I knew what could be going on or had any insights to this (not sure why that person thought that -- I have nothing to do with tinderbox :-) ). Let us know if you could. Thanks! -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | 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"
[releng_8 tinderbox] failure on i386/i386
TB --- 2012-02-03 08:06:42 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-02-03 08:06:42 - starting RELENG_8 tinderbox run for i386/i386 TB --- 2012-02-03 08:06:42 - cleaning the object tree TB --- 2012-02-03 08:06:42 - cvsupping the source tree TB --- 2012-02-03 08:06:42 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/i386/i386/supfile TB --- 2012-02-03 08:07:42 - building world TB --- 2012-02-03 08:07:42 - CROSS_BUILD_TESTING=YES TB --- 2012-02-03 08:07:42 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-03 08:07:42 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-03 08:07:42 - SRCCONF=/dev/null TB --- 2012-02-03 08:07:42 - TARGET=i386 TB --- 2012-02-03 08:07:42 - TARGET_ARCH=i386 TB --- 2012-02-03 08:07:42 - TZ=UTC TB --- 2012-02-03 08:07:42 - __MAKE_CONF=/dev/null TB --- 2012-02-03 08:07:42 - cd /src TB --- 2012-02-03 08:07:42 - /usr/bin/make -B buildworld >>> World build started on Fri Feb 3 08:07:42 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri Feb 3 08:54:36 UTC 2012 TB --- 2012-02-03 08:54:36 - generating LINT kernel config TB --- 2012-02-03 08:54:36 - cd /src/sys/i386/conf TB --- 2012-02-03 08:54:36 - /usr/bin/make -B LINT TB --- 2012-02-03 08:54:37 - cd /src/sys/i386/conf TB --- 2012-02-03 08:54:37 - /usr/sbin/config -m LINT TB --- 2012-02-03 08:54:37 - building LINT kernel TB --- 2012-02-03 08:54:37 - CROSS_BUILD_TESTING=YES TB --- 2012-02-03 08:54:37 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-03 08:54:37 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-03 08:54:37 - SRCCONF=/dev/null TB --- 2012-02-03 08:54:37 - TARGET=i386 TB --- 2012-02-03 08:54:37 - TARGET_ARCH=i386 TB --- 2012-02-03 08:54:37 - TZ=UTC TB --- 2012-02-03 08:54:37 - __MAKE_CONF=/dev/null TB --- 2012-02-03 08:54:37 - cd /src TB --- 2012-02-03 08:54:37 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Feb 3 08:54:37 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] :> hack.c cc -shared -nostdlib hack.c -o hack.So rm -f hack.c MAKE=/usr/bin/make sh /src/sys/conf/newvers.sh LINT cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue vers.c linking kernel ld: kernel: Not enough room for program headers (allocated 5, need 6) ld: final link failed: Bad value *** Error code 1 Stop in /obj/i386/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-02-03 09:06:25 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-02-03 09:06:25 - ERROR: failed to build LINT kernel TB --- 2012-02-03 09:06:25 - 2765.86 user 488.41 system 3582.98 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-i386-i386.full ___ 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 9 crash/deadlock when dump(8)ing file system with journaling enabled.
Hi, what would be the best choice? 1. turn off SUJ and dump using -L flag and the turn it on again (but I'm affraid to destroy the system this way - is this possible?) 2. dump the unmounted partitions with a live cd, per example Sorry for top posting, mobile mail client problem. Em 30/01/2012 12:56, "Ivan Voras" escreveu: On 30/01/2012 13:06, Jeremy Chadwick wrote: >> For now I've turned off journaling (soft updates see... It's a known bug: SU+J currently deadlocks when used with UFS snapshots. ___ freebsd-stable@freebsd.org mailing list http://li... ___ 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 9 crash/deadlock when dump(8)ing file system with journaling enabled.
On Fri, Feb 03, 2012 at 06:45:58AM -0200, Marcel Bonnet wrote: > Hi, what would be the best choice? > > 1. turn off SUJ and dump using -L flag and the turn it on again (but I'm > affraid to destroy the system this way - is this possible?) > 2. dump the unmounted partitions with a live cd, per example > > Sorry for top posting, mobile mail client problem. > > Em 30/01/2012 12:56, "Ivan Voras" escreveu: > > On 30/01/2012 13:06, Jeremy Chadwick wrote: > > >> For now I've turned off journaling (soft updates see... > It's a known bug: SU+J currently deadlocks when used with UFS snapshots. Is there a reason you require use of dump(8) over, say, rsync/rsnapshot or similar tools? As far as disabling the journalling aspect of SU+J on-the-fly (meaning on a mounted filesystem), I don't think this is possible, but I will state boldly up front I have not messed around with 9.0 at all aside from tinkering about in the installer. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | 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: FreeBSD 9 crash/deadlock when dump(8)ing file system with journaling enabled.
On 2/3/2012 15:45, Marcel Bonnet wrote: Hi, what would be the best choice? 1. turn off SUJ and dump using -L flag and the turn it on again (but I'm affraid to destroy the system this way - is this possible?) Yes, this is what I have done for my 9.0 servers. Unfortunately you need to be in single user mode if you need to change /'s setting. This is because you cannot change this option while a file system is mounted read+write. Rebooting into single user mode is the easiest way to do this, as it leaves you with / mounted read only and everything else dismounted for you. Then I ran: tunefs -j disable / For each volume that journaling was enabled for. As a side note remove the .sujournal file in the base of each volume afterwards as it just takes up space. After doing this I have been using dump(8) nightly via cron(8) for about a week now under 9.0 without issue. Running it on 11 servers currently. 2. dump the unmounted partitions with a live cd, per example Sorry for top posting, mobile mail client problem. Em 30/01/2012 12:56, "Ivan Voras"escreveu: On 30/01/2012 13:06, Jeremy Chadwick wrote: For now I've turned off journaling (soft updates see... It's a known bug: SU+J currently deadlocks when used with UFS snapshots. ___ freebsd-stable@freebsd.org mailing list http://li... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 9 crash/deadlock when dump(8)ing file system with journaling enabled.
On 3 February 2012 08:23, Adam Strohl wrote: > On 2/3/2012 17:15, Adam Strohl wrote: >> >> After doing this I have been using dump(8) nightly via cron(8) for about a >> week now under 9.0 without issue. Running it on 11 servers currently. >> > > P.S. > To be clear, I am using dump with -L (snapshots) without issue. > Okay, thanks! If we do that with our server, I'll post the result. -- Marcel Bonnet ___ 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 9 crash/deadlock when dump(8)ing file system with journaling enabled.
On 2/3/2012 17:15, Adam Strohl wrote: After doing this I have been using dump(8) nightly via cron(8) for about a week now under 9.0 without issue. Running it on 11 servers currently. P.S. To be clear, I am using dump with -L (snapshots) without issue.
Sector size of a zvol
So, I was trying to create a disc witha sector size of 4096 bytes, and I assumed that simply creating a zvol with that blocksize would do the trick. But it appears that whatever the blocksize is on the xvol, diskinfo is reporting the sector size as 512 bytes. I this the intended behaviour ? I dont have a Solaris system to hand to test it on, so I have no ida if this is BSD specific or not. 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"
FreeBSD 9: Group quotas increase but don't decrease automatically
I'm running FreeBSD 9 on a number of systems and finally decided to take advantage of the quota system to enforce limits on my users. No real issues setting it all up aside from finding that http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/quotas.html needs to be updated. The new /etc/rc.conf entry is quota_enable="YES" not enable_quotas="YES" as it says (assuming it used to be this in 8.x?). I'll file a PR for this shortly. I did however run into a more serious issue (I think): A group or user's allocation as reported by repquota(8) will increases with new/growing files, however when a file is deleted or chgrped out of the quota's group, the amount of space reported by repquota(8) does not decrease. I have verified that the system does not register the freed space by going over the soft limit, being denied write, then deleting files. Even if I delete files which drop me below the soft quota limit, I will not be able to add them as I am still "over quota".So it does not appear to be reporting issue, the system really doesn't realize the usage has gone down. Interestingly the inode counts do decrease automatically/"instantly" as I would expect. Running quotacheck(8) fixes the issue and updates the allocation counts, but does not magically fix auto-updating, so needs to be done periodically which can be a bit intensive depending on file count. I see this on all FreeBSD 9 machines with quotas turned on. For now I have a cron script which tries to guess (based on changing inode counts, etc) if it should run quotacheck, and does so if needed (to avoid just blindly running it periodically). Anyone else run into this? Am I missing something? Known issue? Let me know if anyone wants more info, etc. I can also paste the work around "smart" cron script if anyone is interested (and I'm not missing something silly :P). -- Adam Strohl A-Team Systems http://ateamsystems.com/ ___ 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: sentex tinderbox build cluster failures
On 2/3/2012 3:48 AM, Jeremy Chadwick wrote: > Mike, > > For many days now (almost a week?) there have been tinderbox build mails > coming from the sentex.ca build cluster, specific to powerpc, mips, and > sparc64 platforms. Hi, I will let des@freebsd speak to the errors. We host the boxes here, but he is in charge of them and better understands the issue ---Mike > > The errors in question are strange and may indicate some kind of > filesystem corruption or equivalent -- I'm really not sure. > > Breaking them down: > > powerpc/powerpc, RELENG_8_2 -- > > /src/sys/powerpc/booke/platform_bare.c:82: error: expected '}' before > ';' token > > This file hasn't been touched in over 2 months: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/powerpc/booke/platform_bare.c > > mips/mips, RELENG_8_2 -- > > /src/sys/mips/alchemy/obio.c:513: warning: pointer type mismatch in > conditional expression > > This file hasn't been touched in over 2 months: > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/mips/alchemy/obio.c > > mips/mips, RELENG_8_1 -- > > In file included from /src/sys/mips/sentry5/siba_cc.c:58: > /src/sys/dev/siba/sibavar.h:487: error: field 'sd_id' has incomplete > type > /src/sys/dev/siba/sibavar.h:526: error: 'SIBA_MAX_CORES' undeclared > here (not in a function) > > src/sys/mips/sentry5/siba_cc.c has been Attic'd, and the last > time it was touched was 14 months ago: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/mips/sentry5/Attic/siba_cc.c > > src/sys/dev/siba/sibavar.h hasn't been touched in over 2 months: > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/siba/sibavar.h > > All recent tinderbox failures for RELENG_8 (for mips, ia64, and sparc64) > appear to be related to a commit Jack did ~7 hours ago, and are almost > certainly temporary/transient errors (e.g. csup/cvs pulldown didn't get > the full commit). So we can ignore those. > > The others need to be investigated though. > > Users on the freebsd-stable lists have been complaining about these > continual errors, so I was wondering if they're being investigated. > I also got one off-list mail from someone personally asking me if I knew > what could be going on or had any insights to this (not sure why that > person thought that -- I have nothing to do with tinderbox :-) ). > > Let us know if you could. Thanks! > -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ 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: [releng_8_2 tinderbox] failure on powerpc/powerpc
George Mitchell writes: > Apparently two or three people have all recently checked in code > without first verifying that it compiled (let alone ran), or else > possibly did not completely commit their changes, and then absconded > to a place where they fail to receive these emails about the problems. > Can someone please either diagnose these errors or else revert the > deficient commits? These are old bugs that nobody noticed because they're in code that the tinderbox didn't use to build. They're in releng branches, so fixing them requires re@ and / or so@ approval. DES -- Dag-Erling Smørgrav - d...@des.no ___ 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: sentex tinderbox build cluster failures
Jeremy Chadwick writes: > For many days now (almost a week?) there have been tinderbox build mails > coming from the sentex.ca build cluster, specific to powerpc, mips, and > sparc64 platforms. > > The errors in question are strange and may indicate some kind of > filesystem corruption or equivalent -- I'm really not sure. You could have taken the time to check the code before jumping to conclusions about "filesystem corruption or equivalent". These are genuine bugs. The tinderbox didn't warn about them earlier because it didn't build other kernels than LINT and GENERIC, and these bugs are in machine-dependent code that isn't included in LINT and GENERIC. I enabled additional kernels after the arm / mips people complained that the arm / mips build was sometimes broken for weeks without anybody noticing. DES -- Dag-Erling Smørgrav - d...@des.no ___ 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: [releng_8_2 tinderbox] failure on powerpc/powerpc
On Thursday, February 02, 2012 7:17:14 pm George Mitchell wrote: > On 02/02/12 15:37, FreeBSD Tinderbox wrote: > > [... one of three errors it's been reporting repeatedly for days ...] > Talk about a lack of focus! Apparently two or three people have all > recently checked in code without first verifying that it compiled (let > alone ran), or else possibly did not completely commit their changes, > and then absconded to a place where they fail to receive these emails > about the problems. Can someone please either diagnose these errors or > else revert the deficient commits? -- George Mitchell No, it is more that the tinderbox for 8 wasn't actually checking these kernels before (they have been broken since 8.1 and 8.2 were released) and they are on less-used platforms. I do agree it needs to be cleaned up one way or another. Given the reticence to commit changes to release branches, it is probably simpler to mask this via the tinderbox instead. -- 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"
Re: sentex tinderbox build cluster failures
On Friday, February 03, 2012 3:48:17 am Jeremy Chadwick wrote: > Mike, > > For many days now (almost a week?) there have been tinderbox build mails > coming from the sentex.ca build cluster, specific to powerpc, mips, and > sparc64 platforms. > > The errors in question are strange and may indicate some kind of > filesystem corruption or equivalent -- I'm really not sure. > > Breaking them down: > > powerpc/powerpc, RELENG_8_2 -- > > /src/sys/powerpc/booke/platform_bare.c:82: error: expected '}' before > ';' token > > This file hasn't been touched in over 2 months: > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/powerpc/booke/platform_bare.c > > mips/mips, RELENG_8_2 -- > > /src/sys/mips/alchemy/obio.c:513: warning: pointer type mismatch in conditional expression > > This file hasn't been touched in over 2 months: > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/mips/alchemy/obio.c > > mips/mips, RELENG_8_1 -- > > In file included from /src/sys/mips/sentry5/siba_cc.c:58: > /src/sys/dev/siba/sibavar.h:487: error: field 'sd_id' has incomplete > type > /src/sys/dev/siba/sibavar.h:526: error: 'SIBA_MAX_CORES' undeclared > here (not in a function) > > src/sys/mips/sentry5/siba_cc.c has been Attic'd, and the last > time it was touched was 14 months ago: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/mips/sentry5/Attic/siba_cc.c > > src/sys/dev/siba/sibavar.h hasn't been touched in over 2 months: > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/siba/sibavar.h > > All recent tinderbox failures for RELENG_8 (for mips, ia64, and sparc64) > appear to be related to a commit Jack did ~7 hours ago, and are almost > certainly temporary/transient errors (e.g. csup/cvs pulldown didn't get > the full commit). So we can ignore those. > > The others need to be investigated though. > > Users on the freebsd-stable lists have been complaining about these > continual errors, so I was wondering if they're being investigated. > I also got one off-list mail from someone personally asking me if I knew > what could be going on or had any insights to this (not sure why that > person thought that -- I have nothing to do with tinderbox :-) ). > > Let us know if you could. Thanks! The periodically failing ones are old bugs that were uncovered recently when the tinderbox was fixed to compile kernels for these branches. Most of these bugs are trivial to fix, but require committing a change to release branches which requires a whole bunch of hoopla and red tape (otherwise I would have merged the fixes by now). -- 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"
Re: [releng_8_1 tinderbox] failure on amd64/amd64
FreeBSD Tinderbox writes:
> cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall
> -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes
> -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign
> -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq
> -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common
> -finline-limit=8000 --param inline-unit-growth=100 --param
> large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF
> -fno-builtin -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 -Werror -pg
> -mprofiler-epilogue /src/sys/dev/e1000/if_em.c -I/src/sys/dev/e1000
> if_em.o: No space left on device
> {standard input}: Assembler messages:
> {standard input}:13043: FATAL: Can't write if_em.o: No space left on device
> *** Error code 1
Fixed, sorry for the noise.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
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 supported mps(4) driver in stable/9 and stable/8
Kenneth D. Merry schreef: Hi folks, The LSI-supported version of the mps(4) driver that supports their 6Gb SAS HBAs as well as WarpDrive controllers, is now in stable/9 and stable/8. Please test it out and let me and Kashyap (CCed) know if you run into any problems. In addition to supporting WarpDrive, the driver also supports Integrated RAID. Thanks to LSI for doing the work on this driver! Note that the CAM infrastructure changes that went into FreeBSD/head along with this driver have not gone into either stable/9 or stable/8. Only the driver itself has been merged. The CAM infrastructure changes depend on some other da(4) driver changes that will need to get merged before they can go back. If that merge happens, it will probably only be into stable/9. A couple of notes about issues with this driver: - Unlike the previous mps(4) driver, it probes sequentially. If you have a lot of drives in your system, it will take a while to probe them all. - You may see warning messages like this: _mapping_add_new_device: failed to add the device with handle 0x0019 to persiste nt table because there is no free space available _mapping_add_new_device: failed to add the device with handle 0x001a to persiste nt table because there is no free space available - The driver is not endian safe. (It assumes a little endian machine.) This is not new, the previous version of the driver had the same issue. The LSI folks know about these issues. The driver has passed their testing process. Many thanks to LSI for going through the effort to support FreeBSD. Ken Hello Ken. Just updated our 16 bay server. did a csup today. did try some commands, it looked like the drives got husseled. But after giving the command camcontrol rescan all it does not give back the prompt. Also top shows me the following. 1589 root1 200 16384K 1376K cbwait 3 0:00 0.00% camcontrol # on another console things works filer01# camcontrol devlist at scbus0 target 8 lun 0 (pass0,da0) at scbus0 target 9 lun 0 (pass1,da1) at scbus0 target 10 lun 0 (pass2,da2) at scbus0 target 11 lun 0 (pass3,da3) at scbus0 target 12 lun 0 (pass4,da4) at scbus0 target 13 lun 0 (pass5,da5) at scbus0 target 16 lun 0 (probe16,ses0,pass6) at scbus0 target 17 lun 0 (pass7,da6) at scbus0 target 18 lun 0 (pass8,da7) at scbus0 target 19 lun 0 (pass9,da8) at scbus0 target 20 lun 0 (pass10,da9) at scbus0 target 21 lun 0 (pass11,da10) at scbus0 target 22 lun 0 (pass12,da11) at scbus0 target 23 lun 0 (pass13,da12) at scbus0 target 24 lun 0 (pass14,da13) at scbus0 target 27 lun 0 (pass15,da14) at scbus0 target 28 lun 0 (pass16,da15) at scbus1 target 0 lun 0 (ada0,pass17) at scbus3 target 0 lun 0 (pass18,cd0) The controller is a LSI 9211-8i with IT firmware. here is the dmesg Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-STABLE #0: Fri Feb 3 10:27:18 CET 2012 root@filer01.neuteboom.local:/usr/obj/usr/src/sys/KRNL amd64 CPU: Intel(R) Xeon(R) CPU E31220 @ 3.10GHz (3093.04-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x206a7 Family = 6 Model = 2a Stepping = 7 Features=0xbfebfbff Features2=0x15bae3ff AMD Features=0x28100800 AMD Features2=0x1 TSC: P-state invariant, performance statistics real memory = 17179869184 (16384 MB) avail memory = 16493441024 (15729 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 19 at device 6.0 on pci0 pci1: on pcib1 mps0: port 0xe000-0xe0ff mem 0xfb60-0xfb603fff irq 19 at device 0.0 on pci1 mps0: Firmware: 11.00.00.00, Driver: 11.255.03.00-fbsd mps0: IOCCapabilities: 1285c em0: port 0xf020-0xf03f mem 0xfb80-0xfb81,0xfb824000-0xfb824fff irq 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: Ethernet address: 00:25:90:57:20:bd ehci0: mem 0xfb823000-0xfb8233ff irq 16 at device 26.0 on pci0 usbus0: EHCI version 1.0 usbus0: on ehci0 pcib2: irq 17 at device 28.0 on pci0 pci2: on pcib2 pcib3: irq 17 at device 28.4 on pci0 pci3: on pcib3 em1: port 0xd000-0xd01f mem 0xfb70-0xfb71,0xfb72-0xfb723
Re: Sector size of a zvol
On Fri, February 3, 2012 07:25, Pete French wrote: > So, I was trying to create a disc witha sector size of 4096 bytes, and I > assumed that simply creating a zvol with that blocksize would do the > trick. > But it appears that whatever the blocksize is on the xvol, diskinfo is > reporting the sector size as 512 bytes. > > I this the intended behaviour ? I dont have a Solaris system to hand to > test it on, so I have no ida if this is BSD specific or not. Yes, it is intended. The pool sector size and ZFS dataset block size are parameters are independent of each other. AFAIK, there is no way to specify the sector size to use in a ZFS pool: it is completely automatic when you call "zpool create". Ideally it should query the disk about its sector size and use that, but I don't know if that has been implemented (and can't be bothered to dig through the source at this time :). ___ 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 supported mps(4) driver in stable/9 and stable/8
Hi Johan, I have already figure out this issue in our lab. I also have fix for this issue. (Just don't want to create regression, that is why I have not posted outside) Since you have seen similar issue, It is worth to try my patch. My machine is not getting IP right now. I will send you patch once my machine is in network ? ~ Kashyap > -Original Message- > From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd- > sta...@freebsd.org] On Behalf Of Johan Hendriks > Sent: Friday, February 03, 2012 8:13 PM > To: Kenneth D. Merry > Cc: freebsd-stable > Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 > > Kenneth D. Merry schreef: > > Hi folks, > > > > The LSI-supported version of the mps(4) driver that supports their 6Gb > SAS > > HBAs as well as WarpDrive controllers, is now in stable/9 and > stable/8. > > > > Please test it out and let me and Kashyap (CCed) know if you run into > > any problems. > > > > In addition to supporting WarpDrive, the driver also supports > Integrated > > RAID. > > > > Thanks to LSI for doing the work on this driver! > > > > Note that the CAM infrastructure changes that went into FreeBSD/head > along > > with this driver have not gone into either stable/9 or stable/8. Only > the > > driver itself has been merged. > > > > The CAM infrastructure changes depend on some other da(4) driver > changes > > that will need to get merged before they can go back. If that merge > > happens, it will probably only be into stable/9. > > > > A couple of notes about issues with this driver: > > > > - Unlike the previous mps(4) driver, it probes sequentially. If you > have > > a lot of drives in your system, it will take a while to probe them > all. > > - You may see warning messages like this: > > > > _mapping_add_new_device: failed to add the device with handle 0x0019 > to persiste > > nt table because there is no free space available > > _mapping_add_new_device: failed to add the device with handle 0x001a > to persiste > > nt table because there is no free space available > > > > - The driver is not endian safe. (It assumes a little endian > machine.) > > This is not new, the previous version of the driver had the same > issue. > > > > The LSI folks know about these issues. The driver has passed their > testing > > process. > > > > Many thanks to LSI for going through the effort to support FreeBSD. > > > > Ken > Hello Ken. > > Just updated our 16 bay server. did a csup today. > did try some commands, it looked like the drives got husseled. > > But after giving the command camcontrol rescan all it does not give back > the prompt. > Also top shows me the following. > 1589 root1 200 16384K 1376K cbwait 3 0:00 0.00% > camcontrol > > # on another console things works > filer01# camcontrol devlist > at scbus0 target 8 lun 0 (pass0,da0) > at scbus0 target 9 lun 0 (pass1,da1) > at scbus0 target 10 lun 0 (pass2,da2) > at scbus0 target 11 lun 0 (pass3,da3) > at scbus0 target 12 lun 0 (pass4,da4) > at scbus0 target 13 lun 0 (pass5,da5) > at scbus0 target 16 lun 0 > (probe16,ses0,pass6) > at scbus0 target 17 lun 0 (pass7,da6) > at scbus0 target 18 lun 0 (pass8,da7) > at scbus0 target 19 lun 0 (pass9,da8) > at scbus0 target 20 lun 0 > (pass10,da9) > at scbus0 target 21 lun 0 > (pass11,da10) > at scbus0 target 22 lun 0 > (pass12,da11) > at scbus0 target 23 lun 0 > (pass13,da12) > at scbus0 target 24 lun 0 > (pass14,da13) > at scbus0 target 27 lun 0 > (pass15,da14) > at scbus0 target 28 lun 0 > (pass16,da15) > at scbus1 target 0 lun 0 > (ada0,pass17) > at scbus3 target 0 lun 0 (pass18,cd0) > > The controller is a LSI 9211-8i with IT firmware. > > here is the dmesg > Copyright (c) 1992-2012 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights > reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 9.0-STABLE #0: Fri Feb 3 10:27:18 CET 2012 > root@filer01.neuteboom.local:/usr/obj/usr/src/sys/KRNL amd64 > CPU: Intel(R) Xeon(R) CPU E31220 @ 3.10GHz (3093.04-MHz K8-class CPU) >Origin = "GenuineIntel" Id = 0x206a7 Family = 6 Model = 2a > Stepping = 7 > > Features=0xbfebfbff ,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > Features2=0x15bae3ff SE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,XSAVE,AVX> >AMD Features=0x28100800 >AMD Features2=0x1 >TSC: P-state invariant, performance statistics > real memory = 17179869184 (16384 MB) > avail memory = 16493441024 (15729 MB) > Event timer "LAPIC" quality 600 > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > FreeBSD/SMP: 1 package(s) x 4 core(s) > cpu0 (BSP): APIC ID: 0 > cpu1
Re: FreeBSD 9: Group quotas increase but don't decrease automatically
On Fri, Feb 03, 2012 at 07:30:54PM +0700, Adam Strohl wrote:
> I'm running FreeBSD 9 on a number of systems and finally decided to take
> advantage of the quota system to enforce limits on my users.
>
> No real issues setting it all up aside from finding that
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/quotas.html
> needs to be updated. The new /etc/rc.conf entry is quota_enable="YES"
> not enable_quotas="YES" as it says (assuming it used to be this in
> 8.x?). I'll file a PR for this shortly.
>
> I did however run into a more serious issue (I think):
>
> A group or user's allocation as reported by repquota(8) will increases
> with new/growing files, however when a file is deleted or chgrped out of
> the quota's group, the amount of space reported by repquota(8) does not
> decrease. I have verified that the system does not register the freed
> space by going over the soft limit, being denied write, then deleting
> files. Even if I delete files which drop me below the soft quota limit,
> I will not be able to add them as I am still "over quota".So it does
> not appear to be reporting issue, the system really doesn't realize the
> usage has gone down.
>
> Interestingly the inode counts do decrease automatically/"instantly" as
> I would expect.
>
> Running quotacheck(8) fixes the issue and updates the allocation counts,
> but does not magically fix auto-updating, so needs to be done
> periodically which can be a bit intensive depending on file count.
>
> I see this on all FreeBSD 9 machines with quotas turned on.
>
> For now I have a cron script which tries to guess (based on changing
> inode counts, etc) if it should run quotacheck, and does so if needed
> (to avoid just blindly running it periodically).
>
> Anyone else run into this? Am I missing something? Known issue? Let
> me know if anyone wants more info, etc. I can also paste the work
> around "smart" cron script if anyone is interested (and I'm not missing
> something silly :P).
This is a bug in +J code (even if you do not use +J). Do you have
softupdates enabled on the volume ? If yes, try the following patch.
diff --git a/sys/ufs/ffs/ffs_softdep.c b/sys/ufs/ffs/ffs_softdep.c
index 5b4b6b9..ed2db79 100644
--- a/sys/ufs/ffs/ffs_softdep.c
+++ b/sys/ufs/ffs/ffs_softdep.c
@@ -43,6 +43,7 @@
__FBSDID("$FreeBSD$");
#include "opt_ffs.h"
+#include "opt_quota.h"
#include "opt_ddb.h"
/*
@@ -6428,7 +6429,7 @@ softdep_setup_freeblocks(ip, length, flags)
}
#ifdef QUOTA
/* Reference the quotas in case the block count is wrong in the end. */
- quotaref(vp, freeblks->fb_quota);
+ quotaref(ITOV(ip), freeblks->fb_quota);
(void) chkdq(ip, -datablocks, NOCRED, 0);
#endif
freeblks->fb_chkcnt = -datablocks;
pgpQDka7ROEOo.pgp
Description: PGP signature
Re: Sector size of a zvol
> AFAIK, there is no way to specify the sector size to use in a ZFS pool: it > is completely automatic when you call "zpool create". Ideally it should > query the disk about its sector size and use that, but I don't know if > that has been implemented (and can't be bothered to dig through the source > at this time :). I think we are talking about different things - the sector size used by the zpool on the underlying system is automatic, and may or may not come from the disc sector size (like you, I hope it does, but havent checked ;-) ). But what I am talking about is the sector size presneted by the 'fake' disc that a ZVOL creates - that always seems to be 512 bytes, despite the fact that the zvol blocksize is 8k. Seems odd to me (and that 8k size os alterable, but just doesnt seem to be reflected in the zvol). As it stands I can make a zpool on top of 4k discs, a ZVOL using 8k blocks on top of that, but the things talking to it will use 512 byte chunks, which surely impacts performance ? -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: LSI supported mps(4) driver in stable/9 and stable/8
Desai, Kashyap schreef: Hi Johan, I have already figure out this issue in our lab. I also have fix for this issue. (Just don't want to create regression, that is why I have not posted outside) Since you have seen similar issue, It is worth to try my patch. My machine is not getting IP right now. I will send you patch once my machine is in network ? ~ Kashyap -Original Message- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd- sta...@freebsd.org] On Behalf Of Johan Hendriks Sent: Friday, February 03, 2012 8:13 PM To: Kenneth D. Merry Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Kenneth D. Merry schreef: Hi folks, The LSI-supported version of the mps(4) driver that supports their 6Gb SAS HBAs as well as WarpDrive controllers, is now in stable/9 and stable/8. Please test it out and let me and Kashyap (CCed) know if you run into any problems. In addition to supporting WarpDrive, the driver also supports Integrated RAID. Thanks to LSI for doing the work on this driver! Note that the CAM infrastructure changes that went into FreeBSD/head along with this driver have not gone into either stable/9 or stable/8. Only the driver itself has been merged. The CAM infrastructure changes depend on some other da(4) driver changes that will need to get merged before they can go back. If that merge happens, it will probably only be into stable/9. A couple of notes about issues with this driver: - Unlike the previous mps(4) driver, it probes sequentially. If you have a lot of drives in your system, it will take a while to probe them all. - You may see warning messages like this: _mapping_add_new_device: failed to add the device with handle 0x0019 to persiste nt table because there is no free space available _mapping_add_new_device: failed to add the device with handle 0x001a to persiste nt table because there is no free space available - The driver is not endian safe. (It assumes a little endian machine.) This is not new, the previous version of the driver had the same issue. The LSI folks know about these issues. The driver has passed their testing process. Many thanks to LSI for going through the effort to support FreeBSD. Ken Hello Ken. Just updated our 16 bay server. did a csup today. did try some commands, it looked like the drives got husseled. But after giving the command camcontrol rescan all it does not give back the prompt. Also top shows me the following. 1589 root1 200 16384K 1376K cbwait 3 0:00 0.00% camcontrol # on another console things works filer01# camcontrol devlist at scbus0 target 8 lun 0 (pass0,da0) at scbus0 target 9 lun 0 (pass1,da1) at scbus0 target 10 lun 0 (pass2,da2) at scbus0 target 11 lun 0 (pass3,da3) at scbus0 target 12 lun 0 (pass4,da4) at scbus0 target 13 lun 0 (pass5,da5) at scbus0 target 16 lun 0 (probe16,ses0,pass6) at scbus0 target 17 lun 0 (pass7,da6) at scbus0 target 18 lun 0 (pass8,da7) at scbus0 target 19 lun 0 (pass9,da8) at scbus0 target 20 lun 0 (pass10,da9) at scbus0 target 21 lun 0 (pass11,da10) at scbus0 target 22 lun 0 (pass12,da11) at scbus0 target 23 lun 0 (pass13,da12) at scbus0 target 24 lun 0 (pass14,da13) at scbus0 target 27 lun 0 (pass15,da14) at scbus0 target 28 lun 0 (pass16,da15) at scbus1 target 0 lun 0 (ada0,pass17) at scbus3 target 0 lun 0 (pass18,cd0) The controller is a LSI 9211-8i with IT firmware. here is the dmesg Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-STABLE #0: Fri Feb 3 10:27:18 CET 2012 root@filer01.neuteboom.local:/usr/obj/usr/src/sys/KRNL amd64 CPU: Intel(R) Xeon(R) CPU E31220 @ 3.10GHz (3093.04-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x206a7 Family = 6 Model = 2a Stepping = 7 Features=0xbfebfbff Features2=0x15bae3ff AMD Features=0x28100800 AMD Features2=0x1 TSC: P-state invariant, performance statistics real memory = 17179869184 (16384 MB) avail memory = 16493441024 (15729 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0:<24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 pcib0: port 0xcf8-0x
Re: Sector size of a zvol
On Fri, Feb 3, 2012 at 1:25 PM, Pete French wrote: > So, I was trying to create a disc witha sector size of 4096 bytes, and I > assumed that simply creating a zvol with that blocksize would do the trick. > But it appears that whatever the blocksize is on the xvol, diskinfo is > reporting the sector size as 512 bytes. > > I this the intended behaviour ? I dont have a Solaris system to hand to > test it on, so I have no ida if this is BSD specific or not. > > 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" > You can use the method described here to create a zvol with 4k sector size: http://lists.freebsd.org/pipermail/freebsd-fs/2010-December/010350.html -- :wq ___ 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: Sector size of a zvol
On Fri, February 3, 2012 10:03, Pete French wrote: > [...] But what I am talking about is the sector size > presneted by the 'fake' disc that a ZVOL creates - that always seems > to be 512 bytes, despite the fact that the zvol blocksize is 8k. Seems > odd to me (and that 8k size os alterable, but just doesnt seem to > be reflected in the zvol). As it stands I can make a zpool on top > of 4k discs, a ZVOL using 8k blocks on top of that, but the things > talking to it will use 512 byte chunks, which surely impacts performance ? Try the following from the zfs(1M) man page: zfs create [-ps] [-b blocksize] [-o property=value] ... -V size volume [...] -b blocksize Equivalent to -o volblocksize=blocksize. If this option is specified in conjunction with -o volblocksize, the resulting behavior is undefined. http://www.freebsd.org/cgi/man.cgi?query=zfs Did use "blocksize" or "volblocksize" in your "zfs create" command? A thread for zfs-discus on "volblocksize": http://mail.opensolaris.org/pipermail/zfs-discuss/2005-November/000450.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"
[releng_8_1 tinderbox] failure on mips/mips
TB --- 2012-02-03 15:07:14 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-02-03 15:07:14 - starting RELENG_8_1 tinderbox run for mips/mips TB --- 2012-02-03 15:07:14 - cleaning the object tree TB --- 2012-02-03 15:07:29 - cvsupping the source tree TB --- 2012-02-03 15:07:29 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8_1/mips/mips/supfile TB --- 2012-02-03 15:12:52 - building world TB --- 2012-02-03 15:12:52 - CROSS_BUILD_TESTING=YES TB --- 2012-02-03 15:12:52 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-03 15:12:52 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-03 15:12:52 - SRCCONF=/dev/null TB --- 2012-02-03 15:12:52 - TARGET=mips TB --- 2012-02-03 15:12:52 - TARGET_ARCH=mips TB --- 2012-02-03 15:12:52 - TZ=UTC TB --- 2012-02-03 15:12:52 - __MAKE_CONF=/dev/null TB --- 2012-02-03 15:12:52 - cd /src TB --- 2012-02-03 15:12:52 - /usr/bin/make -B buildworld >>> World build started on Fri Feb 3 15:12:53 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri Feb 3 15:49:28 UTC 2012 TB --- 2012-02-03 15:49:28 - cd /src/sys/mips/conf TB --- 2012-02-03 15:49:28 - /usr/sbin/config -m ADM5120 TB --- 2012-02-03 15:49:28 - building ADM5120 kernel TB --- 2012-02-03 15:49:28 - CROSS_BUILD_TESTING=YES TB --- 2012-02-03 15:49:28 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-03 15:49:28 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-03 15:49:28 - SRCCONF=/dev/null TB --- 2012-02-03 15:49:28 - TARGET=mips TB --- 2012-02-03 15:49:28 - TARGET_ARCH=mips TB --- 2012-02-03 15:49:28 - TZ=UTC TB --- 2012-02-03 15:49:28 - __MAKE_CONF=/dev/null TB --- 2012-02-03 15:49:28 - cd /src TB --- 2012-02-03 15:49:28 - /usr/bin/make -B buildkernel KERNCONF=ADM5120 >>> Kernel build for ADM5120 started on Fri Feb 3 15:49:28 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for ADM5120 completed on Fri Feb 3 15:50:39 UTC 2012 TB --- 2012-02-03 15:50:39 - cd /src/sys/mips/conf TB --- 2012-02-03 15:50:39 - /usr/sbin/config -m IDT TB --- 2012-02-03 15:50:39 - building IDT kernel TB --- 2012-02-03 15:50:39 - CROSS_BUILD_TESTING=YES TB --- 2012-02-03 15:50:39 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-03 15:50:39 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-03 15:50:39 - SRCCONF=/dev/null TB --- 2012-02-03 15:50:39 - TARGET=mips TB --- 2012-02-03 15:50:39 - TARGET_ARCH=mips TB --- 2012-02-03 15:50:39 - TZ=UTC TB --- 2012-02-03 15:50:39 - __MAKE_CONF=/dev/null TB --- 2012-02-03 15:50:39 - cd /src TB --- 2012-02-03 15:50:39 - /usr/bin/make -B buildkernel KERNCONF=IDT >>> Kernel build for IDT started on Fri Feb 3 15:50:39 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for IDT completed on Fri Feb 3 15:52:15 UTC 2012 TB --- 2012-02-03 15:52:15 - cd /src/sys/mips/conf TB --- 2012-02-03 15:52:15 - /usr/sbin/config -m MALTA TB --- 2012-02-03 15:52:15 - building MALTA kernel TB --- 2012-02-03 15:52:15 - CROSS_BUILD_TESTING=YES TB --- 2012-02-03 15:52:15 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-03 15:52:15 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-03 15:52:15 - SRCCONF=/dev/null TB --- 2012-02-03 15:52:15 - TARGET=mips TB --- 2012-02-03 15:52:15 - TARGET_ARCH=mips TB --- 2012-02-03 15:52:15 - TZ=UTC TB --- 2012-02-03 15:52:15 - __MAKE_CONF=/dev/null TB --- 2012-02-03 15:52:15 - cd /src TB --- 2012-02-03 15:52:15 - /usr/bin/make -B buildkernel KERNCONF=MALTA >>> Kernel build for MALTA started on Fri Feb 3 15:52:15 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for MALTA completed on Fri Feb 3 15:53:42 UTC 2012 TB --- 2012-02-03 15:53:42 - cd /src/sys/mips/conf TB --- 2012-02-03 15:53:42 - /usr/sbin/config -m QEMU TB --- 2012-02-03 15:53:42 - building QEMU kernel TB --- 2012-02-03 15:53:42 - CROSS_BUILD_TESTING=YES TB --- 2012-02-03 15:53:42 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-03 15:53:42 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-03 15:53:42 - SRCCONF=/dev/null TB --- 2012-02-03 15:53:42 - TARGET=mips TB --- 2012-02-03 15:53:42 - TARGET_ARCH=mips TB --- 2012-02-03 15:53:42 - TZ=UTC TB --- 2012-02-03 15:53:42 - __MAKE_CONF=/dev/null TB ---
Re: Sector size of a zvol
> Try the following from the zfs(1M) man page: > > zfs create [-ps] [-b blocksize] [-o property=value] ... -V size volume > [...] >-b blocksize > > Equivalent to -o volblocksize=blocksize. If this option is > specified in conjunction with -o volblocksize, the resulting > behavior is undefined. Yes, thats the parameter I have been playing around with - whether you set it with -b or -o volblocksize, the zvol still presents itself as being 512 bytes. This is what is puzzling me. Quick example: # zfs create -V 1G -b 512 tank/test1 # zfs create -V 1G -b 4k tank/test2 # zfs create -V 1G tank/test3 # zfs get volblocksize tank/test1 tank/test2 tank/test3 NAMEPROPERTY VALUE SOURCE tank/test1 volblocksize 512 - tank/test2 volblocksize 4K- tank/test3 volblocksize 8K- # diskinfo /dev/zvol/tank/test* /dev/zvol/tank/test1512 1073741824 2097152 0 0 /dev/zvol/tank/test2512 1073741824 2097152 0 0 /dev/zvol/tank/test3512 1073741824 2097152 0 0 As you can see, the blocksize is being set properly in the volume, but in the actial device it's always 512. Now the reason behind this was to share out a 4k block sizes iscsi target, and I have subsequently discovered that I can set that parameter on istgt which should mitigate the effect, but I still think it is odd. 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: Sector size of a zvol
> You can use the method described here to create a zvol with 4k sector size: > http://lists.freebsd.org/pipermail/freebsd-fs/2010-December/010350.html I saw that, but it describes setting up a zpool, not a zvol - or are you saying that a zvol created on such a zpool will have 4k sectors ? Unfortunately I am not at liberty to recreate the pool on the server, so I cant try it, but thanks for the tip... -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: Sector size of a zvol
On Fri, February 3, 2012 11:05, Pete French wrote: >> You can use the method described here to create a zvol with 4k sector >> size: >> http://lists.freebsd.org/pipermail/freebsd-fs/2010-December/010350.html > > I saw that, but it describes setting up a zpool, not a zvol - or are > you saying that a zvol created on such a zpool will have 4k sectors ? > Unfortunately I am not at liberty to recreate the pool on the server, > so I cant try it, but thanks for the tip... No, I think it's just that few folks work with/ask about zvols that most people's brains short-circuit and go straight to thinking about only zpools and datasets--regardless of the text of the subject line. :) ___ 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 supported mps(4) driver in stable/9 and stable/8
Desai, Kashyap schreef: Try attached patch.! (This patch is not taken against upstream code, so you may see some hunk fail.) ~ Kashyap -Original Message- From: Johan Hendriks [mailto:joh.hendr...@gmail.com] Sent: Friday, February 03, 2012 8:42 PM To: Desai, Kashyap Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Desai, Kashyap schreef: Hi Johan, I have already figure out this issue in our lab. I also have fix for this issue. (Just don't want to create regression, that is why I have not posted outside) Since you have seen similar issue, It is worth to try my patch. My machine is not getting IP right now. I will send you patch once my machine is in network ? ~ Kashyap -Original Message- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd- sta...@freebsd.org] On Behalf Of Johan Hendriks Sent: Friday, February 03, 2012 8:13 PM To: Kenneth D. Merry Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Kenneth D. Merry schreef: Hi folks, The LSI-supported version of the mps(4) driver that supports their 6Gb SAS HBAs as well as WarpDrive controllers, is now in stable/9 and stable/8. Please test it out and let me and Kashyap (CCed) know if you run into any problems. In addition to supporting WarpDrive, the driver also supports Integrated RAID. Thanks to LSI for doing the work on this driver! Note that the CAM infrastructure changes that went into FreeBSD/head along with this driver have not gone into either stable/9 or stable/8. Only the driver itself has been merged. The CAM infrastructure changes depend on some other da(4) driver changes that will need to get merged before they can go back. If that merge happens, it will probably only be into stable/9. A couple of notes about issues with this driver: - Unlike the previous mps(4) driver, it probes sequentially. If you have a lot of drives in your system, it will take a while to probe them all. - You may see warning messages like this: _mapping_add_new_device: failed to add the device with handle 0x0019 to persiste nt table because there is no free space available _mapping_add_new_device: failed to add the device with handle 0x001a to persiste nt table because there is no free space available - The driver is not endian safe. (It assumes a little endian machine.) This is not new, the previous version of the driver had the same issue. The LSI folks know about these issues. The driver has passed their testing process. Many thanks to LSI for going through the effort to support FreeBSD. Ken Hello Ken. Just updated our 16 bay server. did a csup today. did try some commands, it looked like the drives got husseled. But after giving the command camcontrol rescan all it does not give back the prompt. Also top shows me the following. 1589 root1 200 16384K 1376K cbwait 3 0:00 0.00% camcontrol # on another console things works filer01# camcontrol devlist at scbus0 target 8 lun 0 (pass0,da0) at scbus0 target 9 lun 0 (pass1,da1) at scbus0 target 10 lun 0 (pass2,da2) at scbus0 target 11 lun 0 (pass3,da3) at scbus0 target 12 lun 0 (pass4,da4) at scbus0 target 13 lun 0 (pass5,da5) at scbus0 target 16 lun 0 (probe16,ses0,pass6) at scbus0 target 17 lun 0 (pass7,da6) at scbus0 target 18 lun 0 (pass8,da7) at scbus0 target 19 lun 0 (pass9,da8) at scbus0 target 20 lun 0 (pass10,da9) at scbus0 target 21 lun 0 (pass11,da10) at scbus0 target 22 lun 0 (pass12,da11) at scbus0 target 23 lun 0 (pass13,da12) at scbus0 target 24 lun 0 (pass14,da13) at scbus0 target 27 lun 0 (pass15,da14) at scbus0 target 28 lun 0 (pass16,da15) at scbus1 target 0 lun 0 (ada0,pass17) at scbus3 target 0 lun 0 (pass18,cd0) The controller is a LSI 9211-8i with IT firmware. here is the dmesg Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-STABLE #0: Fri Feb 3 10:27:18 CET 2012 root@filer01.neuteboom.local:/usr/obj/usr/src/sys/KRNL amd64 CPU: Intel(R) Xeon(R) CPU E31220 @ 3.10GHz (3093.04-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x206a7 Family = 6 Model = 2a Stepping = 7 Features=0xbfebfbff ,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> Features2=0x15bae3ff SE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,XSAVE,AVX> AMD Features=0x28100800 AMD Features2=0x1 TSC: P-state invariant, performance statistics real memory = 17179869184 (16384 MB) avail memory = 1649344102
Re: FreeBSD 9 crash/deadlock when dump(8)ing file system with journaling enabled.
On Mon, Jan 30, 2012 at 9:38 AM, Ivan Voras wrote: > On 30/01/2012 13:06, Jeremy Chadwick wrote: > >>> For now I've turned off journaling (soft updates seem fine) and that >>> works around the issue. >>> >>> Let me know if I can provide more details etc! >> >> >> I'm not sure, but this may be an after-effect of known problems right >> now with SU+J on 9.0. It would help if you could state if you're using >> "dump -L" or not. >> >> I've seen the "deadlock" behaviour you describe on older FreeBSD >> versions (dating back to at least 7.x) when using "dump -L", which >> generates a fs snapshot. Obviously 7.x does not have SU+J, so I'm a >> little surprised disabling journalling fixes the problem for you. > > > It's a known bug: SU+J currently deadlocks when used with UFS snapshots. Is there any additional information somewhere on when this is expected to be fixed? Seems like a fairly significant problem to me, especially since SU+J is the default when creating new file systems with bsdinstall. - Max ___ 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 supported mps(4) driver in stable/9 and stable/8
> -Original Message- > From: Johan Hendriks [mailto:joh.hendr...@gmail.com] > Sent: Friday, February 03, 2012 10:02 PM > To: Desai, Kashyap > Cc: freebsd-stable > Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 > > Desai, Kashyap schreef: > > Try attached patch.! (This patch is not taken against upstream code, > so you may see some hunk fail.) > > > > ~ Kashyap > > > >> -Original Message- > >> From: Johan Hendriks [mailto:joh.hendr...@gmail.com] > >> Sent: Friday, February 03, 2012 8:42 PM > >> To: Desai, Kashyap > >> Cc: freebsd-stable > >> Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 > >> > >> Desai, Kashyap schreef: > >>> Hi Johan, > >>> > >>> I have already figure out this issue in our lab. > >>> > >>> I also have fix for this issue. (Just don't want to create > regression, > >> that is why I have not posted outside) > >>> Since you have seen similar issue, It is worth to try my patch. > >>> > >>> My machine is not getting IP right now. I will send you patch once > my > >> machine is in network ? > >>> ~ Kashyap > >>> > >>> > -Original Message- > From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd- > sta...@freebsd.org] On Behalf Of Johan Hendriks > Sent: Friday, February 03, 2012 8:13 PM > To: Kenneth D. Merry > Cc: freebsd-stable > Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 > > Kenneth D. Merry schreef: > > Hi folks, > > > > The LSI-supported version of the mps(4) driver that supports their > >> 6Gb > SAS > > HBAs as well as WarpDrive controllers, is now in stable/9 and > stable/8. > > Please test it out and let me and Kashyap (CCed) know if you run > >> into > > any problems. > > > > In addition to supporting WarpDrive, the driver also supports > Integrated > > RAID. > > > > Thanks to LSI for doing the work on this driver! > > > > Note that the CAM infrastructure changes that went into > FreeBSD/head > along > > with this driver have not gone into either stable/9 or stable/8. > >> Only > the > > driver itself has been merged. > > > > The CAM infrastructure changes depend on some other da(4) driver > changes > > that will need to get merged before they can go back. If that > merge > > happens, it will probably only be into stable/9. > > > > A couple of notes about issues with this driver: > > > > - Unlike the previous mps(4) driver, it probes sequentially. > If > >> you > have > > a lot of drives in your system, it will take a while to > probe > >> them > all. > > - You may see warning messages like this: > > > > _mapping_add_new_device: failed to add the device with handle > 0x0019 > to persiste > > nt table because there is no free space available > > _mapping_add_new_device: failed to add the device with handle > 0x001a > to persiste > > nt table because there is no free space available > > > > - The driver is not endian safe. (It assumes a little endian > machine.) > > This is not new, the previous version of the driver had the > >> same > issue. > > The LSI folks know about these issues. The driver has passed > their > testing > > process. > > > > Many thanks to LSI for going through the effort to support > FreeBSD. > > > > Ken > Hello Ken. > > Just updated our 16 bay server. did a csup today. > did try some commands, it looked like the drives got husseled. > > But after giving the command camcontrol rescan all it does not give > >> back > the prompt. > Also top shows me the following. > 1589 root1 200 16384K 1376K cbwait 3 0:00 0.00% > camcontrol > > # on another console things works > filer01# camcontrol devlist > at scbus0 target 8 lun 0 > >> (pass0,da0) > at scbus0 target 9 lun 0 > >> (pass1,da1) > at scbus0 target 10 lun 0 > >> (pass2,da2) > at scbus0 target 11 lun 0 > >> (pass3,da3) > at scbus0 target 12 lun 0 > >> (pass4,da4) > at scbus0 target 13 lun 0 > >> (pass5,da5) > at scbus0 target 16 lun 0 > (probe16,ses0,pass6) > at scbus0 target 17 lun 0 > >> (pass7,da6) > at scbus0 target 18 lun 0 > >> (pass8,da7) > at scbus0 target 19 lun 0 > >> (pass9,da8) > at scbus0 target 20 lun 0 > (pass10,da9) > at scbus0 target 21 lun 0 > (pass11,da10) > at scbus0 target 22 lun 0 > (pass12,da11) > at scbus0 target 23 lun 0 > (pass13,da12) > at scbus0 target 24 lun 0 > (pass14,da13) > at scbus0 target 27 lun 0 > (pass15,da14) > >
Re: LSI supported mps(4) driver in stable/9 and stable/8
Desai, Kashyap schreef: -Original Message- From: Johan Hendriks [mailto:joh.hendr...@gmail.com] Sent: Friday, February 03, 2012 10:02 PM To: Desai, Kashyap Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Desai, Kashyap schreef: Try attached patch.! (This patch is not taken against upstream code, so you may see some hunk fail.) ~ Kashyap -Original Message- From: Johan Hendriks [mailto:joh.hendr...@gmail.com] Sent: Friday, February 03, 2012 8:42 PM To: Desai, Kashyap Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Desai, Kashyap schreef: Hi Johan, I have already figure out this issue in our lab. I also have fix for this issue. (Just don't want to create regression, that is why I have not posted outside) Since you have seen similar issue, It is worth to try my patch. My machine is not getting IP right now. I will send you patch once my machine is in network ? ~ Kashyap -Original Message- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd- sta...@freebsd.org] On Behalf Of Johan Hendriks Sent: Friday, February 03, 2012 8:13 PM To: Kenneth D. Merry Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Kenneth D. Merry schreef: Hi folks, The LSI-supported version of the mps(4) driver that supports their 6Gb SAS HBAs as well as WarpDrive controllers, is now in stable/9 and stable/8. Please test it out and let me and Kashyap (CCed) know if you run into any problems. In addition to supporting WarpDrive, the driver also supports Integrated RAID. Thanks to LSI for doing the work on this driver! Note that the CAM infrastructure changes that went into FreeBSD/head along with this driver have not gone into either stable/9 or stable/8. Only the driver itself has been merged. The CAM infrastructure changes depend on some other da(4) driver changes that will need to get merged before they can go back. If that merge happens, it will probably only be into stable/9. A couple of notes about issues with this driver: - Unlike the previous mps(4) driver, it probes sequentially. If you have a lot of drives in your system, it will take a while to probe them all. - You may see warning messages like this: _mapping_add_new_device: failed to add the device with handle 0x0019 to persiste nt table because there is no free space available _mapping_add_new_device: failed to add the device with handle 0x001a to persiste nt table because there is no free space available - The driver is not endian safe. (It assumes a little endian machine.) This is not new, the previous version of the driver had the same issue. The LSI folks know about these issues. The driver has passed their testing process. Many thanks to LSI for going through the effort to support FreeBSD. Ken Hello Ken. Just updated our 16 bay server. did a csup today. did try some commands, it looked like the drives got husseled. But after giving the command camcontrol rescan all it does not give back the prompt. Also top shows me the following. 1589 root1 200 16384K 1376K cbwait 3 0:00 0.00% camcontrol # on another console things works filer01# camcontrol devlist at scbus0 target 8 lun 0 (pass0,da0) at scbus0 target 9 lun 0 (pass1,da1) at scbus0 target 10 lun 0 (pass2,da2) at scbus0 target 11 lun 0 (pass3,da3) at scbus0 target 12 lun 0 (pass4,da4) at scbus0 target 13 lun 0 (pass5,da5) at scbus0 target 16 lun 0 (probe16,ses0,pass6) at scbus0 target 17 lun 0 (pass7,da6) at scbus0 target 18 lun 0 (pass8,da7) at scbus0 target 19 lun 0 (pass9,da8) at scbus0 target 20 lun 0 (pass10,da9) at scbus0 target 21 lun 0 (pass11,da10) at scbus0 target 22 lun 0 (pass12,da11) at scbus0 target 23 lun 0 (pass13,da12) at scbus0 target 24 lun 0 (pass14,da13) at scbus0 target 27 lun 0 (pass15,da14) at scbus0 target 28 lun 0 (pass16,da15) at scbus1 target 0 lun 0 (ada0,pass17) at scbus3 target 0 lun 0 (pass18,cd0) The controller is a LSI 9211-8i with IT firmware. here is the dmesg Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-STABLE #0: Fri Feb 3 10:27:18 CET 2012 root@filer01.neuteboom.local:/usr/obj/usr/src/sys/KRNL amd64 CPU: Intel(R) Xeon(R) CPU E31220 @ 3.10GHz (3093.04-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x206a7 Family = 6 Model = 2a Stepping = 7 Features=0xbfebfbff Features2=0x15bae3ff AMD Feat
RE: LSI supported mps(4) driver in stable/9 and stable/8
> -Original Message- > From: Johan Hendriks [mailto:joh.hendr...@gmail.com] > Sent: Friday, February 03, 2012 10:53 PM > To: Desai, Kashyap > Cc: freebsd-stable > Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 > > Desai, Kashyap schreef: > > > >> -Original Message- > >> From: Johan Hendriks [mailto:joh.hendr...@gmail.com] > >> Sent: Friday, February 03, 2012 10:02 PM > >> To: Desai, Kashyap > >> Cc: freebsd-stable > >> Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 > >> > >> Desai, Kashyap schreef: > >>> Try attached patch.! (This patch is not taken against upstream code, > >> so you may see some hunk fail.) > >>> ~ Kashyap > >>> > -Original Message- > From: Johan Hendriks [mailto:joh.hendr...@gmail.com] > Sent: Friday, February 03, 2012 8:42 PM > To: Desai, Kashyap > Cc: freebsd-stable > Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 > > Desai, Kashyap schreef: > > Hi Johan, > > > > I have already figure out this issue in our lab. > > > > I also have fix for this issue. (Just don't want to create > >> regression, > that is why I have not posted outside) > > Since you have seen similar issue, It is worth to try my patch. > > > > My machine is not getting IP right now. I will send you patch once > >> my > machine is in network ? > > ~ Kashyap > > > > > >> -Original Message- > >> From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd- > >> sta...@freebsd.org] On Behalf Of Johan Hendriks > >> Sent: Friday, February 03, 2012 8:13 PM > >> To: Kenneth D. Merry > >> Cc: freebsd-stable > >> Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 > >> > >> Kenneth D. Merry schreef: > >>> Hi folks, > >>> > >>> The LSI-supported version of the mps(4) driver that supports > their > 6Gb > >> SAS > >>> HBAs as well as WarpDrive controllers, is now in stable/9 and > >> stable/8. > >>> Please test it out and let me and Kashyap (CCed) know if you run > into > >>> any problems. > >>> > >>> In addition to supporting WarpDrive, the driver also supports > >> Integrated > >>> RAID. > >>> > >>> Thanks to LSI for doing the work on this driver! > >>> > >>> Note that the CAM infrastructure changes that went into > >> FreeBSD/head > >> along > >>> with this driver have not gone into either stable/9 or stable/8. > Only > >> the > >>> driver itself has been merged. > >>> > >>> The CAM infrastructure changes depend on some other da(4) driver > >> changes > >>> that will need to get merged before they can go back. If that > >> merge > >>> happens, it will probably only be into stable/9. > >>> > >>> A couple of notes about issues with this driver: > >>> > >>> - Unlike the previous mps(4) driver, it probes > sequentially. > >> If > you > >> have > >>>a lot of drives in your system, it will take a while to > >> probe > them > >> all. > >>> - You may see warning messages like this: > >>> > >>> _mapping_add_new_device: failed to add the device with handle > >> 0x0019 > >> to persiste > >>> nt table because there is no free space available > >>> _mapping_add_new_device: failed to add the device with handle > >> 0x001a > >> to persiste > >>> nt table because there is no free space available > >>> > >>> - The driver is not endian safe. (It assumes a little > endian > >> machine.) > >>>This is not new, the previous version of the driver had > the > same > >> issue. > >>> The LSI folks know about these issues. The driver has passed > >> their > >> testing > >>> process. > >>> > >>> Many thanks to LSI for going through the effort to support > >> FreeBSD. > >>> Ken > >> Hello Ken. > >> > >> Just updated our 16 bay server. did a csup today. > >> did try some commands, it looked like the drives got husseled. > >> > >> But after giving the command camcontrol rescan all it does not > give > back > >> the prompt. > >> Also top shows me the following. > >> 1589 root1 200 16384K 1376K cbwait 3 0:00 0.00% > >> camcontrol > >> > >> # on another console things works > >> filer01# camcontrol devlist > >>at scbus0 target 8 lun 0 > (pass0,da0) > >>at scbus0 target 9 lun 0 > (pass1,da1) > >>at scbus0 target 10 lun 0 > (pass2,da2) > >>at scbus0 target 11 lun 0 > (pass3,da3) > >>at scbus0 target 12 lun 0 > (pass4,da4) > >> at scbus0 target 13 lun 0 > (pass5,da5) > >>at scbus0 target 16 lun 0 > >> (probe16,ses0,pass6) > >> at s
[releng_8_2 tinderbox] failure on mips/mips
TB --- 2012-02-03 17:24:15 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-02-03 17:24:15 - starting RELENG_8_2 tinderbox run for mips/mips TB --- 2012-02-03 17:24:15 - cleaning the object tree TB --- 2012-02-03 17:24:23 - cvsupping the source tree TB --- 2012-02-03 17:24:23 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8_2/mips/mips/supfile TB --- 2012-02-03 17:24:34 - building world TB --- 2012-02-03 17:24:34 - CROSS_BUILD_TESTING=YES TB --- 2012-02-03 17:24:34 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-03 17:24:34 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-03 17:24:34 - SRCCONF=/dev/null TB --- 2012-02-03 17:24:34 - TARGET=mips TB --- 2012-02-03 17:24:34 - TARGET_ARCH=mips TB --- 2012-02-03 17:24:34 - TZ=UTC TB --- 2012-02-03 17:24:34 - __MAKE_CONF=/dev/null TB --- 2012-02-03 17:24:34 - cd /src TB --- 2012-02-03 17:24:34 - /usr/bin/make -B buildworld >>> World build started on Fri Feb 3 17:24:34 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri Feb 3 18:00:54 UTC 2012 TB --- 2012-02-03 18:00:54 - cd /src/sys/mips/conf TB --- 2012-02-03 18:00:54 - /usr/sbin/config -m ADM5120 TB --- 2012-02-03 18:00:54 - building ADM5120 kernel TB --- 2012-02-03 18:00:54 - CROSS_BUILD_TESTING=YES TB --- 2012-02-03 18:00:54 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-03 18:00:54 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-03 18:00:54 - SRCCONF=/dev/null TB --- 2012-02-03 18:00:54 - TARGET=mips TB --- 2012-02-03 18:00:54 - TARGET_ARCH=mips TB --- 2012-02-03 18:00:54 - TZ=UTC TB --- 2012-02-03 18:00:54 - __MAKE_CONF=/dev/null TB --- 2012-02-03 18:00:54 - cd /src TB --- 2012-02-03 18:00:54 - /usr/bin/make -B buildkernel KERNCONF=ADM5120 >>> Kernel build for ADM5120 started on Fri Feb 3 18:00:54 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for ADM5120 completed on Fri Feb 3 18:02:07 UTC 2012 TB --- 2012-02-03 18:02:07 - cd /src/sys/mips/conf TB --- 2012-02-03 18:02:07 - /usr/sbin/config -m ALCHEMY TB --- 2012-02-03 18:02:07 - building ALCHEMY kernel TB --- 2012-02-03 18:02:07 - CROSS_BUILD_TESTING=YES TB --- 2012-02-03 18:02:07 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-03 18:02:07 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-03 18:02:07 - SRCCONF=/dev/null TB --- 2012-02-03 18:02:07 - TARGET=mips TB --- 2012-02-03 18:02:07 - TARGET_ARCH=mips TB --- 2012-02-03 18:02:07 - TZ=UTC TB --- 2012-02-03 18:02:07 - __MAKE_CONF=/dev/null TB --- 2012-02-03 18:02:07 - cd /src TB --- 2012-02-03 18:02:07 - /usr/bin/make -B buildkernel KERNCONF=ALCHEMY >>> Kernel build for ALCHEMY started on Fri Feb 3 18:02:07 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O -pipe -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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=1000 --param large-function-growth=10 -EL -fno-pic -mno-abicalls -G0 -EL -march=mips32 -msoft-float -mno-dsp -ffreestanding -Werror /src/sys/libkern/ucmpdi2.c cc -c -O -pipe -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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=1000 --param large-function-growth=10 -EL -fno-pic -mno-abicalls -G0 -EL -march=mips32 -msoft-float -mno-dsp -ffreestanding -Werror /src/sys/libkern/udivdi3.c cc -c -O -pipe -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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=1000 --param large-function-growth=10 -EL -fno-pic -mno-abicalls -G0 -EL -march=mips32 -msoft-float -mno-dsp -ffreestanding -Werror /src/sys/libkern/umod
[releng_8_2 tinderbox] failure on powerpc/powerpc
TB --- 2012-02-03 17:50:25 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-02-03 17:50:25 - starting RELENG_8_2 tinderbox run for powerpc/powerpc TB --- 2012-02-03 17:50:25 - cleaning the object tree TB --- 2012-02-03 17:50:54 - cvsupping the source tree TB --- 2012-02-03 17:50:54 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8_2/powerpc/powerpc/supfile TB --- 2012-02-03 17:52:00 - building world TB --- 2012-02-03 17:52:00 - CROSS_BUILD_TESTING=YES TB --- 2012-02-03 17:52:00 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-03 17:52:00 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-03 17:52:00 - SRCCONF=/dev/null TB --- 2012-02-03 17:52:00 - TARGET=powerpc TB --- 2012-02-03 17:52:00 - TARGET_ARCH=powerpc TB --- 2012-02-03 17:52:00 - TZ=UTC TB --- 2012-02-03 17:52:00 - __MAKE_CONF=/dev/null TB --- 2012-02-03 17:52:00 - cd /src TB --- 2012-02-03 17:52:00 - /usr/bin/make -B buildworld >>> World build started on Fri Feb 3 17:52:00 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri Feb 3 18:38:05 UTC 2012 TB --- 2012-02-03 18:38:05 - generating LINT kernel config TB --- 2012-02-03 18:38:05 - cd /src/sys/powerpc/conf TB --- 2012-02-03 18:38:05 - /usr/bin/make -B LINT TB --- 2012-02-03 18:38:05 - cd /src/sys/powerpc/conf TB --- 2012-02-03 18:38:05 - /usr/sbin/config -m LINT TB --- 2012-02-03 18:38:05 - building LINT kernel TB --- 2012-02-03 18:38:05 - CROSS_BUILD_TESTING=YES TB --- 2012-02-03 18:38:05 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-03 18:38:05 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-03 18:38:05 - SRCCONF=/dev/null TB --- 2012-02-03 18:38:05 - TARGET=powerpc TB --- 2012-02-03 18:38:05 - TARGET_ARCH=powerpc TB --- 2012-02-03 18:38:05 - TZ=UTC TB --- 2012-02-03 18:38:05 - __MAKE_CONF=/dev/null TB --- 2012-02-03 18:38:05 - cd /src TB --- 2012-02-03 18:38:05 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Feb 3 18:38:05 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Fri Feb 3 18:53:29 UTC 2012 TB --- 2012-02-03 18:53:29 - cd /src/sys/powerpc/conf TB --- 2012-02-03 18:53:29 - /usr/sbin/config -m GENERIC TB --- 2012-02-03 18:53:29 - building GENERIC kernel TB --- 2012-02-03 18:53:29 - CROSS_BUILD_TESTING=YES TB --- 2012-02-03 18:53:29 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-03 18:53:29 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-03 18:53:29 - SRCCONF=/dev/null TB --- 2012-02-03 18:53:29 - TARGET=powerpc TB --- 2012-02-03 18:53:29 - TARGET_ARCH=powerpc TB --- 2012-02-03 18:53:29 - TZ=UTC TB --- 2012-02-03 18:53:29 - __MAKE_CONF=/dev/null TB --- 2012-02-03 18:53:29 - cd /src TB --- 2012-02-03 18:53:29 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Feb 3 18:53:29 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Fri Feb 3 19:04:00 UTC 2012 TB --- 2012-02-03 19:04:00 - cd /src/sys/powerpc/conf TB --- 2012-02-03 19:04:00 - /usr/sbin/config -m MPC85XX TB --- 2012-02-03 19:04:00 - building MPC85XX kernel TB --- 2012-02-03 19:04:00 - CROSS_BUILD_TESTING=YES TB --- 2012-02-03 19:04:00 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-03 19:04:00 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-03 19:04:00 - SRCCONF=/dev/null TB --- 2012-02-03 19:04:00 - TARGET=powerpc TB --- 2012-02-03 19:04:00 - TARGET_ARCH=powerpc TB --- 2012-02-03 19:04:00 - TZ=UTC TB --- 2012-02-03 19:04:00 - __MAKE_CONF=/dev/null TB --- 2012-02-03 19:04:00 - cd /src TB --- 2012-02-03 19:04:00 - /usr/bin/make -B buildkernel KERNCONF=MPC85XX >>> Kernel build for MPC85XX started on Fri Feb 3 19:04:00 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O -pipe -std=c99 -Wa,-me500 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --pa
Re: FreeBSD 8.2-stable: devd fails to restart
On Thu, 02 Feb 2012 21:45:26 -0800 Doug Barton wrote: > > Actually all the OP needs to do is to make sure the src tree is up to > date and run mergemaster. I MFC'ed the relevant changes to rc.d/devd > last April. Strange, my machine was rebuilt later than that (yes, I always run mergemaster as part of the the "make world"): root@kg-v7# uname -a FreeBSD kg-v7.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #7: Sat Jul 9 23:00:31 CEST 2011 r...@kg-v7.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 root@kg-v7# root@kg-v7# head -3 /etc/rc.subr # $NetBSD: rc.subr,v 1.67 2006/10/07 11:25:15 elad Exp $ # $FreeBSD: src/etc/rc.subr,v 1.88.2.16 2011/04/29 20:31:52 dougb Exp $ # root@kg-v7# head -3 /etc/rc.d/devd #!/bin/sh # # $FreeBSD: src/etc/rc.d/devd,v 1.11.2.2 2011/04/29 20:31:52 dougb Exp $ Another machine which also has the same problem: root@kg-v2# uname -a FreeBSD kg-v2.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #4: Sat Jul 16 02:07:14 CEST 2011 r...@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 root@kg-v2# head -3 /etc/rc.subr # $NetBSD: rc.subr,v 1.67 2006/10/07 11:25:15 elad Exp $ # $FreeBSD: src/etc/rc.subr,v 1.88.2.17 2011/07/03 16:32:03 jilles Exp $ # root@kg-v2# head -3 /etc/rc.d/devd #!/bin/sh # # $FreeBSD: src/etc/rc.d/devd,v 1.11.2.2 2011/04/29 20:31:52 dougb Exp $ Is that the versions you are referring to? I have a machine with world built in December, it seems to have the same versions of the files: (note: i have not tried restarting devd on that machine) root@kg-vm# uname -a FreeBSD kg-vm.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #4: Sat Dec 17 17:47:43 CET 2011 r...@kg-vm.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 root@kg-vm# head -3 /etc/rc.subr # $NetBSD: rc.subr,v 1.67 2006/10/07 11:25:15 elad Exp $ # $FreeBSD: src/etc/rc.subr,v 1.88.2.17 2011/07/03 16:32:03 jilles Exp $ # root@kg-vm# head -3 /etc/rc.d/devd #!/bin/sh # # $FreeBSD: src/etc/rc.d/devd,v 1.11.2.2 2011/04/29 20:31:52 dougb Exp $ -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 8.2-stable: devd fails to restart
On Fri, 03 Feb 2012 08:34:10 +0300
Sergey Kandaurov wrote:
> Please apply this patch and report how it goes for you.
> http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.d/devd.diff?r1=1.12;r2=1.13
>
> This is not in 8-STABLE yet.
It looks like it (or almost the same) is here already:
root@kg-v2# more /etc/rc.d/devd
#!/bin/sh
#
# $FreeBSD: src/etc/rc.d/devd,v 1.11.2.2 2011/04/29 20:31:52 dougb Exp $
#
# PROVIDE: devd
# REQUIRE: netif network_ipv6
# BEFORE: NETWORKING mountcritremote
# KEYWORD: nojail shutdown
. /etc/rc.subr
name="devd"
rcvar=`set_rcvar`
command="/sbin/${name}"
start_precmd=${name}_prestart
stop_precmd=find_pidfile
find_pidfile()
{
if get_pidfile_from_conf pid-file /etc/devd.conf; then
pidfile="$_pidfile_from_conf"
else
pidfile="/var/run/${name}.pid"
fi
}
devd_prestart ()
{
find_pidfile
# If devd is disabled, turn it off in the kernel to avoid memory leaks.
if ! checkyesno ${rcvar}; then
$SYSCTL hw.bus.devctl_disable=1
fi
}
load_rc_config $name
run_rc_command "$1"
HTH
--
Torfinn
___
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 tinderbox] failure on i386/i386
TB --- 2012-02-03 18:49:49 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-02-03 18:49:49 - starting RELENG_8 tinderbox run for i386/i386 TB --- 2012-02-03 18:49:49 - cleaning the object tree TB --- 2012-02-03 18:50:19 - cvsupping the source tree TB --- 2012-02-03 18:50:19 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/i386/i386/supfile TB --- 2012-02-03 18:51:13 - building world TB --- 2012-02-03 18:51:13 - CROSS_BUILD_TESTING=YES TB --- 2012-02-03 18:51:13 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-03 18:51:13 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-03 18:51:13 - SRCCONF=/dev/null TB --- 2012-02-03 18:51:13 - TARGET=i386 TB --- 2012-02-03 18:51:13 - TARGET_ARCH=i386 TB --- 2012-02-03 18:51:13 - TZ=UTC TB --- 2012-02-03 18:51:13 - __MAKE_CONF=/dev/null TB --- 2012-02-03 18:51:13 - cd /src TB --- 2012-02-03 18:51:13 - /usr/bin/make -B buildworld >>> World build started on Fri Feb 3 18:51:14 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri Feb 3 19:38:19 UTC 2012 TB --- 2012-02-03 19:38:19 - generating LINT kernel config TB --- 2012-02-03 19:38:19 - cd /src/sys/i386/conf TB --- 2012-02-03 19:38:19 - /usr/bin/make -B LINT TB --- 2012-02-03 19:38:19 - cd /src/sys/i386/conf TB --- 2012-02-03 19:38:19 - /usr/sbin/config -m LINT TB --- 2012-02-03 19:38:19 - building LINT kernel TB --- 2012-02-03 19:38:19 - CROSS_BUILD_TESTING=YES TB --- 2012-02-03 19:38:19 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-03 19:38:19 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-03 19:38:19 - SRCCONF=/dev/null TB --- 2012-02-03 19:38:19 - TARGET=i386 TB --- 2012-02-03 19:38:19 - TARGET_ARCH=i386 TB --- 2012-02-03 19:38:19 - TZ=UTC TB --- 2012-02-03 19:38:19 - __MAKE_CONF=/dev/null TB --- 2012-02-03 19:38:19 - cd /src TB --- 2012-02-03 19:38:19 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Feb 3 19:38:19 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] :> hack.c cc -shared -nostdlib hack.c -o hack.So rm -f hack.c MAKE=/usr/bin/make sh /src/sys/conf/newvers.sh LINT cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue vers.c linking kernel ld: kernel: Not enough room for program headers (allocated 5, need 6) ld: final link failed: Bad value *** Error code 1 Stop in /obj/i386/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-02-03 19:50:03 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-02-03 19:50:03 - ERROR: failed to build LINT kernel TB --- 2012-02-03 19:50:03 - 2773.73 user 494.55 system 3613.59 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-i386-i386.full ___ 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_1 tinderbox] failure on mips/mips
TB --- 2012-02-04 01:30:58 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-02-04 01:30:58 - starting RELENG_8_1 tinderbox run for mips/mips TB --- 2012-02-04 01:30:58 - cleaning the object tree TB --- 2012-02-04 01:31:06 - cvsupping the source tree TB --- 2012-02-04 01:31:06 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8_1/mips/mips/supfile TB --- 2012-02-04 01:36:33 - building world TB --- 2012-02-04 01:36:33 - CROSS_BUILD_TESTING=YES TB --- 2012-02-04 01:36:33 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-04 01:36:33 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-04 01:36:33 - SRCCONF=/dev/null TB --- 2012-02-04 01:36:33 - TARGET=mips TB --- 2012-02-04 01:36:33 - TARGET_ARCH=mips TB --- 2012-02-04 01:36:33 - TZ=UTC TB --- 2012-02-04 01:36:33 - __MAKE_CONF=/dev/null TB --- 2012-02-04 01:36:33 - cd /src TB --- 2012-02-04 01:36:33 - /usr/bin/make -B buildworld >>> World build started on Sat Feb 4 01:36:33 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Sat Feb 4 02:12:47 UTC 2012 TB --- 2012-02-04 02:12:47 - cd /src/sys/mips/conf TB --- 2012-02-04 02:12:47 - /usr/sbin/config -m ADM5120 TB --- 2012-02-04 02:12:47 - building ADM5120 kernel TB --- 2012-02-04 02:12:47 - CROSS_BUILD_TESTING=YES TB --- 2012-02-04 02:12:47 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-04 02:12:47 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-04 02:12:47 - SRCCONF=/dev/null TB --- 2012-02-04 02:12:47 - TARGET=mips TB --- 2012-02-04 02:12:47 - TARGET_ARCH=mips TB --- 2012-02-04 02:12:47 - TZ=UTC TB --- 2012-02-04 02:12:47 - __MAKE_CONF=/dev/null TB --- 2012-02-04 02:12:47 - cd /src TB --- 2012-02-04 02:12:47 - /usr/bin/make -B buildkernel KERNCONF=ADM5120 >>> Kernel build for ADM5120 started on Sat Feb 4 02:12:47 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for ADM5120 completed on Sat Feb 4 02:13:58 UTC 2012 TB --- 2012-02-04 02:13:58 - cd /src/sys/mips/conf TB --- 2012-02-04 02:13:58 - /usr/sbin/config -m IDT TB --- 2012-02-04 02:13:58 - building IDT kernel TB --- 2012-02-04 02:13:58 - CROSS_BUILD_TESTING=YES TB --- 2012-02-04 02:13:58 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-04 02:13:58 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-04 02:13:58 - SRCCONF=/dev/null TB --- 2012-02-04 02:13:58 - TARGET=mips TB --- 2012-02-04 02:13:58 - TARGET_ARCH=mips TB --- 2012-02-04 02:13:58 - TZ=UTC TB --- 2012-02-04 02:13:58 - __MAKE_CONF=/dev/null TB --- 2012-02-04 02:13:58 - cd /src TB --- 2012-02-04 02:13:58 - /usr/bin/make -B buildkernel KERNCONF=IDT >>> Kernel build for IDT started on Sat Feb 4 02:13:58 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for IDT completed on Sat Feb 4 02:15:36 UTC 2012 TB --- 2012-02-04 02:15:36 - cd /src/sys/mips/conf TB --- 2012-02-04 02:15:36 - /usr/sbin/config -m MALTA TB --- 2012-02-04 02:15:36 - building MALTA kernel TB --- 2012-02-04 02:15:36 - CROSS_BUILD_TESTING=YES TB --- 2012-02-04 02:15:36 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-04 02:15:36 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-04 02:15:36 - SRCCONF=/dev/null TB --- 2012-02-04 02:15:36 - TARGET=mips TB --- 2012-02-04 02:15:36 - TARGET_ARCH=mips TB --- 2012-02-04 02:15:36 - TZ=UTC TB --- 2012-02-04 02:15:36 - __MAKE_CONF=/dev/null TB --- 2012-02-04 02:15:36 - cd /src TB --- 2012-02-04 02:15:36 - /usr/bin/make -B buildkernel KERNCONF=MALTA >>> Kernel build for MALTA started on Sat Feb 4 02:15:36 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for MALTA completed on Sat Feb 4 02:17:02 UTC 2012 TB --- 2012-02-04 02:17:02 - cd /src/sys/mips/conf TB --- 2012-02-04 02:17:02 - /usr/sbin/config -m QEMU TB --- 2012-02-04 02:17:02 - building QEMU kernel TB --- 2012-02-04 02:17:02 - CROSS_BUILD_TESTING=YES TB --- 2012-02-04 02:17:02 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-04 02:17:02 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-04 02:17:02 - SRCCONF=/dev/null TB --- 2012-02-04 02:17:02 - TARGET=mips TB --- 2012-02-04 02:17:02 - TARGET_ARCH=mips TB --- 2012-02-04 02:17:02 - TZ=UTC TB --- 2012-02-04 02:17:02 - __MAKE_CONF=/dev/null TB ---
Re: [releng_8_2 tinderbox] failure on powerpc/powerpc
On 02/03/2012 05:34, John Baldwin wrote: > On Thursday, February 02, 2012 7:17:14 pm George Mitchell wrote: >> On 02/02/12 15:37, FreeBSD Tinderbox wrote: >>> [... one of three errors it's been reporting repeatedly for days ...] >> Talk about a lack of focus! Apparently two or three people have all >> recently checked in code without first verifying that it compiled (let >> alone ran), or else possibly did not completely commit their changes, >> and then absconded to a place where they fail to receive these emails >> about the problems. Can someone please either diagnose these errors or >> else revert the deficient commits? -- George Mitchell > > No, it is more that the tinderbox for 8 wasn't actually checking these > kernels before (they have been broken since 8.1 and 8.2 were released) and > they are on less-used platforms. Shouldn't whoever asked for that to be enabled take responsibility for cleaning them up then? > I do agree it needs to be cleaned up one way > or another. Given the reticence to commit changes to release branches, They're already broken. It's hard to see how fixing the problems could make things worse. :) Doug -- It's always a long day; 86400 doesn't fit into a short. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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_2 tinderbox] failure on mips/mips
TB --- 2012-02-04 03:54:57 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-02-04 03:54:57 - starting RELENG_8_2 tinderbox run for mips/mips TB --- 2012-02-04 03:54:57 - cleaning the object tree TB --- 2012-02-04 03:55:06 - cvsupping the source tree TB --- 2012-02-04 03:55:06 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8_2/mips/mips/supfile TB --- 2012-02-04 03:55:21 - building world TB --- 2012-02-04 03:55:21 - CROSS_BUILD_TESTING=YES TB --- 2012-02-04 03:55:21 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-04 03:55:21 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-04 03:55:21 - SRCCONF=/dev/null TB --- 2012-02-04 03:55:21 - TARGET=mips TB --- 2012-02-04 03:55:21 - TARGET_ARCH=mips TB --- 2012-02-04 03:55:21 - TZ=UTC TB --- 2012-02-04 03:55:21 - __MAKE_CONF=/dev/null TB --- 2012-02-04 03:55:21 - cd /src TB --- 2012-02-04 03:55:21 - /usr/bin/make -B buildworld >>> World build started on Sat Feb 4 03:55:21 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Sat Feb 4 04:31:41 UTC 2012 TB --- 2012-02-04 04:31:41 - cd /src/sys/mips/conf TB --- 2012-02-04 04:31:41 - /usr/sbin/config -m ADM5120 TB --- 2012-02-04 04:31:41 - building ADM5120 kernel TB --- 2012-02-04 04:31:41 - CROSS_BUILD_TESTING=YES TB --- 2012-02-04 04:31:41 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-04 04:31:41 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-04 04:31:41 - SRCCONF=/dev/null TB --- 2012-02-04 04:31:41 - TARGET=mips TB --- 2012-02-04 04:31:41 - TARGET_ARCH=mips TB --- 2012-02-04 04:31:41 - TZ=UTC TB --- 2012-02-04 04:31:41 - __MAKE_CONF=/dev/null TB --- 2012-02-04 04:31:41 - cd /src TB --- 2012-02-04 04:31:41 - /usr/bin/make -B buildkernel KERNCONF=ADM5120 >>> Kernel build for ADM5120 started on Sat Feb 4 04:31:41 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for ADM5120 completed on Sat Feb 4 04:32:52 UTC 2012 TB --- 2012-02-04 04:32:52 - cd /src/sys/mips/conf TB --- 2012-02-04 04:32:52 - /usr/sbin/config -m ALCHEMY TB --- 2012-02-04 04:32:52 - building ALCHEMY kernel TB --- 2012-02-04 04:32:52 - CROSS_BUILD_TESTING=YES TB --- 2012-02-04 04:32:52 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-04 04:32:52 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-04 04:32:52 - SRCCONF=/dev/null TB --- 2012-02-04 04:32:52 - TARGET=mips TB --- 2012-02-04 04:32:52 - TARGET_ARCH=mips TB --- 2012-02-04 04:32:52 - TZ=UTC TB --- 2012-02-04 04:32:52 - __MAKE_CONF=/dev/null TB --- 2012-02-04 04:32:52 - cd /src TB --- 2012-02-04 04:32:52 - /usr/bin/make -B buildkernel KERNCONF=ALCHEMY >>> Kernel build for ALCHEMY started on Sat Feb 4 04:32:52 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O -pipe -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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=1000 --param large-function-growth=10 -EL -fno-pic -mno-abicalls -G0 -EL -march=mips32 -msoft-float -mno-dsp -ffreestanding -Werror /src/sys/libkern/ucmpdi2.c cc -c -O -pipe -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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=1000 --param large-function-growth=10 -EL -fno-pic -mno-abicalls -G0 -EL -march=mips32 -msoft-float -mno-dsp -ffreestanding -Werror /src/sys/libkern/udivdi3.c cc -c -O -pipe -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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=1000 --param large-function-growth=10 -EL -fno-pic -mno-abicalls -G0 -EL -march=mips32 -msoft-float -mno-dsp -ffreestanding -Werror /src/sys/libkern/umod
Re: FreeBSD 8.2-stable: devd fails to restart
Just because of what I read already is pretty terse I am top-posting for
a reason.
$ su -
# /etc/rc.d/devd stop
# pgrep -l devd (This should show nothing if so kill the results)
# /sbin/devd -D -d (Paste the results)
On Fri, Feb 03, 2012 at 08:41:10PM +0100, Torfinn Ingolfsen wrote:
> On Fri, 03 Feb 2012 08:34:10 +0300
> Sergey Kandaurov wrote:
>
> > Please apply this patch and report how it goes for you.
> > http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.d/devd.diff?r1=1.12;r2=1.13
> >
> > This is not in 8-STABLE yet.
>
> It looks like it (or almost the same) is here already:
> root@kg-v2# more /etc/rc.d/devd
> #!/bin/sh
> #
> # $FreeBSD: src/etc/rc.d/devd,v 1.11.2.2 2011/04/29 20:31:52 dougb Exp $
> #
>
> # PROVIDE: devd
> # REQUIRE: netif network_ipv6
> # BEFORE: NETWORKING mountcritremote
> # KEYWORD: nojail shutdown
>
> . /etc/rc.subr
>
> name="devd"
> rcvar=`set_rcvar`
> command="/sbin/${name}"
>
> start_precmd=${name}_prestart
> stop_precmd=find_pidfile
>
> find_pidfile()
> {
> if get_pidfile_from_conf pid-file /etc/devd.conf; then
> pidfile="$_pidfile_from_conf"
> else
> pidfile="/var/run/${name}.pid"
> fi
> }
>
> devd_prestart ()
> {
> find_pidfile
>
> # If devd is disabled, turn it off in the kernel to avoid memory
> leaks.
> if ! checkyesno ${rcvar}; then
> $SYSCTL hw.bus.devctl_disable=1
> fi
> }
>
> load_rc_config $name
> run_rc_command "$1"
>
> HTH
> --
> Torfinn
>
> ___
> 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"
--
;s =;
___
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_2 tinderbox] failure on powerpc/powerpc
TB --- 2012-02-04 04:13:46 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-02-04 04:13:46 - starting RELENG_8_2 tinderbox run for powerpc/powerpc TB --- 2012-02-04 04:13:46 - cleaning the object tree TB --- 2012-02-04 04:14:14 - cvsupping the source tree TB --- 2012-02-04 04:14:14 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8_2/powerpc/powerpc/supfile TB --- 2012-02-04 04:14:30 - building world TB --- 2012-02-04 04:14:30 - CROSS_BUILD_TESTING=YES TB --- 2012-02-04 04:14:30 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-04 04:14:30 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-04 04:14:30 - SRCCONF=/dev/null TB --- 2012-02-04 04:14:30 - TARGET=powerpc TB --- 2012-02-04 04:14:30 - TARGET_ARCH=powerpc TB --- 2012-02-04 04:14:30 - TZ=UTC TB --- 2012-02-04 04:14:30 - __MAKE_CONF=/dev/null TB --- 2012-02-04 04:14:30 - cd /src TB --- 2012-02-04 04:14:30 - /usr/bin/make -B buildworld >>> World build started on Sat Feb 4 04:14:30 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Sat Feb 4 05:00:17 UTC 2012 TB --- 2012-02-04 05:00:17 - generating LINT kernel config TB --- 2012-02-04 05:00:17 - cd /src/sys/powerpc/conf TB --- 2012-02-04 05:00:17 - /usr/bin/make -B LINT TB --- 2012-02-04 05:00:17 - cd /src/sys/powerpc/conf TB --- 2012-02-04 05:00:17 - /usr/sbin/config -m LINT TB --- 2012-02-04 05:00:17 - building LINT kernel TB --- 2012-02-04 05:00:17 - CROSS_BUILD_TESTING=YES TB --- 2012-02-04 05:00:17 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-04 05:00:17 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-04 05:00:17 - SRCCONF=/dev/null TB --- 2012-02-04 05:00:17 - TARGET=powerpc TB --- 2012-02-04 05:00:17 - TARGET_ARCH=powerpc TB --- 2012-02-04 05:00:17 - TZ=UTC TB --- 2012-02-04 05:00:17 - __MAKE_CONF=/dev/null TB --- 2012-02-04 05:00:17 - cd /src TB --- 2012-02-04 05:00:17 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Feb 4 05:00:17 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Sat Feb 4 05:15:31 UTC 2012 TB --- 2012-02-04 05:15:31 - cd /src/sys/powerpc/conf TB --- 2012-02-04 05:15:31 - /usr/sbin/config -m GENERIC TB --- 2012-02-04 05:15:31 - building GENERIC kernel TB --- 2012-02-04 05:15:31 - CROSS_BUILD_TESTING=YES TB --- 2012-02-04 05:15:31 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-04 05:15:31 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-04 05:15:31 - SRCCONF=/dev/null TB --- 2012-02-04 05:15:31 - TARGET=powerpc TB --- 2012-02-04 05:15:31 - TARGET_ARCH=powerpc TB --- 2012-02-04 05:15:31 - TZ=UTC TB --- 2012-02-04 05:15:31 - __MAKE_CONF=/dev/null TB --- 2012-02-04 05:15:31 - cd /src TB --- 2012-02-04 05:15:31 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sat Feb 4 05:15:31 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Sat Feb 4 05:25:45 UTC 2012 TB --- 2012-02-04 05:25:45 - cd /src/sys/powerpc/conf TB --- 2012-02-04 05:25:45 - /usr/sbin/config -m MPC85XX TB --- 2012-02-04 05:25:45 - building MPC85XX kernel TB --- 2012-02-04 05:25:45 - CROSS_BUILD_TESTING=YES TB --- 2012-02-04 05:25:45 - MAKEOBJDIRPREFIX=/obj TB --- 2012-02-04 05:25:45 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-02-04 05:25:45 - SRCCONF=/dev/null TB --- 2012-02-04 05:25:45 - TARGET=powerpc TB --- 2012-02-04 05:25:45 - TARGET_ARCH=powerpc TB --- 2012-02-04 05:25:45 - TZ=UTC TB --- 2012-02-04 05:25:45 - __MAKE_CONF=/dev/null TB --- 2012-02-04 05:25:45 - cd /src TB --- 2012-02-04 05:25:45 - /usr/bin/make -B buildkernel KERNCONF=MPC85XX >>> Kernel build for MPC85XX started on Sat Feb 4 05:25:45 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O -pipe -std=c99 -Wa,-me500 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --pa
