Date: Wed, 24 Nov 2004 07:50:56 -0700 From: Scott Long <scottl@freebsd.org> To: Michal Konieczny <mk@capri.pl> Cc: freebsd-sparc64@freebsd.org Subject: Re: 5.3 on ultra2: scsi disk not detected Message-ID: <41A49FD0.2080400@freebsd.org> In-Reply-To: <Pine.LNX.4.44.0411241447300.28863-100000@grendel.oldford.pl> References: <Pine.LNX.4.44.0411241447300.28863-100000@grendel.oldford.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
mk@capri.pl wrote:
> First of all, congratulations for bringing FreeBSD to ultra2 ! Great job.
> I encountered few problems during installation. Till now my ultra2 ran
> SunOS 5.8 only, from IBM DRVS09D 9GB disk. I wanted to keep this Solaris
> install, so for FreeBSD install, I put second trial disk: IBM DORS32160
> (2160MB) and started installation. After boot from CDROM selection menu
> appears with several terminal option selections, but they all are
> unusable - this problem is already known on this list. Output
> problems are understandable, but keyboard input is totally unreliable,
> quite strange for locally attached device. So I disconnect the
> keyboard and connect the terminal emulator to ttya.
> Both disks and cdrom are visible - here is probe-scsi output:
>
> Sun Ultra 2 UPA/SBus (2 X UltraSPARC 168MHz), No Keyboard
> OpenBoot 3.25, 512 MB memory installed, Serial #8416406.
> Ethernet address 8:0:20:80:6c:96, Host ID: 80806c96.
>
> {0} ok probe-scsi
> Target 0
> Unit 0 Disk IBM DRVS09D 037013600063QARSPKT037
> 09RI0002400012209L1492
> E32057 Q09L1438B06 E32044 2000
> Target 1
> Unit 0 Disk IBM DORS32160SUN2.1GWA7A96262Q2011
> 0933 000116
> 46H6081 07H1118
> Target 6
> Unit 0 Removable Read Only device TEAC CD-ROM CD-532S 3.0A
>
> Time for booting install CDROM. Unfortunatelly FreeBSD kernel doesn't
> detect disk with Solaris (target 0), only the second disk (scsi target 1),
> as device da0:
>
> Boot device: /sbus/SUNW,fas@e,8800000/sd@6,0:f File and args:
>
>
>>>FreeBSD/sparc64 boot block
>
> Boot path: /sbus@1f,0/SUNW,fas@e,8800000/sd@6,0:f
> Boot loader: /boot/loader
> Console: Open Firmware console
> Boot path set to /sbus@1f,0/SUNW,fas@e,8800000/sd@6,0:a
>
> FreeBSD/sparc64 bootstrap loader, Revision 1.0
> (root@bobbi.cse.buffalo.edu, Fri Nov 5 02:16:10 UTC 2004)
> bootpath="/sbus@1f,0/SUNW,fas@e,8800000/sd@6,0:a"
> Loading /boot/defaults/loader.conf
> /boot/kernel/kernel data=0x3b5f08+0x49e28 syms=[0x8+0x4ef60+0x8+0x43746]
> |
> Hit [Enter] to boot immediately, or any other key for command prompt.
> Booting [/boot/kernel/kernel]...
> nothing to autoload yet.
> jumping to kernel entry at 0xc0040000.
> stray vector interrupt 2033
> 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.3-RELEASE #0: Fri Nov 5 19:30:40 UTC 2004
> root@bobbi.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
> real memory = 536870912 (512 MB)
> avail memory = 506355712 (482 MB)
> cpu0: Sun Microsystems UltraSparc-I Processor (168.00 MHz CPU)
> cpu1: Sun Microsystems UltraSparc-I Processor (168.00 MHz CPU)
> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
> nexus0: <Open Firmware Nexus device>
> sbus0: clock 25.000 MHz
> sbus dvma: DVMA map: 0xfc000000 to 0xffffffff
> sbus0: [FAST]
> sbus0: [FAST]
> initializing counter-timer
> Timecounter "counter-timer" frequency 1000000 Hz quality 100
> sbus0: <U2S UPA-SBus bridge> on nexus0
> sbus0: <SUNW,CS4231>, type (unknown) (no driver attached)
> sbus0: <auxio>, type (unknown) (no driver attached)
> sbus0: <flashprom>, type (unknown) (no driver attached)
> sbus0: <SUNW,fdtwo>, type block (no driver attached)
> eeprom0: <EEPROM/clock> mem 0x1200000-0x1201fff on sbus0
> eeprom0: model mk48t59
> eeprom0: mk48txx_attach: battery low
> eeprom0: Can't attach mk48t59 tod clockdevice_attach: eeprom0 attach
> returned 6
> zs0: <Zilog Z8530> mem 0x1100000-0x1100003 irq 2024 on sbus0
> zs0: [FAST]
> zstty0: <ttya> on zs0
> zstty0: console 9600,8,n,1,-
> zstty1: <ttyb> on zs0
> sbus0: <zs>, type serial (no driver attached)
> sbus0: <sc>, type (unknown) (no driver attached)
> sbus0: <SUNW,pll>, type (unknown) (no driver attached)
> esp0: <Sun FAS366 Fast-Wide SCSI> mem
> 0x8810000-0x881003f,0x8800000-0x880000f irq 2016 on sbus0
> esp0: [GIANT-LOCKED]
> esp0: FAS366/HME, 40MHz, SCSI ID 7
> hme0: <Sun HME 10/100 Ethernet> mem
> 0x8c07000-0x8c0701f,0x8c06000-0x8c07fff,0x8c04000-0x8c05fff,0x8c02000-0x8c03fff,0x8c00000-0x8c00107
> irq 2017 on sbus0
> miibus0: <MII bus> on hme0
> nsphy0: <DP83840 10/100 media interface> on miibus0
> nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> hme0: Ethernet address: 08:00:20:80:6c:96
> hme0: if_start running deferred for Giant
> hme0: [GIANT-LOCKED]
> sbus0: <SUNW,bpp>, type (unknown) (no driver attached)
> sbus0: <cgsix>, type display (no driver attached)
> Timecounters tick every 10.000 msec
> Waiting 15 seconds for SCSI devices to settle
> md0: Preloaded image </boot/mfsroot> 4194304 bytes at 0xc04923e8
> esp0: SCSI bus parity error
> esp0: !TC on DATA XFER [intr 10, stat 86, step 4] prevphase 1, resid 24
> esp0: SCSI bus parity error
> esp0: !TC on DATA XFER [intr 10, stat 86, step 4] prevphase 1, resid 20
> (probe0:esp0:0:0:0): AutoSense Failed
> SMP: AP CPU #1 Launched!
> cd0 at esp0 bus 0 target 6 lun 0
> cd0: <TEAC CD-ROM CD-532S 3.0A> Removable CD-ROM SCSI-2 device
> cd0: 10.000MB/s transfers (10.000MHz, offset 15)
> cd0: cd present [310886 x 2048 byte records]
> da0 at esp0 bus 0 target 1 lun 0
> da0: <IBM DORS32160SUN2.1G WA7A> Fixed Direct Access SCSI-2 device
> da0: 20.000MB/s transfers (10.000MHz, offset 15, 16bit), Tagged Queueing Enabled
> da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C)
> Mounting root from ufs:/dev/md0
>
>
> After settling SCSI devices, SCSI parity errors appear, only second disk
> is detected as da0, first disk gets unnoticed.
> On the hardware side, everything seems to be ok, disks are sca, so no
> problems with scsi cable and termination. Solaris doesn't see any
> problems, detects both disks:
>
>
> Boot device: /sbus/SUNW,fas@e,8800000/sd@0,0 File and args: -v
> Size: 338848+89946+75918 Bytes
> SunOS Release 5.8 Version Generic_108528-11 64-bit
> Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
> Ethernet address = 8:0:20:80:6c:96
> mem = 524288K (0x20000000)
> avail mem = 510091264
> root nexus = Sun Ultra 2 UPA/SBus (2 X UltraSPARC 168MHz)
> sbus0 at root: UPA 0x1f 0x0 ...
> sbus0 is /sbus@1f,0
> /sbus@1f,0/SUNW,fas@e,8800000 (fas0):
> rev 2.2 FEPS chip
> fas0 at sbus0: SBus0 slot 0xe offset 0x8800000 and slot 0xe offset
> 0x8810000 Onboard device sparc9 ipl 4
> fas0 is /sbus@1f,0/SUNW,fas@e,8800000
> sd0 at fas0: target 0 lun 0
> sd0 is /sbus@1f,0/SUNW,fas@e,8800000/sd@0,0
> <IBM-DRVS09D-0370 cyl 6589 alt 2 hd 10 sec 272>
> sd1 at fas0: target 1 lun 0
> sd1 is /sbus@1f,0/SUNW,fas@e,8800000/sd@1,0
> <FreeBSD2064M cyl 2778 alt 2 hd 19 sec 80>
> sd6 at fas0: target 6 lun 0
> sd6 is /sbus@1f,0/SUNW,fas@e,8800000/sd@6,0
> root on /sbus@1f,0/SUNW,fas@e,8800000/sd@0,0:a fstype ufs
> zs0 at sbus0: SBus0 slot 0xf offset 0x1100000 Onboard device sparc9 ipl 12
> zs0 is /sbus@1f,0/zs@f,1100000
> zs1 at sbus0: SBus0 slot 0xf offset 0x1000000 Onboard device sparc9 ipl 12
> zs1 is /sbus@1f,0/zs@f,1000000
> cpu0: SUNW,UltraSPARC (upaid 0 impl 0x10 ver 0x40 clock 168 MHz)
> cpu1: SUNW,UltraSPARC (upaid 1 impl 0x10 ver 0x40 clock 168 MHz)
> SUNW,hme0 : Sbus (Rev Id = 22) Found
> hme0 at sbus0: SBus0 slot 0xe offset 0x8c00000 and slot 0xe offset
> 0x8c02000 and slot 0xe offset 0x8c04000 and slot 0xe offset 0x8c06000 and slot 0xe offset 0x8c07000 Onboard device sparc9 ipl 6
> hme0 is /sbus@1f,0/SUNW,hme@e,8c00000
> configuring IPv4 interfaces: hme0.
> Hostname: ultra2
> dump on /dev/dsk/c0t0d0s1 size 512 MB
> SUNW,hme0 : Internal Transceiver Selected.
> SUNW,hme0 : Auto-Negotiated 100 Mbps Full-Duplex Link Up
> pseudo-device: devinfo0
> devinfo0 is /pseudo/devinfo@0
> The system is coming up. Please wait.
>
>
> Both sd0 and sd1 get detected with no problems.
> So now I took out the second disk, leaving target 0 with Solaris - the
> same results: parity error and no disk detection:
>
> [...]
> Waiting 15 seconds for SCSI devices to settle
> md0: Preloaded image </boot/mfsroot> 4194304 bytes at 0xc04923e8
> esp0: SCSI bus parity error
> esp0: !TC on DATA XFER [intr 10, stat 86, step 4] prevphase 1, resid 24
> esp0: SCSI bus parity error
> esp0: !TC on DATA XFER [intr 10, stat 86, step 4] prevphase 1, resid 20
> (probe0:esp0:0:0:0): AutoSense Failed
> SMP: AP CPU #1 Launched!
> cd0 at esp0 bus 0 target 6 lun 0
> cd0: <TEAC CD-ROM CD-532S 3.0A> Removable CD-ROM SCSI-2 device
> cd0: 10.000MB/s transfers (10.000MHz, offset 15)
> cd0: cd present [310886 x 2048 byte records]
> Mounting root from ufs:/dev/md0
>
>
> Now the second disk as the only disk:
>
>
> [...]
> Waiting 15 seconds for SCSI devices to settle
> md0: Preloaded image </boot/mfsroot> 4194304 bytes at 0xc04923e8
> SMP: AP CPU #1 Launched!
> cd0 at esp0 bus 0 target 6 lun 0
> cd0: <TEAC CD-ROM CD-532S 3.0A> Removable CD-ROM SCSI-2 device
> cd0: 10.000MB/s transfers (10.000MHz, offset 15)
> cd0: cd present [310886 x 2048 byte records]
> da0 at esp0 bus 0 target 1 lun 0
> da0: <IBM DORS32160SUN2.1G WA7A> Fixed Direct Access SCSI-2 device
> da0: 20.000MB/s transfers (10.000MHz, offset 15, 16bit), Tagged Queueing
> Enabled
> da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C)
> Mounting root from ufs:/dev/md0
>
>
> Much better - no parity errors and disk gets detected. But it got detected
> also with the first disk installed. I tried all combinations swapping
> disks between both trays, but results are always the same.
>
> I've seen here few problem reports with no disk detection, the hint was
> to clear starting sectors of the disk to mess the disk label - but I really
> want to keep this Solaris install, is this the "feature" of FreeBSD to
> give up with this disk, or is it real hardware problem ? The latter is
> not so convincing, because Solaris boots with no complaints and sees both
> disks.
>
> Best regards,
>
This is definitely strange. The only thing I can think of is that maybe
the first disk has been forced into narrow mode. Will Solaris tell you
what it thinks the transfer settings are for each disk? Are there any
interesting jumpers on the first disk that might need to be looked at?
Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41A49FD0.2080400>