Date: Tue, 4 Nov 2003 16:50:33 +0100 (CET) From: Harti Brandt <brandt@fokus.fraunhofer.de> To: John Baldwin <jhb@FreeBSD.org> Cc: current@FreeBSD.org Subject: RE: New interrupt stuff breaks ASUS 2 CPU system Message-ID: <20031104164938.D72398@beagle.fokus.fraunhofer.de> In-Reply-To: <XFMail.20031104103812.jhb@FreeBSD.org> References: <XFMail.20031104103812.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 4 Nov 2003, John Baldwin wrote: JB> JB>On 04-Nov-2003 Harti Brandt wrote: JB>> JB>> Hi, JB>> JB>> I have an ASUS system with 2 CPUs that I need to run at HZ=10000. This JB>> worked until yesterday, but with the new interrupt code it doesn't boot JB>> anymore. It works for the standard HZ, but if I set HZ=1000 I get a double JB>> fault. I suspect a race condition in the interrupt handling. My config JB>> file has JB>> JB>> options SMP JB>> device apic JB>> options HZ=1000 JB> JB>Ok, I can try to reproduce. JB> JB>> Device configuration finished. JB>> Timecounter "TSC" frequency 1380009492 Hz quality -100 JB>> Timecounters cpuid = 0; apic id = 00 JB>> instruction pointer = 0x8:0xc048995d JB>> stack pointer = 0x10:0xc0821bf4 JB>> frame pointer cpuid = 0; apic id = 00 JB>> JB>> 0xc048995d is in critical_exit. It is the jmp after the popf from JB>> cpu_critical_exit. JB> JB>This is where interrupts are re-enabled, so you are getting an interrupt. JB>It might be helpful to figure what type of fault you are actually getting. tf_err is 0, tf_trapno is 30 (decimal). harti -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.fraunhofer.de, harti@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031104164938.D72398>