From owner-freebsd-bugs@freebsd.org Fri Nov 18 16:11:12 2016 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8793FC48E68 for ; Fri, 18 Nov 2016 16:11:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 76D8FB12 for ; Fri, 18 Nov 2016 16:11:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uAIGBCuc062699 for ; Fri, 18 Nov 2016 16:11:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 213856] Fatal trap12: page fault while in kernel mode; Supervisor read data, page not present Date: Fri, 18 Nov 2016 16:11:12 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: arkadiusz.majewski@iptrace.pl X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2016 16:11:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213856 --- Comment #14 from IPTRACE --- The PCIe network card (QUAD PORT INTEL PRO1000ET PCI-E 0HM9JY) stopped work= ing. When I was waiting for the new one (INTEL GIGABIT ET2 QUAD PORT SERVER ADAP= TER E1G44ET) the system worked fine through 7 days. Then I've installed the new card and after a dozen or so hours system terminated. Fatal trap 9: general protection fault while in kernel mode cpuid =3D 33; apic id =3D 33 instruction pointer =3D 0x20:0xffffffff80b6a89e stack pointer =3D 0x28:0xffffffe3fcab4e7d0 frame pointer =3D 0x28:ffffffe3fcab4e820 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 Processor eflags =3D interrupt enabled, resume, IOPL =3D 0 Current process =3D 5639 (vtnet-2:0 tx) Trap number =3D 9 Panic: general protection fault Cupid =3D 33 KDB: stack backtrace: #0 0xffffffff80b24747 at kdb_backtrace+0x67 #1 0xffffffff80ad9ab2 at vpanic+0x182 #2 0xffffffff80ad9923 at panic+0x43 #3 0xffffffff80fa9d51 at trap_fatal+0x351 #4 0xffffffff80fa94ec at trap+0x26c #5 0xffffffff80f8d101 at calltrap+0x8 #6 0xffffffff821e4e1e at tapwrite+0x9e #7 0xffffffff80986677 at devfs_write_f+0xe7 #8 0xffffffff80b419a7 at dofilewrite+0x87 #9 0xffffffff80b41688 at kern_writev+0x68 #10 0xffffffff80b418f6 at sys_writev+0x36 #11 0xffffffff80faa6ae at amd64_syscall+0x4ce #12 0xffffffff80f8d3eb at Xfast_syscall+0xfb Uptime: 15h45m2s Please look at the difference between dmesg on 10.3-RELEASE and 11-RELEASE. There is problem with PCI bus or something like this on 11.0-RELEASE?! 11.0-RELEASE: pcib0: on acpi0 pcib0: _OSC returned error 0x10 pci0: on pcib0 pcib1: on acpi0 pcib1: _OSC returned error 0x10 pci1: on pcib1 pcib2: port 0xcf8-0xcff numa-domain 0 on acpi0 pcib2: _OSC returned error 0x10 pci2: numa-domain 0 on pcib2 pcib3: irq 26 at device 1.0 numa-domain 0 on pci2 pci3: numa-domain 0 on pcib3 pcib4: irq 32 at device 2.0 numa-domain 0 on pci2 pci4: numa-domain 0 on pcib4 pcib5: irq 32 at device 2.2 numa-domain 0 on pci2 pci5: numa-domain 0 on pcib5 pcib6: irq 40 at device 3.0 numa-domain 0 on pci2 pci6: numa-domain 0 on pcib6 pcib7: irq 40 at device 3.2 numa-domain 0 on pci2 pci7: numa-domain 0 on pcib7 pci2: at device 17.0 (no driver attached) xhci0: mem 0xc7200000-0xc720ffff irq 1= 9 at device 20.0 numa-domain 0 on pci2 pci2: at device 22.0 (no driver attached) pci2: at device 22.1 (no driver attached) ehci0: mem 0xc7214000-0xc72143ff irq 1= 8 at device 26.0 numa-domain 0 on pci2 pcib8: irq 16 at device 28.0 numa-domain 0 on pci2 pci8: numa-domain 0 on pcib8 pcib9: irq 18 at device 28.2 numa-domain 0 on pci2 pci9: numa-domain 0 on pcib9 pcib10: at device 0.0 numa-domain 0 on pci9 pci10: numa-domain 0 on pcib10 10.3-RELEASE: pcib0: on acpi0 pci255: on pcib0 pcib1: on acpi0 pci127: on pcib1 pcib2: port 0xcf8-0xcff on acpi0 pci0: on pcib2 pcib3: irq 26 at device 1.0 on pci0 pci1: on pcib3 pcib4: irq 32 at device 2.0 on pci0 pci2: on pcib4 pcib5: irq 32 at device 2.2 on pci0 pci3: on pcib5 pcib6: irq 40 at device 3.0 on pci0 pci4: on pcib6 pcib7: irq 40 at device 3.2 on pci0 pci5: on pcib7 pci0: at device 17.0 (no driver attached) --=20 You are receiving this mail because: You are the assignee for the bug.=