Re: sun4v arch
In message: [EMAIL PROTECTED] Pietro Cerutti [EMAIL PROTECTED] writes: : -BEGIN PGP SIGNED MESSAGE- : Hash: SHA512 : : Kris Kennaway wrote: : | Just so everyone is on the same page, what is needed to keep sun4v : | viable are people with experience with (or intention to learn about) low : | level architectural and implementation details of the FreeBSD kernel and : | the sun4v hardware platform, who know their way around things like : | pmap.c and other MD places where the kernel interfaces with the bare : | metal, and who are willing to make a long term (multi-year) commitment : | to supporting the platform. : : If we had docs... There's a bunch of sun4v docs available. See http://www.sun.com/processors/documentation.html for example. Warner ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_6 tinderbox] failure on amd64/amd64
TB --- 2008-08-23 09:21:47 - tinderbox 2.3 running on freebsd-legacy.sentex.ca TB --- 2008-08-23 09:21:47 - starting RELENG_6 tinderbox run for amd64/amd64 TB --- 2008-08-23 09:21:47 - cleaning the object tree TB --- 2008-08-23 09:22:16 - cvsupping the source tree TB --- 2008-08-23 09:22:16 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_6/amd64/amd64/supfile TB --- 2008-08-23 09:22:24 - building world (CFLAGS=-O2 -pipe) TB --- 2008-08-23 09:22:24 - cd /src TB --- 2008-08-23 09:22:24 - /usr/bin/make -B buildworld 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 [...] === lib/libpam/modules/pam_rootok (buildincludes) === lib/libpam/modules/pam_securetty (buildincludes) === lib/libpam/modules/pam_self (buildincludes) === lib/libpam/modules/pam_ssh (buildincludes) === lib/libpam/modules/pam_tacplus (buildincludes) === lib/libpam/modules/pam_unix (buildincludes) === lib/libpam/libpam (buildincludes) make: don't know how to make security/openpam_attr.h. Stop *** Error code 2 Stop in /src/lib/libpam. *** Error code 1 Stop in /src/lib. *** Error code 1 Stop in /src/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-08-23 09:29:47 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-08-23 09:29:47 - ERROR: failed to build world TB --- 2008-08-23 09:29:47 - tinderbox aborted TB --- 356.13 user 40.32 system 480.31 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-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_6 tinderbox] failure on i386/i386
TB --- 2008-08-23 09:29:47 - tinderbox 2.3 running on freebsd-legacy.sentex.ca TB --- 2008-08-23 09:29:47 - starting RELENG_6 tinderbox run for i386/i386 TB --- 2008-08-23 09:29:47 - cleaning the object tree TB --- 2008-08-23 09:30:13 - cvsupping the source tree TB --- 2008-08-23 09:30:13 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_6/i386/i386/supfile TB --- 2008-08-23 09:30:21 - building world (CFLAGS=-O2 -pipe) TB --- 2008-08-23 09:30:21 - cd /src TB --- 2008-08-23 09:30:21 - /usr/bin/make -B buildworld 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 [...] === lib/libpam/modules/pam_rootok (buildincludes) === lib/libpam/modules/pam_securetty (buildincludes) === lib/libpam/modules/pam_self (buildincludes) === lib/libpam/modules/pam_ssh (buildincludes) === lib/libpam/modules/pam_tacplus (buildincludes) === lib/libpam/modules/pam_unix (buildincludes) === lib/libpam/libpam (buildincludes) make: don't know how to make security/openpam_attr.h. Stop *** Error code 2 Stop in /src/lib/libpam. *** Error code 1 Stop in /src/lib. *** Error code 1 Stop in /src/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-08-23 09:37:05 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-08-23 09:37:05 - ERROR: failed to build world TB --- 2008-08-23 09:37:05 - tinderbox aborted TB --- 327.26 user 32.47 system 437.70 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-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]
[releng_6 tinderbox] failure on i386/pc98
TB --- 2008-08-23 09:37:05 - tinderbox 2.3 running on freebsd-legacy.sentex.ca TB --- 2008-08-23 09:37:05 - starting RELENG_6 tinderbox run for i386/pc98 TB --- 2008-08-23 09:37:05 - cleaning the object tree TB --- 2008-08-23 09:37:29 - cvsupping the source tree TB --- 2008-08-23 09:37:29 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_6/i386/pc98/supfile TB --- 2008-08-23 09:37:37 - building world (CFLAGS=-O2 -pipe) TB --- 2008-08-23 09:37:37 - cd /src TB --- 2008-08-23 09:37:37 - /usr/bin/make -B buildworld 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 [...] === lib/libpam/modules/pam_rootok (buildincludes) === lib/libpam/modules/pam_securetty (buildincludes) === lib/libpam/modules/pam_self (buildincludes) === lib/libpam/modules/pam_ssh (buildincludes) === lib/libpam/modules/pam_tacplus (buildincludes) === lib/libpam/modules/pam_unix (buildincludes) === lib/libpam/libpam (buildincludes) make: don't know how to make security/openpam_attr.h. Stop *** Error code 2 Stop in /src/lib/libpam. *** Error code 1 Stop in /src/lib. *** Error code 1 Stop in /src/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-08-23 09:44:34 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-08-23 09:44:34 - ERROR: failed to build world TB --- 2008-08-23 09:44:34 - tinderbox aborted TB --- 328.09 user 32.62 system 448.51 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-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_6 tinderbox] failure on sparc64/sparc64
TB --- 2008-08-23 09:39:44 - tinderbox 2.3 running on freebsd-legacy.sentex.ca TB --- 2008-08-23 09:39:44 - starting RELENG_6 tinderbox run for sparc64/sparc64 TB --- 2008-08-23 09:39:44 - cleaning the object tree TB --- 2008-08-23 09:40:05 - cvsupping the source tree TB --- 2008-08-23 09:40:05 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_6/sparc64/sparc64/supfile TB --- 2008-08-23 09:40:16 - building world (CFLAGS=-O2 -pipe) TB --- 2008-08-23 09:40:16 - cd /src TB --- 2008-08-23 09:40:16 - /usr/bin/make -B buildworld 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 [...] === lib/libpam/modules/pam_rootok (buildincludes) === lib/libpam/modules/pam_securetty (buildincludes) === lib/libpam/modules/pam_self (buildincludes) === lib/libpam/modules/pam_ssh (buildincludes) === lib/libpam/modules/pam_tacplus (buildincludes) === lib/libpam/modules/pam_unix (buildincludes) === lib/libpam/libpam (buildincludes) make: don't know how to make security/openpam_attr.h. Stop *** Error code 2 Stop in /src/lib/libpam. *** Error code 1 Stop in /src/lib. *** Error code 1 Stop in /src/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-08-23 09:46:06 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-08-23 09:46:06 - ERROR: failed to build world TB --- 2008-08-23 09:46:06 - tinderbox aborted TB --- 281.35 user 31.88 system 381.98 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-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: Regression 7.0R - 7-stable?
On Thursday 14 August 2008 02:46:37 am Gerrit Kühn wrote: On Thu, 07 Aug 2008 15:55:30 -0700 Xin LI [EMAIL PROTECTED] wrote about Re: Regression 7.0R - 7-stable?: XL Could you please try disabling ACPI and boot? Additionally a 'boot - XL v' may reveal some useful information as well. Just some random XL thoughts. Disabling ACPI does not help, either (forgot to mention that earlier, sorry). I will post a boot -v log as soon as I have a working 7.0R on the system again. What about disabling apic? Also, are you using a serial console? If so, can you put DDB in your kernel and when it hangs break into ddb and do a 'ps' and capture the output. -- 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: Upcoming Releases Schedule...
Ken Smith wrote: We're about to start the release cycle for FreeBSD-7.1 and FreeBSD-6.4. The proposed schedule for the major events of the cycle is: Freeze August 29 BETASeptember 1 Branch September 6 6.4-RC1 September 8 7.1-RC1 September 15 6.4-RC2 September 22 7.1-RC2 September 29 6.4-REL October 6 7.1-REL October 13 *snip* In 25 words or less, what are the major changes in 7.0-7.1 and 6.3-6.4 for us end users? //Svein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sun4v arch
Peter Jeremy wrote: Is there a summary of the open issues somewhere? There are no sun4v PRs open. http://wiki.freebsd.org/FreeBSD/sun4v effectively hasn't been touched since November 2006 and suggests that the only critical issue is lack of serial port support. There is a better interpretation, which is that the only critical issue is lack of real users for this port, not lack of serial port support :). -Maxim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sun4v arch
On Sat, Aug 23, 2008 at 06:52:07PM -0700, Maxim Sobolev wrote: There is a better interpretation, which is that the only critical issue is lack of real users for this port, not lack of serial port support :). My understanding is the the port is in a pre-alpha state due to unfinished work in the kernel, so expecting there to be any userbase is premature. All of our 'new' architectures which are in this state have so few non- developer users that there is hardly any reason to submit PRs. AFAICT the active developers already know what's missing :-) Our implementation of GNATS barely serves us as a problem report system; it fails almost completely as a system for listing missing features. We would need to have something like that to track the status of the non- Tier-1 ports. (I used to maintain a table of how feature-complete the various ports are, but it is now way out of date.) mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sun4v arch
On Sat, Aug 23, 2008 at 6:52 PM, Maxim Sobolev [EMAIL PROTECTED] wrote: Peter Jeremy wrote: Is there a summary of the open issues somewhere? There are no sun4v PRs open. http://wiki.freebsd.org/FreeBSD/sun4v effectively hasn't been touched since November 2006 and suggests that the only critical issue is lack of serial port support. There is a better interpretation, which is that the only critical issue is lack of real users for this port, not lack of serial port support :). -Maxim Maybe some time should be spent looking at stuff from NetBSD to see whether or not they've solved some already critical porting pieces that FreeBSD lacks in this architecture? -Garrett ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sun4v arch
On 2008-Aug-23 22:40:55 -0500, Mark Linimon [EMAIL PROTECTED] wrote: My understanding is the the port is in a pre-alpha state due to unfinished work in the kernel, so expecting there to be any userbase is premature. Except that the wiki gives a far more optimistic picture. All of our 'new' architectures which are in this state have so few non- developer users that there is hardly any reason to submit PRs. AFAICT the active developers already know what's missing :-) That makes it very difficult for someone outside that group to come up to speed. I can't find anything in the freebsd-sun4v archvies. I was hoping that there would be a list somewhere of what state various subsystems were in and what remained to be done. wiki.freebsd.org sounds like the ideal place for this. On 2008-Aug-23 20:39:29 -0700, Garrett Cooper [EMAIL PROTECTED] wrote: Maybe some time should be spent looking at stuff from NetBSD to see whether or not they've solved some already critical porting pieces that FreeBSD lacks in this architecture? I can't find anything that suggests NetBSD runs on sun4v. Their sparc64 port only covers the US-I/II families and there's no mention of sun4v. -- 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. pgpoen3snXqeK.pgp Description: PGP signature
Re: sun4v arch
Hi Peter, There really isn't any magic to bringing up a port. You compile it, install it, and then run it until it breaks. Once it breaks you spend a lot of time instrumenting the code to track down what went wrong. Then, depending on the amount of technical insight you have in to the issue, you go through a number of iterations until it is fixed. Fixing the pmap issue is just (notice the quotes) a matter of tracking down the missing TLB shootdowns. For anyone who chooses pick this up it will be very educational. It will also be very time consuming. -Kip On Sat, Aug 23, 2008 at 9:23 PM, Peter Jeremy [EMAIL PROTECTED] wrote: On 2008-Aug-23 22:40:55 -0500, Mark Linimon [EMAIL PROTECTED] wrote: My understanding is the the port is in a pre-alpha state due to unfinished work in the kernel, so expecting there to be any userbase is premature. Except that the wiki gives a far more optimistic picture. All of our 'new' architectures which are in this state have so few non- developer users that there is hardly any reason to submit PRs. AFAICT the active developers already know what's missing :-) That makes it very difficult for someone outside that group to come up to speed. I can't find anything in the freebsd-sun4v archvies. I was hoping that there would be a list somewhere of what state various subsystems were in and what remained to be done. wiki.freebsd.org sounds like the ideal place for this. On 2008-Aug-23 20:39:29 -0700, Garrett Cooper [EMAIL PROTECTED] wrote: Maybe some time should be spent looking at stuff from NetBSD to see whether or not they've solved some already critical porting pieces that FreeBSD lacks in this architecture? I can't find anything that suggests NetBSD runs on sun4v. Their sparc64 port only covers the US-I/II families and there's no mention of sun4v. -- 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. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: sun4v arch
I can't find anything that suggests NetBSD runs on sun4v. Their sparc64 port only covers the US-I/II families and there's no mention of sun4v. OpenBSD/sparc64 supports the sun4v architecture has done for a while. _ Win New York holidays with Kellogg’s Live Search http://clk.atdmt.com/UKM/go/107571440/direct/01/___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sun4v arch
On Sat, Aug 23, 2008 at 9:34 PM, Sevan / Venture37 [EMAIL PROTECTED] wrote: I can't find anything that suggests NetBSD runs on sun4v. Their sparc64 port only covers the US-I/II families and there's no mention of sun4v. OpenBSD/sparc64 supports the sun4v architecture has done for a while. Heh. The bugs that FreeBSD exhibits on sun4v won't be hit on UP and are much less prevalent without preemption. -Kip ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upcoming Releases Schedule...
On Sun, Aug 24, 2008 at 01:45:08AM +0200, Svein Skogen wrote: In 25 words or less, what are the major changes in 7.0-7.1 and 6.3-6.4 for us end users? In more words, but pretty interesting: http://people.freebsd.org/~bmah/relnotes/6-STABLE/relnotes-i386.html http://people.freebsd.org/~bmah/relnotes/7-STABLE/relnotes.html Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
