Date: Sat, 15 Dec 2007 22:40:05 +0100 From: Bernd Walter <ticso@cicely12.cicely.de> To: Stanislav Sedov <stas@freebsd.org> Cc: freebsd-arm@freebsd.org Subject: Re: Align exception (was: MMC cards support) Message-ID: <20071215214005.GE48684@cicely12.cicely.de> In-Reply-To: <20071215211014.GA27843@dracon.ht-systems.ru> References: <20071214090128.GM31230@cicely12.cicely.de> <20071214115226.0b2cb7e2@peedub.jennejohn.org> <20071214.062511.74732956.imp@bsdimp.com> <20071214153201.18c4c5ea@peedub.jennejohn.org> <47629E53.30404@semihalf.com> <20071214190825.GG17356@dracon.ht-systems.ru> <20071215105951.GN17356@dracon.ht-systems.ru> <20071215152242.GP17356@dracon.ht-systems.ru> <20071215164348.GQ17356@dracon.ht-systems.ru> <20071215211014.GA27843@dracon.ht-systems.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Dec 16, 2007 at 12:10:14AM +0300, Stanislav Sedov wrote: > On Sat, Dec 15, 2007 at 07:43:48PM +0300 Stanislav Sedov mentioned: > > This address always comes from it->it_thread. and should obviously > > reflect thread td structure: > > > > td = it->it_thread; > > c00ee064: e51b301c ldr r3, [fp, #-28] > > c00ee068: e5933004 ldr r3, [r3, #4] > > c00ee06c: e50b3018 str r3, [fp, #-24] > > p = td->td_proc; > > c00ee070: e51b3018 ldr r3, [fp, #-24] > > c00ee074: e5933004 ldr r3, [r3, #4] > > > > However the contents of td (r3) is always 42203735 when > > it's loaded from it->it_thread. It looks like uart does > > something awful with the interrupt thread pointer. > > > > It's even better, when ithread_create initializes > structure for intr_thread, it does this correctly for all > interrupts, however when intr_event_schedule_thread began to > work on the uart0 interrupt event the intr_thread *it > structure contents is entirely broken, though the address > itself is correct. Very suspicios... > > Maybe I'm doing something wrong? What I did - I've build > the kernel using usual buildworld/buildkernel sequence, > loaded the resulting kernel image (I've tried both > kernel and kernel.bin) using u-boot to the KERNPHYSADDR > and jumped there. Though it seems to mount NFS correctly, > so the memory should be ok in my case. I'm not 100% sure if it is the same thing - would have to search in old mails. We've seen a something like this with specific kernel on RM9200 systems. I'm not aware of other ARM systems, so it's likely a problem in an Atmel driver. It comes and goes with adding/removing unrelated options. I personally use spi support, which I don't need, to toggle the symptom if this happens to me. If you can find the real cause of this many people would be very happy. -- B.Walter http://www.bwct.de http://www.fizon.de bernd@bwct.de info@bwct.de support@fizon.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071215214005.GE48684>