From owner-freebsd-sparc64@FreeBSD.ORG Sun Jan 15 12:20:15 2012 Return-Path: Delivered-To: freebsd-sparc64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1046910656D9 for ; Sun, 15 Jan 2012 12:20:15 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 955EA8FC08 for ; Sun, 15 Jan 2012 12:20:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0FCKD0I054399 for ; Sun, 15 Jan 2012 12:20:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0FCKDWY054398; Sun, 15 Jan 2012 12:20:13 GMT (envelope-from gnats) Date: Sun, 15 Jan 2012 12:20:13 GMT Message-Id: <201201151220.q0FCKDWY054398@freefall.freebsd.org> To: freebsd-sparc64@FreeBSD.org From: Marius Strobl Cc: Subject: Re: sparc64/164123: Kernel fails to boot on Sun Ultra 5 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marius Strobl List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jan 2012 12:20:15 -0000 The following reply was made to PR sparc64/164123; it has been noted by GNATS. From: Marius Strobl To: bug-followup@FreeBSD.org, gmbroome@vcu.edu Cc: Subject: Re: sparc64/164123: Kernel fails to boot on Sun Ultra 5 Date: Sun, 15 Jan 2012 13:01:14 +0100 Please grab the following kernel: http://people.freebsd.org/~marius/kernel.debug.bz2 That is a kernel built from the 9.0-R sources but with debugging symbols. You could also build such a kernel yourself and provide me with the resulting binary instead, this way around is just to save some time. Please boot it and when it crashes enter 'ctrace' and 'ftrace' on the OBP promt and provide me with the output of each of these commands. This probably is most easily done using a serial console. Marius From owner-freebsd-sparc64@FreeBSD.ORG Sun Jan 15 15:20:12 2012 Return-Path: Delivered-To: freebsd-sparc64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F1258106564A for ; Sun, 15 Jan 2012 15:20:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C62AD8FC13 for ; Sun, 15 Jan 2012 15:20:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0FFKCQQ021998 for ; Sun, 15 Jan 2012 15:20:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0FFKCQx021997; Sun, 15 Jan 2012 15:20:12 GMT (envelope-from gnats) Date: Sun, 15 Jan 2012 15:20:12 GMT Message-Id: <201201151520.q0FFKCQx021997@freefall.freebsd.org> To: freebsd-sparc64@FreeBSD.org From: Guy M Broome/FS/VCU Cc: Subject: Re: sparc64/164123: Kernel fails to boot on Sun Ultra 5 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Guy M Broome/FS/VCU List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jan 2012 15:20:13 -0000 The following reply was made to PR sparc64/164123; it has been noted by GNATS. From: Guy M Broome/FS/VCU To: bug-followup@freebsd.org Cc: Subject: Re: sparc64/164123: Kernel fails to boot on Sun Ultra 5 Date: Sun, 15 Jan 2012 09:47:36 -0500 --=_alternative 0051435785257986_= Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Marius, Nevermind tomorrow- I had a chance to get the debugging output immediately. After attempting to boot the debug kernel you provided, The result of "ctrace" is: --------------------------------------------- PC: c07dc388 Last leaf: XXXXXXX=A0=A0=A0=A0 from c07dc350 =A0=A0=A0=A0=A0=A0 0 w=A0=A0 %o0-%o5=A0=A0 (c0b93888 4b0 8 1 0 4 ) --------------------------------------------- and the result of "ftrace" is: --------------------------------------------- =A0=A0=A0=A0=A0=A0=A0=A0 0 Fast Data Access MMU Miss --------------------------------------------- Sincerely, Guy M. Broome --=_alternative 0051435785257986_= Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1 Marius,

Nevermind tomorrow- I had a chance to get the de= bugging output immediately.

After attempting to boot the debug kerne= l you provided,

The result of "ctrace" is:
----------------------= -----------------------

PC: c07dc388
Last leaf: XXXXXXX &nbs= p;   from c07dc350
       0 w&nb= sp;  %o0-%o5   (c0b93888 4b0 8 1 0 4 )

--------------= -------------------------------


and the result of "ftrace" is:---------------------------------------------

   &n= bsp;     0
Fast Data Access MMU Miss

--------= -------------------------------------

Sincerely,
Guy M. Broome
 --=_alternative 0051435785257986_=-- From owner-freebsd-sparc64@FreeBSD.ORG Sun Jan 15 16:23:26 2012 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 8285C1065673; Sun, 15 Jan 2012 16:23:26 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 4739F8FC12; Sun, 15 Jan 2012 16:23:25 +0000 (UTC) Received: by obcwo16 with SMTP id wo16so238116obc.13 for ; Sun, 15 Jan 2012 08:23:25 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.117.8 with SMTP id ka8mr7857972obb.73.1326644605455; Sun, 15 Jan 2012 08:23:25 -0800 (PST) Received: by 10.182.71.201 with HTTP; Sun, 15 Jan 2012 08:23:25 -0800 (PST) X-Originating-IP: [93.221.165.179] In-Reply-To: References: Date: Sun, 15 Jan 2012 17:23:25 +0100 Message-ID: From: "C. P. Ghost" To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-sparc64@freebsd.org Subject: Re: Can't boot 9.0-RELEASE 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: Sun, 15 Jan 2012 16:23:26 -0000 On Sun, Jan 15, 2012 at 5:02 PM, C. P. Ghost wrote: > Hi, > > I'm trying to boot 9.0-RELEASE on sparc64, but I'm > getting stuck at: > > panic: kmem_suballoc: bad status return of 3 > cpuid =3D 0 > KDB: stack backtrace: > =A0#0 0xc079841c at ??+0 > =A0#1 0xc04ca59c at ??+0 > =A0#2 0xc0487f90 at ??+0 > =A0#3 0xc0098028 at ??+0 > > I'm not able to break into the kernel debugger from > there. > > This is a SunBlade 1500 with 2GB of RAM, booting > from cdrom. Just a little follow-up: If I set hw.physmem=3D1048576000 in the loader, 9.0 finally boots. What's going on? Are there some memory holes above 1G that 9.0 can't deal with (but 8.2 can)? Thanks, -cpghost. --=20 Cordula's Web. http://www.cordula.ws/ From owner-freebsd-sparc64@FreeBSD.ORG Sun Jan 15 16:31:48 2012 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 D8D2F106566C for ; Sun, 15 Jan 2012 16:31:48 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 731F88FC14 for ; Sun, 15 Jan 2012 16:31:48 +0000 (UTC) Received: by obcwo16 with SMTP id wo16so243032obc.13 for ; Sun, 15 Jan 2012 08:31:48 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.122.71 with SMTP id lq7mr7897557obb.33.1326643353164; Sun, 15 Jan 2012 08:02:33 -0800 (PST) Received: by 10.182.71.201 with HTTP; Sun, 15 Jan 2012 08:02:33 -0800 (PST) X-Originating-IP: [93.221.165.179] Date: Sun, 15 Jan 2012 17:02:33 +0100 Message-ID: From: "C. P. Ghost" To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-sparc64@freebsd.org Subject: Can't boot 9.0-RELEASE 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: Sun, 15 Jan 2012 16:31:48 -0000 Hi, I'm trying to boot 9.0-RELEASE on sparc64, but I'm getting stuck at: panic: kmem_suballoc: bad status return of 3 cpuid = 0 KDB: stack backtrace: #0 0xc079841c at ??+0 #1 0xc04ca59c at ??+0 #2 0xc0487f90 at ??+0 #3 0xc0098028 at ??+0 I'm not able to break into the kernel debugger from there. This is a SunBlade 1500 with 2GB of RAM, booting from cdrom. The same machine boots 8.2-RELEASE from disk without any problems. boot -v of 8.2 yields: Copyright (c) 1992-2011 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.2-RELEASE #0: Thu Feb 17 06:57:44 UTC 2011 root@araz.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC sparc64 Preloaded elf kernel "/boot/GENERIC/kernel" at 0xc0b9c000. real memory = 2147483648 (2048 MB) avail memory = 2079563776 (1983 MB) machine: SUNW,Sun-Blade-1500-S cpu0: Sun Microsystems UltraSparc-IIIi Processor (1503.00 MHz CPU) mask=0x34 maxtl=5 maxwin=7 wlan: <802.11 Link Layer> firmware: 'isp_1000' version 1: 20142 bytes loaded at 0xc0725d38 ispfw: registered firmware firmware: 'isp_1040' version 1: 22944 bytes loaded at 0xc072abe6 ispfw: registered firmware firmware: 'isp_1040_it' version 1: 32942 bytes loaded at 0xc0730586 ispfw: registered firmware firmware: 'isp_1080' version 1: 31350 bytes loaded at 0xc0738634 ispfw: registered firmware firmware: 'isp_1080_it' version 1: 40644 bytes loaded at 0xc07400aa ispfw: registered firmware firmware: 'isp_12160' version 1: 28050 bytes loaded at 0xc0749f6e ispfw: registered firmware firmware: 'isp_12160_it' version 1: 40604 bytes loaded at 0xc0750d00 ispfw: registered firmware firmware: 'isp_2100' version 1: 76770 bytes loaded at 0xc075ab9c ispfw: registered firmware firmware: 'isp_2200' version 1: 77214 bytes loaded at 0xc076d77e ispfw: registered firmware firmware: 'isp_2300' version 1: 106640 bytes loaded at 0xc078051c ispfw: registered firmware firmware: 'isp_2322' version 1: 108856 bytes loaded at 0xc079a5ac ispfw: registered firmware firmware: 'isp_2400' version 1: 177416 bytes loaded at 0xc07b8164 ispfw: registered firmware firmware: 'isp_2400_multi' version 1: 193652 bytes loaded at 0xc07efe54 ispfw: registered firmware firmware: 'isp_2500' version 1: 140732 bytes loaded at 0xc082c140 ispfw: registered firmware firmware: 'isp_2500_multi' version 1: 164528 bytes loaded at 0xc085d0c4 ispfw: registered firmware null: random: nfslock: pseudo-device kbd0 at kbdmux0 openfirm: mem: nexus0: pcib0: mem 0x4000f600000-0x4000f60afff,0x4000f410000-0x4000f41701f,0x7fe00000000-0x7fe000000ff,0x4000f780000-0x4000f78ffff irq 1970,1968,1969,1972,1953 on nexus0 pcib0: Tomatillo, version 4, IGN 0x1e, bus A, 33MHz Timecounter "pcib0" frequency 167000000 Hz quality -100 pcib0: DVMA map: 0xc0000000 to 0xdfffffff 65536 entries pcib0: PROM IOTSB size: 1 (2048 entries) pcib0: adding PROM IOTSB slot 0 (kernel slot 63488) TTE: 0x800000013fde0012 pcib0: adding PROM IOTSB slot 1 (kernel slot 63489) TTE: 0x800000013fde2012 pcib0: adding PROM IOTSB slot 2 (kernel slot 63490) TTE: 0x800000013fde4012 pcib0: adding PROM IOTSB slot 3 (kernel slot 63491) TTE: 0x800000013fde6012 pcib0: adding PROM IOTSB slot 4 (kernel slot 63492) TTE: 0x800000013fde8012 pcib0: adding PROM IOTSB slot 5 (kernel slot 63493) TTE: 0x800000013fdea012 pcib0: adding PROM IOTSB slot 6 (kernel slot 63494) TTE: 0x800000013fdec012 pcib0: adding PROM IOTSB slot 7 (kernel slot 63495) TTE: 0x800000013fdee012 pcib0: adding PROM IOTSB slot 8 (kernel slot 63496) TTE: 0x800000013fdf0012 pcib0: adding PROM IOTSB slot 9 (kernel slot 63497) TTE: 0x800000013fdf2012 pcib0: adding PROM IOTSB slot 10 (kernel slot 63498) TTE: 0x800000013fdf4012 pcib0: adding PROM IOTSB slot 11 (kernel slot 63499) TTE: 0x800000013fdf6012 pcib0: adding PROM IOTSB slot 12 (kernel slot 63500) TTE: 0x800000013fdf8012 pcib0: adding PROM IOTSB slot 13 (kernel slot 63501) TTE: 0x800000013fdfa012 pcib0: adding PROM IOTSB slot 14 (kernel slot 63502) TTE: 0x800000013fdfc012 pcib0: adding PROM IOTSB slot 15 (kernel slot 63503) TTE: 0x800000013fdfe012 pcib0: adding PROM IOTSB slot 16 (kernel slot 63504) TTE: 0x800000013fe00012 pcib0: adding PROM IOTSB slot 17 (kernel slot 63505) TTE: 0x800000013fe02012 pcib0: adding PROM IOTSB slot 18 (kernel slot 63506) TTE: 0x800000013fe04012 pcib0: adding PROM IOTSB slot 19 (kernel slot 63507) TTE: 0x800000013fe06012 pcib0: adding PROM IOTSB slot 20 (kernel slot 63508) TTE: 0x800000013fe08012 pcib0: adding PROM IOTSB slot 21 (kernel slot 63509) TTE: 0x800000013fe0a012 pcib0: adding PROM IOTSB slot 22 (kernel slot 63510) TTE: 0x800000013fe0c012 pcib0: adding PROM IOTSB slot 23 (kernel slot 63511) TTE: 0x800000013fe0e012 pcib0: adding PROM IOTSB slot 24 (kernel slot 63512) TTE: 0x800000013fe10012 pcib0: adding PROM IOTSB slot 25 (kernel slot 63513) TTE: 0x800000013fe12012 pcib0: adding PROM IOTSB slot 26 (kernel slot 63514) TTE: 0x800000013fe14012 pcib0: adding PROM IOTSB slot 27 (kernel slot 63515) TTE: 0x800000013fe16012 pcib0: adding PROM IOTSB slot 28 (kernel slot 63516) TTE: 0x800000013fe18012 pcib0: adding PROM IOTSB slot 29 (kernel slot 63517) TTE: 0x800000013fe1a012 pcib0: adding PROM IOTSB slot 30 (kernel slot 63518) TTE: 0x800000013fe1c012 pcib0: adding PROM IOTSB slot 31 (kernel slot 63519) TTE: 0x800000013fe1e012 pcib0: adding PROM IOTSB slot 32 (kernel slot 63520) TTE: 0x800000013fe20012 pcib0: adding PROM IOTSB slot 33 (kernel slot 63521) TTE: 0x800000013fe22012 pcib0: adding PROM IOTSB slot 34 (kernel slot 63522) TTE: 0x800000013fe24012 pcib0: adding PROM IOTSB slot 35 (kernel slot 63523) TTE: 0x800000013fe26012 pcib0: adding PROM IOTSB slot 36 (kernel slot 63524) TTE: 0x800000013fe28012 pcib0: adding PROM IOTSB slot 37 (kernel slot 63525) TTE: 0x800000013fe2a012 pcib0: adding PROM IOTSB slot 38 (kernel slot 63526) TTE: 0x800000013fe2c012 pcib0: adding PROM IOTSB slot 39 (kernel slot 63527) TTE: 0x800000013fe2e012 pcib0: adding PROM IOTSB slot 40 (kernel slot 63528) TTE: 0x800000013fe30012 pcib0: adding PROM IOTSB slot 41 (kernel slot 63529) TTE: 0x800000013fe32012 pcib0: adding PROM IOTSB slot 42 (kernel slot 63530) TTE: 0x800000013fe34012 pcib0: adding PROM IOTSB slot 43 (kernel slot 63531) TTE: 0x800000013fe36012 pcib0: adding PROM IOTSB slot 44 (kernel slot 63532) TTE: 0x800000013fe38012 pcib0: adding PROM IOTSB slot 45 (kernel slot 63533) TTE: 0x800000013fe3a012 pcib0: adding PROM IOTSB slot 46 (kernel slot 63534) TTE: 0x800000013fe3c012 pcib0: adding PROM IOTSB slot 47 (kernel slot 63535) TTE: 0x800000013fe3e012 pcib0: adding PROM IOTSB slot 48 (kernel slot 63536) TTE: 0x800000013fe40012 pcib0: adding PROM IOTSB slot 49 (kernel slot 63537) TTE: 0x800000013fe42012 pcib0: adding PROM IOTSB slot 50 (kernel slot 63538) TTE: 0x800000013fe44012 pcib0: adding PROM IOTSB slot 51 (kernel slot 63539) TTE: 0x800000013fe46012 pcib0: adding PROM IOTSB slot 52 (kernel slot 63540) TTE: 0x800000013fe48012 pcib0: adding PROM IOTSB slot 53 (kernel slot 63541) TTE: 0x800000013fe4a012 pcib0: adding PROM IOTSB slot 54 (kernel slot 63542) TTE: 0x800000013fe4c012 pcib0: adding PROM IOTSB slot 55 (kernel slot 63543) TTE: 0x800000013fe4e012 pcib0: adding PROM IOTSB slot 56 (kernel slot 63544) TTE: 0x800000013fe50012 pcib0: adding PROM IOTSB slot 57 (kernel slot 63545) TTE: 0x800000013fe52012 pcib0: adding PROM IOTSB slot 58 (kernel slot 63546) TTE: 0x800000013fe54012 pcib0: adding PROM IOTSB slot 59 (kernel slot 63547) TTE: 0x800000013fe56012 pcib0: adding PROM IOTSB slot 60 (kernel slot 63548) TTE: 0x800000013fe58012 pcib0: adding PROM IOTSB slot 61 (kernel slot 63549) TTE: 0x800000013fe5a012 pcib0: adding PROM IOTSB slot 62 (kernel slot 63550) TTE: 0x800000013fe5c012 pcib0: adding PROM IOTSB slot 63 (kernel slot 63551) TTE: 0x800000013fe5e012 pcib0: adding PROM IOTSB slot 64 (kernel slot 63552) TTE: 0x800000013fe60012 pcib0: adding PROM IOTSB slot 65 (kernel slot 63553) TTE: 0x800000013fe62012 pcib0: adding PROM IOTSB slot 66 (kernel slot 63554) TTE: 0x800000013fe64012 pcib0: adding PROM IOTSB slot 67 (kernel slot 63555) TTE: 0x800000013fe66012 pcib0: adding PROM IOTSB slot 68 (kernel slot 63556) TTE: 0x800000013fe68012 pcib0: adding PROM IOTSB slot 69 (kernel slot 63557) TTE: 0x800000013fe6a012 pcib0: adding PROM IOTSB slot 70 (kernel slot 63558) TTE: 0x800000013fe6c012 pcib0: adding PROM IOTSB slot 71 (kernel slot 63559) TTE: 0x800000013fe6e012 pcib0: adding PROM IOTSB slot 72 (kernel slot 63560) TTE: 0x800000013fe70012 pcib0: adding PROM IOTSB slot 73 (kernel slot 63561) TTE: 0x800000013fe72012 pcib0: adding PROM IOTSB slot 74 (kernel slot 63562) TTE: 0x800000013fe74012 pcib0: adding PROM IOTSB slot 75 (kernel slot 63563) TTE: 0x800000013fe76012 pcib0: adding PROM IOTSB slot 76 (kernel slot 63564) TTE: 0x800000013fe78012 pcib0: adding PROM IOTSB slot 77 (kernel slot 63565) TTE: 0x800000013fe7a012 pcib0: adding PROM IOTSB slot 78 (kernel slot 63566) TTE: 0x800000013fe7c012 pcib0: adding PROM IOTSB slot 79 (kernel slot 63567) TTE: 0x800000013fe7e012 pcib0: adding PROM IOTSB slot 80 (kernel slot 63568) TTE: 0x800000013fe80012 pcib0: adding PROM IOTSB slot 81 (kernel slot 63569) TTE: 0x800000013fe82012 pcib0: adding PROM IOTSB slot 82 (kernel slot 63570) TTE: 0x800000013fe84012 pcib0: adding PROM IOTSB slot 83 (kernel slot 63571) TTE: 0x800000013fe86012 pcib0: adding PROM IOTSB slot 84 (kernel slot 63572) TTE: 0x800000013fe88012 pcib0: adding PROM IOTSB slot 85 (kernel slot 63573) TTE: 0x800000013fe8a012 pcib0: adding PROM IOTSB slot 86 (kernel slot 63574) TTE: 0x800000013fe8c012 pcib0: adding PROM IOTSB slot 87 (kernel slot 63575) TTE: 0x800000013fe8e012 pcib0: adding PROM IOTSB slot 88 (kernel slot 63576) TTE: 0x800000013fe90012 pcib0: adding PROM IOTSB slot 89 (kernel slot 63577) TTE: 0x800000013fe92012 pcib0: adding PROM IOTSB slot 90 (kernel slot 63578) TTE: 0x800000013fe94012 pcib0: adding PROM IOTSB slot 91 (kernel slot 63579) TTE: 0x800000013fe96012 pcib0: adding PROM IOTSB slot 92 (kernel slot 63580) TTE: 0x800000013fe98012 pcib0: adding PROM IOTSB slot 93 (kernel slot 63581) TTE: 0x800000013fe9a012 pcib0: adding PROM IOTSB slot 94 (kernel slot 63582) TTE: 0x800000013fe9c012 pcib0: adding PROM IOTSB slot 95 (kernel slot 63583) TTE: 0x800000013fe9e012 pcib0: adding PROM IOTSB slot 96 (kernel slot 63584) TTE: 0x800000013fea0012 pcib0: adding PROM IOTSB slot 97 (kernel slot 63585) TTE: 0x800000013fea2012 pcib0: adding PROM IOTSB slot 98 (kernel slot 63586) TTE: 0x800000013fea4012 pcib0: adding PROM IOTSB slot 99 (kernel slot 63587) TTE: 0x800000013fea6012 pcib0: adding PROM IOTSB slot 100 (kernel slot 63588) TTE: 0x800000013fea8012 pcib0: adding PROM IOTSB slot 101 (kernel slot 63589) TTE: 0x800000013feaa012 pcib0: adding PROM IOTSB slot 102 (kernel slot 63590) TTE: 0x800000013feac012 pcib0: adding PROM IOTSB slot 103 (kernel slot 63591) TTE: 0x800000013feae012 pcib0: adding PROM IOTSB slot 104 (kernel slot 63592) TTE: 0x800000013feb0012 pcib0: adding PROM IOTSB slot 105 (kernel slot 63593) TTE: 0x800000013feb2012 pcib0: adding PROM IOTSB slot 106 (kernel slot 63594) TTE: 0x800000013feb4012 pcib0: adding PROM IOTSB slot 107 (kernel slot 63595) TTE: 0x800000013feb6012 pcib0: adding PROM IOTSB slot 108 (kernel slot 63596) TTE: 0x800000013feb8012 pcib0: adding PROM IOTSB slot 109 (kernel slot 63597) TTE: 0x800000013feba012 pcib0: adding PROM IOTSB slot 110 (kernel slot 63598) TTE: 0x800000013febc012 pcib0: adding PROM IOTSB slot 111 (kernel slot 63599) TTE: 0x800000013febe012 pcib0: adding PROM IOTSB slot 112 (kernel slot 63600) TTE: 0x800000013fec0012 pcib0: adding PROM IOTSB slot 113 (kernel slot 63601) TTE: 0x800000013fec2012 pcib0: adding PROM IOTSB slot 114 (kernel slot 63602) TTE: 0x800000013fec4012 pcib0: adding PROM IOTSB slot 115 (kernel slot 63603) TTE: 0x800000013fec6012 pcib0: adding PROM IOTSB slot 116 (kernel slot 63604) TTE: 0x800000013fec8012 pcib0: adding PROM IOTSB slot 117 (kernel slot 63605) TTE: 0x800000013feca012 pcib0: adding PROM IOTSB slot 118 (kernel slot 63606) TTE: 0x800000013fecc012 pcib0: adding PROM IOTSB slot 119 (kernel slot 63607) TTE: 0x800000013fece012 pcib0: adding PROM IOTSB slot 120 (kernel slot 63608) TTE: 0x800000013fed0012 pcib0: adding PROM IOTSB slot 121 (kernel slot 63609) TTE: 0x800000013fed2012 pcib0: adding PROM IOTSB slot 122 (kernel slot 63610) TTE: 0x800000013fed4012 pcib0: adding PROM IOTSB slot 123 (kernel slot 63611) TTE: 0x800000013fed6012 pcib0: adding PROM IOTSB slot 124 (kernel slot 63612) TTE: 0x800000013fed8012 pcib0: adding PROM IOTSB slot 125 (kernel slot 63613) TTE: 0x800000013feda012 pcib0: adding PROM IOTSB slot 126 (kernel slot 63614) TTE: 0x800000013fedc012 pcib0: adding PROM IOTSB slot 127 (kernel slot 63615) TTE: 0x800000013fede012 pcib0: bus range 0 to 1; PCI bus 0 initalizing intr_countp pcib0: [FILTER] pci0: on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x108e, dev=0xa801, revid=0x00 domain=0, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0146, statreg=0x02a0, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10b9, dev=0x1533, revid=0x00 domain=0, bus=0, slot=7, func=0 class=06-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x000f, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) powerspec 1 supports D0 D3 current D0 found-> vendor=0x10b9, dev=0x7101, revid=0x00 domain=0, bus=0, slot=6, func=0 class=00-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10b9, dev=0x5451, revid=0x02 domain=0, bus=0, slot=8, func=0 class=04-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x10 (480 ns), mingnt=0x02 (500 ns), maxlat=0x18 (6000 ns) intpin=a, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type I/O Port, range 32, base 0x900, size 8, port disabled map[14]: type Memory, range 32, base 0x100000, size 12, memory disabled found-> vendor=0x10b9, dev=0x5237, revid=0x03 domain=0, bus=0, slot=10, func=0 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x50 (20000 ns) intpin=a, irq=255 powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 32, base 0x1000000, size 12, memory disabled found-> vendor=0x10b9, dev=0x5237, revid=0x03 domain=0, bus=0, slot=11, func=0 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x0146, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x50 (20000 ns) intpin=a, irq=255 powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 32, base 0x2000000, size 12, enabled found-> vendor=0x10b9, dev=0x5229, revid=0xc4 domain=0, bus=0, slot=13, func=0 class=01-01-ff, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x10 (480 ns), mingnt=0x02 (500 ns), maxlat=0x04 (1000 ns) intpin=a, irq=255 powerspec 2 supports D0 D3 current D0 map[10]: type I/O Port, range 32, base 0xa00, size 3, port disabled map[14]: type I/O Port, range 32, base 0xa18, size 2, enabled map[18]: type I/O Port, range 32, base 0xa10, size 3, enabled map[1c]: type I/O Port, range 32, base 0xa08, size 2, enabled map[20]: type I/O Port, range 32, base 0xa20, size 4, enabled found-> vendor=0x104c, dev=0xac23, revid=0x02 domain=0, bus=0, slot=2, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x0210, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x23 (8750 ns), maxlat=0x00 (0 ns) powerspec 1 supports D0 D3 current D0 found-> vendor=0x1002, dev=0x4752, revid=0x27 domain=0, bus=0, slot=5, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0082, statreg=0x0290, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0x4000000, size 24, enabled map[14]: type I/O Port, range 32, base 0xb00, size 8, port disabled map[18]: type Memory, range 32, base 0x102000, size 12, enabled pcib1: at device 2.0 on pci0 pcib1: domain 0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0x1000-0xfff pcib1: memory decode 0x3000000-0x30fffff pcib1: no prefetched decode pci1: on pcib1 pci1: domain=0, physical bus=1 found-> vendor=0x1033, dev=0x0035, revid=0x43 domain=0, bus=1, slot=8, func=0 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0210, cachelnsz=16 (dwords) lattimer=0x08 (240 ns), mingnt=0x01 (250 ns), maxlat=0x2a (10500 ns) intpin=a, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0x3000000, size 12, memory disabled pcib1: requested memory range 0x3000000-0x3000fff: good found-> vendor=0x1033, dev=0x0035, revid=0x43 domain=0, bus=1, slot=8, func=1 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0210, cachelnsz=16 (dwords) lattimer=0x08 (240 ns), mingnt=0x01 (250 ns), maxlat=0x2a (10500 ns) intpin=b, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0x3002000, size 12, memory disabled pcib1: requested memory range 0x3002000-0x3002fff: good found-> vendor=0x1033, dev=0x00e0, revid=0x04 domain=0, bus=1, slot=8, func=2 class=0c-03-20, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0210, cachelnsz=16 (dwords) lattimer=0x80 (3840 ns), mingnt=0x10 (4000 ns), maxlat=0x22 (8500 ns) intpin=c, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0x3004000, size 8, memory disabled pcib1: requested memory range 0x3004000-0x30040ff: good found-> vendor=0x104c, dev=0x8024, revid=0x00 domain=0, bus=1, slot=11, func=0 class=0c-00-10, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0210, cachelnsz=16 (dwords) lattimer=0x10 (480 ns), mingnt=0x02 (500 ns), maxlat=0x04 (1000 ns) intpin=a, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0x3006000, size 11, memory disabled pcib1: requested memory range 0x3006000-0x30067ff: good map[14]: type Memory, range 32, base 0x3008000, size 14, enabled pcib1: requested memory range 0x3008000-0x300bfff: good pcib2: mem 0x4000ff00000-0x4000ff0afff,0x4000fc10000-0x4000fc1701f,0x7f600000000-0x7f6000000ff,0x4000ff80000-0x4000ff8ffff irq 2035,2032,2033,2036,2019 on nexus0 pcib2: Tomatillo, version 4, IGN 0x1f, bus B, 66MHz pcib2: DVMA map: 0xc0000000 to 0xdfffffff 65536 entries pcib2: PROM IOTSB size: 1 (2048 entries) pcib2: bus range 0 to 0; PCI bus 0 pcib2: [FILTER] pcib2: [FILTER] pcib2: [FILTER] pcib2: [FILTER] pci2: on pcib2 pci2: domain=2, physical bus=0 found-> vendor=0x108e, dev=0xa801, revid=0x00 domain=2, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0146, statreg=0x02a0, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x14e4, dev=0x1647, revid=0x00 domain=2, bus=0, slot=2, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x02b0, cachelnsz=16 (dwords) lattimer=0xf8 (7440 ns), mingnt=0x40 (16000 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 powerspec 2 supports D0 D3 current D0 MSI supports 8 messages, 64 bit map[10]: type Memory, range 64, base 0x200000, size 16, memory disabled nexus0: mem 0x40000000000-0x40000000007 type memory-controller (no driver attached) isab0: at device 7.0 on pci0 pcib0: could not route pin 1 for device 7.0 isa0: could not map ISA interrupt 1 for node 0xf0088520: parallel isa0: on isab0 pci0: at device 6.0 (no driver attached) pci0: at device 8.0 (no driver attached) ohci0: mem 0x1000000-0x1000fff at device 10.0 on pci0 ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0x1000000 ohci0: [MPSAFE] ohci0: [ITHREAD] usbus0: on ohci0 ohci1: mem 0x2000000-0x2000fff at device 11.0 on pci0 ohci1: Reserved 0x1000 bytes for rid 0x10 type 3 at 0x2000000 ohci1: [MPSAFE] ohci1: [ITHREAD] usbus1: on ohci1 atapci0: port 0xa00-0xa07,0xa18-0xa1b,0xa10-0xa17,0xa08-0xa0b,0xa20-0xa2f at device 13.0 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xa20 atapci0: [MPSAFE] atapci0: [ITHREAD] atapci0: using PIO transfers above 137GB as workaround for 48bit DMA access bug, expect reduced performance ata2: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0xa00 atapci0: Reserved 0x4 bytes for rid 0x14 type 4 at 0xa18 ata2: reset tp1 mask=03 ostat0=50 ostat1=00 ata2: stat0=0x90 err=0x90 lsb=0x90 msb=0x90 ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata2: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata2: reset tp2 stat0=50 stat1=00 devices=0x1 ata2: [MPSAFE] ata2: [ITHREAD] ata3: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0xa10 atapci0: Reserved 0x4 bytes for rid 0x1c type 4 at 0xa08 ata3: reset tp1 mask=03 ostat0=00 ostat1=00 ata3: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata3: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata3: reset tp2 stat0=00 stat1=00 devices=0x10000 ata3: [MPSAFE] ata3: [ITHREAD] ohci2: mem 0x3000000-0x3000fff at device 8.0 on pci1 ohci2: Reserved 0x1000 bytes for rid 0x10 type 3 at 0x3000000 pcib1: slot 8 INTA is routed to irq 16 pcib0: installed DMA sync wrapper for device 8.0 on bus 1 ohci2: [MPSAFE] ohci2: [ITHREAD] usbus2: on ohci2 ohci3: mem 0x3002000-0x3002fff at device 8.1 on pci1 ohci3: Reserved 0x1000 bytes for rid 0x10 type 3 at 0x3002000 pcib1: slot 8 INTB is routed to irq 17 pcib0: installed DMA sync wrapper for device 8.1 on bus 1 ohci3: [MPSAFE] ohci3: [ITHREAD] usbus3: on ohci3 ehci0: mem 0x3004000-0x30040ff at device 8.2 on pci1 ehci0: Reserved 0x100 bytes for rid 0x10 type 3 at 0x3004000 pcib1: slot 8 INTC is routed to irq 18 pcib0: installed DMA sync wrapper for device 8.2 on bus 1 ehci0: [MPSAFE] ehci0: [ITHREAD] usbus4: EHCI version 1.0 usbus4: on ehci0 fwohci0: mem 0x3006000-0x30067ff,0x3008000-0x300bfff at device 11.0 on pci1 fwohci0: Reserved 0x800 bytes for rid 0x10 type 3 at 0x3006000 pcib1: slot 11 INTA is routed to irq 19 pcib0: installed DMA sync wrapper for device 11.0 on bus 1 fwohci0: [MPSAFE] fwohci0: [ITHREAD] fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:05:16:00:00:71:20:54 fwohci0: Phy 1394a available S400, 3 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0xc1590000 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:05:16:71:20:54 fwe0: bpf attached fwe0: Ethernet address: 02:05:16:71:20:54 fwip0: on firewire0 fwip0: bpf attached fwip0: Firewire address: 00:05:16:00:00:71:20:54 @ 0xfffe00000000, S400, maxrec 2048 fwohci0: Initiate bus reset fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=0x00000000, SelfID Count=1, CYCLEMASTER mode machfb0: port 0xb00-0xbff mem 0x4000000-0x4ffffff,0x102000-0x102fff at device 5.0 on pci0 machfb0: console machfb0: Reserved 0x1000000 bytes for rid 0x10 type 3 at 0x4000000 machfb0: Reserved 0x1000 bytes for rid 0x18 type 3 at 0x102000 machfb0: 16 MB aperture at 0xfddcc000 not swapped machfb0: 8188 KB SGRAM 114.992 MHz, maximum RAMDAC clock 230 MHz, DSP machfb0: resolution 1152x900 at 8 bpp jbusppm0: mem 0x4000f000000-0x4000f000007,0x4000f410050-0x4000f41005f on nexus0 jbusppm0: master I/O bridge jbusppm0: running at full speed bge0: mem 0x200000-0x20ffff at device 2.0 on pci2 bge0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0x200000 bge0: CHIP ID 0x00001002; ASIC REV 0x01; CHIP REV 0x10; PCI miibus0: on bge0 brgphy0: PHY 1 on miibus0 brgphy0: OUI 0x000818, model 0x0016, rev. 2 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow bge0: bpf attached bge0: Ethernet address: 00:14:4f:23:7e:fe bge0: [MPSAFE] bge0: [ITHREAD] nexus0: mem 0x4000fc64000-0x4000fc6400f type i2c (no driver attached) syscons0: on nexus0 syscons0: Unknown <16 virtual consoles, flags=0x300> syscons0: fb0, kbd0, terminal emulator: scteken (teken terminal) (null) failed to probe at iomem 0xf0000000-0xf00fffff on isa0 rtc0: at port 0x70-0x71 on isa0 rtc0: registered as a time-of-day clock (resolution 1000000us) ct_to_ts([2012-01-15 15:52:10]) = 1326642730.000000000 rtc0: current time: 1326642730.000000000 (null) failed to probe at port 0x320-0x321 irq 46 on isa0 (null) failed to probe at port 0x800-0x82f irq 32 on isa0 uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 44 on isa0 uart0: [FILTER] uart0: fast interrupt uart1: <16550 or compatible> at port 0x2e8-0x2ef irq 44 on isa0 uart1: [FILTER] uart1: fast interrupt (null) failed to probe at port 0-0xffff on isa0 (null) failed to probe at port 0x378-0x37f,0-0x4ff drq 1 on isa0 procfs registered Timecounter "tick" frequency 1503000000 Hz quality 1000 Timecounter "stick" frequency 12000000 Hz quality 1000 Timecounters tick every 1.000 msec vlan: initialized, using hash tables with chaining lo0: bpf attached ata2: Identifying devices: 00000001 ata2: New devices: 00000001 firewire0: 1 nodes, maxhop <= 0 cable IRM irm(0) (me) firewire0: bus manager 0 usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 12Mbps Full Speed USB v1.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 usbus3: 12Mbps Full Speed USB v1.0 usbus4: 480Mbps High Speed USB v2.0 ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=80 wire ugen3.1: at usbus3 uhub3: on usbus3 ugen4.1: at usbus4 uhub4: on usbus4 ad0: setting UDMA100 ad0: 114473MB at ata2-master UDMA100 ad0: 234441648 sectors [232581C/16H/63S] 16 sectors/interrupt 1 depth queue ata3: Identifying devices: 00010000 ata3: New devices: 00010000 GEOM: new disk ad0 ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA66 cable=40 wire acd0: setting UDMA66 acd0: DVDR drive at ata3 as master acd0: read 8269KB/s (8269KB/s) write 8269KB/s (8269KB/s), 2048KB buffer, UDMA66 acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, DVDRAM, packet acd0: Writes: CDR, CDRW, DVDR, DVDRAM, test write, burnproof acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: CD-R 120mm data disc GEOM: ad0: adding VTOC8 information. uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered uhub3: 2 ports with 2 removable, self powered uhub2: 3 ports with 3 removable, self powered ugen1.2: at usbus1 ukbd0: on usbus1 kbd: new array size 4 kbd1 at ukbd0 kbd1: ukbd0, generic (0), config:0x0, flags:0x3d0000 uhid0: on usbus1 ugen1.3: at usbus1 ums0: on usbus1 ums0: 8 buttons and [XYZT] coordinates ID=0 uhub4: 5 ports with 5 removable, self powered acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x05 Trying to mount root from ufs:/dev/ad0a ct_to_ts([2012-01-15 15:52:21]) = 1326642741.000000000 start_init: trying /sbin/init Please let me know if I can provide more help. Thanks, -cpghost. -- Cordula's Web. http://www.cordula.ws/ From owner-freebsd-sparc64@FreeBSD.ORG Sun Jan 15 16:40:12 2012 Return-Path: Delivered-To: freebsd-sparc64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B3167106564A for ; Sun, 15 Jan 2012 16:40:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A1F878FC16 for ; Sun, 15 Jan 2012 16:40:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0FGeCIn097207 for ; Sun, 15 Jan 2012 16:40:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0FGeCh2097206; Sun, 15 Jan 2012 16:40:12 GMT (envelope-from gnats) Date: Sun, 15 Jan 2012 16:40:12 GMT Message-Id: <201201151640.q0FGeCh2097206@freefall.freebsd.org> To: freebsd-sparc64@FreeBSD.org From: Guy M Broome/FS/VCU Cc: Subject: Re: sparc64/164123: Kernel fails to boot on Sun Ultra 5 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Guy M Broome/FS/VCU List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jan 2012 16:40:12 -0000 The following reply was made to PR sparc64/164123; it has been noted by GNATS. From: Guy M Broome/FS/VCU To: Marius Strobl Cc: bug-followup@FreeBSD.org Subject: Re: sparc64/164123: Kernel fails to boot on Sun Ultra 5 Date: Sun, 15 Jan 2012 11:37:21 -0500 According to GDB, the problem is coming from line 237 of src/sys/dev/uart/u= art=5Fkbd=5Fsun.h: -------------------------------------------------------------------- 233: uart=5Finit(&uart=5Fkeyboard); 234: 235: uart=5Fkeyboard.type =3D UART=5FDEV=5FKEYBOARD; 236: uart=5Fkeyboard.attach =3D sunkbd=5Fattach; 237: uart=5Fadd=5Fsysdev(&uart=5Fkeyboard); 238: 239: if (sunkbd=5Fprobe=5Fkeyboard(&uart=5Fkeyboard) !=3D KB=5FSUN4) 240: return (0); -------------------------------------------------------------------- I'm trying to hunt through the CVS tree to find any changes made to the UAR= T code between 9.0-RC1 and 9.0-RELEASE, but that's proving rather tedious a= s I have little to no experience with either CVS or SVN. --Guy From owner-freebsd-sparc64@FreeBSD.ORG Sun Jan 15 22:30:15 2012 Return-Path: Delivered-To: freebsd-sparc64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 428661065679 for ; Sun, 15 Jan 2012 22:30:15 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2CB048FC1A for ; Sun, 15 Jan 2012 22:30:15 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0FMUFXl020237 for ; Sun, 15 Jan 2012 22:30:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0FMUFbY020232; Sun, 15 Jan 2012 22:30:15 GMT (envelope-from gnats) Date: Sun, 15 Jan 2012 22:30:15 GMT Message-Id: <201201152230.q0FMUFbY020232@freefall.freebsd.org> To: freebsd-sparc64@FreeBSD.org From: Marius Strobl Cc: Subject: Re: sparc64/164123: Kernel fails to boot on Sun Ultra 5 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marius Strobl List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jan 2012 22:30:15 -0000 The following reply was made to PR sparc64/164123; it has been noted by GNATS. From: Marius Strobl To: Guy M Broome/FS/VCU Cc: bug-followup@FreeBSD.org Subject: Re: sparc64/164123: Kernel fails to boot on Sun Ultra 5 Date: Sun, 15 Jan 2012 23:23:52 +0100 On Sun, Jan 15, 2012 at 09:42:05AM -0500, Guy M Broome/FS/VCU wrote: > Marius, > > Nevermind tomorrow- I had a chance to get the debugging output immediately. > > After attempting to boot the debug kernel you provided, > > The result of "ctrace" is: > --------------------------------------------- > > PC: c07dc388 > Last leaf: XXXXXXX???? from c07dc350 > ?????? 0 w?? %o0-%o5?? (c0b93888 4b0 8 1 0 4 ) > > --------------------------------------------- > Thanks, I now understand what's going on. Basically this is the same issue as described in the commit log of r227537, I'm not yet sure how to solve this for uart(4) though. Marius From owner-freebsd-sparc64@FreeBSD.ORG Mon Jan 16 11:07:12 2012 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 91A961065670 for ; Mon, 16 Jan 2012 11:07:12 +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 7F4038FC15 for ; Mon, 16 Jan 2012 11:07:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0GB7BVV057766 for ; Mon, 16 Jan 2012 11:07:11 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0GB7B85057764 for freebsd-sparc64@FreeBSD.org; Mon, 16 Jan 2012 11:07:11 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 16 Jan 2012 11:07:11 GMT Message-Id: <201201161107.q0GB7B85057764@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, 16 Jan 2012 11:07:12 -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 -------------------------------------------------------------------------------- o sparc/164123 sparc64 [boot] Kernel fails to boot on Sun Ultra 5 o sparc/162513 sparc64 mpt(4), mptutil(8) reports variable, erroneous drive i o sparc/141918 sparc64 [ehci] ehci_interrupt: unrecoverable error, controller s sparc/139134 sparc64 kernel output corruption s sparc/107087 sparc64 [hang] system is hung during boot from CD o sparc/105048 sparc64 [trm] trm(4) panics on sparc64 o sparc/104428 sparc64 [nullfs] nullfs panics on E4500 (but not E420) o sparc/71729 sparc64 printf in kernel thread causes panic on SPARC 8 problems total. From owner-freebsd-sparc64@FreeBSD.ORG Mon Jan 16 13:54:41 2012 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 B68DD106566C; Mon, 16 Jan 2012 13:54:41 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 7D5438FC0A; Mon, 16 Jan 2012 13:54:41 +0000 (UTC) Received: by obcwo16 with SMTP id wo16so1434520obc.13 for ; Mon, 16 Jan 2012 05:54:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.0.106 with SMTP id 10mr10959494obd.72.1326722081079; Mon, 16 Jan 2012 05:54:41 -0800 (PST) Received: by 10.182.150.69 with HTTP; Mon, 16 Jan 2012 05:54:41 -0800 (PST) X-Originating-IP: [93.221.190.159] Date: Mon, 16 Jan 2012 14:54:41 +0100 Message-ID: From: "C. P. Ghost" To: freebsd-sparc64 Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable Subject: Reading from CDROM broken on 9.0-RELEASE/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: Mon, 16 Jan 2012 13:54:41 -0000 Hello, I think that reading from CDROM is actually broken in 9.0-RELEASE/sparc64. On FreeBSD 8.2-RELEASE/sparc64, mounting a physical CDROM burned with FreeBSD-9.0-RELEASE-sparc64-disc1.iso and running sha256 on usr/freebsd-dist/*.txz yields the same results as listed in usr/freebsd-dist/MANIFEST. However, on FreeBSD 9.0-RELEASE/sparc64, mounting the same CDROM (using /dev/cd0), and running sha256 on the same usr/freebsd-dist/*.txz files yields completely different results: SHA256 (base.txz) = a96e255a9379ec1a58b756c3e788e34345fd79e35234925df842d700ccb10e1a SHA256 (doc.txz) = 54674bb68b111c3465b0beca8893a6b514b80e20dc22f2bbd208b992568261dc SHA256 (games.txz) = b9bedddeea549640b4f41a577f4c5f09aa29d0c3d0d4c105bc4fe7d327bf9fcd SHA256 (kernel.txz) = 661df36b4a2e87d2aa88ce998b50d48f2a91892fc288452a0282e3c092739046 SHA256 (ports.txz) = 315cbfac6f252de5209a3513a846d14650b98e2dcf99c12779ffd1d32acaa287 SHA256 (src.txz) = 6b3a4a9536b1ca2618949bb7bb44478266db551ac9f09ccfc92b5469a715f3cf This also prevents an installation of 9.0-RELEASE/sparc64 via bsdinstall from CDROM (bsdinistall says that the data sets are corrupted). I was only able to get 9.0 on that SunBlade 1500 by using a regular source upgrade from a running 8.2-RELEASE system (using usr/freebsd-dist/src.txz from that very same CDROM that checksummed correctly on 8.2-RELEASE). Just to make it clear: the CDROM media is correct and checksums correctly on 8.2-RELEASE. It doesn't checksum correctly on 9.0-RELEASE because reading from CDROM media is now (partially) broken. Just to make sure the 9.0-RELEASE sha256 program isn't at fault, I've mounted FreeBSD-9.0-RELEASE-sparc64-disc1.iso via mdconfig and run sha256 on the *.txz files again: same results as in MANIFEST. So sha256 on 9.0 itself is okay, it's only the reading from physical media that corrupts data (and prevents installation from CDROM -- funny that this passed release engineering and testing...). Thanks, -cpghost. -- Cordula's Web. http://www.cordula.ws/ From owner-freebsd-sparc64@FreeBSD.ORG Mon Jan 16 16:59:48 2012 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 CCD73106564A; Mon, 16 Jan 2012 16:59:48 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8FBFC8FC0C; Mon, 16 Jan 2012 16:59:48 +0000 (UTC) Received: by obcwo16 with SMTP id wo16so1712887obc.13 for ; Mon, 16 Jan 2012 08:59:48 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.116.38 with SMTP id jt6mr11718146obb.52.1326733187223; Mon, 16 Jan 2012 08:59:47 -0800 (PST) Received: by 10.182.150.69 with HTTP; Mon, 16 Jan 2012 08:59:47 -0800 (PST) X-Originating-IP: [93.221.190.159] In-Reply-To: References: Date: Mon, 16 Jan 2012 17:59:47 +0100 Message-ID: From: "C. P. Ghost" To: freebsd-sparc64 Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable Subject: Re: Reading from CDROM broken on 9.0-RELEASE/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: Mon, 16 Jan 2012 16:59:48 -0000 On Mon, Jan 16, 2012 at 2:54 PM, C. P. Ghost wrote: > Hello, > > I think that reading from CDROM is actually broken > in 9.0-RELEASE/sparc64. > > On FreeBSD 8.2-RELEASE/sparc64, mounting a physical > CDROM burned with FreeBSD-9.0-RELEASE-sparc64-disc1.iso > and running sha256 on usr/freebsd-dist/*.txz yields the same > results as listed in usr/freebsd-dist/MANIFEST. > > However, on FreeBSD 9.0-RELEASE/sparc64, mounting the > same CDROM (using /dev/cd0), and running sha256 on the > same usr/freebsd-dist/*.txz files yields completely different results: > > SHA256 (base.txz) = > a96e255a9379ec1a58b756c3e788e34345fd79e35234925df842d700ccb10e1a > SHA256 (doc.txz) = > 54674bb68b111c3465b0beca8893a6b514b80e20dc22f2bbd208b992568261dc > SHA256 (games.txz) = > b9bedddeea549640b4f41a577f4c5f09aa29d0c3d0d4c105bc4fe7d327bf9fcd > SHA256 (kernel.txz) = > 661df36b4a2e87d2aa88ce998b50d48f2a91892fc288452a0282e3c092739046 > SHA256 (ports.txz) = > 315cbfac6f252de5209a3513a846d14650b98e2dcf99c12779ffd1d32acaa287 > SHA256 (src.txz) = > 6b3a4a9536b1ca2618949bb7bb44478266db551ac9f09ccfc92b5469a715f3cf > > This also prevents an installation of 9.0-RELEASE/sparc64 > via bsdinstall from CDROM (bsdinistall says that the data sets > are corrupted). I was only able to get 9.0 on that SunBlade 1500 > by using a regular source upgrade from a running 8.2-RELEASE > system (using usr/freebsd-dist/src.txz from that very same CDROM > that checksummed correctly on 8.2-RELEASE). > > Just to make it clear: the CDROM media is correct and checksums > correctly on 8.2-RELEASE. It doesn't checksum correctly on 9.0-RELEASE > because reading from CDROM media is now (partially) broken. > > Just to make sure the 9.0-RELEASE sha256 program isn't at fault, > I've mounted FreeBSD-9.0-RELEASE-sparc64-disc1.iso via mdconfig > and run sha256 on the *.txz files again: same results as in MANIFEST. > So sha256 on 9.0 itself is okay, it's only the reading from physical > media that corrupts data (and prevents installation from CDROM -- funny > that this passed release engineering and testing...). One more thing: With a 9.0-RELEASE world installed, if I boot the old 8.2-RELEASE kernel (/boot/kernel.old/kernel), mount /dev/acd0 and checksum the files with sha256, everything is okay. If I boot again the new 9.0-RELEASE kernel (/boot/kernel/kernel), mount /dev/cd0 and checksum the files with sha256, I get the wrong results above. Since there's no /dev/acd0 on 9.0-RELEASE, I can't test mounting that on 9 and compare the results with /dev/cd0. But obviously, whatever /dev/cd0 returns to cd9660 seems to be silently corrupted on 9.0; at least on sparc64. -cpghost. -- Cordula's Web. http://www.cordula.ws/ From owner-freebsd-sparc64@FreeBSD.ORG Mon Jan 16 18:44:15 2012 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 9F142106566C for ; Mon, 16 Jan 2012 18:44:15 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6F6B28FC0A for ; Mon, 16 Jan 2012 18:44:15 +0000 (UTC) Received: by obcwo16 with SMTP id wo16so1863582obc.13 for ; Mon, 16 Jan 2012 10:44:14 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.116.38 with SMTP id jt6mr12029615obb.52.1326739454842; Mon, 16 Jan 2012 10:44:14 -0800 (PST) Received: by 10.182.150.69 with HTTP; Mon, 16 Jan 2012 10:44:14 -0800 (PST) X-Originating-IP: [93.221.190.159] In-Reply-To: References: Date: Mon, 16 Jan 2012 19:44:14 +0100 Message-ID: From: "C. P. Ghost" To: Garrett Cooper Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-sparc64 Subject: Re: Reading from CDROM broken on 9.0-RELEASE/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: Mon, 16 Jan 2012 18:44:15 -0000 On Mon, Jan 16, 2012 at 6:05 PM, Garrett Cooper wrote: > What happens if you remove ATA_CAM from the kernel and try and boot > with that in 9.0? There might be some endianness bugs that mav@ wasn't > aware of in the new ata code.. No joy here. Booting the new kernel stops at mountroot: Mounting from ufs:/dev/ad0a failed with error 19. mountroot> ? List of GEOM managed disk devices mountroot> ufs:/dev/ad0a Mounting from ufs:/dev/ad0a failed with error 19. mountroot> I've only removed option ATA_CAM from GENERIC, but didn't change anything else. Any idea where the root filesystem is supposed to be in this case? On 8.2-RELEASE it was/is definitely under /dev/ad0a... Thanks, -cpghost. -- Cordula's Web. http://www.cordula.ws/ From owner-freebsd-sparc64@FreeBSD.ORG Tue Jan 17 00:40:08 2012 Return-Path: Delivered-To: freebsd-sparc64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 030A11065670 for ; Tue, 17 Jan 2012 00:40:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id CFE768FC14 for ; Tue, 17 Jan 2012 00:40:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0H0e7b6010201 for ; Tue, 17 Jan 2012 00:40:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0H0e7Ur010200; Tue, 17 Jan 2012 00:40:07 GMT (envelope-from gnats) Resent-Date: Tue, 17 Jan 2012 00:40:07 GMT Resent-Message-Id: <201201170040.q0H0e7Ur010200@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-sparc64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, "C. P. Ghost" Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 95544106564A for ; Tue, 17 Jan 2012 00:31:43 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 800A68FC1A for ; Tue, 17 Jan 2012 00:31:43 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id q0H0Vhj1062956 for ; Tue, 17 Jan 2012 00:31:43 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id q0H0VhqN062955; Tue, 17 Jan 2012 00:31:43 GMT (envelope-from nobody) Message-Id: <201201170031.q0H0VhqN062955@red.freebsd.org> Date: Tue, 17 Jan 2012 00:31:43 GMT From: "C. P. Ghost" To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: sparc64/164226: Data corruption on 9.0-RELEASE when reading from CDROM 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, 17 Jan 2012 00:40:08 -0000 >Number: 164226 >Category: sparc64 >Synopsis: Data corruption on 9.0-RELEASE when reading from CDROM >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-sparc64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jan 17 00:40:07 UTC 2012 >Closed-Date: >Last-Modified: >Originator: C. P. Ghost >Release: FreeBSD 9.0-RELEASE/sparc64 >Organization: Cordula's Web >Environment: FreeBSD tarazed.cordula.ws 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Mon Jan 16 01:51:15 CET 2012 root@tarazed.cordula.ws:/usr/obj/usr/src/sys/GENERIC sparc64 >Description: It's not possible to install FreeBSD 9.0-RELEASE from CDROM on a Blade 1500, because bsdinstall reports a corrupt base.txz. Investigating the issue further, revealed that the 9.0 kernel corrupts data read from a CDROM mounted via /dev/cd0, while the 8.2 kernel doesn't corrupt data when the CDROM is mounted via /dev/acd0. >How-To-Repeat: 8.2-RELEASE doesn't exhibit the bug: 1. Install 8.2-RELEASE on a sun4u system. 2. Mount the 9.0-RELEASE CDROM (using /dev/acd0) 3. cd /cdrom/usr/freebsd-dist; sha256 *.txz; 4. compare with MANIFEST -> same checksums. Upgrade to 9.0-RELEASE, e.g. from source: 4. mv /usr/src /usr/src.82 5. cd /; tar -xvpf /cdrom/usr/freebsd-dist/src.txz 6. source upgrade from 8.2 to 9.0 9.0-RELEASE exhibits the problem: 7. Reboot to 9.0-RELEASE 8. Mount the 9.0-RELEASE CDROM (using /dev/cd0) 9. cd /cdrom/usr/freebsd-dist; sha256 *.txz 10. compare checksums with MANIFEST -> different checksums! Reboot 9.0 userland to 8.2 (/boot/kernel.old/kernel) and repeat sha256 checksums -> no errors. Note, the sha256 program on 9.0 yields the same checksums on arbitrary files than on 8.2, as long as those files are not read from CDROM (e.g. fetched from the net). It is okay. >Fix: No fix known yet. Workaround: netboot 9.0, or source-upgrade from a previous release. Don't use CDROM (/dev/cd0) on 9.0 until this bug is fixed. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-sparc64@FreeBSD.ORG Tue Jan 17 00:50:10 2012 Return-Path: Delivered-To: freebsd-sparc64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5AF291065674 for ; Tue, 17 Jan 2012 00:50:10 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 324A58FC12 for ; Tue, 17 Jan 2012 00:50:10 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0H0oAEh019235 for ; Tue, 17 Jan 2012 00:50:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0H0oAAh019234; Tue, 17 Jan 2012 00:50:10 GMT (envelope-from gnats) Resent-Date: Tue, 17 Jan 2012 00:50:10 GMT Resent-Message-Id: <201201170050.q0H0oAAh019234@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-sparc64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, "C. P. Ghost" Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED1291065670 for ; Tue, 17 Jan 2012 00:47:14 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id D5E178FC0C for ; Tue, 17 Jan 2012 00:47:14 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id q0H0lE8S097647 for ; Tue, 17 Jan 2012 00:47:14 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id q0H0lEV4097646; Tue, 17 Jan 2012 00:47:14 GMT (envelope-from nobody) Message-Id: <201201170047.q0H0lEV4097646@red.freebsd.org> Date: Tue, 17 Jan 2012 00:47:14 GMT From: "C. P. Ghost" To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: sparc64/164227: Can't boot 9.0-RELEASE/sparc64 on Blade 1500 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, 17 Jan 2012 00:50:10 -0000 >Number: 164227 >Category: sparc64 >Synopsis: Can't boot 9.0-RELEASE/sparc64 on Blade 1500 >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-sparc64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jan 17 00:50:09 UTC 2012 >Closed-Date: >Last-Modified: >Originator: C. P. Ghost >Release: FreeBSD 9.0-RELEASE/sparc64 >Organization: Cordula's Web >Environment: FreeBSD tarazed.cordula.ws 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Mon Jan 16 01:51:15 CET 2012 root@tarazed.cordula.ws:/usr/obj/usr/src/sys/GENERIC sparc64 >Description: Booting a FreeBSD-9.0-RELEASE kernel on a Blade 1500 panics with: panic: kmem_suballoc: bad status return of 3 cpuid = 0 KDB: stack backtrace: #0 0xc079841c at ??+0 #1 0xc04ca59c at ??+0 #2 0xc0487f90 at ??+0 #3 0xc0098028 at ??+0 This is on a Blade 1500 with 2 GB of RAM. dmesg when verbose booting 8.2-RELEASE with the full 2 GB: Copyright (c) 1992-2011 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.2-RELEASE #0: Thu Feb 17 06:57:44 UTC 2011 root@araz.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC sparc64 Preloaded elf kernel "/boot/GENERIC/kernel" at 0xc0b9c000. real memory = 2147483648 (2048 MB) avail memory = 2079563776 (1983 MB) machine: SUNW,Sun-Blade-1500-S cpu0: Sun Microsystems UltraSparc-IIIi Processor (1503.00 MHz CPU) mask=0x34 maxtl=5 maxwin=7 wlan: <802.11 Link Layer> firmware: 'isp_1000' version 1: 20142 bytes loaded at 0xc0725d38 ispfw: registered firmware firmware: 'isp_1040' version 1: 22944 bytes loaded at 0xc072abe6 ispfw: registered firmware firmware: 'isp_1040_it' version 1: 32942 bytes loaded at 0xc0730586 ispfw: registered firmware firmware: 'isp_1080' version 1: 31350 bytes loaded at 0xc0738634 ispfw: registered firmware firmware: 'isp_1080_it' version 1: 40644 bytes loaded at 0xc07400aa ispfw: registered firmware firmware: 'isp_12160' version 1: 28050 bytes loaded at 0xc0749f6e ispfw: registered firmware firmware: 'isp_12160_it' version 1: 40604 bytes loaded at 0xc0750d00 ispfw: registered firmware firmware: 'isp_2100' version 1: 76770 bytes loaded at 0xc075ab9c ispfw: registered firmware firmware: 'isp_2200' version 1: 77214 bytes loaded at 0xc076d77e ispfw: registered firmware firmware: 'isp_2300' version 1: 106640 bytes loaded at 0xc078051c ispfw: registered firmware firmware: 'isp_2322' version 1: 108856 bytes loaded at 0xc079a5ac ispfw: registered firmware firmware: 'isp_2400' version 1: 177416 bytes loaded at 0xc07b8164 ispfw: registered firmware firmware: 'isp_2400_multi' version 1: 193652 bytes loaded at 0xc07efe54 ispfw: registered firmware firmware: 'isp_2500' version 1: 140732 bytes loaded at 0xc082c140 ispfw: registered firmware firmware: 'isp_2500_multi' version 1: 164528 bytes loaded at 0xc085d0c4 ispfw: registered firmware null: random: nfslock: pseudo-device kbd0 at kbdmux0 openfirm: mem: nexus0: pcib0: mem 0x4000f600000-0x4000f60afff,0x4000f410000-0x4000f41701f,0x7fe00000000-0x7fe000000ff,0x4000f780000-0x4000f78ffff irq 1970,1968,1969,1972,1953 on nexus0 pcib0: Tomatillo, version 4, IGN 0x1e, bus A, 33MHz Timecounter "pcib0" frequency 167000000 Hz quality -100 pcib0: DVMA map: 0xc0000000 to 0xdfffffff 65536 entries pcib0: PROM IOTSB size: 1 (2048 entries) pcib0: adding PROM IOTSB slot 0 (kernel slot 63488) TTE: 0x800000013fde0012 pcib0: adding PROM IOTSB slot 1 (kernel slot 63489) TTE: 0x800000013fde2012 pcib0: adding PROM IOTSB slot 2 (kernel slot 63490) TTE: 0x800000013fde4012 pcib0: adding PROM IOTSB slot 3 (kernel slot 63491) TTE: 0x800000013fde6012 pcib0: adding PROM IOTSB slot 4 (kernel slot 63492) TTE: 0x800000013fde8012 pcib0: adding PROM IOTSB slot 5 (kernel slot 63493) TTE: 0x800000013fdea012 pcib0: adding PROM IOTSB slot 6 (kernel slot 63494) TTE: 0x800000013fdec012 pcib0: adding PROM IOTSB slot 7 (kernel slot 63495) TTE: 0x800000013fdee012 pcib0: adding PROM IOTSB slot 8 (kernel slot 63496) TTE: 0x800000013fdf0012 pcib0: adding PROM IOTSB slot 9 (kernel slot 63497) TTE: 0x800000013fdf2012 pcib0: adding PROM IOTSB slot 10 (kernel slot 63498) TTE: 0x800000013fdf4012 pcib0: adding PROM IOTSB slot 11 (kernel slot 63499) TTE: 0x800000013fdf6012 pcib0: adding PROM IOTSB slot 12 (kernel slot 63500) TTE: 0x800000013fdf8012 pcib0: adding PROM IOTSB slot 13 (kernel slot 63501) TTE: 0x800000013fdfa012 pcib0: adding PROM IOTSB slot 14 (kernel slot 63502) TTE: 0x800000013fdfc012 pcib0: adding PROM IOTSB slot 15 (kernel slot 63503) TTE: 0x800000013fdfe012 pcib0: adding PROM IOTSB slot 16 (kernel slot 63504) TTE: 0x800000013fe00012 pcib0: adding PROM IOTSB slot 17 (kernel slot 63505) TTE: 0x800000013fe02012 pcib0: adding PROM IOTSB slot 18 (kernel slot 63506) TTE: 0x800000013fe04012 pcib0: adding PROM IOTSB slot 19 (kernel slot 63507) TTE: 0x800000013fe06012 pcib0: adding PROM IOTSB slot 20 (kernel slot 63508) TTE: 0x800000013fe08012 pcib0: adding PROM IOTSB slot 21 (kernel slot 63509) TTE: 0x800000013fe0a012 pcib0: adding PROM IOTSB slot 22 (kernel slot 63510) TTE: 0x800000013fe0c012 pcib0: adding PROM IOTSB slot 23 (kernel slot 63511) TTE: 0x800000013fe0e012 pcib0: adding PROM IOTSB slot 24 (kernel slot 63512) TTE: 0x800000013fe10012 pcib0: adding PROM IOTSB slot 25 (kernel slot 63513) TTE: 0x800000013fe12012 pcib0: adding PROM IOTSB slot 26 (kernel slot 63514) TTE: 0x800000013fe14012 pcib0: adding PROM IOTSB slot 27 (kernel slot 63515) TTE: 0x800000013fe16012 pcib0: adding PROM IOTSB slot 28 (kernel slot 63516) TTE: 0x800000013fe18012 pcib0: adding PROM IOTSB slot 29 (kernel slot 63517) TTE: 0x800000013fe1a012 pcib0: adding PROM IOTSB slot 30 (kernel slot 63518) TTE: 0x800000013fe1c012 pcib0: adding PROM IOTSB slot 31 (kernel slot 63519) TTE: 0x800000013fe1e012 pcib0: adding PROM IOTSB slot 32 (kernel slot 63520) TTE: 0x800000013fe20012 pcib0: adding PROM IOTSB slot 33 (kernel slot 63521) TTE: 0x800000013fe22012 pcib0: adding PROM IOTSB slot 34 (kernel slot 63522) TTE: 0x800000013fe24012 pcib0: adding PROM IOTSB slot 35 (kernel slot 63523) TTE: 0x800000013fe26012 pcib0: adding PROM IOTSB slot 36 (kernel slot 63524) TTE: 0x800000013fe28012 pcib0: adding PROM IOTSB slot 37 (kernel slot 63525) TTE: 0x800000013fe2a012 pcib0: adding PROM IOTSB slot 38 (kernel slot 63526) TTE: 0x800000013fe2c012 pcib0: adding PROM IOTSB slot 39 (kernel slot 63527) TTE: 0x800000013fe2e012 pcib0: adding PROM IOTSB slot 40 (kernel slot 63528) TTE: 0x800000013fe30012 pcib0: adding PROM IOTSB slot 41 (kernel slot 63529) TTE: 0x800000013fe32012 pcib0: adding PROM IOTSB slot 42 (kernel slot 63530) TTE: 0x800000013fe34012 pcib0: adding PROM IOTSB slot 43 (kernel slot 63531) TTE: 0x800000013fe36012 pcib0: adding PROM IOTSB slot 44 (kernel slot 63532) TTE: 0x800000013fe38012 pcib0: adding PROM IOTSB slot 45 (kernel slot 63533) TTE: 0x800000013fe3a012 pcib0: adding PROM IOTSB slot 46 (kernel slot 63534) TTE: 0x800000013fe3c012 pcib0: adding PROM IOTSB slot 47 (kernel slot 63535) TTE: 0x800000013fe3e012 pcib0: adding PROM IOTSB slot 48 (kernel slot 63536) TTE: 0x800000013fe40012 pcib0: adding PROM IOTSB slot 49 (kernel slot 63537) TTE: 0x800000013fe42012 pcib0: adding PROM IOTSB slot 50 (kernel slot 63538) TTE: 0x800000013fe44012 pcib0: adding PROM IOTSB slot 51 (kernel slot 63539) TTE: 0x800000013fe46012 pcib0: adding PROM IOTSB slot 52 (kernel slot 63540) TTE: 0x800000013fe48012 pcib0: adding PROM IOTSB slot 53 (kernel slot 63541) TTE: 0x800000013fe4a012 pcib0: adding PROM IOTSB slot 54 (kernel slot 63542) TTE: 0x800000013fe4c012 pcib0: adding PROM IOTSB slot 55 (kernel slot 63543) TTE: 0x800000013fe4e012 pcib0: adding PROM IOTSB slot 56 (kernel slot 63544) TTE: 0x800000013fe50012 pcib0: adding PROM IOTSB slot 57 (kernel slot 63545) TTE: 0x800000013fe52012 pcib0: adding PROM IOTSB slot 58 (kernel slot 63546) TTE: 0x800000013fe54012 pcib0: adding PROM IOTSB slot 59 (kernel slot 63547) TTE: 0x800000013fe56012 pcib0: adding PROM IOTSB slot 60 (kernel slot 63548) TTE: 0x800000013fe58012 pcib0: adding PROM IOTSB slot 61 (kernel slot 63549) TTE: 0x800000013fe5a012 pcib0: adding PROM IOTSB slot 62 (kernel slot 63550) TTE: 0x800000013fe5c012 pcib0: adding PROM IOTSB slot 63 (kernel slot 63551) TTE: 0x800000013fe5e012 pcib0: adding PROM IOTSB slot 64 (kernel slot 63552) TTE: 0x800000013fe60012 pcib0: adding PROM IOTSB slot 65 (kernel slot 63553) TTE: 0x800000013fe62012 pcib0: adding PROM IOTSB slot 66 (kernel slot 63554) TTE: 0x800000013fe64012 pcib0: adding PROM IOTSB slot 67 (kernel slot 63555) TTE: 0x800000013fe66012 pcib0: adding PROM IOTSB slot 68 (kernel slot 63556) TTE: 0x800000013fe68012 pcib0: adding PROM IOTSB slot 69 (kernel slot 63557) TTE: 0x800000013fe6a012 pcib0: adding PROM IOTSB slot 70 (kernel slot 63558) TTE: 0x800000013fe6c012 pcib0: adding PROM IOTSB slot 71 (kernel slot 63559) TTE: 0x800000013fe6e012 pcib0: adding PROM IOTSB slot 72 (kernel slot 63560) TTE: 0x800000013fe70012 pcib0: adding PROM IOTSB slot 73 (kernel slot 63561) TTE: 0x800000013fe72012 pcib0: adding PROM IOTSB slot 74 (kernel slot 63562) TTE: 0x800000013fe74012 pcib0: adding PROM IOTSB slot 75 (kernel slot 63563) TTE: 0x800000013fe76012 pcib0: adding PROM IOTSB slot 76 (kernel slot 63564) TTE: 0x800000013fe78012 pcib0: adding PROM IOTSB slot 77 (kernel slot 63565) TTE: 0x800000013fe7a012 pcib0: adding PROM IOTSB slot 78 (kernel slot 63566) TTE: 0x800000013fe7c012 pcib0: adding PROM IOTSB slot 79 (kernel slot 63567) TTE: 0x800000013fe7e012 pcib0: adding PROM IOTSB slot 80 (kernel slot 63568) TTE: 0x800000013fe80012 pcib0: adding PROM IOTSB slot 81 (kernel slot 63569) TTE: 0x800000013fe82012 pcib0: adding PROM IOTSB slot 82 (kernel slot 63570) TTE: 0x800000013fe84012 pcib0: adding PROM IOTSB slot 83 (kernel slot 63571) TTE: 0x800000013fe86012 pcib0: adding PROM IOTSB slot 84 (kernel slot 63572) TTE: 0x800000013fe88012 pcib0: adding PROM IOTSB slot 85 (kernel slot 63573) TTE: 0x800000013fe8a012 pcib0: adding PROM IOTSB slot 86 (kernel slot 63574) TTE: 0x800000013fe8c012 pcib0: adding PROM IOTSB slot 87 (kernel slot 63575) TTE: 0x800000013fe8e012 pcib0: adding PROM IOTSB slot 88 (kernel slot 63576) TTE: 0x800000013fe90012 pcib0: adding PROM IOTSB slot 89 (kernel slot 63577) TTE: 0x800000013fe92012 pcib0: adding PROM IOTSB slot 90 (kernel slot 63578) TTE: 0x800000013fe94012 pcib0: adding PROM IOTSB slot 91 (kernel slot 63579) TTE: 0x800000013fe96012 pcib0: adding PROM IOTSB slot 92 (kernel slot 63580) TTE: 0x800000013fe98012 pcib0: adding PROM IOTSB slot 93 (kernel slot 63581) TTE: 0x800000013fe9a012 pcib0: adding PROM IOTSB slot 94 (kernel slot 63582) TTE: 0x800000013fe9c012 pcib0: adding PROM IOTSB slot 95 (kernel slot 63583) TTE: 0x800000013fe9e012 pcib0: adding PROM IOTSB slot 96 (kernel slot 63584) TTE: 0x800000013fea0012 pcib0: adding PROM IOTSB slot 97 (kernel slot 63585) TTE: 0x800000013fea2012 pcib0: adding PROM IOTSB slot 98 (kernel slot 63586) TTE: 0x800000013fea4012 pcib0: adding PROM IOTSB slot 99 (kernel slot 63587) TTE: 0x800000013fea6012 pcib0: adding PROM IOTSB slot 100 (kernel slot 63588) TTE: 0x800000013fea8012 pcib0: adding PROM IOTSB slot 101 (kernel slot 63589) TTE: 0x800000013feaa012 pcib0: adding PROM IOTSB slot 102 (kernel slot 63590) TTE: 0x800000013feac012 pcib0: adding PROM IOTSB slot 103 (kernel slot 63591) TTE: 0x800000013feae012 pcib0: adding PROM IOTSB slot 104 (kernel slot 63592) TTE: 0x800000013feb0012 pcib0: adding PROM IOTSB slot 105 (kernel slot 63593) TTE: 0x800000013feb2012 pcib0: adding PROM IOTSB slot 106 (kernel slot 63594) TTE: 0x800000013feb4012 pcib0: adding PROM IOTSB slot 107 (kernel slot 63595) TTE: 0x800000013feb6012 pcib0: adding PROM IOTSB slot 108 (kernel slot 63596) TTE: 0x800000013feb8012 pcib0: adding PROM IOTSB slot 109 (kernel slot 63597) TTE: 0x800000013feba012 pcib0: adding PROM IOTSB slot 110 (kernel slot 63598) TTE: 0x800000013febc012 pcib0: adding PROM IOTSB slot 111 (kernel slot 63599) TTE: 0x800000013febe012 pcib0: adding PROM IOTSB slot 112 (kernel slot 63600) TTE: 0x800000013fec0012 pcib0: adding PROM IOTSB slot 113 (kernel slot 63601) TTE: 0x800000013fec2012 pcib0: adding PROM IOTSB slot 114 (kernel slot 63602) TTE: 0x800000013fec4012 pcib0: adding PROM IOTSB slot 115 (kernel slot 63603) TTE: 0x800000013fec6012 pcib0: adding PROM IOTSB slot 116 (kernel slot 63604) TTE: 0x800000013fec8012 pcib0: adding PROM IOTSB slot 117 (kernel slot 63605) TTE: 0x800000013feca012 pcib0: adding PROM IOTSB slot 118 (kernel slot 63606) TTE: 0x800000013fecc012 pcib0: adding PROM IOTSB slot 119 (kernel slot 63607) TTE: 0x800000013fece012 pcib0: adding PROM IOTSB slot 120 (kernel slot 63608) TTE: 0x800000013fed0012 pcib0: adding PROM IOTSB slot 121 (kernel slot 63609) TTE: 0x800000013fed2012 pcib0: adding PROM IOTSB slot 122 (kernel slot 63610) TTE: 0x800000013fed4012 pcib0: adding PROM IOTSB slot 123 (kernel slot 63611) TTE: 0x800000013fed6012 pcib0: adding PROM IOTSB slot 124 (kernel slot 63612) TTE: 0x800000013fed8012 pcib0: adding PROM IOTSB slot 125 (kernel slot 63613) TTE: 0x800000013feda012 pcib0: adding PROM IOTSB slot 126 (kernel slot 63614) TTE: 0x800000013fedc012 pcib0: adding PROM IOTSB slot 127 (kernel slot 63615) TTE: 0x800000013fede012 pcib0: bus range 0 to 1; PCI bus 0 initalizing intr_countp pcib0: [FILTER] pci0: on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x108e, dev=0xa801, revid=0x00 domain=0, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0146, statreg=0x02a0, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10b9, dev=0x1533, revid=0x00 domain=0, bus=0, slot=7, func=0 class=06-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x000f, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) powerspec 1 supports D0 D3 current D0 found-> vendor=0x10b9, dev=0x7101, revid=0x00 domain=0, bus=0, slot=6, func=0 class=00-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10b9, dev=0x5451, revid=0x02 domain=0, bus=0, slot=8, func=0 class=04-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x10 (480 ns), mingnt=0x02 (500 ns), maxlat=0x18 (6000 ns) intpin=a, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type I/O Port, range 32, base 0x900, size 8, port disabled map[14]: type Memory, range 32, base 0x100000, size 12, memory disabled found-> vendor=0x10b9, dev=0x5237, revid=0x03 domain=0, bus=0, slot=10, func=0 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x50 (20000 ns) intpin=a, irq=255 powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 32, base 0x1000000, size 12, memory disabled found-> vendor=0x10b9, dev=0x5237, revid=0x03 domain=0, bus=0, slot=11, func=0 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x0146, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x50 (20000 ns) intpin=a, irq=255 powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 32, base 0x2000000, size 12, enabled found-> vendor=0x10b9, dev=0x5229, revid=0xc4 domain=0, bus=0, slot=13, func=0 class=01-01-ff, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x10 (480 ns), mingnt=0x02 (500 ns), maxlat=0x04 (1000 ns) intpin=a, irq=255 powerspec 2 supports D0 D3 current D0 map[10]: type I/O Port, range 32, base 0xa00, size 3, port disabled map[14]: type I/O Port, range 32, base 0xa18, size 2, enabled map[18]: type I/O Port, range 32, base 0xa10, size 3, enabled map[1c]: type I/O Port, range 32, base 0xa08, size 2, enabled map[20]: type I/O Port, range 32, base 0xa20, size 4, enabled found-> vendor=0x104c, dev=0xac23, revid=0x02 domain=0, bus=0, slot=2, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x0210, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x23 (8750 ns), maxlat=0x00 (0 ns) powerspec 1 supports D0 D3 current D0 found-> vendor=0x1002, dev=0x4752, revid=0x27 domain=0, bus=0, slot=5, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0082, statreg=0x0290, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0x4000000, size 24, enabled map[14]: type I/O Port, range 32, base 0xb00, size 8, port disabled map[18]: type Memory, range 32, base 0x102000, size 12, enabled pcib1: at device 2.0 on pci0 pcib1: domain 0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0x1000-0xfff pcib1: memory decode 0x3000000-0x30fffff pcib1: no prefetched decode pci1: on pcib1 pci1: domain=0, physical bus=1 found-> vendor=0x1033, dev=0x0035, revid=0x43 domain=0, bus=1, slot=8, func=0 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0210, cachelnsz=16 (dwords) lattimer=0x08 (240 ns), mingnt=0x01 (250 ns), maxlat=0x2a (10500 ns) intpin=a, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0x3000000, size 12, memory disabled pcib1: requested memory range 0x3000000-0x3000fff: good found-> vendor=0x1033, dev=0x0035, revid=0x43 domain=0, bus=1, slot=8, func=1 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0210, cachelnsz=16 (dwords) lattimer=0x08 (240 ns), mingnt=0x01 (250 ns), maxlat=0x2a (10500 ns) intpin=b, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0x3002000, size 12, memory disabled pcib1: requested memory range 0x3002000-0x3002fff: good found-> vendor=0x1033, dev=0x00e0, revid=0x04 domain=0, bus=1, slot=8, func=2 class=0c-03-20, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0210, cachelnsz=16 (dwords) lattimer=0x80 (3840 ns), mingnt=0x10 (4000 ns), maxlat=0x22 (8500 ns) intpin=c, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0x3004000, size 8, memory disabled pcib1: requested memory range 0x3004000-0x30040ff: good found-> vendor=0x104c, dev=0x8024, revid=0x00 domain=0, bus=1, slot=11, func=0 class=0c-00-10, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0210, cachelnsz=16 (dwords) lattimer=0x10 (480 ns), mingnt=0x02 (500 ns), maxlat=0x04 (1000 ns) intpin=a, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0x3006000, size 11, memory disabled pcib1: requested memory range 0x3006000-0x30067ff: good map[14]: type Memory, range 32, base 0x3008000, size 14, enabled pcib1: requested memory range 0x3008000-0x300bfff: good pcib2: mem 0x4000ff00000-0x4000ff0afff,0x4000fc10000-0x4000fc1701f,0x7f600000000-0x7f6000000ff,0x4000ff80000-0x4000ff8ffff irq 2035,2032,2033,2036,2019 on nexus0 pcib2: Tomatillo, version 4, IGN 0x1f, bus B, 66MHz pcib2: DVMA map: 0xc0000000 to 0xdfffffff 65536 entries pcib2: PROM IOTSB size: 1 (2048 entries) pcib2: bus range 0 to 0; PCI bus 0 pcib2: [FILTER] pcib2: [FILTER] pcib2: [FILTER] pcib2: [FILTER] pci2: on pcib2 pci2: domain=2, physical bus=0 found-> vendor=0x108e, dev=0xa801, revid=0x00 domain=2, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0146, statreg=0x02a0, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x14e4, dev=0x1647, revid=0x00 domain=2, bus=0, slot=2, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x02b0, cachelnsz=16 (dwords) lattimer=0xf8 (7440 ns), mingnt=0x40 (16000 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 powerspec 2 supports D0 D3 current D0 MSI supports 8 messages, 64 bit map[10]: type Memory, range 64, base 0x200000, size 16, memory disabled nexus0: mem 0x40000000000-0x40000000007 type memory-controller (no driver attached) isab0: at device 7.0 on pci0 pcib0: could not route pin 1 for device 7.0 isa0: could not map ISA interrupt 1 for node 0xf0088520: parallel isa0: on isab0 pci0: at device 6.0 (no driver attached) pci0: at device 8.0 (no driver attached) ohci0: mem 0x1000000-0x1000fff at device 10.0 on pci0 ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0x1000000 ohci0: [MPSAFE] ohci0: [ITHREAD] usbus0: on ohci0 ohci1: mem 0x2000000-0x2000fff at device 11.0 on pci0 ohci1: Reserved 0x1000 bytes for rid 0x10 type 3 at 0x2000000 ohci1: [MPSAFE] ohci1: [ITHREAD] usbus1: on ohci1 atapci0: port 0xa00-0xa07,0xa18-0xa1b,0xa10-0xa17,0xa08-0xa0b,0xa20-0xa2f at device 13.0 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xa20 atapci0: [MPSAFE] atapci0: [ITHREAD] atapci0: using PIO transfers above 137GB as workaround for 48bit DMA access bug, expect reduced performance ata2: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0xa00 atapci0: Reserved 0x4 bytes for rid 0x14 type 4 at 0xa18 ata2: reset tp1 mask=03 ostat0=50 ostat1=00 ata2: stat0=0x90 err=0x90 lsb=0x90 msb=0x90 ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata2: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata2: reset tp2 stat0=50 stat1=00 devices=0x1 ata2: [MPSAFE] ata2: [ITHREAD] ata3: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0xa10 atapci0: Reserved 0x4 bytes for rid 0x1c type 4 at 0xa08 ata3: reset tp1 mask=03 ostat0=00 ostat1=00 ata3: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata3: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata3: reset tp2 stat0=00 stat1=00 devices=0x10000 ata3: [MPSAFE] ata3: [ITHREAD] ohci2: mem 0x3000000-0x3000fff at device 8.0 on pci1 ohci2: Reserved 0x1000 bytes for rid 0x10 type 3 at 0x3000000 pcib1: slot 8 INTA is routed to irq 16 pcib0: installed DMA sync wrapper for device 8.0 on bus 1 ohci2: [MPSAFE] ohci2: [ITHREAD] usbus2: on ohci2 ohci3: mem 0x3002000-0x3002fff at device 8.1 on pci1 ohci3: Reserved 0x1000 bytes for rid 0x10 type 3 at 0x3002000 pcib1: slot 8 INTB is routed to irq 17 pcib0: installed DMA sync wrapper for device 8.1 on bus 1 ohci3: [MPSAFE] ohci3: [ITHREAD] usbus3: on ohci3 ehci0: mem 0x3004000-0x30040ff at device 8.2 on pci1 ehci0: Reserved 0x100 bytes for rid 0x10 type 3 at 0x3004000 pcib1: slot 8 INTC is routed to irq 18 pcib0: installed DMA sync wrapper for device 8.2 on bus 1 ehci0: [MPSAFE] ehci0: [ITHREAD] usbus4: EHCI version 1.0 usbus4: on ehci0 fwohci0: mem 0x3006000-0x30067ff,0x3008000-0x300bfff at device 11.0 on pci1 fwohci0: Reserved 0x800 bytes for rid 0x10 type 3 at 0x3006000 pcib1: slot 11 INTA is routed to irq 19 pcib0: installed DMA sync wrapper for device 11.0 on bus 1 fwohci0: [MPSAFE] fwohci0: [ITHREAD] fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:05:16:00:00:71:20:54 fwohci0: Phy 1394a available S400, 3 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0xc1590000 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:05:16:71:20:54 fwe0: bpf attached fwe0: Ethernet address: 02:05:16:71:20:54 fwip0: on firewire0 fwip0: bpf attached fwip0: Firewire address: 00:05:16:00:00:71:20:54 @ 0xfffe00000000, S400, maxrec 2048 fwohci0: Initiate bus reset fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=0x00000000, SelfID Count=1, CYCLEMASTER mode machfb0: port 0xb00-0xbff mem 0x4000000-0x4ffffff,0x102000-0x102fff at device 5.0 on pci0 machfb0: console machfb0: Reserved 0x1000000 bytes for rid 0x10 type 3 at 0x4000000 machfb0: Reserved 0x1000 bytes for rid 0x18 type 3 at 0x102000 machfb0: 16 MB aperture at 0xfddcc000 not swapped machfb0: 8188 KB SGRAM 114.992 MHz, maximum RAMDAC clock 230 MHz, DSP machfb0: resolution 1152x900 at 8 bpp jbusppm0: mem 0x4000f000000-0x4000f000007,0x4000f410050-0x4000f41005f on nexus0 jbusppm0: master I/O bridge jbusppm0: running at full speed bge0: mem 0x200000-0x20ffff at device 2.0 on pci2 bge0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0x200000 bge0: CHIP ID 0x00001002; ASIC REV 0x01; CHIP REV 0x10; PCI miibus0: on bge0 brgphy0: PHY 1 on miibus0 brgphy0: OUI 0x000818, model 0x0016, rev. 2 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow bge0: bpf attached bge0: Ethernet address: 00:14:4f:23:7e:fe bge0: [MPSAFE] bge0: [ITHREAD] nexus0: mem 0x4000fc64000-0x4000fc6400f type i2c (no driver attached) syscons0: on nexus0 syscons0: Unknown <16 virtual consoles, flags=0x300> syscons0: fb0, kbd0, terminal emulator: scteken (teken terminal) (null) failed to probe at iomem 0xf0000000-0xf00fffff on isa0 rtc0: at port 0x70-0x71 on isa0 rtc0: registered as a time-of-day clock (resolution 1000000us) ct_to_ts([2012-01-15 15:52:10]) = 1326642730.000000000 rtc0: current time: 1326642730.000000000 (null) failed to probe at port 0x320-0x321 irq 46 on isa0 (null) failed to probe at port 0x800-0x82f irq 32 on isa0 uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 44 on isa0 uart0: [FILTER] uart0: fast interrupt uart1: <16550 or compatible> at port 0x2e8-0x2ef irq 44 on isa0 uart1: [FILTER] uart1: fast interrupt (null) failed to probe at port 0-0xffff on isa0 (null) failed to probe at port 0x378-0x37f,0-0x4ff drq 1 on isa0 procfs registered Timecounter "tick" frequency 1503000000 Hz quality 1000 Timecounter "stick" frequency 12000000 Hz quality 1000 Timecounters tick every 1.000 msec vlan: initialized, using hash tables with chaining lo0: bpf attached ata2: Identifying devices: 00000001 ata2: New devices: 00000001 firewire0: 1 nodes, maxhop <= 0 cable IRM irm(0) (me) firewire0: bus manager 0 usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 12Mbps Full Speed USB v1.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 usbus3: 12Mbps Full Speed USB v1.0 usbus4: 480Mbps High Speed USB v2.0 ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=80 wire ugen3.1: at usbus3 uhub3: on usbus3 ugen4.1: at usbus4 uhub4: on usbus4 ad0: setting UDMA100 ad0: 114473MB at ata2-master UDMA100 ad0: 234441648 sectors [232581C/16H/63S] 16 sectors/interrupt 1 depth queue ata3: Identifying devices: 00010000 ata3: New devices: 00010000 GEOM: new disk ad0 ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA66 cable=40 wire acd0: setting UDMA66 acd0: DVDR drive at ata3 as master acd0: read 8269KB/s (8269KB/s) write 8269KB/s (8269KB/s), 2048KB buffer, UDMA66 acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, DVDRAM, packet acd0: Writes: CDR, CDRW, DVDR, DVDRAM, test write, burnproof acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: CD-R 120mm data disc GEOM: ad0: adding VTOC8 information. uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered uhub3: 2 ports with 2 removable, self powered uhub2: 3 ports with 3 removable, self powered ugen1.2: at usbus1 ukbd0: on usbus1 kbd: new array size 4 kbd1 at ukbd0 kbd1: ukbd0, generic (0), config:0x0, flags:0x3d0000 uhid0: on usbus1 ugen1.3: at usbus1 ums0: on usbus1 ums0: 8 buttons and [XYZT] coordinates ID=0 uhub4: 5 ports with 5 removable, self powered acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x05 Trying to mount root from ufs:/dev/ad0a ct_to_ts([2012-01-15 15:52:21]) = 1326642741.000000000 start_init: trying /sbin/init -------------- dmesg when booting 9.0 with hw.physmem set to 1048576000: Copyright (c) 1992-2012 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 9.0-RELEASE #0: Mon Jan 16 01:51:15 CET 2012 root@tarazed.cordula.ws:/usr/obj/usr/src/sys/GENERIC sparc64 real memory = 2147483648 (2048 MB) avail memory = 1018658816 (971 MB) cpu0: Sun Microsystems UltraSparc-IIIi Processor (1503.00 MHz CPU) kbd0 at kbdmux0 nexus0: pcib0: mem 0x4000f600000-0x4000f60afff,0x4000f410000-0x4000f41701f,0x7fe00000000-0x7fe000000ff,0x4000f780000-0x4000f78ffff irq 1970,1968,1969,1972,1953 on nexus0 pcib0: Tomatillo, version 4, IGN 0x1e, bus A, PCI mode, 33MHz pcib0: DVMA map: 0xc0000000 to 0xdfffffff 65536 entries pci0: on pcib0 pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: mem 0x4000ff00000-0x4000ff0afff,0x4000fc10000-0x4000fc1701f,0x7f600000000-0x7f6000000ff,0x4000ff80000-0x4000ff8ffff irq 2035,2032,2033,2036,2019 on nexus0 pcib2: Tomatillo, version 4, IGN 0x1f, bus B, PCI mode, 66MHz pcib2: DVMA map: 0xc0000000 to 0xdfffffff 65536 entries pci2: on pcib2 nexus0: mem 0x40000000000-0x40000000007 type memory-controller (no driver attached) isab0: at device 7.0 on pci0 pcib0: could not route pin 1 for device 7.0 isa0: could not map ISA interrupt 1 for node 0xf0088520: parallel isa0: on isab0 pci0: at device 6.0 (no driver attached) pcm0: port 0x900-0x9ff mem 0x100000-0x100fff at device 8.0 on pci0 pcm0: pcm0: [GIANT-LOCKED] ohci0: mem 0x1000000-0x1000fff at device 10.0 on pci0 usbus0: on ohci0 ohci1: mem 0x2000000-0x2000fff at device 11.0 on pci0 usbus1: on ohci1 atapci0: port 0xa00-0xa07,0xa18-0xa1b,0xa10-0xa17,0xa08-0xa0b,0xa20-0xa2f at device 13.0 on pci0 atapci0: using PIO transfers above 137GB as workaround for 48bit DMA access bug, expect reduced performance ata2: on atapci0 ata3: on atapci0 ohci2: mem 0x3000000-0x3000fff at device 8.0 on pci1 usbus2: on ohci2 ohci3: mem 0x3002000-0x3002fff at device 8.1 on pci1 usbus3: on ohci3 ehci0: mem 0x3004000-0x30040ff at device 8.2 on pci1 usbus4: EHCI version 1.0 usbus4: on ehci0 fwohci0: mem 0x3006000-0x30067ff,0x3008000-0x300bfff at device 11.0 on pci1 fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:05:16:00:00:71:20:54 fwohci0: Phy 1394a available S400, 3 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0xc15b4000 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:05:16:71:20:54 fwe0: Ethernet address: 02:05:16:71:20:54 fwip0: on firewire0 fwip0: Firewire address: 00:05:16:00:00:71:20:54 @ 0xfffe00000000, S400, maxrec 2048 fwohci0: Initiate bus reset fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=0x00000000, SelfID Count=1, CYCLEMASTER mode machfb0: port 0xb00-0xbff mem 0x4000000-0x4ffffff,0x102000-0x102fff at device 5.0 on pci0 machfb0: console machfb0: 16 MB aperture at 0xfddcc000 not swapped machfb0: 8188 KB SGRAM 114.992 MHz, maximum RAMDAC clock 230 MHz, DSP machfb0: resolution 1152x900 at 8 bpp jbusppm0: mem 0x4000f000000-0x4000f000007,0x4000f410050-0x4000f41005f on nexus0 bge0: mem 0x200000-0x20ffff at device 2.0 on pci2 bge0: CHIP ID 0x00001002; ASIC REV 0x01; CHIP REV 0x10; PCI miibus0: on bge0 brgphy0: PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow bge0: Ethernet address: 00:14:4f:23:7e:fe nexus0: mem 0x4000fc64000-0x4000fc6400f type i2c (no driver attached) syscons0: on nexus0 syscons0: Unknown <16 virtual consoles, flags=0x300> rtc0: at port 0x70-0x71 on isa0 uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 44 on isa0 uart1: <16550 or compatible> at port 0x2e8-0x2ef irq 44 on isa0 Timecounter "tick" frequency 1503000000 Hz quality 1000 Timecounter "stick" frequency 12000000 Hz quality 1000 Event timer "tick" frequency 1503000000 Hz quality 1000 Timecounters tick every 1.000 msec firewire0: 1 nodes, maxhop <= 0 cable IRM irm(0) (me) firewire0: bus manager 0 usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 12Mbps Full Speed USB v1.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 usbus3: 12Mbps Full Speed USB v1.0 usbus4: 480Mbps High Speed USB v2.0 ugen3.1: at usbus3 uhub3: on usbus3 ugen4.1: at usbus4 uhub4: on usbus4 ada0 at ata2 bus 0 scbus0 target 0 lun 0 ada0: ATA-6 device ada0: 100.000MB/s transfers (UDMA5, PIO 8192bytes) ada0: 114473MB (234441648 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad0 cd0 at ata3 bus 0 scbus1 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 66.700MB/s transfers (UDMA4, ATAPI 12bytes, PIO 65534bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered GEOM: ada0: adding VTOC8 information. uhub2: 3 ports with 3 removable, self powered uhub3: 2 ports with 2 removable, self powered Root mount waiting for: usbus4 usbus1 ugen1.2: at usbus1 ums0: on usbus1 ums0: 8 buttons and [XYZT] coordinates ID=0 Root mount waiting for: usbus4 usbus1 ugen1.3: at usbus1 uhub5: on usbus1 uhub4: 5 ports with 5 removable, self powered Root mount waiting for: usbus1 uhub5: 4 ports with 3 removable, bus powered Root mount waiting for: usbus1 ugen1.4: at usbus1 ukbd0: on usbus1 kbd1 at ukbd0 Trying to mount root from ufs:/dev/ad0a [rw]... >How-To-Repeat: Install 9.0-RELEASE via source-upgrade from a previous release on a SunBlade 1500 with 2 GB RAM, and reboot. >Fix: No fix for now. Workaround 1: When booting, get the loader prompt and enter set hw.physmem=1048576000 then boot. Workaround 2: Set hw.physmem in /boot/loader.conf: hw.physmem="1048576000" >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-sparc64@FreeBSD.ORG Tue Jan 17 01:10:19 2012 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 8A053106566B for ; Tue, 17 Jan 2012 01:10:19 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 571428FC08 for ; Tue, 17 Jan 2012 01:10:19 +0000 (UTC) Received: by obcwo16 with SMTP id wo16so2347553obc.13 for ; Mon, 16 Jan 2012 17:10:18 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.75.65 with SMTP id a1mr13021885obw.32.1326762618914; Mon, 16 Jan 2012 17:10:18 -0800 (PST) Received: by 10.182.150.69 with HTTP; Mon, 16 Jan 2012 17:10:18 -0800 (PST) X-Originating-IP: [93.221.190.159] In-Reply-To: References: Date: Tue, 17 Jan 2012 02:10:18 +0100 Message-ID: From: "C. P. Ghost" To: freebsd-sparc64 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: Can't boot 9.0-RELEASE 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, 17 Jan 2012 01:10:19 -0000 On Sun, Jan 15, 2012 at 5:23 PM, C. P. Ghost wrote: > On Sun, Jan 15, 2012 at 5:02 PM, C. P. Ghost wrote: >> Hi, >> >> I'm trying to boot 9.0-RELEASE on sparc64, but I'm >> getting stuck at: >> >> panic: kmem_suballoc: bad status return of 3 >> cpuid =3D 0 >> KDB: stack backtrace: >> =A0#0 0xc079841c at ??+0 >> =A0#1 0xc04ca59c at ??+0 >> =A0#2 0xc0487f90 at ??+0 >> =A0#3 0xc0098028 at ??+0 Submitted as sparc64/164227 Thanks, -cpghost. --=20 Cordula's Web. http://www.cordula.ws/ From owner-freebsd-sparc64@FreeBSD.ORG Tue Jan 17 01:12:32 2012 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 6DA671065670; Tue, 17 Jan 2012 01:12:32 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2E0018FC13; Tue, 17 Jan 2012 01:12:32 +0000 (UTC) Received: by obcwo16 with SMTP id wo16so2349663obc.13 for ; Mon, 16 Jan 2012 17:12:31 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.222.102 with SMTP id ql6mr13108468obc.2.1326762751732; Mon, 16 Jan 2012 17:12:31 -0800 (PST) Received: by 10.182.150.69 with HTTP; Mon, 16 Jan 2012 17:12:31 -0800 (PST) X-Originating-IP: [93.221.190.159] In-Reply-To: References: Date: Tue, 17 Jan 2012 02:12:31 +0100 Message-ID: From: "C. P. Ghost" To: freebsd-sparc64 Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable Subject: Re: Reading from CDROM broken on 9.0-RELEASE/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, 17 Jan 2012 01:12:32 -0000 On Mon, Jan 16, 2012 at 2:54 PM, C. P. Ghost wrote: > Hello, > > I think that reading from CDROM is actually broken > in 9.0-RELEASE/sparc64. > > On FreeBSD 8.2-RELEASE/sparc64, mounting a physical > CDROM burned with FreeBSD-9.0-RELEASE-sparc64-disc1.iso > and running sha256 on usr/freebsd-dist/*.txz yields the same > results as listed in usr/freebsd-dist/MANIFEST. > > However, on FreeBSD 9.0-RELEASE/sparc64, mounting the > same CDROM (using /dev/cd0), and running sha256 on the > same usr/freebsd-dist/*.txz files yields completely different results: > > SHA256 (base.txz) = > a96e255a9379ec1a58b756c3e788e34345fd79e35234925df842d700ccb10e1a > SHA256 (doc.txz) = > 54674bb68b111c3465b0beca8893a6b514b80e20dc22f2bbd208b992568261dc > SHA256 (games.txz) = > b9bedddeea549640b4f41a577f4c5f09aa29d0c3d0d4c105bc4fe7d327bf9fcd > SHA256 (kernel.txz) = > 661df36b4a2e87d2aa88ce998b50d48f2a91892fc288452a0282e3c092739046 > SHA256 (ports.txz) = > 315cbfac6f252de5209a3513a846d14650b98e2dcf99c12779ffd1d32acaa287 > SHA256 (src.txz) = > 6b3a4a9536b1ca2618949bb7bb44478266db551ac9f09ccfc92b5469a715f3cf > > This also prevents an installation of 9.0-RELEASE/sparc64 > via bsdinstall from CDROM (bsdinistall says that the data sets > are corrupted). I was only able to get 9.0 on that SunBlade 1500 > by using a regular source upgrade from a running 8.2-RELEASE > system (using usr/freebsd-dist/src.txz from that very same CDROM > that checksummed correctly on 8.2-RELEASE). > > Just to make it clear: the CDROM media is correct and checksums > correctly on 8.2-RELEASE. It doesn't checksum correctly on 9.0-RELEASE > because reading from CDROM media is now (partially) broken. > > Just to make sure the 9.0-RELEASE sha256 program isn't at fault, > I've mounted FreeBSD-9.0-RELEASE-sparc64-disc1.iso via mdconfig > and run sha256 on the *.txz files again: same results as in MANIFEST. > So sha256 on 9.0 itself is okay, it's only the reading from physical > media that corrupts data (and prevents installation from CDROM -- funny > that this passed release engineering and testing...). Submitted as sparc64/164226 Thanks, -cpghost. -- Cordula's Web. http://www.cordula.ws/ From owner-freebsd-sparc64@FreeBSD.ORG Wed Jan 18 10:50:12 2012 Return-Path: Delivered-To: freebsd-sparc64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67DB2106566B for ; Wed, 18 Jan 2012 10:50:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5164E8FC08 for ; Wed, 18 Jan 2012 10:50:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0IAoCD7086272 for ; Wed, 18 Jan 2012 10:50:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0IAoClv086271; Wed, 18 Jan 2012 10:50:12 GMT (envelope-from gnats) Date: Wed, 18 Jan 2012 10:50:12 GMT Message-Id: <201201181050.q0IAoClv086271@freefall.freebsd.org> To: freebsd-sparc64@FreeBSD.org From: Peter Jeremy Cc: Subject: Re: sparc64/164227: Can't boot 9.0-RELEASE/sparc64 on Blade 1500 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Peter Jeremy List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jan 2012 10:50:12 -0000 The following reply was made to PR sparc64/164227; it has been noted by GNATS. From: Peter Jeremy To: "C. P. Ghost" Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: sparc64/164227: Can't boot 9.0-RELEASE/sparc64 on Blade 1500 Date: Wed, 18 Jan 2012 19:43:55 +1100 --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2012-Jan-17 00:47:14 +0000, "C. P. Ghost" wrote: >Booting a FreeBSD-9.0-RELEASE kernel on a Blade 1500 panics with: > >panic: kmem_suballoc: bad status return of 3 >cpuid =3D 0 >KDB: stack backtrace: > #0 0xc079841c at ??+0 > #1 0xc04ca59c at ??+0 > #2 0xc0487f90 at ??+0 > #3 0xc0098028 at ??+0 > >This is on a Blade 1500 with 2 GB of RAM. I can reproduce this on my SB1500 but only with 2GB RAM (4x512MB DIMMs) installed. When I install 1GB RAM (4x256MB) or 4GB RAM (4x1GB), FreeBSD-9.0-RELEASE-sparc64-disc1.iso boots successfully. The problem is still present in 10-current: ok boot freebsd Boot device: /pci@1e,600000/ide@d/disk@1,0 File and args:=20 =20 >> FreeBSD/sparc64 boot block Boot path: /pci@1e,600000/ide@d/disk@1,0:a Boot loader: /boot/loader Consoles: Open Firmware console FreeBSD/sparc64 bootstrap loader, Revision 1.0 (root@sb1500.vk2pj.dyndns.org, Fri Jan 6 14:29:31 EST 2012) bootpath=3D"/pci@1e,600000/ide@d/disk@1,0:a" Loading /boot/defaults/loader.conf /boot/kernel/kernel data=3D0x576f58+0x1fbea8 syms=3D[0x8+0x7db80+0x8+0x7298= 1] Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... jumping to kernel entry at 0xc0070000. KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2012 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 10.0-CURRENT #4 r229481M: Tue Jan 10 15:54:52 EST 2012 root@sb1500.vk2pj.dyndns.org:/usr/obj/usr/src/sys/sb1500 sparc64 WARNING: WITNESS option enabled, expect reduced performance. panic: kmem_suballoc: bad status return of 3 KDB: stack backtrace: (null)() at 0xc02a0330 (null)() at 0xc04526fc (null)() at 0xc028a894 (null)() at 0xc024da70 (null)() at 0xc0070028 KDB: enter: panic [ thread pid 0 tid 0 ] Stopped at 0xc02d5dc0: ta %xcc, 1 db> bt Tracing pid 0 tid 0 td 0xc0587890 (null)() at 0xc02a0374 (null)() at 0xc04526fc (null)() at 0xc028a894 (null)() at 0xc024da70 (null)() at 0xc0070028 db>=20 Since DDB isn't seeing the symbols, I didn't go further but expanded those addresses later via kgdb: 0x00000000c02a0330 : call 0xc02d6340 0x00000000c02a0374 : call 0xc02d5d40 0x00000000c04526fc : call 0xc02a01e0 0x00000000c028a894 : call 0xc0452680 0x00000000c024da70 : call %g1 0x00000000c0070028 : call 0xc024d8a0 Overall, this suggests that Marius is correct in his suspicion that this is related to strangeness in the RAM layout. --=20 Peter Jeremy --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk8WhksACgkQ/opHv/APuIcTGgCfQKe0Djq8IU4V9kb8pneJV26F tfkAoJWeLUjZGaWVXu/KeRZ5ZnHMWFsF =g7Py -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM-- From owner-freebsd-sparc64@FreeBSD.ORG Wed Jan 18 11:07:41 2012 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 3E2F8106566B for ; Wed, 18 Jan 2012 11:07:40 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirg.bris.ac.uk (dirg.bris.ac.uk [137.222.10.102]) by mx1.freebsd.org (Postfix) with ESMTP id E7B538FC16 for ; Wed, 18 Jan 2012 11:07:39 +0000 (UTC) Received: from ncsd.bris.ac.uk ([137.222.10.59] helo=ncs.bris.ac.uk) by dirg.bris.ac.uk with esmtp (Exim 4.72) (envelope-from ) id 1RnTLd-0006J1-5T; Wed, 18 Jan 2012 11:07:31 +0000 Received: from mech-cluster241.men.bris.ac.uk ([137.222.187.241]) by ncs.bris.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1RnTLH-0006t5-Nu; Wed, 18 Jan 2012 11:06:11 +0000 Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.5/8.14.5) with ESMTP id q0IB6Bv8028744; Wed, 18 Jan 2012 11:06:11 GMT (envelope-from mexas@bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.5/8.14.5/Submit) id q0IB6Bdi028743; Wed, 18 Jan 2012 11:06:11 GMT (envelope-from mexas@bris.ac.uk) X-Authentication-Warning: mech-cluster241.men.bris.ac.uk: mexas set sender to mexas@bris.ac.uk using -f Date: Wed, 18 Jan 2012 11:06:11 +0000 From: Anton Shterenlikht To: Peter Jeremy Message-ID: <20120118110611.GA28694@mech-cluster241.men.bris.ac.uk> References: <201201181050.q0IAoClv086271@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201201181050.q0IAoClv086271@freefall.freebsd.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-sparc64@freebsd.org Subject: Re: sparc64/164227: Can't boot 9.0-RELEASE/sparc64 on Blade 1500 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, 18 Jan 2012 11:07:41 -0000 On Wed, Jan 18, 2012 at 10:50:12AM +0000, Peter Jeremy wrote: > The following reply was made to PR sparc64/164227; it has been noted by GNATS. > > From: Peter Jeremy > To: "C. P. Ghost" > Cc: freebsd-gnats-submit@FreeBSD.org > Subject: Re: sparc64/164227: Can't boot 9.0-RELEASE/sparc64 on Blade 1500 > Date: Wed, 18 Jan 2012 19:43:55 +1100 > > --cWoXeonUoKmBZSoM > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On 2012-Jan-17 00:47:14 +0000, "C. P. Ghost" wrote: > >Booting a FreeBSD-9.0-RELEASE kernel on a Blade 1500 panics with: > > > >panic: kmem_suballoc: bad status return of 3 > >cpuid =3D 0 > >KDB: stack backtrace: > > #0 0xc079841c at ??+0 > > #1 0xc04ca59c at ??+0 > > #2 0xc0487f90 at ??+0 > > #3 0xc0098028 at ??+0 > > > >This is on a Blade 1500 with 2 GB of RAM. > > I can reproduce this on my SB1500 but only with 2GB RAM (4x512MB > DIMMs) installed. When I install 1GB RAM (4x256MB) or 4GB RAM > (4x1GB), FreeBSD-9.0-RELEASE-sparc64-disc1.iso boots successfully. > > The problem is still present in 10-current: > ok boot freebsd > Boot device: /pci@1e,600000/ide@d/disk@1,0 File and args:=20 > =20 > >> FreeBSD/sparc64 boot block > Boot path: /pci@1e,600000/ide@d/disk@1,0:a > Boot loader: /boot/loader > Consoles: Open Firmware console > > FreeBSD/sparc64 bootstrap loader, Revision 1.0 > (root@sb1500.vk2pj.dyndns.org, Fri Jan 6 14:29:31 EST 2012) > bootpath=3D"/pci@1e,600000/ide@d/disk@1,0:a" > Loading /boot/defaults/loader.conf > /boot/kernel/kernel data=3D0x576f58+0x1fbea8 syms=3D[0x8+0x7db80+0x8+0x7298= > 1] > > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [/boot/kernel/kernel]... > jumping to kernel entry at 0xc0070000. > KDB: debugger backends: ddb > KDB: current backend: ddb > Copyright (c) 1992-2012 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 10.0-CURRENT #4 r229481M: Tue Jan 10 15:54:52 EST 2012 > root@sb1500.vk2pj.dyndns.org:/usr/obj/usr/src/sys/sb1500 sparc64 > WARNING: WITNESS option enabled, expect reduced performance. > panic: kmem_suballoc: bad status return of 3 > KDB: stack backtrace: > (null)() at 0xc02a0330 > (null)() at 0xc04526fc > (null)() at 0xc028a894 > (null)() at 0xc024da70 > (null)() at 0xc0070028 > KDB: enter: panic > [ thread pid 0 tid 0 ] > Stopped at 0xc02d5dc0: ta %xcc, 1 > db> bt > Tracing pid 0 tid 0 td 0xc0587890 > (null)() at 0xc02a0374 > (null)() at 0xc04526fc > (null)() at 0xc028a894 > (null)() at 0xc024da70 > (null)() at 0xc0070028 > db>=20 > > Since DDB isn't seeing the symbols, I didn't go further but expanded > those addresses later via kgdb: > 0x00000000c02a0330 : call 0xc02d6340 > 0x00000000c02a0374 : call 0xc02d5d40 > 0x00000000c04526fc : call 0xc02a01e0 > 0x00000000c028a894 : call 0xc0452680 > 0x00000000c024da70 : call %g1 > 0x00000000c0070028 : call 0xc024d8a0 > > Overall, this suggests that Marius is correct in his suspicion that > this is related to strangeness in the RAM layout. oh.. this is similar to my panic: http://lists.freebsd.org/pipermail/freebsd-sparc64/2012-January/008164.html but my keyboard freezes, so I can't get a backtrace. This is also on a 2GB box. My other box with 4GB is fine. -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 From owner-freebsd-sparc64@FreeBSD.ORG Wed Jan 18 18:52:35 2012 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 57B1B106566B for ; Wed, 18 Jan 2012 18:52:35 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id ECC498FC1A for ; Wed, 18 Jan 2012 18:52:34 +0000 (UTC) Received: by obcwo16 with SMTP id wo16so5823192obc.13 for ; Wed, 18 Jan 2012 10:52:32 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.0.106 with SMTP id 10mr19983476obd.72.1326912752580; Wed, 18 Jan 2012 10:52:32 -0800 (PST) Received: by 10.182.150.69 with HTTP; Wed, 18 Jan 2012 10:52:32 -0800 (PST) X-Originating-IP: [93.221.178.188] In-Reply-To: <20120118110611.GA28694@mech-cluster241.men.bris.ac.uk> References: <201201181050.q0IAoClv086271@freefall.freebsd.org> <20120118110611.GA28694@mech-cluster241.men.bris.ac.uk> Date: Wed, 18 Jan 2012 19:52:32 +0100 Message-ID: From: "C. P. Ghost" To: Anton Shterenlikht Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-sparc64@freebsd.org Subject: Re: sparc64/164227: Can't boot 9.0-RELEASE/sparc64 on Blade 1500 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, 18 Jan 2012 18:52:35 -0000 On Wed, Jan 18, 2012 at 12:06 PM, Anton Shterenlikht wrote: >> =A0Overall, this suggests that Marius is correct in his suspicion that >> =A0this is related to strangeness in the RAM layout. > > oh.. this is similar to my panic: > > http://lists.freebsd.org/pipermail/freebsd-sparc64/2012-January/008164.ht= ml > > but my keyboard freezes, so I can't get a backtrace. > This is also on a 2GB box. My other box with 4GB is fine. Interesting. I couldn't get a backtrace either (kbd freezes too). Have you tried via serial console? -cpghost. > -- > Anton Shterenlikht > Room 2.6, Queen's Building > Mech Eng Dept > Bristol University > University Walk, Bristol BS8 1TR, UK > Tel: +44 (0)117 331 5944 > Fax: +44 (0)117 929 4423 > _______________________________________________ > freebsd-sparc64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64 > To unsubscribe, send any mail to "freebsd-sparc64-unsubscribe@freebsd.org= " --=20 Cordula's Web. http://www.cordula.ws/ From owner-freebsd-sparc64@FreeBSD.ORG Wed Jan 18 19:23:16 2012 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 B243B1065672 for ; Wed, 18 Jan 2012 19:23:16 +0000 (UTC) (envelope-from peterjeremy@acm.org) Received: from mail30.syd.optusnet.com.au (mail30.syd.optusnet.com.au [211.29.133.193]) by mx1.freebsd.org (Postfix) with ESMTP id 404CA8FC08 for ; Wed, 18 Jan 2012 19:23:15 +0000 (UTC) Received: from server.vk2pj.dyndns.org (c220-239-116-103.belrs4.nsw.optusnet.com.au [220.239.116.103]) by mail30.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id q0IJMkYK009363 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 19 Jan 2012 06:22:47 +1100 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.5/8.14.4) with ESMTP id q0IJMkpN076327; Thu, 19 Jan 2012 06:22:46 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.5/8.14.4/Submit) id q0IJMj5V076326; Thu, 19 Jan 2012 06:22:45 +1100 (EST) (envelope-from peter) Date: Thu, 19 Jan 2012 06:22:44 +1100 From: Peter Jeremy To: Marius Strobl Message-ID: <20120118192244.GA76300@server.vk2pj.dyndns.org> References: <20111216084048.GA98967@mech-cluster241.men.bris.ac.uk> <20111216103720.GA853@alchemy.franken.de> <20111216111922.GA99512@mech-cluster241.men.bris.ac.uk> <20111216161031.GA2371@alchemy.franken.de> <20120106112126.GA69964@mech-cluster241.men.bris.ac.uk> <20120110134600.GA7617@mech-cluster241.men.bris.ac.uk> <20120111194134.GC44286@alchemy.franken.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LQksG6bCIzRHxTLp" Content-Disposition: inline In-Reply-To: <20120111194134.GC44286@alchemy.franken.de> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-sparc64@freebsd.org Subject: Re: r223378 panic [Re: sparc64 r228561 panic: kmem_suballoc: bad status return of 3] 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, 18 Jan 2012 19:23:16 -0000 --LQksG6bCIzRHxTLp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2012-Jan-11 20:41:34 +0100, Marius Strobl wr= ote: >So far I didn't have time to look into this. I suspect the issue >has to do with the holes USIIIi machines tend to have in their >physical memory layout. For a b1k5 with 2GB RAM such a hole might >be large enough to trigger some bug in the VM but not trigger >with 4GB or as in my case with 1GB. I have tried 1GB, 2GB & 4GB in my SB1500 and the problem only shows up with 2GB RAM. I've put details in a followup to sparc64/164227 --=20 Peter Jeremy --LQksG6bCIzRHxTLp Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk8XHAQACgkQ/opHv/APuIcSQgCfQQ0SvRP2uVaByiSS4tSGasa/ nPwAoKFZISlQgQpUZq93yT4UpFhrkisk =b23B -----END PGP SIGNATURE----- --LQksG6bCIzRHxTLp-- From owner-freebsd-sparc64@FreeBSD.ORG Fri Jan 20 18:20:14 2012 Return-Path: Delivered-To: freebsd-sparc64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EBCF9106564A for ; Fri, 20 Jan 2012 18:20:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id CC0078FC0A for ; Fri, 20 Jan 2012 18:20:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0KIKDNH054438 for ; Fri, 20 Jan 2012 18:20:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0KIKDsi054437; Fri, 20 Jan 2012 18:20:13 GMT (envelope-from gnats) Date: Fri, 20 Jan 2012 18:20:13 GMT Message-Id: <201201201820.q0KIKDsi054437@freefall.freebsd.org> To: freebsd-sparc64@FreeBSD.org From: Marius Strobl Cc: Subject: Re: sparc64/164226: Data corruption on 9.0-RELEASE when reading from CDROM X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marius Strobl List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2012 18:20:14 -0000 The following reply was made to PR sparc64/164226; it has been noted by GNATS. From: Marius Strobl To: mav@freebsd.org Cc: freebsd-gnats-submit@freebsd.org, "C. P. Ghost" Subject: Re: sparc64/164226: Data corruption on 9.0-RELEASE when reading from CDROM Date: Fri, 20 Jan 2012 18:51:06 +0100 On Tue, Jan 17, 2012 at 12:31:43AM +0000, C. P. Ghost wrote: > > >Number: 164226 > >Category: sparc64 > >Synopsis: Data corruption on 9.0-RELEASE when reading from CDROM > >Confidential: no > >Severity: serious > >Priority: medium > >Responsible: freebsd-sparc64 > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Tue Jan 17 00:40:07 UTC 2012 > >Closed-Date: > >Last-Modified: > >Originator: C. P. Ghost > >Release: FreeBSD 9.0-RELEASE/sparc64 > >Organization: > Cordula's Web > >Environment: > FreeBSD tarazed.cordula.ws 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Mon Jan 16 01:51:15 CET 2012 root@tarazed.cordula.ws:/usr/obj/usr/src/sys/GENERIC sparc64 > >Description: > It's not possible to install FreeBSD 9.0-RELEASE from CDROM on > a Blade 1500, because bsdinstall reports a corrupt base.txz. > > Investigating the issue further, revealed that the 9.0 kernel > corrupts data read from a CDROM mounted via /dev/cd0, while > the 8.2 kernel doesn't corrupt data when the CDROM is mounted > via /dev/acd0. > > >How-To-Repeat: > 8.2-RELEASE doesn't exhibit the bug: > > 1. Install 8.2-RELEASE on a sun4u system. > 2. Mount the 9.0-RELEASE CDROM (using /dev/acd0) > 3. cd /cdrom/usr/freebsd-dist; sha256 *.txz; > 4. compare with MANIFEST -> same checksums. > > Upgrade to 9.0-RELEASE, e.g. from source: > > 4. mv /usr/src /usr/src.82 > 5. cd /; tar -xvpf /cdrom/usr/freebsd-dist/src.txz > 6. source upgrade from 8.2 to 9.0 > > 9.0-RELEASE exhibits the problem: > > 7. Reboot to 9.0-RELEASE > 8. Mount the 9.0-RELEASE CDROM (using /dev/cd0) > 9. cd /cdrom/usr/freebsd-dist; sha256 *.txz > 10. compare checksums with MANIFEST -> different checksums! > > Reboot 9.0 userland to 8.2 (/boot/kernel.old/kernel) > and repeat sha256 checksums -> no errors. > > Note, the sha256 program on 9.0 yields the same checksums > on arbitrary files than on 8.2, as long as those files are > not read from CDROM (e.g. fetched from the net). It is okay. > >Fix: > No fix known yet. > > Workaround: netboot 9.0, or source-upgrade from a previous > release. Don't use CDROM (/dev/cd0) on 9.0 until this bug > is fixed. > Alexander, could you please look into this? Apparently, using cd(4) with ATA_CAM on sparc64 causes seemingly random data corruption while using the same hardware with acd(4) doesn't. Also cd(4) works just fine with SPI CD-ROMs. This affects CD-ROMs connected to both AcerLabs M5229 and CMD 646. Btw., apparently hw.ata.ata_dma and w.ata.atapi_dma no longer work when using ATA_CAM as ata_getparam() isn't called in the first place. On a quick glance hw.ata.ata_dma_check_80pin and hw.ata.wc probably also are no longer available with ATA_CAM. Is there an alternative to these tunables to achieve the same when using ATA_CAM? Marius From owner-freebsd-sparc64@FreeBSD.ORG Fri Jan 20 18:50:09 2012 Return-Path: Delivered-To: freebsd-sparc64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1EB7E106564A for ; Fri, 20 Jan 2012 18:50:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id EDA448FC0C for ; Fri, 20 Jan 2012 18:50:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0KIo8hC082523 for ; Fri, 20 Jan 2012 18:50:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0KIo80D082522; Fri, 20 Jan 2012 18:50:08 GMT (envelope-from gnats) Date: Fri, 20 Jan 2012 18:50:08 GMT Message-Id: <201201201850.q0KIo80D082522@freefall.freebsd.org> To: freebsd-sparc64@FreeBSD.org From: Alexander Motin Cc: Subject: Re: sparc64/164226: Data corruption on 9.0-RELEASE when reading from CDROM X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alexander Motin List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2012 18:50:09 -0000 The following reply was made to PR sparc64/164226; it has been noted by GNATS. From: Alexander Motin To: Marius Strobl Cc: freebsd-gnats-submit@freebsd.org, "C. P. Ghost" Subject: Re: sparc64/164226: Data corruption on 9.0-RELEASE when reading from CDROM Date: Fri, 20 Jan 2012 20:13:38 +0200 On 20.01.2012 19:51, Marius Strobl wrote: > Alexander, could you please look into this? > Apparently, using cd(4) with ATA_CAM on sparc64 causes seemingly > random data corruption while using the same hardware with acd(4) > doesn't. Also cd(4) works just fine with SPI CD-ROMs. This affects > CD-ROMs connected to both AcerLabs M5229 and CMD 646. > Btw., apparently hw.ata.ata_dma and w.ata.atapi_dma no longer > work when using ATA_CAM as ata_getparam() isn't called in the > first place. On a quick glance hw.ata.ata_dma_check_80pin and > hw.ata.wc probably also are no longer available with ATA_CAM. > Is there an alternative to these tunables to achieve the same > when using ATA_CAM? hw.ata.ata_dma and hw.ata.atapi_dma are indeed no longer exist. But hint.ata.X.mode and hint.ata.X.devX.mode are working. In run tame it can be done via `camcontrol negotiate cd0 -U -M mode; camcontrol rescan X`, where X is a CAM bus number. hw.ata.ata_dma_check_80pin still exist, but CAM ATA transport is no longer look on whet device thinks about cable type. It is tricky in SATA world. Cable type is checked only from controller driver side now. Looks like none of mentioned controller drivers are doing it. hw.ata.wc was replaced by kern.cam.ada.write_cache and kern.cam.ada.X.write_cache. I would start experiments from limiting transfer speed manually. -- Alexander Motin From owner-freebsd-sparc64@FreeBSD.ORG Fri Jan 20 19:40:15 2012 Return-Path: Delivered-To: freebsd-sparc64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 86D16106564A for ; Fri, 20 Jan 2012 19:40:15 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7108F8FC23 for ; Fri, 20 Jan 2012 19:40:15 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0KJeF8F030029 for ; Fri, 20 Jan 2012 19:40:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0KJeFb4030028; Fri, 20 Jan 2012 19:40:15 GMT (envelope-from gnats) Date: Fri, 20 Jan 2012 19:40:15 GMT Message-Id: <201201201940.q0KJeFb4030028@freefall.freebsd.org> To: freebsd-sparc64@FreeBSD.org From: Marius Strobl Cc: Subject: Re: sparc64/164226: Data corruption on 9.0-RELEASE when reading from CDROM X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marius Strobl List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2012 19:40:15 -0000 The following reply was made to PR sparc64/164226; it has been noted by GNATS. From: Marius Strobl To: Alexander Motin Cc: freebsd-gnats-submit@FreeBSD.org, "C. P. Ghost" Subject: Re: sparc64/164226: Data corruption on 9.0-RELEASE when reading from CDROM Date: Fri, 20 Jan 2012 20:32:54 +0100 On Fri, Jan 20, 2012 at 08:13:38PM +0200, Alexander Motin wrote: > On 20.01.2012 19:51, Marius Strobl wrote: > >Alexander, could you please look into this? > >Apparently, using cd(4) with ATA_CAM on sparc64 causes seemingly > >random data corruption while using the same hardware with acd(4) > >doesn't. Also cd(4) works just fine with SPI CD-ROMs. This affects > >CD-ROMs connected to both AcerLabs M5229 and CMD 646. > >Btw., apparently hw.ata.ata_dma and w.ata.atapi_dma no longer > >work when using ATA_CAM as ata_getparam() isn't called in the > >first place. On a quick glance hw.ata.ata_dma_check_80pin and > >hw.ata.wc probably also are no longer available with ATA_CAM. > >Is there an alternative to these tunables to achieve the same > >when using ATA_CAM? > > hw.ata.ata_dma and hw.ata.atapi_dma are indeed no longer exist. But > hint.ata.X.mode and hint.ata.X.devX.mode are working. In run tame it can > be done via `camcontrol negotiate cd0 -U -M mode; camcontrol rescan X`, > where X is a CAM bus number. > > hw.ata.ata_dma_check_80pin still exist, but CAM ATA transport is no > longer look on whet device thinks about cable type. It is tricky in SATA > world. Cable type is checked only from controller driver side now. Looks > like none of mentioned controller drivers are doing it. > > hw.ata.wc was replaced by kern.cam.ada.write_cache and > kern.cam.ada.X.write_cache. > > I would start experiments from limiting transfer speed manually. > Hrm, limitting the mode to PIO avoids the data corruption with ATA_CAM. Marius From owner-freebsd-sparc64@FreeBSD.ORG Fri Jan 20 19:50:13 2012 Return-Path: Delivered-To: freebsd-sparc64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5BFFB106566B for ; Fri, 20 Jan 2012 19:50:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2C3AF8FC18 for ; Fri, 20 Jan 2012 19:50:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0KJoDbv038895 for ; Fri, 20 Jan 2012 19:50:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0KJoD4x038890; Fri, 20 Jan 2012 19:50:13 GMT (envelope-from gnats) Date: Fri, 20 Jan 2012 19:50:13 GMT Message-Id: <201201201950.q0KJoD4x038890@freefall.freebsd.org> To: freebsd-sparc64@FreeBSD.org From: Alexander Motin Cc: Subject: Re: sparc64/164226: Data corruption on 9.0-RELEASE when reading from CDROM X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alexander Motin List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2012 19:50:13 -0000 The following reply was made to PR sparc64/164226; it has been noted by GNATS. From: Alexander Motin To: Marius Strobl Cc: freebsd-gnats-submit@FreeBSD.org, "C. P. Ghost" Subject: Re: sparc64/164226: Data corruption on 9.0-RELEASE when reading from CDROM Date: Fri, 20 Jan 2012 21:40:35 +0200 On 01/20/12 21:32, Marius Strobl wrote: > On Fri, Jan 20, 2012 at 08:13:38PM +0200, Alexander Motin wrote: >> On 20.01.2012 19:51, Marius Strobl wrote: >>> Alexander, could you please look into this? >>> Apparently, using cd(4) with ATA_CAM on sparc64 causes seemingly >>> random data corruption while using the same hardware with acd(4) >>> doesn't. Also cd(4) works just fine with SPI CD-ROMs. This affects >>> CD-ROMs connected to both AcerLabs M5229 and CMD 646. >>> Btw., apparently hw.ata.ata_dma and w.ata.atapi_dma no longer >>> work when using ATA_CAM as ata_getparam() isn't called in the >>> first place. On a quick glance hw.ata.ata_dma_check_80pin and >>> hw.ata.wc probably also are no longer available with ATA_CAM. >>> Is there an alternative to these tunables to achieve the same >>> when using ATA_CAM? >> >> hw.ata.ata_dma and hw.ata.atapi_dma are indeed no longer exist. But >> hint.ata.X.mode and hint.ata.X.devX.mode are working. In run tame it can >> be done via `camcontrol negotiate cd0 -U -M mode; camcontrol rescan X`, >> where X is a CAM bus number. >> >> hw.ata.ata_dma_check_80pin still exist, but CAM ATA transport is no >> longer look on whet device thinks about cable type. It is tricky in SATA >> world. Cable type is checked only from controller driver side now. Looks >> like none of mentioned controller drivers are doing it. >> >> hw.ata.wc was replaced by kern.cam.ada.write_cache and >> kern.cam.ada.X.write_cache. >> >> I would start experiments from limiting transfer speed manually. > > Hrm, limitting the mode to PIO avoids the data corruption with > ATA_CAM. What's about limiting speed to UDMA33? Is it DMA problem or result of dropped device side cable detection that could limit to UDMA33 before? -- Alexander Motin From owner-freebsd-sparc64@FreeBSD.ORG Fri Jan 20 20:00:31 2012 Return-Path: Delivered-To: freebsd-sparc64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 141D3106564A for ; Fri, 20 Jan 2012 20:00:31 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D39BF8FC12 for ; Fri, 20 Jan 2012 20:00:30 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0KK0UuL047157 for ; Fri, 20 Jan 2012 20:00:30 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0KK0Ubd047155; Fri, 20 Jan 2012 20:00:30 GMT (envelope-from gnats) Date: Fri, 20 Jan 2012 20:00:30 GMT Message-Id: <201201202000.q0KK0Ubd047155@freefall.freebsd.org> To: freebsd-sparc64@FreeBSD.org From: Marius Strobl Cc: Subject: Re: sparc64/164226: Data corruption on 9.0-RELEASE when reading from CDROM X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marius Strobl List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2012 20:00:31 -0000 The following reply was made to PR sparc64/164226; it has been noted by GNATS. From: Marius Strobl To: Alexander Motin Cc: freebsd-gnats-submit@FreeBSD.org, "C. P. Ghost" Subject: Re: sparc64/164226: Data corruption on 9.0-RELEASE when reading from CDROM Date: Fri, 20 Jan 2012 20:50:05 +0100 On Fri, Jan 20, 2012 at 09:40:35PM +0200, Alexander Motin wrote: > On 01/20/12 21:32, Marius Strobl wrote: > >On Fri, Jan 20, 2012 at 08:13:38PM +0200, Alexander Motin wrote: > >>On 20.01.2012 19:51, Marius Strobl wrote: > >>>Alexander, could you please look into this? > >>>Apparently, using cd(4) with ATA_CAM on sparc64 causes seemingly > >>>random data corruption while using the same hardware with acd(4) > >>>doesn't. Also cd(4) works just fine with SPI CD-ROMs. This affects > >>>CD-ROMs connected to both AcerLabs M5229 and CMD 646. > >>>Btw., apparently hw.ata.ata_dma and w.ata.atapi_dma no longer > >>>work when using ATA_CAM as ata_getparam() isn't called in the > >>>first place. On a quick glance hw.ata.ata_dma_check_80pin and > >>>hw.ata.wc probably also are no longer available with ATA_CAM. > >>>Is there an alternative to these tunables to achieve the same > >>>when using ATA_CAM? > >> > >>hw.ata.ata_dma and hw.ata.atapi_dma are indeed no longer exist. But > >>hint.ata.X.mode and hint.ata.X.devX.mode are working. In run tame it can > >>be done via `camcontrol negotiate cd0 -U -M mode; camcontrol rescan X`, > >>where X is a CAM bus number. > >> > >>hw.ata.ata_dma_check_80pin still exist, but CAM ATA transport is no > >>longer look on whet device thinks about cable type. It is tricky in SATA > >>world. Cable type is checked only from controller driver side now. Looks > >>like none of mentioned controller drivers are doing it. > >> > >>hw.ata.wc was replaced by kern.cam.ada.write_cache and > >>kern.cam.ada.X.write_cache. > >> > >>I would start experiments from limiting transfer speed manually. > > > >Hrm, limitting the mode to PIO avoids the data corruption with > >ATA_CAM. > > What's about limiting speed to UDMA33? Is it DMA problem or result of > dropped device side cable detection that could limit to UDMA33 before? > Apparently it's some sort of DMA problem. UDMA2 is also the maximum negotiated with acd(4). Limitting to UDMA1, UDMA0 or even WDMA0 makes no differnce to the problem. Marius From owner-freebsd-sparc64@FreeBSD.ORG Sat Jan 21 01:00:25 2012 Return-Path: Delivered-To: freebsd-sparc64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 463E1106564A for ; Sat, 21 Jan 2012 01:00:25 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 137788FC0C for ; Sat, 21 Jan 2012 01:00:25 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0L10Ovm025641 for ; Sat, 21 Jan 2012 01:00:24 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0L10Oqs025636; Sat, 21 Jan 2012 01:00:24 GMT (envelope-from gnats) Date: Sat, 21 Jan 2012 01:00:24 GMT Message-Id: <201201210100.q0L10Oqs025636@freefall.freebsd.org> To: freebsd-sparc64@FreeBSD.org From: Marius Strobl Cc: Subject: Re: sparc64/164226: Data corruption on 9.0-RELEASE when reading from CDROM X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marius Strobl List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jan 2012 01:00:25 -0000 The following reply was made to PR sparc64/164226; it has been noted by GNATS. From: Marius Strobl To: Alexander Motin Cc: freebsd-gnats-submit@FreeBSD.org, "C. P. Ghost" Subject: Re: sparc64/164226: Data corruption on 9.0-RELEASE when reading from CDROM Date: Sat, 21 Jan 2012 01:59:19 +0100 On Fri, Jan 20, 2012 at 08:50:05PM +0100, Marius Strobl wrote: > On Fri, Jan 20, 2012 at 09:40:35PM +0200, Alexander Motin wrote: > > On 01/20/12 21:32, Marius Strobl wrote: > > >On Fri, Jan 20, 2012 at 08:13:38PM +0200, Alexander Motin wrote: > > >>On 20.01.2012 19:51, Marius Strobl wrote: > > >>>Alexander, could you please look into this? > > >>>Apparently, using cd(4) with ATA_CAM on sparc64 causes seemingly > > >>>random data corruption while using the same hardware with acd(4) > > >>>doesn't. Also cd(4) works just fine with SPI CD-ROMs. This affects > > >>>CD-ROMs connected to both AcerLabs M5229 and CMD 646. > > >>>Btw., apparently hw.ata.ata_dma and w.ata.atapi_dma no longer > > >>>work when using ATA_CAM as ata_getparam() isn't called in the > > >>>first place. On a quick glance hw.ata.ata_dma_check_80pin and > > >>>hw.ata.wc probably also are no longer available with ATA_CAM. > > >>>Is there an alternative to these tunables to achieve the same > > >>>when using ATA_CAM? > > >> > > >>hw.ata.ata_dma and hw.ata.atapi_dma are indeed no longer exist. But > > >>hint.ata.X.mode and hint.ata.X.devX.mode are working. In run tame it can > > >>be done via `camcontrol negotiate cd0 -U -M mode; camcontrol rescan X`, > > >>where X is a CAM bus number. > > >> > > >>hw.ata.ata_dma_check_80pin still exist, but CAM ATA transport is no > > >>longer look on whet device thinks about cable type. It is tricky in SATA > > >>world. Cable type is checked only from controller driver side now. Looks > > >>like none of mentioned controller drivers are doing it. > > >> > > >>hw.ata.wc was replaced by kern.cam.ada.write_cache and > > >>kern.cam.ada.X.write_cache. > > >> > > >>I would start experiments from limiting transfer speed manually. > > > > > >Hrm, limitting the mode to PIO avoids the data corruption with > > >ATA_CAM. > > > > What's about limiting speed to UDMA33? Is it DMA problem or result of > > dropped device side cable detection that could limit to UDMA33 before? > > > > Apparently it's some sort of DMA problem. UDMA2 is also the maximum > negotiated with acd(4). Limitting to UDMA1, UDMA0 or even WDMA0 > makes no differnce to the problem. ... for the ALi M5229 rev. 0xc4 that is. The CMD 646 is limited to WDMA2 in the firstplace, a user also reported data corruption with these though. Marius From owner-freebsd-sparc64@FreeBSD.ORG Sat Jan 21 08:55:24 2012 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 DD6A31065675 for ; Sat, 21 Jan 2012 08:55:24 +0000 (UTC) (envelope-from Kashyap.Desai@lsi.com) Received: from na3sys009aog126.obsmtp.com (na3sys009aog126.obsmtp.com [74.125.149.155]) by mx1.freebsd.org (Postfix) with ESMTP id 57DC18FC12 for ; Sat, 21 Jan 2012 08:55:24 +0000 (UTC) Received: from paledge01.lsi.com ([192.19.193.42]) (using TLSv1) by na3sys009aob126.postini.com ([74.125.148.12]) with SMTP ID DSNKTxp9e+rMyZwjYN5USHuIX64U3XtGzf7m@postini.com; Sat, 21 Jan 2012 00:55:24 PST Received: from PALHUB01.lsi.com (128.94.213.114) by PALEDGE01.lsi.com (192.19.193.42) with Microsoft SMTP Server (TLS) id 8.3.213.0; Sat, 21 Jan 2012 03:49:33 -0500 Received: from inbexch02.lsi.com (135.36.98.40) by PALHUB01.lsi.com (128.94.213.114) with Microsoft SMTP Server (TLS) id 8.3.213.0; Sat, 21 Jan 2012 03:44:35 -0500 Received: from inbmail01.lsi.com ([135.36.98.64]) by inbexch02.lsi.com ([135.36.98.40]) with mapi; Sat, 21 Jan 2012 14:14:32 +0530 From: "Desai, Kashyap" To: "freebsd-sparc64@freebsd.org" Date: Sat, 21 Jan 2012 14:14:30 +0530 Thread-Topic: Installation problem for FreeBSD SPARC64 on M3000 Thread-Index: AczYGORlK5MnQEiXQaemiw9BAYDBdA== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Installation problem for FreeBSD SPARC64 on M3000 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: Sat, 21 Jan 2012 08:55:24 -0000 Hi, =20 I am using below machine and seeing some basic installation problem with Fr= eeBSD 8.2 and 9.0 ( I have not tried other releases) Sun SPARC Enterprise M3000 Server, using Domain console Copyright 2008 Sun = Microsystems, Inc. All rights reserved. Copyright 2008 Sun Microsystems, Inc. and Fujitsu Limited. All rights reser= ved. OpenBoot 4.24.10, 4096 MB memory installed, Serial #10031494. Ethernet address 0:b:5d:e2:11:86, Host ID: 80991186. Here is error message.=20 Rebooting with command: boot cdrom Boot device: /pci@0,600000/pci@0/pci@0/scsi@0/disk@4,0:f File and args: >> FreeBSD/sparc64 boot block Boot path: /pci@0,600000/pci@0/pci@0/scsi@0/disk@4,0:f Boot loader: /boot/loader Consoles: Open Firmware console Booting with sun4u support. panic: tlb_init_sun4u: no node for bootcpu?!?! --> Press a key on the console to reboot <-- Is there any work around/solution for this issue ? Thanks, Kashyap