From owner-cvs-all@FreeBSD.ORG Thu Dec 2 21:11:05 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DDD8A16A4E3 for ; Thu, 2 Dec 2004 21:11:04 +0000 (GMT) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C39C43D5D for ; Thu, 2 Dec 2004 21:11:04 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 14407 invoked from network); 2 Dec 2004 21:11:04 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 2 Dec 2004 21:11:03 -0000 Received: from qa4379.itdev.weather.com (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iB2LArj0007530; Thu, 2 Dec 2004 16:11:01 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Pawel Jakub Dawidek Date: Thu, 2 Dec 2004 15:33:44 -0500 User-Agent: KMail/1.6.2 References: <200412012105.iB1L52xX017823@repoman.freebsd.org> <20041201231730.GB813@darkness.comp.waw.pl> In-Reply-To: <20041201231730.GB813@darkness.comp.waw.pl> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200412021533.44254.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/acpica acpi_pci_link.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 21:11:05 -0000 On Wednesday 01 December 2004 06:17 pm, Pawel Jakub Dawidek wrote: > On Wed, Dec 01, 2004 at 09:05:02PM +0000, John Baldwin wrote: > +> jhb 2004-12-01 21:05:02 UTC > +> > +> FreeBSD src repository > +> > +> Modified files: > +> sys/dev/acpica acpi_pci_link.c > +> Log: > +> - Do a better job of handling any Dependent Functions (aka DPFs) that > appear +> in the _PRS or _CRS of link devices. If faced with multiple > DPFs in a +> _PRS, we just use the first one. We assume that if _CRS > has DPF tags they +> only contain a single set since multiple DPFs > wouldn't make any sense. In +> practice, the only DPFs I've seen so > far for link devices are that the one +> IRQ resource is surrounded by > a DPF tag pair for no apparent reason, and +> this should handle that > case fine now. > +> - Only allocate link structures for IRQ resources for link devices > rather +> than allocating a link structure for every resource. > > On my box things looks much worse (not sure if this is related): > > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) XEON(TM) CPU 1.80GHz (1799.75-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 > > Features=0x3febfbffA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM> > Hyperthreading: 2 logical CPUs > real memory = 1073741824 (1024 MB) > avail memory = 1046126592 (997 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 6 > cpu3 (AP): APIC ID: 7 > kernel trap 12 with interrupts disabled > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x9 > fault code = supervisor write, page not present > instruction pointer = 0x8:0xc05ac7c9 > stack pointer = 0x10:0xc0820cb4 > frame pointer = 0x10:0xc0820cd0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = resume, IOPL = 0 > current process = 0 (swapper) > [thread pid 0 tid 0 ] > Stopped at cpu_fork+0x1a1: incl 0x8(%eax) > db> tr > Tracing pid 0 tid 0 td 0xc0617e20 > cpu_fork(c0617e20,c1e8b000,c1e83300,60034,c1e8b068,0,c05cd0e1,287,c0619fe0, >c05cd0e1,283) at cpu_fork+0x1a1 > fork1(c0617e20,60034,0,c0820d4c) at fork1+0xbe5 > kthread_create(c0488eac,0,0,40000,0) at kthread_create+0x33 > ktrace_init(0,c1e70f70,81ec00,81e000,828000) at ktrace_init+0xac > mi_startup() at mi_startup+0xb3 > begin() at begin+0x2c > db> This is well before the link code. Can you use gdb to find the file/line for cpu_fork+0x1a1? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org