Problems on a Netra T1 105 using FreeBSD 5.2.1

[RJ45]

This happens to me also on Ultra 60 but once in a month or two
and not very often. Someone told me it is a SMP issue
but Netra T1 105 is not a SMP machine...

Rick


On Mon, 26 Jul 2004, Jörg Reisenweber wrote:

> Hello,
> 
> we are having problems with the installation of 5.2.1 on a Netra T1  
> 105. dmesg output:
> 
> ===========================
> Copyright (c) 1992-2004 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 5.2.1-RELEASE #0: Tue Feb 24 07:47:33 GMT 2004
>      root at bobbi.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
> Preloaded elf kernel "/boot/kernel/kernel" at 0xc0452000.
> Timecounter "tick" frequency 440027828 Hz quality 0
> real memory  = 536870912 (512 MB)
> avail memory = 505610240 (482 MB)
> cpu0: Sun Microsystems UltraSparc-IIi Processor (440.03 MHz CPU)
> nexus0: <OpenFirmware Nexus device>
> pcib0: <U2P UPA-PCI bridge> on nexus0
> pcib0: Sabre, impl 0, version 0, ign 0x7c0, bus A
> pcib0: [FAST]
> pcib0: [FAST]
> DVMA map: 0xc0000000 to 0xc3ffffff
> pci0: <OFW PCI bus> on pcib0
> pcib1: <APB PCI-PCI bridge> at device 1.1 on pci0
> pci1: <OFW PCI bus> on pcib1
> ebus0: revision 0x01
> ebus0: <PCI-EBus2 bridge> mem  
> 0xf1000000-0xf17fffff,0xf0000000-0xf0ffffff at device 1.0 on pci1
> ebus0: <auxio> addr  
> 0x140072f000-0x140072f003,0x140072c000-0x140072c003,0x140072a000 
> -0x140072a003,0x1400728000-0x1400728003,0x1400726000-0x1400726003 (no  
> driver attached)
> ebus0: <power> addr 0x1400724000-0x1400724003 irq 37 (no driver  
> attached)
> ebus0: <SUNW,pll> addr 0x1400504000-0x1400504002 (no driver attached)
> ebus0: <su> addr 0x14003803f8-0x14003803ff irq 28 (no driver attached)
> ebus0: <su> addr 0x14003602f8-0x14003602ff irq 20 (no driver attached)
> ebus0: <ecpp> addr  
> 0x1400700000-0x140070000f,0x140030015c-0x140030015d,0x1400340278 
> -0x1400340287 irq 34 (no driver attached)
> ebus0: <fdthree> addr  
> 0x1400720000-0x1400720003,0x1400706000-0x140070600f,0x14003203f0 
> -0x14003203f7 irq 39 (no driver attached)
> eeprom0: <EBus EEPROM/clock> addr 0x1400000000-0x1400001fff on ebus0
> eeprom0: model mk48t59
> eeprom0: hostid 80c251b0
> ebus0: <flashprom> addr 0x1000000000-0x10000fffff (no driver attached)
> ebus0: <watchdog> addr 0x1400200000-0x140020003f irq 4 (no driver  
> attached)
> ebus0: <display7seg> addr 0x1400200040 (no driver attached)
> ebus0: <beeper> addr 0x1400722000-0x1400722003 (no driver attached)
> ebus0: <flashprom> addr 0x1000400000-0x10005fffff (no driver attached)
> ebus0: <flashprom> addr 0x1000800000-0x10009fffff (no driver attached)
> ebus0: <i2c> addr 0x1400600000-0x1400600003 irq 40 (no driver attached)
> ebus0: <i2c> addr 0x1400100000-0x1400100003 irq 27 (no driver attached)
> ebus0: <SUNW,lom> addr 0x1400400000-0x1400400063 (no driver attached)
> hme0: <Sun HME 10/100 Ethernet> mem 0xe0000000-0xe0007fff at device 1.1  
> on pci1
> hme0: Ethernet address: 08:00:20:c2:51:b0
> miibus0: <MII bus> on hme0
> ukphy0: <Generic IEEE 802.3u media interface> on miibus0
> ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> ukphy1: <Generic IEEE 802.3u media interface> on miibus0
> ukphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> sym0: <875> port 0xc00000-0xc000ff mem  
> 0xe000a000-0xe000afff,0xe0008000-0xe00080ff at device 2.0 on pci1
> sym0: No NVRAM, ID 7, Fast-20, SE, parity checking
> hme1: <Sun HME 10/100 Ethernet> mem 0xe0010000-0xe0017fff at device 3.1  
> on pci1
> hme1: Ethernet address: 08:00:20:c2:51:b0
> miibus1: <MII bus> on hme1
> ukphy2: <Generic IEEE 802.3u media interface> on miibus1
> ukphy2:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> pcib2: <APB PCI-PCI bridge> at device 1.0 on pci0
> pci2: <OFW PCI bus> on pcib2
> pcib3: <OFW PCI-PCI bridge> at device 1.0 on pci2
> pci3: <OFW PCI bus> on pcib3
> atapci0: <CMD 646 WDMA2 controller> port  
> 0x1020-0x102f,0x1018-0x101b,0x1010-0x1017,0x1008-0x100b,0x1000-0x1007  
> at device 14.0 on pci3
> pcib3: slot 14 INTA is routed to irq 2
> atapci0: [MPSAFE]
> ata2: at 0x1000 on atapci0
> ata2: [MPSAFE]
> ata3: at 0x1010 on atapci0
> ata3: [MPSAFE]
> Timecounters tick every 10.000 msec
> Waiting 15 seconds for SCSI devices to settle
> GEOM: create disk da0 dp=0xfffff8002faf5868
> GEOM: create disk da1 dp=0xfffff80000812868
> da0 at sym0 bus 0 target 0 lun 0
> da0: <SEAGATE ST318203LSUN18G 034A> Fixed Direct Access SCSI-2 device
> da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged  
> Queueing Enabled
> da0: 17274MB (35378533 512 byte sectors: 255H 63S/T 2202C)
> da1 at sym0 bus 0 target 1 lun 0
> da1: <IBM IC35L018UCDY10-0 S23C> Fixed Direct Access SCSI-3 device
> da1: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged  
> Queueing Enabled
> da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C)
> Mounting root from ufs:/dev/da0a
> ===========================
> 
> We are currently using this machine for Typo3, a php-based Content  
> Management System.
> 
> Every few days the machine seems to hang. The machine is still pingable  
> but nothing else works. Even the console screen stays black. A hard  
> reset is all that helps...
> 
> We browsed the log files but didn't find anything useful to solve the  
> problem.
> 
> Are there any known such issues with FreeBSD 5.2.1 on a Netra T1 105 or  
> do you have any clues?
> 
> Thank you in advance and best regards,
> Jörg
> _______________________________________
> Ecce Terram GmbH			Jörg Reisenweber
> Edewechter Landstr. 42		Systemintegration
> 26131 Oldenburg				Tel.: 0441-500120
> jr at ecce-terram.de			Fax: 0441-5001229
> _______________________________________________
> freebsd-sparc64 at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64
> To unsubscribe, send any mail to "freebsd-sparc64-unsubscribe at freebsd.org"
>