Date: Sat, 20 Sep 2014 21:14:54 +0200 (CEST) From: Gilles DALMAS <gdalmas@wanadoo.fr> To: Ganbold Tsagaankhuu <ganbold@gmail.com> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: kernel debugger on cubietruck Message-ID: <857916216.19088.1411240494803.JavaMail.www@wwinf1p21> In-Reply-To: <139071258.18161.1411238741408.JavaMail.www@wwinf1p20> References: <568188637.10901.1411218668061.JavaMail.www@wwinf1p20> <CAP=KkTwhRpJRW8jTLCjYRf55RLc-xSi%2BFCEBd5WHpU0hn-bUmQ@mail.gmail.com> <1886035707.11136.1411219513483.JavaMail.www@wwinf1p20> <CAGtf9xNnNavZLsSkTEpku187z7cCA%2BtgmXNODa3UQJZ4Kncqcg@mail.gmail.com> <284420224.12277.1411223197278.JavaMail.www@wwinf1p20> <584735728.12399.1411223474805.JavaMail.www@wwinf1p20> <CAGtf9xNRanWo1F_hY4KHWCWDUNfNn=bcq__qxT-i2YbJCgE%2BWA@mail.gmail.com> <139071258.18161.1411238741408.JavaMail.www@wwinf1p20>
index | next in thread | previous in thread | raw e-mail
the network interface is not detected > Message du 20/09/14 20:45 > De : "Gilles DALMAS" > A : "Ganbold Tsagaankhuu" > Copie à : "freebsd-arm" > Objet : Re: kernel debugger on cubietruck > > when I try to put "ufs: / dev / da0", the system starts but I have a lot of "no such device" and "spurious interrupt detected" > Message du 20/09/14 16:35 > De : "Ganbold Tsagaankhuu" > A : "Gilles DALMAS" > Copie à : > Objet : Re: kernel debugger on cubietruck > > > > On Sat, Sep 20, 2014 at 10:31 PM, Gilles DALMAS wrote: > > no need to re make the kernel-toolchain ? > > No just build kernel only. > Ganbold > > > > > > Message du 20/09/14 16:26 > > De : "Gilles DALMAS" > > A : "Ganbold Tsagaankhuu" > > Copie à : "freebsd-arm@freebsd.org" > > Objet : Re: kernel debugger on cubietruck > > > > i comment emac line from : # Ethernet device loop device ether device mii device smscphy #device cpsw device bpf device emac # USB ethernet support, requires miibus device miibus and re run the compilation ? no need to re created the sd card ? just the USB flash ? > Message du 20/09/14 16:09 > De : "Ganbold Tsagaankhuu" > A : "Gilles DALMAS" > Copie à : "freebsd-arm@freebsd.org" > Objet : Re: kernel debugger on cubietruck > > > > On Sat, Sep 20, 2014 at 9:25 PM, Gilles DALMAS wrote: > I did not know much about debug kernel, but when I pass the trace command, I get: > > db> trace > Tracing pid 0 tid 100000 td 0xc08ba870 > db_trace_self() at db_trace_self > pc = 0xc04eba6c lr = 0xc0232780 (db_hex2dec+0x4d8) > sp = 0xc08e5750 fp = 0xc08e5768 > r10 = 0xc08ba1c4 > db_hex2dec() at db_hex2dec+0x4d8 > pc = 0xc0232780 lr = 0xc02320f0 (db_command_loop+0x2fc) > sp = 0xc08e5770 fp = 0xc08e5810 > r4 = 0x00000000 r5 = 0x00000000 > r6 = 0x00000063 > db_command_loop() at db_command_loop+0x2fc > pc = 0xc02320f0 lr = 0xc0231e54 (db_command_loop+0x60) > sp = 0xc08e5818 fp = 0xc08e5828 > r4 = 0xc0528609 r5 = 0xc0540c1c > r6 = 0xc08ba1b0 r7 = 0xc08e5a48 > r8 = 0x00000001 r9 = 0xc05d2918 > r10 = 0xc0615aa4 > db_command_loop() at db_command_loop+0x60 > pc = 0xc0231e54 lr = 0xc023481c (X_db_symbol_values+0x250) > sp = 0xc08e5830 fp = 0xc08e5950 > r4 = 0x00000000 r5 = 0xc08ba1bc > r6 = 0xc0615ac8 > X_db_symbol_values() at X_db_symbol_values+0x250 > pc = 0xc023481c lr = 0xc0352c88 (kdb_trap+0x15c) > sp = 0xc08e5958 fp = 0xc08e5978 > r4 = 0x00000000 r5 = 0x00000005 > r6 = 0xc0615ac8 r7 = 0xc08e5a48 > kdb_trap() at kdb_trap+0x15c > pc = 0xc0352c88 lr = 0xc050138c (data_abort_handler+0x680) > sp = 0xc08e5980 fp = 0xc08e5998 > r4 = 0xc08e5a48 r5 = 0x00000005 > r6 = 0x600001d3 r7 = 0x00000000 > r8 = 0x00000013 r9 = 0xc08e5a48 > r10 = 0x00000001 > data_abort_handler() at data_abort_handler+0x680 > pc = 0xc050138c lr = 0xc0501134 (data_abort_handler+0x428) > sp = 0xc08e59a0 fp = 0xc08e5a40 > r4 = 0xc08e5eb0 r5 = 0xc08ba870 > r6 = 0xc08ba548 r7 = 0x00000005 > data_abort_handler() at data_abort_handler+0x428 > pc = 0xc0501134 lr = 0xc04ed754 (exception_exit) > sp = 0xc08e5a48 fp = 0xc08e5ab0 > r4 = 0xc3b49f00 r5 = 0xc3b4a080 > r6 = 0xc3b4a0b8 r7 = 0x00000000 > r8 = 0xc056b038 r9 = 0xc3ae1700 > r10 = 0xc05d4930 > exception_exit() at exception_exit > pc = 0xc04ed754 lr = 0xc024e0f0 (mii_phy_flowstatus+0x2080) > sp = 0xc08e5a98 fp = 0xc08e5ab0 > r0 = 0x00000000 r1 = 0xc0547c85 > r2 = 0x00000072 r3 = 0x00000008 > r4 = 0xc3b49f00 r5 = 0xc3b4a080 > r6 = 0xc3b4a0b8 r7 = 0x00000000 > r8 = 0xc056b038 r9 = 0xc3ae1700 > r10 = 0xc05d4930 r12 = 0x00000000 > strcmp() at strcmp+0x4 > pc = 0xc03d7604 lr = 0xc024e0f0 (mii_phy_flowstatus+0x2080) > sp = 0xc08e5a98 fp = 0xc08e5ab0 > Unwind failure (no registers changed) > > Please try without emac driver. MII in Cubietruck could be different. > > Ganbold > > > > > > > > Message du 20/09/14 15:13 > > De : "Boris Astardzhiev" > > A : "Gilles DALMAS" > > Copie à : freebsd-arm@freebsd.org > > Objet : Re: kernel debugger on cubietruck > > > > > > Hi, > > > As far as I see strcmp() is passed a NULL pointer, try issuing a backtrace to get the exact place of calling. > > > Regards > > On Sep 20, 2014 4:11 PM, "Gilles DALMAS" wrote: > > hi, > > > > > > > > I would compile freebsd for it run on a cubietruck. For this I used the wiki page: https://wiki.freebsd.org/FreeBSD/arm/Cubieboard using option confifuration "CUBIEBOARD2." everything goes well, but starting on the "truck", I get this message: > > > > > > > > vm_fault(0xc08bab80, 0, 1, 0) -> 1 > > Fatal kernel mode data abort: 'Translation Fault (S)' > > trapframe: 0xc08e5a48 > > FSR=00000005, FAR=00000000, spsr=a00001d3 > > r0 =00000000, r1 =c0547c85, r2 =00000072, r3 =00000008 > > r4 =c3b49f00, r5 =c3b4a080, r6 =c3b4a0b8, r7 =00000000 > > r8 =c056b038, r9 =c3ae1700, r10=c05d4930, r11=c08e5ab0 > > r12=00000000, ssp=c08e5a98, slr=c024e0f0, pc =c03d7604 > > > > [ thread pid 0 tid 100000 ] > > Stopped at strcmp+0x4: ldrb r3, [r0] > > > > > > > > where is the problem please ? > > > > _______________________________________________ > > freebsd-arm@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > _______________________________________________ freebsd-arm@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-arm To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > _______________________________________________ freebsd-arm@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-arm To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@FreeBSD.ORG Sat Sep 20 19:24:17 2014 Return-Path: <owner-freebsd-arm@FreeBSD.ORG> Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E98EFEE5; Sat, 20 Sep 2014 19:24:17 +0000 (UTC) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 61AE3F48; Sat, 20 Sep 2014 19:24:17 +0000 (UTC) Received: from [73.34.117.227] (helo=ilsoft.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <ian@FreeBSD.org>) id 1XVQGQ-0001If-DY; Sat, 20 Sep 2014 19:24:10 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id s8KJO9qr016862; Sat, 20 Sep 2014 13:24:09 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/hPFpEMvfkAv00kf34fk4v X-Authentication-Warning: paranoia.hippie.lan: Host revolution.hippie.lan [172.22.42.240] claimed to be [172.22.42.240] Subject: Re: FreeBSD-11.0-CURRENT on ARM: performance and load average From: Ian Lepore <ian@FreeBSD.org> To: Maxim V FIlimonov <che@bein.link> In-Reply-To: <7351653.A2UeEk9AA3@quad> References: <7351653.A2UeEk9AA3@quad> Content-Type: multipart/mixed; boundary="=-z+3p5YfilYZLalC+jqRC" Date: Sat, 20 Sep 2014 13:24:08 -0600 Message-ID: <1411241048.66615.148.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Cc: freebsd-arm@freebsd.org, freebsd-current@freebsd.org, mav@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arm>, <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>; List-Post: <mailto:freebsd-arm@freebsd.org> List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>, <mailto:freebsd-arm-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 20 Sep 2014 19:24:18 -0000 --=-z+3p5YfilYZLalC+jqRC Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Sat, 2014-09-20 at 22:44 +0400, Maxim V FIlimonov wrote: > Hello everyone, > > Recently, I encountered a problem with -CURRENT on an ARM board (cubieboard2 > to be precise). The problem was that the load average was above 2. Including > the fact that the board has 2 CPU cores, that's strange. Also, the network > throughput was way too slow: from 3 kilobytes per second earlier to 20..50 > about now. > > Here's a workaround for that: > > sysctl kern.eventtimer.periodic=1 > With that, the network performance increased while LA decreased to a decent > 0.3..0.5. Since it's happening only on that hardware, there's a good chance the problem is in the allwinner a10/a20 clock driver, not in the general eventtimer code. In fact, looking at the code it appears that a divide-by-16 is being set in the hardware, but not accounted for when setting the frequency of the eventtimer. Hmm, it should affect the timecounter too, in which case you'd see time-of-day advancing 16x too fast. If ntpd is running it would need to step the clock pretty frequently, which would show up in syslog. I don't have hardware to test on, please see if the attached patch makes a difference. -- Ian --=-z+3p5YfilYZLalC+jqRC Content-Disposition: inline; filename="allwinner_timer.diff" Content-Type: text/x-patch; name="allwinner_timer.diff"; charset="us-ascii" Content-Transfer-Encoding: 7bit Index: sys/arm/allwinner/timer.c ==================================================================--- sys/arm/allwinner/timer.c (revision 271909) +++ sys/arm/allwinner/timer.c (working copy) @@ -199,7 +199,7 @@ a10_timer_attach(device_t dev) val |= TIMER_ENABLE; timer_write_4(sc, SW_TIMER_IRQ_EN_REG, val); - sc->timer0_freq = SYS_TIMER_CLKSRC; + sc->timer0_freq = SYS_TIMER_CLKSRC / 16; /* Set desired frequency in event timer and timecounter */ sc->et.et_frequency = sc->timer0_freq; --=-z+3p5YfilYZLalC+jqRC--help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?857916216.19088.1411240494803.JavaMail.www>