Date: Wed, 12 Mar 2008 12:24:07 -1000 (HST) From: Jeff Roberson <jroberson@chesapeake.net> To: Gary Jennejohn <gary.jennejohn@freenet.de> Cc: arch@FreeBSD.org Subject: Re: amd64 cpu_switch in C. Message-ID: <20080312122300.Y1091@desktop> In-Reply-To: <20080312110229.5aeefc1f@peedub.jennejohn.org> References: <20080310161115.X1091@desktop> <47D758AC.2020605@freebsd.org> <20080312110229.5aeefc1f@peedub.jennejohn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 12 Mar 2008, Gary Jennejohn wrote: > On Wed, 12 Mar 2008 12:14:36 +0800 > David Xu <davidxu@FreeBSD.org> wrote: > >> Jeff Roberson wrote: >>> http://people.freebsd.org/~jeff/amd64.diff >> >> This is a good idea. In fact, according to calling conversion, some >> registers are not needed to be saved across function call, e.g on >> i386, eax, edx, and ecx. :-) but gdb may need them to dig out >> stack variable's value. >> > > I applied this patch yesterday on an AMD64 X2 box and got this panic > today after I started X: > > Unread portion of the kernel message buffer: > panic: smp_tlb_shootdown: interrupts disabled > cpuid = 0 > Uptime: 47s > Physical memory: 3062 MB > Dumping 169 MB: 154 138 122 106 90 74 58 42 26 10 > > That's all the useful information which I have because the back trace > is corrupted. > > BTW I'm using SCHED_ULE. > > Maybe I shouldn't have tried this patch yet since it doesn't seem to be SMP > ready. Thanks for testing. I just ran into that panic myself. I don't think it's a SMP problem. In general things on arch@ are sometimes more experimental than things we mail to to current@ asking for people to test. Thanks, Jeff > > --- > Gary Jennejohn >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080312122300.Y1091>