Problem building boot2 amd64->i386
Hi, I currently try to build the boot2 part of the bootloader on my amd64 for i386. I tried the crochet building script for the i386 and this script run into the problem. How to repeat: # cd head/sys/boot/i386/boot2 # make TARGET_ARCH=i386 Warning: Object directory not changed from original /usr/home/martin/Rasperry/head/sys/boot/i386/boot2 cc -Os -fno-guess-branch-probability -fomit-frame-pointer -fno-unit-at-a-time -mno-align-long-strings -mrtd -mregparm=3 -DUSE_XREAD -DUFS1_AND_UFS2 -DFLAGS=0x80 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 -I/usr/home/martin/Rasperry/head/sys/boot/i386/boot2/../../common -I/usr/home/martin/Rasperry/head/sys/boot/i386/boot2/../btx/lib -I. -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -Winline --param max-inline-insns-single=100 -march=i386 -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -m32 -std=gnu99 -m32 -c boot1.S ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -e start -Ttext 0x7c00 -o boot1.out boot1.o objcopy -S -O binary boot1.out boot1 dd if=/dev/zero of=boot2.ldr bs=512 count=1 1+0 records in 1+0 records out 512 bytes transferred in 0.000123 secs (4161790 bytes/sec) make: don't know how to make /usr/home/martin/Rasperry/head/sys/boot/i386/boot2/../btx/lib/crt0.o. Stop Don't get confused that the head source is in a directory named raspberry - I just want to build a reference i386 system to see if a problem with the kerberos also occurs on i386 systems. Is there a way to build the boot2 part the right way? In this case I would like to update the crochet script. Thank you, Martin Laabs ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Raspberry PI Kernel data abort
Hi, Sporadically the raspberry pi fails to mount its root mmc card. After power off and power on again works most of the time. However there seem to be also configurations that fail permanently. Unfortunately I have no image of a sd card that fails on every boot. Do you have any idea how to get more information whats going wrong? For details and the full boot log have a look to: http://www.freebsd.org/cgi/query-pr.cgi?pr=181601 Best regards, Martin Laabs ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Raspberry PI Kernel data abort
= 0xc2819960 r10 = 0x2081f0f0 kern_readv() at kern_readv+0x60 pc = 0xc0286764 lr = 0xc02866f4 (sys_read+0x4c) sp = 0xdd3eed90 fp = 0xdd3eedb8 r4 = 0xc2819960 r5 = 0x r6 = 0xbfffe5a0 r7 = 0x r8 = 0xdd3eee10 r9 = 0xc2872640 sys_read() at sys_read+0x4c pc = 0xc02866f4 lr = 0xc0476bc4 (swi_handler+0x284) sp = 0xdd3eedc0 fp = 0xdd3eee58 swi_handler() at swi_handler+0x284 pc = 0xc0476bc4 lr = 0xc0466928 (swi_entry+0x2c) sp = 0xdd3eee60 fp = 0xbfffedc0 r4 = 0x000378f8 r5 = 0x0002d258 r6 = 0xbfffe5a0 r7 = 0x0003 r8 = 0x r9 = 0x521d3af3 swi_entry() at swi_entry+0x2c pc = 0xc0466928 lr = 0xc0466928 (swi_entry+0x2c) sp = 0xdd3eee60 fp = 0xbfffedc0 Unable to unwind further vm_fault(0xc28999e0, 3601a000, 2, 0) -> 5 Fatal kernel mode data abort: 'Translation Fault (S)' trapframe: 0xdd3eec58 FSR=0805, FAR=3601a8c4, spsr=2013 r0 =3601a8c0, r1 =c272fb00, r2 =c04c14d9, r3 =05ef r4 =c056b1cc, r5 =c2857da4, r6 =c2857d00, r7 =3601a8c0 r8 =, r9 =c2857d88, r10=c272fd00, r11=dd3eed10 r12=, ssp=dd3eeca8, slr=c2819960, pc =c02a9aec [ thread pid 542 tid 100059 ] Stopped at soreceive_generic+0x4a8:str r1, [r0, #0x004] db> Best regards, Martin Laabs ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Raspberry PI sporadically fails to mount mmc card
Hi, Sporadically the raspberry pi fails to mount its root mmc card. After power off and power on again it works most of the time. However there seem to be also configurations that fail permanently. Unfortunately I have no image of a sd card that fails on every boot. Do you have any idea how to get more information whats going wrong? I think the problem starts after mmcsd0 received a timeout. Before that there are three lock reversals but I am not sure if they have any connection to the timeouts: lock order reversals before the timeout: 1st 0xc06f3c0c entropy harvest mutex (entropy harvest mutex) @ /usr/home/martin/Rasperry/head/sys/dev/random/randomdev_soft.c:242 2nd 0xc25d7c20 uart_hwmtx (uart_hwmtx) @ /usr/home/martin/Rasperry/head/sys/dev/uart/uart_cpu.h:92 1st 0xc06f3c0c entropy harvest mutex (entropy harvest mutex) @ /usr/home/martin/Rasperry/head/sys/dev/random/randomdev_soft.c:242 2nd 0xc059198c sleepq chain (sleepq chain) @ /usr/home/martin/Rasperry/head/sys/kern/subr_sleepqueue.c:240 1st 0xc06f3c0c entropy harvest mutex (entropy harvest mutex) @ /usr/home/martin/Rasperry/head/sys/dev/random/randomdev_soft.c:242 2nd 0xc059198c sleepq chain (sleepq chain) @ /usr/home/martin/Rasperry/head/sys/kern/subr_sleepqueue.c:240 [...] usbus0: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 uhub0: 1 port with 1 removable, self powered mmcsd0: 8GB at mmc0 50.0MHz/4bit/65535-block WARNING: WITNESS option enabled, expect reduced performance. WARNING: DIAGNOSTIC option enabled, expect reduced performance. mmcsd0: Error indicated: 1 Timeout mmcsd0: Error indicated: 1 Timeout Root mount waiting for: usbus0 ugen0.2: at usbus0 uhub1: on usbus0 uhub1: MTT enabled Root mount waiting for: usbus0 uhub1: 3 ports with 2 removable, self powered Root mount waiting for: usbus0 ugen0.3: at usbus0 smsc0: on usbus0 Trying to mount root from ufs:/dev/mmcsd0s2a [rw,noatime]... mountroot: waiting for device /dev/mmcsd0s2a ... smsc0: chip 0xec00, rev. 0002 miibus0: on smsc0 ukphy0: PHY 1 on miibus0 ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ue0: on smsc0 ue0: Ethernet address: b8:27:eb:1d:b7:5a Mounting from ufs:/dev/mmcsd0s2a failed with error 19. Loader variables: vfs.root.mountfrom=ufs:/dev/mmcsd0s2a vfs.root.mountfrom.options=rw,noatime Manual root filesystem specification: : [options] Mount using filesystem and with the specified (optional) option list. eg. ufs:/dev/da0s1a zfs:tank cd9660:/dev/acd0 ro (which is equivalent to: mount -t cd9660 -o ro /dev/acd0 /) ? List valid disk boot devices . Yield 1 second (for background tasks) Abort manual input mountroot> For details and the full boot log have a look to: http://www.freebsd.org/cgi/query-pr.cgi?pr=181601 Best regards, Martin Laabs ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: arm/181602: Raspberry PI kernel panic after DHCP
On 28.08.2013 14:10, Ian Lepore wrote: > On Wed, 2013-08-28 at 05:44 +0000, Martin Laabs wrote: >>> Number: 181602 >>> Category: arm >>> Synopsis: Raspberry PI kernel panic after DHCP [...] > This problem was caused by recent changes to the layout of struct mbuf > and the structures embedded within it. Fixed in r254973. OK. I can confirm this for the Raspberry-Pi. Running a r254984 So from my side it is OK to close the bug. Best regards, Martin Laabs ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
No UDP/TCP IPv6 connectivity (only) to router using gif interface - maybe ARM related
Hi, I tried to set up my raspberry PI as an ipv6 router. As a tunnel broker I use sixxs. Now I observed an interesting behavior: Every host from my network can reach the ipv6 world. The ipv6 world can also reach every host in my network. However - the router itself is unable to make udp or tcp connection to the "world" and is also unable to accept connections form the "world" ICMP however works properly. I had a look to the tcpdump and when trying to connect i.e. to www.kame.net the rasperry router sends a syn packet and get a syn/ack packet back. The rest of the handshake is missing. I tried also some udp with netcat (nc -6 -u -l on the server and nc -6 -u on the client) This works great for internal (ethernet) traffic but when the data should go through the tunnel if fails. The last test is maybe the most significant to describe the bug: Start netcat to listen for UDP packages on an external host: nc -6 -u -l Connect from the RPI-Router to that host nc -6 -u 2001:4dd0::::2 Now it is possible to send data from the RPI router to the external host but the opposite direction does not work. Tcpdump however shows that the udp package arrives but it is not "forwarded" to the application. So for me it seems to be a problem with the handling of the receiving data in the gif interface. This behavior is independent from net.inet6.ip6.forwarding or net.inet6.ip6.redirect status. The router system: FreeBSD raspberry-pi.xxx 10.0-CURRENT FreeBSD 10.0-CURRENT #2 r254984 Best regards, Martin Laabs ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No UDP/TCP IPv6 connectivity (only) to router using gif interface - maybe ARM related
Hi , > Whether you feel it right, or not, net.inet.ip.forwarding must be 1 for gif > to work (even for IPv6). This is a unintuitive behavior. But fortunately this solve this problem. I suggest adding setting this sysctl if ipv6_gateway_enable is enabled in the rc.conf. Best regards, Martin Laabs ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"