Date: Wed, 30 May 2007 03:42:48 +0200 From: "Michal Zygmunt" <lahcim@fajne.com> To: "'Remko Lodder'" <remko@elvandar.org> Cc: freebsd-bugs@freebsd.org, ipfw@freebsd.org Subject: RE: page fault while in kernel-mode (dummynet) - amd64 Message-ID: <D6EB3E60C31C423C9CB10D7FF04F4FEE@ANTARESPC> In-Reply-To: <465C9BF5.8040302@elvandar.org> References: <34515DB3553C4F9E94A9649ABFF9FE71@ANTARESPC> <465C9BF5.8040302@elvandar.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Remko, I am providing coredump: http://www.lahcim.net/dump.tgz And some additional dmesg info that can be useful Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x28 fault code = supervisor write data, page not present instruction pointer = 0x8:0xffffffff805841d5 stack pointer = 0x10:0xffffffffb1c11b10 frame pointer = 0x10:0xffffff004d65e200 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 43 (dummynet) trap number = 12 panic: page fault cpuid = 0 Uptime: 5h38m15s Dumping 2021 MB (4 chunks) chunk 0: 1MB (156 pages) ... ok chunk 1: 2021MB (517274 pages) 2005 1989 1973 1957 1941 1925 1909 1893 1877 1861 1845 1829 1813 1797 1781 1765 1749 1733 1717 1701 1685 1669 1653 1637 1621 1605 1589 1573 1557 1541 1525 1509 1493 1477 1461 1445 1429 1413 1397 1381 1365 1349 1333 1317 1301 1285 1269 1253 1237 1221 1205 1189 1173 1157 1141 1125 1109 1093 1077 1061 1045 1029 1013 997 981 965 949 933 917 901 885 869 853 837 821 805 789 773 757 741 725 709 693 677 661 645 629 613 597 581 565 549 533 517 501 485 469 453 437 421 405 389 373 357 341 325 309 293 277 261 245 229 213 197 181 165 149 133 117 101 85 69 53 37 21 5 ... ok chunk 2: 1MB (149 pages) ... ok chunk 3: 1MB (1 pages) ... ok Dump complete Automatic reboot in 16 seconds - press a key on the console to abort Rebooting... cpu_reset: Stopping other CPUs Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-STABLE #1: Sun May 27 23:28:12 CEST 2007 root@plustech.pl:/usr/obj/usr/src/sys/GTT WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant WARNING: MPSAFE network stack disabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz (2404.82-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA ,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> Features2=0xe3bd<SSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,<b9>,CX16,XTPR,<b15>> AMD Features=0x20100800<SYSCALL,NX,LM> AMD Features2=0x1<LAHF> Cores per package: 2 real memory = 2120462336 (2022 MB) avail memory = 2034073600 (1939 MB) ACPI APIC Table: <INTEL DG965SS > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic0 <Version 2.0> irqs 0-23 on motherboard wlan: mac acl policy registered kbd1 at kbdmux0 netsmb_dev: loaded ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: <INTEL DG965SS> on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: <ACPI CPU> on acpi0 acpi_perf0: <ACPI CPU Frequency Control> on cpu0 acpi_perf0: failed in PERF_STATUS attach device_attach: acpi_perf0 attach returned 6 acpi_perf0: <ACPI CPU Frequency Control> on cpu0 acpi_perf0: failed in PERF_STATUS attach device_attach: acpi_perf0 attach returned 6 acpi_throttle0: <ACPI CPU Throttling> on cpu0 cpu1: <ACPI CPU> on acpi0 acpi_perf1: <ACPI CPU Frequency Control> on cpu1 acpi_perf1: failed in PERF_STATUS attach device_attach: acpi_perf1 attach returned 6 acpi_perf1: <ACPI CPU Frequency Control> on cpu1 acpi_perf1: failed in PERF_STATUS attach device_attach: acpi_perf1 attach returned 6 acpi_throttle1: <ACPI CPU Throttling> on cpu1 acpi_throttle1: failed to attach P_CNT device_attach: acpi_throttle1 attach returned 6 acpi_button0: <Sleep Button> on acpi0 pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 pci0: <ACPI PCI bus> on pcib0 pci0: <display, VGA> at device 2.0 (no driver attached) pci0: <simple comms> at device 3.0 (no driver attached) em0: <Intel(R) PRO/1000 Network Connection Version - 6.2.9> port 0x30c0-0x30df mem 0x90500000-0x9051ffff,0x90524000-0x90524fff irq 20 at device 25.0 on pci0 em0: Ethernet address: 00:19:d1:79:cf:bf em0: [GIANT-LOCKED] uhci0: <UHCI (generic) USB controller> port 0x30a0-0x30bf irq 16 at device 26.0 on pci0 uhci0: [GIANT-LOCKED] usb0: <UHCI (generic) USB controller> on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: <UHCI (generic) USB controller> port 0x3080-0x309f irq 21 at device 26.1 on pci0 uhci1: [GIANT-LOCKED] usb1: <UHCI (generic) USB controller> on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered ehci0: <EHCI (generic) USB 2.0 controller> mem 0x90525400-0x905257ff irq 18 at device 26.7 on pci0 ehci0: [GIANT-LOCKED] usb2: EHCI version 1.0 usb2: companion controllers, 2 ports each: usb0 usb1 usb2: <EHCI (generic) USB 2.0 controller> on ehci0 usb2: USB revision 2.0 uhub2: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 4 ports with 4 removable, self powered pci0: <multimedia> at device 27.0 (no driver attached) pcib1: <ACPI PCI-PCI bridge> at device 28.0 on pci0 pci1: <ACPI PCI bus> on pcib1 pcib2: <ACPI PCI-PCI bridge> at device 28.1 on pci0 pci2: <ACPI PCI bus> on pcib2 atapci0: <GENERIC ATA controller> port 0x2018-0x201f,0x2024-0x2027,0x2010-0x2017,0x2020-0x2023,0x2000-0x200f mem 0x90300000-0x903001ff irq 17 at device 0.0 on pci2 ata2: <ATA channel 0> on atapci0 ata3: <ATA channel 1> on atapci0 pcib3: <ACPI PCI-PCI bridge> at device 28.2 on pci0 pci3: <ACPI PCI bus> on pcib3 pcib4: <ACPI PCI-PCI bridge> at device 28.3 on pci0 pci4: <ACPI PCI bus> on pcib4 pcib5: <ACPI PCI-PCI bridge> at device 28.4 on pci0 pci5: <ACPI PCI bus> on pcib5 uhci2: <UHCI (generic) USB controller> port 0x3060-0x307f irq 23 at device 29.0 on pci0 uhci2: [GIANT-LOCKED] usb3: <UHCI (generic) USB controller> on uhci2 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered uhci3: <UHCI (generic) USB controller> port 0x3040-0x305f irq 19 at device 29.1 on pci0 uhci3: [GIANT-LOCKED] usb4: <UHCI (generic) USB controller> on uhci3 usb4: USB revision 1.0 uhub4: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub4: 2 ports with 2 removable, self powered uhci4: <UHCI (generic) USB controller> port 0x3020-0x303f irq 18 at device 29.2 on pci0 uhci4: [GIANT-LOCKED] usb5: <UHCI (generic) USB controller> on uhci4 usb5: USB revision 1.0 uhub5: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub5: 2 ports with 2 removable, self powered ehci1: <EHCI (generic) USB 2.0 controller> mem 0x90525000-0x905253ff irq 23 at device 29.7 on pci0 ehci1: [GIANT-LOCKED] usb6: EHCI version 1.0 usb6: companion controllers, 2 ports each: usb3 usb4 usb5 usb6: <EHCI (generic) USB 2.0 controller> on ehci1 usb6: USB revision 2.0 uhub6: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub6: 6 ports with 6 removable, self powered pcib6: <ACPI PCI-PCI bridge> at device 30.0 on pci0 pci6: <ACPI PCI bus> on pcib6 fxp0: <Intel 82558 Pro/100 Ethernet> port 0x1000-0x101f mem 0x90000000-0x90000fff,0x90100000-0x901fffff irq 21 at device 0.0 on pci6 miibus0: <MII bus> on fxp0 inphy0: <i82555 10/100 media interface> on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:08:c7:8c:96:06 fxp0: [GIANT-LOCKED] atapci1: <ITE IT8212F UDMA133 controller> port 0x1038-0x103f,0x1044-0x1047,0x1030-0x1037,0x1040-0x1043,0x1020-0x102f irq 22 at device 1.0 on pci6 ata4: <ATA channel 0> on atapci1 ata5: <ATA channel 1> on atapci1 fwohci0: <Texas Instruments TSB43AB22/A> mem 0x90204000-0x902047ff,0x90200000-0x90203fff irq 19 at device 3.0 on pci6 fwohci0: [GIANT-LOCKED] fwohci0: OHCI version 1.10 (ROM=0) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:90:27:00:01:c9:fa:f9 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: <IEEE1394(FireWire) bus> on fwohci0 fwe0: <Ethernet over FireWire> on firewire0 if_fwe0: Fake Ethernet address: 02:90:27:c9:fa:f9 fwe0: Ethernet address: 02:90:27:c9:fa:f9 sbp0: <SBP-2/SCSI over FireWire> on firewire0 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) isab0: <PCI-ISA bridge> at device 31.0 on pci0 isa0: <ISA bus> on isab0 atapci2: <Intel ICH8 SATA300 controller> port 0x3138-0x313f,0x3154-0x3157,0x3130-0x3137,0x3150-0x3153,0x3110-0x311f,0x3100 -0x310f irq 19 at device 31.2 on pci0 ata6: <ATA channel 0> on atapci2 ata7: <ATA channel 1> on atapci2 pci0: <serial bus, SMBus> at device 31.3 (no driver attached) atapci3: <Intel ICH8 SATA300 controller> port 0x3128-0x312f,0x314c-0x314f,0x3120-0x3127,0x3148-0x314b,0x30f0-0x30ff,0x30e0 -0x30ef irq 19 at device 31.5 on pci0 ata8: <ATA channel 0> on atapci3 ata9: <ATA channel 1> on atapci3 ppc0: <ECP parallel printer port> port 0x378-0x37f,0x778-0x77f irq 7 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: <Parallel port bus> on ppc0 plip0: <PLIP network interface> on ppbus0 lpt0: <Printer> on ppbus0 lpt0: Interrupt-driven port ppi0: <Parallel I/O> on ppbus0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A orm0: <ISA Option ROMs> at iomem 0xc0000-0xcafff,0xcb000-0xcbfff,0xcc000-0xcc7ff,0xce800-0xcf7ff on isa0 atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0 atkbd0: <AT Keyboard> irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] sc0: <System console> at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec fwe0f0: Ethernet address: 02:90:27:c9:fa:f9 fwe0f1: Ethernet address: 02:90:27:c9:fa:f9 fwe0f2: Ethernet address: 02:90:27:c9:fa:f9 fwe0f3: Ethernet address: 02:90:27:c9:fa:f9 fxp0f0: Ethernet address: 00:08:c7:8c:96:06 fxp0f1: Ethernet address: 00:08:c7:8c:96:06 fxp0f2: Ethernet address: 00:08:c7:8c:96:06 fxp0f3: Ethernet address: 00:08:c7:8c:96:06 em0f0: Ethernet address: 00:19:d1:79:cf:bf em0f1: Ethernet address: 00:19:d1:79:cf:bf em0f2: Ethernet address: 00:19:d1:79:cf:bf em0f3: Ethernet address: 00:19:d1:79:cf:bf IPv6 packet filtering initialized, default to accept, logging limited to 100 packets/entry IPsec: Initialized Security Association Processing. IP Filter: v4.1.13 initialized. Default = pass all, Logging = enabled ipfw2 (+ipv6) initialized, divert enabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry by default ad8: 190782MB <Seagate ST3200822A 3.01> at ata4-master UDMA100 ad10: 76318MB <WDC WD800BB-00JHA0 05.01C05> at ata5-master UDMA100 ad12: 305245MB <Seagate ST3320620AS 3.AAK> at ata6-master SATA150 SMP: AP CPU #1 Launched! P.S. I added ipfw@freebsd.org as CC but I am not subscribed to that list so I am not sure if this mail will be delivered properly to that list. If you will need any other dumps, let me know. Thanks, Michal Zygmunt -----Original Message----- From: Remko Lodder [mailto:remko@elvandar.org] Sent: Tuesday, May 29, 2007 11:33 PM To: Michal Zygmunt Cc: freebsd-bugs@freebsd.org Subject: Re: page fault while in kernel-mode (dummynet) - amd64 Michal Zygmunt wrote: > Hi, > > > > It seems that there is some problem with dummynet implementation and > happened on amd64 build > > > hello, The information you provided is not nearly enough to get started {sorry}, please see the developers handbook for more information http://www.freebsd.org/doc/en/books/developers-handbook on how to obtain the proper kernel dump that can be processed by our developers. Also please consider using ipfw@FreeBSD.org for this report since it would most likely get better attention there {special ipfw mailinglist which seems more appropriate}. Thanks for using FreeBSD!! -- Kind regards, Remko Lodder ** remko@elvandar.org FreeBSD ** remko@FreeBSD.org /* Quis custodiet ipsos custodes */
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D6EB3E60C31C423C9CB10D7FF04F4FEE>