From nse at delfi-konsult.com Fri Jul 4 22:15:02 2008 From: nse at delfi-konsult.com (Niels S. Eliasen) Date: Fri Jul 4 22:15:08 2008 Subject: Linkin problem when trying to compile "gnash" Message-ID: <07568EF6-EC74-4639-AA7F-8839F4B38A8B@delfi-konsult.com> Hi guys Trying to compile(and install) gnash I get an error while trying to compile the "x264" package which gnash is dependent upon .... ===> Building for x264-0.0.20080409_2 cc -o x264 x264.o matroska.o muxers.o libx264.a -L/usr/local/lib -L/ usr/local/lib -L/usr/X11R6/lib -lX11 -lm -pthread -lgpac -Wl,- Bsymbolic -s libx264.a(common.o)(.text+0xfb8): In function `x264_param_default': : undefined reference to `x264_cpu_detect' libx264.a(common.o)(.text+0x1774): In function `x264_param_parse': : undefined reference to `x264_cpu_detect' libx264.a(mc.o)(.text+0x1c9c): In function `x264_mc_init': : undefined reference to `x264_mc_altivec_init' libx264.a(predict.o)(.text+0x3580): In function `x264_predict_16x16_init': : undefined reference to `x264_predict_16x16_init_altivec' libx264.a(pixel.o)(.text+0x6cc0): In function `x264_pixel_init': : undefined reference to `x264_pixel_altivec_init' libx264.a(frame.o)(.got2+0x20): undefined reference to `x264_deblock_v_luma_altivec' libx264.a(frame.o)(.got2+0x24): undefined reference to `x264_deblock_h_luma_altivec' libx264.a(dct.o)(.got2+0x34): undefined reference to `x264_sub4x4_dct_altivec' libx264.a(dct.o)(.got2+0x38): undefined reference to `x264_sub8x8_dct_altivec' libx264.a(dct.o)(.got2+0x3c): undefined reference to `x264_sub16x16_dct_altivec' libx264.a(dct.o)(.got2+0x40): undefined reference to `x264_add4x4_idct_altivec' libx264.a(dct.o)(.got2+0x44): undefined reference to `x264_add8x8_idct_altivec' libx264.a(dct.o)(.got2+0x48): undefined reference to `x264_add16x16_idct_altivec' libx264.a(dct.o)(.got2+0x4c): undefined reference to `x264_sub8x8_dct8_altivec' libx264.a(dct.o)(.got2+0x50): undefined reference to `x264_sub16x16_dct8_altivec' libx264.a(dct.o)(.got2+0x54): undefined reference to `x264_add8x8_idct8_altivec' libx264.a(dct.o)(.got2+0x58): undefined reference to `x264_add16x16_idct8_altivec' libx264.a(dct.o)(.got2+0x74): undefined reference to `x264_zigzag_scan_4x4_field_altivec' libx264.a(dct.o)(.got2+0x84): undefined reference to `x264_zigzag_scan_4x4_frame_altivec' libx264.a(quant.o)(.got2+0x18): undefined reference to `x264_quant_2x2_dc_altivec' libx264.a(quant.o)(.got2+0x1c): undefined reference to `x264_quant_4x4_dc_altivec' libx264.a(quant.o)(.got2+0x20): undefined reference to `x264_quant_4x4_altivec' libx264.a(quant.o)(.got2+0x24): undefined reference to `x264_quant_8x8_altivec' libx264.a(quant.o)(.got2+0x28): undefined reference to `x264_dequant_4x4_altivec' libx264.a(quant.o)(.got2+0x2c): undefined reference to `x264_dequant_8x8_altivec' gmake: *** [x264] Error 1 *** Error code 2 Stop in /usr/ports/multimedia/x264. *** Error code 1 Stop in /usr/ports/multimedia/x264. anyone knows how to fix this ? kind regards nse "Ach, crivens, what a wee snotter....." Quote from "The Wee Free Men" by Terry Pratchett From won.derick at yahoo.com Sun Jul 6 23:39:39 2008 From: won.derick at yahoo.com (Won De Erick) Date: Sun Jul 6 23:39:46 2008 Subject: Porting FreeBSD to PPC Message-ID: <248507.66773.qm@web45806.mail.sp1.yahoo.com> I am new in FPGA Embedded Development. I want to port FreeBSD using the embedded PPC in Xilinx Virtex4 ML403 board. Can anybody point me to the right path?? I want to know how the bootloader should also be. From bugmaster at FreeBSD.org Mon Jul 7 11:07:04 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jul 7 11:08:54 2008 Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org Message-ID: <200807071107.m67B74NX062134@freefall.freebsd.org> Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o power/93203 ppc FreeBSD PPC Can't Write to Partitions. a power/121407 ppc [panic] Won't boot up; strange error message. 2 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o power/111296 ppc [kernel] [patch] [request] Support IMISS, DLMISS an DS o power/112435 ppc [nexus] [patch] Update nexus children to use ofw_bus f 2 problems total. From grehan at freebsd.org Mon Jul 7 17:31:29 2008 From: grehan at freebsd.org (Peter Grehan) Date: Mon Jul 7 17:31:35 2008 Subject: Linkin problem when trying to compile "gnash" In-Reply-To: <07568EF6-EC74-4639-AA7F-8839F4B38A8B@delfi-konsult.com> References: <07568EF6-EC74-4639-AA7F-8839F4B38A8B@delfi-konsult.com> Message-ID: <487252EC.8010905@freebsd.org> Hi Niels, > anyone knows how to fix this ? It's a problem with the port: it doesn't pick the correct build options on FreeBSD, and some of the source files don't use the correct #defines - they think it is either OSX or Linux. My guess is it doesn't build on any *BSD without patches. later, Peter. From grehan at freebsd.org Mon Jul 7 17:36:51 2008 From: grehan at freebsd.org (Peter Grehan) Date: Mon Jul 7 17:36:58 2008 Subject: Porting FreeBSD to PPC In-Reply-To: <248507.66773.qm@web45806.mail.sp1.yahoo.com> References: <248507.66773.qm@web45806.mail.sp1.yahoo.com> Message-ID: <4872542E.6050701@freebsd.org> Hi, > I want to port FreeBSD using the embedded PPC in Xilinx Virtex4 ML403 board. > Can anybody point me to the right path?? It's going to take a lot of work - CPU support for the embedded 405 ppc core. This isn't in FreeBSD yet. - drivers for the on-chip peripherals > I want to know how the bootloader should also be. Looks like u-boot supports the ml403, and with u-boot now supporting FreeBSD, that should be the place to start. later, Peter. From raj at semihalf.com Mon Jul 7 18:30:09 2008 From: raj at semihalf.com (Rafal Jaworowski) Date: Mon Jul 7 18:30:18 2008 Subject: Porting FreeBSD to PPC In-Reply-To: <4872542E.6050701@freebsd.org> References: <248507.66773.qm@web45806.mail.sp1.yahoo.com> <4872542E.6050701@freebsd.org> Message-ID: <48725919.7060908@semihalf.com> Peter Grehan wrote: >> I want to port FreeBSD using the embedded PPC in Xilinx Virtex4 ML403 >> board. >> Can anybody point me to the right path?? > > It's going to take a lot of work > > - CPU support for the embedded 405 ppc core. This isn't in FreeBSD yet. True. One of the directions would be looking at NetBSD code, as they have some ppc405 support (at least Walnut platform was supposed to run when I last looked it it). >> I want to know how the bootloader should also be. > > Looks like u-boot supports the ml403, and with u-boot now supporting > FreeBSD, that should be the place to start. Yes, and getting the loader to work should be a pretty easy step: our existing PowerPC loader(8) for U-Boot should run as is in most cases: it's known to work on MPC85xx (e500) and MPC83xx (e300) and I don't see why this code would not run on other PowerPC variations. Rafal From nse at delfi-konsult.com Mon Jul 7 20:27:55 2008 From: nse at delfi-konsult.com (Niels S. Eliasen) Date: Mon Jul 7 20:28:03 2008 Subject: Linkin problem when trying to compile "gnash" In-Reply-To: <487252EC.8010905@freebsd.org> References: <07568EF6-EC74-4639-AA7F-8839F4B38A8B@delfi-konsult.com> <487252EC.8010905@freebsd.org> Message-ID: Hi Peter too bad... but at least I know it's not specific to FreeBSD then... ;-) Den 07/07/2008 kl. 19.31 skrev Peter Grehan: > Hi Niels, > >> anyone knows how to fix this ? > > It's a problem with the port: it doesn't pick the correct build > options on FreeBSD, and some of the source files don't use the > correct #defines - they think it is either OSX or Linux. My guess > is it doesn't build on any *BSD without patches. > > later, > > Peter. kind regards nse "Ach, crivens, what a wee snotter....." Quote from "The Wee Free Men" by Terry Pratchett From ross at grinz.com Tue Jul 8 14:51:54 2008 From: ross at grinz.com (Ross Gohlke) Date: Tue Jul 8 14:52:01 2008 Subject: CD boot fails (Decrementer exception) Message-ID: <50246.166.214.185.147.1215527482.squirrel@grinzport.grinz.com> I am finally getting around to the Xserve installation I asked about previously: FreeBSD 7.0-RELEASE installer CD (burned on an iBook a month ago) Xserve G4 Dual 1GHz Following these instructions: http://people.freebsd.org/~grehan/iso_install.txt Boot holding down 'c' does not work. Boot into Open Firmware (hold down Cmd-Opt-o-f) and issue: 0 > boot cd:,\boot\loader cd:0 OF finishes loading, then reports: Decrementer exception at %SRR0: 0035fc04 %SRR1: 00002032 ok 0 > Any ideas how I can fix this? Thanks. Ross Gohlke From geraldablists at gmail.com Tue Jul 8 16:18:33 2008 From: geraldablists at gmail.com (Gerald A) Date: Tue Jul 8 16:18:40 2008 Subject: Rescue FreeBSD (PowerPC)?? In-Reply-To: <4861EB3E.8000501@freebsd.org> References: <3CC3A394-8C85-4BBA-A52A-2045441F9398@delfi-konsult.com> <8e0ed1e00806241821m340fd33eu791a3a5542457da4@mail.gmail.com> <7d6fde3d0806242216i52cee175o35ad25d587260879@mail.gmail.com> <4861EB3E.8000501@freebsd.org> Message-ID: <8e0ed1e00807080918s2d6118b3l2e8d3f4ed63cd8d9@mail.gmail.com> On Wed, Jun 25, 2008 at 2:52 AM, Peter Grehan wrote: > The new "LiveCD" for x86 and amd64 isn't half bad, and feels a lot >> like the installer disk. >> > > The reason this isn't being built as part of the pp release process is > that it hasn't been determined what the mkisofs switches are to create a > bootable hybrid 9660/HFS image and also deal with the hard links that > FreeBSD creates without blowing out the size beyond a CD. Could it work as a DVD? (Can DVD PPC's be booted from a DVD?) I think both of my Blue and White's have DVDs in them. If I can get this far, I can work on... > So here's a call to action for ppc hackers: experiment and see if you can > work out what the magic incantation is. Start off by looking at the scripts > in src/release/powerpc. > I'm very familiar with FreeBSD. Would it be possible to cross compile world? (I know it is in theory, but is it a few switches that need tweaking, or is it microsurgery and headaches that will take weeks to sort out?). I'd love to get FreeBSD on my Blue and Whites, and am willing to fiddle a bit. Is it better to cross compile, or should I invest some time getting a hosted env on PPC going first? Any thoughts or advice are appreciated. Thanks, Gerald From nathanw at uchicago.edu Tue Jul 8 17:02:30 2008 From: nathanw at uchicago.edu (Nathan Whitehorn) Date: Tue Jul 8 17:02:43 2008 Subject: Rescue FreeBSD (PowerPC)?? In-Reply-To: <8e0ed1e00807080918s2d6118b3l2e8d3f4ed63cd8d9@mail.gmail.com> References: <3CC3A394-8C85-4BBA-A52A-2045441F9398@delfi-konsult.com> <8e0ed1e00806241821m340fd33eu791a3a5542457da4@mail.gmail.com> <7d6fde3d0806242216i52cee175o35ad25d587260879@mail.gmail.com> <4861EB3E.8000501@freebsd.org> <8e0ed1e00807080918s2d6118b3l2e8d3f4ed63cd8d9@mail.gmail.com> Message-ID: <487397FD.6010902@uchicago.edu> Gerald A wrote: > On Wed, Jun 25, 2008 at 2:52 AM, Peter Grehan wrote: > > >> The reason this isn't being built as part of the pp release process is >> that it hasn't been determined what the mkisofs switches are to create a >> bootable hybrid 9660/HFS image and also deal with the hard links that >> FreeBSD creates without blowing out the size beyond a CD. >> > > > Could it work as a DVD? (Can DVD PPC's be booted from a DVD?) > > I think both of my Blue and White's have DVDs in them. If I can get this > far, I can work on... > > They can, but it's probably easier/better to figure out a way around the size explosion. >> So here's a call to action for ppc hackers: experiment and see if you can >> work out what the magic incantation is. Start off by looking at the scripts >> in src/release/powerpc. >> >> > > I'm very familiar with FreeBSD. Would it be possible to cross compile world? > (I know it is in theory, but is it a few switches that need tweaking, or is > it microsurgery and headaches that will take weeks to sort out?). I'd love > to get FreeBSD on my Blue and Whites, and am willing to fiddle a bit. > Is it better to cross compile, or should I invest some time getting a hosted > env on PPC going first? Any thoughts or advice are appreciated. > Cross-compiling works very well, depending on what you want to do. You can't build release ISOs, but you can get a bootable system which is useful for netbooting. Just do something like this and wait: make buildworld buildkernel installworld installkernel distribution TARGET_ARCH=powerpc DESTDIR=$(PPC_NFSBOOT) For the blue and whites, you'll want a fairly recent (last couple weeks) -CURRENT to get support for the built-in ethernet. I'd appreciate any testing you feel like doing with the ethernet too, since I've only tested it on my machine. -Nathan From philip.s.schulz at googlemail.com Tue Jul 8 17:41:58 2008 From: philip.s.schulz at googlemail.com (Philip Schulz) Date: Tue Jul 8 17:42:04 2008 Subject: CD boot fails (Decrementer exception) In-Reply-To: <50246.166.214.185.147.1215527482.squirrel@grinzport.grinz.com> References: <50246.166.214.185.147.1215527482.squirrel@grinzport.grinz.com> Message-ID: <1c66db910807081041n4f58a5b8rf083ed65b61ed79a@mail.gmail.com> 2008/7/8 Ross Gohlke : > I am finally getting around to the Xserve installation I asked about > previously: > FreeBSD 7.0-RELEASE installer CD (burned on an iBook a month ago) > Xserve G4 Dual 1GHz > Following these instructions: > http://people.freebsd.org/~grehan/iso_install.txt > > Boot holding down 'c' does not work. > Boot into Open Firmware (hold down Cmd-Opt-o-f) and issue: > 0 > boot cd:,\boot\loader cd:0 > > OF finishes loading, then reports: > Decrementer exception at %SRR0: 0035fc04 %SRR1: 00002032 > ok > 0 > > Does the loader start at all? I haven't experienced the issue myself, but I think what happens is that Open Firmware enables interrupts before the kernel has a chance to install its own exception handlers. I have seen reports that the exception occurs both on NetBSD and OpenBSD. The latter seems to have added a workaround: They set the decrementer register to a very high value, very early in the boot process (possibly even in their loader). You can accomplish the same from Open Firmware: > 1 1f lshift not dec! This should set the decrementer register to 0x7fffffff which is the highest possible value. This should give you enough time to execute the loader and start the kernel. You could also try and start the kernel directly, without the loader. HTH, Philip From ross at grinz.com Tue Jul 8 21:51:08 2008 From: ross at grinz.com (Ross Gohlke) Date: Tue Jul 8 21:51:16 2008 Subject: CD boot fails (Decrementer exception) In-Reply-To: <1c66db910807081041n4f58a5b8rf083ed65b61ed79a@mail.gmail.com> References: <50246.166.214.185.147.1215527482.squirrel@grinzport.grinz.com> <1c66db910807081041n4f58a5b8rf083ed65b61ed79a@mail.gmail.com> Message-ID: <50771.166.214.0.37.1215553782.squirrel@grinzport.grinz.com> Thanks for the suggestion. In the meantime, I downloaded a fresh bootonly ISO from freebsd.org and burned it on a friend's Windows XP box. It boots per the instructions, but hangs for about 10 minutes: acd0: TIMEOUT - READ_BIG retrying (1 retry left) ... variations of the above for about 12 lines But it works! > 2008/7/8 Ross Gohlke : >> I am finally getting around to the Xserve installation I asked about previously: >> FreeBSD 7.0-RELEASE installer CD (burned on an iBook a month ago) Xserve G4 Dual 1GHz >> Following these instructions: >> http://people.freebsd.org/~grehan/iso_install.txt >> Boot holding down 'c' does not work. >> Boot into Open Firmware (hold down Cmd-Opt-o-f) and issue: >> 0 > boot cd:,\boot\loader cd:0 >> OF finishes loading, then reports: >> Decrementer exception at %SRR0: 0035fc04 %SRR1: 00002032 >> ok >> 0 > > > Does the loader start at all? Yes, the loader got all the way to "hit [enter]" screen (I let it time out). then gave the error, which changed to: Invalid memory access at %SRR0: 0035fc04 %SRR1: 00002032 I'm not sure what happened to the CD since I burned it... > I haven't experienced the issue myself, but I think what happens is that Open Firmware enables interrupts before the kernel has a chance to install its own exception handlers. I have seen reports that the exception occurs both on NetBSD and OpenBSD. The latter seems to have added a workaround: They set the decrementer register to a very high value, very early in the boot process (possibly even in their loader). > > You can accomplish the same from Open Firmware: > >> 1 1f lshift not dec! > > This should set the decrementer register to 0x7fffffff which is the highest possible value. This should give you enough time to execute the loader and start the kernel. > > You could also try and start the kernel directly, without the loader. > > HTH, > > Philip > _______________________________________________ > 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" > From freebsd-questions at slightlystrange.org Wed Jul 9 15:48:31 2008 From: freebsd-questions at slightlystrange.org (Daniel Bye) Date: Wed Jul 9 15:48:38 2008 Subject: GTK+ build fails on FreeBSD7-STABLE/PowerPC Message-ID: <20080709153436.GC37232@torus.slightlystrange.org> Hi all, Sorry to ask about ports on this list, but it seems only to affect FreeBSD/PowerPC. Trying to build XFCE4, which requires gtk+-2.12.11 (x11-toolkits/gtk20). The build of gtk+ bombs out with this: gmake[3]: Leaving directory `/usr/ports/x11-toolkits/gtk20/work/gtk+-2.12.11/gtk' GDK_PIXBUF_MODULE_FILE=../gdk-pixbuf/gdk-pixbuf.loaders ./gtk-update-icon-cache --force --ignore-theme-index \ --source builtin_icons stock-icons > gtkbuiltincache.h.tmp && \ mv gtkbuiltincache.h.tmp gtkbuiltincache.h gtk-update-icon-cache: The generated cache was invalid. gmake[2]: *** [gtkbuiltincache.h] Error 1 gmake[2]: Leaving directory `/usr/ports/x11-toolkits/gtk20/work/gtk+-2.12.11/gtk' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/x11-toolkits/gtk20/work/gtk+-2.12.11' gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/x11-toolkits/gtk20. I have built the same port on i386 and sparc64 without problems. I have seen many mentions of the "generated cache was invalid" error on the web, but all reports seem related to Linux, and offer no hints as to fixing it on FreeBSD. I have tried portdowngrade to get a previous version, but portdowngrade just sits there at around 99% CPU indefinitely. Anyone else similar problems? Cheers, Dan -- Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20080709/e37c29cf/attachment.pgp From Marek.Woloszyn at comp-css.pl Thu Jul 10 07:04:26 2008 From: Marek.Woloszyn at comp-css.pl (Marek Woloszyn) Date: Thu Jul 10 07:04:33 2008 Subject: FreeBSD on MPC8349 (e300 core) Message-ID: <619ad8c052767e90.4875c952@comp.waw.pl> Hi All, We have FreeBSD 6.3 running on our Freescale MPC8349 board (e300 core). But, unfortunately, it is not stable and we don't know what to do now. We have added several things to FreeBSD 6.3 to make it work on our board: 1. Some workarounds for OpenBIOS. 2. IMISS, DLMISS and DSMISS exceptions handlers in trap_subr.S. 3. Other hardware dependent stuff. We have noticed that there were some errors in pmap: 1. Unnecessary ptegidx shift in pmap_pte_insert function (already fixed in 7.0). 2. Hash table overflows when the system works with high load - caused by non-uniform PTE entries distribution in the hash table. Unfortunately we still have problems with the system. We experience random processes crashes when the system is starting. It happens approximately once for 20 boots. If the system does not crash at the startup, everything works fine. We do not know where to look for the solution: pmap? vm? Could you help us? Any suggestions were to start or something else we could do? Do you plan to work with e300 and e600 cores? And if so, when do you plan to implement IMISS, DLMISS and DSMISS exceptions handlers? Our might not work properly. Kind regards, Marek Wo?oszyn, Marcin Ligenza, Konrad Karpowicz From grehan at freebsd.org Thu Jul 10 07:07:24 2008 From: grehan at freebsd.org (Peter Grehan) Date: Thu Jul 10 07:07:54 2008 Subject: GTK+ build fails on FreeBSD7-STABLE/PowerPC In-Reply-To: <20080709153436.GC37232@torus.slightlystrange.org> References: <20080709153436.GC37232@torus.slightlystrange.org> Message-ID: <4875B526.6090601@freebsd.org> Hi Daniel, > gtk-update-icon-cache: The generated cache was invalid. ... > I have built the same port on i386 and sparc64 without problems. I have > seen many mentions of the "generated cache was invalid" error on the web, > but all reports seem related to Linux, and offer no hints as to fixing it > on FreeBSD. > > I have tried portdowngrade to get a previous version, but portdowngrade > just sits there at around 99% CPU indefinitely. > > Anyone else similar problems? I'll give it a try and see what happens. later, Peter. From grehan at freebsd.org Thu Jul 10 07:23:14 2008 From: grehan at freebsd.org (Peter Grehan) Date: Thu Jul 10 07:23:21 2008 Subject: FreeBSD on MPC8349 (e300 core) In-Reply-To: <619ad8c052767e90.4875c952@comp.waw.pl> References: <619ad8c052767e90.4875c952@comp.waw.pl> Message-ID: <4875B8DD.5060005@freebsd.org> Hi Marek, > We have FreeBSD 6.3 running on our Freescale MPC8349 board (e300 > core). Excellent ! > But, unfortunately, it is not stable and we don't know what to > do now. > > We have added several things to FreeBSD 6.3 to make it work on our > board: 1. Some workarounds for OpenBIOS. 2. IMISS, DLMISS and DSMISS > exceptions handlers in trap_subr.S. 3. Other hardware dependent > stuff. There is a SoC project this year to port to the Efika platform: http://wiki.freebsd.org/Porting_FreeBSD_to_Efika_%28PPC_bring_up%29 The *MISS exception handlers are in that, via some patches that Andrew Turner contributed many moons back. > We have noticed that there were some errors in pmap: 1. Unnecessary > ptegidx shift in pmap_pte_insert function (already fixed in 7.0). Yep, needs to be MFC'd back to RELENG_6. > 2. Hash table overflows when the system works with high load - caused > by non-uniform PTE entries distribution in the hash table. Have you tried increasing the size of the hash table ? That is a simple workaround. As you may have seen, there is no facility for overflow of the secondary hash bucket: that is something that could be added. > Unfortunately we still have problems with the system. We experience > random processes crashes when the system is starting. It happens > approximately once for 20 boots. If the system does not crash at the > startup, everything works fine. We do not know where to look for the > solution: pmap? vm? Is it a hang ? A panic ? If the latter, do you have a console trace ? > Could you help us? Any suggestions were to start or something else we > could do? Do you plan to work with e300 and e600 cores? And if so, > when do you plan to implement IMISS, DLMISS and DSMISS exceptions > handlers? Our might not work properly. As above, the code from the SoC project will probably make it's way into the codebase. later, Peter. From won.derick at yahoo.com Thu Jul 10 09:23:29 2008 From: won.derick at yahoo.com (Won De Erick) Date: Thu Jul 10 09:23:58 2008 Subject: Porting FreeBSD to PPC Message-ID: <623735.31011.qm@web45811.mail.sp1.yahoo.com> Hi Peter, thanks. Is U-boot an open source? When porting, what are the things that I need to know. I can't see detailed tutorials on the internet. Hope for your support! Won ----- Original Message ---- From: Peter Grehan To: Won De Erick Cc: freebsd-ppc@freebsd.org Sent: Tuesday, July 8, 2008 1:36:46 AM Subject: Re: Porting FreeBSD to PPC Hi, > I want to port FreeBSD using the embedded PPC in Xilinx Virtex4 ML403 board. > Can anybody point me to the right path?? It's going to take a lot of work - CPU support for the embedded 405 ppc core. This isn't in FreeBSD yet. - drivers for the on-chip peripherals > I want to know how the bootloader should also be. Looks like u-boot supports the ml403, and with u-boot now supporting FreeBSD, that should be the place to start. later, Peter. From won.derick at yahoo.com Thu Jul 10 09:25:39 2008 From: won.derick at yahoo.com (Won De Erick) Date: Thu Jul 10 09:25:52 2008 Subject: Porting FreeBSD to PPC Message-ID: <677262.66173.qm@web45815.mail.sp1.yahoo.com> Hi Rafal, Is PowerPC loader(8) an open source? Can you point to me where I could have the codes? Thanks, Won ----- Original Message ---- From: Rafal Jaworowski To: grehan@freebsd.org Cc: Won De Erick ; freebsd-ppc@freebsd.org Sent: Tuesday, July 8, 2008 1:57:45 AM Subject: Re: Porting FreeBSD to PPC Peter Grehan wrote: >> I want to port FreeBSD using the embedded PPC in Xilinx Virtex4 ML403 >> board. >> Can anybody point me to the right path?? > > It's going to take a lot of work > > - CPU support for the embedded 405 ppc core. This isn't in FreeBSD yet. True. One of the directions would be looking at NetBSD code, as they have some ppc405 support (at least Walnut platform was supposed to run when I last looked it it). >> I want to know how the bootloader should also be. > > Looks like u-boot supports the ml403, and with u-boot now supporting > FreeBSD, that should be the place to start. Yes, and getting the loader to work should be a pretty easy step: our existing PowerPC loader(8) for U-Boot should run as is in most cases: it's known to work on MPC85xx (e500) and MPC83xx (e300) and I don't see why this code would not run on other PowerPC variations. Rafal From Marek.Woloszyn at comp-css.pl Thu Jul 10 09:42:19 2008 From: Marek.Woloszyn at comp-css.pl (Marek Woloszyn) Date: Thu Jul 10 09:42:25 2008 Subject: FreeBSD on MPC8349 (e300 core) Message-ID: <4884777a784ee096.4875f596@comp.waw.pl>
Peter Grehan wrote:
Hi Marek,
< FreeBSD 6.3 running on (e300
core).

 Excellent !

h tt p://wiki.freebsd.org/Porting_FreeBSD_to_Efika_%28PPC=5 Fb exception hand Andrew
Turner contribut back.

We will look into it.


 Yep, be MFC'd back to RELENG_6.

2. Hash table overflows when the system works with distribution in th table.

 Have you tried increasing the size of the hash table ? That is a simple
worka facility for overflow of< something that could be added.

Yes. We have already tried that. It stil bucket hi hash bucket an type="cite">random processes crashes when the syste starting. It happens
approximately once for 20 boots. If the system does not crash at the
startup, everything works fin pmap? vm? ? A panic ? ?



Kind Regards,
Marcin Ligenza
< -------------- next part -------------- A non-text attachment was scrubbed... Name: 225.tail.core.bt Type: application/octet-stream Size: 1241 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20080710/288328fb/225.tail.core.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: 371.sh.core.bt Type: application/octet-stream Size: 4116 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20080710/288328fb/371.sh.core.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: 467.pkill.core Type: application/octet-stream Size: 3497 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20080710/288328fb/467.pkill.obj From philip.s.schulz at googlemail.com Thu Jul 10 10:00:55 2008 From: philip.s.schulz at googlemail.com (Philip Schulz) Date: Thu Jul 10 10:01:03 2008 Subject: Porting FreeBSD to PPC In-Reply-To: <623735.31011.qm@web45811.mail.sp1.yahoo.com> References: <623735.31011.qm@web45811.mail.sp1.yahoo.com> Message-ID: <1c66db910807100300u21d3e51p517ca0c22ac126b6@mail.gmail.com> Neither Peter nor Rafal, but ... 2008/7/10 Won De Erick : > Hi Peter, > > thanks. Is U-boot an open source? When porting, what are the things that I need to know. I can't see detailed tutorials on the internet. > Hope for your support! > Yes, u-boot is an open source project. See http://www.denx.de/wiki/UBoot/WebHome Btw, you could have easily found that out using Google. 2008/7/10 Won De Erick : > Hi Rafal, > > Is PowerPC loader(8) an open source? Can you point to me where I could have the codes? > loader(8) is the FreeBSD loader which is available as part of the FreeBSD source code. HTH, Philip From Marek.Woloszyn at comp-css.pl Thu Jul 10 10:40:24 2008 From: Marek.Woloszyn at comp-css.pl (Marek Woloszyn) Date: Thu Jul 10 10:40:31 2008 Subject: FreeBSD on MPC8349 (e300 core) Message-ID: <57ea49861343a439.48760333@comp.waw.pl> Peter Grehan wrote: > Hi Marek, > >> We have FreeBSD 6.3 running on our Freescale MPC8349 board (e300 >> core). > > Excellent ! > >> But, unfortunately, it is not stable and we don't know what to >> do now. >> >> We have added several things to FreeBSD 6.3 to make it work on our >> board: 1. Some workarounds for OpenBIOS. 2. IMISS, DLMISS and DSMISS >> exceptions handlers in trap_subr.S. 3. Other hardware dependent >> stuff. > > There is a SoC project this year to port to the Efika platform: > > http://wiki.freebsd.org/Porting_FreeBSD_to_Efika_%28PPC_bring_up%29 > > The *MISS exception handlers are in that, via some patches that Andrew > Turner contributed many moons back. We will look into it. >> We have noticed that there were some errors in pmap: 1. Unnecessary >> ptegidx shift in pmap_pte_insert function (already fixed in 7.0). > > Yep, needs to be MFC'd back to RELENG_6. > >> 2. Hash table overflows when the system works with high load - caused >> by non-uniform PTE entries distribution in the hash table. > > Have you tried increasing the size of the hash table ? That is a simple > workaround. As you may have seen, there is no facility for overflow of > the secondary hash bucket: that is something that could be added. > Yes. We have already tried that. It helps, but the PTE usage distribution in PTEG table is still non-uniform. For normal PTEG table size the secondary hash bucket hits PTEGs that are already filled by the primary hash bucket and then we get a panic. >> Unfortunately we still have problems with the system. We experience >> random processes crashes when the system is starting. It happens >> approximately once for 20 boots. If the system does not crash at the >> startup, everything works fine. We do not know where to look for the >> solution: pmap? vm? > > Is it a hang ? A panic ? If the latter, do you have a console trace ? > It's a panic. I've attached three example backtraces from sh, tail and pkill. They have all appeared during the boot process. We have many more core dumps from various system tools, but they are all similar to these. Suddenly a pointer points to 0x0 or an index in a table is invalid. Maybe something in the kernel overwrites user pages or maps a wrong page for a process? We have also tried some tricks with in pmap.c. There is a variable witch is initialized with timebase register values and used to make VSID values more random. As our problem seems to be random and the booting process is rather deterministic, we have initialized the entropy with a constant value to check if it would have an impact on our problem. The first chosen value 0x12345678 didn't help, but 0x35913521chosen at random seems to help (we do not observe any crashed at boot, but we still haven't tried any long runs). Never the less, we haven't found the heart of this problem and we hardly have a clue where to look. We have been wondering if anybody else had expierienced similar program crashes. Ps. I'm not sure if my last e-mail reached your server, so i'm sending it once again. Please don't treat it as spam. Kind Regards, Marcin Ligenza -------------- next part -------------- A non-text attachment was scrubbed... Name: 225.tail.core.bt Type: application/octet-stream Size: 1267 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20080710/932b7c9c/225.tail.core.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: 371.sh.core.bt Type: application/octet-stream Size: 4181 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20080710/932b7c9c/371.sh.core.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: 467.pkill.core Type: application/octet-stream Size: 3553 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ppc/attachments/20080710/932b7c9c/467.pkill.obj From raj at semihalf.com Thu Jul 10 15:31:31 2008 From: raj at semihalf.com (Rafal Jaworowski) Date: Thu Jul 10 15:31:38 2008 Subject: Porting FreeBSD to PPC In-Reply-To: <623735.31011.qm@web45811.mail.sp1.yahoo.com> References: <623735.31011.qm@web45811.mail.sp1.yahoo.com> Message-ID: <48762B49.7010800@semihalf.com> Won De Erick wrote: > thanks. Is U-boot an open source? When porting, what are the things that I need to know. I can't see detailed tutorials on the internet. > Hope for your support! I had a look and it seems U-Boot doesn't have a dedicated configuration for the ML403 board yet, although some people mentioned a successful attempts to use the one for ML300. You basically need to download U-Boot and first make it run on the ML403 (which might require some work on its own). After this initial stage, enable U-Boot API (add #define CONFIG_API to the board's config) and have FreeBSD loader run on top of U-Boot; only after this the proper kernel work would start.. Rafal From raj at semihalf.com Thu Jul 10 15:34:30 2008 From: raj at semihalf.com (Rafal Jaworowski) Date: Thu Jul 10 15:34:36 2008 Subject: Porting FreeBSD to PPC In-Reply-To: <677262.66173.qm@web45815.mail.sp1.yahoo.com> References: <677262.66173.qm@web45815.mail.sp1.yahoo.com> Message-ID: <48762C04.6060608@semihalf.com> Won De Erick wrote: > > Is PowerPC loader(8) an open source? Can you point to me where I could have the codes? Sure, the loader(8) is bundled as part of the FreeBSD system. You can review the sources here: - http://fxr.watson.org/fxr/source/boot/powerpc/uboot/ - http://fxr.watson.org/fxr/source/boot/uboot/ Rafal From grehan at freebsd.org Thu Jul 10 15:39:55 2008 From: grehan at freebsd.org (Peter Grehan) Date: Thu Jul 10 15:40:01 2008 Subject: FreeBSD on MPC8349 (e300 core) In-Reply-To: <4884777a784ee096.4875f596@comp.waw.pl> References: <4884777a784ee096.4875f596@comp.waw.pl> Message-ID: <48762D45.7050405@freebsd.org> Hi Marek, > the PTE usage distribution in PTEG table is still non-uniform. For > normal PTEG table size the secondary hash bucket hits PTEGs that are > already filled by the primary hash bucket and then we get a panic. The G3/G4 pmap code has been stable for a while now. The fact that it took a number of years to find the pteg secondary-hash index issue indicated that the hash was working well and spreading entries well enough that the primary buckets were rarely overflowing. One avenue to look into is to make sure your TLB miss handler is functionally correct. If it's generating an incorrect value (or even a poor hash), that may result in entries not being spread well enough. > It's a panic. I've attached three example backtraces from sh, tail > and pkill. They have all appeared during the boot process. We have > many more core dumps from various system tools, but they are all > similar to these. Suddenly a pointer points to 0x0 or an index in a > table is invalid. Maybe something in the kernel overwrites user pages > or maps a wrong page for a process? One way to debug these type of problems is to put some code in the kernel's trap handler to validate the virt/phys translation that caused the problem is the same as that described in the faulting process's vm data structures. later, Peter. From won.derick at yahoo.com Thu Jul 10 23:14:30 2008 From: won.derick at yahoo.com (Won De Erick) Date: Thu Jul 10 23:15:06 2008 Subject: Porting FreeBSD to PPC Message-ID: <353200.26634.qm@web45812.mail.sp1.yahoo.com> Hi Rafal, Thanks for the tip. How the configuration on the board? I would like to know also the different things that I must do to properly configure the FPGA. Are the Xilinx integrated IPs in the XPS enough for this matter? Thanks, Won ----- Original Message ---- From: Rafal Jaworowski To: Won De Erick Cc: grehan@freebsd.org; freebsd-ppc@freebsd.org Sent: Thursday, July 10, 2008 11:31:21 PM Subject: Re: Porting FreeBSD to PPC Won De Erick wrote: > thanks. Is U-boot an open source? When porting, what are the things that I need to know. I can't see detailed tutorials on the internet. > Hope for your support! I had a look and it seems U-Boot doesn't have a dedicated configuration for the ML403 board yet, although some people mentioned a successful attempts to use the one for ML300. You basically need to download U-Boot and first make it run on the ML403 (which might require some work on its own). After this initial stage, enable U-Boot API (add #define CONFIG_API to the board's config) and have FreeBSD loader run on top of U-Boot; only after this the proper kernel work would start.. Rafal From won.derick at yahoo.com Sat Jul 12 03:21:45 2008 From: won.derick at yahoo.com (Won De Erick) Date: Sat Jul 12 03:21:52 2008 Subject: Porting FreeBSD to PPC Message-ID: <956056.86031.qm@web45809.mail.sp1.yahoo.com> Thank you for this info. I finally got a ML403 board for me. My problem is, is it necessary to compile or build the FreeBSD kernel with the Xilinx tool? How should I go about this? The Xilinx XPS is specific on some smaller systems (like the built-in standalone, vxworks, linux). ----- Original Message ---- From: Wojciech A. Koszek To: Rafal Jaworowski Cc: Won De Erick Sent: Friday, July 11, 2008 6:06:21 PM Subject: Re: Porting FreeBSD to PPC On Fri, Jul 11, 2008 at 09:50:15AM +0200, Rafal Jaworowski wrote: > Wojciech A. Koszek wrote: > >>> thanks. Is U-boot an open source? When porting, what are the things that I need to know. I can't see detailed tutorials on the internet. > >>> Hope for your support! > >> I had a look and it seems U-Boot doesn't have a dedicated configuration for > >> the ML403 board yet, although some people mentioned a successful attempts to > >> use the one for ML300. > > [..] > > > > The closest possible is probably: > > > > u-boot/board/xilinx/ml401/ > > > > Are you sure ML401 is really PPC and not Microblaze? > > The ML300 that I mentioned is PPC405 and I think this was the reason why > people used this on ML403... You're right. ML401 comes with different Virtex than I thought.. Sorry for misleading. -- Wojciech A. Koszek wkoszek@FreeBSD.org http://people.freebsd.org/~wkoszek/ From bugmaster at FreeBSD.org Mon Jul 14 11:07:03 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jul 14 11:08:34 2008 Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org Message-ID: <200807141107.m6EB73oE014512@freefall.freebsd.org> Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o power/93203 ppc FreeBSD PPC Can't Write to Partitions. a power/121407 ppc [panic] Won't boot up; strange error message. 2 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o power/111296 ppc [kernel] [patch] [request] Support IMISS, DLMISS an DS o power/112435 ppc [nexus] [patch] Update nexus children to use ofw_bus f 2 problems total. From lizeqiang at gmail.com Mon Jul 14 12:31:58 2008 From: lizeqiang at gmail.com (=?GB2312?B?wO7Hvw==?=) Date: Mon Jul 14 13:53:19 2008 Subject: About install freebsd on ibook g4(2005) Message-ID: <703e09cb0807140506y30572b94j41a21b0e86c2e2a7@mail.gmail.com> Hi, I try to install freeebsd on my Ibook ,but last time it can't recognize the inner keyboard (can't remember 6.0 or 7.0) . I'd like to know the inner keyboard on ibook problem is solved at version 7.0 or 8.0. And is there a release note for install on powerpc or ibook? Thanks. Li Qiang From zielonka.markus at googlemail.com Tue Jul 15 12:01:01 2008 From: zielonka.markus at googlemail.com (Markus Zielonka) Date: Tue Jul 15 12:01:07 2008 Subject: Question iBook G3 Message-ID: <4be23f950807150432m7b6867c3p403e4c6061d8fa65@mail.gmail.com> Hello FreeBSD ppc User, my old good iBook run with MAC OS X 10.2. More Info about my iBook here: http://forum.ubuntuusers.de/topic/187227/ I search with Google for a wiki or tutorial about a good installation documantion. > I found only this: http://lists.freebsd.org/pipermail/freebsd-ppc/2008-July/002912.html Have some a good link for me? Thanks for help. Bye Markus -- Markus Zielonka Germany Tel.: +49(0)32 224040302 Fax.: +49(0)1805 06034504323 Jabber: airjump@jabber.org Blog: http://goto-zille.blogspot.com From nathanw at uchicago.edu Fri Jul 18 16:24:52 2008 From: nathanw at uchicago.edu (Nathan Whitehorn) Date: Fri Jul 18 16:24:59 2008 Subject: About install freebsd on ibook g4(2005) In-Reply-To: <703e09cb0807140506y30572b94j41a21b0e86c2e2a7@mail.gmail.com> References: <703e09cb0807140506y30572b94j41a21b0e86c2e2a7@mail.gmail.com> Message-ID: <4880B638.4060306@uchicago.edu> ?? wrote: > Hi, > I try to install freeebsd on my Ibook ,but last time it can't > recognize the inner keyboard (can't remember 6.0 or 7.0) . I'd like to > know the inner keyboard on ibook problem is solved at version 7.0 or > 8.0. And is there a release note for install on powerpc or ibook? There is still no support for the built-in keyboard on PowerPC laptops. I've started work on ADB support, which now works on some older machines, and Peter Grehan was working on a module to let it run on later laptops, so this support should be available in the next few months. For now, though, you will be stuck with an external USB keyboard. -Nathan From nwhitehorn at freebsd.org Sat Jul 19 21:17:14 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Sat Jul 19 21:17:44 2008 Subject: Single user mode on G5! Message-ID: <48824C5A.2010805@freebsd.org> Patches at http://banshee.uchicago.edu/~nwhitehorn/g5.diff. Beware that kernels with INVARIANTS enabled do not run on G5s because of some issues writing to the console in early boot and that the patch breaks building loader, and thus world. These should be easy to fix, and will be fixed once the system is working. A failed attempt to start multi-user is listed below -- remounting / read-write causes a panic for some reason that is not currently clear to me. A kernel built with G5 support should work fine on G3/G4 machines (tested on a G3). The patches also change a few things that may affect Book-E systems; I'd appreciate comments from people with such hardware. -Nathan Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.0-CURRENT #724: Sat Jul 19 15:01:10 CDT 2008 root@trantor.tachypleus.net:/usr/obj/powerpc/usr/src/sys/CETO cpu0: IBM PowerPC 970FX revision 3.0 cpu0: HID0 4 real memory = 790847488 (754 MB) avail memory = 740294656 (706 MB) kbd0 at kbdmux0 nexus0: powermac_nvram0: on nexus0 powermac_nvram0: both banks appear to be corrupt device_attach: powermac_nvram0 attach returned 6 pcib0: on nexus0 pci0: on pcib0 vgapci0: mem 0x91000000-0x91ffffff,0xa0000000-0xa7ffffff irq 59 at device 16.0 on pci0 cpcht0: on nexus0 pcib1: on cpcht0 pci1: on pcib1 gem0: mem 0x80400000-0x805fffff irq 40 at device 15.0 on pci1 miibus0: on gem0 bmtphy0: PHY 0 on miibus0 bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto gem0: 10kB RX FIFO, 4kB TX FIFO gem0: Ethernet address: 00:0d:93:48:c2:86 gem0: [ITHREAD] pcib2: on cpcht0 pci2: on pcib2 pci2: at device 1.0 (no driver attached) macio0: mem 0x80000000-0x8007ffff at device 7.0 on pci2 openpic0: mem 0x40000-0x7ffff on macio0 scc0: mem 0x13000-0x13fff,0x8400-0x84ff,0x8500-0x 85ff,0x8600-0x86ff,0x8700-0x87ff irq 23,17,18,24,19,20 on macio0 scc0: [FILTER] scc0: [FILTER] uart0: on scc0 uart0: [FILTER] uart1: on scc0 uart1: [FILTER] ohci0: mem 0x80082000-0x80082fff irq 70 at device 11.0 on pci2 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0 usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0x80081000-0x80081fff irq 70 at device 11.1 on pci2 ohci1: [GIANT-LOCKED] ohci1: [ITHREAD] usb1: OHCI version 1.0 usb1: on ohci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered ehci0: mem 0x80080000-0x800800ff irq 70 at device 11.2 on pci2 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb2: EHCI version 1.0 usb2: companion controllers, 3 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: on usb2 uhub2: 5 ports with 5 removable, self powered pcib3: on cpcht0 pci3: on pcib3 atapci0: mem 0x80102000-0x80103fff at device 12.0 on pci3 atapci0: unable to map interrupt device_attach: atapci0 attach returned 6 pci3: at device 13.0 (no driver attached) fwohci0: <1394 Open Host Controller Interface> mem 0x80100000-0x80100fff irq 39 at device 14.0 on pci3 fwohci0: [FILTER] fwohci0: OHCI version 1.0 (ROM=0) fwohci0: No. of Isochronous channels is 8. fwohci0: EUI64 00:0d:93:ff:fe:48:c2:86 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:0d:93:48:c2:86 fwe0: Ethernet address: 02:0d:93:48:c2:86 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0x1db4000 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0x8800ffc0, gen=2, non CYCLEMASTER mode sc0: on nexus0 sc0: Unknown <16 virtual consoles, flags=0x300> uhub3: on uhub1 uhub3: 3 ports with 2 removable, bus powered ukbd0: on uhub3 kbd1 at ukbd0 uhid0: on uhub3 Timecounter "decrementer" frequency 33333333 Hz quality 0 Timecounters tick every 10.000 msec firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 Trying to mount root from nfs:trantor:/tank/powerpc NFS ROOT: 10.0.1.100:/tank/powerpc gem0: link state changed to UP firewire0: New S400 device ID:0011066645555bf7 Interface gem0 IP-Address 10.0.1.99 Broadcast 10.0.1.255 Loading configuration files. No suitable dump device was found. Entropy harvesting: interrupts ethernet point_to_point kickstart. Starting file system checks: mount_nfs: can't update /var/db/mounttab for trantor:/tank/powerpc fatal kernel trap: exception = 0x3 (data storage interrupt) virtual address = 0x18159d0 srr0 = 0x310548 srr1 = 0x9032 lr = 0x4147ac curthread = 0xd14f8d20 pid = 73, comm = mount_nfs [thread pid 73 tid 100040 ] Stopped at 0x310548: lbz r0, r3, 0x0 db> bt Tracing pid 73 tid 100040 td 0xd14f8d20 0xe219f980: at nfs_decode_args+0x638 0xe219f9b0: at nfs_mount+0x124 0xe219fae0: at vfs_donmount+0x1320 0xe219fca0: at nmount+0xd8 0xe219fce0: at trap+0x45c 0xe219fda0: at powerpc_interrupt+0x11c 0xe219fdd0: user SC trap by 0x218a6408: srr1=0xd032 r1=0x7fffd8c0 cr=0x24000084 xer=0 ctr=0x218a6400 db> From bugmaster at FreeBSD.org Mon Jul 21 11:07:01 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jul 21 11:08:28 2008 Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org Message-ID: <200807211107.m6LB704f031967@freefall.freebsd.org> Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o power/93203 ppc FreeBSD PPC Can't Write to Partitions. a power/121407 ppc [panic] Won't boot up; strange error message. 2 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o power/111296 ppc [kernel] [patch] [request] Support IMISS, DLMISS an DS o power/112435 ppc [nexus] [patch] Update nexus children to use ofw_bus f 2 problems total. From raj at semihalf.com Mon Jul 21 12:30:00 2008 From: raj at semihalf.com (Rafal Jaworowski) Date: Mon Jul 21 12:30:07 2008 Subject: Single user mode on G5! In-Reply-To: <48824C5A.2010805@freebsd.org> References: <48824C5A.2010805@freebsd.org> Message-ID: <48848144.5040609@semihalf.com> Nathan Whitehorn wrote: > Patches at http://banshee.uchicago.edu/~nwhitehorn/g5.diff. Beware that > kernels with INVARIANTS enabled do not run on G5s because of some issues > writing to the console in early boot and that the patch breaks building > loader, and thus world. These should be easy to fix, and will be fixed > once the system is working. Fantastic news, congratulations! I have one very general comment regarding naming scheme, which isn't even strictly related to your G5 work but the existing G3/4 port too. There is the 'OEA' prefix used, which came from NetBSD, but it seems rather unfortunate to me: Operating Environment Architecure is a generic term for certain layer in PowerPC definition nomenclature, and each implementation variant of the CPU has actually its own OEA defined... I think it would be better to change it to something more meaningful. Rafal From nwhitehorn at freebsd.org Mon Jul 21 15:43:04 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Mon Jul 21 15:43:10 2008 Subject: Single user mode on G5! In-Reply-To: <48848144.5040609@semihalf.com> References: <48824C5A.2010805@freebsd.org> <48848144.5040609@semihalf.com> Message-ID: <4884A7A6.9050806@freebsd.org> Rafal Jaworowski wrote: > Nathan Whitehorn wrote: > >> Patches at http://banshee.uchicago.edu/~nwhitehorn/g5.diff. Beware that >> kernels with INVARIANTS enabled do not run on G5s because of some issues >> writing to the console in early boot and that the patch breaks building >> loader, and thus world. These should be easy to fix, and will be fixed >> once the system is working. >> > > Fantastic news, congratulations! > > I have one very general comment regarding naming scheme, which isn't even > strictly related to your G5 work but the existing G3/4 port too. There is the > 'OEA' prefix used, which came from NetBSD, but it seems rather unfortunate to > me: Operating Environment Architecure is a generic term for certain layer in > PowerPC definition nomenclature, and each implementation variant of the CPU > has actually its own OEA defined... I think it would be better to change it to > something more meaningful. > > Rafal > How about aim(64)? It's the name of the directory for the Book-S support anyway. We should probably also start thinking about a full 64-bit port soon. With support for the 64-bit MMU stuff required for bridge mode, we should end up with a lot of shared code. -Nathan From nwhitehorn at freebsd.org Mon Jul 21 23:08:32 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Mon Jul 21 23:08:38 2008 Subject: G5 boots multi-user! Message-ID: <4885176C.8000206@freebsd.org> There appears to be a bug in NFS not using using copyin() to get the hostname from its arguments when a mount is being updating. Fixing that with an #if 0 sledgehammer produces the following patch: http://people.freebsd.org/~nwhitehorn/nfs_vfsops.diff Combine that with the main G5 patch: http://people.freebsd.org/~nwhitehorn/g5.diff This produces a system that will boot multiuser on my iMac G5. It still has plenty of bugs, to whit: 1) The system is extremely slow. Measured CPU clock speed is 50 MHz, which is about what it feels like. I think it is in a low-power mode, but IBM docs say it can only run at 1800 and 900 MHz. So this is probably an inefficiency in the MMU module. 2) There remain several nasty panics. The system is not especially stable yet. -Nathan From tinderbox at freebsd.org Tue Jul 22 03:08:49 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Jul 22 03:08:55 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20080722030846.9F01273039@freebsd-current.sentex.ca> TB --- 2008-07-22 01:52:32 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-07-22 01:52:32 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-07-22 01:52:32 - cleaning the object tree TB --- 2008-07-22 01:52:59 - cvsupping the source tree TB --- 2008-07-22 01:52:59 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-07-22 01:53:08 - building world (CFLAGS=-O -pipe) TB --- 2008-07-22 01:53:08 - cd /src TB --- 2008-07-22 01:53:08 - /usr/bin/make -B buildworld >>> World build started on Tue Jul 22 01:53:10 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Tue Jul 22 03:02:40 UTC 2008 TB --- 2008-07-22 03:02:40 - generating LINT kernel config TB --- 2008-07-22 03:02:40 - cd /src/sys/powerpc/conf TB --- 2008-07-22 03:02:40 - /usr/bin/make -B LINT TB --- 2008-07-22 03:02:40 - building LINT kernel (COPTFLAGS=) TB --- 2008-07-22 03:02:40 - cd /src TB --- 2008-07-22 03:02:40 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Jul 22 03:02:40 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 -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/netinet/ip_id.c cc -c -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/netinet/in_mcast.c cc -c -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/netinet/in_pcb.c cc1: warnings being treated as errors /src/sys/netinet/in_pcb.c: In function 'inp_4tuple_get': /src/sys/netinet/in_pcb.c:1306: warning: passing argument 1 of '_rw_assert' discards qualifiers from pointer target type /src/sys/netinet/in_pcb.c:1307: error: incompatible types in assignment /src/sys/netinet/in_pcb.c:1308: error: incompatible types in assignment *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-07-22 03:08:46 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-07-22 03:08:46 - ERROR: failed to build lint kernel TB --- 2008-07-22 03:08:46 - tinderbox aborted TB --- 3343.91 user 402.12 system 4574.12 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From yanefbsd at gmail.com Tue Jul 22 06:13:42 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Tue Jul 22 06:13:49 2008 Subject: G5 boots multi-user! In-Reply-To: <4885176C.8000206@freebsd.org> References: <4885176C.8000206@freebsd.org> Message-ID: <7d6fde3d0807212313j73919327s3e8c8fdb9ef56a01@mail.gmail.com> On Mon, Jul 21, 2008 at 4:10 PM, Nathan Whitehorn wrote: > There appears to be a bug in NFS not using using copyin() to get the > hostname from its arguments when a mount is being updating. Fixing that with > an #if 0 sledgehammer produces the following patch: > > http://people.freebsd.org/~nwhitehorn/nfs_vfsops.diff > > Combine that with the main G5 patch: > > http://people.freebsd.org/~nwhitehorn/g5.diff > > This produces a system that will boot multiuser on my iMac G5. It still has > plenty of bugs, to whit: > > 1) The system is extremely slow. Measured CPU clock speed is 50 MHz, which > is about what it feels like. I think it is in a low-power mode, but IBM docs > say it can only run at 1800 and 900 MHz. So this is probably an inefficiency > in the MMU module. > > 2) There remain several nasty panics. The system is not especially stable > yet. > -Nathan Nathan, Let me know if / when you need to test out some changes on a Powermac G5 UP system. Cheers, -Garrett From raj at semihalf.com Tue Jul 22 12:29:12 2008 From: raj at semihalf.com (Rafal Jaworowski) Date: Tue Jul 22 12:29:18 2008 Subject: Single user mode on G5! In-Reply-To: <4884A7A6.9050806@freebsd.org> References: <48824C5A.2010805@freebsd.org> <48848144.5040609@semihalf.com> <4884A7A6.9050806@freebsd.org> Message-ID: <4885D290.20406@semihalf.com> >> I have one very general comment regarding naming scheme, which isn't even >> strictly related to your G5 work but the existing G3/4 port too. There >> is the >> 'OEA' prefix used, which came from NetBSD, but it seems rather >> unfortunate to >> me: Operating Environment Architecure is a generic term for certain >> layer in >> PowerPC definition nomenclature, and each implementation variant of >> the CPU >> has actually its own OEA defined... I think it would be better to >> change it to >> something more meaningful. >> >> Rafal >> > How about aim(64)? It's the name of the directory for the Book-S support > anyway. We should probably also start thinking about a full 64-bit port > soon. With support for the 64-bit MMU stuff required for bridge mode, we > should end up with a lot of shared code. Sounds good. Rafal From nse at delfi-konsult.com Tue Jul 22 13:32:24 2008 From: nse at delfi-konsult.com (Niels S. Eliasen) Date: Tue Jul 22 13:32:30 2008 Subject: gtk2 compilation error... Message-ID: <0BD193D4-542E-45F3-81F3-C40231534F36@delfi-konsult.com> Hi guys Anyone knows how to fix this ?? > creating gtk-update-icon-cache > gmake[3]: Leaving directory `/usr/ports/x11-toolkits/gtk20/work/gtk > +-2.12.11/gtk > ' > GDK_PIXBUF_MODULE_FILE=../gdk-pixbuf/gdk-pixbuf.loaders ./gtk- > update-icon-cache > --force --ignore-theme-index \ > --source builtin_icons stock-icons > > gtkbuiltincache.h.tmp && > \ > mv gtkbuiltincache.h.tmp gtkbuiltincache.h > gtk-update-icon-cache: The generated cache was invalid. > gmake[2]: *** [gtkbuiltincache.h] Error 1 > gmake[2]: Leaving directory `/usr/ports/x11-toolkits/gtk20/work/gtk > +-2.12.11/gtk > ' > gmake[1]: *** [all-recursive] Error 1 > gmake[1]: Leaving directory `/usr/ports/x11-toolkits/gtk20/work/gtk > +-2.12.11' > gmake: *** [all] Error 2 > *** Error code 2 > > Stop in /usr/ports/x11-toolkits/gtk20. > regards niels From tinderbox at freebsd.org Tue Jul 22 14:53:13 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Jul 22 14:53:30 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20080722145310.19E5C73039@freebsd-current.sentex.ca> TB --- 2008-07-22 14:52:36 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-07-22 14:52:36 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-07-22 14:52:36 - cleaning the object tree TB --- 2008-07-22 14:53:02 - cvsupping the source tree TB --- 2008-07-22 14:53:02 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-07-22 14:53:09 - building world (CFLAGS=-O -pipe) TB --- 2008-07-22 14:53:09 - cd /src TB --- 2008-07-22 14:53:09 - /usr/bin/make -B buildworld TB --- 2008-07-22 14:53:09 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-07-22 14:53:09 - ERROR: failed to build world TB --- 2008-07-22 14:53:09 - tinderbox aborted TB --- 2.15 user 3.09 system 33.89 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From nwhitehorn at freebsd.org Tue Jul 22 23:23:39 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Tue Jul 22 23:23:45 2008 Subject: G5 boots multi-user! In-Reply-To: <4885176C.8000206@freebsd.org> References: <4885176C.8000206@freebsd.org> Message-ID: <48866C90.2010800@freebsd.org> I've fixed the crashing bugs and some issues with TLB invalidation, and my G5 now runs stably. I can build ports, etc., and it is reasonably fast. Updated patch here: http://people.freebsd.org/~nwhitehorn/g5.diff Known bugs: 1. World builds are broken due to changes to CACHELINESIZE, so build world first. 2. ATA controller does not work on my iMac because of a bug with the controller's interrupt property. 3. The patch touches some things it shouldn't in the MI UMA allocator that require a better solution. Seems mostly harmless, though. 4. The patch touches some things it shouldn't in the NFS client to fix the bug mentioned in my last email. This breaks NFS locking. 5. No thermal or fan control. 6. No SMP. 7. CPC 945 (PCI Express) systems are untested. 8. /dev/mem does not work, so no X. Aside from that, any single CPU G5 machine with AGP (single CPU Powermac G5s and iMacs) should work without noticeable problems aside from the broken NFS locking. Please let me know if this isn't true. -Nathan From tinderbox at freebsd.org Wed Jul 23 16:05:51 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Wed Jul 23 16:05:57 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20080723160548.CA4E073039@freebsd-current.sentex.ca> TB --- 2008-07-23 15:06:05 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-07-23 15:06:05 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-07-23 15:06:06 - cleaning the object tree TB --- 2008-07-23 15:06:33 - cvsupping the source tree TB --- 2008-07-23 15:06:33 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-07-23 15:06:41 - building world (CFLAGS=-O -pipe) TB --- 2008-07-23 15:06:41 - cd /src TB --- 2008-07-23 15:06:41 - /usr/bin/make -B buildworld >>> World build started on Wed Jul 23 15:06:44 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 [...] In file included from /src/sbin/ipf/ipresend/../../../contrib/ipfilter/ipsend/sock.c:81: /obj/powerpc/src/tmp/usr/include/string.h:81: error: conflicting types for 'strdup' /src/sbin/ipf/ipresend/../../../sys/sys/libkern.h:109: error: previous declaration of 'strdup' was here In file included from /src/sbin/ipf/ipresend/../../../contrib/ipfilter/ipsend/sock.c:82: /obj/powerpc/src/tmp/usr/include/stdlib.h:163: error: conflicting types for 'setenv' /src/sbin/ipf/ipresend/../../../sys/sys/systm.h:239: error: previous declaration of 'setenv' was here /obj/powerpc/src/tmp/usr/include/stdlib.h:201: error: conflicting types for 'random' /src/sbin/ipf/ipresend/../../../sys/sys/libkern.h:99: error: previous declaration of 'random' was here *** Error code 1 Stop in /src/sbin/ipf/ipresend. *** Error code 1 Stop in /src/sbin/ipf. *** Error code 1 Stop in /src/sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-07-23 16:05:48 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-07-23 16:05:48 - ERROR: failed to build world TB --- 2008-07-23 16:05:48 - tinderbox aborted TB --- 2623.82 user 321.73 system 3582.79 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From gad at FreeBSD.org Wed Jul 23 19:02:03 2008 From: gad at FreeBSD.org (Garance A Drosehn) Date: Wed Jul 23 19:02:10 2008 Subject: G5 boots multi-user! In-Reply-To: <48866C90.2010800@freebsd.org> References: <4885176C.8000206@freebsd.org> <48866C90.2010800@freebsd.org> Message-ID: At 6:26 PM -0500 7/22/08, Nathan Whitehorn wrote: >I've fixed the crashing bugs and some issues with TLB invalidation, >and my G5 now runs stably. I can build ports, etc., and it is >reasonably fast. Updated patch here: > >http://people.freebsd.org/~nwhitehorn/g5.diff > >Known bugs: >1. World builds are broken due to changes to CACHELINESIZE, > so build world first. I don't understand what you mean by this... Or does this mean one has to do a cross-build (from a different platform) for 'make buildworld'? >Aside from that, any single CPU G5 machine with AGP (single CPU >Powermac G5s and iMacs) should work without noticeable problems >aside from the broken NFS locking. Please let me know if this isn't >true. I can't easily test this right now, but this is very encouraging progress! The guy down the hall from me will probably be unhappy though. I was going to give him my old G5, but if FreeBSD runs on that then I'd much rather use that than my Mac mini! -- Garance Alistair Drosehn = drosehn@rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy, NY; USA From danfe at FreeBSD.org Wed Jul 23 19:05:30 2008 From: danfe at FreeBSD.org (Alexey Dokuchaev) Date: Wed Jul 23 19:05:37 2008 Subject: G5 boots multi-user! In-Reply-To: References: <4885176C.8000206@freebsd.org> <48866C90.2010800@freebsd.org> Message-ID: <20080723190530.GA32613@FreeBSD.org> On Wed, Jul 23, 2008 at 01:49:32PM -0400, Garance A Drosehn wrote: > At 6:26 PM -0500 7/22/08, Nathan Whitehorn wrote: > >Aside from that, any single CPU G5 machine with AGP (single CPU > >Powermac G5s and iMacs) should work without noticeable problems > >aside from the broken NFS locking. Please let me know if this isn't > >true. > > I can't easily test this right now, but this is very encouraging > progress! The guy down the hall from me will probably be unhappy > though. I was going to give him my old G5, but if FreeBSD runs > on that then I'd much rather use that than my Mac mini! Hahaha, now this is pretty funny. :-) ./danfe From nwhitehorn at freebsd.org Wed Jul 23 19:14:43 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Wed Jul 23 19:15:05 2008 Subject: G5 boots multi-user! In-Reply-To: References: <4885176C.8000206@freebsd.org> <48866C90.2010800@freebsd.org> Message-ID: <4887831E.2000806@freebsd.org> Garance A Drosehn wrote: > At 6:26 PM -0500 7/22/08, Nathan Whitehorn wrote: >> I've fixed the crashing bugs and some issues with TLB invalidation, >> and my G5 now runs stably. I can build ports, etc., and it is >> reasonably fast. Updated patch here: >> >> http://people.freebsd.org/~nwhitehorn/g5.diff >> >> Known bugs: >> 1. World builds are broken due to changes to CACHELINESIZE, >> so build world first. > > I don't understand what you mean by this... Or does this mean one has > to do a cross-build (from a different platform) for 'make buildworld'? You just have to have built a world before applying the patch, since loader wants CACHELINESIZE defined for standalone executables, and it varies depending on CPU model. Any PowerPC world that was built without applying the patch will work fine on G5. >> Aside from that, any single CPU G5 machine with AGP (single CPU >> Powermac G5s and iMacs) should work without noticeable problems aside >> from the broken NFS locking. Please let me know if this isn't true. > > I can't easily test this right now, but this is very encouraging > progress! The guy down the hall from me will probably be unhappy > though. I was going to give him my old G5, but if FreeBSD runs > on that then I'd much rather use that than my Mac mini! Oh well :P Assuming it's a dual-CPU machine, it will take a little more time before that is supported at all, and any G5 will be very loud because we don't have fan control yet. It will also be a while until X is supported because we no longer have a direct physical memory mappping. I'm going to have a stab at SMP support before the week is out. -Nathan From imp at bsdimp.com Wed Jul 23 22:49:56 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Wed Jul 23 22:50:03 2008 Subject: Device trees Message-ID: <20080723.164741.163264646.imp@bsdimp.com> Does FreeBSD/powerpc on the MPC85xx machine use the fake device open firmware tree stuff from uboot (aka dts in the linux kernel sources)? Warner From benno at jeamland.net Wed Jul 23 23:42:25 2008 From: benno at jeamland.net (Benno Rice) Date: Wed Jul 23 23:42:32 2008 Subject: Device trees In-Reply-To: <20080723.164741.163264646.imp@bsdimp.com> References: <20080723.164741.163264646.imp@bsdimp.com> Message-ID: On 24/07/2008, at 8:47 AM, M. Warner Losh wrote: > Does FreeBSD/powerpc on the MPC85xx machine use the fake device open > firmware tree stuff from uboot (aka dts in the linux kernel sources)? I've got a machine (Mikrotik RouterBOARD 333, uses MPC8321) that has this. I've been working with one of the dtc developers to port their code over to FreeBSD. I'm trying to hide it underneath our existing OpenFirmware stuff. I've got a few more bugs to get out of it but I can probably send you some patches early next week... -- Benno Rice benno@jeamland.net From nwhitehorn at freebsd.org Thu Jul 24 01:25:05 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Thu Jul 24 01:25:11 2008 Subject: Device trees In-Reply-To: References: <20080723.164741.163264646.imp@bsdimp.com> Message-ID: <4887CC78.8040707@freebsd.org> Benno Rice wrote: > > On 24/07/2008, at 8:47 AM, M. Warner Losh wrote: > >> Does FreeBSD/powerpc on the MPC85xx machine use the fake device open >> firmware tree stuff from uboot (aka dts in the linux kernel sources)? > > I've got a machine (Mikrotik RouterBOARD 333, uses MPC8321) that has > this. I've been working with one of the dtc developers to port their > code over to FreeBSD. I'm trying to hide it underneath our existing > OpenFirmware stuff. I've got a few more bugs to get out of it but I can > probably send you some patches early next week... > Can you use this to abstract real OF too? We don't support real mode Open Firmware and IBM is shipping new systems with a very basic firmware that runs only in real mode (this includes the Bimini 970MP dev board, apparently, as well as their Cell blades). The easiest course seems to be just to pretend it's a flattened device tree if we can support that. -Nathan From benno at jeamland.net Thu Jul 24 01:30:02 2008 From: benno at jeamland.net (Benno Rice) Date: Thu Jul 24 01:30:08 2008 Subject: Device trees In-Reply-To: <4887CC78.8040707@freebsd.org> References: <20080723.164741.163264646.imp@bsdimp.com> <4887CC78.8040707@freebsd.org> Message-ID: <3008B18B-DC6F-4E33-939E-169484B6EEFE@jeamland.net> On 24/07/2008, at 10:27 AM, Nathan Whitehorn wrote: > Benno Rice wrote: >> On 24/07/2008, at 8:47 AM, M. Warner Losh wrote: >>> Does FreeBSD/powerpc on the MPC85xx machine use the fake device open >>> firmware tree stuff from uboot (aka dts in the linux kernel >>> sources)? >> I've got a machine (Mikrotik RouterBOARD 333, uses MPC8321) that >> has this. I've been working with one of the dtc developers to port >> their code over to FreeBSD. I'm trying to hide it underneath our >> existing OpenFirmware stuff. I've got a few more bugs to get out >> of it but I can probably send you some patches early next week... > > > Can you use this to abstract real OF too? We don't support real mode > Open Firmware and IBM is shipping new systems with a very basic > firmware that runs only in real mode (this includes the Bimini 970MP > dev board, apparently, as well as their Cell blades). The easiest > course seems to be just to pretend it's a flattened device tree if > we can support that. My plan (assuming some measure of available time) was to actually get loader to handle turning OpenFirmware device data into an FDT which could be handed to FreeBSD as part of the loader metadata. On platforms like the Mikrotik where all we get is an FDT, if we have loader it can just pass it through or if we're not using loader we can have a hook that shunts the data into the right place. Does that sound workable? -- Benno Rice benno@jeamland.net From xcllnt at mac.com Thu Jul 24 02:19:30 2008 From: xcllnt at mac.com (Marcel Moolenaar) Date: Thu Jul 24 02:19:36 2008 Subject: Device trees In-Reply-To: <20080723.164741.163264646.imp@bsdimp.com> References: <20080723.164741.163264646.imp@bsdimp.com> Message-ID: <106CEF8A-EA8A-48BC-BAF7-B9C112F58A92@mac.com> On Jul 23, 2008, at 3:47 PM, M. Warner Losh wrote: > Does FreeBSD/powerpc on the MPC85xx machine use the fake device open > firmware tree stuff from uboot (aka dts in the linux kernel sources)? No, it doesn't. -- Marcel Moolenaar xcllnt@mac.com From imp at bsdimp.com Thu Jul 24 03:41:32 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Thu Jul 24 03:41:38 2008 Subject: Device trees In-Reply-To: References: <20080723.164741.163264646.imp@bsdimp.com> Message-ID: <20080723.213817.1661913390.imp@bsdimp.com> In message: Benno Rice writes: : : On 24/07/2008, at 8:47 AM, M. Warner Losh wrote: : : > Does FreeBSD/powerpc on the MPC85xx machine use the fake device open : > firmware tree stuff from uboot (aka dts in the linux kernel sources)? : : I've got a machine (Mikrotik RouterBOARD 333, uses MPC8321) that has : this. I've been working with one of the dtc developers to port their : code over to FreeBSD. Cool! : I'm trying to hide it underneath our existing : OpenFirmware stuff. I've got a few more bugs to get out of it but I : can probably send you some patches early next week... That's basically what Linux does. They force the boot loader to pass in all kinds of information about the system. This makes a lot of sense, I think. Are you booting /boot/loader? Or directly booting the kernel from uboot? In message: <106CEF8A-EA8A-48BC-BAF7-B9C112F58A92@mac.com> Marcel Moolenaar writes: : No, it doesn't. Is there any reason it doesn't? Having looked at the dtc stuff, it seems to have all the requirements of device enumeration that we talked about at BSDcan... Warner From benno at jeamland.net Thu Jul 24 03:59:12 2008 From: benno at jeamland.net (Benno Rice) Date: Thu Jul 24 03:59:19 2008 Subject: Device trees In-Reply-To: <20080723.213817.1661913390.imp@bsdimp.com> References: <20080723.164741.163264646.imp@bsdimp.com> <20080723.213817.1661913390.imp@bsdimp.com> Message-ID: <4C17792D-C96D-461C-A85A-BDF599CAD628@jeamland.net> On 24/07/2008, at 1:38 PM, M. Warner Losh wrote: > In message: > Benno Rice writes: > : > : On 24/07/2008, at 8:47 AM, M. Warner Losh wrote: > : > : > Does FreeBSD/powerpc on the MPC85xx machine use the fake device > open > : > firmware tree stuff from uboot (aka dts in the linux kernel > sources)? > : > : I've got a machine (Mikrotik RouterBOARD 333, uses MPC8321) that has > : this. I've been working with one of the dtc developers to port > their > : code over to FreeBSD. > > Cool! > > : I'm trying to hide it underneath our existing > : OpenFirmware stuff. I've got a few more bugs to get out of it but I > : can probably send you some patches early next week... > > That's basically what Linux does. They force the boot loader to pass > in all kinds of information about the system. This makes a lot of > sense, I think. > > Are you booting /boot/loader? Or directly booting the kernel from > uboot? s/uboot/RouterBOOT/ =) Directly booting. RouterBOOT supports netbooting but doesn't provide hooks that loader can use to do anything itself. It also only supports yaffs2 as a local boot filesystem. I'm going to look into porting yaffs2 at some point. The only thing RouterBOOT hands us is a pointer to a flattened device tree a-la what uboot hands to Linux so I need to be able to handle it to get things like memory sizes/locations, SoC base addresses and where the hell my console is. =) -- Benno Rice benno@jeamland.net From philip.s.schulz at googlemail.com Thu Jul 24 12:17:40 2008 From: philip.s.schulz at googlemail.com (Philip Schulz) Date: Thu Jul 24 12:17:46 2008 Subject: Device trees In-Reply-To: <20080723.213817.1661913390.imp@bsdimp.com> References: <20080723.164741.163264646.imp@bsdimp.com> <20080723.213817.1661913390.imp@bsdimp.com> Message-ID: <1c66db910807240451n5c181956rfe82b2ba4e80c5ae@mail.gmail.com> 2008/7/24 M. Warner Losh : > In message: > Benno Rice writes: > : > : On 24/07/2008, at 8:47 AM, M. Warner Losh wrote: > : > : > Does FreeBSD/powerpc on the MPC85xx machine use the fake device open > : > firmware tree stuff from uboot (aka dts in the linux kernel sources)? > : > : I've got a machine (Mikrotik RouterBOARD 333, uses MPC8321) that has > : this. I've been working with one of the dtc developers to port their > : code over to FreeBSD. > > Cool! > > : I'm trying to hide it underneath our existing > : OpenFirmware stuff. I've got a few more bugs to get out of it but I > : can probably send you some patches early next week... > > That's basically what Linux does. They force the boot loader to pass > in all kinds of information about the system. This makes a lot of > sense, I think. > Unless I misunderstood what you guys said, I think it should be done the other way around. It's my understanding that Linux always uses the FDT internally. If it finds that it's being booted from a full Open Firmware implementation with device tree, it will first parse the device tree and convert it to an FDT. That way, Linux doesn't have to do any client interface calls once it's past the device tree parsing stage. I think that's good, see below. > Are you booting /boot/loader? Or directly booting the kernel from > uboot? > > In message: <106CEF8A-EA8A-48BC-BAF7-B9C112F58A92@mac.com> > Marcel Moolenaar writes: > : No, it doesn't. > > Is there any reason it doesn't? Having looked at the dtc stuff, it > seems to have all the requirements of device enumeration that we > talked about at BSDcan... > Don't know what happened at BSDcan, but... Since the FDT encodes pretty much all information the full device tree does, but doesn't provide the methods, I don't see a problem with device enumeration in FreeBSD. I.e. all devices that appear in the full device tree would also appear in the FDT, but you can't use their methods. So while this may be a problem for the FreeBSD loader, it certainly shouldn't be for the kernel. I personally think that the Linux design makes a lot of sense and I think that you should hide the real Open Firmware device tree behind the flattened device tree (FDT). From my point of view, doing so will prepare and strengthen FreeBSD on the embedded PowerPC front and also, as Nathan noted, simplify ports to other PowerPC-based platforms. Regards, Philip From raj at semihalf.com Thu Jul 24 13:00:09 2008 From: raj at semihalf.com (Rafal Jaworowski) Date: Thu Jul 24 13:00:15 2008 Subject: Device trees In-Reply-To: <20080723.213817.1661913390.imp@bsdimp.com> References: <20080723.164741.163264646.imp@bsdimp.com> <20080723.213817.1661913390.imp@bsdimp.com> Message-ID: <4888798B.2050903@semihalf.com> M. Warner Losh wrote: > In message: <106CEF8A-EA8A-48BC-BAF7-B9C112F58A92@mac.com> > Marcel Moolenaar writes: > : No, it doesn't. > > Is there any reason it doesn't? Having looked at the dtc stuff, it > seems to have all the requirements of device enumeration that we > talked about at BSDcan... At the time FreeBSD/MPC85xx was developed the flattened device tree concept was only getting momentum on Linux, so it was very much fluctuating. But the main reason was it's quite a bit of work to put everything together and it wasn't a critical item for the port. FDT is more or less what we discussed in May, and I think it was mentioned as one of the possible ways to go. Please note however the FDT infrastructure is quite heavy and getting it right needs to account for the non-code dependencies and elements too: - adopting external (GPL) tools, or providing our own - working out DTS layouts, OF bindings definitions and conventions (and their further maintenance) so that they can be used on architectures other that PowerPC (as having a modern device resources representation accross different architectures in FreeBSD was very important aspect of our discussions) Rafal From nwhitehorn at freebsd.org Thu Jul 24 16:45:08 2008 From: nwhitehorn at freebsd.org (Nathan Whitehorn) Date: Thu Jul 24 16:45:14 2008 Subject: Device trees In-Reply-To: <3008B18B-DC6F-4E33-939E-169484B6EEFE@jeamland.net> References: <20080723.164741.163264646.imp@bsdimp.com> <4887CC78.8040707@freebsd.org> <3008B18B-DC6F-4E33-939E-169484B6EEFE@jeamland.net> Message-ID: <4888AD0A.4020001@freebsd.org> Benno Rice wrote: > > On 24/07/2008, at 10:27 AM, Nathan Whitehorn wrote: > >> Benno Rice wrote: >>> On 24/07/2008, at 8:47 AM, M. Warner Losh wrote: >>>> Does FreeBSD/powerpc on the MPC85xx machine use the fake device open >>>> firmware tree stuff from uboot (aka dts in the linux kernel sources)? >>> I've got a machine (Mikrotik RouterBOARD 333, uses MPC8321) that has >>> this. I've been working with one of the dtc developers to port >>> their code over to FreeBSD. I'm trying to hide it underneath our >>> existing OpenFirmware stuff. I've got a few more bugs to get out of >>> it but I can probably send you some patches early next week... >> >> >> Can you use this to abstract real OF too? We don't support real mode >> Open Firmware and IBM is shipping new systems with a very basic >> firmware that runs only in real mode (this includes the Bimini 970MP >> dev board, apparently, as well as their Cell blades). The easiest >> course seems to be just to pretend it's a flattened device tree if we >> can support that. > > My plan (assuming some measure of available time) was to actually get > loader to handle turning OpenFirmware device data into an FDT which > could be handed to FreeBSD as part of the loader metadata. On > platforms like the Mikrotik where all we get is an FDT, if we have > loader it can just pass it through or if we're not using loader we can > have a hook that shunts the data into the right place. > > Does that sound workable? > It would be nice not to require loader at all and support direct loading of the kernel. We already support this, and it is handy on systems with low-featured firmware that doesn't allow loader to easily load more files. I think the best way forward is to support some kind of pluggable Open Firmware implementation. On systems with nonexistent/bad firmware, we can supply a fake interpreter with a very limited vocabulary to OF_init (I'm assuming this is what you are doing with the Microtik board) that either uses a passed-in FDT or generates one from the real-mode firmware early in the boot process. But I don't think we should turn everything into an FDT: we gain some real advantages on systems with decent firmware implementations from being able to use them, like RTC and power management support. It would be silly to throw that away and I believe the existing architecture is flexible enough to support runtime switching between implementations. Also, while I'm sending email to everyone, I'll give my apparently daily update on G5 support. We're self-hosting! This means that my patches (http://people.freebsd.org/~nwhitehorn/g5.diff, as before) fix building PPC world and that the system is now stable enough to build that world itself. The NFS bug has now been fixed in HEAD (thanks to dfr). You still can't build a kernel with INVARIANTS. -Nathan From benno at jeamland.net Thu Jul 24 23:20:56 2008 From: benno at jeamland.net (Benno Rice) Date: Thu Jul 24 23:21:03 2008 Subject: Device trees In-Reply-To: <4888798B.2050903@semihalf.com> References: <20080723.164741.163264646.imp@bsdimp.com> <20080723.213817.1661913390.imp@bsdimp.com> <4888798B.2050903@semihalf.com> Message-ID: <6618A7BB-08EA-4963-94B8-560F48DE29A3@jeamland.net> On 24/07/2008, at 10:46 PM, Rafal Jaworowski wrote: > M. Warner Losh wrote: >> In message: <106CEF8A-EA8A-48BC-BAF7-B9C112F58A92@mac.com> >> Marcel Moolenaar writes: >> : No, it doesn't. >> >> Is there any reason it doesn't? Having looked at the dtc stuff, it >> seems to have all the requirements of device enumeration that we >> talked about at BSDcan... > > At the time FreeBSD/MPC85xx was developed the flattened device tree > concept > was only getting momentum on Linux, so it was very much fluctuating. > But the > main reason was it's quite a bit of work to put everything together > and it > wasn't a critical item for the port. > > FDT is more or less what we discussed in May, and I think it was > mentioned as > one of the possible ways to go. Please note however the FDT > infrastructure is > quite heavy and getting it right needs to account for the non-code > dependencies and elements too: > > - adopting external (GPL) tools, or providing our own The libfdt part of dtc is dual licensed. One of the developers has also given me a lot of assistance in making it work in our kernel code. (I'm using it in some code I've got here) The userland parts are GPL but we can reimplement those if we really want. > - working out DTS layouts, OF bindings definitions and conventions > (and their > further maintenance) so that they can be used on architectures other > that > PowerPC (as having a modern device resources representation accross > different > architectures in FreeBSD was very important aspect of our discussions) We could open up a dialogue with the dtc developers if you think that'd help. My contact seemed very keen to have the code be used in FreeBSD. -- Benno Rice benno@jeamland.net From imp at bsdimp.com Fri Jul 25 06:26:48 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Fri Jul 25 06:26:57 2008 Subject: Device trees In-Reply-To: <48896F25.6060204@fang.fa.gau.hu> References: <4888798B.2050903@semihalf.com> <6618A7BB-08EA-4963-94B8-560F48DE29A3@jeamland.net> <48896F25.6060204@fang.fa.gau.hu> Message-ID: <20080725.002550.-1558769372.imp@bsdimp.com> In message: <48896F25.6060204@fang.fa.gau.hu> Peter Czanik writes: : Helo, : : Benno Rice ?rta: : >> - working out DTS layouts, OF bindings definitions and conventions : >> (and their : >> further maintenance) so that they can be used on architectures other : >> that : >> PowerPC (as having a modern device resources representation accross : >> different : >> architectures in FreeBSD was very important aspect of our discussions) : > : > We could open up a dialogue with the dtc developers if you think : > that'd help. My contact seemed very keen to have the code be used in : > FreeBSD. : The Linux guys just announced on the linuxppc-dev mailing list, that a : new device-tree specific mailing list was created. Please see : http://ozlabs.org/pipermail/linuxppc-dev/2008-July/060558.html Thanks! I think this would be totally cool. Having a standardized resource description language between Linux and FreeBSD would make it faster/easier to import board support from Linux into FreeBSD :-) Warner From pczanik at fang.fa.gau.hu Fri Jul 25 06:28:13 2008 From: pczanik at fang.fa.gau.hu (Peter Czanik) Date: Fri Jul 25 06:28:20 2008 Subject: Device trees In-Reply-To: <4888798B.2050903@semihalf.com> References: <20080723.164741.163264646.imp@bsdimp.com> <20080723.213817.1661913390.imp@bsdimp.com> <4888798B.2050903@semihalf.com> Message-ID: <48897005.6030400@fang.fa.gau.hu> Hello, Rafal Jaworowski ?rta: > At the time FreeBSD/MPC85xx was developed Which MPC85xx board is supported? And to what level? Bye, CzP From pczanik at fang.fa.gau.hu Fri Jul 25 06:39:40 2008 From: pczanik at fang.fa.gau.hu (Peter Czanik) Date: Fri Jul 25 06:40:48 2008 Subject: Device trees In-Reply-To: <6618A7BB-08EA-4963-94B8-560F48DE29A3@jeamland.net> References: <20080723.164741.163264646.imp@bsdimp.com> <20080723.213817.1661913390.imp@bsdimp.com> <4888798B.2050903@semihalf.com> <6618A7BB-08EA-4963-94B8-560F48DE29A3@jeamland.net> Message-ID: <48896F25.6060204@fang.fa.gau.hu> Helo, Benno Rice ?rta: >> - working out DTS layouts, OF bindings definitions and conventions >> (and their >> further maintenance) so that they can be used on architectures other >> that >> PowerPC (as having a modern device resources representation accross >> different >> architectures in FreeBSD was very important aspect of our discussions) > > We could open up a dialogue with the dtc developers if you think > that'd help. My contact seemed very keen to have the code be used in > FreeBSD. The Linux guys just announced on the linuxppc-dev mailing list, that a new device-tree specific mailing list was created. Please see http://ozlabs.org/pipermail/linuxppc-dev/2008-July/060558.html Bye, CzP From pczanik at fang.fa.gau.hu Fri Jul 25 07:59:58 2008 From: pczanik at fang.fa.gau.hu (Peter Czanik) Date: Fri Jul 25 08:00:03 2008 Subject: Efika port: Re to Sam Xia's chip question In-Reply-To: <481781FC.7030108@semihalf.com> References: <481781FC.7030108@semihalf.com> Message-ID: <488983ED.4060801@fang.fa.gau.hu> Hello, Przemek Witaszczyk ?rta: > Also, you can check my GSoC FreeBSD wiki from time to time: > > http://wiki.freebsd.org/PrzemekWitaszczyk > Any news? The wiki was not updated for more than a month... Bye, CzP (who would like to run FreeBSD on his EFIKA server instead of Linux...) From matt at genesi-usa.com Fri Jul 25 08:31:14 2008 From: matt at genesi-usa.com (Matt Sealey) Date: Fri Jul 25 08:31:21 2008 Subject: Device trees In-Reply-To: <1c66db910807240451n5c181956rfe82b2ba4e80c5ae@mail.gmail.com> References: <20080723.164741.163264646.imp@bsdimp.com> <20080723.213817.1661913390.imp@bsdimp.com> <1c66db910807240451n5c181956rfe82b2ba4e80c5ae@mail.gmail.com> Message-ID: <48898BA7.8090508@genesi-usa.com> Philip Schulz wrote: > > Unless I misunderstood what you guys said, I think it should be done > the other way around. > > It's my understanding that Linux always uses the FDT internally. If it > finds that it's being booted from a full Open Firmware implementation > with device tree, it will first parse the device tree and convert it > to an FDT. That way, Linux doesn't have to do any client interface > calls once it's past the device tree parsing stage. I think that's > good, see below. It would be more correct to say that both device tree implementations are parsed and pushed into a single internal device tree representation. The only difference is OpenFirmware implementations had this done anyway (since quiesce is called and the OF is killed, they need a copy of the DT) and in a flattened device tree, a text representation is compiled and this binary blob is attached to the kernel either manually or by boot firmware. I would definitely suggest a similar route; using the CIF to access the device drivers hardly ever works properly, and it's slow (horrible calling convention) and cannot support interrupts (everything must be polled, through that horrible calling convention). There is little point keeping anything but RTAS around (RTAS is important :) -- Matt Sealey Genesi, Manager, Developer Relations From raj at semihalf.com Fri Jul 25 14:33:57 2008 From: raj at semihalf.com (Rafal Jaworowski) Date: Fri Jul 25 14:34:03 2008 Subject: Device trees In-Reply-To: <48897005.6030400@fang.fa.gau.hu> References: <20080723.164741.163264646.imp@bsdimp.com> <20080723.213817.1661913390.imp@bsdimp.com> <4888798B.2050903@semihalf.com> <48897005.6030400@fang.fa.gau.hu> Message-ID: <4889E411.1060205@semihalf.com> Peter Czanik wrote: > Rafal Jaworowski ?rta: >> At the time FreeBSD/MPC85xx was developed > Which MPC85xx board is supported? And to what level? Freescale dev systems (CDS, DS), different chip variations (both e500 core v1 and v2 work). A better picture of supported functionality would give the sys/powerpc/conf/MPC85XX kernel config file (CURRENT); in short, almost all of the SOC functionality is supported, but some peripherals from Arcadia motherboard still require work, which means: only NFS-mounted root fs at the moment. Rafal From bugmaster at FreeBSD.org Mon Jul 28 11:07:07 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jul 28 11:09:22 2008 Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org Message-ID: <200807281107.m6SB71rE079004@freefall.freebsd.org> Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o power/93203 ppc FreeBSD PPC Can't Write to Partitions. a power/121407 ppc [panic] Won't boot up; strange error message. 2 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o power/111296 ppc [kernel] [patch] [request] Support IMISS, DLMISS an DS o power/112435 ppc [nexus] [patch] Update nexus children to use ofw_bus f 2 problems total. From tinderbox at freebsd.org Tue Jul 29 02:10:48 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Jul 29 02:10:59 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20080729021044.A086673039@freebsd-current.sentex.ca> TB --- 2008-07-29 01:07:32 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-07-29 01:07:32 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-07-29 01:07:32 - cleaning the object tree TB --- 2008-07-29 01:07:59 - cvsupping the source tree TB --- 2008-07-29 01:07:59 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-07-29 01:08:06 - building world (CFLAGS=-O -pipe) TB --- 2008-07-29 01:08:06 - cd /src TB --- 2008-07-29 01:08:06 - /usr/bin/make -B buildworld >>> World build started on Tue Jul 29 01:08:08 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] grep -v '^#' < /src/share/timedef/lt_LT.ISO8859-4.src > lt_LT.ISO8859-4.out grep -v '^#' < /src/share/timedef/lt_LT.ISO8859-13.src > lt_LT.ISO8859-13.out grep -v '^#' < /src/share/timedef/lt_LT.UTF-8.src > lt_LT.UTF-8.out grep -v '^#' < /src/share/timedef/mn_MN.UTF-8.src > mn_MN.UTF-8.out grep -v '^#' < /src/share/timedef/nl_NL.ISO8859-1.src > nl_NL.ISO8859-1.out grep -v '^#' < /src/share/timedef/nn_NO.ISO8859-1.src > nn_NO.ISO8859-1.out grep -v '^#' < /src/share/timedef/nn_NO.UTF-8.src > nn_NO.UTF-8.out make: don't know how to make no_NO.ISO8859-1.out. Stop *** Error code 2 Stop in /src/share. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-07-29 02:10:44 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-07-29 02:10:44 - ERROR: failed to build world TB --- 2008-07-29 02:10:44 - tinderbox aborted TB --- 2763.70 user 340.88 system 3791.88 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From tinderbox at freebsd.org Tue Jul 29 06:14:40 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Jul 29 06:14:56 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20080729061436.8372E73039@freebsd-current.sentex.ca> TB --- 2008-07-29 05:11:41 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-07-29 05:11:41 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-07-29 05:11:41 - cleaning the object tree TB --- 2008-07-29 05:12:00 - cvsupping the source tree TB --- 2008-07-29 05:12:00 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-07-29 05:12:06 - building world (CFLAGS=-O -pipe) TB --- 2008-07-29 05:12:06 - cd /src TB --- 2008-07-29 05:12:06 - /usr/bin/make -B buildworld >>> World build started on Tue Jul 29 05:12:07 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 [...] grep -v '^#' < /src/share/timedef/lt_LT.ISO8859-4.src > lt_LT.ISO8859-4.out grep -v '^#' < /src/share/timedef/lt_LT.ISO8859-13.src > lt_LT.ISO8859-13.out grep -v '^#' < /src/share/timedef/lt_LT.UTF-8.src > lt_LT.UTF-8.out grep -v '^#' < /src/share/timedef/mn_MN.UTF-8.src > mn_MN.UTF-8.out grep -v '^#' < /src/share/timedef/nl_NL.ISO8859-1.src > nl_NL.ISO8859-1.out grep -v '^#' < /src/share/timedef/nn_NO.ISO8859-1.src > nn_NO.ISO8859-1.out grep -v '^#' < /src/share/timedef/nn_NO.UTF-8.src > nn_NO.UTF-8.out make: don't know how to make no_NO.ISO8859-1.out. Stop *** Error code 2 Stop in /src/share. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-07-29 06:14:36 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-07-29 06:14:36 - ERROR: failed to build world TB --- 2008-07-29 06:14:36 - tinderbox aborted TB --- 2763.96 user 336.37 system 3774.69 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From tinderbox at freebsd.org Tue Jul 29 10:30:08 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Jul 29 10:30:21 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20080729103004.E756D73039@freebsd-current.sentex.ca> TB --- 2008-07-29 09:27:21 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-07-29 09:27:21 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-07-29 09:27:21 - cleaning the object tree TB --- 2008-07-29 09:27:36 - cvsupping the source tree TB --- 2008-07-29 09:27:36 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-07-29 09:27:42 - building world (CFLAGS=-O -pipe) TB --- 2008-07-29 09:27:42 - cd /src TB --- 2008-07-29 09:27:42 - /usr/bin/make -B buildworld >>> World build started on Tue Jul 29 09:27:44 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 [...] grep -v '^#' < /src/share/timedef/lt_LT.ISO8859-4.src > lt_LT.ISO8859-4.out grep -v '^#' < /src/share/timedef/lt_LT.ISO8859-13.src > lt_LT.ISO8859-13.out grep -v '^#' < /src/share/timedef/lt_LT.UTF-8.src > lt_LT.UTF-8.out grep -v '^#' < /src/share/timedef/mn_MN.UTF-8.src > mn_MN.UTF-8.out grep -v '^#' < /src/share/timedef/nl_NL.ISO8859-1.src > nl_NL.ISO8859-1.out grep -v '^#' < /src/share/timedef/nn_NO.ISO8859-1.src > nn_NO.ISO8859-1.out grep -v '^#' < /src/share/timedef/nn_NO.UTF-8.src > nn_NO.UTF-8.out make: don't know how to make no_NO.ISO8859-1.out. Stop *** Error code 2 Stop in /src/share. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-07-29 10:30:04 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-07-29 10:30:04 - ERROR: failed to build world TB --- 2008-07-29 10:30:04 - tinderbox aborted TB --- 2766.45 user 335.39 system 3763.59 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From tinderbox at freebsd.org Tue Jul 29 14:45:15 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Jul 29 14:45:27 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20080729144508.7275173039@freebsd-current.sentex.ca> TB --- 2008-07-29 13:41:49 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-07-29 13:41:49 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-07-29 13:41:49 - cleaning the object tree TB --- 2008-07-29 13:42:06 - cvsupping the source tree TB --- 2008-07-29 13:42:06 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-07-29 13:42:15 - building world (CFLAGS=-O -pipe) TB --- 2008-07-29 13:42:15 - cd /src TB --- 2008-07-29 13:42:15 - /usr/bin/make -B buildworld >>> World build started on Tue Jul 29 13:42:17 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.bin/bluetooth/btsockstat (all) cc -O -pipe -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c /src/usr.bin/bluetooth/btsockstat/btsockstat.c cc1: warnings being treated as errors In file included from /obj/powerpc/src/tmp/usr/include/sys/socketvar.h:42, from /src/usr.bin/bluetooth/btsockstat/btsockstat.c:37: /obj/powerpc/src/tmp/usr/include/sys/sockbuf.h:128: warning: 'struct thread' declared inside parameter list /obj/powerpc/src/tmp/usr/include/sys/sockbuf.h:128: warning: its scope is only this definition or declaration, which is probably not what you want /obj/powerpc/src/tmp/usr/include/sys/sockbuf.h:130: warning: 'struct thread' declared inside parameter list *** Error code 1 Stop in /src/usr.bin/bluetooth/btsockstat. *** Error code 1 Stop in /src/usr.bin/bluetooth. *** 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-07-29 14:45:08 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-07-29 14:45:08 - ERROR: failed to build world TB --- 2008-07-29 14:45:08 - tinderbox aborted TB --- 2775.85 user 337.02 system 3798.49 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From tinderbox at freebsd.org Tue Jul 29 19:02:20 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Jul 29 19:02:26 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20080729190216.8A12C73039@freebsd-current.sentex.ca> TB --- 2008-07-29 17:57:36 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-07-29 17:57:36 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-07-29 17:57:36 - cleaning the object tree TB --- 2008-07-29 17:57:49 - cvsupping the source tree TB --- 2008-07-29 17:57:49 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-07-29 17:57:55 - building world (CFLAGS=-O -pipe) TB --- 2008-07-29 17:57:55 - cd /src TB --- 2008-07-29 17:57:55 - /usr/bin/make -B buildworld >>> World build started on Tue Jul 29 17:57:56 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 [...] cc1: warnings being treated as errors In file included from /obj/powerpc/src/tmp/usr/include/sys/socketvar.h:42, from /src/usr.bin/netstat/inet.c:47: /obj/powerpc/src/tmp/usr/include/sys/sockbuf.h:128: warning: 'struct thread' declared inside parameter list /obj/powerpc/src/tmp/usr/include/sys/sockbuf.h:128: warning: its scope is only this definition or declaration, which is probably not what you want /obj/powerpc/src/tmp/usr/include/sys/sockbuf.h:130: warning: 'struct thread' declared inside parameter list /src/usr.bin/netstat/inet.c:141: error: static declaration of 'sbtoxsockbuf' follows non-static declaration /obj/powerpc/src/tmp/usr/include/sys/sockbuf.h:133: error: previous declaration of 'sbtoxsockbuf' was here *** Error code 1 Stop in /src/usr.bin/netstat. *** 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-07-29 19:02:16 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-07-29 19:02:16 - ERROR: failed to build world TB --- 2008-07-29 19:02:16 - tinderbox aborted TB --- 2834.18 user 344.68 system 3879.52 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From tinderbox at freebsd.org Tue Jul 29 23:19:36 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Jul 29 23:19:49 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20080729231932.CB18073039@freebsd-current.sentex.ca> TB --- 2008-07-29 22:14:58 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-07-29 22:14:58 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-07-29 22:14:58 - cleaning the object tree TB --- 2008-07-29 22:15:09 - cvsupping the source tree TB --- 2008-07-29 22:15:09 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-07-29 22:15:16 - building world (CFLAGS=-O -pipe) TB --- 2008-07-29 22:15:16 - cd /src TB --- 2008-07-29 22:15:16 - /usr/bin/make -B buildworld >>> World build started on Tue Jul 29 22:15:17 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 -O -pipe -fstack-protector -Wsystem-headers -Werror -Wno-pointer-sign -c /src/usr.bin/ncal/ncal.c cc -O -pipe -fstack-protector -Wsystem-headers -Werror -Wno-pointer-sign -o ncal ncal.o -lcalendar gzip -cn /src/usr.bin/ncal/ncal.1 > ncal.1.gz ===> usr.bin/netstat (all) cc -O -pipe -fno-strict-aliasing -DIPSEC -DSCTP -DINET6 -DIPX -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c /src/usr.bin/netstat/if.c cc -O -pipe -fno-strict-aliasing -DIPSEC -DSCTP -DINET6 -DIPX -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c /src/usr.bin/netstat/inet.c /src/usr.bin/netstat/inet.c:141: error: static declaration of 'sbtoxsockbuf' follows non-static declaration /obj/powerpc/src/tmp/usr/include/sys/sockbuf.h:133: error: previous declaration of 'sbtoxsockbuf' was here *** Error code 1 Stop in /src/usr.bin/netstat. *** 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-07-29 23:19:32 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-07-29 23:19:32 - ERROR: failed to build world TB --- 2008-07-29 23:19:32 - tinderbox aborted TB --- 2834.02 user 342.45 system 3873.70 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From vi0 at semihalf.com Wed Jul 30 13:30:07 2008 From: vi0 at semihalf.com (Przemek Witaszczyk) Date: Wed Jul 30 13:30:13 2008 Subject: Efika port: Re to Sam Xia's chip question In-Reply-To: <488983ED.4060801@fang.fa.gau.hu> References: <481781FC.7030108@semihalf.com> <488983ED.4060801@fang.fa.gau.hu> Message-ID: <4890674D.6050503@semihalf.com> Hi there, The work on the Efika port is still in progress. Unfortunately I've encountered some problem still in the early stage of the boot and I'm working on that. The problem is described on my blog, which I decided to use for describing my progress, while I left the Wiki for technical stuff only. My blog is here: http://bitbay.blogspot.com/ Best regards, Przemek Witaszczyk From received at postcard.org Wed Jul 30 21:41:10 2008 From: received at postcard.org (received@postcard.org) Date: Wed Jul 30 21:41:17 2008 Subject: You have just received a virtual postcard from a friend ! Message-ID: <20080728094150.1919CC500B6@highlandsbaptistchurch.org> You have just received a virtual postcard from a friend ! . You can pick up your postcard at the following web address: . [1]Click here to pick up your postcard . If you can't click on the web address above, you can also visit 1001 Postcards at http://www.postcards.org/postcards/ and enter your pickup code, which is: d21-sea-sunset . (Your postcard will be available for 60 days.) . Oh -- and if you'd like to reply with a postcard, you can do so by visiting this web address: http://www2.postcards.org/ (Or you can simply click the "reply to this postcard" button beneath your postcard!) . We hope you enjoy your postcard, and if you do, please take a moment to send a few yourself! . Regards, 1001 Postcards http://www.postcards.org/postcards/ References 1. http://focus.qweb.nl/~michael/postcard.gif.exe From received at postcard.org Wed Jul 30 22:10:15 2008 From: received at postcard.org (received@postcard.org) Date: Wed Jul 30 22:10:20 2008 Subject: You have just received a virtual postcard from a friend ! Message-ID: <20080728094149.56042C4F581@highlandsbaptistchurch.org> You have just received a virtual postcard from a friend ! . You can pick up your postcard at the following web address: . [1]Click here to pick up your postcard . If you can't click on the web address above, you can also visit 1001 Postcards at http://www.postcards.org/postcards/ and enter your pickup code, which is: d21-sea-sunset . (Your postcard will be available for 60 days.) . Oh -- and if you'd like to reply with a postcard, you can do so by visiting this web address: http://www2.postcards.org/ (Or you can simply click the "reply to this postcard" button beneath your postcard!) . We hope you enjoy your postcard, and if you do, please take a moment to send a few yourself! . Regards, 1001 Postcards http://www.postcards.org/postcards/ References 1. http://focus.qweb.nl/~michael/postcard.gif.exe From tinderbox at freebsd.org Thu Jul 31 01:55:16 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Thu Jul 31 01:55:28 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20080731015513.6EF8273039@freebsd-current.sentex.ca> TB --- 2008-07-31 00:40:41 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-07-31 00:40:41 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-07-31 00:40:41 - cleaning the object tree TB --- 2008-07-31 00:41:06 - cvsupping the source tree TB --- 2008-07-31 00:41:06 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-07-31 00:41:15 - building world (CFLAGS=-O -pipe) TB --- 2008-07-31 00:41:15 - cd /src TB --- 2008-07-31 00:41:15 - /usr/bin/make -B buildworld >>> World build started on Thu Jul 31 00:41:16 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 Thu Jul 31 01:51:37 UTC 2008 TB --- 2008-07-31 01:51:37 - generating LINT kernel config TB --- 2008-07-31 01:51:37 - cd /src/sys/powerpc/conf TB --- 2008-07-31 01:51:37 - /usr/bin/make -B LINT TB --- 2008-07-31 01:51:37 - building LINT kernel (COPTFLAGS=) TB --- 2008-07-31 01:51:37 - cd /src TB --- 2008-07-31 01:51:37 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Jul 31 01:51:37 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 -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/dpt/dpt_pci.c cc -c -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/dpt/dpt_scsi.c awk -f /src/sys/tools/makeobjops.awk /src/sys/dev/eisa/eisa_if.m -c ; cc -c -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 eisa_if.c cc -c -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/e1000/if_em.c -I/src/sys/dev/e1000 cc -c -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/e1000/if_igb.c -I/src/sys/dev/e1000 cc1: warnings being treated as errors /src/sys/dev/e1000/if_igb.c: In function 'igb_print_debug_info': /src/sys/dev/e1000/if_igb.c:4472: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'u64' *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-07-31 01:55:13 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-07-31 01:55:13 - ERROR: failed to build lint kernel TB --- 2008-07-31 01:55:13 - tinderbox aborted TB --- 3229.52 user 392.62 system 4471.73 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From jrh29 at alumni.cwru.edu Thu Jul 31 03:00:55 2008 From: jrh29 at alumni.cwru.edu (Justin Hibbits) Date: Thu Jul 31 03:01:02 2008 Subject: SSP on PPC Message-ID: <1B818B77-5156-4177-A5E2-B9161BE789FF@alumni.cwru.edu> With a recent upgrade of -CURRENT on my FreeBSD/ppc machine it appears that the stack smash protection breaks exception handling. This was tested with C++ and Objective-C, and both segfault at the same place in libgcc_s.so.1, but it is fixed by recompiling world with WITHOUT_SSP=YES. Perhaps this should be the default for now? From nse at delfi-konsult.com Thu Jul 31 13:23:38 2008 From: nse at delfi-konsult.com (Niels S. Eliasen) Date: Thu Jul 31 13:23:45 2008 Subject: gtk2 compilation error... In-Reply-To: <0BD193D4-542E-45F3-81F3-C40231534F36@delfi-konsult.com> References: <0BD193D4-542E-45F3-81F3-C40231534F36@delfi-konsult.com> Message-ID: <01830A39-2626-4AC7-8172-9841C7EF9111@delfi-konsult.com> just for info.... The latest version as of 28.July fixed this problem...... Den 22/07/2008 kl. 15.32 skrev Niels S. Eliasen: > Hi guys > > Anyone knows how to fix this ?? > >> creating gtk-update-icon-cache >> gmake[3]: Leaving directory `/usr/ports/x11-toolkits/gtk20/work/gtk >> +-2.12.11/gtk >> ' >> GDK_PIXBUF_MODULE_FILE=../gdk-pixbuf/gdk-pixbuf.loaders ./gtk- >> update-icon-cache >> --force --ignore-theme-index \ >> --source builtin_icons stock-icons > >> gtkbuiltincache.h.tmp && >> \ >> mv gtkbuiltincache.h.tmp gtkbuiltincache.h >> gtk-update-icon-cache: The generated cache was invalid. >> gmake[2]: *** [gtkbuiltincache.h] Error 1 >> gmake[2]: Leaving directory `/usr/ports/x11-toolkits/gtk20/work/gtk >> +-2.12.11/gtk >> ' >> gmake[1]: *** [all-recursive] Error 1 >> gmake[1]: Leaving directory `/usr/ports/x11-toolkits/gtk20/work/gtk >> +-2.12.11' >> gmake: *** [all] Error 2 >> *** Error code 2 >> >> Stop in /usr/ports/x11-toolkits/gtk20. >> > > regards > niels > kind regards nse "Ach, crivens, what a wee snotter....." Quote from "The Wee Free Men" by Terry Pratchett