From owner-freebsd-sparc64@FreeBSD.ORG Tue May 4 12:05:05 2004 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 082E316A4CE for ; Tue, 4 May 2004 12:05:05 -0700 (PDT) Received: from ida.interface-business.de (ida.interface-business.de [193.101.57.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE1E943D46 for ; Tue, 4 May 2004 12:05:03 -0700 (PDT) (envelope-from j@ida.interface-business.de) Received: by ida.interface-business.de (Postfix, from userid 107) id CA00B7A48; Tue, 4 May 2004 21:05:01 +0200 (MET DST) Date: Tue, 4 May 2004 21:05:01 +0200 From: Joerg Wunsch To: freebsd-sparc64@freebsd.org Message-ID: <20040504210501.A45938@ida.interface-business.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Phone: +49-351-31809-14 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Organization: interface systems GmbH, Dresden Subject: -current panics on E450 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joerg Wunsch List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 May 2004 19:05:05 -0000 I just built FreeBSD-current (CVS as of this morning European time) on this E450 here (first step, still with 32-bit time_t), but it no longer boots: real memory = 268435456 (256 MB) avail memory = 247365632 (235 MB) cpu0: Sun Microsystems UltraSparc-II Processor (296.00 MHz CPU) cpu1: Sun Microsystems UltraSparc-II Processor (296.00 MHz CPU) cpu2: Sun Microsystems UltraSparc-II Processor (296.00 MHz CPU) cpu3: Sun Microsystems UltraSparc-II Processor (296.00 MHz CPU) FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs random: nexus0: nexus0: nexus0: , type (unknown) (no driver attached) pcib0: on nexus0 pcib0: Psycho, impl 0, version 4, ign 0x7c0, bus B pcib0: [FAST] pcib0: [FAST] pcib0: [FAST] initialializing counter-timer Timecounter "counter-timer" frequency 1000000 Hz quality 0 DVMA map: 0xfc000000 to 0xffffffff pci0: on pcib0 ebus0: revision 0x01 ebus0: mem 0x71000000-0x717fffff,0x70000000-0x70ffffff at device 1.0 on pci0 ebus0: addr 0x140072f000-0x140072f003,0x140072c000-0x140072c003,0x140072a000-0x140072a003,0x1400728000-0x1400728003,0x1400726000-0x1400726003 (no driver attached) ebus0: addr 0x1400724000-0x1400724003 irq 2034,2021 (no driver attached) ebus0: addr 0x1400504000-0x1400504002 (no driver attached) ebus0: addr 0x1400500000-0x1400500007 (no driver attached) sab0: addr 0x1400400000-0x140040007f irq 43 on ebus0 sab0: [FAST] sabtty0: on sab0 sabtty0: console 9600,8,n,1,- sabtty1: on sab0 ebus0: addr 0x14003083f8-0x14003083ff irq 41 (no driver attached) ebus0: addr 0x14003062f8-0x14003062ff irq 42 (no driver attached) ebus0: addr 0x1400700000-0x140070000f,0x1400300398-0x1400300399,0x14003043bc-0x14003043cb irq 2018 (no driver attached) ebus0: addr 0x1400720000-0x1400720003,0x1400706000-0x140070600f,0x14003023f0-0x14003023f7 irq 2023 (no driver attached) eeprom0: addr 0x1400000000-0x1400001fff on ebus0 eeprom0: model mk48t59 eeprom0: hostid 8087adb0 ebus0: addr 0x1000000000-0x10000fffff,0x1000000000-0x10000fffff (no driver attached) ebus0: addr 0x1400600000-0x1400600003 irq 2021,2024 (no driver attached) hme0: mem 0x8000-0xffff at device 1.1 on pci0 hme0: Ethernet address: 08:00:20:87:ad:b0 miibus0: on hme0 nsphy0: on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sym0: <875> port 0x400-0x4ff mem 0x12000-0x12fff,0x10000-0x100ff at device 3.0 on pci0 sym0: No NVRAM, ID 7, Fast-20, SE, parity checking sym1: <875> port 0x800-0x8ff mem 0x16000-0x16fff,0x14000-0x140ff at device 2.0 on pci0 sym1: No NVRAM, ID 7, Fast-20, SE, parity checking pci0: at device 4.0 (no driver attached) pcib1: on nexus0 pcib1: Psycho, impl 0, version 4, ign 0x7c0, bus A pci1: on pcib1 nexus0: , type memory-controller (no driver attached) pcib2: on nexus0 pcib2: Psycho, impl 0, version 4, ign 0x100, bus B pcib2: [FAST] pcib2: [FAST] pcib2: [FAST] initialializing counter-timer Timecounter "counter-timer" frequency 1000000 Hz quality 0 DVMA map: 0xfc000000 to 0xffffffff pci2: on pcib2 pcib3: on nexus0 pcib3: Psycho, impl 0, version 4, ign 0x100, bus A pci3: on pcib3 pcib4: on nexus0 pcib4: Psycho, impl 0, version 4, ign 0x180, bus B pcib4: [FAST] pcib4: [FAST] pcib4: [FAST] initialializing counter-timer Timecounter "counter-timer" frequency 1000000 Hz quality 0 DVMA map: 0xfc000000 to 0xffffffff pci4: on pcib4 sym2: <875> port 0x400-0x4ff mem 0x4000-0x4fff,0x2000-0x20ff at device 4.0 on pci4 pcib4: guessing interrupt 24 for device 4/0 pin 1 sym2: No NVRAM, ID 7, Fast-20, SE, parity checking sym3: <875> port 0x800-0x8ff mem 0x8000-0x8fff,0x6000-0x60ff at device 4.1 on pci4 pcib4: guessing interrupt 25 for device 4/1 pin 2 sym3: No NVRAM, ID 7, Fast-20, SE, parity checking pcib5: on nexus0 pcib5: Psycho, impl 0, version 4, ign 0x180, bus A pci5: on pcib5 Timecounters tick every 10.000 msec Waiting 15 seconds for SCSI devices to settle GEOM: create disk da0 dp=0xfffff800009eb868 GEOM: create disk da1 dp=0xfffff800009eb468 GEOM: create disk da2 dp=0xfffff800009eb068 GEOM: create disk da3 dp=0xfffff80000977468 GEOM: create disk da4 dp=0xfffff80000977068 GEOM: create disk da5 dp=0xfffff800009ca468 GEOM: create disk da6 dp=0xfffff80000953468 GEOM: create disk da7 dp=0xfffff800009b1c68 sa0 at sym1 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 15) GEOM: create disk cd0 dp=0xfffff80000438e98 da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4094MB (8385121 512 byte sectors: 255H 63S/T 521C) da1 at sym0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4094MB (8385121 512 byte sectors: 255H 63S/T 521C) da2 at sym0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da2: 4094MB (8385121 512 byte sectors: 255H 63S/T 521C) da3 at sym0 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da3: 4094MB (8385121 512 byte sectors: 255H 63S/T 521C) da4 at sym2 bus 0 target 0 lun 0 da4: Fixed Direct Access SCSI-2 device da4: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da4: 4094MB (8385121 512 byte sectors: 255H 63S/T 521C) da5 at sym2 bus 0 target 1 lun 0 da5: Fixed Direct Access SCSI-2 device da5: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da5: 4094MB (8385121 512 byte sectors: 255H 63S/T 521C) da6 at sym2 bus 0 target 2 lun 0 da6: Fixed Direct Access SCSI-2 device da6: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da6: 4094MB (8385121 512 byte sectors: 255H 63S/T 521C) da7 at sym2 bus 0 target 3 lun 0 da7: Fixed Direct Access SCSI-2 device da7: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da7: 4094MB (8385121 512 byte sectors: 255H 63S/T 521C) vinum: loaded cd0 at sym1 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present vinum: reading configuration from /dev/da0h vinum: updating configuration from /dev/da2h vinum: updating configuration from /dev/da3h vinum: updating configuration from /dev/da5h vinum: updating configuration from /dev/da6h vinum: updating configuration from /dev/da1h vinum: updating configuration from /dev/da4h SMP: AP CPU #3 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/vinum/root Enter full pathname of shell or RETURN for /bin/sh: So it appears that device is somehow causing the trouble, doesn't it? Any clues about how to fix that? Is it safe to run the -current (32-bit time_t) world against a 5.2.1 kernel to recover from this situation? Right now, the box is just at the single-user prompt only. -- J"org Wunsch Unix support engineer joerg_wunsch@interface-systems.de http://www.interface-systems.de/~j/