Date: Sat, 27 Nov 2004 23:26:44 -0500 From: "Alexandre \"Sunny\" Kovalenko" <Alex.Kovalenko@verizon.net> To: Divacky Roman <xdivac02@stud.fit.vutbr.cz> Cc: current@freebsd.org Subject: Re: ACPI related panic on early boot Message-ID: <1101616004.1087.9.camel@RabbitsDen> In-Reply-To: <20041127092059.GA93818@stud.fit.vutbr.cz> References: <20041127092059.GA93818@stud.fit.vutbr.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2004-11-27 at 10:20 +0100, Divacky Roman wrote: > Hi, > > after jhb@-s commits to acpi I am getting this panic early on boot, its > handwritten so there might be mistakes. > I have acpi as a module, and the panic seems to occur after probing fdc wihle I > have no fdc attached. I can provide any info you ask for... > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x5 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc049fb86 > stack pointer = 0x10:0xc0820c88 > frame pointer = 0x10:0xc0820c8c > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 0 (swapper) > [thread pid 0 tid 0] > Stopped at device_get_children+0x10: movl 0x4(%eax),%eax > db>trace > Tracing pid 0 tid 0 td 0xc05f7de0 > device_get_children(c1646100,c0820ca4,c0820ca8,c05d5bc0,101) at device_get_children+0x10 > acpi_wake_sysctl_walk(c157bb00,c1670a00,31,c157bb00,c157bb00) at acpi_wake_sysctl_walk+0x17 > acpi_wake_sysctl_walk(fee00fff,fee00000,c163a028,3,c07072a0) at acpi_wake_sysctl_walk+0x44 > acpi_attach(c157bb00,c157bb00,c1573dc0,c157bc00,c0820d34) at acpi_attach+0x684 > device_attach(c157bb00,c157bc00,c0820d48,c058feb3,c157bc00) at device_attach+0x226 > bus_generic_attach(c157bc00,c157bc00,c157bc4c,c0820d60,c04a039c) at bus_generic_attach+0x14 > nexus_attach(c157bc00,c157bc00,0,825000,c0820d70) at nexus_attach+0x13 > device_attach(c157bc00) at device_attach+0x226 > root_bus_configure(c15ca300,c05c5eec,0,c0820d98,c0468fab) at root_bus_configure+0x16 > configure(0,81ec00,81e000,0,c0429e05) at configure+0x1b > mi_startup() at mi_startup+0x86 > begin() at begin+0x2c > > roman > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Rolling back files below while keeping the rest of the tree current as of 21:40 EST eliminated crash for me: acpi_pci_link.c: 1.33 2004/09/25 06:15:56 acpi_pcib.c: 1.51 2004/11/11 22:33:08 acpi_pcib_acpi.c: 1.45 2004/11/09 07:02:33 acpi_pcib_pci.c: 1.10 2004/08/11 14:52:50 acpi_pcibvar.h: 1.3 2004/08/11 14:52:50 I can try patches or provide any additional details. Unfortunately, panic kicks in way before my remote console (PCMCIA Firewire), so backtraces would have to be hand-trascribed. Current one looks sufficiently like one above that I do not think it will add any value. -- Alexandre "Sunny" Kovalenko (Олександр Коваленко).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1101616004.1087.9.camel>