silicon image 3124 data corruption with siis driver (10.0 RELEASE, GENERIC) (update)
David Cross
dcrosstech at gmail.com
Mon Oct 13 17:44:13 UTC 2014
This pattern is actually replicated exactly between 2 different machines,
both with ECC memory. (That being said, I have done a spot check on the
memory and it came out clean, I don't think I'd need a thorough check given
I can reproduce this problem in seconds, across difference machines)
On Mon, Oct 13, 2014 at 1:31 PM, Rob Sciuk <rob at controlq.com> wrote:
>
> Just a suggestion, but I would run an exhaustive memory test on the SPARC
> machine. As it is aging hw, sha variations can be caused by bad ram, and
> this can be difficult to detect if you aren't looking for it.
>
> Cheers,
> Rob.
>
>
> On Mon, 13 Oct 2014, David Cross wrote:
>
> Date: Mon, 13 Oct 2014 13:11:00 -0400
>> From: David Cross <dcrosstech at gmail.com>
>> To: freebsd-sparc64 at freebsd.org
>> Subject: silicon image 3124 data corruption with siis driver (10.0
>> RELEASE,
>> GENERIC) (update)
>>
>>
>> Ok, I had a chance to do a bit more research.
>>
>> 1) confirmed 10.1-RC2/sparc64 still has the problem (it does)
>> 2) confirmed 10.0/amd64 doesn't have the problem (it doesn't)
>> 3) attempting to verify with linux or openbsd.. (in progress, this is
>> actually pretty tough to do, I had a spare machine that I installed
>> freebsd
>> onto for testing, and tried and failed to install linux about 5 times
>> now..
>> ubuntu 10.04 (last LTS to 'support' this hardware chokes instantly on
>> install (reported problem since 8.04, and debian 7.6 has locked 3 times on
>> install now... freebsd runs 100% on it; trying openbsd 5.5 next)
>>
>> In researching similar problems I found that sometimes these cards need
>> help from their BIOS to init correctly, so I grabbed the PCI config space
>> from the amd64 and sparc64 installs:
>>
>> Ultra10 PCI Config Space:
>> 95 10 24 31 87 00 b0 02 01 00 04 01 10 40 00 00
>> 04 20 00 00 00 00 00 00 04 80 00 00 00 00 00 00
>> 01 04 00 00 00 00 00 00 00 00 00 00 95 10 24 71
>> 00 00 08 00 64 00 00 00 00 00 00 00 10 01 00 00
>> 07 54 52 00 f8 ff c3 12 00 00 00 00 00 00 00 00
>> 00 00 00 00 05 00 80 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 01 40 22 06 00 20 00 19 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>
>> amd64 config space:
>> 95 10 24 31 87 04 b0 02 01 00 04 01 10 00 00 00
>> 04 f0 8f fd 00 00 00 00 04 00 8f fd 00 00 00 00
>> 01 ef 00 00 00 00 00 00 00 00 00 00 95 10 24 71
>> 00 00 00 00 64 00 00 00 00 00 00 00 12 01 00 00
>> 07 54 52 00 f8 ff c3 12 00 00 00 00 00 00 00 00
>> 00 00 00 00 05 00 81 00 00 10 e0 fe 00 00 00 00
>> 36 00 00 00 01 40 22 06 00 20 00 19 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>
>> The only real difference I noticed here is the latency timer on amd64 is
>> set correctly (per the silicon image 3124 programming referece) to 0; on
>> sparc64 its set to 0x40 (the PCI-X value). I updated that with pciconf -w
>> -b siis0 13 0x00 and still had the problem, I looked at other chips on
>> the
>> PCI bus (hme0) and they had it set to 0x50.. which I tried. Neither value
>> resolved the issue (can I update it on the fly like that, or does it need
>> to be in the driver as part of the init routine?
>>
>> Additionally I grabbed an example of the differences between solo and
>> shared output of the card; the pattern is really bizarre and not what I
>> would expect:
>>
>> Given the test methodology of:
>> dd bs=126b if=/dev/ada1 count=4096 of=somefile
>>
>> and then running:
>> dd bs=126b if=/dev/ada1 of=/dev/null
>>
>> in the background I 'hd' the resulting 'somefiles' and diff them; the
>> results are included below:
>>
>> --- ada1.solo.hd 2014-10-02 18:26:18.000000000 +0000
>> +++ ada1.new.hd 2014-10-02 18:15:04.000000000 +0000
>> 0086e010 xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx
>> 0086e020 xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx
>> 0086e030 xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx
>> 0086e040 xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx
>> -0086e050 xx xx xx xx xx xx xx xx xx xx xx xx 3b 5f 79 67
>> +0086e050 xx xx xx xx xx xx xx xx xx xx xx xx 00 00 15 00
>> 0086e060 xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx
>> [for the sake of brevity I will only show the differences]
>> -0108d050 xx xx xx xx xx xx xx xx xx xx xx xx f6 68 c2 9a
>> +0108d050 xx xx xx xx xx xx xx xx xx xx xx xx 0b 71 f6 71
>> -0149c880 xx xx xx xx 3c 9a 34 0f xx xx xx xx xx xx xx xx
>> +0149c880 xx xx xx xx 1f d8 dd 9f xx xx xx xx xx xx xx xx
>> -02bde500 xx xx xx xx 52 71 27 93 xx xx xx xx xx xx xx xx
>> +02bde500 xx xx xx xx 61 50 85 d7 xx xx xx xx xx xx xx xx
>> -02fcdd40 xx xx xx xx xx xx xx xx xx xx xx xx a6 96 34 59
>> +02fcdd40 xx xx xx xx xx xx xx xx xx xx xx xx 2c e4 ec d0
>>
>> Contrary to those examples, I have seen the 'corruption' be not 32bit
>> aligned, I have seen it span the 0x08 boundary as well as the 0x10
>> boundary
>> (though that was under a different testing methodology, that was when I
>> noticed the issue on a live FS that led me down this path). The blocksize
>> of 126b (picked because its close to 64k, and is an even multiple of
>> standard ATA sector sizes) is a hex 0xfc00, so these aren't even all in
>> the
>> same location within a block; which would be a single DMA transfer?
>>
>> The first corruption of '00 00 15 00' seems especially odd since its not
>> obviously 'random'; it looks like a command (like an ATA command?) that
>> somehow got mixed into the datastream.
>>
>> Anyway; does anyone have pointers for where to look next on tracking this
>> down? Frustrating having this so close to working!
>>
>> (oh, as promised a dmesg with verbose boot):
>> 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.1-RC2 #0 r272876: Fri Oct 10 05:25:28 UTC 2014
>> root at releng1.nyi.freebsd.org:/usr/obj/sparc64.sparc64/usr/
>> src/sys/GENERIC
>> sparc64
>> gcc version 4.2.1 20070831 patched [FreeBSD]
>> Preloaded elf kernel "/boot/kernel/kernel" at 0xc0e76000.
>> real memory = 402653184 (384 MB)
>> avail memory = 370155520 (353 MB)
>> machine: SUNW,Ultra-5_10
>> cpu0: Sun Microsystems UltraSparc-IIi Processor (270.00 MHz CPU)
>> mask=0x12 maxtl=5 maxwin=7
>> ULE: setup cpu 0
>> wlan: <802.11 Link Layer>
>> snd_unit_init() u=0x00ff8000 [512] d=0x00007c00 [32] c=0x000003ff [1024]
>> feeder_register: snd_unit=-1 snd_maxautovchans=16 latency=5
>> feeder_rate_min=1 feeder_rate_max=2016000 feeder_rate_round=25
>> firmware: 'isp_1000' version 1: 20142 bytes loaded at 0xc090acc8
>> ispfw: registered firmware <isp_1000>
>> firmware: 'isp_1040' version 1: 22944 bytes loaded at 0xc090fb76
>> ispfw: registered firmware <isp_1040>
>> firmware: 'isp_1040_it' version 1: 32942 bytes loaded at 0xc0915516
>> ispfw: registered firmware <isp_1040_it>
>> firmware: 'isp_1080' version 1: 31350 bytes loaded at 0xc091d5c4
>> ispfw: registered firmware <isp_1080>
>> firmware: 'isp_1080_it' version 1: 40644 bytes loaded at 0xc092503a
>> ispfw: registered firmware <isp_1080_it>
>> firmware: 'isp_12160' version 1: 28050 bytes loaded at 0xc092eefe
>> ispfw: registered firmware <isp_12160>
>> firmware: 'isp_12160_it' version 1: 40604 bytes loaded at 0xc0935c90
>> ispfw: registered firmware <isp_12160_it>
>> firmware: 'isp_2100' version 1: 76770 bytes loaded at 0xc093fb2c
>> ispfw: registered firmware <isp_2100>
>> firmware: 'isp_2200' version 1: 77214 bytes loaded at 0xc095270e
>> ispfw: registered firmware <isp_2200>
>> firmware: 'isp_2300' version 1: 113630 bytes loaded at 0xc09654ac
>> ispfw: registered firmware <isp_2300>
>> firmware: 'isp_2322' version 1: 120466 bytes loaded at 0xc098108a
>> ispfw: registered firmware <isp_2322>
>> firmware: 'isp_2400' version 1: 179908 bytes loaded at 0xc09a2284
>> ispfw: registered firmware <isp_2400>
>> firmware: 'isp_2400_multi' version 1: 198628 bytes loaded at 0xc09db0dc
>> ispfw: registered firmware <isp_2400_multi>
>> firmware: 'isp_2500' version 1: 142704 bytes loaded at 0xc0a193a8
>> ispfw: registered firmware <isp_2500>
>> firmware: 'isp_2500_multi' version 1: 169352 bytes loaded at 0xc0a4b290
>> ispfw: registered firmware <isp_2500_multi>
>> mem: <memory>
>> null: <null device, zero device>
>> nfslock: pseudo-device
>> Falling back to <Software, Yarrow> random adaptor
>> random: <Software, Yarrow> initialized
>> kbd0 at kbdmux0
>> openfirm: <Open Firmware control device>
>> nexus0: <Open Firmware Nexus device>
>> pcib0: <U2P UPA-PCI bridge> mem
>> 0x1fe00000000-0x1fe0000ffff,0x1fe01000000-0x1fe010000ff irq
>> 2032,2030,2031,2021 on nexus0
>> pcib0: Sabre, impl 0, version 0, IGN 0x1f, bus A, 66MHz
>> pcib0: DVMA map: 0xc0000000 to 0xc3ffffff 8192 entries
>> pcib0: PROM IOTSB size: 7 (131072 entries)
>> pcib0: bus range 0 to 2; PCI bus 0
>> initalizing intr_countp
>> pcib0: [GIANT-LOCKED]
>> pci0: <OFW PCI bus> on pcib0
>> pci0: domain=0, physical bus=0
>> found-> vendor=0x108e, dev=0xa000, 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=0x108e, dev=0x5000, revid=0x11
>> domain=0, bus=0, slot=1, func=1
>> class=06-04-00, hdrtype=0x01, mfdev=1
>> cmdreg=0x0147, statreg=0x02a0, cachelnsz=16 (dwords)
>> lattimer=0x40 (1920 ns), mingnt=0x23 (8750 ns), maxlat=0x00 (0 ns)
>> found-> vendor=0x108e, dev=0x5000, revid=0x11
>> domain=0, bus=0, slot=1, func=0
>> class=06-04-00, hdrtype=0x01, mfdev=1
>> cmdreg=0x0147, statreg=0x02a0, cachelnsz=16 (dwords)
>> lattimer=0x40 (1920 ns), mingnt=0x23 (8750 ns), maxlat=0x00 (0 ns)
>> pcib1: <APB PCI-PCI bridge> at device 1.1 on pci0
>> pcib1: domain 0
>> pcib1: secondary bus 1
>> pcib1: subordinate bus 1
>> pcib1: I/O decode 0xc00000-0xdfffff, 0xe00000-0xffffff
>> pcib1: memory decode 0xe0000000-0xffffffff
>> pci1: <OFW PCI bus> on pcib1
>> pci1: domain=0, physical bus=1
>> found-> vendor=0x108e, dev=0x1000, revid=0x01
>> domain=0, bus=1, slot=1, func=0
>> class=06-80-00, hdrtype=0x00, mfdev=1
>> cmdreg=0x0146, statreg=0x0280, cachelnsz=16 (dwords)
>> lattimer=0x50 (2400 ns), mingnt=0x0a (2500 ns), maxlat=0x19 (6250
>> ns)
>> map[10]: type Memory, range 32, base 0xf0000000, size 24, enabled
>> pcib1: device (null) requested decoded memory range 0xf0000000-0xf0ffffff
>> map[14]: type Memory, range 32, base 0xf1000000, size 23, enabled
>> pcib1: device (null) requested decoded memory range 0xf1000000-0xf17fffff
>> found-> vendor=0x108e, dev=0x1001, revid=0x01
>> domain=0, bus=1, slot=1, func=1
>> class=02-00-00, hdrtype=0x00, mfdev=1
>> cmdreg=0x0000, statreg=0x0280, cachelnsz=16 (dwords)
>> lattimer=0x50 (2400 ns), mingnt=0x0a (2500 ns), maxlat=0x05 (1250
>> ns)
>> map[10]: type Memory, range 32, base 0xe0000000, size 15, memory
>> disabled
>> pcib1: device (null) requested decoded memory range 0xe0000000-0xe0007fff
>> found-> vendor=0x1002, dev=0x4754, revid=0x9a
>> domain=0, bus=1, slot=2, func=0
>> class=03-00-00, hdrtype=0x00, mfdev=0
>> cmdreg=0x0080, statreg=0x0280, cachelnsz=16 (dwords)
>> lattimer=0x40 (1920 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns)
>> intpin=a, irq=255
>> map[10]: type Memory, range 32, base 0xe1000000, size 24, memory
>> disabled
>> pcib1: device (null) requested decoded memory range 0xe1000000-0xe1ffffff
>> map[14]: type I/O Port, range 32, base 0, size 8, port disabled
>> pcib1: device (null) requested unsupported I/O range 0x0-0xff
>> pci1: pci0:1:2:0 bar 0x14 failed to allocate
>> map[18]: type Memory, range 32, base 0, size 12, enabled
>> pcib1: device (null) requested unsupported memory range 0x0-0xfff
>> pci1: pci0:1:2:0 bar 0x18 failed to allocate
>> found-> vendor=0x1095, dev=0x0646, revid=0x03
>> domain=0, bus=1, slot=3, func=0
>> class=01-01-8f, hdrtype=0x00, mfdev=0
>> cmdreg=0x0001, statreg=0x0280, cachelnsz=0 (dwords)
>> lattimer=0x10 (480 ns), mingnt=0x02 (500 ns), maxlat=0x04 (1000 ns)
>> intpin=a, irq=255
>> map[10]: type I/O Port, range 32, base 0xc00000, size 3, enabled
>> pcib1: device (null) requested decoded I/O range 0xc00000-0xc00007
>> map[14]: type I/O Port, range 32, base 0xc00008, size 2, enabled
>> pcib1: device (null) requested decoded I/O range 0xc00008-0xc0000b
>> map[18]: type I/O Port, range 32, base 0xc00010, size 3, enabled
>> pcib1: device (null) requested decoded I/O range 0xc00010-0xc00017
>> map[1c]: type I/O Port, range 32, base 0xc00018, size 2, enabled
>> pcib1: device (null) requested decoded I/O range 0xc00018-0xc0001b
>> map[20]: type I/O Port, range 32, base 0xc00020, size 4, enabled
>> pcib1: device (null) requested decoded I/O range 0xc00020-0xc0002f
>> ebus0: <PCI-EBus2 bridge> mem 0xf0000000-0xf0ffffff,0xf1000000-0xf17fffff
>> at device 1.0 on pci1
>> pcib2: <APB PCI-PCI bridge> at device 1.0 on pci0
>> pcib2: domain 0
>> pcib2: secondary bus 2
>> pcib2: subordinate bus 255
>> pcib2: I/O decode 0x0-0x1fffff, 0x200000-0x3fffff,
>> 0x400000-0x5fffff, 0x600000-0x7fffff, 0x800000-0x9fffff, 0xa00000-0xbfffff
>> pcib2: memory decode 0x0-0x1fffffff, 0x20000000-0x3fffffff,
>> 0x40000000-0x5fffffff, 0x60000000-0x7fffffff, 0x80000000-0x9fffffff,
>> 0xa0000000-0xbfffffff
>> pci2: <OFW PCI bus> on pcib2
>> pci2: domain=0, physical bus=2
>> found-> vendor=0x1095, dev=0x3124, revid=0x01
>> domain=0, bus=2, slot=1, func=0
>> class=01-04-00, hdrtype=0x00, mfdev=0
>> cmdreg=0x0080, statreg=0x02b0, cachelnsz=16 (dwords)
>> lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
>> intpin=a, irq=255
>> powerspec 2 supports D0 D1 D2 D3 current D0
>> MSI supports 1 message, 64 bit
>> map[10]: type Memory, range 64, base 0x2000, size 7, memory
>> disabled
>> pcib2: device (null) requested decoded memory range 0x2000-0x207f
>> map[18]: type Memory, range 64, base 0x8000, size 15, enabled
>> pcib2: device (null) requested decoded memory range 0x8000-0xffff
>> map[20]: type I/O Port, range 32, base 0x400, size 4, port
>> disabled
>> pcib2: device (null) requested decoded I/O range 0x400-0x40f
>> auxio0: <Sun Auxiliary I/O> addr
>> 0x1400726000-0x1400726003,0x1400728000-0x1400728003,
>> 0x140072a000-0x140072a003,0x140072c000-0x140072c003,
>> 0x140072f000-0x140072f003
>> on ebus0
>> ebus0: <power> addr 0x1400724000-0x1400724003 irq 37 (no driver attached)
>> ebus0: <SUNW,pll> addr 0x1400504000-0x1400504002 (no driver attached)
>> scc0: <Siemens SAB 82532 dual channel SCC> addr 0x1400400000-0x140040007f
>> irq 43 on ebus0
>> scc0: not resetting hardware
>> uart0: <SAB 82532 v3.2, channel A> on scc0
>> uart0: CTS oflow
>> uart0: console (9600,n,8,1)
>> uart0: fast interrupt
>> uart1: <SAB 82532 v3.2, channel B> on scc0
>> uart1: CTS oflow
>> uart1: fast interrupt
>> scc0: fast interrupt
>> uart2: <16550 or compatible> addr 0x14003083f8-0x14003083ff irq 41 on
>> ebus0
>> uart2: keyboard (1200,n,8,1)
>> uart2: fast interrupt
>> uart2: keyboard not present
>> uart3: <16550 or compatible> addr 0x14003062f8-0x14003062ff irq 42 on
>> ebus0
>> uart3: fast interrupt
>> ebus0: <ecpp> addr
>> 0x14003043bc-0x14003043cb,0x140030015c-0x140030015d,
>> 0x1400700000-0x140070000f
>> irq 34 (no driver attached)
>> ebus0: <fdthree> addr
>> 0x14003023f0-0x14003023f7,0x1400706000-0x140070600f,
>> 0x1400720000-0x1400720003
>> irq 39 (no driver attached)
>> eeprom0: <EEPROM/clock> addr 0x1400000000-0x1400001fff on ebus0
>> eeprom0: model mk48t59
>> eeprom0: mk48txx_attach: battery low
>> eeprom0: cannot attach time of day clock
>> device_attach: eeprom0 attach returned 6
>> ebus0: <flashprom> addr 0x1000000000-0x10000fffff (no driver attached)
>> pcm0: <Sun Audiocs> addr
>> 0x1400200000-0x14002000ff,0x1400702000-0x140070200f,
>> 0x1400704000-0x140070400f,0x1400722000-0x1400722003
>> irq 35,36 on ebus0
>> pcm0: <CS4231A Codec Id. 10>
>> pcm0: Mixer "pcm":
>> pcm0: Mixer "speaker":
>> pcm0: Mixer "line":
>> pcm0: Mixer "mic":
>> pcm0: Mixer "cd":
>> hme0: <Sun HME 10/100 Ethernet> mem 0xe0000000-0xe0007fff at device 1.1 on
>> pci1
>> miibus0: <MII bus> on hme0
>> nsphy0: <DP83840 10/100 media interface> PHY 1 on miibus0
>> nsphy0: OUI 0x1000e8, model 0x0000, rev. 1
>> nsphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
>> hme0: bpf attached
>> hme0: Ethernet address: 08:00:20:79:87:9a
>> machfb0: <ATI 3D Rage I/II> mem 0xe1000000-0xe1ffffff at device 2.0 on
>> pci1
>> machfb0: 8 MB aperture at 0xd09f6000 swapped
>> machfb0: 2048 KB SGRAM 62.999 MHz, maximum RAMDAC clock 170 MHz, DSP
>> machfb0: resolution 1152x900 at 8 bpp
>> atapci0: <SiI (CMD) 646 WDMA2 controller> port
>> 0xc00000-0xc00007,0xc00008-0xc0000b,0xc00010-0xc00017,
>> 0xc00018-0xc0001b,0xc00020-0xc0002f
>> at device 3.0 on pci1
>> ata2: <ATA channel> at channel 0 on atapci0
>> ata3: <ATA channel> at channel 1 on atapci0
>> siis0: <SiI3124 SATA controller> port 0x400-0x40f mem
>> 0x2000-0x207f,0x8000-0xffff at device 1.0 on pci2
>> siisch0: <SIIS channel> at channel 0 on siis0
>> siisch1: <SIIS channel> at channel 1 on siis0
>> siisch2: <SIIS channel> at channel 2 on siis0
>> siisch3: <SIIS channel> at channel 3 on siis0
>> syscons0: <System console> on nexus0
>> syscons0: Unknown <16 virtual consoles, flags=0x100>
>> syscons0: fb0, kbd0, terminal emulator: scteken (teken terminal)
>> procfs registered
>> Timecounter "tick" frequency 270000000 Hz quality 1000
>> Event timer "tick" frequency 270000000 Hz quality 1000
>> Timecounters tick every 1.000 msec
>> siisch0: CONNECT requested
>> siisch0: SIIS reset...
>> siisch0: SATA connect time=100us status=00000123
>> siisch0: SIIS reset done: devices=00000001
>> (noperiph:siisch0:0:-1:ffffffff): rescan already queued
>> vlan: initialized, using hash tables with chaining
>> tcp_init: net.inet.tcp.tcbhashsize auto tuned to 2048
>> lo0: bpf attached
>> ata2: reset tp1 mask=01 ostat0=50 ostat1=ff
>> ata2: stat0=0xd0 err=0x00 lsb=0x6b msb=0x8a
>> ata2: stat0=0xd0 err=0x00 lsb=0x6b msb=0x8a
>> ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
>> ata2: reset tp2 stat0=50 stat1=00 devices=0x1
>> ata3: reset tp1 mask=01 ostat0=00 ostat1=ff
>> ata3: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb
>> ata3: reset tp2 stat0=00 stat1=00 devices=0x10000
>> siisch1: SIIS reset...
>> siisch1: SATA connect timeout time=10000us status=00000000
>> siisch1: SIIS reset done: phy reset found no device
>> siisch2: SIIS reset...
>> siisch2: SATA connect timeout time=10000us status=00000000
>> siisch2: SIIS reset done: phy reset found no device
>> siisch3: SIIS reset...
>> siisch3: SATA connect timeout time=10000us status=00000000
>> siisch3: SIIS reset done: phy reset found no device
>> GEOM: new disk cd0
>> pass0 at ata2 bus 0 scbus0 target 0 lun 0
>> pass0: cd0 at ata3 bus 0 scbus1 target 0 lun 0
>> cd0: <GoldStar CD-ROM CRD-8240B 1.24> Removable CD-ROM SCSI-0 device
>> cd0: Serial Number 1997/12/08
>> cd0: 16.700MB/s transfers (WDMA2, ATAPI 12bytes, PIO 65534bytes)
>> cd0: cd present [88382 x 2048 byte records]
>> <WDC WD2500BEVT-00A23T0 01.01A01> ATA-8 SATA 2.x device
>> pass0: Serial Number WD-WXQ0A99K2533
>> pass0: 16.700MB/s transfers (WDMA2, PIO 8192bytes)
>> pass1 at ata3 bus 0 scbus1 target 0 lun 0
>> pass1: <GoldStar CD-ROM CRD-8240B 1.24> Removable CD-ROM SCSI-0 device
>> pass1: Serial Number 1997/12/08
>> pass1: 16.700MB/s transfers (WDMA2, ATAPI 12bytes, PIO 65534bytes)
>> pass2 at siisch0 bus 0 scbus2 target 0 lun 0
>> pass2: <WDC WD7502ABYS-01A6B0 03.00C05> ATA-8 SATA 2.x device
>> pass2: Serial Number WD-WMAU00028845
>> pass2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
>> pass2: Command Queueing enabled
>> ada0 at ata2 bus 0 scbus0 target 0 lun 0
>> ada0: <WDC WD2500BEVT-00A23T0 01.01A01> ATA-8 SATA 2.x device
>> ada0: Serial Number WD-WXQ0A99K2533
>> ada0: 16.700MB/s transfers (WDMA2, PIO 8192bytes)
>> ada0: 238475MB (488397168 512 byte sectors: 16H 63S/T 16383C)
>> ada0: Previously was known as ad0
>> ada1 at siisch0 bus 0 scbus2 target 0 lun 0
>> ada1: <WDC WD7502ABYS-01A6B0 03.00C05> ATA-8 SATA 2.x device
>> ada1: Serial Number WD-WMAU00028845
>> ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
>> ada1: Command Queueing enabled
>> ada1: 715404MB (1465149168 512 byte sectors: 16H 63S/T 16383C)
>> ada1: Previously was known as ad1
>> random: unblocking device.
>> GEOM: new disk ada0
>> GEOM: new disk ada1
>> GEOM: ada1: the secondary GPT table is corrupt or invalid.
>> GEOM: ada1: using the primary only -- recovery suggested.
>> GEOM: diskid/DISK-WD-WMAU00028845: the secondary GPT table is corrupt or
>> invalid.
>> GEOM: diskid/DISK-WD-WMAU00028845: using the primary only -- recovery
>> suggested.
>> Trying to mount root from ufs:/dev/ada0a [rw]...
>> warning: no time-of-day clock registered, system time will not be set
>> accurately
>> start_init: trying /sbin/init
>> crypto: <crypto core>
>> cryptosoft0: <software crypto> on nexus0
>> crypto: assign cryptosoft0 driver id 0, flags 100663296
>> crypto: cryptosoft0 registers alg 1 flags 0 maxoplen 0
>> crypto: cryptosoft0 registers alg 2 flags 0 maxoplen 0
>> crypto: cryptosoft0 registers alg 3 flags 0 maxoplen 0
>> crypto: cryptosoft0 registers alg 4 flags 0 maxoplen 0
>> crypto: cryptosoft0 registers alg 5 flags 0 maxoplen 0
>> crypto: cryptosoft0 registers alg 16 flags 0 maxoplen 0
>> crypto: cryptosoft0 registers alg 6 flags 0 maxoplen 0
>> crypto: cryptosoft0 registers alg 7 flags 0 maxoplen 0
>> crypto: cryptosoft0 registers alg 18 flags 0 maxoplen 0
>> crypto: cryptosoft0 registers alg 19 flags 0 maxoplen 0
>> crypto: cryptosoft0 registers alg 20 flags 0 maxoplen 0
>> crypto: cryptosoft0 registers alg 8 flags 0 maxoplen 0
>> crypto: cryptosoft0 registers alg 15 flags 0 maxoplen 0
>> crypto: cryptosoft0 registers alg 9 flags 0 maxoplen 0
>> crypto: cryptosoft0 registers alg 10 flags 0 maxoplen 0
>> crypto: cryptosoft0 registers alg 13 flags 0 maxoplen 0
>> crypto: cryptosoft0 registers alg 14 flags 0 maxoplen 0
>> crypto: cryptosoft0 registers alg 11 flags 0 maxoplen 0
>> crypto: cryptosoft0 registers alg 22 flags 0 maxoplen 0
>> crypto: cryptosoft0 registers alg 21 flags 0 maxoplen 0
>> crypto: cryptosoft0 registers alg 17 flags 0 maxoplen 0
>> GEOM_ELI: Device ada0b.eli created.
>> GEOM_ELI: Encryption: AES-XTS 128
>> GEOM_ELI: Crypto: software
>> _______________________________________________
>> 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
>> "
>>
>>
> --
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> -=-=-=-=-=--=-=-=-=
> Robert S. Sciuk http://www.controlq.com 259 Simcoe St. S.
> Control-Q Research tel: 905.706.1354 Oshawa, Ont.
> rob at ControlQ.com Canada, L1H 4H3
>
More information about the freebsd-sparc64
mailing list