Bug 195130 - 10.1-STABLE r274611 panics randomly [amd64,zfs,wlan,ral,bridge]
Summary: 10.1-STABLE r274611 panics randomly [amd64,zfs,wlan,ral,bridge]
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 10.1-STABLE
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-bugs mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-18 05:12 UTC by ruanchunping
Modified: 2015-07-07 16:06 UTC (History)
0 users

See Also:


Attachments
three core.txt.X files. (242.90 KB, application/gzip)
2014-11-18 05:12 UTC, ruanchunping
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description ruanchunping 2014-11-18 05:12:14 UTC
Created attachment 149549 [details]
three core.txt.X files.

after upgrade to r274611 , the box panics randomly.

uname -a:
FreeBSD dev.myoffice.com 10.1-STABLE FreeBSD 10.1-STABLE #0 r274611: Mon Nov 17 19:08:05 CST 2014     root@dev.myoffice.com:/usr/obj/usr/src/sys/GENERIC_GATEWAY  amd64


core.txt.6:
======================================================================
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0xfffff80145d48808
fault code              = supervisor write data, page not present
instruction pointer     = 0x20:0xffffffff819e226e
stack pointer           = 0x28:0xfffffe010fd01a80
frame pointer           = 0x28:0xfffffe010fd01a90
code segment            = base rx0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 5 (arc_reclaim_thread)
trap number             = 12
panic: page fault
cpuid = 0
KDB: stack backtrace:
#0 0xffffffff809787b0 at kdb_backtrace+0x60
#1 0xffffffff8093d895 at panic+0x155
#2 0xffffffff80d8e62f at trap_fatal+0x38f
#3 0xffffffff80d8e948 at trap_pfault+0x308
#4 0xffffffff80d8dfaa at trap+0x47a
#5 0xffffffff80d73d52 at calltrap+0x8
#6 0xffffffff81a6b118 at zap_evict+0x58
#7 0xffffffff81a0579a at dbuf_clear+0x4a
#8 0xffffffff81a0a3c9 at dbuf_do_evict+0x69
#9 0xffffffff819fdc11 at arc_do_user_evicts+0xe1
#10 0xffffffff81a00fb1 at arc_reclaim_thread+0x221
#11 0xffffffff8090e2da at fork_exit+0x9a
#12 0xffffffff80d7428e at fork_trampoline+0xe
Uptime: 13h4m44s


core.txt.7:
=======================================================================
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x1
fault code              = supervisor read data, page not present
instruction pointer     = 0x20:0xffffffff809f2635
stack pointer           = 0x28:0xfffffe0110557bd0
frame pointer           = 0x28:0xfffffe0110557be0
code segment            = base rx0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = resume, IOPL = 0
current process         = 5013 (ps)
trap number             = 12
panic: page fault
cpuid = 0
KDB: stack backtrace:
#0 0xffffffff809787b0 at kdb_backtrace+0x60
#1 0xffffffff8093d895 at panic+0x155
#2 0xffffffff80d8e62f at trap_fatal+0x38f
#3 0xffffffff80d8e948 at trap_pfault+0x308
#4 0xffffffff80d8dfaa at trap+0x47a
#5 0xffffffff80d73d52 at calltrap+0x8
#6 0xffffffff8092f8dd at fill_kinfo_thread+0xbd
#7 0xffffffff8092f765 at fill_kinfo_proc+0x6f5
#8 0xffffffff8092fda9 at kern_proc_out+0x39
#9 0xffffffff809330b0 at sysctl_out_proc+0x60
#10 0xffffffff80932faf at sysctl_kern_proc+0x51f
#11 0xffffffff8094902e at sysctl_root+0x24e
#12 0xffffffff80949608 at userland_sysctl+0x1d8
#13 0xffffffff809493f4 at sys___sysctl+0x74
#14 0xffffffff80d8ef61 at amd64_syscall+0x351
#15 0xffffffff80d7403b at Xfast_syscall+0xfb
Uptime: 14m19s


core.txt.8:
====================================================================
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x809ada91
fault code              = supervisor read instruction, page not present
instruction pointer     = 0x20:0x809ada91
stack pointer           = 0x28:0xfffffe010fcaa9a0
frame pointer           = 0x28:0xfffffe010fcaaa20
code segment            = base rx0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 12 (irq265: ral0)
trap number             = 12
panic: page fault
cpuid = 0
KDB: stack backtrace:
#0 0xffffffff809787b0 at kdb_backtrace+0x60
#1 0xffffffff8093d895 at panic+0x155
#2 0xffffffff80d8e62f at trap_fatal+0x38f
#3 0xffffffff80d8e948 at trap_pfault+0x308
#4 0xffffffff80d8dfaa at trap+0x47a
#5 0xffffffff80d73d52 at calltrap+0x8
#6 0xffffffff809a9893 at m_freem+0x63
#7 0xffffffff81c74aec at rt2860_tx_intr+0xec
#8 0xffffffff81c747e1 at rt2860_intr+0x681
#9 0xffffffff809106bb at intr_event_execute_handlers+0xab
#10 0xffffffff80910b06 at ithread_loop+0x96
#11 0xffffffff8090e2da at fork_exit+0x9a
#12 0xffffffff80d7428e at fork_trampoline+0xe
Uptime: 2h35m1s


I'v attached three core.txt.X file.
Comment 1 Glen Barber freebsd_committer 2015-07-07 16:06:11 UTC
Does this problem still exist on 10.2-PRERELEASE?