Re: IPMI and Dell ERA/O
I have a 1950-III 1U on the floor here that I'm loading. After configuring IPMI in the BIOS, I can: [2:6:[EMAIL PROTECTED]:~ ipmitool -I lanplus -U root -H 192.168.221.160 shell Password: ipmitool power on Chassis Power Control: Up/On Now. strike is not the 1U in question... and does not, in fact, have IPMI of it's own, but it can talk to the 1950-III, but... [1:1:[EMAIL PROTECTED]:~ dmesg | grep ipmi ipmi0: KCS mode found at io 0xca8 on acpi ipmi0: KCS error: ff ipmi1: IPMI System Interface on isa0 device_attach: ipmi1 attach returned 16 ipmi0: IPMI device rev. 0, firmware rev. 2.2, version 2.0 ipmi0: Number of channels 4 ipmi0: Attached watchdog ... and it will respond to local use of the ipmi tool. Serial console works --- although it seems like it has a finite buffer and too much output overflows the buffer (flow control doesn't seem to fix this). You also have to custom compile the kernel and boot blocks to use COM2 (sio1) as the console. The BIOS seems to have settings to make the external serial port COM2 and use COM1 for IPMI, but the settings don't work. You need to use COM2. While you're at it, the default speed is 57600 (might as well compile in that default, too). The R200's that I have also seem to work fine. I haven't tested serial consoles with them --- but it's on the list. Curiously, IPMI shares the ethernet ports with the onboard ethernet controllers without FreeBSD's knowledge. It does use a different MAC address. It is also apparently capable of using vlans (haven't tested this yet). I'm most nervous about how this might behave if the port was being nailed with traffic --- but I can't easily test this to my satisfaction. What controls the contention for the port between whatever IPMI magic is going on and the OS use of the port? Anyways... the really cool thing about IPMI is that it's cheap enough to be included. The original poster spoke of a PCI card (likely one of the management cards) --- these are expensive options --- especially if you don't need graphics or remote media. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Possible ZFS patch, please test!
John Baldwin wrote: This patch merges a few changes from HEAD back to 7.x. I think the endian changes specifically might solve the issue people saw with zpools created with non-dtrace kernels not being readable by dtrace kernels and vice versa. http://www.FreeBSD.org/~jhb/patches/zfs_7.patch It works for me with the root on zfs Thanks Henri ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPMI and Dell ERA/O
On Fri, Aug 29, 2008 at 02:17:17AM -0400, Zaphod Beeblebrox wrote: Curiously, IPMI shares the ethernet ports with the onboard ethernet controllers without FreeBSD's knowledge. It does use a different MAC address. It is also apparently capable of using vlans (haven't tested this yet). I'm most nervous about how this might behave if the port was being nailed with traffic --- but I can't easily test this to my satisfaction. What controls the contention for the port between whatever IPMI magic is going on and the OS use of the port? My general opinion is to avoid IPMI at all costs. The concept itself is great, and the design idea is okay, but the implementation is an atrocity. If you *must* use IPMI, get an implementation that uses its own, dedicated NIC. That said, the feature you're referring to (IPMI piggybacking on top of an existing NIC on the mainboard) is called ASF from a NIC driver perspective. The NIC driver for the OS *must* have full awareness of said piggybacking, and if it doesn't, a couple different things can happen: a) NIC simply does not work b) NIC works, but behaves oddly -- usually this is tracked down to the local network seeing the MAC address continually change for the IP address associated with the machine c) NIC works, but IPMI and other features do not work There are a couple different drivers for FreeBSD which have ASF knowledge; bge(4) does, and I believe em(4) does (I could be wrong here). bge(4) has a loader.conf tunable that tells the driver to understand ASF or not. In general, it's horrible, and I feel sorry for driver authors having to deal with it. -- | 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: Possible ZFS patch, please test!
Henri Hennebert wrote: John Baldwin wrote: This patch merges a few changes from HEAD back to 7.x. I think the endian changes specifically might solve the issue people saw with zpools created with non-dtrace kernels not being readable by dtrace kernels and vice versa. http://www.FreeBSD.org/~jhb/patches/zfs_7.patch It works for me with the root on zfs While rebuilding the ports index with `portsdb -Uu` the system become really sluggish with cpu running more than 60% in system... Something really strange here. Henri Thanks Henri ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ 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 amd64/amd64
TB --- 2008-08-29 06:42:04 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-08-29 06:42:04 - starting RELENG_7 tinderbox run for amd64/amd64 TB --- 2008-08-29 06:42:04 - cleaning the object tree TB --- 2008-08-29 06:42:20 - cvsupping the source tree TB --- 2008-08-29 06:42:20 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/amd64/amd64/supfile TB --- 2008-08-29 06:42:27 - building world (CFLAGS=-O2 -pipe) TB --- 2008-08-29 06:42:27 - cd /src TB --- 2008-08-29 06:42:27 - /usr/bin/make -B buildworld World build started on Fri Aug 29 06:42:29 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 stage 5.1: building 32 bit shim libraries World build completed on Fri Aug 29 08:16:44 UTC 2008 TB --- 2008-08-29 08:16:44 - generating LINT kernel config TB --- 2008-08-29 08:16:44 - cd /src/sys/amd64/conf TB --- 2008-08-29 08:16:44 - /usr/bin/make -B LINT TB --- 2008-08-29 08:16:44 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2008-08-29 08:16:44 - cd /src TB --- 2008-08-29 08:16:44 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Fri Aug 29 08:16:44 UTC 2008 stage 1: configuring the kernel [...] WARNING: kernel contains GPL contaminated emu10k1 headers WARNING: kernel contains GPL contaminated emu10kx headers WARNING: kernel contains GPL contaminated emu10kx headers WARNING: kernel contains GPL contaminated emu10kx headers WARNING: kernel contains GPL contaminated maestro3 headers WARNING: kernel contains GPL contaminated ext2fs filesystem WARNING: kernel contains GPL contaminated ReiserFS filesystem WARNING: kernel contains GPL contaminated xfs filesystem *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-08-29 08:16:44 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-08-29 08:16:44 - ERROR: failed to build lint kernel TB --- 2008-08-29 08:16:44 - tinderbox aborted TB --- 4593.07 user 508.20 system 5680.52 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-amd64-amd64.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 i386/i386
TB --- 2008-08-29 07:36:05 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-08-29 07:36:05 - starting RELENG_7 tinderbox run for i386/i386 TB --- 2008-08-29 07:36:05 - cleaning the object tree TB --- 2008-08-29 07:36:19 - cvsupping the source tree TB --- 2008-08-29 07:36:19 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/i386/i386/supfile TB --- 2008-08-29 07:36:26 - building world (CFLAGS=-O2 -pipe) TB --- 2008-08-29 07:36:26 - cd /src TB --- 2008-08-29 07:36:26 - /usr/bin/make -B buildworld World build started on Fri Aug 29 07:36:27 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 Aug 29 08:40:50 UTC 2008 TB --- 2008-08-29 08:40:50 - generating LINT kernel config TB --- 2008-08-29 08:40:50 - cd /src/sys/i386/conf TB --- 2008-08-29 08:40:50 - /usr/bin/make -B LINT TB --- 2008-08-29 08:40:50 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2008-08-29 08:40:50 - cd /src TB --- 2008-08-29 08:40:50 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Fri Aug 29 08:40:50 UTC 2008 stage 1: configuring the kernel [...] WARNING: kernel contains GPL contaminated emu10kx headers WARNING: kernel contains GPL contaminated emu10kx headers WARNING: kernel contains GPL contaminated emu10kx headers WARNING: kernel contains GPL contaminated maestro3 headers WARNING: kernel contains GPL contaminated ext2fs filesystem WARNING: kernel contains GPL contaminated ReiserFS filesystem WARNING: kernel contains GPL contaminated xfs filesystem WARNING: COMPAT_SVR4 is broken and should be avoided *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-08-29 08:40:50 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-08-29 08:40:50 - ERROR: failed to build lint kernel TB --- 2008-08-29 08:40:50 - tinderbox aborted TB --- 3301.27 user 334.54 system 3885.04 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-i386-i386.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPMI and Dell ERA/O
Hi, On 29 Aug 2008, at 08:44, Jeremy Chadwick wrote: [...]That said, the feature you're referring to (IPMI piggybacking on top of an existing NIC on the mainboard) is called ASF from a NIC driver perspective. In implementations I've looked at, the interfaces really are distinct hardware but they use a common phy. It's just about transparent to software. The NIC driver for the OS *must* have full awareness of said piggybacking, and if it doesn't, a couple different things can happen: a) NIC simply does not work b) NIC works, but behaves oddly -- usually this is tracked down to the local network seeing the MAC address continually change for the IP address associated with the machine That might just be be misconfiguration: the IPMI interface should have an IP address distinct from (any address of) the 'proper' interface. c) NIC works, but IPMI and other features do not work There are a couple different drivers for FreeBSD which have ASF knowledge; bge(4) does, and I believe em(4) does (I could be wrong here). em(4) does indeed work, we are using it on a couple of dozen boxes. bge(4) has a loader.conf tunable that tells the driver to understand ASF or not. In general, it's horrible, and I feel sorry for driver authors having to deal with it. The only problem I have seen on em is that by default the driver resets the phy during boot which confuses IPMI; if a SOL console session is active, the driver is signalled not to do the reset. -- | 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] -- Bob Bishop [EMAIL PROTECTED] ___ 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 i386/pc98
TB --- 2008-08-29 08:16:45 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-08-29 08:16:45 - starting RELENG_7 tinderbox run for i386/pc98 TB --- 2008-08-29 08:16:45 - cleaning the object tree TB --- 2008-08-29 08:16:56 - cvsupping the source tree TB --- 2008-08-29 08:16:56 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/i386/pc98/supfile TB --- 2008-08-29 08:17:04 - building world (CFLAGS=-O2 -pipe) TB --- 2008-08-29 08:17:04 - cd /src TB --- 2008-08-29 08:17:04 - /usr/bin/make -B buildworld World build started on Fri Aug 29 08:17:05 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 Aug 29 09:21:10 UTC 2008 TB --- 2008-08-29 09:21:10 - generating LINT kernel config TB --- 2008-08-29 09:21:10 - cd /src/sys/pc98/conf TB --- 2008-08-29 09:21:10 - /usr/bin/make -B LINT TB --- 2008-08-29 09:21:10 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2008-08-29 09:21:10 - cd /src TB --- 2008-08-29 09:21:10 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Fri Aug 29 09:21:10 UTC 2008 stage 1: configuring the kernel [...] WARNING: kernel contains GPL contaminated emu10kx headers WARNING: kernel contains GPL contaminated emu10kx headers WARNING: kernel contains GPL contaminated emu10kx headers WARNING: kernel contains GPL contaminated maestro3 headers WARNING: kernel contains GPL contaminated ext2fs filesystem WARNING: kernel contains GPL contaminated ReiserFS filesystem WARNING: kernel contains GPL contaminated xfs filesystem WARNING: COMPAT_SVR4 is broken and should be avoided *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-08-29 09:21:11 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-08-29 09:21:11 - ERROR: failed to build lint kernel TB --- 2008-08-29 09:21:11 - tinderbox aborted TB --- 3266.72 user 343.78 system 3865.77 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-i386-pc98.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 ia64/ia64
TB --- 2008-08-29 08:40:50 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-08-29 08:40:50 - starting RELENG_7 tinderbox run for ia64/ia64 TB --- 2008-08-29 08:40:50 - cleaning the object tree TB --- 2008-08-29 08:41:03 - cvsupping the source tree TB --- 2008-08-29 08:41:03 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/ia64/ia64/supfile TB --- 2008-08-29 08:41:09 - building world (CFLAGS=-O2 -pipe) TB --- 2008-08-29 08:41:09 - cd /src TB --- 2008-08-29 08:41:09 - /usr/bin/make -B buildworld World build started on Fri Aug 29 08:41:10 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 Aug 29 10:07:05 UTC 2008 TB --- 2008-08-29 10:07:05 - generating LINT kernel config TB --- 2008-08-29 10:07:05 - cd /src/sys/ia64/conf TB --- 2008-08-29 10:07:05 - /usr/bin/make -B LINT TB --- 2008-08-29 10:07:05 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2008-08-29 10:07:05 - cd /src TB --- 2008-08-29 10:07:05 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Fri Aug 29 10:07:05 UTC 2008 stage 1: configuring the kernel [...] WARNING: kernel contains GPL contaminated emu10k1 headers WARNING: kernel contains GPL contaminated emu10kx headers WARNING: kernel contains GPL contaminated emu10kx headers WARNING: kernel contains GPL contaminated emu10kx headers WARNING: kernel contains GPL contaminated maestro3 headers WARNING: kernel contains GPL contaminated ext2fs filesystem WARNING: kernel contains GPL contaminated ReiserFS filesystem WARNING: kernel contains GPL contaminated xfs filesystem *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-08-29 10:07:05 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-08-29 10:07:05 - ERROR: failed to build lint kernel TB --- 2008-08-29 10:07:05 - tinderbox aborted TB --- 4537.60 user 349.38 system 5174.98 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: Recent breakage due to the DTrace merge
John Birrell wrote: I know that there are issues with upgrading from 6.X (where .X isn't the most recent on RELENG6). I'll need help from someone with an old 6.2 box (say) to test out the builds. I have no hardware to run an old version of 6 on. I've got a 6.2 box that needs upgrading anyway, so I'll bite. The install was from an ISO image and has never been upgraded, so I know it's not most recent. Do you simply want an upgrade to RELENG_7 and then a report of any breakage? Steve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPMI and Dell ERA/O
On Fri, Aug 29, 2008 at 4:48 AM, Bob Bishop [EMAIL PROTECTED] wrote: The only problem I have seen on em is that by default the driver resets the phy during boot which confuses IPMI; if a SOL console session is active, the driver is signalled not to do the reset. Same here. The 1950-III that I have has bce cards (2) on the motherboard. When the kernel probes them, the IPMI interface dissapears for a second or so. The IPMI documentation seems to imply that either port will talk IPMI --- but I havn't tested this. I havn't noticed any problems with the port otherwise. I'm even bridging the two motherboard ports right now. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recent breakage due to the DTrace merge
On Thursday 28 August 2008 06:36:30 pm John Birrell wrote: It goes without saying that this didn't go anywhere near as smoothly as I hoped it would. My attention to detail was less than perfect. Sorry for the pain I've caused. A big thanks to those who've put work into fixing the mistakes, particularly jhb, kib and csjp. What I'd like right now is for anybody with unresolved problems to write a summry and email it to me so I can see what needs to be addressed. I know that there are issues with upgrading from 6.X (where .X isn't the most recent on RELENG6). I'll need help from someone with an old 6.2 box (say) to test out the builds. I have no hardware to run an old version of 6 on. The issue with upgrades is that the dtrace_tools can't be built on 6.x systems during the bootstrap stage because 6.x doesn't have libelf. It may be that you need to bootstrap libelf differently than you are currently doing now. I can reproduce this easily on 6.3-RELEASE box. I would ask ru@ how best to handle this case. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPMI and Dell ERA/O
On Friday 29 August 2008 01:33:36 am Jonathan Bond-Caron wrote: Hi Everyone, I have a dell 1750 server with ERA/O card running on FreeBSD 7.0-STABLE According to Dell, the ERA card supports ipmi 1.0: http://linux.dell.com/ipmi.shtml But so far no luck with freebsd :/ If your BIOS doesn't tell us about the IPMI BMC via ACPI or SMBIOS, you can try using hints (I've seen machines thave a BMC, but the BIOS doesn't bother to tell you about it). Dell boxes I've seen have KCS at the default address, so you can just do: hint.ipmi.0.at=isa0 hint.ipmi.0.mode=KCS Either add that to /boot/device.hints or for a test just explicitly set those variables at the loader prompt before booting. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
WARNING: 7-STABLE BROKEN -- please wait to upgrade / Should be OK now
Well I got bit by this and am dead in the water. Nothing builds. I tried the DEBUG_FLAGS=-g trick but to no avail. I get this: cc: Internal error: segmentation fault: 11 (program ld) I do not have a backup ld. (My bad.) Where can I get a good one? I cannot find any servers with built individual tools. Thanks, Dan Allen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: WARNING: 7-STABLE BROKEN -- please wait to upgrade / Should be OK now
On Fri, 29 Aug 2008, Dan Allen wrote: Well I got bit by this and am dead in the water. Nothing builds. I tried the DEBUG_FLAGS=-g trick but to no avail. I get this: cc: Internal error: segmentation fault: 11 (program ld) I do not have a backup ld. (My bad.) Where can I get a good one? I cannot find any servers with built individual tools. Judging from others regarding this problem, you may need a few utilities. Can you download a 7.0-RELEASE live CD image, burn it, then use the utilities from that? -- DE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: WARNING: 7-STABLE BROKEN -- please wait to upgrade / Should be OK now
Dan Allen wrote: Well I got bit by this and am dead in the water. Nothing builds. I tried the DEBUG_FLAGS=-g trick but to no avail. My 7.0 box upgraded fine this morning: FreeBSD ids.eagle.ca 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Fri Aug 29 11:38:12 EDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386 The dmesg if it is relevant: http://ww3.ibctech.ca/ids.dmesg Steve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recent breakage due to the DTrace merge
John Birrell wrote: I know that there are issues with upgrading from 6.X (where .X isn't the most recent on RELENG6). I'll need help from someone with an old 6.2 box (say) to test out the builds. I have no hardware to run an old version of 6 on. This is most likely not exactly what you are after, but: Earlier in the week I put a message to -stable asking how to upgrade a minimal install of a system that runs entirely from USB key. This key was running 6.2. Using a host build machine running 7.0, setting DESTDIR accordingly, and configuring numerous NO_* in /etc/make.conf, I was not only able to achieve my minimal install using buildworld etc process, I was able to upgrade it to stable sources from this morning successfully. I'm now off to upgrade a box that is actually _running_ 6.2, and I'll report back with any details. Steve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: WARNING: 7-STABLE BROKEN -- please wait to upgrade / Should be OK now
On Fri, Aug 29, 2008 at 10:43:39AM -0600, Dan Allen wrote: Well I got bit by this and am dead in the water. Nothing builds. I tried the DEBUG_FLAGS=-g trick but to no avail. I get this: cc: Internal error: segmentation fault: 11 (program ld) I do not have a backup ld. (My bad.) Where can I get a good one? I cannot find any servers with built individual tools. The breakage from the WITH_CTF build is indicated by Abort from the image activator. Signal 11, AKA segmentation fault, is not likely to be caused by the dtrace MFC problems. Just in case, if you have buildworld result intact, you should enter /usr/src/gnu/usr.bin/binutils/ld and do make install DEBUG_FLAGS=-g But I think your problem is not related. pgpRrM7DTniLr.pgp Description: PGP signature
Detangling the ppbus/ppc interrupt stuff..
So I have a patch to try and straighten out the ppbus/ppc interrupt stuff a bit. Rather than passing IRQ numbers around as ivars, etc., ppc is smart enough to let child devices ask for SYS_RES_IRQ rid 0 and let them use its assigned IRQ resource. It then uses an interrupt event to mange the list of child interrupt handlers which it invokes from its own interrupt handler. I don't currently have any boxes running HEAD that have anything hooked up to their ppc0 port, so I'd appreciate folks testing this if possible. http://www.FreeBSD.org/~jhb/patches/ppc_intr.patch -- John Baldwin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [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: Possible ZFS patch, please test!
On Friday 29 August 2008 03:57:46 am Henri Hennebert wrote: Henri Hennebert wrote: John Baldwin wrote: This patch merges a few changes from HEAD back to 7.x. I think the endian changes specifically might solve the issue people saw with zpools created with non-dtrace kernels not being readable by dtrace kernels and vice versa. http://www.FreeBSD.org/~jhb/patches/zfs_7.patch It works for me with the root on zfs While rebuilding the ports index with `portsdb -Uu` the system become really sluggish with cpu running more than 60% in system... Something really strange here. Can you try removing the 'KDTRACE_*' options from your kernel config file? It appears that they haven't been enabled in 8.x by default yet. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: WARNING: 7-STABLE BROKEN -- please wait to upgrade / Should be OK now
On Fri, 29 Aug 2008 10:43:39 -0600 Dan Allen wrote: Well I got bit by this and am dead in the water. Nothing builds. I tried the DEBUG_FLAGS=-g trick but to no avail. I get this: cc: Internal error: segmentation fault: 11 (program ld) Yep, you need some tools installed with debug flag. I didn't try to verify them, I just did a full installworld with that flag: - # cd /usr/src # make installworld DEBUG_FLAGS=-g - Then reboot, csup and rebuild and reinstall the system once more. All is well now. I do not have a backup ld. (My bad.) Where can I get a good one? I cannot find any servers with built individual tools. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD committer, http://www.FreeBSD.org 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: WARNING: 7-STABLE BROKEN -- please wait to upgrade / Should be OK now
The breakage from the WITH_CTF build is indicated by Abort from the image activator. Signal 11, AKA segmentation fault, is not likely to be caused by the dtrace MFC problems. Just in case, if you have buildworld result intact, you should enter /usr/src/gnu/usr.bin/binutils/ld and do make install DEBUG_FLAGS=-g But I think your problem is not related. I cvsuped and built 7-STABLE just a couple of hours ago. No problems at all. So I agree that this may be a different problem. Steinar Haug, Nethelp consulting, [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: WARNING: 7-STABLE BROKEN -- please wait to upgrade / Should be OK now
On Fri, 29 Aug 2008 22:08:47 +0300 Kostik Belousov wrote: On Fri, Aug 29, 2008 at 10:43:39AM -0600, Dan Allen wrote: Well I got bit by this and am dead in the water. Nothing builds. I tried the DEBUG_FLAGS=-g trick but to no avail. I get this: cc: Internal error: segmentation fault: 11 (program ld) I do not have a backup ld. (My bad.) Where can I get a good one? I cannot find any servers with built individual tools. The breakage from the WITH_CTF build is indicated by Abort from the image activator. Signal 11, AKA segmentation fault, is not likely to be caused by the dtrace MFC problems. I've also got Signal 11 breaks for this problem. Just in case, if you have buildworld result intact, you should enter /usr/src/gnu/usr.bin/binutils/ld and do make install DEBUG_FLAGS=-g My problem was with gcc, then cc... I stopped here and installed the whole world with the debug flag. When I've read an all clean message source update and world rebuild/reinstall helped. I don't have any zfs filesystems here though. But I think your problem is not related. Related for sure. ;-) WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD committer, http://www.FreeBSD.org 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: WARNING: 7-STABLE BROKEN -- please wait to upgrade / Should be OK now
Steve Bertrand wrote: Dan Allen wrote: Well I got bit by this and am dead in the water. Nothing builds. I tried the DEBUG_FLAGS=-g trick but to no avail. My 7.0 box upgraded fine this morning: FreeBSD ids.eagle.ca 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Fri Aug 29 11:38:12 EDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386 The dmesg if it is relevant: http://ww3.ibctech.ca/ids.dmesg Steve Well, mine did not. I was capable of compiling world and kernel and also capable of installing all things like I did in the past, but ZFS seems still broken - the module does not load automatically at initialization time nor is it loadable via kldload (there is an error about missing opensolaris module but I can't find anything about this module ...). oliver ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
stable/6 make and build errors
I've run into a variance in behavior between my SVN updated tree and my CVSUP'd tree that is befuddling me. Running a make depend on two freshly updated trees seems to generate errors with my SVN tree but not my CVSUP tree. Here is the output of the SVN tree. This is freshly checked out from stable/6 not updated. SVN: === share/info (depend) === include (depend) === include/arpa (depend) === include/protocols (depend) === include/rpcsvc (depend) === include/rpc (depend) === lib (depend) === lib/csu/i386-elf (depend) rm -f .depend mkdep -f .depend -a-I/home/sbruno/bsd/6/lib/csu/i386-elf/../common -I/home/sbruno/bsd/6/lib/csu/i386-elf/../../libc/include /home/sbruno/bsd/6/lib/csu/i386-elf/crt1.c /home/sbruno/bsd/6/lib/csu/i386-elf/crti.S /home/sbruno/bsd/6/lib/csu/i386-elf/crtn.S /usr/bin/mkdep: cannot create _mkdep18423: Permission denied /usr/bin/mkdep: cannot create _mkdep18423: Permission denied mkdep: compile failed *** Error code 1 Stop in /home/sbruno/bsd/6/lib/csu/i386-elf. *** Error code 1 Stop in /home/sbruno/bsd/6/lib. *** Error code 1 Stop in /home/sbruno/bsd/6. *** Error code 1 -- Sean Bruno MiraLink Corporation 6015 NE 80th Ave, Ste 100 Portland, OR 97218 Phone 503-621-5143 Fax 503-621-5199 MSN: [EMAIL PROTECTED] Google: [EMAIL PROTECTED] Yahoo: [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: WARNING: 7-STABLE BROKEN -- please wait to upgrade / Should be OK now
O. Hartmann wrote: Steve Bertrand wrote: Dan Allen wrote: Well I got bit by this and am dead in the water. Nothing builds. I tried the DEBUG_FLAGS=-g trick but to no avail. My 7.0 box upgraded fine this morning: FreeBSD ids.eagle.ca 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Fri Aug 29 11:38:12 EDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386 The dmesg if it is relevant: http://ww3.ibctech.ca/ids.dmesg Steve Well, mine did not. I was capable of compiling world and kernel and also capable of installing all things like I did in the past, but ZFS seems still broken - the module does not load automatically at initialization time nor is it loadable via kldload (there is an error about missing opensolaris module but I can't find anything about this module ...). It's new, you need to build it. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: stable/6 make and build errors
Sean Bruno wrote: mkdep -f .depend -a-I/home/sbruno/bsd/6/lib/csu/i386-elf/../common -I/home/sbruno/bsd/6/lib/csu/i386-elf/../../libc/include /home/sbruno/bsd/6/lib/csu/i386-elf/crt1.c /home/sbruno/bsd/6/lib/csu/i386-elf/crti.S /home/sbruno/bsd/6/lib/csu/i386-elf/crtn.S /usr/bin/mkdep: cannot create _mkdep18423: Permission denied /usr/bin/mkdep: cannot create _mkdep18423: Permission denied mkdep: compile failed *** Error code 1 Stop in /home/sbruno/bsd/6/lib/csu/i386-elf. *** Error code 1 Stop in /home/sbruno/bsd/6/lib. *** Error code 1 Stop in /home/sbruno/bsd/6. *** Error code 1 After poking around a bit, I discovered an old build dir in /usr/obj/ that matched the path that my tree was currently a part of. So, a make clean or a make cleanworld doesn't delete /usr/obj/(DIR) for some reason? Bug? -- Sean Bruno MiraLink Corporation 6015 NE 80th Ave, Ste 100 Portland, OR 97218 Phone 503-621-5143 Fax 503-621-5199 MSN: [EMAIL PROTECTED] Google: [EMAIL PROTECTED] Yahoo: [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: WARNING: 7-STABLE BROKEN -- please wait to upgrade / Should be OK now
Dan Allen wrote previously: well I got bit by this and am dead in the water. I got the tools and built everything okay once again. Thanks to everyone for the help! Dan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
HEADSUP: 7-stable considered to be OK again
The feedback I've been getting indicates that it's safe to go back in the water again. -- John Birrell ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: stable/6 make and build errors
On Fri, Aug 29, 2008 at 03:39:30PM -0700, Sean Bruno wrote: Sean Bruno wrote: mkdep -f .depend -a-I/home/sbruno/bsd/6/lib/csu/i386-elf/../common -I/home/sbruno/bsd/6/lib/csu/i386-elf/../../libc/include /home/sbruno/bsd/6/lib/csu/i386-elf/crt1.c /home/sbruno/bsd/6/lib/csu/i386-elf/crti.S /home/sbruno/bsd/6/lib/csu/i386-elf/crtn.S /usr/bin/mkdep: cannot create _mkdep18423: Permission denied /usr/bin/mkdep: cannot create _mkdep18423: Permission denied mkdep: compile failed *** Error code 1 Stop in /home/sbruno/bsd/6/lib/csu/i386-elf. *** Error code 1 Stop in /home/sbruno/bsd/6/lib. *** Error code 1 Stop in /home/sbruno/bsd/6. *** Error code 1 After poking around a bit, I discovered an old build dir in /usr/obj/ that matched the path that my tree was currently a part of. So, a make clean or a make cleanworld doesn't delete /usr/obj/(DIR) for some reason? Bug? It's known that 'make clean' will occasionally not nuke all the necessary objects in /usr/obj/*. rm -fr /usr/obj/* is a better bet. Do not rely on 'make clean'. -- | 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: stable/6 make and build errors
It's known that 'make clean' will occasionally not nuke all the necessary objects in /usr/obj/*. rm -fr /usr/obj/* is a better bet. Do not rely on 'make clean'. Oh? Should I look into why the make system isn't removing /usr/obj/ on a make clean and submit a patch? -- Sean Bruno MiraLink Corporation 6015 NE 80th Ave, Ste 100 Portland, OR 97218 Cell 503-358-6832 Phone 503-621-5143 Fax 503-621-5199 MSN: [EMAIL PROTECTED] Google: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
How reliable is make delete-old and make delete-old-libs on 7.1-PRERELEASE?
How reliable is make delete-old and make delete-old-libs on 7.1-PRERELEASE? I ask because I just upgraded a remote system from 6.3-stable to 7.1-PRERELEASE. All seems well so far. Apps are running fine. I just figure I should do this final bit. FYI, I've written up how I did this migration: http//www.freebsddiary.org/upgrade-6.3-to-7.0.php At the end, I've included the output of make check-old. Does it look good to you? Thanks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
