Bug 15087
| Summary: | 3.3-STABLE panic while starting daemons (rlist_free) | ||
|---|---|---|---|
| Product: | Base System | Reporter: | graaf <graaf> |
| Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | 3.3-STABLE | ||
| Hardware: | Any | ||
| OS: | Any | ||
State Changed From-To: open->closed Upgrade to 4.3 and let us know is problem is still there. |
When booting, the server panics shortly after Postfix is started. The panic does not happen if Postfix is not started from the boot scripts but sometime later by hand (Postfix was started about 15 minutes after booting, and that did not cause a panic). This problem does not happen with 3.1-RELEASE. I believe that the problem is related to a combination of high network traffic combined with lots of disk activity. High activity on swap may also be related. The trace in kgdb looks like this: IdlePTD 2928640 initial pcb at 24dca4 panicstr: rlist_free: free end overlaps already freed area panic messages: --- panic: rlist_free: free end overlaps already freed area syncing disks... 35 35 35 35 35 35 35 35 35 35 35 35 35 35 35 35 35 35 35 35 giving up (da1:ahc0:0:1:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da1:ahc0:0:1:0): error code 10 dumping to dev 20401, offset 499712 dump 256 [ rest erased ] #0 boot (howto=256) at ../../kern/kern_shutdown.c:285 285 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=256) at ../../kern/kern_shutdown.c:285 #1 0xc0145521 in panic ( fmt=0xc021dd47 "rlist_free: free end overlaps already freed area") at ../../kern/kern_shutdown.c:446 #2 0xc014f009 in rlist_free (rlh=0xc02754a4, start=0, end=7) at ../../kern/subr_rlist.c:155 #3 0xc01da26b in swap_pager_freeswapspace (object=0xca6631f0, from=0, to=7) at ../../vm/swap_pager.c:422 #4 0xc01da34c in swap_pager_freespace (object=0xca6631f0, start=34, size=23393) at ../../vm/swap_pager.c:445 #5 0xc01df7ad in vm_map_delete (map=0xca6522c0, start=134811648, end=230629376) at ../../vm/vm_map.c:1833 #6 0xc01df850 in vm_map_remove (map=0xca6522c0, start=134811648, end=230629376) at ../../vm/vm_map.c:1874 #7 0xc01e76ef in obreak (p=0xca659b80, uap=0xca701f94) at ../../vm/vm_unix.c:107 #8 0xc020250b in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 134811648, tf_esi = 134549824, tf_ebp = -1077946656, tf_isp = -898621468, tf_ebx = 671987596, tf_edx = 671987576, tf_ecx = 671987572, tf_eax = 17, tf_trapno = 0, tf_err = 2, tf_eip = 671951496, tf_cs = 31, tf_eflags = 647, tf_esp = -1077946692, tf_ss = 39}) at ../../i386/i386/trap.c:1100 #9 0xc01f78fc in Xint0x80_syscall () #10 0x280d24f2 in ?? () #11 0x804c1a8 in ?? () #12 0x804b087 in ?? () #13 0x804a6c1 in ?? () #14 0x80490f5 in ?? () --- Fix: None known. How-To-Repeat: The problem happens everytime our main server is rebooted if Postfix is started at boot. Of course we do not want to do this very often ...