Banana pi pro SATA

[Franco Ricci]

Hi Jindra,
you are right, the problem is related to disk attached while I reading form SD.
If I boot from SATA disk and I never read nothing form SD all seems to work fine.

Franco


On 26 Feb, 2016, at 5:53 PM, Jindrich Fucik <fulda at seznam.cz> wrote:

> Franco Ricci franco.ricci at uniroma1.it
> Sat Feb 20 09:59:19 UTC 2016
> 
> > After several days I found that problem was HD type.
> > With a rotational HD all works fine.
> > I don't know why.
> 
> Hello Franco,
> 
> I fave found, that it does not matter you are using disk or not.
> Only the fact the disk is attached mean, that you will have troubles with reading more files from SD card.
> I did small experiment - download last image (same epeerience with previous one), boot, and without any modifications start reading files from SD. Attached sata ssd have no UFS/FAT partition and no any partition is mounted. (my hardware is Banana PI M1)
> 
> Here is three examples:
> read disk using tar with transfer data to another process (wc) and without (to dev/null)
> 
> Interesting is, that after successful read, when I'm trying to "halt" the computer I'm receiving fantastic error I not understand.
> 
> Outputs from my experiment follows.
> 
> Jindra
> 
> ---------------------------------------------
> SATA disk attached, but not used:
> ---------------------------------------------
> root at a20:~ # uname -a
> 
> FreeBSD a20 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r295683: Wed Feb 17 05:22:46 UTC 2016 root at releng2.nyi.freebsd.org:/usr/obj/arm.armv6/usr/src/sys/A20  arm
> root at a20:~ # tar cf - /usr | wc
> 
> tar: Removing leading '/' from member names
> panic: vm_page_insert_after: page already inserted
> cpuid = 0
> KDB: enter: panic
> [ thread pid 679 tid 100084 ]
> Stopped at      $d.7:   ldrb    r15, [r15, r15, ror r15]!
> db>
> 
> ---------------------------------------------
> root at a20:~ # tar cf /dev/null /usr
> 
> tar: Removing leading '/' from member names
> panic: vm_page_insert_after: page already inserted
> cpuid = 0
> KDB: enter: panic
> [ thread pid 644 tid 100067 ]
> Stopped at      $d.7:   ldrb    r15, [r15, r15, ror r15]!
> db>
> 
> 
> ---------------------------------------------
> NO SATA disk attached:
> ---------------------------------------------
> 
> root at a20:~ # uname -a
> 
> FreeBSD a20 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r295683: Wed Feb 17 05:22:46 UTC 2016 root at releng2.nyi.freebsd.org:/usr/obj/arm.armv6/usr/src/sys/A20  arm
> root at a20:~ # tar cf - /usr | wc
> 
> tar: Removing leading '/' from member names
> 5994501 28169833 716206080
> root at a20:~ #
> root at a20:~ # halt
> 
> Feb 17 05:37:21 a20 halt: halted by root
> 
> Feb 17 05:37:21 a20 syslogd: exiting on signal 15
> 
> Waiting (max 60 seconds) for system process `vnlru' to stop...done
> Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
> Waiting (max 60 seconds) for system process `syncer' to stop...
> Syncing disks, vnodes remaining...2 1 0 0 done
> All buffers synced.
> lock order reversal:
> 1st 0xc45b3db4 ufs (ufs) @ /usr/src/sys/kern/vfs_mount.c:1222
> 2nd 0xc432cc94 syncer (syncer) @ /usr/src/sys/kern/vfs_subr.c:2617
> stack backtrace:
> lock order reversal:
> 1st 0xc45b3b74 ufs (ufs) @ /usr/src/sys/kern/vfs_mount.c:1222
> 2nd 0xc45b35d4 devfs (devfs) @ /usr/src/sys/fs/msdosfs/msdosfs_vfsops.c:994
> stack backtrace:
> Uptime: 3m12s
> 
> The operating system has halted.
> Please press any key to reboot.
> _______________________________________________
> freebsd-arm at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"