Re: gmirror problem with HP Proliant ML110 G5
On 17/apr/08, at 19:28, Josep Pujadas i Jubany wrote: Two weeks ago I installed FreeBSD 7.0 in a new HP Proliant ML110 G5 machine and I configured ad0 for using gmirror, waiting for a second disk. I just added a second hard disk arrived today from HP ... # gmirror insert gm0 /dev/ad2 I'm having DMA errors: Apr 17 16:49:55 mail_2 kernel: GEOM_MIRROR: Device gm0: rebuilding provider ad2. Apr 17 16:50:13 mail_2 kernel: ad2: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=1534720 Apr 17 16:50:46 mail_2 kernel: ad2: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4563840 ... ... Apr 17 17:39:28 mail_2 kernel: ad2: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=268281088 Apr 17 17:39:46 mail_2 kernel: ad2: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=269601536 Apr 17 17:39:46 mail_2 kernel: ad2: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=269601536 Apr 17 17:39:46 mail_2 kernel: GEOM_MIRROR: Synchronization request failed (error=5). ad2[WRITE(offset=138035986432, length=131072)] Apr 17 17:39:46 mail_2 kernel: GEOM_MIRROR: Device gm0: provider ad2 disconnected. Apr 17 17:39:46 mail_2 kernel: GEOM_MIRROR: Device gm0: rebuilding provider ad2 stopped. Disks are equal in capactiy: Apr 17 16:40:48 mail_2 kernel: ad0: 238475MB Seagate ST3250620NS 3BJP at ata0-master SATA150 Apr 17 16:40:48 mail_2 kernel: ad2: 238475MB GB0250C8045 HPG1 at ata1- master SATA150 # atacontrol list ATA channel 0: Master: ad0 ST3250620NS/3BJP Serial ATA v1.0 Slave: no device present ATA channel 1: Master: ad2 GB0250C8045/HPG1 Serial ATA v1.0 Slave: no device present ATA channel 2: Master: acd0 HL-DT-ST DVD-RAM GSA-H60L/E904 Serial ATA v1.0 Slave: no device present ATA channel 3: Master: no device present Slave: no device present Any ideas? Thanks, Josep Pujadas There are a few reports of this on the freebsd-stable mailing list in March and I'm also experiencing the same problem, so far none of the suggested resolutions has helped for me. http://lists.freebsd.org/pipermail/freebsd-stable/2008-March/thread.html I've got the issue on a custom built box with amd64 + 7.0 + gmirror and I've got a Proliant ML110 G5 running 6.3 I'd like to upgrade to 7.0 but too scared to do so until this issue appears to have been identified and fixed. Copying in freebsd-stable as it's not just a problem on Proliant. -Gianni ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re[2]: freebsd i386 releng_7 odd problem - cant shut down
-- Friday, April 18, 2008, 2:13:56 AM: On Thu, Apr 17, 2008 at 10:57:52PM +0300, Georgi Iovchev wrote: Hello list I have really strange problem. When I select shut down (from gnome, or manually from console halt -p) the system begins to shutdown. Actually everything looks fine ... it sh uts down correctly. Hard drives goes down, monitor is turned off etc... But after a few seconds the computer powers on by itself This behaviour begen a few days ago ... I really cant remember what I did this time... Yesterday I updated all sources and ports, recompilled world and ke rnel. But the shutdown problem still exists. I tought that my motherboard may be broken. I have windows server 2 003 too, but with windows the shutdown works ok. So I think, my mobo is ok. Try playing with sysctls hw.acpi.disable_on_reboot and hw.acpi.handle_reboot. Hello again, 10x for answer I tried both (00,01,10,11 :) in any case it didn't help, I still cant shutdown my computer. I am recomiling my kernel now with device acpi options ACPI_DEBUG ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gmirror problem with HP Proliant ML110 G5
On Fri, Apr 18, 2008 at 07:12:06AM +0200, Gianni wrote: On 17/apr/08, at 19:28, Josep Pujadas i Jubany wrote: Two weeks ago I installed FreeBSD 7.0 in a new HP Proliant ML110 G5 machine and I configured ad0 for using gmirror, waiting for a second disk. I just added a second hard disk arrived today from HP ... # gmirror insert gm0 /dev/ad2 I'm having DMA errors: Apr 17 16:49:55 mail_2 kernel: GEOM_MIRROR: Device gm0: rebuilding provider ad2. Apr 17 16:50:13 mail_2 kernel: ad2: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=1534720 Apr 17 16:50:46 mail_2 kernel: ad2: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4563840 ... ... Apr 17 17:39:28 mail_2 kernel: ad2: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=268281088 Apr 17 17:39:46 mail_2 kernel: ad2: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=269601536 Apr 17 17:39:46 mail_2 kernel: ad2: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=269601536 Apr 17 17:39:46 mail_2 kernel: GEOM_MIRROR: Synchronization request failed (error=5). ad2[WRITE(offset=138035986432, length=131072)] Apr 17 17:39:46 mail_2 kernel: GEOM_MIRROR: Device gm0: provider ad2 disconnected. Apr 17 17:39:46 mail_2 kernel: GEOM_MIRROR: Device gm0: rebuilding provider ad2 stopped. Disks are equal in capactiy: Apr 17 16:40:48 mail_2 kernel: ad0: 238475MB Seagate ST3250620NS 3BJP at ata0-master SATA150 Apr 17 16:40:48 mail_2 kernel: ad2: 238475MB GB0250C8045 HPG1 at ata1- master SATA150 # atacontrol list ATA channel 0: Master: ad0 ST3250620NS/3BJP Serial ATA v1.0 Slave: no device present ATA channel 1: Master: ad2 GB0250C8045/HPG1 Serial ATA v1.0 Slave: no device present ATA channel 2: Master: acd0 HL-DT-ST DVD-RAM GSA-H60L/E904 Serial ATA v1.0 Slave: no device present ATA channel 3: Master: no device present Slave: no device present Any ideas? Thanks, Josep Pujadas Josep, the disks may be the same in capacity, but they aren't completely identical. It's fairly obvious one is a Seagate and the other is HP/Compaq drive. This is very likely **not** the cause of the DMA errors you're seeing, but I did want to take a moment to state that mix-matching drives with different semantics in a mirror is somewhat risky. There are a few reports of this on the freebsd-stable mailing list in March and I'm also experiencing the same problem, so far none of the suggested resolutions has helped for me. http://lists.freebsd.org/pipermail/freebsd-stable/2008-March/thread.html I've got the issue on a custom built box with amd64 + 7.0 + gmirror and I've got a Proliant ML110 G5 running 6.3 I'd like to upgrade to 7.0 but too scared to do so until this issue appears to have been identified and fixed. Copying in freebsd-stable as it's not just a problem on Proliant. -Gianni I've documented the DMA problem quite thoroughly. The DMA errors are not specific to gmirror: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues If the problem is easily repeatable, and you have serial console available on the box, please contact Scott Long who has offered to help track the source of these problems down. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | 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 [EMAIL PROTECTED]
Re: Dreadful gmirror performance, though each half works fine
Pete French wrote: I have experimented with this rather extensively and have operationally decided not to use ggated in combination with gmirror --- it doesn't appear to work as well as one might expect. Ah, thats unmfortunate :-( I oroginally started off using the iscsi initiator and target, which did work O.K., but when actually ran live ended up locking up after several hours,a nd then panicing Some problems with the iSCSI initiator were found a bit after 7.0-RELEASE was made, they should have been fixed by now in 7-STABLE. If not, try the patch that appears in this thread: http://lists.freebsd.org/pipermail/freebsd-scsi/2008-February/003383.html signature.asc Description: OpenPGP digital signature
Re: gmirror problem with HP Proliant ML110 G5
Jeremy Chadwick [EMAIL PROTECTED] wrote at 02:20 on 2008-04-18: I've documented the DMA problem quite thoroughly. The DMA errors are not specific to gmirror: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues If the problem is easily repeatable, and you have serial console available on the box, please contact Scott Long who has offered to help track the source of these problems down. Just thought I'd mention that I saw lots of DMA errors when installing Nexenta (OpenSolaris kernel) 1.0RC2 on an ML110 G5 using a ZFS mirror of two 1G Seagate Barracuda ES SATAs. The DMA timeouts vanished when I tried again with Nexenta 1.0 proper. Might it be worth someone having a look at the Solaris SATA driver diffs to see if any insight can be gained? S ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panics on 6.3-RELEASE in IP stack
Bruce M. Simpson wrote: I started to play with RAT application (ports: mbone/rat + an SVN version) and it seems to crash my 6.3-RELEASE-p1 box in rather deterministic way. Crash details are shown below. Has anyone seen a problem like this? Yes, there's an off-by-one reference count bug in the multicast stuff. I concur, this fix should really be MFCed. The problem went away in 7.x due to a total rewrite. I am distracted by other stuff at the moment, so, starter's orders... This just bit me. The fix is in RELENG_6, but it is not present after the -p1 tag. So updating to STABLE should fix the problem for Petr. Whilst 6 is no longer the STABLE branch, I think this really should go onto 6 in case any other releases happen from that branch. cheers BMS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dreadful gmirror performance, though each half works fine
Some problems with the iSCSI initiator were found a bit after 7.0-RELEASE was made, they should have been fixed by now in 7-STABLE. If not, try the patch that appears in this thread: http://lists.freebsd.org/pipermail/freebsd-scsi/2008-February/003383.html= Ah, excellent, thankyou. This patch is not uyet in -STABLE though, but I will give it a try and see if that helps. It does explain why I diidn't find this in testing - all my test boxes are single core, os don't show up problems like this (am rectifying that soon). -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_7 tinderbox] failure on ia64/ia64
TB --- 2008-04-18 11:00:39 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-04-18 11:00:39 - starting RELENG_7 tinderbox run for ia64/ia64 TB --- 2008-04-18 11:00:39 - cleaning the object tree TB --- 2008-04-18 11:00:55 - cvsupping the source tree TB --- 2008-04-18 11:00:55 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/ia64/ia64/supfile TB --- 2008-04-18 11:01:01 - building world (CFLAGS=-O2 -pipe) TB --- 2008-04-18 11:01:01 - cd /src TB --- 2008-04-18 11:01:01 - /usr/bin/make -B buildworld World build started on Fri Apr 18 11:01:02 UTC 2008 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 Apr 18 12:27:23 UTC 2008 TB --- 2008-04-18 12:27:23 - generating LINT kernel config TB --- 2008-04-18 12:27:23 - cd /src/sys/ia64/conf TB --- 2008-04-18 12:27:23 - /usr/bin/make -B LINT TB --- 2008-04-18 12:27:24 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2008-04-18 12:27:24 - cd /src TB --- 2008-04-18 12:27:24 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Fri Apr 18 12:27:24 UTC 2008 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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/dev/cmx/cmx_pccard.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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/dev/cnw/if_cnw.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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/dev/cxgb/cxgb_main.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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/dev/cxgb/cxgb_offload.c cc1: warnings being treated as errors /src/sys/dev/cxgb/cxgb_offload.c: In function 'do_bad_cpl': /src/sys/dev/cxgb/cxgb_offload.c:318: warning: implicit declaration of function 'kdb_backtrace' /src/sys/dev/cxgb/cxgb_offload.c:318: warning: nested extern declaration of 'kdb_backtrace' *** Error code 1 Stop in /obj/ia64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-04-18 12:32:41 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-04-18 12:32:41 - ERROR: failed to build lint kernel TB --- 2008-04-18 12:32:41 - tinderbox aborted TB --- 4691.20 user 377.33 system 5522.18 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-ia64-ia64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ZFS Bittorent - Hang?
OK. I've been able to reproduce the issue. Conditions: - Stock shipped kernel and modules from RELENG 7.0 loader.conf settings: - zfs prefetch enabled - zfs zil disabled - vm.kmem_size_max=1073741824 - vm.kmem_size=1073741824 AMD64 on Core 2 Duo w/ 4 GB RAM raidz across 4 disks, using root on zfs (also experienced this hang with zfs just on /usr) How To Reproduce - install transmission-daemon, run transmission-daemon (it will daemonize, automatically backgrounding) - grab a torrent, such as KNOPPIX (http://torrent.unix-ag.uni-kl.de/) - transmission-remote -a torrentfile (add the torrent) - transmission-remote -s all (start all the torrents) wait hours to a day or so with whatever you want logging things running and active since anything that hits disk after the hang will get hung as well I've just done this twice. It doesn't seem to happen with zil enabled and prefetch off. Expected Behavior No hang. jbsnyder wrote: Thanks for the followup. I have not yet gotten a reliable test case to reproduce the problem. I've done a number of tests with the zil and/or prefetch on with no hangs. I will be collecting some more data later this week. If anyone knows a source of consistently slow but large torrents (I suppose I could artificially limit bandwidth, or connection states at my router which is running pfSense), that might help for testing. The process that triggered things before was about a gigabyte or two but took around 12 hours to complete. Here's the overall group of variables I'm experimenting with. Stock Kernel vs Recompiled Kerel w/ ULE (stock sources otherwise) ZIL on and off prefetch on and off Should I add or remove anything? I have no idea if ULE may or may not play a role here, but my original failing condition had the zil off, prefetch on, ule for the scheduler. I also had: vm.kmem_size_max=1073741824 (loader.conf) vm.kmem_size=1073741824 (loader.conf) Any recommendations on what to leave running to record what zfs is getting hung on, beside watching states? Since I can fire up things prior to the hang, and they'll keep running if disk isn't hit, I could leave some diagnostics running to display what's blowing up. Thanks! On Tue, Apr 15, 2008 at 4:44 AM, Claus Guttesen [EMAIL PROTECTED] wrote: http://wiki.freebsd.org/ZFSKnownProblems This looks like #1. Hmm.. I don't think there's a large amount of transfer between UFS ZFS, unless the client is using /tmp a lot, it should all be on ZFS. I noted #4 as well, and therefore tried disabling prefetch. I can't seem to get it to hang now. I queued up a bunch of different torrents (full freebsd 7 amd64 i386, some other random things), and they all completed without leading to me being locked out or any processes waiting on zfs. I'll try some testing this weekend to see if I can reproduce the lock-up again by re-enabling prefetch. Perhaps we can confirm that issue? Should I bother with trying to run CURRENT or should any testing I do be done with STABLE. I don't see any indication that there might be experimental patches for dealing with this or related issues. Were you able to reproduce the lock-up by re-enabling prefetch? -- regards Claus When lenity and cruelty play for a kingdom, the gentlest gamester is the soonest winner. Shakespeare -- James Snyder Biomedical Engineering Northwestern University [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/ZFS---Bittorent--%3E-Hang--tp16447331p16763410.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
connection reset after second syn-ack was sent (FreeBSD 7.0)
Hello, I have a little problem here that is driving me nuts: I occasionally experience the following: 2008-04-18 10:38:46.454495 IP 192.168.1.1.55784 192.168.188.188.515: S 2765551688:2765551688(0) win 32768 mss 1460,wscale 0,nop 2008-04-18 10:38:46.454507 IP 192.168.188.188.515 192.168.1.1.55784: S 3468383339:3468383339(0) ack 2765551689 win 65535 mss 1460,nop,wscale 3 2008-04-18 10:38:49.453868 IP 192.168.188.188.515 192.168.1.1.55784: S 3468383339:3468383339(0) ack 2765551689 win 65535 mss 1460,nop,wscale 3 2008-04-18 10:38:49.722767 IP 192.168.1.1.55784 192.168.188.188.515: . ack 1 win 32768 2008-04-18 10:38:49.722786 IP 192.168.188.188.515 192.168.1.1.55784: R 3468383340:3468383340(0) win 0 2008-04-18 10:38:49.727926 IP 192.168.1.1.55784 192.168.188.188.515: P 1:7(6) ack 1 win 32768 2008-04-18 10:38:49.819709 IP 192.168.188.188.515 192.168.1.1.55784: P 1:2(1) ack 7 win 65535 2008-04-18 10:38:50.006543 IP 192.168.1.1.55784 192.168.188.188.515: R 2765551695:2765551695(0) win 0 and 2008-04-18 15:30:31.256246 IP 192.168.1.1.53597 192.168.188.188.515: S 1236263266:1236263266(0) win 32768 mss 1460,wscale 0,nop 2008-04-18 15:30:31.256257 IP 192.168.188.188.515 192.168.1.1.53597: S 559988198:559988198(0) ack 1236263267 win 65535 mss 1460,nop,wscale 3 2008-04-18 15:30:34.255479 IP 192.168.188.188.515 192.168.1.1.53597: S 559988198:559988198(0) ack 1236263267 win 65535 mss 1460,nop,wscale 3 2008-04-18 15:30:34.440092 IP 192.168.1.1.53597 192.168.188.188.515: . ack 1 win 32768 2008-04-18 15:30:34.440112 IP 192.168.188.188.515 192.168.1.1.53597: R 559988199:559988199(0) win 0 2008-04-18 15:30:34.496849 IP 192.168.1.1.53597 192.168.188.188.515: P 1:7(6) ack 1 win 32768 2008-04-18 15:30:34.596461 IP 192.168.188.188.515 192.168.1.1.53597: . ack 7 win 65535 2008-04-18 15:30:34.620914 IP 192.168.188.188.515 192.168.1.1.53597: P 1:2(1) ack 7 win 65535 2008-04-18 15:30:34.780723 IP 192.168.1.1.53597 192.168.188.188.515: R 1236263273:1236263273(0) win 0 2008-04-18 15:30:34.804966 IP 192.168.1.1.53597 192.168.188.188.515: R 1236263273:1236263273(0) win 0 (IP addresses changed to protect the innocent ;-) Can anyone enlighten me as to why the freebsd printserver (192.168.188.188) is sending a reset after ack had been received - this only happens if no answer was received for the first syn-ack reply, so a second one is send out? System is 7.0-RELEASE out of the box on a single-processor 2.4GHz P4 Compaq with 1 GB main memory, with lpd configured. Here the usual behaviour (I would expect this to be the same even with two syn-acks send back): 2008-04-18 10:38:47.921055 IP 192.168.1.1.55786 192.168.188.188.515: S 2765866087:2765866087(0) win 32768 mss 1460,wscale 0,nop 2008-04-18 10:38:47.921081 IP 192.168.188.188.515 192.168.1.1.55786: S 4178311531:4178311531(0) ack 2765866088 win 65535 mss 1460,nop,wscale 3 2008-04-18 10:38:48.389707 IP 192.168.1.1.55786 192.168.188.188.515: P 1:7(6) ack 1 win 32768 2008-04-18 10:38:48.488906 IP 192.168.188.188.515 192.168.1.1.55786: . ack 7 win 8211 2008-04-18 10:38:49.760593 IP 192.168.188.188.515 192.168.1.1.55786: P 1:2(1) ack 7 win 8212 2008-04-18 10:38:49.945735 IP 192.168.1.1.55786 192.168.188.188.515: P 7:26(19) ack 2 win 32768 2008-04-18 10:38:49.946002 IP 192.168.188.188.515 192.168.1.1.55786: P 2:3(1) ack 26 win 8212 2008-04-18 10:38:50.236467 IP 192.168.1.1.55786 192.168.188.188.515: P 26:1050(1024) ack 3 win 32768 2008-04-18 10:38:50.244742 IP 192.168.1.1.55786 192.168.188.188.515: P 1050:2074(1024) ack 3 win 32768 2008-04-18 10:38:50.244762 IP 192.168.188.188.515 192.168.1.1.55786: . ack 2074 win 8084 2008-04-18 10:38:50.253217 IP 192.168.1.1.55786 192.168.188.188.515: P 2074:3098(1024) ack 3 win 32768 2008-04-18 10:38:50.261559 IP 192.168.1.1.55786 192.168.188.188.515: P 3098:4122(1024) ack 3 win 32768 2008-04-18 10:38:50.261571 IP 192.168.188.188.515 192.168.1.1.55786: . ack 4122 win 8084 [..] 2008-04-18 10:38:51.236260 IP 192.168.1.1.55786 192.168.188.188.515: P 26200:26201(1) ack 5 win 32768 2008-04-18 10:38:51.236271 IP 192.168.188.188.515 192.168.1.1.55786: . ack 26201 win 8212 2008-04-18 10:38:51.236289 IP 192.168.188.188.515 192.168.1.1.55786: P 5:6(1) ack 26201 win 8212 2008-04-18 10:38:51.539638 IP 192.168.1.1.55786 192.168.188.188.515: F 26201:26201(0) ack 6 win 32768 2008-04-18 10:38:51.539667 IP 192.168.188.188.515 192.168.1.1.55786: . ack 26202 win 8212 2008-04-18 10:38:51.539713 IP 192.168.188.188.515 192.168.1.1.55786: P 6:7(1) ack 26202 win 8212 2008-04-18 10:38:51.540199 IP 192.168.188.188.515 192.168.1.1.55786: F 7:7(0) ack 26202 win 8212 2008-04-18 10:38:51.751202 IP 192.168.1.1.55786 192.168.188.188.515: R 2765892289:2765892289(0) win 32768 2008-04-18 10:38:51.751539 IP 192.168.1.1.55786 192.168.188.188.515: R 2765892289:2765892289(0) win 0 Best regards, Holger Kipp ___ freebsd-stable@freebsd.org mailing list
[releng_7 tinderbox] failure on powerpc/powerpc
TB --- 2008-04-18 12:15:49 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-04-18 12:15:49 - starting RELENG_7 tinderbox run for powerpc/powerpc TB --- 2008-04-18 12:15:49 - cleaning the object tree TB --- 2008-04-18 12:16:07 - cvsupping the source tree TB --- 2008-04-18 12:16:07 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/powerpc/powerpc/supfile TB --- 2008-04-18 12:16:14 - building world (CFLAGS=-O2 -pipe) TB --- 2008-04-18 12:16:14 - cd /src TB --- 2008-04-18 12:16:14 - /usr/bin/make -B buildworld World build started on Fri Apr 18 12:16:15 UTC 2008 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 Apr 18 13:22:15 UTC 2008 TB --- 2008-04-18 13:22:15 - generating LINT kernel config TB --- 2008-04-18 13:22:15 - cd /src/sys/powerpc/conf TB --- 2008-04-18 13:22:15 - /usr/bin/make -B LINT TB --- 2008-04-18 13:22:15 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2008-04-18 13:22:15 - cd /src TB --- 2008-04-18 13:22:15 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Fri Apr 18 13:22:15 UTC 2008 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 -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 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -Werror /src/sys/dev/cmx/cmx_pccard.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 -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 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -Werror /src/sys/dev/cnw/if_cnw.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 -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 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -Werror /src/sys/dev/cxgb/cxgb_main.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 -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 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -Werror /src/sys/dev/cxgb/cxgb_offload.c cc1: warnings being treated as errors /src/sys/dev/cxgb/cxgb_offload.c: In function 'do_bad_cpl': /src/sys/dev/cxgb/cxgb_offload.c:318: warning: implicit declaration of function 'kdb_backtrace' /src/sys/dev/cxgb/cxgb_offload.c:318: warning: nested extern declaration of 'kdb_backtrace' *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-04-18 13:25:47 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-04-18 13:25:47 - ERROR: failed to build lint kernel TB --- 2008-04-18 13:25:47 - tinderbox aborted TB --- 3481.16 user 356.90 system 4198.33 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-powerpc-powerpc.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_7 tinderbox] failure on sparc64/sparc64
TB --- 2008-04-18 12:32:42 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-04-18 12:32:42 - starting RELENG_7 tinderbox run for sparc64/sparc64 TB --- 2008-04-18 12:32:42 - cleaning the object tree TB --- 2008-04-18 12:32:54 - cvsupping the source tree TB --- 2008-04-18 12:32:54 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/sparc64/sparc64/supfile TB --- 2008-04-18 12:33:00 - building world (CFLAGS=-O2 -pipe) TB --- 2008-04-18 12:33:00 - cd /src TB --- 2008-04-18 12:33:00 - /usr/bin/make -B buildworld World build started on Fri Apr 18 12:33:01 UTC 2008 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 Apr 18 13:34:19 UTC 2008 TB --- 2008-04-18 13:34:19 - generating LINT kernel config TB --- 2008-04-18 13:34:19 - cd /src/sys/sparc64/conf TB --- 2008-04-18 13:34:19 - /usr/bin/make -B LINT TB --- 2008-04-18 13:34:19 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2008-04-18 13:34:19 - cd /src TB --- 2008-04-18 13:34:19 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Fri Apr 18 13:34:19 UTC 2008 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 -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 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror /src/sys/dev/cmx/cmx_pccard.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 -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 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror /src/sys/dev/cnw/if_cnw.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 -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 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror /src/sys/dev/cxgb/cxgb_main.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 -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 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror /src/sys/dev/cxgb/cxgb_offload.c cc1: warnings being treated as errors /src/sys/dev/cxgb/cxgb_offload.c: In function 'do_bad_cpl': /src/sys/dev/cxgb/cxgb_offload.c:318: warning: implicit declaration of function 'kdb_backtrace' /src/sys/dev/cxgb/cxgb_offload.c:318: warning: nested extern declaration of 'kdb_backtrace' *** Error code 1 Stop in /obj/sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-04-18 13:37:49 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-04-18 13:37:49 - ERROR: failed to build lint kernel TB --- 2008-04-18 13:37:49 - tinderbox aborted TB --- 3265.33 user 347.55 system 3907.98 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-sparc64-sparc64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: calcru: time went backwards
Larry Rosenman wrote: On Tue, 15 Apr 2008, Jeremy Chadwick wrote: And what the FAQ doesn't cover is here: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues * EIST (Intel SpeedStep) incompatibilities with Supermicro PDSMI+ motherboards (and possibly others) * Symptom: kernel outputs messages like kernel: calcru: negative runtime of -X usec for pid XX * Workaround: Disable the EIST feature in the BIOS. You can still achieve ACPI-based processor frequency throttling by using powerd(8). * Reference: http://lists.freebsd.org/pipermail/freebsd-questions/2006-October/133253.html What I find interesting is I hadn't seen these until this kernel update :( Same problem here with Tyan Toledo i3000R (S5191) motherboard if cpufreq module is loaded. 7.0-RELEASE (AMD64) didn't have this problem. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: calcru: time went backwards
On Fri, Apr 18, 2008 at 04:51:50PM +0300, Pertti Kosunen wrote: Larry Rosenman wrote: On Tue, 15 Apr 2008, Jeremy Chadwick wrote: And what the FAQ doesn't cover is here: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues * EIST (Intel SpeedStep) incompatibilities with Supermicro PDSMI+ motherboards (and possibly others) * Symptom: kernel outputs messages like kernel: calcru: negative runtime of -X usec for pid XX * Workaround: Disable the EIST feature in the BIOS. You can still achieve ACPI-based processor frequency throttling by using powerd(8). * Reference: http://lists.freebsd.org/pipermail/freebsd-questions/2006-October/133253.html What I find interesting is I hadn't seen these until this kernel update :( Same problem here with Tyan Toledo i3000R (S5191) motherboard if cpufreq module is loaded. 7.0-RELEASE (AMD64) didn't have this problem. Are you absolutely positive about this (re: amd64 not having the problem)? I can reproduce the issue documented in my Wiki page on i386 or amd64. The piece that seems to cause it, at least in the case of the PDSMI+, is EIST being enabled in the BIOS. For example, this is my a PDSMI+ system (amd64), which exhibits the problem (when EIST is enabled). EIST in the BIOS is disabled here: est0: Enhanced SpeedStep Frequency Control on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 928092806000928 device_attach: est0 attach returned 6 est1: Enhanced SpeedStep Frequency Control on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 928092806000928 device_attach: est1 attach returned 6 powerd(8) is running and working perfectly, as shown below. Look closely at dev.cpu.0.freq and freq_levels: # ps -auxw | grep powerd root 714 0.0 0.1 5628 1172 ?? Ss Wed04AM 0:10.08 /usr/sbin/powerd -p 2000 # sysctl -a | grep dev.cpu.0.freq dev.cpu.0.freq: 297 dev.cpu.0.freq_levels: 2382/-1 2084/-1 1786/-1 1488/-1 1191/-1 893/-1 595/-1 297/-1 Under heavy load, the frequency gradually steps/climbs to 2382MHz as expected. During this time, absolutely no negative runtime messages appear (and have never appeared). If I reboot the box, enable EIST in the BIOS, and start FreeBSD, negative runtime messages begin almost immediately. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | 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 [EMAIL PROTECTED]
Re: calcru: time went backwards
On Fri, 18 Apr 2008, Jeremy Chadwick wrote: On Fri, Apr 18, 2008 at 04:51:50PM +0300, Pertti Kosunen wrote: Larry Rosenman wrote: On Tue, 15 Apr 2008, Jeremy Chadwick wrote: And what the FAQ doesn't cover is here: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues * EIST (Intel SpeedStep) incompatibilities with Supermicro PDSMI+ motherboards (and possibly others) * Symptom: kernel outputs messages like kernel: calcru: negative runtime of -X usec for pid XX * Workaround: Disable the EIST feature in the BIOS. You can still achieve ACPI-based processor frequency throttling by using powerd(8). * Reference: http://lists.freebsd.org/pipermail/freebsd-questions/2006-October/133253.html What I find interesting is I hadn't seen these until this kernel update :( Same problem here with Tyan Toledo i3000R (S5191) motherboard if cpufreq module is loaded. 7.0-RELEASE (AMD64) didn't have this problem. Are you absolutely positive about this (re: amd64 not having the problem)? I can reproduce the issue documented in my Wiki page on i386 or amd64. The piece that seems to cause it, at least in the case of the PDSMI+, is EIST being enabled in the BIOS. For example, this is my a PDSMI+ system (amd64), which exhibits the problem (when EIST is enabled). EIST in the BIOS is disabled here: est0: Enhanced SpeedStep Frequency Control on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 928092806000928 device_attach: est0 attach returned 6 est1: Enhanced SpeedStep Frequency Control on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 928092806000928 device_attach: est1 attach returned 6 powerd(8) is running and working perfectly, as shown below. Look closely at dev.cpu.0.freq and freq_levels: # ps -auxw | grep powerd root 714 0.0 0.1 5628 1172 ?? Ss Wed04AM 0:10.08 /usr/sbin/powerd -p 2000 # sysctl -a | grep dev.cpu.0.freq dev.cpu.0.freq: 297 dev.cpu.0.freq_levels: 2382/-1 2084/-1 1786/-1 1488/-1 1191/-1 893/-1 595/-1 297/-1 Under heavy load, the frequency gradually steps/climbs to 2382MHz as expected. During this time, absolutely no negative runtime messages appear (and have never appeared). If I reboot the box, enable EIST in the BIOS, and start FreeBSD, negative runtime messages begin almost immediately. My cpu frequency is ALWAYS at the full-version, since I have [EMAIL PROTECTED] processes running. This didn't start happening until the latest kernel Boot bmesg. Copyright (c) 1992-2008 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 7.0-STABLE #34: Sat Apr 12 10:06:17 CDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BORG Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU5120 @ 1.86GHz (1862.01-MHz K8-class CPU) Origin = GenuineIntel Id = 0x6f6 Stepping = 6 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x4e3bdSSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF Cores per package: 2 usable memory = 4284116992 (4085 MB) avail memory = 4113575936 (3923 MB) ACPI APIC Table: PTLTD APIC FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard kbd1 at kbdmux0 cryptosoft0: software crypto on motherboard acpi0: PTLTD RSDT on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 900 cpu0: ACPI CPU on acpi0 coretemp0: CPU On-Die Thermal Sensors on cpu0 est0: Enhanced SpeedStep Frequency Control on cpu0 est0: Setting 1867 MHz p4tcc0: CPU Frequency Thermal Control on cpu0 cpu1: ACPI CPU on acpi0 coretemp1: CPU On-Die Thermal Sensors on cpu1 est1: Enhanced SpeedStep Frequency Control on cpu1 est1: Setting 1867 MHz p4tcc1: CPU Frequency Thermal Control on cpu1 cpu2: ACPI CPU on acpi0 coretemp2: CPU On-Die Thermal Sensors on cpu2 est2: Enhanced SpeedStep Frequency Control on cpu2 est2: Setting 1867 MHz p4tcc2: CPU Frequency Thermal Control on cpu2 cpu3: ACPI CPU on acpi0 coretemp3: CPU On-Die Thermal Sensors on cpu3 est3: Enhanced SpeedStep Frequency Control on cpu3 est3: Setting 1867 MHz p4tcc3: CPU Frequency Thermal Control on cpu3 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1:
g_vfs_done errors
Dear FreeBSD friends, Again I have the following errors in /var/log/messages: snip Apr 18 12:09:19 sun kernel: g_vfs_done():ar0s1g[WRITE(offset=290725068800, length=4096)]error = 5 Apr 18 12:09:25 sun kernel: g_vfs_done():ar0s1g[WRITE(offset=290725072896, length=2048)]error = 5 Apr 18 12:09:33 sun kernel: g_vfs_done():ar0s1g[WRITE(offset=290725068800, length=4096)]error = 5 Apr 18 12:09:33 sun kernel: g_vfs_done():ar0s1g[WRITE(offset=290725072896, length=2048)]error = 5 Apr 18 12:09:48 sun kernel: g_vfs_done():ar0s1g[WRITE(offset=290725068800, length=4096)]error = 5 Apr 18 12:09:48 sun kernel: g_vfs_done():ar0s1g[WRITE(offset=290725072896, length=2048)]error = 5 Apr 18 12:10:04 sun kernel: g_vfs_done():ar0s1g[WRITE(offset=290725068800, length=4096)]error = 5 Apr 18 12:10:06 sun kernel: g_vfs_done():ar0s1g[WRITE(offset=290725072896, length=2048)]error = 5 Apr 18 12:10:21 sun kernel: g_vfs_done():ar0s1g[WRITE(offset=290725068800, length=4096)]error = 5 Apr 18 12:10:21 sun kernel: g_vfs_done():ar0s1g[WRITE(offset=290725072896, length=2048)]error = 5 Apr 18 12:10:34 sun kernel: g_vfs_done():ar0s1g[WRITE(offset=290725068800, length=4096)]error = 5 ... /snip I have no clue what the errors mean, since an offset of 290725068800 seems to be ridiculous. Does anybody have a clue what is going on? I'm using FreeBSD 7.0, but found the error being reported before with previous versions of FreeBSD. I can and will provide more details on demand. Any hints are very much appreciated. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 653 27 16 23 e-mail: [EMAIL PROTECTED] Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: umass causes panic on 7 amd64
On Thu, Apr 17, 2008 at 07:13:17PM -0400, Garrett Wollman wrote: In article [EMAIL PROTECTED], [EMAIL PROTECTED] writes: Eh I think I saw something like this myself. Do you by a chance have that new device sg in your kernel? I assume you do (GENERIC) - try to drop it. I am not sure if this is some brokenness of that driver or fighting of several USB drivers over the same hardware. In my experience, umass over EHCI has never worked on any machine ever, going back to 5.x and over multiple kinds of umass devices. (I I've had several machines with VIA chipsets where ehci never was a problem. My current machine has: usb4: VIA VT6202 USB 2.0 controller on ehci0 uhub4: VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 on usb4 uhub4: 8 ports with 8 removable, self powered A 256MB usb flash drive works OK with this controller: umass0: vendor 0x3538 USB Mass Storage Device, class 0/0, rev 2.00/1.00, addr 2 on uhub4 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Generic USB Flash Disk 0.00 Removable Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: 250MB (512000 512 byte sectors: 64H 32S/T 250C) As does an external harddisk enclosure. umass0: JMicron USB to ATA/ATAPI Bridge, class 0/0, rev 2.00/1.00, addr 2 on u hub4 da0 at umass-sim0 bus 0 target 0 lun 0 da0: WDC WD25 00JB-00REA0 0K20 Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: 238475MB (488397168 512 byte sectors: 255H 63S/T 30401C) I've never had read/write or data corruption problems with these. Only when copying from _and_ to GELI encrypted devices has the transfer stalled occasionally. But that's probably due to my (single core) CPU running out of steam. In my experience machines with Via chipsets have always worked well and are very well supported by FreeBSD's drivers. Likewise I've avoided nvidia stuff because of the lack of support. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpGI2EyxG2mP.pgp Description: PGP signature
Re: calcru: time went backwards
On Fri, 18 Apr 2008, Jeremy Chadwick wrote: On Fri, Apr 18, 2008 at 04:51:50PM +0300, Pertti Kosunen wrote: Larry Rosenman wrote: On Tue, 15 Apr 2008, Jeremy Chadwick wrote: And what the FAQ doesn't cover is here: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues * EIST (Intel SpeedStep) incompatibilities with Supermicro PDSMI+ motherboards (and possibly others) * Symptom: kernel outputs messages like kernel: calcru: negative runtime of -X usec for pid XX * Workaround: Disable the EIST feature in the BIOS. You can still achieve ACPI-based processor frequency throttling by using powerd(8). * Reference: http://lists.freebsd.org/pipermail/freebsd-questions/2006-October/133253.html What I find interesting is I hadn't seen these until this kernel update :( Same problem here with Tyan Toledo i3000R (S5191) motherboard if cpufreq module is loaded. 7.0-RELEASE (AMD64) didn't have this problem. Are you absolutely positive about this (re: amd64 not having the problem)? I can reproduce the issue documented in my Wiki page on i386 or amd64. The piece that seems to cause it, at least in the case of the PDSMI+, is EIST being enabled in the BIOS. For what it's worth, I've got five Supermicro PDSMI+ and one PDSMA+ in production, all running amd64, and starting from when I moved from 6.2-STABLE to 7.0-BETA, and continuing through last week's 7.0-STABLE, I started seeing calcru: runtime went backwards... messages for about 2-3 minutes after a reboot, then they'd go away on their own. Disabling EIST in the BIOS two days ago made the problem go away on all six systems. The systems are using the ACPI-fast timecounter (the default) except the PDSMA+ uses TSC because it's faster for MySQL... switching between the two didn't make any difference. I figured the reason the errors went away 3 minutes after boot was due to ntpd beating the clock into behaving. I also don't have the cpufreq module loaded. In my case the error messages seemed pretty harmless and the systems have been running great for a long time... both before and after toggling EIST... I only mention it because in my case, it was a slightly different message (always runtime went backwards not negative runtime), and it did affect 7.0-RELEASE/amd64 for me, and maybe that'll help someone narrow it down... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dreadful gmirror performance, though each half works fine
On Thu, Apr 17, 2008 at 4:01 PM, Pete French [EMAIL PROTECTED] wrote: In the end we found that ggate was crashy after a week or two of heavy use, too... dispite it's performance problems (which can be somewhat fixed by telling gmirror to only read from the local disk) That last part interests me - how did you manage to make it do that ? I read the man page, and the 'prefer' balancing algorithm should let you tell it which disc to read from - but there is no mway to change the priority on a disc in amirror that I can see. It can only be set when inserting new drives. The ddefault is '0' and hence it's nbot possible to attach a new drive with a priority below that of the existing local drive. I tried using '-1' as a priority to fix this, but it came up as 255. I would suppose you might have to sync the mirror and then break off and forget the local copy and then sync again. In our case, I'm not sure --- it was awhile ago, but a number of them are also in the 'load' state --- as the higher latency network drives would normally show a higher load. Certainly ZFS needs lots of memory --- most of my systems running ZFS have 4G of RAM and are running in 64 bit mode. With the wiki's recomendation of a large number of kernel pages, I havn't had a problem with crashing. I am using ZFS RAIDZ as a large data store and ZFS mirroring (separately) on my workstation as /usr, /var, and home directories. All out machine ateb64 bit with between 4 and 16 gig of RAm too, so I could try that. So you trust it then ? I;d be interested to know exactly which options from the wiki page you ended up using for both kernel pages and ZFS itself. That would be my ideal solution if it is stable enough. Hmm. Trust is a funny thing. First the options. On my notebook: vm.kmem_size_max=1073741824 vm.kmem_size=1073741824 On the 32 bit version, I have options KVA_PAGES=512, but the same loader.conf settings above. My large fileserver is used as SMB and NFS filestore for large datasets generally ending in .avi or .iso. Not terribly stressed, I don't think. My laptop is used as a workstation. I don't think I'd run mysql or postgresql on zfs yet --- or if I did, I might run solaris. It's newer there. It would make me nervous at any rate. My laptop is a core-2-duo Extreme 7900 with 4 gig of ram. It will run make -j8 world quite quickly on zfs --- and even quicker the 2nd time. I've been running /usr, /var and home directories on zfs for several months now and I havn't had any problems. That said, I take regular (daily) snapshots and I zfs send the snapshots to the other zfs array for backup. This is a big advantage to zfs --- snapshots and snapshot backups are fast (and still checksum protected). Now as to trust: ZFS is copy-on-write. From my reading of problems people have, it seems that new data might be corrupted in some manner (there are posts even today about zfs and bittorrent) but the snapshots should not be affected. I hedge my bets further by keeping backups. efficient. Removing the read load from the ggated drive seems to help quite a bit in overall performance. But even with this change, I still found that ggate would crash after several days to a week of heavy use. Well, I upped the networking buffers and queue sizes to what I woulkd normally consider 'stupid' values, and now it seems to have settled down and is performing well (am using then 'load' balancing algorithm). Shall see if it stays that way for the next few weeks given what you have just said. I should probably try ZFS on it too, just for my own curiosity. 'load' should almost always prefer the local drive. Large buffers are required to compensate for network latency. Sounds about normal. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ZFS Bittorent - Hang?
OK. I've been able to reproduce the issue. Conditions: - Stock shipped kernel and modules from RELENG 7.0 loader.conf settings: - zfs prefetch enabled - zfs zil disabled - vm.kmem_size_max=1073741824 - vm.kmem_size=1073741824 AMD64 on Core 2 Duo w/ 4 GB RAM raidz across 4 disks, using root on zfs (also experienced this hang with zfs just on /usr) How To Reproduce - install transmission-daemon, run transmission-daemon (it will daemonize, automatically backgrounding) - grab a torrent, such as KNOPPIX (http://torrent.unix-ag.uni-kl.de/) - transmission-remote -a torrentfile (add the torrent) - transmission-remote -s all (start all the torrents) wait hours to a day or so with whatever you want logging things running and active since anything that hits disk after the hang will get hung as well I've just done this twice. It doesn't seem to happen with zil enabled and prefetch off. Expected Behavior No hang. Thank you for spending time on this. I'm getting some jbod-storage in a few weeks and will spend some time using various block-sizes and share partitions across nfs. I'm somewhat confident that zfs on FreeBSD will work fine but Solaris is (of course) also an option. This will be approx. 7 TB to begin with and growing upwards to some two digit TB's. What is the largest storage zfs on FreeBSD has been used on? I tried it for some month on 8 TB. -- regards Claus When lenity and cruelty play for a kingdom, the gentlest gamester is the soonest winner. Shakespeare ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: calcru: time went backwards
Jeremy Chadwick wrote: 7.0-RELEASE (AMD64) didn't have this problem. Are you absolutely positive about this (re: amd64 not having the problem)? I can reproduce the issue documented in my Wiki page on i386 or amd64. The piece that seems to cause it, at least in the case of the PDSMI+, is EIST being enabled in the BIOS. Yes, with 7.0-RELEASE speedstep was working and there was no calcru: runtime went backwards... messages. But i did have cpufreq compiled in kernel.. It seems to be working now when loaded as module from loader.conf. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ZFS Bittorent - Hang?
No problem. I've filed a PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=122888 This doesn't seem to be a volume-of-data thing, not sure if it is related to using raidz or not. I don't have another spare disk in the machine I tested on to pare things down. Otherwise, seems to be pretty stable. I've been knocking on it for some time with no other troubles. Prefetch seems to me to be a little less than ready for prime-time. I seem to recall on a 32-bit machine as well that pkg_delete would run terribly slowly with prefetch on, and things got better when I re-enabled the zil and turned prefetch off. Not sure whether the zil just helped a lot there or if the problem was prefetch. I'm using ZFS on my Mac OS X laptop as well, that's been pretty good too. Latest build (111 on zfs.macosforge.org) has fixed mmap coherency, and a bunch of other things. On Fri, Apr 18, 2008 at 1:03 PM, Claus Guttesen [EMAIL PROTECTED] wrote: OK. I've been able to reproduce the issue. Conditions: - Stock shipped kernel and modules from RELENG 7.0 loader.conf settings: - zfs prefetch enabled - zfs zil disabled - vm.kmem_size_max=1073741824 - vm.kmem_size=1073741824 AMD64 on Core 2 Duo w/ 4 GB RAM raidz across 4 disks, using root on zfs (also experienced this hang with zfs just on /usr) How To Reproduce - install transmission-daemon, run transmission-daemon (it will daemonize, automatically backgrounding) - grab a torrent, such as KNOPPIX (http://torrent.unix-ag.uni-kl.de/) - transmission-remote -a torrentfile (add the torrent) - transmission-remote -s all (start all the torrents) wait hours to a day or so with whatever you want logging things running and active since anything that hits disk after the hang will get hung as well I've just done this twice. It doesn't seem to happen with zil enabled and prefetch off. Expected Behavior No hang. Thank you for spending time on this. I'm getting some jbod-storage in a few weeks and will spend some time using various block-sizes and share partitions across nfs. I'm somewhat confident that zfs on FreeBSD will work fine but Solaris is (of course) also an option. This will be approx. 7 TB to begin with and growing upwards to some two digit TB's. What is the largest storage zfs on FreeBSD has been used on? I tried it for some month on 8 TB. -- regards Claus When lenity and cruelty play for a kingdom, the gentlest gamester is the soonest winner. Shakespeare -- James Snyder Biomedical Engineering Northwestern University [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: LOR sleepq/scrlock
On Thursday 10 April 2008 06:33:40 pm Aristedes Maniatis wrote: http://www.ish.com.au/s/LOR/1.jpg http://www.ish.com.au/s/LOR/2.jpg http://www.ish.com.au/s/LOR/3.jpg (this overlaps with [2]) These are all garbage in kuickshow. :( They work fine for me in Firefox. But don't know what sort of jpegs the Sony camera saves. Anyhow I've also now resaved them as png (about twice the size). Please let me know if that worked. http://www.ish.com.au/s/LOR/1.png , etc kuickshow had issues still, but FF worked ok. The specific LOR at the end is real, but a minor one. Basically, the console driver locks (e.g. sio, scrlock) are higher in the order than the various thread locks, so any printf while holding a thread lock will trigger a LOR. The real problem at the bottom of the screen though is a real issue. It's a LOR of two different sleepqueue chain locks. The problem is that when setrunnable() encounters a swapped out thread it tries to wakeup proc0, but if proc0 is asleep (which is typical) then its thread lock is a sleep queue chain lock, so waking up a swapped out thread from wakeup() will usually trigger this LOR. I think the best fix is to not have setrunnable() kick proc0 directly. Perhaps setrunnable() should return an int and return true if proc0 needs to be awakened and false otherwise. Then the the sleepq code (b/c only sleeping threads can be swapped out anyway) can return that value from sleepq_resume_thread() and can call kick_proc0() directly once it has dropped all of its own locks. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
ule scheduler
I see this is the standard recommendation for those of us using SMP. I am wondering how far away we are from that becoming standard, since on even amd64, I see the older scheduler is still in place? Brian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_7 tinderbox] failure on ia64/ia64
TB --- 2008-04-18 21:32:21 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-04-18 21:32:21 - starting RELENG_7 tinderbox run for ia64/ia64 TB --- 2008-04-18 21:32:21 - cleaning the object tree TB --- 2008-04-18 21:32:33 - cvsupping the source tree TB --- 2008-04-18 21:32:33 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/ia64/ia64/supfile TB --- 2008-04-18 21:32:39 - building world (CFLAGS=-O2 -pipe) TB --- 2008-04-18 21:32:39 - cd /src TB --- 2008-04-18 21:32:39 - /usr/bin/make -B buildworld World build started on Fri Apr 18 21:32:40 UTC 2008 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 Apr 18 22:58:30 UTC 2008 TB --- 2008-04-18 22:58:30 - generating LINT kernel config TB --- 2008-04-18 22:58:30 - cd /src/sys/ia64/conf TB --- 2008-04-18 22:58:30 - /usr/bin/make -B LINT TB --- 2008-04-18 22:58:30 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2008-04-18 22:58:30 - cd /src TB --- 2008-04-18 22:58:30 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Fri Apr 18 22:58:30 UTC 2008 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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/dev/cmx/cmx_pccard.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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/dev/cnw/if_cnw.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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/dev/cxgb/cxgb_main.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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/dev/cxgb/cxgb_offload.c cc1: warnings being treated as errors /src/sys/dev/cxgb/cxgb_offload.c: In function 'do_bad_cpl': /src/sys/dev/cxgb/cxgb_offload.c:318: warning: implicit declaration of function 'kdb_backtrace' /src/sys/dev/cxgb/cxgb_offload.c:318: warning: nested extern declaration of 'kdb_backtrace' *** Error code 1 Stop in /obj/ia64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-04-18 23:03:45 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-04-18 23:03:45 - ERROR: failed to build lint kernel TB --- 2008-04-18 23:03:45 - tinderbox aborted TB --- 4688.45 user 377.95 system 5484.32 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-ia64-ia64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ule scheduler
On Fri, Apr 18, 2008 at 11:35 PM, Brian [EMAIL PROTECTED] wrote: I see this is the standard recommendation for those of us using SMP. I am wondering how far away we are from that becoming standard, since on even amd64, I see the older scheduler is still in place? I believe the current plan is to have ULE be the default scheduler in 7.1-RELEASE. I've been using it since 7.0-PRERELEASE and have had no problems with it, though it is slower than 4BSD for some very specific workloads (ffmpeg with multiple threads). Josh ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_7 tinderbox] failure on powerpc/powerpc
TB --- 2008-04-18 22:45:46 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-04-18 22:45:46 - starting RELENG_7 tinderbox run for powerpc/powerpc TB --- 2008-04-18 22:45:46 - cleaning the object tree TB --- 2008-04-18 22:46:00 - cvsupping the source tree TB --- 2008-04-18 22:46:00 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/powerpc/powerpc/supfile TB --- 2008-04-18 22:46:07 - building world (CFLAGS=-O2 -pipe) TB --- 2008-04-18 22:46:07 - cd /src TB --- 2008-04-18 22:46:07 - /usr/bin/make -B buildworld World build started on Fri Apr 18 22:46:08 UTC 2008 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 Apr 18 23:51:46 UTC 2008 TB --- 2008-04-18 23:51:46 - generating LINT kernel config TB --- 2008-04-18 23:51:46 - cd /src/sys/powerpc/conf TB --- 2008-04-18 23:51:46 - /usr/bin/make -B LINT TB --- 2008-04-18 23:51:46 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2008-04-18 23:51:46 - cd /src TB --- 2008-04-18 23:51:46 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Fri Apr 18 23:51:46 UTC 2008 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 -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 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -Werror /src/sys/dev/cmx/cmx_pccard.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 -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 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -Werror /src/sys/dev/cnw/if_cnw.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 -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 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -Werror /src/sys/dev/cxgb/cxgb_main.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 -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 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -Werror /src/sys/dev/cxgb/cxgb_offload.c cc1: warnings being treated as errors /src/sys/dev/cxgb/cxgb_offload.c: In function 'do_bad_cpl': /src/sys/dev/cxgb/cxgb_offload.c:318: warning: implicit declaration of function 'kdb_backtrace' /src/sys/dev/cxgb/cxgb_offload.c:318: warning: nested extern declaration of 'kdb_backtrace' *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-04-18 23:55:17 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-04-18 23:55:17 - ERROR: failed to build lint kernel TB --- 2008-04-18 23:55:17 - tinderbox aborted TB --- 3484.13 user 351.03 system 4171.06 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-powerpc-powerpc.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_7 tinderbox] failure on sparc64/sparc64
TB --- 2008-04-18 23:03:46 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-04-18 23:03:46 - starting RELENG_7 tinderbox run for sparc64/sparc64 TB --- 2008-04-18 23:03:46 - cleaning the object tree TB --- 2008-04-18 23:03:55 - cvsupping the source tree TB --- 2008-04-18 23:03:55 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/sparc64/sparc64/supfile TB --- 2008-04-18 23:04:00 - building world (CFLAGS=-O2 -pipe) TB --- 2008-04-18 23:04:00 - cd /src TB --- 2008-04-18 23:04:00 - /usr/bin/make -B buildworld World build started on Fri Apr 18 23:04:01 UTC 2008 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 Apr 19 00:05:06 UTC 2008 TB --- 2008-04-19 00:05:06 - generating LINT kernel config TB --- 2008-04-19 00:05:06 - cd /src/sys/sparc64/conf TB --- 2008-04-19 00:05:06 - /usr/bin/make -B LINT TB --- 2008-04-19 00:05:06 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2008-04-19 00:05:06 - cd /src TB --- 2008-04-19 00:05:06 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Sat Apr 19 00:05:06 UTC 2008 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 -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 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror /src/sys/dev/cmx/cmx_pccard.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 -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 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror /src/sys/dev/cnw/if_cnw.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 -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 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror /src/sys/dev/cxgb/cxgb_main.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 -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 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror /src/sys/dev/cxgb/cxgb_offload.c cc1: warnings being treated as errors /src/sys/dev/cxgb/cxgb_offload.c: In function 'do_bad_cpl': /src/sys/dev/cxgb/cxgb_offload.c:318: warning: implicit declaration of function 'kdb_backtrace' /src/sys/dev/cxgb/cxgb_offload.c:318: warning: nested extern declaration of 'kdb_backtrace' *** Error code 1 Stop in /obj/sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-04-19 00:08:35 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-04-19 00:08:35 - ERROR: failed to build lint kernel TB --- 2008-04-19 00:08:35 - tinderbox aborted TB --- 3264.81 user 344.53 system 3889.59 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-sparc64-sparc64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ule scheduler
Brian wrote: I see this is the standard recommendation for those of us using SMP. I am wondering how far away we are from that becoming standard, since on even amd64, I see the older scheduler is still in place? It *is* the default scheduler for RELENG_7 and -HEAD for most architectures. Cheers, -- Xin LI [EMAIL PROTECTED]http://www.delphij.net/ FreeBSD - The Power to Serve! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: umass causes panic on 7 amd64
On Thu, Apr 17, 2008 at 07:13:17PM -0400, Garrett Wollman wrote: In my experience, umass over EHCI has never worked on any machine ever, going back to 5.x and over multiple kinds of umass devices. (I never saw panics, only triple-fault CPU resets.) OTOH, I've had mixed results, though I haven't seen panics caused by EHCI. umass has a tendency to panic when it trips over an interface bug between bus_dmamem_alloc(9) and contigmalloc(9) which has been present since at least 4.x, though the work-arounds have improved and this is less of a problem than it was 3 years ago. On my laptop (HP nx6125, ATI SB400 chipset), I haven't had any problems with EHCI in 6.x or 7.0 (both amd64 - I can't recall if I've tried ECHI whilst running i386). My son's laptop (HP V6107au, nVIDIA MCP51 chipset, 6.x/amd64) gives varying results (sometimes it works, sometimes it doesn't) and he's found that plugging flashdisks into the USB hub on his keyboard gives better results than plugging them into the system (which doesn't make sense to me - they still show a attached to EHCI). My work desktop (Dell OptiPlex GX620, Intel ICH7 chipset 7.0/amd64) refuses to acknowledge EHCI devices - it just reports timeouts and disables that USB port. [See my recent posting to -amd64]. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. pgpwvI0ALZw9N.pgp Description: PGP signature
Re: Open-vm-tools port available for testing
Uwe Laverenz wrote: I just installed your port on 6.3-p1/amd64 on ESX 3.5 (WITHOUT_X11, just guestd and vmmemctl) to see if VMotion works, and it installed and worked perfectly. :-) I'll do some more tests with X11 and RELENG_7 as soon as I find the time for it. Thank you very much for your work! cu, Uwe I am an not great with BSD, how can I install this port without X? Sorry if this is easy but I don't really understand what I am seeing in the Makefile. I have tried various commands referencing --without-x etc. but none of them have worked. Thanks for any help, and thanks for a much needed port!! -Lantard -- View this message in context: http://www.nabble.com/Open-vm-tools-port-available-for-testing-tp16341202p16770848.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
