From owner-freebsd-sparc64@FreeBSD.ORG Mon Dec 8 10:59:52 2008 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C52CD106564A for ; Mon, 8 Dec 2008 10:59:52 +0000 (UTC) (envelope-from beat.gaetzi@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159]) by mx1.freebsd.org (Postfix) with ESMTP id 2375F8FC0C for ; Mon, 8 Dec 2008 10:59:51 +0000 (UTC) (envelope-from beat.gaetzi@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so1325267fgb.35 for ; Mon, 08 Dec 2008 02:59:51 -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:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=Ac2X19T+v3gnFDZmH2mBmhLcH2ZEhbd2kPG/EHmiKdY=; b=HWJ4p7pUdymH0w2F9gNHhPc/IF7H0LLawynReoYChkmdcZljCwKCa5EXms6LE5oVIl TIMpqgHY1TYQw5kLA72MZxU3A2bI69a0D/UPJ+rIXGSvZGIT4600D2XUciemBcw0bix6 Q/okD9E6ZP1PwSqXk0bxUnLtj1GO6ksElcJw0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=GJlsnJA8wdRu8t/CO5lrXShEnkfonDTVrq/GolDjAthF0cCzKEoQqXH1hFwuzQOHh1 HnEYviCKXiFm5VcDvilvC0SMbYIJ++8NxKGqtwDt/b6eJGX6v02YKVGQG/d6kTLOXYQ/ Gz8Tkc2hkI6W2Q6Fbpqc4Dqltbsuiqt5gGkb4= Received: by 10.86.79.19 with SMTP id c19mr2520306fgb.66.1228733991045; Mon, 08 Dec 2008 02:59:51 -0800 (PST) Received: by 10.86.4.11 with HTTP; Mon, 8 Dec 2008 02:59:50 -0800 (PST) Message-ID: <26f6c7210812080259j1cc1cb3bo2fe827a8442f068a@mail.gmail.com> Date: Mon, 8 Dec 2008 11:59:50 +0100 From: "=?ISO-8859-1?Q?Beat_G=E4tzi?=" Sender: beat.gaetzi@gmail.com To: "Marius Strobl" In-Reply-To: <20081205172112.GA52382@alchemy.franken.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4935839E.4010000@chruetertee.ch> <20081204180726.GA19048@alchemy.franken.de> <26f6c7210812050014l5dac2871k7ca1db1677d0b7d0@mail.gmail.com> <20081205172112.GA52382@alchemy.franken.de> X-Google-Sender-Auth: e448d2fbd41da7dc Cc: freebsd-sparc64@freebsd.org Subject: Re: Booting of 200811 snapshot on Sun Fire V880 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2008 10:59:52 -0000 2008/12/5 Marius Strobl : > On Fri, Dec 05, 2008 at 09:14:03AM +0100, Beat Gtzi wrote: >> 2008/12/4 Marius Strobl : >> > On Tue, Dec 02, 2008 at 07:51:10PM +0100, Beat Gtzi wrote: >> >> Hi, >> >> >> >> I'm trying to boot the 8.0-CURRENT-200811-sparc64-disc1.iso on a Sun >> >> Fire V880 but it failed: >> >> >> >> 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-200811 #0: Sun Nov 2 08:50:52 UTC 2008 >> >> root@drazen.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC >> >> WARNING: WITNESS option enabled, expect reduced performance. >> >> real memory = 8589934592 (8192 MB) >> >> avail memory = 8377745408 (7989 MB) >> >> cpu0: Sun Microsystems UltraSparc-III Processor (750.00 MHz CPU) >> >> cpu1: Sun Microsystems UltraSparc-III Processor (750.00 MHz CPU) >> >> cpu2: Sun Microsystems UltraSparc-III Processor (750.00 MHz CPU) >> >> cpu3: Sun Microsystems UltraSparc-III Processor (750.00 MHz CPU) >> >> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs >> >> registered firmware set >> >> registered firmware set >> >> registered firmware set >> >> registered firmware set >> >> registered firmware set >> >> registered firmware set >> >> registered firmware set >> >> registered firmware set >> >> registered firmware set >> >> registered firmware set >> >> registered firmware set >> >> registered firmware set >> >> kdb0 at kdbmux0 >> >> panic: trap: fast data access mmu miss >> >> cpuid = 0 >> >> KDB: enter: panic >> >> [thread pid 0 tid 100000 ] >> >> Stopped at kdb_enter+0x80: ta %xcc, 1 >> >> db> bt >> >> Tracing pid 0 tid 100000 td 0xc082f530 >> >> panic() at panic+0x20c >> >> trap() at trap+0x570 >> >> -- fast data access mmu miss tar=0 %o7=0xc0123530 -- >> >> dcons_init_port() at dcons_init_port+0x7c >> >> dcons_drv_init() at dcons_drv_init+0x144 >> >> dcons_modevent() at dcons_modevent+0x20 >> >> module_register_init() at module_register_init+0xdc >> >> mi_startup() at mi_startup+0x18c >> >> btext() at btext+0x30 >> >> db> >> >> >> >> POST/diagnostic boot don't show any errors hence I think this is not a >> >> hardware error. I already tried a reset-all on OBP, to power-cycle the >> >> machine and updating OBP to the latest version (4.22.34) but it still >> >> fails. Any hints? >> >> >> > >> > Could you please give the image at: >> > http://people.freebsd.org/~marius/8.0-20081203-SNAP-sparc64-disc1.iso.gz >> > a try? >> >> Thanks for the new image. Unfortunately it still fails at: >> >> kdb0 at kdbmux0 >> panic: trap: fast data access mmu miss >> cpuid = 0 >> KDB: enter: panic >> [thread pid 0 tid 100000 ] >> Stopped at kdb_enter+0x80: ta %xcc, 1 >> db> bt >> Tracing pid 0 tid 100000 td 0xc0848780 >> panic() at panic+0x20c >> trap() at trap+0x570 >> -- fast data access mmu miss tar=0 %o7=0xc0166070 -- >> dcons_init_port() at dcons_init_port+0x7c >> dcons_drv_init() at dcons_drv_init+0x144 >> dcons_modevent() at dcons_modevent+0x20 >> module_register_init() at module_register_init+0xdc >> mi_startup() at mi_startup+0x18c >> btext() at btext+0x30 >> db> >> > > Ah, I goofed the change, sorry. Could you please try: > http://people.freebsd.org/~marius/8.0-20081205-SNAP-sparc64-disc1.iso.gz > instead? If that also fails could you provide temporary > remote access to a netboot environment? The new image solves the initial issue but now it fails at: [...] gem0: Ethernet address: 00:03:ba:xx:xx:xx gem0: [ITHREAD] isp0: port 0x300-0x3ff mem 0x400000-0x400fff at device 2.0 on pci1 isp0: [ITHREAD] isp0: Board Type 2200, Chip Revision 0x5, loaded F/W Revision 2.2.6 isp0: invalid NVRAM header isp0: invalid NVRAM header pcib2: mem 0x40004f00000-0x40004f17fff,0x40004c10000-0x40004c1004f,0x7ffea000000-0x7ffea0000ff irq 627,624,625,628,629 on nexus0 pcib2: Schizo, version 4, IGN 0x9, bus B, 33MHz pcib2: DVMA map: 0xc0000000 to 0xffffffff pcib2: [FILTER] pci2: on pcib2 ebus0: mem 0x7d000000-0x7dffffff,0x7e000000-0x7e7fffff at device 1.0 on pci2 ebus0: addr 0-0x1fffff (no driver attached) ebus0: addr 0x100000000-0x1000fffff (no driver attached) ebus0: addr 0x10030002e-0x10030002f,0x100300600-0x100300607 (no driver attached) ebus0: addr 0x10000002e-0x10000002f,0x10000002d irq 35 (no driver attached) ebus0: addr 0x100000030-0x100000031 irq 35 (no driver attached) ebus0: addr 0x100500000-0x1005fffff (no driver attached) ebus0: addr 0x10050002e-0x10050002f,0x10050002d irq 40 (no driver attached) ebus0: addr 0x100500030-0x100500031 irq 40 (no driver attached) rtc0: addr 0x100300070-0x100300071 irq 36 on ebus0 ebus0: addr 0x100300600-0x100300607 (no driver attached) ebus0: addr 0x100300700-0x100300701 (no driver attached) uart0: <16550 or compatible> addr 0x1003062f8-0x1003062ff irq 46 on ebus0 uart0: [FILTER] uart1: <16550 or compatible> addr 0x1003083f8-0x1003083ff irq 45 on ebus0 uart1: [FILTER] scc0: addr 0x100400000-0x10040007f irq 34 on ebus0 scc0: [FILTER] uart2: on scc0 uart2: [FILTER] uart2: CTS oflow uart2: console (9600,n,8,1) uart3: on scc0 uart3: [FILTER] uart3: CTS oflow gem1: mem 0x100000-0x11ffff at device 1.1 on pci2 miibus1: on gem1 ukphy0: PHY 1 on miibus1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto gem1: 2kB RX FIFO, 2kB TX FIFO gem1: Ethernet address: 00:03:ba:xx:xx:xx gem1: [ITHREAD] ohci0: mem 0x1000000-0x1007fff at device 1.3 on pci2 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: <(0x108e) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0 uhub0: 4 ports with 4 removable, self powered pcib3: at device 2.0 on pci2 pci3: on pcib3 isp1: port 0x1000-0x10ff mem 0x2000000-0x2000fff at device 4.0 on pci3 pcib2: WARNING: using devices behind PCI-PCI bridges may cause data corruptionisp1: [ITHREAD] panic: trap: data access error cpuid = 0 KDB: enter: panic [thread pid 0 tid 100000 ] Stopped at kdb_enter+0x80: ta %xcc, 1 db> bt Tracing pid 0 tid 100000 td 0xc0848780 panic() at panic+0x20c trap() at trap+0x570 -- data access error %o7=0xc01e6168 -- isp_pci_rd_reg_1080() at isp_pci_rd_reg_1080+0x198 isp_reset() at isp_reset+0x728 isp_pci_attach() at isp_pci_attach+0x1f70 device_attach() at device_attach+0x4a4 device_probe_and_attach() at device_probe_and_attach+0x64 bus_generic_attach() at bus_generic_attach+0x10 ofw_pcibus_attach() at ofw_pcibus_attach+0x72c device_attach() at device_attach+0x4a4 device_probe_and_attach() at device_probe_and_attach+0x64 bus_generic_attach() at bus_generic_attach+0x10 ofw_pcib_attach() at ofw_pcib_attach+0x38 device_attach() at device_attach+0x4a4 device_probe_and_attach() at device_probe_and_attach+0x64 bus_generic_attach() at bus_generic_attach+0x10 ofw_pcibus_attach() at ofw_pcibus_attach+0x72c device_attach() at device_attach+0x4a4 device_probe_and_attach() at device_probe_and_attach+0x64 bus_generic_attach() at bus_generic_attach+0x10 schizo_attach() at schizo_attach+0x13b8 device_attach() at device_attach+0x4a4 device_probe_and_attach() at device_probe_and_attach+0x64 bus_generic_attach() at bus_generic_attach+0x10 nexus_attach() at nexus_attach+0x4fc device_attach() at device_attach+0x4a4 device_probe_and_attach() at device_probe_and_attach+0x64 root_bus_configure() at root_bus_configure+0x28 configure() at configure+0x4 mi_startup() at mi_startup+0x18c btext() at btext+0x30 db> I could provide remote access to the server but I may need some days to set up a netboot environment. Many thanks for your help! Beat From owner-freebsd-sparc64@FreeBSD.ORG Mon Dec 8 11:07:03 2008 Return-Path: Delivered-To: freebsd-sparc64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 70B151065677 for ; Mon, 8 Dec 2008 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 5E2538FC1A for ; Mon, 8 Dec 2008 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 mB8B73ot014405 for ; Mon, 8 Dec 2008 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 mB8B72QF014401 for freebsd-sparc64@FreeBSD.org; Mon, 8 Dec 2008 11:07:02 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 8 Dec 2008 11:07:02 GMT Message-Id: <200812081107.mB8B72QF014401@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-sparc64@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-sparc64@FreeBSD.org X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2008 11:07:03 -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 -------------------------------------------------------------------------------- f sparc/127051 sparc64 [hme] hme interfaces "pause" with the message "device o sparc/119244 sparc64 X11Forwarding to X11 server on sparc crashes Xorg o sparc/119240 sparc64 top has WCPU over 100% on UP system s sparc/119239 sparc64 gdb coredumps on sparc64 o sparc/119017 sparc64 7.0 Beta won't install on U60 o sparc/118932 sparc64 7.0-BETA4/sparc-64 kernel panic in rip_output o sparc/113556 sparc64 panic: trap: memory address not aligned; Rebooting... o sparc/109908 sparc64 apache22 mod_perl issue on sparc64 f sparc/108732 sparc64 ping(8) reports 14 digit time on sparc64 s sparc/107087 sparc64 system is hinged during boot from CD f sparc/106251 sparc64 [libmalloc] malloc fails > for large allocations f sparc/105157 sparc64 No reply to ping on Sparc64 o sparc/105048 sparc64 [trm] trm(4) panics on sparc64 o sparc/104428 sparc64 [nullfs] nullfs panics on E4500 (but not E420) o sparc/80890 sparc64 [panic] kmem_malloc(73728): kmem_map too small running o sparc/80410 sparc64 [netgraph] netgraph is causing crash with mpd on sparc o sparc/71729 sparc64 printf in kernel thread causes panic on SPARC 17 problems total. From owner-freebsd-sparc64@FreeBSD.ORG Tue Dec 9 08:13:04 2008 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5C1B1065672 for ; Tue, 9 Dec 2008 08:13:04 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id 4CE398FC17 for ; Tue, 9 Dec 2008 08:13:04 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.3/8.14.3/ALCHEMY.FRANKEN.DE) with ESMTP id mB98D0NX014749; Tue, 9 Dec 2008 09:13:01 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.3/8.14.3/Submit) id mB98D0NV014748; Tue, 9 Dec 2008 09:13:00 +0100 (CET) (envelope-from marius) Date: Tue, 9 Dec 2008 09:13:00 +0100 From: Marius Strobl To: Beat =?unknown-8bit?Q?G=E4tzi?= Message-ID: <20081209081300.GK52382@alchemy.franken.de> References: <4935839E.4010000@chruetertee.ch> <20081204180726.GA19048@alchemy.franken.de> <26f6c7210812050014l5dac2871k7ca1db1677d0b7d0@mail.gmail.com> <20081205172112.GA52382@alchemy.franken.de> <26f6c7210812080259j1cc1cb3bo2fe827a8442f068a@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <26f6c7210812080259j1cc1cb3bo2fe827a8442f068a@mail.gmail.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-sparc64@freebsd.org Subject: Re: Booting of 200811 snapshot on Sun Fire V880 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2008 08:13:04 -0000 On Mon, Dec 08, 2008 at 11:59:50AM +0100, Beat Gtzi wrote: > > The new image solves the initial issue but now it fails at: > [...] > isp1: port 0x1000-0x10ff mem > 0x2000000-0x2000fff at device 4.0 on pci3 > pcib2: WARNING: using devices behind PCI-PCI bridges may cause data > corruptionisp1: [ITHREAD] > panic: trap: data access error > cpuid = 0 > KDB: enter: panic > [thread pid 0 tid 100000 ] > Stopped at kdb_enter+0x80: ta %xcc, 1 > db> bt > Tracing pid 0 tid 100000 td 0xc0848780 > panic() at panic+0x20c > trap() at trap+0x570 > -- data access error %o7=0xc01e6168 -- > isp_pci_rd_reg_1080() at isp_pci_rd_reg_1080+0x198 > isp_reset() at isp_reset+0x728 > isp_pci_attach() at isp_pci_attach+0x1f70 > device_attach() at device_attach+0x4a4 > device_probe_and_attach() at device_probe_and_attach+0x64 > bus_generic_attach() at bus_generic_attach+0x10 > ofw_pcibus_attach() at ofw_pcibus_attach+0x72c > device_attach() at device_attach+0x4a4 > device_probe_and_attach() at device_probe_and_attach+0x64 > bus_generic_attach() at bus_generic_attach+0x10 > ofw_pcib_attach() at ofw_pcib_attach+0x38 > device_attach() at device_attach+0x4a4 > device_probe_and_attach() at device_probe_and_attach+0x64 > bus_generic_attach() at bus_generic_attach+0x10 > ofw_pcibus_attach() at ofw_pcibus_attach+0x72c > device_attach() at device_attach+0x4a4 > device_probe_and_attach() at device_probe_and_attach+0x64 > bus_generic_attach() at bus_generic_attach+0x10 > schizo_attach() at schizo_attach+0x13b8 > device_attach() at device_attach+0x4a4 > device_probe_and_attach() at device_probe_and_attach+0x64 > bus_generic_attach() at bus_generic_attach+0x10 > nexus_attach() at nexus_attach+0x4fc > device_attach() at device_attach+0x4a4 > device_probe_and_attach() at device_probe_and_attach+0x64 > root_bus_configure() at root_bus_configure+0x28 > configure() at configure+0x4 > mi_startup() at mi_startup+0x18c > btext() at btext+0x30 > db> > > I could provide remote access to the server but I may need some days > to set up a netboot environment. > If you haven't lost patience yet, could you please try (currently still uploading): http://people.freebsd.org/~marius/8.0-20081208-SNAP-sparc64-disc1.iso.gz ? Btw., sorry for the inconveniences, the drivers bugs you happen to hit aren't actually sparc64-specific though. Marius From owner-freebsd-sparc64@FreeBSD.ORG Tue Dec 9 10:06:55 2008 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C57701065677 for ; Tue, 9 Dec 2008 10:06:55 +0000 (UTC) (envelope-from beat@chruetertee.ch) Received: from marvin.chruetertee.ch (marvin.chruetertee.ch [217.150.245.55]) by mx1.freebsd.org (Postfix) with ESMTP id 565CB8FC18 for ; Tue, 9 Dec 2008 10:06:55 +0000 (UTC) (envelope-from beat@chruetertee.ch) Received: from daedalus.network.local (cafe.interxion.wlan.hotspot.nexellent.net [217.147.222.218]) (authenticated bits=0) by marvin.chruetertee.ch (8.14.2/8.13.6) with ESMTP id mB9A6k66046460 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Tue, 9 Dec 2008 10:06:47 GMT (envelope-from beat@chruetertee.ch) Message-ID: <493E433F.5040703@chruetertee.ch> Date: Tue, 09 Dec 2008 11:06:55 +0100 From: =?ISO-8859-1?Q?Beat_G=E4tzi?= User-Agent: Thunderbird 2.0.0.18 (X11/20081124) MIME-Version: 1.0 To: Marius Strobl References: <4935839E.4010000@chruetertee.ch> <20081204180726.GA19048@alchemy.franken.de> <26f6c7210812050014l5dac2871k7ca1db1677d0b7d0@mail.gmail.com> <20081205172112.GA52382@alchemy.franken.de> <26f6c7210812080259j1cc1cb3bo2fe827a8442f068a@mail.gmail.com> <20081209081300.GK52382@alchemy.franken.de> In-Reply-To: <20081209081300.GK52382@alchemy.franken.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-sparc64@freebsd.org Subject: Re: Booting of 200811 snapshot on Sun Fire V880 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2008 10:06:55 -0000 Marius Strobl wrote: > On Mon, Dec 08, 2008 at 11:59:50AM +0100, Beat Gtzi wrote: >> The new image solves the initial issue but now it fails at: >> [...] >> isp1: port 0x1000-0x10ff mem >> 0x2000000-0x2000fff at device 4.0 on pci3 >> pcib2: WARNING: using devices behind PCI-PCI bridges may cause data >> corruptionisp1: [ITHREAD] >> panic: trap: data access error >> cpuid = 0 >> KDB: enter: panic >> [thread pid 0 tid 100000 ] >> Stopped at kdb_enter+0x80: ta %xcc, 1 >> db> bt >> Tracing pid 0 tid 100000 td 0xc0848780 >> panic() at panic+0x20c >> trap() at trap+0x570 >> -- data access error %o7=0xc01e6168 -- >> isp_pci_rd_reg_1080() at isp_pci_rd_reg_1080+0x198 >> isp_reset() at isp_reset+0x728 >> isp_pci_attach() at isp_pci_attach+0x1f70 >> device_attach() at device_attach+0x4a4 >> device_probe_and_attach() at device_probe_and_attach+0x64 >> bus_generic_attach() at bus_generic_attach+0x10 >> ofw_pcibus_attach() at ofw_pcibus_attach+0x72c >> device_attach() at device_attach+0x4a4 >> device_probe_and_attach() at device_probe_and_attach+0x64 >> bus_generic_attach() at bus_generic_attach+0x10 >> ofw_pcib_attach() at ofw_pcib_attach+0x38 >> device_attach() at device_attach+0x4a4 >> device_probe_and_attach() at device_probe_and_attach+0x64 >> bus_generic_attach() at bus_generic_attach+0x10 >> ofw_pcibus_attach() at ofw_pcibus_attach+0x72c >> device_attach() at device_attach+0x4a4 >> device_probe_and_attach() at device_probe_and_attach+0x64 >> bus_generic_attach() at bus_generic_attach+0x10 >> schizo_attach() at schizo_attach+0x13b8 >> device_attach() at device_attach+0x4a4 >> device_probe_and_attach() at device_probe_and_attach+0x64 >> bus_generic_attach() at bus_generic_attach+0x10 >> nexus_attach() at nexus_attach+0x4fc >> device_attach() at device_attach+0x4a4 >> device_probe_and_attach() at device_probe_and_attach+0x64 >> root_bus_configure() at root_bus_configure+0x28 >> configure() at configure+0x4 >> mi_startup() at mi_startup+0x18c >> btext() at btext+0x30 >> db> >> >> I could provide remote access to the server but I may need some days >> to set up a netboot environment. >> > > If you haven't lost patience yet, could you please try (currently > still uploading): > http://people.freebsd.org/~marius/8.0-20081208-SNAP-sparc64-disc1.iso.gz > ? Btw., sorry for the inconveniences, the drivers bugs you > happen to hit aren't actually sparc64-specific though. The new image fixes the data access error but it seems that I run into another bug: isp1: port 0x1000-0x10ff mem 0x2000000-0x2000fff at device 4.0 on pci3 pcib2: WARNING: using devices behind PCI-PCI bridges may cause data corruptionisp1: [ITHREAD] isp1: Board Type 10160, Chip Revision 0x6, loaded F/W Revision 10.4.41 isp1: invalid NVRAM header isp2: port 0x1100-0x11ff mem 0x2002000-0x2002fff at device 5.0 on pci3 pcib2: WARNING: using devices behind PCI-PCI bridges may cause data corruptionisp2: [ITHREAD] isp2: Board Type 10160, Chip Revision 0x6, loaded F/W Revision 10.4.41 isp2: invalid NVRAM header pcib4: mem 0x40004e00000-0x40004e17fff,0x40004c10000-0x40004c1004f,0x7ffe8000000-0x7ffe80000ff irq 626,624,625,628,630 on nexus0 pcib4: Schizo, version 4, IGN 0x9, bus A, 33MHz Timecounter "pcib4" frequency 150000000 Hz quality 100 pcib4: DVMA map: 0xc0000000 to 0xffffffff pcib4: [FILTER] pcib4: [FILTER] pcib4: [FILTER] pcib4: [FILTER] pci4: on pcib4 pci4: at device 2.0 (no driver attached) hme0: mem 0x100000-0x107fff at device 2.1 on pci4 miibus2: on hme0 ukphy1: PHY 1 on miibus2 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto hme0: Ethernet address: 00:03:ba:xx:xx:xx pcib4: invalid interrupt vector 0x245 hme0: couldn't establish interrupt panic: trap: fast data access mmu miss cpuid = 0 KDB: enter: panic [thread pid 0 tid 100000 ] Stopped at kdb_enter+0x80: ta %xcc, 1 db> bt Tracing pid 0 tid 100000 td 0xc0848780 panic() at panic+0x20c trap() at trap+0x570 -- fast data access mmu miss tar=0 %o7=0xc0328a48 -- _rw_rlock() at _rw_rlock+0x170 in_pcbpurgeif0() at in_pcbpurgeif0+0x24 in_ifdetach() at in_ifdetach+0x1c if_detach() at if_detach+0x180 ether_ifdetach() at ether_ifdetach+0x58 hme_detach() at hme_detach+0x64 hme_pci_attach() at hme_pci_attach+0x388 device_attach() at device_attach+0x4a4 device_probe_and_attach() at device_probe_and_attach+0x64 bus_generic_attach() at bus_generic_attach+0x10 ofw_pcibus_attach() at ofw_pcibus_attach+0x72c device_attach() at device_attach+0x4a4 device_probe_and_attach() at device_probe_and_attach+0x64 bus_generic_attach() at bus_generic_attach+0x10 schizo_attach() at schizo_attach+0x13b8 device_attach() at device_attach+0x4a4 device_probe_and_attach() at device_probe_and_attach+0x64 bus_generic_attach() at bus_generic_attach+0x10 nexus_attach() at nexus_attach+0x4fc device_attach() at device_attach+0x4a4 device_probe_and_attach() at device_probe_and_attach+0x64 root_bus_configure() at root_bus_configure+0x28 configure() at configure+0x4 mi_startup() at mi_startup+0x18c btext() at btext+0x30 db> Thanks for your help! Beat From owner-freebsd-sparc64@FreeBSD.ORG Tue Dec 9 21:19:05 2008 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AAD401065670 for ; Tue, 9 Dec 2008 21:19:05 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id 476C98FC08 for ; Tue, 9 Dec 2008 21:19:05 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.3/8.14.3/ALCHEMY.FRANKEN.DE) with ESMTP id mB9LJ01b021378; Tue, 9 Dec 2008 22:19:00 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.3/8.14.3/Submit) id mB9LJ0c0021377; Tue, 9 Dec 2008 22:19:00 +0100 (CET) (envelope-from marius) Date: Tue, 9 Dec 2008 22:19:00 +0100 From: Marius Strobl To: Beat =?unknown-8bit?Q?G=E4tzi?= Message-ID: <20081209211900.GC15733@alchemy.franken.de> References: <4935839E.4010000@chruetertee.ch> <20081204180726.GA19048@alchemy.franken.de> <26f6c7210812050014l5dac2871k7ca1db1677d0b7d0@mail.gmail.com> <20081205172112.GA52382@alchemy.franken.de> <26f6c7210812080259j1cc1cb3bo2fe827a8442f068a@mail.gmail.com> <20081209081300.GK52382@alchemy.franken.de> <493E433F.5040703@chruetertee.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <493E433F.5040703@chruetertee.ch> User-Agent: Mutt/1.4.2.3i Cc: freebsd-sparc64@freebsd.org Subject: Re: Booting of 200811 snapshot on Sun Fire V880 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2008 21:19:05 -0000 On Tue, Dec 09, 2008 at 11:06:55AM +0100, Beat Gtzi wrote: > > The new image fixes the data access error but it seems that I run into > another bug: > > isp1: port 0x1000-0x10ff mem > 0x2000000-0x2000fff at device 4.0 on pci3 > pcib2: WARNING: using devices behind PCI-PCI bridges may cause data > corruptionisp1: [ITHREAD] > isp1: Board Type 10160, Chip Revision 0x6, loaded F/W Revision 10.4.41 > isp1: invalid NVRAM header > isp2: port 0x1100-0x11ff mem > 0x2002000-0x2002fff at device 5.0 on pci3 > pcib2: WARNING: using devices behind PCI-PCI bridges may cause data > corruptionisp2: [ITHREAD] > isp2: Board Type 10160, Chip Revision 0x6, loaded F/W Revision 10.4.41 > isp2: invalid NVRAM header > pcib4: mem > 0x40004e00000-0x40004e17fff,0x40004c10000-0x40004c1004f,0x7ffe8000000-0x7ffe80000ff > irq > 626,624,625,628,630 on nexus0 > pcib4: Schizo, version 4, IGN 0x9, bus A, 33MHz > Timecounter "pcib4" frequency 150000000 Hz quality 100 > pcib4: DVMA map: 0xc0000000 to 0xffffffff > pcib4: [FILTER] > pcib4: [FILTER] > pcib4: [FILTER] > pcib4: [FILTER] > pci4: on pcib4 > pci4: at device 2.0 (no driver attached) > hme0: mem 0x100000-0x107fff at device 2.1 on pci4 > miibus2: on hme0 > ukphy1: PHY 1 on miibus2 > ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > hme0: Ethernet address: 00:03:ba:xx:xx:xx > pcib4: invalid interrupt vector 0x245 > hme0: couldn't establish interrupt > panic: trap: fast data access mmu miss > cpuid = 0 > KDB: enter: panic > [thread pid 0 tid 100000 ] > Stopped at kdb_enter+0x80: ta %xcc, 1 > db> bt > Tracing pid 0 tid 100000 td 0xc0848780 > panic() at panic+0x20c > trap() at trap+0x570 > -- fast data access mmu miss tar=0 %o7=0xc0328a48 -- > _rw_rlock() at _rw_rlock+0x170 > in_pcbpurgeif0() at in_pcbpurgeif0+0x24 > in_ifdetach() at in_ifdetach+0x1c > if_detach() at if_detach+0x180 > ether_ifdetach() at ether_ifdetach+0x58 > hme_detach() at hme_detach+0x64 > hme_pci_attach() at hme_pci_attach+0x388 > device_attach() at device_attach+0x4a4 > device_probe_and_attach() at device_probe_and_attach+0x64 > bus_generic_attach() at bus_generic_attach+0x10 > ofw_pcibus_attach() at ofw_pcibus_attach+0x72c > device_attach() at device_attach+0x4a4 > device_probe_and_attach() at device_probe_and_attach+0x64 > bus_generic_attach() at bus_generic_attach+0x10 > schizo_attach() at schizo_attach+0x13b8 > device_attach() at device_attach+0x4a4 > device_probe_and_attach() at device_probe_and_attach+0x64 > bus_generic_attach() at bus_generic_attach+0x10 > nexus_attach() at nexus_attach+0x4fc > device_attach() at device_attach+0x4a4 > device_probe_and_attach() at device_probe_and_attach+0x64 > root_bus_configure() at root_bus_configure+0x28 > configure() at configure+0x4 > mi_startup() at mi_startup+0x18c > btext() at btext+0x30 > db> > You have some real luck with this machine... The problem causing the panic seems to be a bug in the network stack which I don't have a clue about, which is triggered by hme(4) immediatley detaching again as it can't setup the interrupt due to what appears to be a firmware bug. Could you please try: http://people.freebsd.org/~marius/8.0-20081209-SNAP-sparc64-disc1.iso.gz which tries to work around the latter bug. Given that this involves some guesswork and I can't tell for sure it's a firmware bug without an OFW device tree dump (if there's still a working Solaris installation on that machine could you please provide the output of `prtconf -Ppv`?) I'm unsure whtether this will actually solve it. Marius From owner-freebsd-sparc64@FreeBSD.ORG Tue Dec 9 21:36:17 2008 Return-Path: Delivered-To: sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2BFB31065670 for ; Tue, 9 Dec 2008 21:36:17 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id AD45D8FC08 for ; Tue, 9 Dec 2008 21:36:16 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.3/8.14.3/ALCHEMY.FRANKEN.DE) with ESMTP id mB9LaEpq021575; Tue, 9 Dec 2008 22:36:14 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.3/8.14.3/Submit) id mB9LaEOI021574; Tue, 9 Dec 2008 22:36:14 +0100 (CET) (envelope-from marius) Date: Tue, 9 Dec 2008 22:36:13 +0100 From: Marius Strobl To: Ruben de Groot Message-ID: <20081209213613.GA21283@alchemy.franken.de> References: <20081103120215.GA32257@ei.bzerk.org> <20081103221111.GA8256@alchemy.franken.de> <20081105195630.GA52831@ei.bzerk.org> <20081109183232.GC76319@alchemy.franken.de> <20081119080344.GA96293@ei.bzerk.org> <20081119220317.GP64456@alchemy.franken.de> <20081120054711.GA11035@ei.bzerk.org> <20081201211806.GF82355@alchemy.franken.de> <20081202115653.GA90256@ei.bzerk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081202115653.GA90256@ei.bzerk.org> User-Agent: Mutt/1.4.2.3i Cc: sparc64@freebsd.org Subject: Re: Panic in 7.1-PRERELEASE (was: Re: kgdb on sparc64) X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2008 21:36:17 -0000 On Tue, Dec 02, 2008 at 12:56:53PM +0100, Ruben de Groot wrote: > On Mon, Dec 01, 2008 at 10:18:06PM +0100, Marius Strobl typed: > > On Thu, Nov 20, 2008 at 06:47:11AM +0100, Ruben de Groot wrote: > > > > > > Thanks. I've moved all websites away from this machine, so it's available for any > > > further tests to help find a solution. > > > > > > > Could you please give the patch at: > > http://people.freebsd.org/~marius/dc_bitbang_delay.diff > > a try? It's based on information gained from other drivers for > > the same chips that there should be an delay after every write > > when bit-banging the MII, which hopefully solves the bus wedging > > you're seeing. So far I didn't manage to reproduce the problem > > though, so I can't test whether the patch makes an actual > > difference either. > > Thanks for looking into this. > Running with this patch right now. It'll take some time to conclude if this > fixes the issue, as the panics normally happen only once every 2-3 days. > How is it doing so far? Marius From owner-freebsd-sparc64@FreeBSD.ORG Wed Dec 10 12:04:08 2008 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D53181065774 for ; Wed, 10 Dec 2008 12:04:07 +0000 (UTC) (envelope-from beat@chruetertee.ch) Received: from marvin.chruetertee.ch (marvin.chruetertee.ch [217.150.245.55]) by mx1.freebsd.org (Postfix) with ESMTP id 679468FC12 for ; Wed, 10 Dec 2008 12:04:07 +0000 (UTC) (envelope-from beat@chruetertee.ch) Received: from daedalus.network.local (cafe.interxion.wlan.hotspot.nexellent.net [217.147.222.218]) (authenticated bits=0) by marvin.chruetertee.ch (8.14.2/8.13.6) with ESMTP id mBAC40Nt058901 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Wed, 10 Dec 2008 12:04:00 GMT (envelope-from beat@chruetertee.ch) Message-ID: <493FB038.3080103@chruetertee.ch> Date: Wed, 10 Dec 2008 13:04:08 +0100 From: =?ISO-8859-1?Q?Beat_G=E4tzi?= User-Agent: Thunderbird 2.0.0.18 (X11/20081124) MIME-Version: 1.0 To: Marius Strobl References: <4935839E.4010000@chruetertee.ch> <20081204180726.GA19048@alchemy.franken.de> <26f6c7210812050014l5dac2871k7ca1db1677d0b7d0@mail.gmail.com> <20081205172112.GA52382@alchemy.franken.de> <26f6c7210812080259j1cc1cb3bo2fe827a8442f068a@mail.gmail.com> <20081209081300.GK52382@alchemy.franken.de> <493E433F.5040703@chruetertee.ch> <20081209211900.GC15733@alchemy.franken.de> In-Reply-To: <20081209211900.GC15733@alchemy.franken.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-sparc64@freebsd.org Subject: Re: Booting of 200811 snapshot on Sun Fire V880 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2008 12:04:09 -0000 Marius Strobl wrote: > On Tue, Dec 09, 2008 at 11:06:55AM +0100, Beat Gtzi wrote: >> The new image fixes the data access error but it seems that I run into >> another bug: >> >> isp1: port 0x1000-0x10ff mem >> 0x2000000-0x2000fff at device 4.0 on pci3 >> pcib2: WARNING: using devices behind PCI-PCI bridges may cause data >> corruptionisp1: [ITHREAD] >> isp1: Board Type 10160, Chip Revision 0x6, loaded F/W Revision 10.4.41 >> isp1: invalid NVRAM header >> isp2: port 0x1100-0x11ff mem >> 0x2002000-0x2002fff at device 5.0 on pci3 >> pcib2: WARNING: using devices behind PCI-PCI bridges may cause data >> corruptionisp2: [ITHREAD] >> isp2: Board Type 10160, Chip Revision 0x6, loaded F/W Revision 10.4.41 >> isp2: invalid NVRAM header >> pcib4: mem >> 0x40004e00000-0x40004e17fff,0x40004c10000-0x40004c1004f,0x7ffe8000000-0x7ffe80000ff >> irq >> 626,624,625,628,630 on nexus0 >> pcib4: Schizo, version 4, IGN 0x9, bus A, 33MHz >> Timecounter "pcib4" frequency 150000000 Hz quality 100 >> pcib4: DVMA map: 0xc0000000 to 0xffffffff >> pcib4: [FILTER] >> pcib4: [FILTER] >> pcib4: [FILTER] >> pcib4: [FILTER] >> pci4: on pcib4 >> pci4: at device 2.0 (no driver attached) >> hme0: mem 0x100000-0x107fff at device 2.1 on pci4 >> miibus2: on hme0 >> ukphy1: PHY 1 on miibus2 >> ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >> hme0: Ethernet address: 00:03:ba:xx:xx:xx >> pcib4: invalid interrupt vector 0x245 >> hme0: couldn't establish interrupt >> panic: trap: fast data access mmu miss >> cpuid = 0 >> KDB: enter: panic >> [thread pid 0 tid 100000 ] >> Stopped at kdb_enter+0x80: ta %xcc, 1 >> db> bt >> Tracing pid 0 tid 100000 td 0xc0848780 >> panic() at panic+0x20c >> trap() at trap+0x570 >> -- fast data access mmu miss tar=0 %o7=0xc0328a48 -- >> _rw_rlock() at _rw_rlock+0x170 >> in_pcbpurgeif0() at in_pcbpurgeif0+0x24 >> in_ifdetach() at in_ifdetach+0x1c >> if_detach() at if_detach+0x180 >> ether_ifdetach() at ether_ifdetach+0x58 >> hme_detach() at hme_detach+0x64 >> hme_pci_attach() at hme_pci_attach+0x388 >> device_attach() at device_attach+0x4a4 >> device_probe_and_attach() at device_probe_and_attach+0x64 >> bus_generic_attach() at bus_generic_attach+0x10 >> ofw_pcibus_attach() at ofw_pcibus_attach+0x72c >> device_attach() at device_attach+0x4a4 >> device_probe_and_attach() at device_probe_and_attach+0x64 >> bus_generic_attach() at bus_generic_attach+0x10 >> schizo_attach() at schizo_attach+0x13b8 >> device_attach() at device_attach+0x4a4 >> device_probe_and_attach() at device_probe_and_attach+0x64 >> bus_generic_attach() at bus_generic_attach+0x10 >> nexus_attach() at nexus_attach+0x4fc >> device_attach() at device_attach+0x4a4 >> device_probe_and_attach() at device_probe_and_attach+0x64 >> root_bus_configure() at root_bus_configure+0x28 >> configure() at configure+0x4 >> mi_startup() at mi_startup+0x18c >> btext() at btext+0x30 >> db> >> > > You have some real luck with this machine... Yes and the story continues... > The problem causing the panic seems to be a bug in the network > stack which I don't have a clue about, which is triggered by > hme(4) immediatley detaching again as it can't setup the > interrupt due to what appears to be a firmware bug. Could > you please try: > http://people.freebsd.org/~marius/8.0-20081209-SNAP-sparc64-disc1.iso.gz > which tries to work around the latter bug. Given that this > involves some guesswork and I can't tell for sure it's a > firmware bug without an OFW device tree dump (if there's > still a working Solaris installation on that machine > could you please provide the output of `prtconf -Ppv`?) > I'm unsure whtether this will actually solve it. With this image the server boots without problems but during the installer the server panics: panic: cheetah_ipi_selected: couldn't send IPI cpuid = 3 KDB: enter: panic I was not able to enter to the debugger and it wasn't possible to send a break signal and return to OBP. I tried it several times and the panic occurred at various points during the installer. Thanks, Beat