Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 28 Jul 2015 17:48:03 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 201947] Panics in if_bfe under certain loads types (reproducible with rtorrent)
Message-ID:  <bug-201947-8@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201947

            Bug ID: 201947
           Summary: Panics in if_bfe under certain loads types
                    (reproducible with rtorrent)
           Product: Base System
           Version: 10.1-STABLE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: obrien.hugh+bacon@gmail.com

Created attachment 159341
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=159341&action=edit
kgdb printout

rtorrent usage will often cause a panic. Sustained traffic with scp, etc. does
not exhibit this. I've caught one in action:

Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x30
fault code              = supervisor write data, page not present
instruction pointer     = 0x20:0xffffffff8048c5ad
stack pointer           = 0x28:0xfffffe0018667a50
frame pointer           = 0x28:0xfffffe0018667ab0
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         = 12 (irq21: bfe0)
trap number             = 12
panic: page fault
cpuid = 0
KDB: stack backtrace:
#0 0xffffffff80963000 at kdb_backtrace+0x60
#1 0xffffffff80928125 at panic+0x155
#2 0xffffffff80d258df at trap_fatal+0x38f
#3 0xffffffff80d25bf8 at trap_pfault+0x308
#4 0xffffffff80d2525a at trap+0x47a
#5 0xffffffff80d0b142 at calltrap+0x8
#6 0xffffffff8048d0bd at bfe_intr+0x17d
#7 0xffffffff808faf4b at intr_event_execute_handlers+0xab
#8 0xffffffff808fb396 at ithread_loop+0x96
#9 0xffffffff808f8b6a at fork_exit+0x9a
#10 0xffffffff80d0b67e at fork_trampoline+0xe
Uptime: 4d17h28m15s

<snip>
Full output in attachment.

Info file:

Dump header from device /dev/ada0p2
  Architecture: amd64
  Architecture Version: 2
  Dump Length: 174780416B (166 MB)
  Blocksize: 512
  Dumptime: Mon Jul 27 14:01:00 2015
  Hostname: majortom
  Magic: FreeBSD Kernel Dump
  Version String: FreeBSD 10.1-RELEASE-p10 #0: Wed May 13 06:54:13 UTC 2015
    root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
  Panic String: page fault
  Dump Parity: 2579429912
  Bounds: 1
  Dump Status: good

I've uploaded the vmcore file here if it's helpful:
https://skynet.ie/~teslacut/vmcore.0.xz

-- 
You are receiving this mail because:
You are the assignee for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-201947-8>