Re: RFC: Suggesting ZFS best practices in FreeBSD
On Tue, 26 Feb 2013 08:33:58 +0100, Daniel Kalchev dan...@digsys.bg wrote: On 25.02.13 18:44, Karl Denninger wrote: On 2/25/2013 8:31 AM, Tom Evans wrote: Using GPT labels is easy to do, and provides a cast iron guarantee that your disk will not EVER be mistaken for a different drive. I put a GPT label on the drive, and then write it in permanent marker on the top of the drive and on a sticky label that is stuck on the front of the chassis. The disk label never changes in its lifetime, so you only get issues if you insert a drive without labelling it first. Cheers Tom Listen to this man. Either do it in gpart or do it with glabel (depending on where you want it to show up); once done the drive will always have the same name in the device tree no matter what slot it shows up in. Then stick that label on the front of the drive carrier, and you never have this problem. Do that or suffer. Your choice. I can only second this advice. Learn to make your setups as generic as possible. Wiring down device names using CAM etc, only complicates matters, at least because that knowledge is contained within the system you boot, not the drive. If you boot from an recovery media, all of your fine crafted CAM wire-down system will be gone and you will suffer. You will suffer exactly at the moment when you need those labels most. Not wise. Yes, Jeremy, there is always the first time. Both glabel and GPT labels do the trick. Both behave differently and depending on your habits and intended usage one or the other is good. Just don't be inclined to use both at the same time. My personal preference as of later is GPT labels. By the way, glabel is a generic term in FreeBSD. It refers to all label types, including those created with glabel, gpart and newfs/tunefs. The later are not really geom labels, these are volume labels, but glabel is smart enough to detect/report them, even if it can't manipulate these labels. I don't find the glabel documentation all that confusing. Daniel I second that. Ronald ___ 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: IPMI serial console
On Thursday, February 21, 2013 5:55:01 pm Glen Barber wrote: On Thu, Feb 21, 2013 at 05:23:14PM -0500, John Baldwin wrote: On Thursday, February 21, 2013 4:56:02 pm Daniel O'Connor wrote: On 22/02/2013, at 2:19, John Baldwin j...@freebsd.org wrote: Does anyone have any hints? Rather than using all these hints, just use these three in loader.conf: console=comconsole vidconsole console_speed=115200 console_port=0xblah (where blah is the correct I/O port for COM3, 0x3e8 maybe?) No dice :( I also tried booting with '-D -h -S 115200' but nothing either. Sorry, those should be 'comconsole_speed' and 'comconsole_port'. Also, you should be able to get the loader prompt working if you enter those by hand using an IPMI KVM or some such. John, this sounds very similar to a question I posed to you a few weeks ago. I guess it's not just me with these weird SuperMicro BMCs. :( I am using exactly this on many SuperMicro X8 and X9 boards. -- 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: IPMI serial console
On Thursday, February 21, 2013 5:42:08 pm Daniel O'Connor wrote: On 22/02/2013, at 8:53, John Baldwin j...@freebsd.org wrote: I also tried booting with '-D -h -S 115200' but nothing either. Sorry, those should be 'comconsole_speed' and 'comconsole_port'. Also, you should be able to get the loader prompt working if you enter those by hand using an IPMI KVM or some such. No luck with that either :( The IPMI serial console works for the BIOS loader so I guess the comconsole parts work, however the kernel doesn't seem to use it even with '-D -h'. The uart(4) flags are correct (I believe) uart0: 16550 or compatible port 0x3f8-0x3ff irq 4 on acpi0 uart1: 16550 or compatible port 0x2f8-0x2ff irq 3 on acpi0 uart2: 16550 or compatible port 0x3e8-0x3ef irq 5 flags 0x30 on acpi0 The way this works with the kernel is that the loader has to be setting a hw.uart.console hint based on comconsole_port. The hint.uart.X.flags settings are completely ignored for this. Also, for 9.1, you must set the speed before you set the port (so the order of lines in loader.conf matters), or hw.uart.console will tell the kernel to use 9600 instead of 115200. -- 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: mfi timeouts
On 28/10/2011 04:14, Jan Mikkelsen wrote: / Hi, // // There is a patch linked to from this PR, which seems very similar: // // http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/140416 // // http://lists.freebsd.org/pipermail/freebsd-scsi/2011-March/004839.html // // The problem is also consistent with running mfiutil clearing the problem. // // I'm about to deploy mfi controllers in a similar configuration, so I'd be very curious about whether the patch fixes the problem for you. // /This looks promising, I'll give a try when I get a moment. Hi, Did the patch help? We're having the same issues running mfiutil show volumes every minute doesn't make the freezes go away. Will this small patch be ok on 8.2-RELEASE-p4? Thanks. ___ 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: watchdogs
Hi. On 22.02.2013 22:47, Mark Atkinson wrote: I just want to /metoo that I have 32bit/i386 box running zfs, pf and - -current that is hardlocking randomly (usually has an uptime for a few days to a couple weeks). SW_WATCHDOG won't fire when it locks so it must be locking pretty fast. I just noticed that ichwd will load on this box, so I'll try that instead, but now I'm wondering if the SW_WATCHDOG kernel will interfere or rather if watchdogd is smart enough to handle both? This box used to occasionally panic on the ZFS stack panic so I did the KSTACK_PAGES=4 change to the kernel and now it just hardlocks. I'm not saying they are related. I also have an 32-bit box running zfs/pf, and it's pretty stable (though I'm knoking on wood right now :) ): [emz@witchdoctor:~] uptime 23:25 up 291 days, 15:44, 1 user, load averages: 0,04 0,04 0,00 but it's running 8.2-STABLE: 8.2-STABLE FreeBSD 8.2-STABLE #0: Tue Sep 20 19:24:35 YEKST 2011 I've also stopped using zfs swap, I'm still not sure whether this added some stability or not, but still. To be honest it's running without any swap last 291 days. :P This machine has only 2 gigs of ram. It's a file storage, dozens of users use it. I've seen some zfs panicks, I've added options KVA_PAGES=512, and it's working like that. So maybe you should try this. I should also say that it's pf is simple and basic (a couple of pass/block rules, nothing complicated). Eugene. ___ 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.1 would not boot on pentium3 laptop
On Tuesday, February 26, 2013 1:10:37 am Mikhail T. wrote: 15.02.2013 08:49, John Baldwin ???(??): Were you able to test this patch? Yes, with the patch my laptop boots -- even after I removed the work-around (hint.ichss.0.disabled=1 from device.hints). powerd is also able to regulate the frequency -- I'm not sure, how else to test the functionality. Thank you. Yours, Perfect, thanks for testing! -- 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: mfi timeouts
On 26/02/2013 18:31, rihad wrote: On 28/10/2011 04:14, Jan Mikkelsen wrote: / Hi, // // There is a patch linked to from this PR, which seems very similar: // // http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/140416 // // http://lists.freebsd.org/pipermail/freebsd-scsi/2011-March/004839.html // // The problem is also consistent with running mfiutil clearing the problem. // // I'm about to deploy mfi controllers in a similar configuration, so I'd be very curious about whether the patch fixes the problem for you. // /This looks promising, I'll give a try when I get a moment. Hi, Did the patch help? We're having the same issues running mfiutil show volumes every minute doesn't make the freezes go away. Will this small patch be ok on 8.2-RELEASE-p4? Thanks. From what I remember this patch did help. That server has been running happily on 8.3 release for the last 300 days or so with no timeouts. Vince ___ 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: mfi timeouts
On Tuesday, February 26, 2013 1:31:44 pm rihad wrote: On 28/10/2011 04:14, Jan Mikkelsen wrote: / Hi, // // There is a patch linked to from this PR, which seems very similar: // // http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/140416 // // http://lists.freebsd.org/pipermail/freebsd-scsi/2011- March/004839.html // // The problem is also consistent with running mfiutil clearing the problem. // // I'm about to deploy mfi controllers in a similar configuration, so I'd be very curious about whether the patch fixes the problem for you. // /This looks promising, I'll give a try when I get a moment. Hi, Did the patch help? We're having the same issues running mfiutil show volumes every minute doesn't make the freezes go away. Will this small patch be ok on 8.2-RELEASE-p4? Thanks. You can use the patch on 8.2. -- 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
Outdated pci_vendors
(CC'ing philip@ since he used to be my commit mentor and is the one who did the most recent head import) Is there anyone in particular who maintains src/share/misc/pci_vendors ? The file[1] on stable/9 is over a year old, and there are some mistakes in it which have since been addressed (this was indirectly brought to my attention on a recent -stable thread involving ICH7 chipsets). It also looks like the MFC'ing of r242471 (circa November 2012) never happened[2]. I would suggest getting the latest set[3] and adding that to head, then MFC'ing that (but do we really need to wait 2 weeks? I can do a full test of it on stable/9 if need be). If all this needs is a PR + patch, just say that and I'll go do it. :-) [1]: http://svnweb.freebsd.org/base/stable/9/share/misc/pci_vendors [2]: http://svnweb.freebsd.org/base/head/share/misc/pci_vendors#rev242471 [3]: http://pciids.sourceforge.net/v2.2/pci.ids -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | 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: Outdated pci_vendors
On 27 Feb 2013, at 00:02, Jeremy Chadwick j...@koitsu.org wrote: (CC'ing philip@ since he used to be my commit mentor and is the one who did the most recent head import) Is there anyone in particular who maintains src/share/misc/pci_vendors ? I've been taking care of it for a bit. The file[1] on stable/9 is over a year old, and there are some mistakes in it which have since been addressed (this was indirectly brought to my attention on a recent -stable thread involving ICH7 chipsets). It also looks like the MFC'ing of r242471 (circa November 2012) never happened[2]. Oh, whoops. Looks like I forgot the MFC. I have been very distracted. I would suggest getting the latest set[3] and adding that to head, then MFC'ing that (but do we really need to wait 2 weeks? I can do a full test of it on stable/9 if need be). If all this needs is a PR + patch, just say that and I'll go do it. :-) I'll take care of it. Thanks for the reminder! - Philip -- Philip Paeps Senior Reality Engineer Ministry of Information ___ 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_9 tinderbox] failure on arm/arm
TB --- 2013-02-26 21:23:55 - tinderbox 2.10 running on freebsd-stable.sentex.ca TB --- 2013-02-26 21:23:55 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2013-02-26 21:23:55 - starting RELENG_9 tinderbox run for arm/arm TB --- 2013-02-26 21:23:55 - cleaning the object tree TB --- 2013-02-26 21:23:55 - checking out /src from svn://svn.freebsd.org/base/stable/9 TB --- 2013-02-26 21:23:55 - cd /tinderbox/RELENG_9/arm/arm TB --- 2013-02-26 21:23:55 - /usr/local/bin/svn cleanup /src TB --- 2013-02-26 21:24:58 - /usr/local/bin/svn update /src TB --- 2013-02-26 21:25:12 - building world TB --- 2013-02-26 21:25:12 - CROSS_BUILD_TESTING=YES TB --- 2013-02-26 21:25:12 - MAKEOBJDIRPREFIX=/obj TB --- 2013-02-26 21:25:12 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-02-26 21:25:12 - SRCCONF=/dev/null TB --- 2013-02-26 21:25:12 - TARGET=arm TB --- 2013-02-26 21:25:12 - TARGET_ARCH=arm TB --- 2013-02-26 21:25:12 - TZ=UTC TB --- 2013-02-26 21:25:12 - __MAKE_CONF=/dev/null TB --- 2013-02-26 21:25:12 - cd /src TB --- 2013-02-26 21:25:12 - /usr/bin/make -B buildworld World build started on Tue Feb 26 21:25:13 UTC 2013 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 Tue Feb 26 22:36:41 UTC 2013 TB --- 2013-02-26 22:36:42 - cd /src/sys/arm/conf TB --- 2013-02-26 22:36:42 - /usr/sbin/config -m AVILA TB --- 2013-02-26 22:36:42 - building AVILA kernel TB --- 2013-02-26 22:36:42 - CROSS_BUILD_TESTING=YES TB --- 2013-02-26 22:36:42 - MAKEOBJDIRPREFIX=/obj TB --- 2013-02-26 22:36:42 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-02-26 22:36:42 - SRCCONF=/dev/null TB --- 2013-02-26 22:36:42 - TARGET=arm TB --- 2013-02-26 22:36:42 - TARGET_ARCH=arm TB --- 2013-02-26 22:36:42 - TZ=UTC TB --- 2013-02-26 22:36:42 - __MAKE_CONF=/dev/null TB --- 2013-02-26 22:36:42 - cd /src TB --- 2013-02-26 22:36:42 - /usr/bin/make -B buildkernel KERNCONF=AVILA Kernel build for AVILA started on Tue Feb 26 22:36:42 UTC 2013 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 AVILA completed on Tue Feb 26 22:41:00 UTC 2013 TB --- 2013-02-26 22:41:00 - cd /src/sys/arm/conf TB --- 2013-02-26 22:41:00 - /usr/sbin/config -m BWCT TB --- 2013-02-26 22:41:00 - building BWCT kernel TB --- 2013-02-26 22:41:00 - CROSS_BUILD_TESTING=YES TB --- 2013-02-26 22:41:00 - MAKEOBJDIRPREFIX=/obj TB --- 2013-02-26 22:41:00 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-02-26 22:41:00 - SRCCONF=/dev/null TB --- 2013-02-26 22:41:00 - TARGET=arm TB --- 2013-02-26 22:41:00 - TARGET_ARCH=arm TB --- 2013-02-26 22:41:00 - TZ=UTC TB --- 2013-02-26 22:41:00 - __MAKE_CONF=/dev/null TB --- 2013-02-26 22:41:00 - cd /src TB --- 2013-02-26 22:41:00 - /usr/bin/make -B buildkernel KERNCONF=BWCT Kernel build for BWCT started on Tue Feb 26 22:41:00 UTC 2013 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 BWCT completed on Tue Feb 26 22:43:51 UTC 2013 TB --- 2013-02-26 22:43:51 - cd /src/sys/arm/conf TB --- 2013-02-26 22:43:51 - /usr/sbin/config -m CAMBRIA TB --- 2013-02-26 22:43:51 - building CAMBRIA kernel TB --- 2013-02-26 22:43:51 - CROSS_BUILD_TESTING=YES TB --- 2013-02-26 22:43:51 - MAKEOBJDIRPREFIX=/obj TB --- 2013-02-26 22:43:51 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-02-26 22:43:51 - SRCCONF=/dev/null TB --- 2013-02-26 22:43:51 - TARGET=arm TB --- 2013-02-26 22:43:51 - TARGET_ARCH=arm TB --- 2013-02-26 22:43:51 - TZ=UTC TB --- 2013-02-26 22:43:51 - __MAKE_CONF=/dev/null TB --- 2013-02-26 22:43:51 - cd /src TB --- 2013-02-26 22:43:51 - /usr/bin/make -B buildkernel KERNCONF=CAMBRIA Kernel build for CAMBRIA started on Tue Feb 26 22:43:51 UTC 2013 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 CAMBRIA completed on Tue Feb 26 22:47:13 UTC 2013 TB --- 2013-02-26 22:47:13 - cd /src/sys/arm/conf TB --- 2013-02-26 22:47:13 - /usr/sbin/config -m CNS11XXNAS TB --- 2013-02-26 22:47:13 - building CNS11XXNAS kernel TB --- 2013-02-26 22:47:13 - CROSS_BUILD_TESTING=YES TB --- 2013-02-26 22:47:13 - MAKEOBJDIRPREFIX=/obj TB --- 2013-02-26 22:47:13 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-02-26 22:47:13 -
Re: mfi timeouts
- Original Message - From: rihad ri...@mail.ru On 28/10/2011 04:14, Jan Mikkelsen wrote: / Hi, // // There is a patch linked to from this PR, which seems very similar: // // http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/140416 // // http://lists.freebsd.org/pipermail/freebsd-scsi/2011-March/004839.html // // The problem is also consistent with running mfiutil clearing the problem. // // I'm about to deploy mfi controllers in a similar configuration, so I'd be very curious about whether the patch fixes the problem for you. // /This looks promising, I'll give a try when I get a moment. Hi, Did the patch help? We're having the same issues running mfiutil show volumes every minute doesn't make the freezes go away. Will this small patch be ok on 8.2-RELEASE-p4? Thanks. I'm about to commit a major patch to mfi, which many problems with the current driver. Given info in that PR it could well fix this problem. Unfortunately due to the number of changes, its likely to sit in head for a while before it gets MFC, just to be safe. We've been running it on 8.3-RELEASE on top of the driver from head for some months and not issues so far. So if anyone is interested in a patchset for that I'll be able to provide. I'll post a link to the commit when I'm done. Regards Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk. ___ 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_9 tinderbox] failure on i386/i386
TB --- 2013-02-26 22:56:48 - tinderbox 2.10 running on freebsd-stable.sentex.ca TB --- 2013-02-26 22:56:48 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2013-02-26 22:56:48 - starting RELENG_9 tinderbox run for i386/i386 TB --- 2013-02-26 22:56:48 - cleaning the object tree TB --- 2013-02-26 22:56:48 - checking out /src from svn://svn.freebsd.org/base/stable/9 TB --- 2013-02-26 22:56:48 - cd /tinderbox/RELENG_9/i386/i386 TB --- 2013-02-26 22:56:48 - /usr/local/bin/svn cleanup /src TB --- 2013-02-26 22:58:02 - /usr/local/bin/svn update /src TB --- 2013-02-26 22:58:16 - building world TB --- 2013-02-26 22:58:16 - CROSS_BUILD_TESTING=YES TB --- 2013-02-26 22:58:16 - MAKEOBJDIRPREFIX=/obj TB --- 2013-02-26 22:58:16 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-02-26 22:58:16 - SRCCONF=/dev/null TB --- 2013-02-26 22:58:16 - TARGET=i386 TB --- 2013-02-26 22:58:16 - TARGET_ARCH=i386 TB --- 2013-02-26 22:58:16 - TZ=UTC TB --- 2013-02-26 22:58:16 - __MAKE_CONF=/dev/null TB --- 2013-02-26 22:58:16 - cd /src TB --- 2013-02-26 22:58:16 - /usr/bin/make -B buildworld World build started on Tue Feb 26 22:58:17 UTC 2013 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 Wed Feb 27 01:58:13 UTC 2013 TB --- 2013-02-27 01:58:13 - generating LINT kernel config TB --- 2013-02-27 01:58:13 - cd /src/sys/i386/conf TB --- 2013-02-27 01:58:13 - /usr/bin/make -B LINT TB --- 2013-02-27 01:58:13 - cd /src/sys/i386/conf TB --- 2013-02-27 01:58:13 - /usr/sbin/config -m LINT TB --- 2013-02-27 01:58:13 - building LINT kernel TB --- 2013-02-27 01:58:13 - CROSS_BUILD_TESTING=YES TB --- 2013-02-27 01:58:13 - MAKEOBJDIRPREFIX=/obj TB --- 2013-02-27 01:58:13 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-02-27 01:58:13 - SRCCONF=/dev/null TB --- 2013-02-27 01:58:13 - TARGET=i386 TB --- 2013-02-27 01:58:13 - TARGET_ARCH=i386 TB --- 2013-02-27 01:58:13 - TZ=UTC TB --- 2013-02-27 01:58:13 - __MAKE_CONF=/dev/null TB --- 2013-02-27 01:58:13 - cd /src TB --- 2013-02-27 01:58:13 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Wed Feb 27 01:58:13 UTC 2013 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 [...] uudecode -o mwlboot.fw /src/sys/contrib/dev/mwl/mwlboot.fw.uu ld -b binary --no-warn-mismatch -d -warn-common -r -o mwlboot.fwo mwlboot.fw 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 -Wmissing-include-dirs -fdiagnostics-show-option -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-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/mxge/if_mxge.c cc1: warnings being treated as errors /src/sys/dev/mxge/if_mxge.c: In function 'mxge_intr': /src/sys/dev/mxge/if_mxge.c:3105: warning: large integer implicitly truncated to unsigned type [-Woverflow] /src/sys/dev/mxge/if_mxge.c: In function 'mxge_attach': /src/sys/dev/mxge/if_mxge.c:4897: warning: large integer implicitly truncated to unsigned type [-Woverflow] *** Error code 1 Stop in /obj/i386.i386/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-02-27 02:10:03 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-02-27 02:10:03 - ERROR: failed to build LINT kernel TB --- 2013-02-27 02:10:03 - 8407.99 user 939.84 system 11595.64 real http://tinderbox.freebsd.org/tinderbox-releng_9-RELENG_9-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_9 tinderbox] failure on i386/pc98
TB --- 2013-02-26 23:01:23 - tinderbox 2.10 running on freebsd-stable.sentex.ca TB --- 2013-02-26 23:01:23 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2013-02-26 23:01:23 - starting RELENG_9 tinderbox run for i386/pc98 TB --- 2013-02-26 23:01:23 - cleaning the object tree TB --- 2013-02-26 23:01:23 - checking out /src from svn://svn.freebsd.org/base/stable/9 TB --- 2013-02-26 23:01:23 - cd /tinderbox/RELENG_9/i386/pc98 TB --- 2013-02-26 23:01:23 - /usr/local/bin/svn cleanup /src TB --- 2013-02-26 23:02:38 - /usr/local/bin/svn update /src TB --- 2013-02-26 23:02:48 - building world TB --- 2013-02-26 23:02:48 - CROSS_BUILD_TESTING=YES TB --- 2013-02-26 23:02:48 - MAKEOBJDIRPREFIX=/obj TB --- 2013-02-26 23:02:48 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-02-26 23:02:48 - SRCCONF=/dev/null TB --- 2013-02-26 23:02:48 - TARGET=pc98 TB --- 2013-02-26 23:02:48 - TARGET_ARCH=i386 TB --- 2013-02-26 23:02:48 - TZ=UTC TB --- 2013-02-26 23:02:48 - __MAKE_CONF=/dev/null TB --- 2013-02-26 23:02:48 - cd /src TB --- 2013-02-26 23:02:48 - /usr/bin/make -B buildworld World build started on Tue Feb 26 23:02:49 UTC 2013 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 Wed Feb 27 02:02:03 UTC 2013 TB --- 2013-02-27 02:02:03 - generating LINT kernel config TB --- 2013-02-27 02:02:03 - cd /src/sys/pc98/conf TB --- 2013-02-27 02:02:03 - /usr/bin/make -B LINT TB --- 2013-02-27 02:02:03 - cd /src/sys/pc98/conf TB --- 2013-02-27 02:02:03 - /usr/sbin/config -m LINT TB --- 2013-02-27 02:02:04 - building LINT kernel TB --- 2013-02-27 02:02:04 - CROSS_BUILD_TESTING=YES TB --- 2013-02-27 02:02:04 - MAKEOBJDIRPREFIX=/obj TB --- 2013-02-27 02:02:04 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-02-27 02:02:04 - SRCCONF=/dev/null TB --- 2013-02-27 02:02:04 - TARGET=pc98 TB --- 2013-02-27 02:02:04 - TARGET_ARCH=i386 TB --- 2013-02-27 02:02:04 - TZ=UTC TB --- 2013-02-27 02:02:04 - __MAKE_CONF=/dev/null TB --- 2013-02-27 02:02:04 - cd /src TB --- 2013-02-27 02:02:04 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Wed Feb 27 02:02:04 UTC 2013 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 -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 -Wmissing-include-dirs -fdiagnostics-show-option -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-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/mwl/if_mwl_pci.c 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 -Wmissing-include-dirs -fdiagnostics-show-option -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-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/mwl/mwlhal.c 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 -Wmissing-include-dirs -fdiagnostics-show-option -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-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/mxge/if_mxge.c cc1: warnings being treated as errors /src/sys/dev/mxge/if_mxge.c: In
Re: mfi timeouts
On 02/27/2013 12:48 AM, John Baldwin wrote: On Tuesday, February 26, 2013 1:31:44 pm rihad wrote: On 28/10/2011 04:14, Jan Mikkelsen wrote: / Hi, // // There is a patch linked to from this PR, which seems very similar: // // http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/140416 // // http://lists.freebsd.org/pipermail/freebsd-scsi/2011- March/004839.html // // The problem is also consistent with running mfiutil clearing the problem. // // I'm about to deploy mfi controllers in a similar configuration, so I'd be very curious about whether the patch fixes the problem for you. // /This looks promising, I'll give a try when I get a moment. Hi, Did the patch help? We're having the same issues running mfiutil show volumes every minute doesn't make the freezes go away. Will this small patch be ok on 8.2-RELEASE-p4? Thanks. You can use the patch on 8.2. Thanks, I was forced to apply the patch to 8.2-p4 and rebuild the kernel yesterday in the night, as it sometimes locks up both interfaces in periods of high disk/net activity (around 4-5 gbit/s passing through). Has anyone had full system lock-ups besides the i/o stall mfi timeout errors? I hope those issues are related. In such cases sometimes one of the interfaces lives, sometimes both are down. Happened 2-3 times during a little over a month. Now about this part taken from here http://lists.freebsd.org/pipermail/freebsd-scsi/2011-March/004839.html By issuing a dummy read operation (thus forcing a flush of data buffers), this issue is largely averted. Does this mean that battery-backed cache (BBU) is effectively rendered useless, as all write operations are forced on to the disk platters on every interrupt? # mfiutil show adapter mfi0 Adapter: Product Name: Integrated Intel(R) RAID Controller SROMBSASMP2 Serial Number: Firmware: 8.0.1-0033 RAID Levels: JBOD, RAID0, RAID1, RAID5, RAID6, RAID10, RAID50 Battery Backup: present NVRAM: 32K Onboard Memory: 512M Minimum Stripe: 8K Maximum Stripe: 1M ___ 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: mfi timeouts
On 02/27/2013 03:39 AM, Steven Hartland wrote: - Original Message - From: rihad ri...@mail.ru On 28/10/2011 04:14, Jan Mikkelsen wrote: / Hi, // // There is a patch linked to from this PR, which seems very similar: // // http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/140416 // // http://lists.freebsd.org/pipermail/freebsd-scsi/2011-March/004839.html // // The problem is also consistent with running mfiutil clearing the problem. // // I'm about to deploy mfi controllers in a similar configuration, so I'd be very curious about whether the patch fixes the problem for you. // /This looks promising, I'll give a try when I get a moment. Hi, Did the patch help? We're having the same issues running mfiutil show volumes every minute doesn't make the freezes go away. Will this small patch be ok on 8.2-RELEASE-p4? Thanks. I'm about to commit a major patch to mfi, which many problems with the current driver. Given info in that PR it could well fix this problem. Unfortunately due to the number of changes, its likely to sit in head for a while before it gets MFC, just to be safe. We've been running it on 8.3-RELEASE on top of the driver from head for some months and not issues so far. So if anyone is interested in a patchset for that I'll be able to provide. I'll post a link to the commit when I'm done. Thanks, if the trivial dummy read proves insufficient, sure I'll need to look into that :) Thanks. ___ 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
Odd issue with VirtualBox+9-STABLE+bce ...
I'm experiencing some odd issues with Virtualbox running on 9-STABLE. where my network periodically disappears … sometimes, it comes back again after a few minutes, other times I have to reboot the server … This last time, the error on the screen states: bce1: bce_pulse(): Warning: boot code thinks driver is absent! (bc_state = 0x4006) I had 20 regular 'jail' VPSs running on it before I tried VirtualBox on it,and never had this problem, so figure it has to be something with VirtualBox / kmod … ? Anyone experiencing any odd issues with VirtualBox and 9-STABLE? Pointers / ideas? Thx … ___ 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
