Re: [Soekris] Fwd: mSATA failure on 6501 w/ OpenBSD 5.0

2011-11-28 Thread Chris Cappuccio
Christopher LILJENSTOLPE [soek...@cdl.asgaard.org] wrote:
> Greetings,
> 
>   Any thoughts as to how to get around this - it's only been up for a few 
> days.  Rebooting my home router every 24 hours is not spouse endearing 
> behavior :)
> 

port over some workarounds from dragonfly, or just figure out what is causing 
enough disk access to trigger this behavior and use a different machine for it

-- 
There are only three sports: bullfighting, motor racing, and mountaineering; 
all the rest are merely games. - E. Hemingway
___
Soekris-tech mailing list
Soekris-tech@lists.soekris.com
http://lists.soekris.com/mailman/listinfo/soekris-tech


Re: [Soekris] Fwd: mSATA failure on 6501 w/ OpenBSD 5.0

2011-11-28 Thread Christopher LILJENSTOLPE
Greetings,

Any thoughts as to how to get around this - it's only been up for a few 
days.  Rebooting my home router every 24 hours is not spouse endearing behavior 
:)

Chris

On 28Nov2011, at 14.30, Chris Cappuccio wrote:

> here is the key error message. it means your whole ahci disk has disappeared 
> (and anything you can still run is happening from cache.)
> 
> --
> ahci0: stopping the port, softreset slot 31 was still active.
> ahci0: failed to reset port during timeout handling, disabling it
> --
> 
> likely a reboot will fix it. this is a known problem with ahci driver and 
> intel ahci controllers.
> 
> the "failed to reset port" and "softreset slot was still active" problems 
> become really obvious once you start maxing out disks on an ahci controller 
> with a softraid array. they rarely present problems in normal use! but, the 
> SSD sata drive may evoke different behavior for some reason. i think 
> continuous runs of iogen over a RAID1 array might bring out similar issues 
> all by itself, even with regular hard disks 
> 
> dragonflybsd's port of openbsd's ahci driver has incorporated several of 
> workarounds for problems directly related to this. (reset this when that 
> happens, etc..) that might be a good place to start looking, if you can 
> easily reproduce the problem then you would know quickly when a ported fix 
> from their driver has helped.

--  
李柯睿
Check my PGP key here: https://www.asgaard.org/~cdl/cdl.asc
Current vCard here: https://www.asgaard.org/~cdl/cdl.vcf

___
Soekris-tech mailing list
Soekris-tech@lists.soekris.com
http://lists.soekris.com/mailman/listinfo/soekris-tech


Re: [Soekris] Fwd: mSATA failure on 6501 w/ OpenBSD 5.0

2011-11-28 Thread Chris Cappuccio
here is the key error message. it means your whole ahci disk has disappeared 
(and anything you can still run is happening from cache.)

--
ahci0: stopping the port, softreset slot 31 was still active.
ahci0: failed to reset port during timeout handling, disabling it
--

likely a reboot will fix it. this is a known problem with ahci driver and intel 
ahci controllers.

the "failed to reset port" and "softreset slot was still active" problems 
become really obvious once you start maxing out disks on an ahci controller 
with a softraid array. they rarely present problems in normal use! but, the SSD 
sata drive may evoke different behavior for some reason. i think continuous 
runs of iogen over a RAID1 array might bring out similar issues all by itself, 
even with regular hard disks 

dragonflybsd's port of openbsd's ahci driver has incorporated several of 
workarounds for problems directly related to this. (reset this when that 
happens, etc..) that might be a good place to start looking, if you can easily 
reproduce the problem then you would know quickly when a ported fix from their 
driver has helped.
___
Soekris-tech mailing list
Soekris-tech@lists.soekris.com
http://lists.soekris.com/mailman/listinfo/soekris-tech


[Soekris] Fwd: mSATA failure on 6501 w/ OpenBSD 5.0

2011-11-28 Thread Christopher LILJENSTOLPE


Begin forwarded message:

> From: Christopher LILJENSTOLPE 
> Subject: Re: [Soekris] mSATA failure on 6501 w/ OpenBSD 5.0
> Date: 28 November 2011 14.08.40 -0800
> To: w...@kd85.com
> 
> Greetings,
> 
> Transcend 
> 
> dmesg to follow:
> 
> % dmesg
> OpenBSD 5.0 (GENERIC) #43: Wed Aug 17 10:10:52 MDT 2011
>dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: Genuine Intel(R) CPU @ 1.60GHz ("GenuineIntel" 686-class) 1.61 GHz
> cpu0: 
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE
> real mem  = 2147016704 (2047MB)
> avail mem = 2101841920 (2004MB)
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 20/10/06, BIOS32 rev. 0 @ 0xfac40
> bios0: MP Configuration Table checksum mismatch
> pcibios0 at bios0: rev 2.0 @ 0xf/0x1
> pcibios0: pcibios_get_intr_routing - function not supported
> pcibios0: PCI IRQ Routing information unavailable.
> pcibios0: PCI bus #13 is the last bus
> bios0: ROM list: 0xc8000/0xee00 0xd7000/0x2400
> cpu0 at mainbus0: (uniprocessor)
> cpu0: unknown i686 model 0x26, can't get bus clock (0x4188)
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> pchb0 at pci0 dev 0 function 0 vendor "Intel", unknown product 0x4114 rev 0x05
> pchb1 at pci0 dev 1 function 0 vendor "Intel", unknown product 0x8183 rev 0x00
> ppb0 at pci0 dev 23 function 0 vendor "Intel", unknown product 0x8184 rev 0x00
> pci1 at ppb0 bus 1
> ppb1 at pci1 dev 0 function 0 vendor "Intel", unknown product 0x8800 rev 0x01
> pci2 at ppb1 bus 2
> io address conflict 0x5800/0x20
> mem address conflict 0x8000/0x200
> mem address conflict 0x8200/0x200
> mem address conflict 0x8400/0x200
> mem address conflict 0x8600/0x100
> io address conflict 0x5820/0x8
> mem address conflict 0x8700/0x10
> io address conflict 0x5828/0x8
> mem address conflict 0x8710/0x10
> mem address conflict 0x8800/0x100
> mem address conflict 0x8720/0x20
> mem address conflict 0x8900/0x100
> vendor "Intel", unknown product 0x8801 (class undefined unknown subclass 
> 0x00, rev 0x01) at pci2 dev 0 function 0 not configured
> vendor "Intel", unknown product 0x8802 (class network subclass ethernet, rev 
> 0x01) at pci2 dev 0 function 1 not configured
> vendor "Intel", unknown product 0x8803 (class undefined unknown subclass 
> 0x00, rev 0x00) at pci2 dev 0 function 2 not configured
> ohci0 at pci2 dev 2 function 0 vendor "Intel", unknown product 0x8804 rev 
> 0x01: irq 9, version 1.0, legacy support
> ohci1 at pci2 dev 2 function 1 vendor "Intel", unknown product 0x8805 rev 
> 0x01: irq 9, version 1.0, legacy support
> ohci2 at pci2 dev 2 function 2 vendor "Intel", unknown product 0x8806 rev 
> 0x01: irq 9, version 1.0, legacy support
> ehci0 at pci2 dev 2 function 3 vendor "Intel", unknown product 0x8807 rev 
> 0x01: irq 9
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
> vendor "Intel", unknown product 0x8808 (class serial bus subclass USB, rev 
> 0x01) at pci2 dev 2 function 4 not configured
> sdhc0 at pci2 dev 4 function 0 vendor "Intel", unknown product 0x8809 rev 
> 0x01: can't map interrupt
> sdhc1 at pci2 dev 4 function 1 vendor "Intel", unknown product 0x880a rev 
> 0x01: can't map interrupt
> ahci0 at pci2 dev 6 function 0 vendor "Intel", unknown product 0x880b rev 
> 0x01: irq 11, AHCI 1.1
> scsibus0 at ahci0: 32 targets
> sd0 at scsibus0 targ 0 lun 0:  SCSI3 0/direct fixed 
> t10.ATA_TS16GMSA300_201109190083_
> sd0: 15104MB, 512 bytes/sector, 30932992 sectors, thin
> ohci3 at pci2 dev 8 function 0 vendor "Intel", unknown product 0x880c rev 
> 0x01: irq 10, version 1.0, legacy support
> ohci4 at pci2 dev 8 function 1 vendor "Intel", unknown product 0x880d rev 
> 0x01: irq 10, version 1.0, legacy support
> ohci5 at pci2 dev 8 function 2 vendor "Intel", unknown product 0x880e rev 
> 0x01: irq 10, version 1.0, legacy support
> ehci1 at pci2 dev 8 function 3 vendor "Intel", unknown product 0x880f rev 
> 0x01: irq 10
> usb1 at ehci1: USB revision 2.0
> uhub1 at usb1 "Intel EHCI root hub" rev 2.00/1.00 addr 1
> vendor "Intel", unknown product 0x8810 (class undefined unknown subclass 
> 0x00, rev 0x00) at pci2 dev 10 function 0 not configured
> vendor "Intel", unknown product 0x8811 (class communications subclass serial, 
> rev 0x00) at pci2 dev 10 function 1 not configured
> vendor "Intel", unknown product 0x8812 (class communications subclass serial, 
> rev 0x00) at pci2 dev 10 function 2 not configured
> vendor "Intel", unknown product 0x8813 (class communications subclass serial, 
> rev 0x00) at pci2 dev 10 function 3 not configured
> vendor "Intel", unknown product 0x8814 (class communications subclass serial, 
> rev 0x00) at pci2 dev 10 function 4 not configured
> vendor "Intel", unknown product 0x8815 (class undefined unknown subclass 
> 0x00, rev 0x00) at pci2 dev 12 function 0 not configured
> vendor "Inte