Date: Thu, 14 Dec 2006 11:56:46 -0500 From: John Baldwin <jhb@freebsd.org> To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de> Cc: freebsd-acpi@freebsd.org Subject: Re: Interrupt routing issue on Compaq nx6325 Message-ID: <200612141156.46852.jhb@freebsd.org> In-Reply-To: <20061214162947.GA6287@uriah.heep.sax.de> References: <20061213221550.GA67376@uriah.heep.sax.de> <200612141053.10344.jhb@freebsd.org> <20061214162947.GA6287@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 14 December 2006 11:29, Joerg Wunsch wrote: > As John Baldwin wrote: > > > > My current workaround is (for RELENG_6) > > > > > > http://people.freebsd.org/~ariff/misc/idlecpu_apic_4.diff > > > > > > (hw.apic.idle_cpu=1 or 2) > > > This doesn't sound like his problem. Joerg, can you get a linux > > dmesg and a freebsd dmesg from the box so I can compare them? > > Well, at least Ariff's workaround helped my system as well. My > only/major concern with it is about the additional power consumption > when running on batteries, but for the time being, I can live with two > different boot modes for this: one that uses HLT and only 1 CPU > (without the APIC) for minimal battery power consumption, and another > one using the APIC and both CPU cores, with HLT disabled. > > What in particular caught my eye in the Linux messages is: > > Dec 12 23:33:26 remi kernel: ENABLING IO-APIC IRQs > Dec 12 23:33:26 remi kernel: ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 > Dec 12 23:33:26 remi kernel: ..MP-BIOS bug: 8254 timer not connected to IO-APIC > Dec 12 23:33:26 remi kernel: ...trying to set up timer (IRQ0) through the 8259A ... failed. > Dec 12 23:33:26 remi kernel: ...trying to set up timer as Virtual Wire IRQ... works. > > I didn't quite follow the referred to discussion of the Linux kernel > hackers, is the above their workaround, or is that something entirely > different? That's something different because of the way IRQ0 doesn't consistently work when using APIC. I thought you meant that you had a problem with PCI devices not working (i.e. an "interrupt routing problem"). -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200612141156.46852.jhb>