From owner-freebsd-ppc@FreeBSD.ORG Sun Jan 18 05:18:45 2009 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8416D1065670 for ; Sun, 18 Jan 2009 05:18:45 +0000 (UTC) (envelope-from nick@nickwithers.com) Received: from mail.nickwithers.com (mail.nickwithers.com [123.243.228.66]) by mx1.freebsd.org (Postfix) with ESMTP id 9935F8FC16 for ; Sun, 18 Jan 2009 05:18:43 +0000 (UTC) (envelope-from nick@nickwithers.com) Received: from [10.0.0.245] (unknown [10.0.0.245]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.nickwithers.com (Postfix) with ESMTPSA id BE2E13F for ; Sun, 18 Jan 2009 16:18:26 +1100 (EST) From: Nick Withers To: freebsd-ppc@freebsd.org Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-rS29BGPvLAxsFwneuDJR" Date: Sun, 18 Jan 2009 16:18:15 +1100 Message-Id: <1232255895.67062.27.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.24.3 FreeBSD GNOME Team Port X-MailScanner-ID: BE2E13F.6026B X-nickwithers-MailScanner: Found to be clean X-nickwithers-MailScanner-From: nick@nickwithers.com Subject: Fatal kernel trap - "data storage interrupt" - on recent 7-STABLE X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jan 2009 05:18:45 -0000 --=-rS29BGPvLAxsFwneuDJR Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi all, My lofty plans for testing PPC ATA DMA have been thwarted somewhat by my bringing my G4 box from 7-STABLE / 7.1-PRERELEASE as of around the 2008-11-26 to 7-STABLE of around the 2009-01-15, where I'm now seeing, after a few hours of uptime (transcribed from the screen): ____ fatal kernel trap: exception =3D 0x3 (data storage interrupt) virtual address =3D 0x4200009c srr0 =3D 0x2175b0 srr1 =3D 0x9032 curthread =3D 0x1deed20 pid =3D 40264, comm =3D find [thread pid 40264 tid 100126 ] Stopped at 0x2175b0: lwarx r10, r0, r9, db> ____ I've had it twice now (I've been off-site a lot, sure I could've had it more often if I were quicker rebooting the thing), with only the thread information changing on the second - same exception, virtual address, srr0 and srr1. The keyboard is non-responsive at this point and I have to hard reset it. I've just switched back to running the old (i.e, November 2008 7-STABLE) kernel and am expecting not to see it again... Boot dmesg: ____ Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-STABLE #0: Thu Jan 15 23:32:53 EST 2009 nick@internal.shmon.net:/usr/obj/usr/RELENG_7/src/sys/INTERNAL module_register: module uhub/ugen already exists! Module uhub/ugen failed to register: 17 cpu0: Motorola PowerPC 7400 revision 2.8, 400.00 MHz cpu0: HID0 8094c0a4 real memory =3D 393060352 (374 MB) avail memory =3D 378433536 (360 MB) kbd0 at kbdmux0 nexus0: unin0: on nexus0 unin0: Version 8 pcib0: on nexus0 pci0: on pcib0 vgapci0: port 0x400-0x4ff mem 0x94000000-0x97ffffff,0x90000000-0x90003fff irq 48 at device 16.0 on pci0 pcib1: on nexus0 pci1: on pcib1 pcib2: at device 13.0 on pci1 pci2: on pcib2 macio0: mem 0x80000000-0x8007ffff at device 7.0 on pci2 openpic0: mem 0x40000-0x7ffff on macio0 ata0 mem 0x1f000-0x1ffff,0x8a00-0x8aff irq 19,11 on macio0 ata0: [ITHREAD] ata1 mem 0x20000-0x20fff,0x8b00-0x8bff irq 20,12 on macio0 ata1: [ITHREAD] ata2 mem 0x21000-0x21fff,0x8c00-0x8cff irq 21,13 on macio0 ata2: [ITHREAD] ohci0: mem 0x80082000-0x80082fff irq 27 at device 8.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: 2 ports with 2 removable, self powered ohci1: mem 0x80081000-0x80081fff irq 28 at device 9.0 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 pci2: at device 10.0 (no driver attached) pcib3: on nexus0 pci3: on pcib3 gem0: mem 0xf5200000-0xf53fffff irq 41 at device 15.0 on pci3 miibus0: on gem0 brgphy0: PHY 0 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto gem0: 10kB RX FIFO, 4kB TX FIFO gem0: Ethernet address: 00:30:65:a8:02:3a gem0: [ITHREAD] sc0: on nexus0 sc0: Unknown <16 virtual consoles, flags=3D0x300> ugen0: on uhub0 uhub2: on uhub1 uhub2: 3 ports with 2 removable, bus powered ukbd0: on uhub2 kbd1 at ukbd0 uhid0: on uhub2 Timecounter "decrementer" frequency 24907667 Hz quality 0 Timecounters tick every 10.000 msec ipfw2 (+ipv6) initialized, divert loadable, nat loadable, rule-based forwarding disabled, default to deny, logging limited to 200 packets/entry by default ad0: 19569MB at ata0-master BIOSPIO ad1: 76319MB at ata0-slave BIOSPIO GEOM: ad1: the secondary GPT table is corrupt or invalid. GEOM: ad1: using the primary only -- recovery suggested. Root mount waiting for: GMIRROR Root mount waiting for: GMIRROR Root mount waiting for: GMIRROR Root mount waiting for: GMIRROR GEOM_MIRROR: Force device gm0 start due to timeout. GEOM_MIRROR: Device mirror/gm0 launched (1/2). GEOM: mirror/gm0: the secondary GPT table is corrupt or invalid. GEOM: mirror/gm0: using the primary only -- recovery suggested. Trying to mount root from ufs:/dev/ad0s4 WARNING: / was not properly dismounted WARNING: /tmp was not properly dismounted WARNING: /usr was not properly dismounted /usr: mount pending error: blocks 16 files 1 WARNING: /var was not properly dismounted WARNING: /data was not properly dismounted ____ I'm not much of a kernel debugger, I'm afraid... I'm sure I've seen information on how to translate kernel addresses into the location of the code in the kernel but am doing a poor job of digging it up. Anyone able to give me a pointer or two? Thanks! --=20 Nick Withers email: nick@nickwithers.com Web: http://www.nickwithers.com Mobile: +61 414 397 446 --=-rS29BGPvLAxsFwneuDJR Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEABECAAYFAklyu5cACgkQ3wcG/Pf4WrgtGgCgtezpSR9OMWG5u0V1XdoHyk9N 6zMAnj0eKcrt/aWUH/BUNHgJaz+Ol3d9 =F8/u -----END PGP SIGNATURE----- --=-rS29BGPvLAxsFwneuDJR-- From owner-freebsd-ppc@FreeBSD.ORG Sun Jan 18 05:53:03 2009 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4BF82106566B for ; Sun, 18 Jan 2009 05:53:03 +0000 (UTC) (envelope-from nick@nickwithers.com) Received: from mail.nickwithers.com (mail.nickwithers.com [123.243.228.66]) by mx1.freebsd.org (Postfix) with ESMTP id 85C738FC12 for ; Sun, 18 Jan 2009 05:53:01 +0000 (UTC) (envelope-from nick@nickwithers.com) Received: from [10.0.0.245] (unknown [10.0.0.245]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.nickwithers.com (Postfix) with ESMTPSA id F358143 for ; Sun, 18 Jan 2009 16:52:46 +1100 (EST) From: Nick Withers To: freebsd-ppc@freebsd.org In-Reply-To: <1232255895.67062.27.camel@localhost> References: <1232255895.67062.27.camel@localhost> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-6ZZk1Xdm+my3SpHJyveb" Date: Sun, 18 Jan 2009 16:52:46 +1100 Message-Id: <1232257966.67062.36.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.24.3 FreeBSD GNOME Team Port X-MailScanner-ID: F358143.B047B X-nickwithers-MailScanner: Found to be clean X-nickwithers-MailScanner-From: nick@nickwithers.com Subject: Re: Fatal kernel trap - "data storage interrupt" - on recent 7-STABLE X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jan 2009 05:53:03 -0000 --=-6ZZk1Xdm+my3SpHJyveb Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2009-01-18 at 16:18 +1100, Nick Withers wrote: > Hi all, >=20 > My lofty plans for testing PPC ATA DMA have been thwarted somewhat by my > bringing my G4 box from 7-STABLE / 7.1-PRERELEASE as of around the > 2008-11-26 to 7-STABLE of around the 2009-01-15, where I'm now seeing, > after a few hours of uptime (transcribed from the screen): > ____ >=20 > fatal kernel trap: >=20 > exception =3D 0x3 (data storage interrupt) > virtual address =3D 0x4200009c > srr0 =3D 0x2175b0 > srr1 =3D 0x9032 > curthread =3D 0x1deed20 > pid =3D 40264, comm =3D find >=20 > [thread pid 40264 tid 100126 ] > Stopped at 0x2175b0: lwarx r10, r0, r9, > db> > ____ >=20 > I've had it twice now (I've been off-site a lot, sure I could've had it > more often if I were quicker rebooting the thing), with only the thread > information changing on the second - same exception, virtual address, > srr0 and srr1. >=20 > The keyboard is non-responsive at this point and I have to hard reset > it. >=20 > I've just switched back to running the old (i.e, November 2008 7-STABLE) > kernel and am expecting not to see it again... >=20 > Boot dmesg: > ____ (snip) > ____ >=20 > I'm not much of a kernel debugger, I'm afraid... I'm sure I've seen > information on how to translate kernel addresses into the location of > the code in the kernel but am doing a poor job of digging it up. Hmmm... Is the following useful? ____ %nm /boot/kernel/kernel | sort | grep ^0021=20 0021008c t modlist_lookup2 0021016c T linker_ctf_get 002101f4 T linker_file_function_listall 0021028c t linker_debug_search_symbol 002103f4 T linker_ddb_search_symbol 00210424 t linker_debug_symbol_values 002104f4 T linker_ddb_symbol_values 00210524 t modlist_newmodule 002105cc t linker_addmodules 002106a0 t linker_file_add_dependency 00210768 t sysctl_kern_function_list_iterate 002107d0 t linker_lookup_file 00210b08 t linker_strdup 00210b74 t linker_basename 00210bd8 t linker_find_file_by_name 00210ca4 t linker_debug_search_symbol_name 00210d34 T linker_ddb_search_symbol_name 00210d64 T linker_make_file 00210ed0 T linker_add_class 00210f5c t sysctl_kern_function_list 0021117c T kldfirstmod 0021137c T kldstat 002115c8 T kldnext 0021173c T linker_file_foreach 00211880 T kldfind 00211a04 T linker_search_symbol_name 00211b30 T linker_file_lookup_set 00211cd0 t linker_file_register_modules 00211df4 t linker_init_kernel_modules 00211e2c t linker_file_register_sysctls 00211f58 T linker_file_unload 00212604 t linker_preload 00212d28 T kern_kldunload 00212edc T kldunloadf 00212f28 T kldunload 00212f60 T linker_release_module 00213104 t linker_load_module 00213dc4 T linker_load_dependencies 00214010 T kern_kldload 002141c4 T kldload 00214280 T linker_reference_module 00214438 t linker_file_lookup_symbol_internal 0021463c T linker_file_lookup_symbol 00214788 T linker_ddb_lookup 00214858 T kldsym 00214bf8 t unlock_lockmgr 00214c18 t lock_lockmgr 00214c38 t db_show_lockmgr 00214d18 T lockmgr_chain 00214e34 T lockmgr_printinfo 00214ed0 T lockdestroy 00214f00 T lockinit 00214fc0 t acquire 002151b8 T lockwaiters 002152b0 T lockcount 002153b4 T lockstatus 00215514 T transferlockers 002156ac T _lockmgr 00216070 t lf_blocks 00216114 t lf_insert_lock 002161bc t lf_getblock 00216288 t graph_add_indices 00216354 t graph_assign_indices 00216408 t lf_init 00216500 t lf_clearremotesys_iterator 00216568 t lf_remove_edge 002166a8 t lf_remove_incoming 002166fc t lf_remove_outgoing 00216750 t lf_alloc_vertex 00216870 t lf_add_edge 00216cb4 t lf_add_incoming 00216d50 t lf_alloc_lock 00216e78 T lf_countlocks 00216fbc T lf_iteratelocks_vnode 0021724c t lf_free_lock 00217570 T lf_purgelocks 00217ad8 T lf_iteratelocks_sysid 00217e44 T lf_clearremotesys 00217e80 t lf_update_dependancies 0021808c t lf_set_end 002180cc t lf_set_start 00218164 t lf_activate_lock 002185d0 t lf_cancel_lock 00218754 T lf_advlockasync 00219b24 T lf_advlock 00219b8c T malloc_last_fail 00219bbc t kmeminit 00219e60 t db_show_malloc 00219f58 T malloc_desc2type 00219fcc T malloc_type_freed 0021a06c t malloc_type_zone_allocated 0021a154 T malloc_type_allocated 0021a190 T malloc 0021a2b4 T malloc_init 0021a3d8 T free 0021a4bc T malloc_type_list 0021a754 t sysctl_kern_malloc_stats 0021abdc T realloc 0021ad24 T reallocf 0021ad8c T malloc_uninit 0021af70 t mb_ctor_mbuf 0021aff4 t mb_dtor_clust 0021b010 t mb_ctor_pack 0021b084 t mb_reclaim 0021b110 t tunable_mbinit 0021b194 t sysctl_nmbjumbo16 0021b238 t sysctl_nmbjumbo9 0021b2dc t sysctl_nmbjumbop 0021b380 t mbuf_init 0021b64c t mbuf_jumbo_free 0021b684 t mbuf_jumbo_alloc 0021b6dc t mb_zfini_pack 0021b71c t mb_zinit_pack 0021b78c t mb_dtor_mbuf 0021b7d4 t mb_dtor_pack 0021b834 t mb_ctor_clust 0021b94c t sysctl_nmbclusters 0021bb7c t sysctl_hw_usermem 0021bbd0 t sysctl_hw_realmem 0021bc18 t sysctl_hw_physmem 0021bc60 t sysctl_kern_arnd 0021bce4 t sysctl_hostname 0021bf24 t sysctl_kern_securelvl 0021c274 t modevent_nop 0021c2b8 T module_reference 0021c2e0 T module_lookupbyid 0021c338 T module_getid 0021c358 T module_getfnext 0021c378 T module_setspecific 0021c39c T module_file 0021c3bc t module_init 0021c440 T module_lookupbyname 0021c4b4 T module_unload 0021c60c T module_release 0021c7a0 T module_register 0021ca74 t module_shutdown 0021cc5c T modfind 0021cda4 T modstat 0021d014 T modfnext 0021d168 T modnext 0021d2e8 T module_register_init 0021d5d8 T mtx_pool_find 0021d61c T mtx_pool_alloc 0021d65c t mtx_pool_initialize 0021d734 t mtx_pool_setup_static 0021d790 T mtx_pool_destroy 0021d818 T mtx_pool_create 0021d8c4 t mtx_pool_setup_dynamic 0021d90c t unlock_spin 0021d92c t lock_spin 0021d94c t db_show_mtx 0021daf4 T thread_lock_set 0021db54 T thread_lock_unblock 0021db8c T _mtx_unlock_spin_flags 0021dbe0 T mtx_init 0021dc88 T mtx_sysinit 0021dccc T _mtx_unlock_sleep 0021dd84 t unlock_mtx 0021de04 T thread_lock_block 0021de88 T _mtx_lock_sleep 0021dfbc t lock_mtx 0021e038 T mtx_destroy 0021e0d8 T _mtx_lock_spin_flags 0021e148 T mutex_init 0021e280 T _thread_lock_flags 0021e494 T _mtx_trylock 0021e55c T _mtx_lock_flags 0021e5f4 T _mtx_unlock_flags 0021e678 T ntp_update_second 0021e9f0 t ntp_init 0021ea2c t hardupdate 0021ee04 t ntp_gettime1 0021eec4 t ntp_sysctl 0021ef30 T kern_adjtime 0021f190 T adjtime 0021f238 T ntp_gettime 0021f34c T ntp_adjtime 0021f8d8 T physio 0021fdb4 T pmc_cpu_is_disabled 0021fdd4 T pmc_cpu_is_logical 0021fdf4 T priv_check_cred 0021fe94 T suser_cred 0021fecc T suser 0021ff04 T priv_check 0021ff3c T pargs_hold 0021ff78 t pgrpdump %kldstat Id Refs Address Size Name 1 8 0x100000 4a2d2c kernel 2 1 0x5a3000 2dabc geom_mirror.ko 3 1 0x5d1000 167f8 ugen.ko 4 1 0xd07a4000 15000 nullfs.ko 5 1 0xd07bc000 26000 nfslockd.ko 6 1 0xd07e2000 5c000 nfsclient.ko 7 1 0xd0846000 27000 krpc.ko ____ > Anyone able to give me a pointer or two? >=20 > Thanks! --=20 Nick Withers email: nick@nickwithers.com Web: http://www.nickwithers.com Mobile: +61 414 397 446 --=-6ZZk1Xdm+my3SpHJyveb Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEABECAAYFAklyw64ACgkQ3wcG/Pf4WrjVDQCfYwi4XzmcCtbLef28oBEtcHan ORkAn2U1uLMDYSMRNjM6GuCXMi33wScw =o7Tb -----END PGP SIGNATURE----- --=-6ZZk1Xdm+my3SpHJyveb-- From owner-freebsd-ppc@FreeBSD.ORG Mon Jan 19 05:14:13 2009 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 80177106568E for ; Mon, 19 Jan 2009 05:14:13 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id 5C72A8FC26 for ; Mon, 19 Jan 2009 05:14:13 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1LOmGg-0000Z7-9s for freebsd-ppc@freebsd.org; Sun, 18 Jan 2009 21:01:46 -0800 Message-ID: <21537032.post@talk.nabble.com> Date: Sun, 18 Jan 2009 21:01:46 -0800 (PST) From: blubaustin To: freebsd-ppc@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: blubaustin@gmail.com Subject: IMac G3 Partition X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2009 05:14:14 -0000 Hi, I have an IMac G3 600Mhz, 512mb Ram, 40GB hd, Ati Rage 128 Ultra Pro 16mb. I was wondering how do I pre-partition the hard drive for freebsd? I read that it has to be prepartioned because FDISK doesn't work. I tried using pdisk on NETBSD, and got it partitoned but I got stuck when I had to create an FSTAB since... NETBsd only uses SED or ED for editing, and I don't know how to use those. -- View this message in context: http://www.nabble.com/IMac-G3-Partition-tp21537032p21537032.html Sent from the freebsd-ppc mailing list archive at Nabble.com. From owner-freebsd-ppc@FreeBSD.ORG Mon Jan 19 09:51:31 2009 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3FEF1065679 for ; Mon, 19 Jan 2009 09:51:31 +0000 (UTC) (envelope-from marcotrillo@gmail.com) Received: from mail-bw0-f14.google.com (mail-bw0-f14.google.com [209.85.218.14]) by mx1.freebsd.org (Postfix) with ESMTP id 0F8358FC0C for ; Mon, 19 Jan 2009 09:51:30 +0000 (UTC) (envelope-from marcotrillo@gmail.com) Received: by bwz7 with SMTP id 7so70335bwz.19 for ; Mon, 19 Jan 2009 01:51:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=fRdtozBvbzHE3RhsBuVZ7cLt++qSg6+PagFpMjGKySw=; b=b38/wsFhubbITOcuEdy4ErkP8KWtJpQfN9183XuCbGFvsw2KNBCsiq0FLswUa9WHKM jcKNdPh+hOR2JV1dtY4vd04gpfB9TecobaTRZzHyJ0bM96++KJZLB5q1qTHfRtbKPREu 0EqKPOncPGYfB/AeVD9aqCNeOQKQNk7tIHsvc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=OIRbXsMLVqPGj8qFlQNVVHI6ShtAQCLRTuoj9kzvR/5BwxLUEwU19dIeyfTjTW3UvN GYR821OQp8oUw7Vf/9jRSbEL0K9f1tNR0SVuHlyvTB8CYFdjyu2JvxRQxofJeZAcG16T vckjn9/GvlpjZBjAaeeOjcuez0jUK4lSK7Uzk= Received: by 10.86.92.9 with SMTP id p9mr473857fgb.15.1232356871272; Mon, 19 Jan 2009 01:21:11 -0800 (PST) Received: by 10.86.4.18 with HTTP; Mon, 19 Jan 2009 01:21:11 -0800 (PST) Message-ID: Date: Mon, 19 Jan 2009 10:21:11 +0100 From: "Marco Trillo" To: blubaustin In-Reply-To: <21537032.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <21537032.post@talk.nabble.com> Cc: freebsd-ppc@freebsd.org Subject: Re: IMac G3 Partition X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2009 09:51:32 -0000 Hi, On Mon, Jan 19, 2009 at 6:01 AM, blubaustin wrote: > > Hi, I have an IMac G3 600Mhz, 512mb Ram, 40GB hd, Ati Rage 128 Ultra Pro > 16mb. I was wondering how do I pre-partition the hard drive for freebsd? > read that it has to be prepartioned because FDISK doesn't work. I tried > using pdisk on NETBSD, and got it partitoned but I got stuck when I had to > create an FSTAB since... There are various options available: - If you use NetBSD's pdisk tool, you simply need to create some partitions for FreeBSD (for example with type Apple_UNIX_SVR2). You do not need to create filesystems from NetBSD or to create an fstab file in NetBSD -- the FreeBSD installer does all of this. When you boot the FreeBSD installer you can select the newly created partitions to install FreeBSD. - If you have Mac OS 9 or Mac OS X installation media, you can use "Drive Setup" (for Mac OS 9) or "Disk Utility" (for Mac OS X). With these tools you can create the partitions. Any partition type can be used (HFS, UFS, etc.), as FreeBSD doesn't care about the type and will reformat them with its own filesystem. However the "Drive Setup" tool is more flexible and will allow to select the "A/UX" partition type (equivalent to Apple_UNIX_SVR2 in pdisk), which can be used to avoid Mac OS messing with the FreeBSD partitions . Hope that helps Marco From owner-freebsd-ppc@FreeBSD.ORG Mon Jan 19 11:07:03 2009 Return-Path: Delivered-To: freebsd-ppc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98657106566B for ; Mon, 19 Jan 2009 11:07:03 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 85CAC8FC2D for ; Mon, 19 Jan 2009 11:07:03 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0JB73XP063063 for ; Mon, 19 Jan 2009 11:07:03 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0JB72Ho063059 for freebsd-ppc@FreeBSD.org; Mon, 19 Jan 2009 11:07:03 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 19 Jan 2009 11:07:03 GMT Message-Id: <200901191107.n0JB72Ho063059@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-ppc@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2009 11:07:04 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- a power/121407 ppc [panic] Won't boot up; strange error message. o power/112435 ppc [nexus] [patch] Update nexus children to use ofw_bus f o power/111296 ppc [kernel] [patch] [request] Support IMISS, DLMISS an DS o power/93203 ppc FreeBSD PPC Can't Write to Partitions. 4 problems total. From owner-freebsd-ppc@FreeBSD.ORG Mon Jan 19 11:59:56 2009 Return-Path: Delivered-To: FreeBSD-PPC@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9EB71065672; Mon, 19 Jan 2009 11:59:56 +0000 (UTC) (envelope-from Daan@vehosting.nl) Received: from VM01.VEHosting.nl (unknown [IPv6:2001:470:1f14:32d::1:140]) by mx1.freebsd.org (Postfix) with ESMTP id 9FC288FC0A; Mon, 19 Jan 2009 11:59:56 +0000 (UTC) (envelope-from Daan@vehosting.nl) Received: from [192.168.72.10] (124-54.bbned.dsl.internl.net [92.254.54.124]) (authenticated bits=0) by VM01.VEHosting.nl (8.14.3/8.13.8) with ESMTP id n0JBxugS092482; Mon, 19 Jan 2009 12:59:57 +0100 (CET) (envelope-from Daan@vehosting.nl) From: Daan Vreeken Organization: VEHosting - Vitsch Electronics Hosting To: FreeBSD-PPC@FreeBSD.org Date: Mon, 19 Jan 2009 12:59:50 +0100 User-Agent: KMail/1.9.10 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901191259.50518.Daan@vehosting.nl> x-ve-auth-version: mi-1.0.3 2008-05-30 - Copyright (c) 2008 - Daan Vreeken - VEHosting x-ve-auth: authenticated as 'pa4dan' on VM01.VEHosting.nl Cc: FreeBSD-Embedded@FreeBSD.org Subject: PowerPC embedded board? X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2009 11:59:57 -0000 Hi all, For a new product I am looking for an embedded powerpc board. For the project we need the following : o A board that can (in the near future) boot FreeBSD. o Support for hardware floating point arithmetic. o The board should have some form of bus / IO to connect custom-made peripheral(s) to. Searching the internet I've already stumbled upon the Efika [1] and SAM440 [2] boards, which both look promising, but as far as my Google-skills go, it looks like both boards need more work to get FreeBSD fully functional on them. I'm thinking of buying a couple of boards and helping an interested developer by either setting up a compile & test environment that is accessible over ssh, or donating an entire board (or both :) So I've got some questions : o Are there more interresting boards I could/should consider? (Or even boards that can already run FreeBSD?) o What board is most likely to grow FreeBSD support in the near future? o What parts are currently missing to get these boards up and running? 1: http://www.efika.de/index_en.html , http://www.directron.com/efikakit1.html 2: http://sam440.com/eng/sam440ep-flex.html Kind regards, -- Daan Vreeken VEHosting http://VEHosting.nl tel: +31-(0)40-7113050 / +31-(0)6-46210825 KvK nr: 17174380 From owner-freebsd-ppc@FreeBSD.ORG Mon Jan 19 13:30:04 2009 Return-Path: Delivered-To: FreeBSD-PPC@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1104106566B; Mon, 19 Jan 2009 13:30:04 +0000 (UTC) (envelope-from raj@semihalf.com) Received: from semihalf.com (semihalf.com [206.130.101.55]) by mx1.freebsd.org (Postfix) with ESMTP id 922EF8FC0C; Mon, 19 Jan 2009 13:30:04 +0000 (UTC) (envelope-from raj@semihalf.com) Received: from mail.semihalf.com (mail.semihalf.com [83.15.139.206]) by semihalf.com (8.13.1/8.13.1) with ESMTP id n0JD63HO015008; Mon, 19 Jan 2009 06:06:04 -0700 Message-ID: <49747ABA.9090606@semihalf.com> Date: Mon, 19 Jan 2009 14:06:02 +0100 From: Rafal Jaworowski Organization: Semihalf MIME-Version: 1.0 To: Daan Vreeken References: <200901191259.50518.Daan@vehosting.nl> In-Reply-To: <200901191259.50518.Daan@vehosting.nl> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD-Embedded@FreeBSD.org, FreeBSD-PPC@FreeBSD.org Subject: Re: PowerPC embedded board? X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2009 13:30:05 -0000 Daan Vreeken wrote: > For a new product I am looking for an embedded powerpc board. For the project > we need the following : > o A board that can (in the near future) boot FreeBSD. > o Support for hardware floating point arithmetic. > o The board should have some form of bus / IO to connect custom-made > peripheral(s) to. Other than what you alrady pointed out, what is the overall profile of this deployment i.e. what level of horse power do you need, networking throughput etc.? > Searching the internet I've already stumbled upon the Efika [1] and SAM440 [2] > boards, which both look promising, but as far as my Google-skills go, it > looks like both boards need more work to get FreeBSD fully functional on > them. > I'm thinking of buying a couple of boards and helping an interested developer > by either setting up a compile & test environment that is accessible over > ssh, or donating an entire board (or both :) Both MPC5200 (Efika) and PPC440 (SAM440 and others) require quite a bit of work to turn into a reliable system to be used in a commercial product. They are both at a very similar stage: the kernel initially boots, interrupt controller driver ready, console (UART), work is in progress towards getting user-space pieces together, getting single user shell etc. In both cases virtually all remaining on-chip peripherals need respective drivers newly developed. > So I've got some questions : > o Are there more interresting boards I could/should consider? (Or even boards > that can already run FreeBSD?) > o What board is most likely to grow FreeBSD support in the near future? > o What parts are currently missing to get these boards up and running? Ready to use and stable is the port for higher-end PowerPC systems: PowerQUICC MPC85xx series based on the E500 (BookE) core. You'll find all integrated peripherals supported, although the default environment with regards to the floating point support is running with emulation and not native hard-floats (due to various implemetations of the FPU, or the lack of). Rafal From owner-freebsd-ppc@FreeBSD.ORG Mon Jan 19 15:18:12 2009 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72ACC106566B; Mon, 19 Jan 2009 15:18:12 +0000 (UTC) (envelope-from Daan@vehosting.nl) Received: from VM01.VEHosting.nl (unknown [IPv6:2001:470:1f14:32d::1:140]) by mx1.freebsd.org (Postfix) with ESMTP id 340508FC17; Mon, 19 Jan 2009 15:18:12 +0000 (UTC) (envelope-from Daan@vehosting.nl) Received: from [192.168.72.10] (124-54.bbned.dsl.internl.net [92.254.54.124]) (authenticated bits=0) by VM01.VEHosting.nl (8.14.3/8.13.8) with ESMTP id n0JFICfP098377; Mon, 19 Jan 2009 16:18:13 +0100 (CET) (envelope-from Daan@vehosting.nl) From: Daan Vreeken Organization: VEHosting - Vitsch Electronics Hosting To: freebsd-ppc@freebsd.org Date: Mon, 19 Jan 2009 16:18:06 +0100 User-Agent: KMail/1.9.10 References: <200901191259.50518.Daan@vehosting.nl> <49747ABA.9090606@semihalf.com> In-Reply-To: <49747ABA.9090606@semihalf.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901191618.06297.Daan@vehosting.nl> x-ve-auth-version: mi-1.0.3 2008-05-30 - Copyright (c) 2008 - Daan Vreeken - VEHosting x-ve-auth: authenticated as 'pa4dan' on VM01.VEHosting.nl Cc: FreeBSD-Embedded@freebsd.org Subject: Re: PowerPC embedded board? X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2009 15:18:13 -0000 Hi Rafal, On Monday 19 January 2009 14:06:02 Rafal Jaworowski wrote: > Daan Vreeken wrote: > > For a new product I am looking for an embedded powerpc board. For the > > project we need the following : > > o A board that can (in the near future) boot FreeBSD. > > o Support for hardware floating point arithmetic. > > o The board should have some form of bus / IO to connect custom-made > > peripheral(s) to. > > Other than what you alrady pointed out, what is the overall profile of this > deployment i.e. what level of horse power do you need, networking > throughput etc.? The processor will be used for coordinate transformations in a real-time position control system. We only need a small amount of memory. A network interface would be very nice to have, but it's only used for live debugging and to update software/firmware, so I could live without if needed. What I really need, is a processor that can do a fair amount sine / cosine's per second. I've done some tests with Linux on an MPC5200 board running at 400MHz. ( http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MPC5200 ) The processor has more than enough processing power to run our code, but I'm looking for a (preferably cheap) alternative that can run FreeBSD (with some help). > > Searching the internet I've already stumbled upon the Efika [1] and > > SAM440 [2] boards, which both look promising, but as far as my > > Google-skills go, it looks like both boards need more work to get FreeBSD > > fully functional on them. > > I'm thinking of buying a couple of boards and helping an interested > > developer by either setting up a compile & test environment that is > > accessible over ssh, or donating an entire board (or both :) > > Both MPC5200 (Efika) and PPC440 (SAM440 and others) require quite a bit of > work to turn into a reliable system to be used in a commercial product. > They are both at a very similar stage: the kernel initially boots, > interrupt controller driver ready, console (UART), work is in progress > towards getting user-space pieces together, getting single user shell etc. > In both cases virtually all remaining on-chip peripherals need respective > drivers newly developed. Given enough hardware documentation, I have no problem with writing a couple of drivers. The thing I'm not familiar with, is the lower level development of getting a new platform to run FreeBSD. (I have never touched FreeBSD's VM subsystem for example.) What would be needed to get either of these boards to a single user shell? > > So I've got some questions : > > o Are there more interresting boards I could/should consider? (Or even > > boards that can already run FreeBSD?) > > o What board is most likely to grow FreeBSD support in the near future? > > o What parts are currently missing to get these boards up and running? > > Ready to use and stable is the port for higher-end PowerPC systems: > PowerQUICC MPC85xx series based on the E500 (BookE) core. You'll find all > integrated peripherals supported, although the default environment with > regards to the floating point support is running with emulation and not > native hard-floats (due to various implemetations of the FPU, or the lack > of). What would be needed to get hardware floating point to be supported? Is it something that could be imported from NetBSD? Thanks, -- Daan Vreeken VEHosting http://VEHosting.nl tel: +31-(0)40-7113050 / +31-(0)6-46210825 KvK nr: 17174380 From owner-freebsd-ppc@FreeBSD.ORG Mon Jan 19 16:33:21 2009 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8EE09106564A; Mon, 19 Jan 2009 16:33:21 +0000 (UTC) (envelope-from raj@semihalf.com) Received: from semihalf.com (semihalf.com [206.130.101.55]) by mx1.freebsd.org (Postfix) with ESMTP id 541358FC18; Mon, 19 Jan 2009 16:33:21 +0000 (UTC) (envelope-from raj@semihalf.com) Received: from mail.semihalf.com (mail.semihalf.com [83.15.139.206]) by semihalf.com (8.13.1/8.13.1) with ESMTP id n0JGXIOO008714; Mon, 19 Jan 2009 09:33:19 -0700 Message-ID: <4974AB4D.9040204@semihalf.com> Date: Mon, 19 Jan 2009 17:33:17 +0100 From: Rafal Jaworowski Organization: Semihalf MIME-Version: 1.0 To: Daan Vreeken References: <200901191259.50518.Daan@vehosting.nl> <49747ABA.9090606@semihalf.com> <200901191618.06297.Daan@vehosting.nl> In-Reply-To: <200901191618.06297.Daan@vehosting.nl> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD-Embedded@freebsd.org, freebsd-ppc@freebsd.org Subject: Re: PowerPC embedded board? X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2009 16:33:22 -0000 Hi Daan, Daan Vreeken wrote: >>> Searching the internet I've already stumbled upon the Efika [1] and >>> SAM440 [2] boards, which both look promising, but as far as my >>> Google-skills go, it looks like both boards need more work to get FreeBSD >>> fully functional on them. >>> I'm thinking of buying a couple of boards and helping an interested >>> developer by either setting up a compile & test environment that is >>> accessible over ssh, or donating an entire board (or both :) >> Both MPC5200 (Efika) and PPC440 (SAM440 and others) require quite a bit of >> work to turn into a reliable system to be used in a commercial product. >> They are both at a very similar stage: the kernel initially boots, >> interrupt controller driver ready, console (UART), work is in progress >> towards getting user-space pieces together, getting single user shell etc. >> In both cases virtually all remaining on-chip peripherals need respective >> drivers newly developed. > > Given enough hardware documentation, I have no problem with writing a couple > of drivers. The thing I'm not familiar with, is the lower level development > of getting a new platform to run FreeBSD. (I have never touched FreeBSD's VM > subsystem for example.) > What would be needed to get either of these boards to a single user shell? We're almost there with regards to running from ramdisk based mini-root fs. In case of a more elaborate (full) environment you'd need some kind of storage for the root fs: 1. MPC5200 - built-in ATA controller (getting this to work with DMA will be painful as relies on bringing operation to the microcode-based BestComm engine first) - built-in USB (OHCI), should be relatively easy, with a bit of luck only bus attachment is required 2. 440EP - no integrated S/ATA, the SAM board you mentioned has some external Silicon Image controller, so a driver would be needed for that - built-in USB (not sure if this has any standard host I/F implementation though) >>> So I've got some questions : >>> o Are there more interresting boards I could/should consider? (Or even >>> boards that can already run FreeBSD?) >>> o What board is most likely to grow FreeBSD support in the near future? >>> o What parts are currently missing to get these boards up and running? >> Ready to use and stable is the port for higher-end PowerPC systems: >> PowerQUICC MPC85xx series based on the E500 (BookE) core. You'll find all >> integrated peripherals supported, although the default environment with >> regards to the floating point support is running with emulation and not >> native hard-floats (due to various implemetations of the FPU, or the lack >> of). > > What would be needed to get hardware floating point to be supported? Is it > something that could be imported from NetBSD? Note we're talking about hard-floats for Book-E systems, which are very different from the traditional PowerPC FPU. Since NetBSD doesn't have support for any Book-E system, so it wouldn't be of direct help I think. There are at least two ways to support this: - gcc level - newer gcc (4.2.x IIRC) are able to produce machine code for native E500 FP - interface libc with native E500 FP Neither should be enormously difficult, so let me know if you'd like to work on this :-) The problem is in varieties: some Book-E cores don't have the FP APU and from the FreeBSD/powerpc project perspective we'd need something flexible and uniform enough so that different core variations still work (not to mention the traditional, AIM, PowerPC FPU..). Rafal From owner-freebsd-ppc@FreeBSD.ORG Tue Jan 20 00:14:41 2009 Return-Path: Delivered-To: freebsd-ppc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D9A01065670 for ; Tue, 20 Jan 2009 00:14:41 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from smtp8.server.rpi.edu (smtp8.server.rpi.edu [128.113.2.228]) by mx1.freebsd.org (Postfix) with ESMTP id D8B678FC08 for ; Tue, 20 Jan 2009 00:14:40 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp8.server.rpi.edu (8.13.1/8.13.1) with ESMTP id n0JNDGHq030484 for ; Mon, 19 Jan 2009 18:13:17 -0500 Mime-Version: 1.0 Message-Id: Date: Mon, 19 Jan 2009 18:13:16 -0500 To: freebsd-ppc@FreeBSD.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Bayes-Prob: 0.0001 (Score 0) X-RPI-SA-Score: 0.00 () [Hold at 20.00] 22490(-25) X-CanItPRO-Stream: outgoing X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.228 Cc: Subject: Best options for disk-formatting on PowerPC? (mac-mini) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2009 00:14:41 -0000 It's so rare that I have to partition a disk that I'm pretty sure my knowledge is out-of-date, especially on PowerPC. The last time I did any disk partitioning on PowerPC was back in early 2005! If I go to http://www.FreeBSD.org/platforms/ppc.html for advice, the "How can I install FreeBSD/ppc" section says "Please follow the instructions ", where "" is: http://people.freebsd.org/~grehan/iso_install.txt That, in turn, is the ISO_INSTALL.txt file from 6.0-RELEASE, a page which is also linked to from: http://wiki.freebsd.org//powerpc None of these say much about partitioning. What I have is a new-to-me MacMini, with a brand new disk in it, and nothing installed on that disk. I also have an external FW drive which has all the freebsd filesystems from my other Mac-Mini install. I've just updated the system on that drive so it is the up-to-date version of FreeBSD 7.1-STABLE. What I want to end up with is the new internal disk with two bootable MacOS partitions, two OFW-bootable partitions (one for 7.x, one for 8.x), one swap partition, and a few other filesystems for freebsd. Since I want bootable partitions, as far as Apple is concerned the disk has to be partitioned as "Apple Partition Map". Once I create the freebsd partitions, I'd want to use dump/restore to copy the partitions from the older firedrive to the internal HD on the newer Mac-Mini. If I start with Apple's "Disk Utility" app for the first cut at partitioning, I can use the version on MacOS 10.4 or 10.5. The last time I did this, I used the 10.4 version to create a few unix volumes. I notice that if I use the 10.5 version of that Apple utility, there is no option for unix-formatted volumes. So I took the new mac-mini and booted it into firewire target mode. I hooked that and my other firewire disk up to the older mac mini, and booted that Mac-mini into MacOS 10.4. = = = = = = = = = = = = And here I am, about 12 attempts later, and I still haven't gotten the freebsd partitions from the external FW disk to the new internal disk. I did a number of things that seemed plausible, and while MacOS was always happy with the disk in the new Mac-Mini, I could never get sysinstall on my 7.x FreeBSD system to see that disk, or any of the volumes that Disk Utility created on that disk. I'm still plugging away at my latest attempt, but I thought that maybe I should ask if there is some standard strategy that I should be following. Or might there be a problem with having two firewire disks connected at the same time? Or might there be a problem with freebsd talking to a "firewire disk" which is really some other Mac in FW Target mode? I've started to write a request for help in the middle of each of my other attempts, and kept stopping myself when I thought of "just one more thing" I should try before asking. I think I'm going to send this one out while I'm waiting for my latest MacOS install to finish, and follow up with more details if my latest idea doesn't work. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-ppc@FreeBSD.ORG Tue Jan 20 00:23:24 2009 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0CD2A1065670 for ; Tue, 20 Jan 2009 00:23:24 +0000 (UTC) (envelope-from nwhitehorn@banshee.munuc.org) Received: from banshee.munuc.org (unknown [IPv6:2001:4978:11f:d600::d610]) by mx1.freebsd.org (Postfix) with ESMTP id C88238FC1B for ; Tue, 20 Jan 2009 00:23:23 +0000 (UTC) (envelope-from nwhitehorn@banshee.munuc.org) Received: from nwhitehorn (helo=localhost) by banshee.munuc.org with local-esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LP4Oo-000B88-Dq; Mon, 19 Jan 2009 18:23:22 -0600 Date: Mon, 19 Jan 2009 18:23:22 -0600 (CST) From: Nathan Whitehorn X-X-Sender: nwhitehorn@banshee.munuc.org To: Ed Schouten In-Reply-To: <20081102184335.GT1165@hoeg.nl> Message-ID: References: <20081102171754.GS1165@hoeg.nl> <490DE209.4020109@freebsd.org> <20081102184335.GT1165@hoeg.nl> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: Nathan Whitehorn X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: nwhitehorn@banshee.munuc.org X-SA-Exim-Scanned: No (on banshee.munuc.org); SAEximRunCond expanded to false Cc: FreeBSD/ppc Subject: Re: ADB mouse fixup X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2009 00:23:24 -0000 On Sun, 2 Nov 2008, Ed Schouten wrote: > * Nathan Whitehorn wrote: >> That is really strange. As it happens, the code currently there for high >> buttons is to handle an external ALPS Glidepoint touchpad I have with 3 >> buttons that gives button events on buttons 1,2, and 4. The rest of my >> hardware behaves correctly, and the ALPS device reports itself as a >> mouse, not a trackpad, so I think the patch is fine. Crazy Apple >> hardware... > > Yeah, it is pretty strange. Though I think we may find this useful in > the future. Each time you use the touch pad, it reports button 5 events. > I suspect that when you use two fingers (not supported by my model) it > returns a different button, though I can't confirm. > > I see there's also another small issue with my touch pad. For some > reason X11 doesn't process any click events if I don't move the pointer > after I've clicked/released the button. I'll investigate. > You might want to look at the NetBSD ams driver. It sends a bunch of magic packets to initialize trackpads. Maybe there is something in there that could solve it? Also, the P4 bwi driver seems to work well on PPC. I'm typing this over my wireless connection on my G4 iBook right now. -Nathan From owner-freebsd-ppc@FreeBSD.ORG Tue Jan 20 05:14:32 2009 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 94375106564A for ; Tue, 20 Jan 2009 05:14:32 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from smtp8.server.rpi.edu (smtp8.server.rpi.edu [128.113.2.228]) by mx1.freebsd.org (Postfix) with ESMTP id 3A37F8FC13 for ; Tue, 20 Jan 2009 05:14:31 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp8.server.rpi.edu (8.13.1/8.13.1) with ESMTP id n0K5ERAk015306 for ; Tue, 20 Jan 2009 00:14:29 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Tue, 20 Jan 2009 00:14:27 -0500 To: freebsd-ppc@freebsd.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Bayes-Prob: 0.0001 (Score 0) X-RPI-SA-Score: 1.20 (*) [Hold at 20.00] J_CHICKENPOX_42, J_CHICKENPOX_43, 22490(-25) X-CanItPRO-Stream: outgoing X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.228 Subject: Re: Best options for disk-formatting on PowerPC? (mac-mini) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2009 05:14:37 -0000 At 6:13 PM -0500 1/19/09, Garance A Drosihn wrote: > >What I have is a new-to-me MacMini, with a brand new disk in it, and >nothing installed on that disk. I also have an external FW drive >which has all the freebsd filesystems from my other Mac-Mini install. >I've just updated the system on that drive so it is the up-to-date >version of FreeBSD 7.1-STABLE. >So I took the new mac-mini and booted it into firewire target mode. >I hooked that and my other firewire disk up to the older mac mini, >and booted that Mac-mini into MacOS 10.4. Well, I've made some progress, but I still don't understand all of what went on. At this point I'm pretty tired out after spending most of the weekend on it, so this won't cover all the details. At the end, you'll see that I do have it booting, but there's some things it would be nice to fix (if possible!). Older mini: PPC 1.42 GHz Newer mini: PPC 1.50 GHz (with brand new empty HD) External disk: One of those combination disk/FW-hub/USB-hub things which is the same size and shape as a Mac Mini. All freebsd partitions (except swap) were on the external FW drive. It has 6.x and 7.x systems. It seemed the easiest way to get things from the old MM and the HD to the new MM was to put the new MM into FW target mode, and then connect the hub to the old MM, and the new MM to the hub. So I did, and booted up 10.4. wbich was installed on the old MM. First I partitioned the new disk to have several unix partitions, with two MacOS partitions at the end of the disk. I then booted into 7.x, and the FW disk in the hub had moved from device "da0*" to "da1*" (due to the new MM being "da0*". I fixed fstab, rebooted, and everything I tried seemed to work fine... EXCEPT: Apparently FreeBSD couldn't see the individual partitions under /dev/da0s* , even though it had no trouble finding all the ones under /dev/da1s* . There was a /dev/da0, but no slices under it. I tried running sysinstall, and it would only let me select disks AD0 or DA1 . I tried several ways to get around this, with no luck. It occurred to me that every other time I had done this, I always and a MacOS volume as the first partition on the disk. So I rebooted into MacOS, and reformatted the new disk with one MacOS partition, several Unix partitions, and then a second MacOS volume. I then rebooted back into freebsd 7.x, and now the FW disk in the older hub had moved back to "da0". I fixed fstab to match, and rebooted again. Now I had /dev/ad0* and /dev/da0*, but no /dev/da1 at all. Absolutely no evidence that I had two firewire drives, even though both drives looked and worked perfectly fine in MacOS. Fine. I shut everything down, disconnected the old MM, and plugged the FW disk+hub into the new MM. Installed MacOS 10.4 into the new MM, and booted up off of that. Everything looks fine. I then rebooted into openfirmware, and typed in the commands: show-devs fw boot hd:3,fbsd_loader fw/:9 partition 9 is the /-filesystem for the 7.x system. Total death. The loader does start up, but it complains that it can't load the kernel and drops back to a user prompt. I then ask it to "lsdev" -- and it claims it can't find *any* devices! I power down, power back up, and try this again. Again it fails, in the exact same way. Eventually I boot up the 6.x system on the external FW disk. It boots up perfectly fine (except that I have to fix fstab yet again!). I have several things I want to check out, and reboot several times into 6.x. No problems. I try to boot into 7.x again. It fails again, but in staring at the screen I realize I typo'ed the part. Redo. Fails. I again notice I typo'ed it. Redo. This time I make absolutely certain I type in the right string before hitting 'return'. It fails. Redo. It fails. Redo again. It fails. It occurs to me that for at least some of those attempts, I had started typo the strong, but noticed the error before hitting 'return'. So I just hit the 'delete' key to remove the error, and re-typed it. And each time after it failed, I would even do a 'show' command in the loader, and I could see that the string it picked up looked exactly like I expected it to. I tried one more time, and this time I made sure I didn't make any mistakes, and never had to hit the delete key. This time it works! Apparently I typo'ed (one way or another) every time I tried to boot into 7.x, but never when booting into 6.x. I managed to do this even though the only difference between the two boot commands is the last digit I have to type. Geez, what are the odds? What's worse, I have a vague feeling that I ran into this same problem when doing the initial installs on my first Mac-mini. I haven't had the problem for years now, because I defined a device alias in open-firmware on the older MM, so for years all I've had to type is: boot hd:3,fbsd_loader fw-d0:9 I'll define another device-alias in the new MM, once I figure out how I want the disk partitioned. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-ppc@FreeBSD.ORG Tue Jan 20 05:49:24 2009 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC79B1065670 for ; Tue, 20 Jan 2009 05:49:24 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from smtp5.server.rpi.edu (smtp5.server.rpi.edu [128.113.2.225]) by mx1.freebsd.org (Postfix) with ESMTP id A12C58FC0C for ; Tue, 20 Jan 2009 05:49:24 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp5.server.rpi.edu (8.13.1/8.13.1) with ESMTP id n0K5nMFY002066 for ; Tue, 20 Jan 2009 00:49:22 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Tue, 20 Jan 2009 00:49:21 -0500 To: freebsd-ppc@freebsd.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Bayes-Prob: 0.0001 (Score 0) X-RPI-SA-Score: 0.00 () [Hold at 20.00] 22490(-25) X-CanItPRO-Stream: outgoing X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.225 Subject: Re: Best options for disk-formatting on PowerPC? (mac-mini) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2009 05:49:25 -0000 At 12:14 AM -0500 1/20/09, Garance A Drosihn wrote: >At 6:13 PM -0500 1/19/09, Garance A Drosihn wrote: >> >>What I have is a new-to-me MacMini, with a brand new disk in it, and >>nothing installed on that disk. I also have an external FW drive >>which has all the freebsd filesystems from my other Mac-Mini install. >>I've just updated the system on that drive so it is the up-to-date >>version of FreeBSD 7.1-STABLE. >I'll define another device-alias in the new MM, once I figure out >how I want the disk partitioned. Okay, now I can finally get to writing the real question that I had, before I got bogged down in what I expected to be *simple* steps... What I wanted to end up with is filesystems such as: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/disk1s3 33842792 35092 33807700 0% /Volumes/MmP15_10p4T /dev/disk1s5 10414889 8 9894137 0% /Volumes/7x-root /dev/disk1s7 11776292 8 11187470 0% /Volumes/8x-root /dev/disk1s9 3140772 8 2983726 0% /Volumes/fb_swap /dev/disk1s11 1515374 8 1439598 0% /Volumes/7x-var /dev/disk1s13 1718486 8 1632554 0% /Volumes/8x-var /dev/disk1s15 8006984 8 7606627 0% /Volumes/fb_mkobj /dev/disk1s17 6635601 8 6303813 0% /Volumes/fb_Users /dev/disk1s19 38456984 35232 38421752 0% /Volumes/MmP15_10p5L Actually I would have liked to end up with even more freebsd filesystems than that, but there's a problem which comes up. The above is how the filesystems were listed by 'df -kl' under MacOS, right after I had finished partitioning the new disk with DiskUtility.app . While that is what MacOS *shows*, you can see a glimpse of the problem. Notice that the device names are "disk1s3", "disk1s5", "disk1s7", etc. For every unix partition that I ask DiskUtility.app, it really creates two partitions, thus throwing away one partition-slot which I can not really use in freebsd. The unix command 'diskutil list /dev/disk1' (under MacOS) shows: /dev/disk1 #: type name size identifier 0: Apple_partition_scheme *111.8 GB disk1 1: Apple_partition_map 31.5 KB disk1s1 ( no entry listed for "disk1s2" ) 2: Apple_HFS MmP15_10p4T 32.3 GB disk1s3 3: Apple_Boot 8.5 MB disk1s4 4: Apple_UFS 7x-root 9.9 GB disk1s5 5: Apple_Boot 8.5 MB disk1s6 6: Apple_UFS 8x-root 11.2 GB disk1s7 7: Apple_Boot 8.5 MB disk1s8 8: Apple_UFS fb_swap 3.0 GB disk1s9 9: Apple_Boot 8.5 MB disk1s10 10: Apple_UFS 7x-var 1.4 GB disk1s11 11: Apple_Boot 8.5 MB disk1s12 12: Apple_UFS 8x-var 1.6 GB disk1s13 13: Apple_Boot 8.5 MB disk1s14 14: Apple_UFS fb_mkobj 7.6 GB disk1s15 15: Apple_Boot 8.5 MB disk1s16 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 16: Apple_UFS fb_Users 6.3 GB disk1s17 17: Apple_HFS MmP15_10p5L 36.7 GB disk1s19 It's all those 8.5-meg "Apple_Boot" partitions which are screwing things up on me. The problem is that disklabel on FreeBSD will only show me the first sixteen of the partitions that it finds (it stops where that dotted line is). So, I can't actually *use* the partition which I created as "fb_users". So, finally, my freebsd-partitioning question: Is there something I could do with GEOM and gpart such that I could tell MacOS I want "just one" unix partition, and then on the freebsd side of things I could carve that "one" partition into several ones. I can see dedicating MacOS-visible partitions for 7x-root and 8x-root, since I assume openfirmware needs to have some idea of those to boot up. And it's fine to dedicate another MacOS-visible partition for swap. But after that it'd be mighty convenient if I could create just one more MacOS-visible partition, and then use something on freebsd to split that into 7x-var, 8x-var, fb_mkobj, and fb_users. Or is there some way to get FreeBSD to notice more than 16 of these partitions that MacOS wants to create? We couldn't get freebsd to skip over all those 8.5-meg "Apple_Boot" partitions, could we? -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-ppc@FreeBSD.ORG Wed Jan 21 05:26:09 2009 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ACFF1106566B for ; Wed, 21 Jan 2009 05:26:09 +0000 (UTC) (envelope-from upakul@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.191]) by mx1.freebsd.org (Postfix) with ESMTP id 426238FC13 for ; Wed, 21 Jan 2009 05:26:08 +0000 (UTC) (envelope-from upakul@gmail.com) Received: by fk-out-0910.google.com with SMTP id f40so141257fka.11 for ; Tue, 20 Jan 2009 21:26:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=DFy+zgcr0xNMnVFhqAQ5fsGLqUlicOErd3YqAeTQzxA=; b=xcPnytt2+wWjlJxU4I+wh89nrAznindO9XPL2zBaYXMVw01UbKdAFth/v0quee76W/ qgnagPrsEsTxq/ZmVMSwk+btytBBUiOwn4bNSScA29PABE8NgtO1B5LBHPnLsQwUStsb jMaQJNETmrQJPVeW7nJdCY3bEnjPa+LSa18yw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=s5uixBcUeJ5gYTjMNKGiEIFi2KyoGoc8G6WLAkfFQNT/iIFwQnL3eNRzj+FooOuSlU jhVWgFrPGidvadNADryfx6vD0jJFY0UcnDwdGv4iJlefhLim9HH2IbvA6Z2ricAvSo0T /AyvwnhL/oWgaBCor0te9cAG9wqotV/oCYjwk= MIME-Version: 1.0 Received: by 10.103.240.5 with SMTP id s5mr2472048mur.106.1232513845061; Tue, 20 Jan 2009 20:57:25 -0800 (PST) Date: Wed, 21 Jan 2009 10:27:24 +0530 Message-ID: From: Upakul Barkakaty To: freebsd-ppc@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: USB Device connected to PCI express not working on mpc8641d X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 05:26:09 -0000 Hi all, Looks like I have been hit by another of these pci setup issues. My Setup is as follows: [MPC8614D]--[PCI Express]--[PCIe to PCI bridge]--[NEC USB Host controller card]-->[USB Pen Drive] The same USB card and drivers are working on another board, where the bus is PCI. I tried to debug the USB driver, and it seems to be booting up fine. Even the interrupt handling seems proper. So I come down to the grey area, that is PCIe. The USB host controllers seem to initialize fine and are detected by the PCI utilities. However when I connect a USB device, then it fails @ set addree or get descriptor, whichever transaction is first. So I had a few questions: 1. The processor CCSRBAR map has a PCI Express entry. Am I required to make another entry into the LAWBAR registers for PCI express? 2. Does the PCIe to PCI bridge need to be configured for the inbound/ outbound windows or read/write routines...anything in particular? 3. How do I verify that the PCIe inbound/outbound windows are mapped correctly? Any other setting which needs to be done in this case? Any pointers in this regard will be highly appreciated. Thanks From owner-freebsd-ppc@FreeBSD.ORG Thu Jan 22 02:08:02 2009 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DFD4B106566B for ; Thu, 22 Jan 2009 02:08:02 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from smtp5.server.rpi.edu (smtp5.server.rpi.edu [128.113.2.225]) by mx1.freebsd.org (Postfix) with ESMTP id 8B0BE8FC0A for ; Thu, 22 Jan 2009 02:08:02 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp5.server.rpi.edu (8.13.1/8.13.1) with ESMTP id n0M2809F002764 for ; Wed, 21 Jan 2009 21:08:01 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Wed, 21 Jan 2009 21:08:00 -0500 To: freebsd-ppc@freebsd.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Bayes-Prob: 0.0001 (Score 0) X-RPI-SA-Score: 0.00 () [Hold at 20.00] 22490(-25) X-CanItPRO-Stream: outgoing X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.225 Subject: Re: Best options for disk-formatting on PowerPC? (mac-mini) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2009 02:08:03 -0000 At 12:49 AM -0500 1/20/09, Garance A Drosihn wrote: > >Or is there some way to get FreeBSD to notice more than 16 of these >partitions that MacOS wants to create? We couldn't get freebsd to >skip over all those 8.5-meg "Apple_Boot" partitions, could we? Well, after some sleep and doing a little more work, I seem to have things working fine wrt the partitions. When running an up-to-date build of 7.x, FreeBSD is able to use all the partitions. Due to the confusion caused by my typos in openfirmware, some of my work was done while using an older 6.2-era build, and that's the one which had the limit on partitions. There's still the initial issue I had when trying to work with two firewire drives (one of which was the older MacMini plugged into the external-FW-drive/hub), and I know that problem *is* in the 7.x system, but other than that most of my problems were due to my own mistakes. So no coding changes are needed. Just need to fix the nut who's punching the keyboard. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-ppc@FreeBSD.ORG Thu Jan 22 08:10:32 2009 Return-Path: Delivered-To: powerpc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4975106567A; Thu, 22 Jan 2009 08:10:32 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 89BBB8FC1F; Thu, 22 Jan 2009 08:10:32 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0M8AT1S051276; Thu, 22 Jan 2009 03:10:29 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [64.7.128.103]) by smtp1.sentex.ca (8.14.3/8.14.3) with ESMTP id n0M8ATwR087793; Thu, 22 Jan 2009 03:10:29 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-stable.sentex.ca (Postfix, from userid 666) id 136331B5060; Thu, 22 Jan 2009 03:10:29 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20090122081029.136331B5060@freebsd-stable.sentex.ca> Date: Thu, 22 Jan 2009 03:10:29 -0500 (EST) X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [releng_7 tinderbox] failure on powerpc/powerpc X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2009 08:10:33 -0000 TB --- 2009-01-22 06:56:08 - tinderbox 2.6 running on freebsd-stable.sentex.ca TB --- 2009-01-22 06:56:08 - starting RELENG_7 tinderbox run for powerpc/powerpc TB --- 2009-01-22 06:56:08 - cleaning the object tree TB --- 2009-01-22 06:56:29 - cvsupping the source tree TB --- 2009-01-22 06:56:29 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/powerpc/powerpc/supfile TB --- 2009-01-22 06:56:40 - building world TB --- 2009-01-22 06:56:40 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-22 06:56:40 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-22 06:56:40 - TARGET=powerpc TB --- 2009-01-22 06:56:40 - TARGET_ARCH=powerpc TB --- 2009-01-22 06:56:40 - TZ=UTC TB --- 2009-01-22 06:56:40 - __MAKE_CONF=/dev/null TB --- 2009-01-22 06:56:40 - cd /src TB --- 2009-01-22 06:56:40 - /usr/bin/make -B buildworld >>> World build started on Thu Jan 22 06:56:41 UTC 2009 >>> 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 Jan 22 08:02:21 UTC 2009 TB --- 2009-01-22 08:02:21 - generating LINT kernel config TB --- 2009-01-22 08:02:21 - cd /src/sys/powerpc/conf TB --- 2009-01-22 08:02:21 - /usr/bin/make -B LINT TB --- 2009-01-22 08:02:21 - building LINT kernel TB --- 2009-01-22 08:02:21 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-22 08:02:21 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-22 08:02:21 - TARGET=powerpc TB --- 2009-01-22 08:02:21 - TARGET_ARCH=powerpc TB --- 2009-01-22 08:02:21 - TZ=UTC TB --- 2009-01-22 08:02:21 - __MAKE_CONF=/dev/null TB --- 2009-01-22 08:02:21 - cd /src TB --- 2009-01-22 08:02:21 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Jan 22 08:02:21 UTC 2009 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -Werror /src/sys/dev/usb/uhid.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -Werror /src/sys/dev/usb/uhub.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -Werror /src/sys/dev/usb/uipaq.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -Werror /src/sys/dev/usb/ukbd.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -Werror /src/sys/dev/usb/ulpt.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -Werror /src/sys/dev/usb/umass.c /src/sys/dev/usb/umass.c:577: error: 'USB_PRODUCT_NETAC_ONLYDISK' undeclared here (not in a function) /src/sys/dev/usb/umass.c:613: error: 'USB_PRODUCT_ONSPEC_SDS_HOTFIND_D' undeclared here (not in a function) *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-01-22 08:10:28 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-22 08:10:28 - ERROR: failed to build lint kernel TB --- 2009-01-22 08:10:28 - 3658.32 user 362.18 system 4460.30 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-powerpc-powerpc.full