From bugmaster at FreeBSD.org Mon Dec 1 03:07:01 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 1 03:08:53 2008 Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org Message-ID: <200812011107.mB1B70Lx052644@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- a power/121407 ppc [panic] Won't boot up; strange error message. o power/112435 ppc [nexus] [patch] Update nexus children to use ofw_bus f o power/111296 ppc [kernel] [patch] [request] Support IMISS, DLMISS an DS o power/93203 ppc FreeBSD PPC Can't Write to Partitions. 4 problems total. From tinderbox at freebsd.org Tue Dec 2 04:48:36 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Dec 2 04:50:26 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081202124831.68BC473039@freebsd-current.sentex.ca> TB --- 2008-12-02 11:31:03 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2008-12-02 11:31:03 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-12-02 11:31:03 - cleaning the object tree TB --- 2008-12-02 11:31:34 - cvsupping the source tree TB --- 2008-12-02 11:31:34 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-12-02 11:31:42 - building world TB --- 2008-12-02 11:31:42 - MAKEOBJDIRPREFIX=/obj TB --- 2008-12-02 11:31:42 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2008-12-02 11:31:42 - TARGET=powerpc TB --- 2008-12-02 11:31:42 - TARGET_ARCH=powerpc TB --- 2008-12-02 11:31:42 - TZ=UTC TB --- 2008-12-02 11:31:42 - __MAKE_CONF=/dev/null TB --- 2008-12-02 11:31:42 - cd /src TB --- 2008-12-02 11:31:42 - /usr/bin/make -B buildworld >>> World build started on Tue Dec 2 11:31:45 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 [...] cc -O2 -pipe -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/usr.bin/procstat/procstat_files.c cc -O2 -pipe -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/usr.bin/procstat/procstat_kstack.c cc -O2 -pipe -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/usr.bin/procstat/procstat_threads.c cc -O2 -pipe -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/usr.bin/procstat/procstat_vm.c cc1: warnings being treated as errors /src/usr.bin/procstat/procstat_vm.c: In function 'procstat_vm': /src/usr.bin/procstat/procstat_vm.c:59: warning: format '%*p' expects type 'void *', but argument 3 has type 'uint64_t' /src/usr.bin/procstat/procstat_vm.c:60: warning: format '%*p' expects type 'void *', but argument 3 has type 'uint64_t' *** Error code 1 Stop in /src/usr.bin/procstat. *** Error code 1 Stop in /src/usr.bin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-12-02 12:48:31 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-12-02 12:48:31 - ERROR: failed to build world TB --- 2008-12-02 12:48:31 - 3677.00 user 338.99 system 4647.80 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From bugmaster at FreeBSD.org Mon Dec 8 03:07:01 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 8 03:08:44 2008 Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org Message-ID: <200812081107.mB8B70O9014357@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- a power/121407 ppc [panic] Won't boot up; strange error message. o power/112435 ppc [nexus] [patch] Update nexus children to use ofw_bus f o power/111296 ppc [kernel] [patch] [request] Support IMISS, DLMISS an DS o power/93203 ppc FreeBSD PPC Can't Write to Partitions. 4 problems total. From horst at sxemacs.org Mon Dec 8 07:05:42 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Mon Dec 8 07:05:48 2008 Subject: Sane CFLAGS. Message-ID: <1228748788.1832.18.camel@horst-tla> Hey y'all. FreeBSD is working a treat. Except for one little thing. I changed my CFLAGS in make.conf - then compiled a HEAP of stuff. Which mostly now just spits out SIGILL. I have a PowerMac3,3 - Power Macintosh G4, 400MHz with 1MB cache. my CFLAGS were -Os -pipe -mcpu=7400 -mtune=7400 -maltivec -mabi=altivec I later changed that -Os to -O2 to no effect. What happened? Can I please have some advice regarding CFLAGS to set? (I'm contemplating removing altivec but would like advice from those more experienced than I.) Thanks, -- Horst. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081208/28a4f59b/attachment.pgp From jrh29 at alumni.cwru.edu Mon Dec 8 07:13:49 2008 From: jrh29 at alumni.cwru.edu (Justin Hibbits) Date: Mon Dec 8 07:13:55 2008 Subject: Sane CFLAGS. In-Reply-To: <1228748788.1832.18.camel@horst-tla> References: <1228748788.1832.18.camel@horst-tla> Message-ID: <20081208151307.GA41398@narn.knownspace> On Tue, Dec 09, 2008 at 02:06:28AM +1100, Horst G?nther Burkhardt III wrote: > Hey y'all. > > FreeBSD is working a treat. > > Except for one little thing. > > I changed my CFLAGS in make.conf - then compiled a HEAP of stuff. Which > mostly now just spits out SIGILL. > > I have a PowerMac3,3 - Power Macintosh G4, 400MHz with 1MB cache. > > my CFLAGS were -Os -pipe -mcpu=7400 -mtune=7400 -maltivec -mabi=altivec > > I later changed that -Os to -O2 to no effect. > > What happened? Can I please have some advice regarding CFLAGS to set? > > (I'm contemplating removing altivec but would like advice from those > more experienced than I.) > > Thanks, > -- Horst. Your problem is Altivec - there is no altivec support in the kernel yet, so you'll get SIGILL whenever it hits an altivec instruction. - Justin From horst at sxemacs.org Mon Dec 8 09:04:12 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Mon Dec 8 09:04:18 2008 Subject: Sane CFLAGS. In-Reply-To: <20081208151307.GA41398@narn.knownspace> References: <1228748788.1832.18.camel@horst-tla> <20081208151307.GA41398@narn.knownspace> Message-ID: <1228755903.1832.21.camel@horst-tla> On Mon, 2008-12-08 at 10:13 -0500, Justin Hibbits wrote: > Your problem is Altivec - there is no altivec support in the kernel yet, so > you'll get SIGILL whenever it hits an altivec instruction. > > - Justin Wow, thanks. Dealt with. So... considering I've built most things with those broken CFLAGS, how do I go about rebuilding everything I have installed ? :\ (Also, how far along the line is Altivec support expected to be?) :\ Thanks kindly, --Horst. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081208/7a602fab/attachment.pgp From nwhitehorn at freebsd.org Mon Dec 8 09:35:42 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Mon Dec 8 09:35:48 2008 Subject: Sane CFLAGS. In-Reply-To: <1228755903.1832.21.camel@horst-tla> References: <1228748788.1832.18.camel@horst-tla> <20081208151307.GA41398@narn.knownspace> <1228755903.1832.21.camel@horst-tla> Message-ID: <493D5AE5.6020002@freebsd.org> Horst G?nther Burkhardt III wrote: > On Mon, 2008-12-08 at 10:13 -0500, Justin Hibbits wrote: > >> Your problem is Altivec - there is no altivec support in the kernel yet, so >> you'll get SIGILL whenever it hits an altivec instruction. >> >> - Justin >> > > Wow, thanks. Dealt with. > > So... considering I've built most things with those broken CFLAGS, how > do I go about rebuilding everything I have installed ? :\ > > (Also, how far along the line is Altivec support expected to be?) :\ > > Thanks kindly, > --Horst. > Assuming these are only ports, I would suggest rebuilding ruby by hand, then doing a portupgrade -fa, which will force rebuild all ports. If you rebuilt critical system components (gcc for instance) with these CFLAGS, you might have no option but to reinstall world from CD. Altivec support shouldn't be too very complicated to add to the kernel (a matter of saving/restoring vector registers and parsing VRSAVE), and is on my todo list when I have free time again and G5 support is imported. -Nathan From horst at sxemacs.org Mon Dec 8 10:30:16 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Mon Dec 8 10:30:23 2008 Subject: Sane CFLAGS. In-Reply-To: <493D5AE5.6020002@freebsd.org> References: <1228748788.1832.18.camel@horst-tla> <20081208151307.GA41398@narn.knownspace> <1228755903.1832.21.camel@horst-tla> <493D5AE5.6020002@freebsd.org> Message-ID: <1228761068.1832.25.camel@horst-tla> On Mon, 2008-12-08 at 11:35 -0600, Nathan Whitehorn wrote: > Assuming these are only ports, I would suggest rebuilding ruby by hand, > then doing a portupgrade -fa, which will force rebuild all ports. If you > rebuilt critical system components (gcc for instance) with these CFLAGS, > you might have no option but to reinstall world from CD. ... I just did a rebuild on ruby, db41, ruby-bdb, and portupgrade. I'm _still_ getting SIGILL from trying to use portupgrade. (That's what started this in the first place, ironically)... ... I'm really confused, I _don't_ want to redo the install procedure, it was enough of a pain in my ass the first time. Any way to just remove everything that Ports has done, and rebuild the entire lot using the settings i had saved? :\ > Altivec support shouldn't be too very complicated to add to the kernel > (a matter of saving/restoring vector registers and parsing VRSAVE), and > is on my todo list when I have free time again and G5 support is imported. I look forward to it :) Thanks, --Horst. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081208/31e6e5cd/attachment.pgp From nwhitehorn at freebsd.org Mon Dec 8 10:38:19 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Mon Dec 8 10:38:26 2008 Subject: Sane CFLAGS. In-Reply-To: <1228761068.1832.25.camel@horst-tla> References: <1228748788.1832.18.camel@horst-tla> <20081208151307.GA41398@narn.knownspace> <1228755903.1832.21.camel@horst-tla> <493D5AE5.6020002@freebsd.org> <1228761068.1832.25.camel@horst-tla> Message-ID: <493D6994.60903@freebsd.org> Horst G?nther Burkhardt III wrote: > On Mon, 2008-12-08 at 11:35 -0600, Nathan Whitehorn wrote: > >> Assuming these are only ports, I would suggest rebuilding ruby by hand, >> then doing a portupgrade -fa, which will force rebuild all ports. If you >> rebuilt critical system components (gcc for instance) with these CFLAGS, >> you might have no option but to reinstall world from CD. >> > > ... I just did a rebuild on ruby, db41, ruby-bdb, and portupgrade. I'm > _still_ getting SIGILL from trying to use portupgrade. (That's what > started this in the first place, ironically)... > > ... I'm really confused, I _don't_ want to redo the install procedure, > it was enough of a pain in my ass the first time. > > Any way to just remove everything that Ports has done, and rebuild the entire lot using the settings i had saved? :\ > If you need to wipe everything, pkg_deinstall -a You will need to reinstall everything by hand, unfortunately, but it will keep your settings. You can also make sure you got all the dependencies by doing pkg_info -r portupgrade*, which will list the packages on which portupgrade depends. -Nathan From jrh29 at alumni.cwru.edu Mon Dec 8 11:29:48 2008 From: jrh29 at alumni.cwru.edu (Justin Hibbits) Date: Mon Dec 8 11:29:54 2008 Subject: Sane CFLAGS. In-Reply-To: <493D5AE5.6020002@freebsd.org> References: <1228748788.1832.18.camel@horst-tla> <20081208151307.GA41398@narn.knownspace> <1228755903.1832.21.camel@horst-tla> <493D5AE5.6020002@freebsd.org> Message-ID: <20081208184851.GA42785@narn.knownspace> On Mon, Dec 08, 2008 at 11:35:33AM -0600, Nathan Whitehorn wrote: > Horst G?nther Burkhardt III wrote: > > On Mon, 2008-12-08 at 10:13 -0500, Justin Hibbits wrote: > > > >> Your problem is Altivec - there is no altivec support in the kernel yet, so > >> you'll get SIGILL whenever it hits an altivec instruction. > >> > >> - Justin > >> > > > > Wow, thanks. Dealt with. > > > > So... considering I've built most things with those broken CFLAGS, how > > do I go about rebuilding everything I have installed ? :\ > > > > (Also, how far along the line is Altivec support expected to be?) :\ > > > > Thanks kindly, > > --Horst. > > > Assuming these are only ports, I would suggest rebuilding ruby by hand, > then doing a portupgrade -fa, which will force rebuild all ports. If you > rebuilt critical system components (gcc for instance) with these CFLAGS, > you might have no option but to reinstall world from CD. > > Altivec support shouldn't be too very complicated to add to the kernel > (a matter of saving/restoring vector registers and parsing VRSAVE), and > is on my todo list when I have free time again and G5 support is imported. > -Nathan > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" Nathan, I started working on Altivec support in the kernel, but haven't been successful. I mostly started with a port from NetBSD, but if you want the patches I made, I'll be happy to send them your way. - Justin From nwhitehorn at freebsd.org Mon Dec 8 11:50:21 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Mon Dec 8 11:50:31 2008 Subject: Sane CFLAGS. In-Reply-To: <20081208184851.GA42785@narn.knownspace> References: <1228748788.1832.18.camel@horst-tla> <20081208151307.GA41398@narn.knownspace> <1228755903.1832.21.camel@horst-tla> <493D5AE5.6020002@freebsd.org> <20081208184851.GA42785@narn.knownspace> Message-ID: <493D7A75.8010308@freebsd.org> Justin Hibbits wrote: > On Mon, Dec 08, 2008 at 11:35:33AM -0600, Nathan Whitehorn wrote: > >> Horst G?nther Burkhardt III wrote: >> >>> On Mon, 2008-12-08 at 10:13 -0500, Justin Hibbits wrote: >>> >>> >>>> Your problem is Altivec - there is no altivec support in the kernel yet, so >>>> you'll get SIGILL whenever it hits an altivec instruction. >>>> >>>> - Justin >>>> >>>> >>> Wow, thanks. Dealt with. >>> >>> So... considering I've built most things with those broken CFLAGS, how >>> do I go about rebuilding everything I have installed ? :\ >>> >>> (Also, how far along the line is Altivec support expected to be?) :\ >>> >>> Thanks kindly, >>> --Horst. >>> >>> >> Assuming these are only ports, I would suggest rebuilding ruby by hand, >> then doing a portupgrade -fa, which will force rebuild all ports. If you >> rebuilt critical system components (gcc for instance) with these CFLAGS, >> you might have no option but to reinstall world from CD. >> >> Altivec support shouldn't be too very complicated to add to the kernel >> (a matter of saving/restoring vector registers and parsing VRSAVE), and >> is on my todo list when I have free time again and G5 support is imported. >> -Nathan >> _______________________________________________ >> freebsd-ppc@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-ppc >> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" >> > > Nathan, > > I started working on Altivec support in the kernel, but haven't been > successful. I mostly started with a port from NetBSD, but if you want the > patches I made, I'll be happy to send them your way. > The "after I do x, y, z" above implies something like March, so please continue. -Nathan From horst at sxemacs.org Mon Dec 8 21:09:09 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Mon Dec 8 21:09:16 2008 Subject: Sane CFLAGS. In-Reply-To: <493D6994.60903@freebsd.org> References: <1228748788.1832.18.camel@horst-tla> <20081208151307.GA41398@narn.knownspace> <1228755903.1832.21.camel@horst-tla> <493D5AE5.6020002@freebsd.org> <1228761068.1832.25.camel@horst-tla> <493D6994.60903@freebsd.org> Message-ID: <1228799404.1832.30.camel@horst-tla> On Mon, 2008-12-08 at 12:38 -0600, Nathan Whitehorn wrote: > Horst G?nther Burkhardt III wrote: > > Any way to just remove everything that Ports has done, and rebuild the entire lot using the settings i had saved? :\ > > > If you need to wipe everything, pkg_deinstall -a [ bsdbox ] [ root ] [ ~ ] ==> pkg_deinstall -a [Updating the pkgdb in /var/db/pkg ... ** Stale lock file was found. Removed. Illegal instruction: 4 (core dumped) > You will need to reinstall everything by hand, unfortunately, but it > will keep your settings. > > You can also make sure you got all the dependencies by doing pkg_info -r > portupgrade*, which will list the packages on which portupgrade depends. > -Nathan Doctor, how hosed am I?... (I'm glad I won't lose my distfiles at least, they're NFS mounted on the same folder as my gentoo distfiles, for epic win.) What's the advised course of action? (If I _must_ reinstall is there a way to keep my ports options? some sort of file I can back up?) Also, do I have to go through the bootloader garbage again if I reinstall? :( -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081209/69aa14ca/attachment.pgp From nwhitehorn at freebsd.org Mon Dec 8 21:21:52 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Mon Dec 8 21:21:59 2008 Subject: Sane CFLAGS. In-Reply-To: <1228799404.1832.30.camel@horst-tla> References: <1228748788.1832.18.camel@horst-tla> <20081208151307.GA41398@narn.knownspace> <1228755903.1832.21.camel@horst-tla> <493D5AE5.6020002@freebsd.org> <1228761068.1832.25.camel@horst-tla> <493D6994.60903@freebsd.org> <1228799404.1832.30.camel@horst-tla> Message-ID: <493E00CE.40604@freebsd.org> Horst G?nther Burkhardt III wrote: > On Mon, 2008-12-08 at 12:38 -0600, Nathan Whitehorn wrote: >> Horst G?nther Burkhardt III wrote: >>> Any way to just remove everything that Ports has done, and rebuild the entire lot using the settings i had saved? :\ >>> >> If you need to wipe everything, pkg_deinstall -a > > [ bsdbox ] [ root ] [ ~ ] ==> pkg_deinstall -a > [Updating the pkgdb in /var/db/pkg ... ** Stale lock > file was found. Removed. > Illegal instruction: 4 (core dumped) I meant pkg_delete -a in my last mail, not pkg_deinstall -a. pkg_deinstall is related to portupgrade, whereas pkg_delete is part of the base. You can also rm -rf /usr/local /var/db/pkg to hose everything by hand. This is one of the nice side effects of the base/ports separation. >> You will need to reinstall everything by hand, unfortunately, but it >> will keep your settings. >> >> You can also make sure you got all the dependencies by doing pkg_info -r >> portupgrade*, which will list the packages on which portupgrade depends. >> -Nathan > > Doctor, how hosed am I?... > > (I'm glad I won't lose my distfiles at least, they're NFS mounted on the > same folder as my gentoo distfiles, for epic win.) > > What's the advised course of action? > > (If I _must_ reinstall is there a way to keep my ports options? some > sort of file I can back up?) > > Also, do I have to go through the bootloader garbage again if I > reinstall? :( No, if you have to reinstall you can keep all the bootloader stuff. But there is no reason you should have to if you did not rebuild world with altivec enabled. -Nathan From horst at sxemacs.org Mon Dec 8 22:57:56 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Mon Dec 8 22:58:03 2008 Subject: Sane CFLAGS. In-Reply-To: <493E00CE.40604@freebsd.org> References: <1228748788.1832.18.camel@horst-tla> <20081208151307.GA41398@narn.knownspace> <1228755903.1832.21.camel@horst-tla> <493D5AE5.6020002@freebsd.org> <1228761068.1832.25.camel@horst-tla> <493D6994.60903@freebsd.org> <1228799404.1832.30.camel@horst-tla> <493E00CE.40604@freebsd.org> Message-ID: <1228805931.1832.33.camel@horst-tla> On Mon, 2008-12-08 at 23:23 -0600, Nathan Whitehorn wrote: > Horst G?nther Burkhardt III wrote: > > On Mon, 2008-12-08 at 12:38 -0600, Nathan Whitehorn wrote: > >> Horst G?nther Burkhardt III wrote: > >>> Any way to just remove everything that Ports has done, and rebuild the entire lot using the settings i had saved? :\ > >>> > >> If you need to wipe everything, pkg_deinstall -a > > > > [ bsdbox ] [ root ] [ ~ ] ==> pkg_deinstall -a > > [Updating the pkgdb in /var/db/pkg ... ** Stale lock > > file was found. Removed. > > Illegal instruction: 4 (core dumped) > > I meant pkg_delete -a in my last mail, not pkg_deinstall -a. > pkg_deinstall is related to portupgrade, whereas pkg_delete is part of > the base. You can also rm -rf /usr/local /var/db/pkg to hose everything > by hand. This is one of the nice side effects of the base/ports separation. > > >> You will need to reinstall everything by hand, unfortunately, but it > >> will keep your settings. > -Nathan Wow. I now have two problems for the price of one. One, I have to rebuild my ports collection (not THAT huge an issue) and two: I've lost my ability to login over ssh using either my keys or my password. What gives? :( (I thought OpenSSH and OpenSSL and PAM were in base system...) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081209/e4544a57/attachment.pgp From horst at sxemacs.org Wed Dec 10 04:07:02 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Wed Dec 10 04:07:09 2008 Subject: Two issues. One minor, one major. Message-ID: <1228910881.1832.63.camel@horst-tla> Hey everybody. First question - ========= =syscons= ========= is it possible to change the font on the console? I personally would love to have the same small font as in in the openfirmware screen - or at least a similar small font. I like small console fonts :) Next issue, the more important one: =============== =lang/python25= =============== [ bsdbox ] [ root ] [ /usr/ports/lang/python25 ] ==> make ( ... ) ( Completed successfully ) [ bsdbox ] [ root ] [ /usr/ports/lang/python25 ] ==> make install ( ... ) ( ... ) Listing /usr/local/lib/python2.5/test/output ... Compiling /usr/local/lib/python2.5/test/outstanding_bugs.py ... Compiling /usr/local/lib/python2.5/test/pickletester.py ... Illegal instruction (core dumped) *** Error code 132 Stop in /usr/ports/lang/python25/work/Python-2.5.2/portbld.static. *** Error code 1 Stop in /usr/ports/lang/python25. *** Error code 1 Stop in /usr/ports/lang/python25. [ bsdbox ] [ root ] [ /usr/ports/lang/python25 ] ==> .... This is exceedingly disturbing. EXCEEDINGLY disturbing. I kinda need Python 2.5 :( Has anyone come across this issue? (btw, kdump of the python 'compileall.py' is located at http://midcom.unlogicnetworks/tmpfiles/python-compileall-kdump.txt.bz2 if anyone wants some insight into what's happening...) Thanks, --Horst. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081210/b66524a3/attachment.pgp From jrh29 at alumni.cwru.edu Wed Dec 10 06:11:09 2008 From: jrh29 at alumni.cwru.edu (Justin Hibbits) Date: Wed Dec 10 06:11:15 2008 Subject: Two issues. One minor, one major. In-Reply-To: <1228910881.1832.63.camel@horst-tla> References: <1228910881.1832.63.camel@horst-tla> Message-ID: <20081210141039.GA52605@narn.knownspace> On Wed, Dec 10, 2008 at 11:08:01PM +1100, Horst G?nther Burkhardt III wrote: > [ bsdbox ] [ root ] [ /usr/ports/lang/python25 ] ==> make install > > ( ... ) > > ( ... ) > > Listing /usr/local/lib/python2.5/test/output ... > Compiling /usr/local/lib/python2.5/test/outstanding_bugs.py ... > Compiling /usr/local/lib/python2.5/test/pickletester.py ... > Illegal instruction (core dumped) > *** Error code 132 > > Stop in /usr/ports/lang/python25/work/Python-2.5.2/portbld.static. > *** Error code 1 > > Stop in /usr/ports/lang/python25. > *** Error code 1 > > Stop in /usr/ports/lang/python25. > > [ bsdbox ] [ root ] [ /usr/ports/lang/python25 ] ==> > > > .... This is exceedingly disturbing. EXCEEDINGLY disturbing. I kinda > need Python 2.5 :( Have you been compiling everything with altivec support? That would cause illegal instructions for a lot of things, since it's not yet enabled. - Justin From horst at sxemacs.org Wed Dec 10 06:53:28 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Wed Dec 10 06:53:35 2008 Subject: Two issues. One minor, one major. In-Reply-To: <20081210141039.GA52605@narn.knownspace> References: <1228910881.1832.63.camel@horst-tla> <20081210141039.GA52605@narn.knownspace> Message-ID: <1228920872.1832.67.camel@horst-tla> On Wed, 2008-12-10 at 09:10 -0500, Justin Hibbits wrote: > On Wed, Dec 10, 2008 at 11:08:01PM +1100, Horst G?nther Burkhardt III wrote: > > .... This is exceedingly disturbing. EXCEEDINGLY disturbing. I kinda > > need Python 2.5 :( > > Have you been compiling everything with altivec support? That would cause > illegal instructions for a lot of things, since it's not yet enabled. > > - Justin No no no, I removed the altivec flags to the compiler, make.conf now says : CFLAGS=-Os -pipe -mcpu=7400 -mtune=7400 CCFLAGS=-Os -pipe -mcpu=7400 -mtune=7400 CXXFLAGS=-Os -pipe -mcpu=7400 -mtune=7400 I think those are perfectly reasonable CFLAGS ;) I'm hoping -mcpu=7400 does not imply -maltivec here or I'm really screwed :( Irssi compiled with these flags is working perfectly, as is glib, as is perl, etc. Any other ideas? Thanks, --Horst. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081210/376d6a99/attachment.pgp From horst at sxemacs.org Wed Dec 10 09:58:54 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Wed Dec 10 09:59:00 2008 Subject: Two issues. One minor, one major. In-Reply-To: <1228920872.1832.67.camel@horst-tla> References: <1228910881.1832.63.camel@horst-tla> <20081210141039.GA52605@narn.knownspace> <1228920872.1832.67.camel@horst-tla> Message-ID: <1228931995.1832.81.camel@horst-tla> Another thing I forgot: for those brave enough to look at this problem : the entire session log can be found at http://rafb.net/p/MOTbHY26.html relating to the failure of python25 to build. Any help would be greatly appreciated. I'm completely stumped as to the cause of this odd error. ktrace and kdump links available: ktrace : http://midcom.unlogicnetworks/tmpfiles/python-compileall-trace.txt.bz2 kdump -f: http://midcom.unlogicnetworks/tmpfiles/python-compileall-kdump.txt.bz2 Hopefully these will help unearth what went wrong to some extent. Is there anything further I can provide to assist with diagnosing the problem? (It has been suggested that this is an upstream bug perhaps.) Thanks again, -- Horst. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081210/8c121ec4/attachment.pgp From yanefbsd at gmail.com Thu Dec 11 02:01:06 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Thu Dec 11 02:01:12 2008 Subject: Two issues. One minor, one major. In-Reply-To: <1228931995.1832.81.camel@horst-tla> References: <1228910881.1832.63.camel@horst-tla> <20081210141039.GA52605@narn.knownspace> <1228920872.1832.67.camel@horst-tla> <1228931995.1832.81.camel@horst-tla> Message-ID: <7d6fde3d0812110131p13ae3076r301c708774834b7e@mail.gmail.com> On Wed, Dec 10, 2008 at 9:59 AM, Horst G?nther Burkhardt III wrote: > Another thing I forgot: for those brave enough to look at this problem : > the entire session log can be found at http://rafb.net/p/MOTbHY26.html > relating to the failure of python25 to build. Any help would be greatly > appreciated. > > I'm completely stumped as to the cause of this odd error. > > ktrace and kdump links available: > ktrace : http://midcom.unlogicnetworks/tmpfiles/python-compileall-trace.txt.bz2 > kdump -f: http://midcom.unlogicnetworks/tmpfiles/python-compileall-kdump.txt.bz2 > Hopefully these will help unearth what went wrong to some extent. > > Is there anything further I can provide to assist with diagnosing the problem? (It has been suggested that this is an upstream bug perhaps.) > > Thanks again, > -- Horst. Why are you using mcpu and mtune directly? You can use CPUTYPE, e.g.: CPUTYPE := nocona (Replace nocona with 7400 8-)...) I did a quick google search and while -mcpu=7400 and -mtune=7400 doesn't necessarily imply -maltivec, I would ask the GCC folks whether or not that is truly the case. Or a quicker means to determine if that is the problem is to use mcpu=common (or a known working 32-bit ppc arch) and see whether or not you run across the same error. -Garrett From andreast-list at fgznet.ch Thu Dec 11 03:08:14 2008 From: andreast-list at fgznet.ch (Andreas Tobler) Date: Thu Dec 11 03:08:22 2008 Subject: Two issues. One minor, one major. Message-ID: --------- Original Message -------- From: Garrett Cooper To: Horst G?nther Burkhardt III Cc: FreeBSD PowerPC ML Subject: Re: Two issues. One minor, one major. Date: 11/12/08 11:01 > On Wed, Dec 10, 2008 at 9:59 AM, Horst G?nther Burkhardt III > <horst@sxemacs.org> wrote: > > Another thing I forgot: for those brave enough to look at this problem : > > the entire session log can be found at http://rafb.net/p/MOTbHY26.html > > relating to the failure of python25 to build. Any help would be greatly > > appreciated. > > > > I'm completely stumped as to the cause of this odd error. > > > > ktrace and kdump links available: > > ktrace : http://midcom.unlogicnetworks/tmpfiles/python-compileall-trace.txt.bz2 > > kdump -f: http://midcom.unlogicnetworks/tmpfiles/python-compileall-kdump.txt.bz2 > > Hopefully these will help unearth what went wrong to some extent. > > > > Is there anything further I can provide to assist with diagnosing the problem? (It has been suggested that this is an upstream bug perhaps.) > > > > Thanks again, > > -- Horst. > > Why are you using mcpu and mtune directly? You can use CPUTYPE, e.g.: > > CPUTYPE := nocona > > (Replace nocona with 7400 8-)...) > > I did a quick google search and while -mcpu=7400 and -mtune=7400 > doesn't necessarily imply -maltivec, I would ask the GCC folks whether > or not that is truly the case. Or a quicker means to determine if that > is the problem is to use mcpu=common (or a known working 32-bit ppc > arch) and see whether or not you run across the same error. -mcpu=7400 does imply -mppc -maltivec. See the rs6000.h in the gcc/config/rs6000 directory. I'd suggest to build w/o special cpu flags. Andreas From grehan at freebsd.org Thu Dec 11 12:47:05 2008 From: grehan at freebsd.org (Peter Grehan) Date: Thu Dec 11 12:47:11 2008 Subject: Two issues. One minor, one major. Message-ID: <20081212064621.EMW11796@dommail.onthenet.com.au> Hi Horst, >is it possible to change the font on the console? Yes - use 'vidcontrol -f ', where is one of the standard FreeBSD syscons fonts. I think you might have to switch vty's and back to get it to redraw the existing screen in the new font. >I personally would love to have the same small font as in >in the openfirmware screen - or at least a similar small >font. > >I like small console fonts :) The font size can only be set at boot-time from the loader with the hw.syscons.fsize variable. Supported sizes (heights, really) are 8, 14 and 16, with 16 the default. later, Peter. From horst at sxemacs.org Fri Dec 12 01:56:53 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Fri Dec 12 01:56:59 2008 Subject: Two issues. One minor, one major. In-Reply-To: References: Message-ID: <1229075882.1832.85.camel@horst-tla> On Thu, 2008-12-11 at 11:32 +0100, Andreas Tobler wrote: > -mcpu=7400 does imply -mppc -maltivec. See the rs6000.h in the > gcc/config/rs6000 directory. > I'd suggest to build w/o special cpu flags. Thanks. OK. Idea: -Put patch in devel/gcc and patch in the base system that either makes altivec do nothing (NOT a good idea) makes mcpu not imply maltivec ( a better idea, as it can just be undone when the kernel gets altivec instruction support ) good idea y/y? (also, so it seems the fix is just explicitly supply -mno-altivec in the commandline) --Horst -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081212/3d5d0b95/attachment.pgp From yanefbsd at gmail.com Sat Dec 13 11:45:33 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sat Dec 13 11:45:46 2008 Subject: Two issues. One minor, one major. In-Reply-To: <1229075882.1832.85.camel@horst-tla> References: <1229075882.1832.85.camel@horst-tla> Message-ID: <7d6fde3d0812131145i4560cdb3rbea4c8a072452145@mail.gmail.com> On Fri, Dec 12, 2008 at 1:58 AM, Horst G?nther Burkhardt III wrote: > On Thu, 2008-12-11 at 11:32 +0100, Andreas Tobler wrote: >> -mcpu=7400 does imply -mppc -maltivec. See the rs6000.h in the >> gcc/config/rs6000 directory. >> I'd suggest to build w/o special cpu flags. > > Thanks. > > OK. Idea: > > -Put patch in devel/gcc and patch in the base system that either > > makes altivec do nothing (NOT a good idea) > makes mcpu not imply maltivec ( a better idea, as it can just be undone > when the kernel gets altivec instruction support ) > > > good idea y/y? > > (also, so it seems the fix is just explicitly supply -mno-altivec in the > commandline) > > --Horst I think that putting some logic in the ports and src makefiles to automatically add -mno-altivec would be wise. -Garrett From tinderbox at freebsd.org Sun Dec 14 14:59:52 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Sun Dec 14 14:59:59 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081214225949.9FBA573039@freebsd-current.sentex.ca> TB --- 2008-12-14 21:25:49 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2008-12-14 21:25:49 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-12-14 21:25:50 - cleaning the object tree TB --- 2008-12-14 21:26:23 - cvsupping the source tree TB --- 2008-12-14 21:26:23 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-12-14 21:26:31 - building world TB --- 2008-12-14 21:26:31 - MAKEOBJDIRPREFIX=/obj TB --- 2008-12-14 21:26:31 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2008-12-14 21:26:31 - TARGET=powerpc TB --- 2008-12-14 21:26:31 - TARGET_ARCH=powerpc TB --- 2008-12-14 21:26:31 - TZ=UTC TB --- 2008-12-14 21:26:31 - __MAKE_CONF=/dev/null TB --- 2008-12-14 21:26:31 - cd /src TB --- 2008-12-14 21:26:31 - /usr/bin/make -B buildworld >>> World build started on Sun Dec 14 21:26:32 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 Sun Dec 14 22:51:17 UTC 2008 TB --- 2008-12-14 22:51:17 - generating LINT kernel config TB --- 2008-12-14 22:51:17 - cd /src/sys/powerpc/conf TB --- 2008-12-14 22:51:17 - /usr/bin/make -B LINT TB --- 2008-12-14 22:51:17 - building LINT kernel TB --- 2008-12-14 22:51:17 - MAKEOBJDIRPREFIX=/obj TB --- 2008-12-14 22:51:17 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2008-12-14 22:51:17 - TARGET=powerpc TB --- 2008-12-14 22:51:17 - TARGET_ARCH=powerpc TB --- 2008-12-14 22:51:17 - TZ=UTC TB --- 2008-12-14 22:51:17 - __MAKE_CONF=/dev/null TB --- 2008-12-14 22:51:17 - cd /src TB --- 2008-12-14 22:51:17 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Dec 14 22:51:18 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 -fstack-protector -Werror /src/sys/dev/usb/uark.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 -fstack-protector -Werror /src/sys/dev/usb/u3g.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 -fstack-protector -Werror /src/sys/dev/usb/ubsa.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 -fstack-protector -Werror /src/sys/dev/usb/ucom.c /src/sys/dev/usb/ucom.c: In function 'ucomreadcb': /src/sys/dev/usb/ucom.c:746: error: 'tp' undeclared (first use in this function) /src/sys/dev/usb/ucom.c:746: error: (Each undeclared identifier is reported only once /src/sys/dev/usb/ucom.c:746: error: for each function it appears in.) *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-12-14 22:59:49 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-12-14 22:59:49 - ERROR: failed to build lint kernel TB --- 2008-12-14 22:59:49 - 4414.23 user 397.08 system 5639.26 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From bugmaster at FreeBSD.org Mon Dec 15 03:06:58 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 15 03:08:50 2008 Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org Message-ID: <200812151106.mBFB6uqI004432@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- a power/121407 ppc [panic] Won't boot up; strange error message. o power/112435 ppc [nexus] [patch] Update nexus children to use ofw_bus f o power/111296 ppc [kernel] [patch] [request] Support IMISS, DLMISS an DS o power/93203 ppc FreeBSD PPC Can't Write to Partitions. 4 problems total. From tinderbox at freebsd.org Mon Dec 15 10:04:32 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Mon Dec 15 10:04:43 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081215180428.90EAF73039@freebsd-current.sentex.ca> TB --- 2008-12-15 16:17:30 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2008-12-15 16:17:30 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-12-15 16:17:30 - cleaning the object tree TB --- 2008-12-15 16:18:11 - cvsupping the source tree TB --- 2008-12-15 16:18:11 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-12-15 16:18:22 - building world TB --- 2008-12-15 16:18:22 - MAKEOBJDIRPREFIX=/obj TB --- 2008-12-15 16:18:22 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2008-12-15 16:18:22 - TARGET=powerpc TB --- 2008-12-15 16:18:22 - TARGET_ARCH=powerpc TB --- 2008-12-15 16:18:22 - TZ=UTC TB --- 2008-12-15 16:18:22 - __MAKE_CONF=/dev/null TB --- 2008-12-15 16:18:22 - cd /src TB --- 2008-12-15 16:18:22 - /usr/bin/make -B buildworld >>> World build started on Mon Dec 15 16:18:25 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 [...] ===> usr.sbin/nvram (all) cc -O2 -pipe -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/usr.sbin/nvram/nvram.c cc -O2 -pipe -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -o nvram nvram.o gzip -cn /src/usr.sbin/nvram/nvram.8 > nvram.8.gz ===> usr.sbin/ofwdump (all) cc -O2 -pipe -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/usr.sbin/ofwdump/ofwdump.c In file included from /src/usr.sbin/ofwdump/ofwdump.c:29: /obj/powerpc/src/tmp/usr/include/dev/ofw/openfirm.h:76: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'pcell_t' *** Error code 1 Stop in /src/usr.sbin/ofwdump. *** Error code 1 Stop in /src/usr.sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-12-15 18:04:28 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-12-15 18:04:28 - ERROR: failed to build world TB --- 2008-12-15 18:04:28 - 4065.53 user 380.91 system 6418.03 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From nwhitehorn at freebsd.org Mon Dec 15 10:54:05 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Mon Dec 15 10:54:17 2008 Subject: [head tinderbox] failure on powerpc/powerpc In-Reply-To: <20081215180428.90EAF73039@freebsd-current.sentex.ca> References: <20081215180428.90EAF73039@freebsd-current.sentex.ca> Message-ID: <4946A05C.7090604@freebsd.org> FreeBSD Tinderbox wrote: > In file included from /src/usr.sbin/ofwdump/ofwdump.c:29: > /obj/powerpc/src/tmp/usr/include/dev/ofw/openfirm.h:76: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'pcell_t' > *** Error code 1 > Fixed. I wonder if my commit will beat the email about sparc64 failing... -Nathan From nse at delfi-konsult.com Tue Dec 16 13:09:41 2008 From: nse at delfi-konsult.com (Niels S. Eliasen) Date: Tue Dec 16 13:09:47 2008 Subject: gjournal on powerpc ? Message-ID: <4371EA68-09AF-4A22-88C8-37A2DBE8CC76@delfi-konsult.com> hi guys anyone knows if there are any "specialties" with regard to gjournal and FreeBSD on PowerPC?? or anyone who has this runnning at all ?? kind regards nse "Ach, crivens, what a wee snotter....." Quote from "The Wee Free Men" by Terry Pratchett From grehan at freebsd.org Tue Dec 16 13:46:30 2008 From: grehan at freebsd.org (Peter Grehan) Date: Tue Dec 16 13:46:36 2008 Subject: gjournal on powerpc ? Message-ID: <20081217074545.ENB16009@dommail.onthenet.com.au> >anyone knows if there are any "specialties" with regard to >gjournal and FreeBSD on PowerPC?? >or anyone who has this runnning at all ?? Niels, you're always at the bleeding edge :) I've not run gjournal, but I would hazard it should work fine. later, Peter. From tinderbox at freebsd.org Wed Dec 17 06:33:07 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Wed Dec 17 06:33:19 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081217143304.2CBB173039@freebsd-current.sentex.ca> TB --- 2008-12-17 12:31:54 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2008-12-17 12:31:54 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-12-17 12:31:54 - cleaning the object tree TB --- 2008-12-17 12:32:26 - cvsupping the source tree TB --- 2008-12-17 12:32:26 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-12-17 12:32:36 - building world TB --- 2008-12-17 12:32:36 - MAKEOBJDIRPREFIX=/obj TB --- 2008-12-17 12:32:36 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2008-12-17 12:32:36 - TARGET=powerpc TB --- 2008-12-17 12:32:36 - TARGET_ARCH=powerpc TB --- 2008-12-17 12:32:36 - TZ=UTC TB --- 2008-12-17 12:32:36 - __MAKE_CONF=/dev/null TB --- 2008-12-17 12:32:36 - cd /src TB --- 2008-12-17 12:32:36 - /usr/bin/make -B buildworld >>> World build started on Wed Dec 17 12:32:38 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 Wed Dec 17 14:20:34 UTC 2008 TB --- 2008-12-17 14:20:34 - generating LINT kernel config TB --- 2008-12-17 14:20:34 - cd /src/sys/powerpc/conf TB --- 2008-12-17 14:20:34 - /usr/bin/make -B LINT TB --- 2008-12-17 14:20:35 - building LINT kernel TB --- 2008-12-17 14:20:35 - MAKEOBJDIRPREFIX=/obj TB --- 2008-12-17 14:20:35 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2008-12-17 14:20:35 - TARGET=powerpc TB --- 2008-12-17 14:20:35 - TARGET_ARCH=powerpc TB --- 2008-12-17 14:20:35 - TZ=UTC TB --- 2008-12-17 14:20:35 - __MAKE_CONF=/dev/null TB --- 2008-12-17 14:20:35 - cd /src TB --- 2008-12-17 14:20:35 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Dec 17 14:20:35 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 [...] awk -f /src/sys/tools/makeobjops.awk /src/sys/kern/clock_if.m -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 -fstack-protector -Werror clock_if.c awk -f /src/sys/tools/makeobjops.awk /src/sys/kern/cpufreq_if.m -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 -fstack-protector -Werror cpufreq_if.c awk -f /src/sys/tools/makeobjops.awk /src/sys/kern/device_if.m -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 -fstack-protector -Werror device_if.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 -fstack-protector -Werror /src/sys/kern/imgact_elf.c /src/sys/kern/imgact_elf.c: In function 'elf32_freebsd_fixup': /src/sys/kern/imgact_elf.c:898: error: 'AT_DEBUG' undeclared (first use in this function) /src/sys/kern/imgact_elf.c:898: error: (Each undeclared identifier is reported only once /src/sys/kern/imgact_elf.c:898: error: for each function it appears in.) *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-12-17 14:33:03 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-12-17 14:33:03 - ERROR: failed to build lint kernel TB --- 2008-12-17 14:33:03 - 4687.07 user 430.03 system 7269.41 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From tinderbox at freebsd.org Fri Dec 19 21:12:05 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Fri Dec 19 21:12:12 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081220051202.52C547302F@freebsd-current.sentex.ca> TB --- 2008-12-20 03:39:37 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2008-12-20 03:39:37 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-12-20 03:39:37 - cleaning the object tree TB --- 2008-12-20 03:40:16 - cvsupping the source tree TB --- 2008-12-20 03:40:16 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-12-20 03:40:26 - building world TB --- 2008-12-20 03:40:26 - MAKEOBJDIRPREFIX=/obj TB --- 2008-12-20 03:40:26 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2008-12-20 03:40:26 - TARGET=powerpc TB --- 2008-12-20 03:40:26 - TARGET_ARCH=powerpc TB --- 2008-12-20 03:40:26 - TZ=UTC TB --- 2008-12-20 03:40:26 - __MAKE_CONF=/dev/null TB --- 2008-12-20 03:40:26 - cd /src TB --- 2008-12-20 03:40:26 - /usr/bin/make -B buildworld >>> World build started on Sat Dec 20 03:40:28 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 Dec 20 05:03:56 UTC 2008 TB --- 2008-12-20 05:03:56 - generating LINT kernel config TB --- 2008-12-20 05:03:56 - cd /src/sys/powerpc/conf TB --- 2008-12-20 05:03:56 - /usr/bin/make -B LINT TB --- 2008-12-20 05:03:57 - building LINT kernel TB --- 2008-12-20 05:03:57 - MAKEOBJDIRPREFIX=/obj TB --- 2008-12-20 05:03:57 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2008-12-20 05:03:57 - TARGET=powerpc TB --- 2008-12-20 05:03:57 - TARGET_ARCH=powerpc TB --- 2008-12-20 05:03:57 - TZ=UTC TB --- 2008-12-20 05:03:57 - __MAKE_CONF=/dev/null TB --- 2008-12-20 05:03:57 - cd /src TB --- 2008-12-20 05:03:57 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Dec 20 05:03:57 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 -fstack-protector -Werror /src/sys/dev/uart/uart_subr.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 -fstack-protector -Werror /src/sys/dev/uart/uart_tty.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 -fstack-protector -Werror /src/sys/dev/ubsec/ubsec.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 -fstack-protector -Werror /src/sys/dev/usb/ehci.c cc1: warnings being treated as errors /src/sys/dev/usb/ehci.c: In function 'ehci_idone': /src/sys/dev/usb/ehci.c:872: warning: passing argument 1 of 'ehci_dump_exfer' from incompatible pointer type /src/sys/dev/usb/ehci.c:872: error: too many arguments to function 'ehci_dump_exfer' *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-12-20 05:12:02 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-12-20 05:12:02 - ERROR: failed to build lint kernel TB --- 2008-12-20 05:12:02 - 4415.27 user 392.34 system 5544.22 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From bugmaster at FreeBSD.org Mon Dec 22 03:06:56 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 22 03:08:49 2008 Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org Message-ID: <200812221106.mBMB6ud5060667@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- a power/121407 ppc [panic] Won't boot up; strange error message. o power/112435 ppc [nexus] [patch] Update nexus children to use ofw_bus f o power/111296 ppc [kernel] [patch] [request] Support IMISS, DLMISS an DS o power/93203 ppc FreeBSD PPC Can't Write to Partitions. 4 problems total. From nse at delfi-konsult.com Tue Dec 23 15:44:57 2008 From: nse at delfi-konsult.com (Niels S. Eliasen) Date: Tue Dec 23 15:45:03 2008 Subject: 7.1 Beta 2 .. no fixit menu ? Message-ID: <8AD1BA14-B155-4842-82AD-5702BE8DDE22@delfi-konsult.com> hi guys Trying to restore a dump from a nfs-mount having wiped the disk in order to setup gjournal ... the documentation suggest me to use the "fixit" part from within the installer.... However ... no such thing found (or some similar error...) Is this not supported on PowerPC ...or is there some gotcha? kind regards nse "Ach, crivens, what a wee snotter....." Quote from "The Wee Free Men" by Terry Pratchett From xcllnt at mac.com Tue Dec 23 16:31:51 2008 From: xcllnt at mac.com (Marcel Moolenaar) Date: Tue Dec 23 16:31:57 2008 Subject: panic: ofw_bus_search_intrmap: expected interrupt cell size incorrect: 4 > 8 Message-ID: <460A59E1-DAF6-46B0-960F-337623A27921@mac.com> I just updated my xserve and got the following: ... pcib1: on nexus0 pci1: on pcib1 pcib2: at device 13.0 on pci1 pci2: on pcib2 panic: ofw_bus_search_intrmap: expected interrupt cell size incorrect: 4 > 8 cpuid = 0 KDB: enter: panic [thread pid 0 tid 100000 ] Stopped at 0x271904: addi r0, r0, 0x0 db> bt Tracing pid 0 tid 100000 td 0x508660 0xd00046e0: at panic+0x1cc 0xd0004740: at ofw_bus_search_intrmap+0x1d8 0xd00047a0: at ofw_bus_lookup_imap+0xcc 0xd00047d0: at ofw_pcib_pci_route_interrupt+0xd0 0xd0004840: at ofw_pcibus_assign_interrupt+0x184 0xd0004870: at pci_assign_interrupt+0x120 0xd00048f0: at pci_add_resources+0x648 0xd0004950: at pci_add_child+0x78 0xd0004970: at ofw_pcibus_attach+0x2bc 0xd00049e0: at device_attach+0x338 0xd0004a10: at device_probe_and_attach+0x5c 0xd0004a30: at bus_generic_attach+0x28 0xd0004a50: at ofw_pcib_pci_attach+0xb0 0xd0004a70: at device_attach+0x338 0xd0004aa0: at device_probe_and_attach+0x5c 0xd0004ac0: at bus_generic_attach+0x28 0xd0004ae0: at ofw_pcibus_attach+0x47c 0xd0004b50: at device_attach+0x338 0xd0004b80: at device_probe_and_attach+0x5c ... This is mostly a FYI at this time. I'm building 7.1-RC2 on the machine and can't play around with it... -- Marcel Moolenaar xcllnt@mac.com From nwhitehorn at freebsd.org Wed Dec 24 06:28:08 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Wed Dec 24 06:28:14 2008 Subject: panic: ofw_bus_search_intrmap: expected interrupt cell size incorrect: 4 > 8 In-Reply-To: <460A59E1-DAF6-46B0-960F-337623A27921@mac.com> References: <460A59E1-DAF6-46B0-960F-337623A27921@mac.com> Message-ID: <495246E5.4060305@freebsd.org> Marcel Moolenaar wrote: > I just updated my xserve and got the following: > > ... > pcib1: on nexus0 > pci1: on pcib1 > pcib2: at device 13.0 on pci1 > pci2: on pcib2 > panic: ofw_bus_search_intrmap: expected interrupt cell size incorrect: > 4 > 8 This means that the #interrupt-cells property of the bus's #interrupt-parent and the bus itself disagree (1 versus 2). I'm not even sure what the correct way to handle this is. Could you check some nodes on that PCI bus with ofwdump, and tell me what their interrupts properties look like? If you decide you do want to futz with it at some point, commenting out the three lines starting at line 301 in uninorth.c, immediately after the sc->sc_icells = 2 line, should fix it. -Nathan From xcllnt at mac.com Thu Dec 25 18:11:58 2008 From: xcllnt at mac.com (Marcel Moolenaar) Date: Thu Dec 25 18:12:04 2008 Subject: panic: ofw_bus_search_intrmap: expected interrupt cell size incorrect: 4 > 8 In-Reply-To: <495246E5.4060305@freebsd.org> References: <460A59E1-DAF6-46B0-960F-337623A27921@mac.com> <495246E5.4060305@freebsd.org> Message-ID: On Dec 24, 2008, at 6:27 AM, Nathan Whitehorn wrote: > Marcel Moolenaar wrote: >> I just updated my xserve and got the following: >> >> ... >> pcib1: on nexus0 >> pci1: on pcib1 >> pcib2: at device 13.0 on pci1 >> pci2: on pcib2 >> panic: ofw_bus_search_intrmap: expected interrupt cell size >> incorrect: 4 > 8 > This means that the #interrupt-cells property of the bus's > #interrupt-parent and the bus itself disagree (1 versus 2). I'm not > even sure what the correct way to handle this is. Could you check > some nodes on that PCI bus with ofwdump, and tell me what their > interrupts properties look like? I have a dump here: http://ns1.xcllnt.net/~marcel/machines/xserve/ofwdump.txt I'll see what I can do. FYI, -- Marcel Moolenaar xcllnt@mac.com From horst at sxemacs.org Sun Dec 28 08:55:10 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Sun Dec 28 08:55:16 2008 Subject: framebuffer at wrong resolution? Message-ID: <1230483366.24576.16.camel@horst-tla> Hey everybody :) I've hit yet another wall, this time a minor one, comparatively. My display and video card are usually set at 1280*1024, this even happens in X under FreeBSD with no issues. Yet for some reason the framebuffer is at 1024*768. I'm told this is autodetected. Is there anything I can put in /boot/device.hints or tell the bootloader to do automatically on every startup, to make my framebuffer have a res of 1280*1024? Cheers, -- Horst. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081228/dba8ae33/attachment.pgp From nwhitehorn at freebsd.org Sun Dec 28 12:36:11 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Sun Dec 28 12:36:42 2008 Subject: framebuffer at wrong resolution? In-Reply-To: <1230483366.24576.16.camel@horst-tla> References: <1230483366.24576.16.camel@horst-tla> Message-ID: <4957E32A.3030200@freebsd.org> Horst G?nther Burkhardt III wrote: > Hey everybody :) > > I've hit yet another wall, this time a minor one, comparatively. > > My display and video card are usually set at 1280*1024, this even > happens in X under FreeBSD with no issues. > > Yet for some reason the framebuffer is at 1024*768. I'm told this is > autodetected. > > Is there anything I can put in /boot/device.hints or tell the bootloader > to do automatically on every startup, to make my framebuffer have a res > of 1280*1024? > > Cheers, > -- Horst. > This is inherited from Open Firmware. You can play with the screen device's set-mode word in order to change it, but the ofw syscons driver itself has no ability to change the resolution. -Nathan From bugmaster at FreeBSD.org Mon Dec 29 03:07:00 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 29 03:08:46 2008 Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org Message-ID: <200812291106.mBTB6xkv024537@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- a power/121407 ppc [panic] Won't boot up; strange error message. o power/112435 ppc [nexus] [patch] Update nexus children to use ofw_bus f o power/111296 ppc [kernel] [patch] [request] Support IMISS, DLMISS an DS o power/93203 ppc FreeBSD PPC Can't Write to Partitions. 4 problems total. From tinderbox at freebsd.org Mon Dec 29 19:52:46 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Mon Dec 29 19:52:53 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081229195245.2CCAB7302F@freebsd-current.sentex.ca> TB --- 2008-12-29 18:20:03 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2008-12-29 18:20:03 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-12-29 18:20:03 - cleaning the object tree TB --- 2008-12-29 18:20:32 - cvsupping the source tree TB --- 2008-12-29 18:20:32 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-12-29 18:20:40 - building world TB --- 2008-12-29 18:20:40 - MAKEOBJDIRPREFIX=/obj TB --- 2008-12-29 18:20:40 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2008-12-29 18:20:40 - TARGET=powerpc TB --- 2008-12-29 18:20:40 - TARGET_ARCH=powerpc TB --- 2008-12-29 18:20:40 - TZ=UTC TB --- 2008-12-29 18:20:40 - __MAKE_CONF=/dev/null TB --- 2008-12-29 18:20:40 - cd /src TB --- 2008-12-29 18:20:40 - /usr/bin/make -B buildworld >>> World build started on Mon Dec 29 18:20:41 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 Mon Dec 29 19:42:39 UTC 2008 TB --- 2008-12-29 19:42:39 - generating LINT kernel config TB --- 2008-12-29 19:42:39 - cd /src/sys/powerpc/conf TB --- 2008-12-29 19:42:39 - /usr/bin/make -B LINT TB --- 2008-12-29 19:42:39 - building LINT kernel TB --- 2008-12-29 19:42:39 - MAKEOBJDIRPREFIX=/obj TB --- 2008-12-29 19:42:39 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2008-12-29 19:42:39 - TARGET=powerpc TB --- 2008-12-29 19:42:39 - TARGET_ARCH=powerpc TB --- 2008-12-29 19:42:39 - TZ=UTC TB --- 2008-12-29 19:42:39 - __MAKE_CONF=/dev/null TB --- 2008-12-29 19:42:39 - cd /src TB --- 2008-12-29 19:42:39 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Dec 29 19:42:39 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 -fstack-protector -Werror /src/sys/kern/kern_time.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 -fstack-protector -Werror /src/sys/kern/kern_timeout.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 -fstack-protector -Werror /src/sys/kern/kern_umtx.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 -fstack-protector -Werror /src/sys/kern/kern_uuid.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 -fstack-protector -Werror /src/sys/kern/kern_xxx.c cc1: warnings being treated as errors /src/sys/kern/kern_xxx.c: In function 'osethostname': /src/sys/kern/kern_xxx.c:86: warning: unused variable 'error' *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-12-29 19:52:45 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-12-29 19:52:45 - ERROR: failed to build lint kernel TB --- 2008-12-29 19:52:45 - 4515.57 user 399.84 system 5561.62 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From nse at delfi-konsult.com Tue Dec 30 12:45:25 2008 From: nse at delfi-konsult.com (Niels S. Eliasen) Date: Tue Dec 30 12:45:32 2008 Subject: gjournal on powerpc ? In-Reply-To: <20081217074545.ENB16009@dommail.onthenet.com.au> References: <20081217074545.ENB16009@dommail.onthenet.com.au> Message-ID: <9B79B417-E320-4CCA-A86E-1C1F5B2E5640@delfi-konsult.com> Hi Peter Now... after quite a bit of work... I have a gjournal'ed file- system.... while we are still waiting for ZFS/HammerFS .... (testing the gjournaled file-system doing the good-ole CTRL-ALT- POWER... really shines! how performance is otherwise.... i still need to figure out) just for the benefit of others going along: It is MUCH easier if you have several partitions, where you have a working FreeBSD system, and then setup the other partitions with gjournal..... and do follow the "man gjournal" guidelines.... even the references on the FreeBSD docs page are out-of-date.... And in the process... I noticed that the 7.1-BETA 2 I had installed from 3-4 weeks ago... was outdated! ;-) a few observations: 1. how do you set the hardware clock on PowerPC ?? (dead-annoying that before getting ntpdate/ntpd running... all dates on the filesystems defaults to something in 1904 !!!) 2. speaking of ntpdate/ntpd.... "named" would like to start before having set the date properly, which forces "named" to flunk out because of the date.... how to circumvent this ? 3. 7.1-BETA2 complains on the logfiles in "/var/log" and they do not created correctly... and have to be "touch"'ed accordingly... 4. I have a problem with the "locate" command... it appears that the updatedb produces gibberish... and have tried to re-create the locate db database... but still no luck.... 5. How do make a recovery CD for PowerPC ??? (it would have made my life a lot easier, having dump/restore easily available.... and principally the rest of the FreeBSD available) 6. Is there a "gpart" howto somewhere ? I understand the reason for having gpart, but pdisk is easier to use.... ;-) There are probably quite a number of PR's that needs/could be created by this... but I honestly do not know how do this.... Den 16/12/2008 kl. 22.45 skrev Peter Grehan: >> anyone knows if there are any "specialties" with regard to >> gjournal and FreeBSD on PowerPC?? >> or anyone who has this runnning at all ?? > > Niels, you're always at the bleeding edge :) I've not run > gjournal, but I would hazard it should work fine. > > later, > > Peter. kind regards nse "Ach, crivens, what a wee snotter....." Quote from "The Wee Free Men" by Terry Pratchett From horst at sxemacs.org Tue Dec 30 16:53:01 2008 From: horst at sxemacs.org (Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III) Date: Tue Dec 30 16:53:08 2008 Subject: gjournal on powerpc ? In-Reply-To: <9B79B417-E320-4CCA-A86E-1C1F5B2E5640@delfi-konsult.com> References: <20081217074545.ENB16009@dommail.onthenet.com.au> <9B79B417-E320-4CCA-A86E-1C1F5B2E5640@delfi-konsult.com> Message-ID: <1230656049.24576.22.camel@horst-tla> On Tue, 2008-12-30 at 13:39 +0100, Niels S. Eliasen wrote: > 1. how do you set the hardware clock on PowerPC ?? (dead-annoying that > before getting ntpdate/ntpd running... all dates on the filesystems > defaults to something in 1904 !!!) Heh, mine default to 1976 ;) I believe this is in ofw, but don't know where. > 2. speaking of ntpdate/ntpd.... "named" would like to start before > having set the date properly, which forces "named" to flunk out > because of the date.... how to circumvent this ? change the order of execution, procedure should be the same as on i386. Unfortunately once again I don't know specifics. > 3. 7.1-BETA2 complains on the logfiles in "/var/log" and they do not > created correctly... and have to be "touch"'ed accordingly... you could perhaps set /etc/rc.local to touch them on startup? > 4. I have a problem with the "locate" command... it appears that the > updatedb produces gibberish... and have tried to re-create the locate > db database... but still no luck.... > 5. How do make a recovery CD for PowerPC ??? (it would have made my > life a lot easier, having dump/restore easily available.... and > principally the rest of the FreeBSD available) There is a set of tools called FreeSBIE, I believe there was some work towards powerpc on this, but if you can get it working that will be the easiest way to make a FreeBSD LiveCD or recovery CD. > 6. Is there a "gpart" howto somewhere ? I understand the reason for > having gpart, but pdisk is easier to use.... ;-) > There are probably quite a number of PR's that needs/could be created > by this... but I honestly do not know how do this.... > > kind regards > > nse > > "Ach, crivens, what a wee snotter....." > > Quote from "The Wee Free Men" by Terry Pratchett -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20081230/ae1872ba/attachment.pgp From tinderbox at freebsd.org Wed Dec 31 15:45:17 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Wed Dec 31 15:45:39 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081231154515.B49267302F@freebsd-current.sentex.ca> TB --- 2008-12-31 14:07:33 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2008-12-31 14:07:33 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-12-31 14:07:33 - cleaning the object tree TB --- 2008-12-31 14:08:00 - cvsupping the source tree TB --- 2008-12-31 14:08:00 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-12-31 14:08:14 - building world TB --- 2008-12-31 14:08:14 - MAKEOBJDIRPREFIX=/obj TB --- 2008-12-31 14:08:14 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2008-12-31 14:08:14 - TARGET=powerpc TB --- 2008-12-31 14:08:14 - TARGET_ARCH=powerpc TB --- 2008-12-31 14:08:14 - TZ=UTC TB --- 2008-12-31 14:08:14 - __MAKE_CONF=/dev/null TB --- 2008-12-31 14:08:14 - cd /src TB --- 2008-12-31 14:08:14 - /usr/bin/make -B buildworld >>> World build started on Wed Dec 31 14:08: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 Wed Dec 31 15:30:22 UTC 2008 TB --- 2008-12-31 15:30:22 - generating LINT kernel config TB --- 2008-12-31 15:30:22 - cd /src/sys/powerpc/conf TB --- 2008-12-31 15:30:22 - /usr/bin/make -B LINT TB --- 2008-12-31 15:30:22 - building LINT kernel TB --- 2008-12-31 15:30:22 - MAKEOBJDIRPREFIX=/obj TB --- 2008-12-31 15:30:22 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2008-12-31 15:30:22 - TARGET=powerpc TB --- 2008-12-31 15:30:22 - TARGET_ARCH=powerpc TB --- 2008-12-31 15:30:22 - TZ=UTC TB --- 2008-12-31 15:30:22 - __MAKE_CONF=/dev/null TB --- 2008-12-31 15:30:22 - cd /src TB --- 2008-12-31 15:30:22 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Dec 31 15:30:22 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 [...] :> hack.c cc -shared -nostdlib hack.c -o hack.So rm -f hack.c MAKE=/usr/bin/make sh /src/sys/conf/newvers.sh LINT cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -fstack-protector -Werror vers.c linking kernel audit_bsm.o(.text+0x3dc): In function `kaudit_to_bsm': : undefined reference to `au_errno_to_bsm' *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-12-31 15:45:15 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-12-31 15:45:15 - ERROR: failed to build lint kernel TB --- 2008-12-31 15:45:15 - 4796.43 user 408.46 system 5862.18 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full