Install to M-Sata in APU system freezing during boot to USB installer.

[chadc01e]

Hello all,

Decided to try and re-flash the release version of 2.2 on an APU1d (tried both the Memstick Serial AMD64, and the NanoBSD Serial 4G AMD64) but I'm running into an oddity that I've yet to see before. The APU will boot and I can see data fine across my serial console, then the APU proceeds to boot the USB installer I've created, (Installing to an internal 16G M-Sata) I see the main prompt to press enter to boot pfsense in multi-user mode and see the kernel begin to load without any listed errors. The APU detects all drives and properly mounts them but at this point the code stops, seeming to be frozen, (normally this is right about where I would see the prompt to press I to begin install.) all I can do is remove or replug ethernet cables and I see the "link down / link up" messages but I have no web access to pfsense and can not enter commands.

The last line displayed before the freeze is this:

"Configuring crasre0:"

Couldn't find any information on google for that line. Any ideas or tips for things to try?

EDIT: With the pfSense-memstick-serial-2.2-RELEASE-amd64.img.gz file I get the final message above. (this is the version I've used for both 2.1.5 and 2.2 snapshot installs without issue.)

When trying pfSense-2.2-RELEASE-4g-amd64-nanobsd.img.gz I get a different message that appears to relate to one of the APU's storage mount points. Further up in the code it references da0 being " <multiple card ="" reader="" 1.00="">Removable Direct Access SCSI-4 device"

"Configuring crasg_vfs_done():da0[READ(offset=0, length=8192)]error = 6"

EDIT2: Ok, 2.1.5 Serial Memstick boots fine, 2.2 Serial Memstick Snapshots also boot fine, 2.2 Release stops with the "Configuring crasg_vfs_done():da0[READ(offset=0, length=8192)]error = 6" line as the final output from the console except Link Up / Down messages.

/boot/kernel/kernel text=0x1213f88 data=0x8819b0+0x357620 syms=[0x8+0x16db38+0x8+0x16accb]
Booting...
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 1992-2014 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.1-RELEASE-p4 #0 36d7dec(releng/10.1)-dirty: Thu Jan 22 15:12:35 CST 2015
    root@pfsense-22-amd64-builder:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_SMP.10 amd64
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
CPU: AMD G-T40E Processor (1000.02-MHz K8-class CPU)
  Origin = "AuthenticAMD"  Id = 0x500f20  Family = 0x14  Model = 0x2  Stepping = 0
  Features=0x178bfbff<fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,<br>MMX,FXSR,SSE,SSE2,HTT>
  Features2=0x802209 <sse3,mon,ssse3,cx16,popcnt>AMD Features=0x2e500800 <syscall,nx,mmx+,ffxsr,page1gb,rdtscp,lm>AMD Features2=0x35ff <lahf,cmp,svm,extapic,cr8,abm,sse4a,mas,prefetch,ibs,skinit,wdt>TSC: P-state invariant, performance statistics
real memory  = 2115297280 (2017 MB)
avail memory = 2007150592 (1914 MB)
Event timer "LAPIC" quality 400
ACPI APIC Table: <core  coreboot="">
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s)
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
random device not loaded; using insecure entropy
ioapic0 <version 2.1=""> irqs 0-23 on motherboard
wlan: mac acl policy registered
ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff80606c30, 0) error 1
ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff80606ce0, 0) error 1
ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff80606d90, 0) error 1
iwi_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (iwi_bss_fw, 0xffffffff8062e400, 0) error 1
iwi_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (iwi_ibss_fw, 0xffffffff8062e4b0, 0) error 1
iwi_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
iwi_monitor: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (iwi_monitor_fw, 0xffffffff8062e560, 0) error 1
random: <software, yarrow=""> initialized
module_register_init: MOD_LOAD (vesa, 0xffffffff80fb8b00, 0) error 19
kbd0 at kbdmux0
cryptosoft0: <software crypto=""> on motherboard
padlock0: No ACE support.
acpi0: <core coreboot=""> on motherboard
acpi0: Power Button (fixed)
cpu0: <acpi cpu=""> on acpi0
cpu1: <acpi cpu=""> on acpi0
atrtc0: <at realtime="" clock=""> port 0x70-0x71 irq 8 on acpi0
Event timer "RTC" frequency 32768 Hz quality 0
attimer0: <at timer=""> port 0x40-0x43 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
hpet0: <high precision="" event="" timer=""> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
Event timer "HPET" frequency 14318180 Hz quality 550
Event timer "HPET1" frequency 14318180 Hz quality 450
pcib0: <acpi host-pci="" bridge=""> port 0xcf8-0xcff on acpi0
pci0: <acpi pci="" bus=""> on pcib0
pcib1: <acpi pci-pci="" bridge=""> irq 16 at device 4.0 on pci0
pci1: <acpi pci="" bus=""> on pcib1
re0: <realtek 8111="" 8168="" b="" c="" cp="" d="" dp="" e="" f="" g="" pcie="" gigabit="" ethernet=""> port 0x1000-0x10ff mem 0xf7900000-0xf
7900fff,0xf7800000-0xf7803fff irq 16 at device 0.0 on pci1
re0: Using 1 MSI-X message
re0: ASPM disabled
re0: Chip rev. 0x2c000000
re0: MAC rev. 0x00200000
miibus0: <mii bus=""> on re0
rgephy0: <rtl8169s 8211="" 8110s="" 1000base-t="" media="" interface=""> PHY 1 on miibus0
rgephy0:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 
1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-fl
ow-master, auto, auto-flow
pcib2: <acpi pci-pci="" bridge=""> irq 17 at device 5.0 on pci0
pci2: <acpi pci="" bus=""> on pcib2
re1: <realtek 8111="" 8168="" b="" c="" cp="" d="" dp="" e="" f="" g="" pcie="" gigabit="" ethernet=""> port 0x2000-0x20ff mem 0xf7b00000-0xf
7b00fff,0xf7a00000-0xf7a03fff irq 17 at device 0.0 on pci2
re1: Using 1 MSI-X message
re1: ASPM disabled
re1: Chip rev. 0x2c000000
re1: MAC rev. 0x00200000
miibus1: <mii bus=""> on re1
rgephy1: <rtl8169s 8211="" 8110s="" 1000base-t="" media="" interface=""> PHY 1 on miibus1
rgephy1:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 
1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-fl
ow-master, auto, auto-flow
pcib3: <acpi pci-pci="" bridge=""> irq 18 at device 6.0 on pci0
pci3: <acpi pci="" bus=""> on pcib3
re2: <realtek 8111="" 8168="" b="" c="" cp="" d="" dp="" e="" f="" g="" pcie="" gigabit="" ethernet=""> port 0x3000-0x30ff mem 0xf7d00000-0xf
7d00fff,0xf7c00000-0xf7c03fff irq 18 at device 0.0 on pci3
re2: Using 1 MSI-X message
re2: ASPM disabled
re2: Chip rev. 0x2c000000
re2: MAC rev. 0x00200000
miibus2: <mii bus=""> on re2
rgephy2: <rtl8169s 8211="" 8110s="" 1000base-t="" media="" interface=""> PHY 1 on miibus2
rgephy2:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 
1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-fl
ow-master, auto, auto-flow
pcib4: <acpi pci-pci="" bridge=""> irq 19 at device 7.0 on pci0
pci4: <acpi pci="" bus=""> on pcib4
ath0: <atheros 9280=""> at device 0.0 on pci4
[ath] enabling AN_TOP2_FIXUP
ath0: [HT] enabling HT modes
ath0: [HT] 1 stream STBC receive enabled
ath0: [HT] 1 stream STBC transmit enabled
ath0: [HT] 2 RX streams; 2 TX streams
ath0: AR9280 mac 128.2 RF5133 phy 13.0
ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0
ahci0: <amd sb7x0="" sb8x0="" sb9x0="" ahci="" sata="" controller=""> port 0x4010-0x4017,0x4020-0x4023,0x4018-0x401f,0x4
024-0x4027,0x4000-0x400f mem 0xf7f08000-0xf7f083ff irq 19 at device 17.0 on pci0
ahci0: AHCI v1.20 with 6 6Gbps ports, Port Multiplier supported
ahcich0: <ahci channel=""> at channel 0 on ahci0
ahcich1: <ahci channel=""> at channel 1 on ahci0
ahcich2: <ahci channel=""> at channel 2 on ahci0
ahcich3: <ahci channel=""> at channel 3 on ahci0
ahcich4: <ahci channel=""> at channel 4 on ahci0
ahcich5: <ahci channel=""> at channel 5 on ahci0
ohci0: <amd sb7x0="" sb8x0="" sb9x0="" usb="" controller=""> mem 0xf7f04000-0xf7f04fff irq 18 at device 18.0 on pci0
usbus0 on ohci0
ehci0: <amd sb7x0="" sb8x0="" sb9x0="" usb="" 2.0="" controller=""> mem 0xf7f08400-0xf7f084ff irq 17 at device 18.2 on p
ci0
usbus1: EHCI version 1.0
usbus1 on ehci0
ohci1: <amd sb7x0="" sb8x0="" sb9x0="" usb="" controller=""> mem 0xf7f05000-0xf7f05fff irq 18 at device 19.0 on pci0
usbus2 on ohci1
ehci1: <amd sb7x0="" sb8x0="" sb9x0="" usb="" 2.0="" controller=""> mem 0xf7f08500-0xf7f085ff irq 17 at device 19.2 on p
ci0
usbus3: EHCI version 1.0
usbus3 on ehci1
isab0: <pci-isa bridge=""> at device 20.3 on pci0
isa0: <isa bus=""> on isab0
pcib5: <acpi pci-pci="" bridge=""> at device 20.4 on pci0
pci5: <acpi pci="" bus=""> on pcib5
ohci2: <amd sb7x0="" sb8x0="" sb9x0="" usb="" controller=""> mem 0xf7f06000-0xf7f06fff irq 18 at device 20.5 on pci0
usbus4 on ohci2
pcib6: <acpi pci-pci="" bridge=""> at device 21.0 on pci0
pci6: <acpi pci="" bus=""> on pcib6
ohci3: <amd sb7x0="" sb8x0="" sb9x0="" usb="" controller=""> mem 0xf7f07000-0xf7f07fff at device 22.0 on pci0
usbus5 on ohci3
ehci2: <amd sb7x0="" sb8x0="" sb9x0="" usb="" 2.0="" controller=""> mem 0xf7f08600-0xf7f086ff at device 22.2 on pci0
usbus6: EHCI version 1.0
usbus6 on ehci2
acpi_button0: <power button=""> on acpi0
orm0: <isa option="" rom=""> at iomem 0xee800-0xeffff on isa0
gpioapu0: Environment returned APU
gpioapu0: Address on reg 0x24 is 0xfed80000/4275568640
gpioapu0 at iomem 0xfed80100-0xfed801ff on isa0
ppc0: cannot reserve I/O port range
uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
uart0: console (115200,n,8,1)
uart1: <16550 or compatible> at port 0x2f8-0x2ff irq 3 on isa0
acpi_throttle0: <acpi cpu="" throttling=""> on cpu0
acpi_throttle1: <acpi cpu="" throttling=""> on cpu1
acpi_throttle1: failed to attach P_CNT
device_attach: acpi_throttle1 attach returned 6
Timecounters tick every 1.000 msec
IPsec: Initialized Security Association Processing.
random: unblocking device.
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 480Mbps High Speed USB v2.0
usbus2: 12Mbps Full Speed USB v1.0
usbus3: 480Mbps High Speed USB v2.0
ugen0.1: <ati> at usbus0
uhub0: <ati 1="" 9="" ohci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr=""> on usbus0
ugen1.1: <ati> at usbus1
uhub1: <ati 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr=""> on usbus1
ugen2.1: <ati> at usbus2
uhub2: <ati 1="" 9="" ohci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr=""> on usbus2
ugen3.1: <ati> at usbus3
uhub3: <ati 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr=""> on usbus3
usbus4: 12Mbps Full Speed USB v1.0
usbus5: 12Mbps Full Speed USB v1.0
usbus6: 480Mbps High Speed USB v2.0
ugen4.1: <ati> at usbus4
uhub4: <ati 1="" 9="" ohci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr=""> on usbus4
ugen5.1: <ati> at usbus5
uhub5: <ati 1="" 9="" ohci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr=""> on usbus5
ugen6.1: <ati> at usbus6
uhub6: <ati 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr=""> on usbus6
uhub4: 2 ports with 2 removable, self powered
uhub0: 5 ports with 5 removable, self powered
uhub2: 5 ports with 5 removable, self powered
uhub5: 4 ports with 4 removable, self powered
uhub6: 4 ports with 4 removable, self powered
uhub1: 5 ports with 5 removable, self powered
uhub3: 5 ports with 5 removable, self powered
ugen6.2: <generic> at usbus6
umass0: <generic 0="" 2="" flash="" card="" readerwriter,="" class="" 0,="" rev="" 2.01="" 1.00,="" addr=""> on usbus6
ugen1.2: <sandisk> at usbus1
umass1: <sandisk 0="" 2="" cruzer="" blade,="" class="" 0,="" rev="" 2.00="" 1.27,="" addr=""> on usbus1
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <sb msata="" ssd="" s9fm01.8=""> ATA-10da1 at umass-sim1 bus 1 scbus7 target 0 lun 0
da1: <sandisk cruzer="" blade="" 1.27=""> Removable Direct Access SCSI-6 device 
da1: Serial Number 4C530799930528118492
da1: 40.000MB/s transfers
da1: 7633MB (15633408 512 byte sectors: 255H 63S/T 973C)
da1: quirks=0x2 <no_6_byte>SATA 3.x device
ada0: Serial Number DA5A074704EE00608117
ada0: 600.000MB/s transfersda0 at umass-sim0 bus 0 scbus6 target 0 lun 0
da0: <multiple card ="" reader="" 1.00=""> Removable Direct Access SCSI-4 device 
da0: Serial Number 058F63666485
da0: 40.000MB/s transfers
da0: Attempt to query device size failed: NOT READY, Medium not present
da0: quirks=0x2 <no_6_byte>(SATA 3.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 14318MB (29323728 512 byte sectors: 16H 63S/T 16383C)
ada0: Previously was known as ad4
SMP: AP CPU #1 Launched!
Timecounter "TSC" frequency 1000019790 Hz quality 800
Trying to mount root from ufs:/dev/ufs/pfSense [ro]...
Configuring crasg_vfs_done():da0[READ(offset=0, length=8192)]error = 6
re0: link state changed to DOWN
re1: link state changed to DOWN
re2: link state changed to DOWN</no_6_byte></multiple></no_6_byte></sandisk></sb></sandisk></sandisk></generic></generic></ati></ati></ati></ati></ati></ati></ati></ati></ati></ati></ati></ati></ati></ati></acpi></acpi></isa></power></amd></amd></acpi></acpi></amd></acpi></acpi></isa></pci-isa></amd></amd></amd></amd></ahci></ahci></ahci></ahci></ahci></ahci></amd></atheros></acpi></acpi></rtl8169s></mii></realtek></acpi></acpi></rtl8169s></mii></realtek></acpi></acpi></rtl8169s></mii></realtek></acpi></acpi></acpi></acpi></high></at></at></acpi></acpi></core></software></software,></version></core ></lahf,cmp,svm,extapic,cr8,abm,sse4a,mas,prefetch,ibs,skinit,wdt></syscall,nx,mmx+,ffxsr,page1gb,rdtscp,lm></sse3,mon,ssse3,cx16,popcnt></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,<br>
```</multiple>

[chadc01e]

UPDATE: Continued troubleshooting has provided very odd results.

I attempted to update the APU's BIOS to the most recent (Beta) build and ran into similar issues with the Tiny Core Linux drive that PC Engines has you prepare. The system would boot into tinycore but then fail to detect its own FAT partition leaving me at a prompt similar to how pfsense gets stuck but not frozen.

Now something interesting, Using the automatic scripting of the bios installer I was able to configure everything so that I could perform the flash blind (no connected serial console, Insane, I know, But someone on the PC Engines forum suggested this method with success.) The drive was programmed to trigger three system beeps, One for Tiny Core Boot Success, One for firmware update start, and one more for Success, Rebooting. Sure enough, No serial console, same exact TinyCore install as before, three lines of code added to autostart.sh, and bam… Beep, Beep, Beep...

So for the moment I know this:

APU + Serial Console + USB Boot Device = Issues.

APU + USB Boot Device = Seems fine. (But its sure hard to tell with no console display output.)

I don't have immediate access to another serial cable, but could the cable itself somehow be causing a lock up of the APU? If so, Is this a common thing? If Not what else could be causing havoc when and only when a serial cable (that has been working fine with this exact model of APU, we have 6 APU1d units.) is connected.

EDIT: Ok, So it would appear that a serial cable CAN cause some serious havoc on this APU. I managed to find a second cable and sure enough the install proceeds fine with all three versions (2.1.5, 2.2rc, 2.2final) I have NO idea how it works with 2.1.5 and not 2.2final but I just tried switching back and forth a few times and each time same results.

Cable 1 = no dice
Cable 2 = Always works

Same exact serial to USB cable, Just one is a few months older than the other... So, Yay! Bad Serial Cable = FUN TIME!

[stephenw10]

No reason the serial cable wouldn't work with 2.2 but works fine with 2.1.5.
The last line you are seeing should read:
Configuring crash dumps…
It being interrupted by something either 're0' or 'g_vfs_done():da0[READ(offset=0, length=8192)]error = 6'.

Since it's not crashed try pressing Ctrl+T to see what process it's waiting for.

You might also try a 32bit image to see if that's a factor.

Steve

[stephenw10]

Wow, bad cable or bad adapter? Were you using 115,200bps for both?

Good catch I would have rules that out.  ;) Odd that 2.2RC worked and 2.2-rel didn't.  :-\

Steve