[Soekris] net6501 GPIO
Hi Jeff, I got your email address from my co-worker Alan. I have some net6501 GOIP questions. The GPIO issues are stopping our development right now. Please help me out if you have answers for them. In Soekris-tech Digest, Vol 86, Issue 3 Sat, 02 Apr 2011 09:25:14 -0700 Soren Kristensen wrote: Hi Henrik, Henrik Brix Andersen wrote: Hi Soren, On Apr 2, 2011, at 17:29, Soren Kristensen wrote: The Lattice FPGA is part of CPU control and power manangement. I am confused by the above statement. Is the FPGA available for custom, user-defined functionality or is it pre-programmed with functionality required by the board (CPU control and power management), and thus only providing 16 bit GPIO on the 24 pins header? The Lattice FPGA is only for CPU and Power Management. The Xilinx XC3S50A is user programable. Best Regards, Sorry that I am still confused about the GPIO read/write access. [1] Do I have to modify the FreeBSD devices.hint for the access of XC3S50A from FreeBSD? [2] Is the XC3S50A pre-programmed by Soekris? [3] How can I access the XC3C50A from CPU? It does not show on the comBIOS ver. 1.40a PCI list. [4] If the answer of [2] is no, how can I program the XC3C50A? [5] Is http://www.xilinx.com/support/documentation/data_sheets/ds529.pdf the right data book for XC3C50A? Best Regards, Ted attachment: winmail.dat___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
[Soekris] mSATA failure on 6501 w/ OpenBSD 5.0
Greetings, I've been running a 6501 with OpenBSD 5.0 image on one of the soekris 16 GB mSATA drives. It's been running fine for a few days, but today I was unable to sudo, look at any logs, etc. I'm getting inode exaustion errors, seg faults, etc. df -hi shows plenty of space and inodes. fsck's on the running drives point to problems in all file systems in sector 128-142. I have not had time to reboot the box, as it is still passing traffic. I will reboot late tonight and see if it resolves. However, any-one running this config and seen this? Chris -- 李柯睿 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
[Soekris] Fwd: mSATA failure on 6501 w/ OpenBSD 5.0
Begin forwarded message: From: Christopher LILJENSTOLPE soek...@cdl.asgaard.org 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: ATA, TS16GMSA300, 2010 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 Intel, unknown product 0x8816 (class serial bus unknown subclass 0x80, rev 0x00) at pci2 dev 12 function 1 not
Re: [Soekris] Fwd: mSATA failure on 6501 w/ OpenBSD 5.0
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
Re: [Soekris] Fwd: mSATA failure on 6501 w/ OpenBSD 5.0
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
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] about net6501-70 and amd64 OS
I'm running OpenBSD amd64 on my net6501-50 just fine. On Mon, Nov 28, 2011 at 1:00 PM, Nenhum_de_Nos math...@eternamente.info wrote: hail, I heard about this some time ago, and will just check before ordering it. I plan to run pfSense 2.0 amd64 on it as default, testing OpenBSD and FreeBSD eventually. all runs fine ? thanks, matheus -- Vítima da Oi entre 2007 e 2011. We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
