Re[2]: kmem_map too small: 3832475648 total allocated
Thu, 29 Apr 2010 16:20:32 -0500 письмо от "James R. Van Artsdalen" : > Андрей Смагин wrote: > > > panic: kmem_malloc(131072): kmem_map too small: 3832475648 total > > allocated > > > > > I open PR amd64/145654 with problem like it. Have you increasing Wired > > memory at buildworld ? > > > > No. This > > # while true > > do > > sysctl -A | grep wired > > make -j8 buildworld > > done > > is getting: > > vm.max_wired: 997427 > vm.max_wired: 997427 > vm.max_wired: 997427 > vm.max_wired: 997427 > vm.max_wired: 997427 > vm.max_wired: 997427 > vm.max_wired: 997427 > vm.max_wired: 997427 > vm.max_wired: 997427 > vm.max_wired: 997427 > vm.max_wired: 997427 > vm.max_wired: 997427 > > Is that the right variable to look at? strange - by "top" Wired memory now about 1.2Gbyte, but vm.max_wired: 330338 Also my system crashed after 3-5 buildworld's and kernels. usr/obj+usr/src - ~2GB size, 4GB of RAM - twice more than need to have all data for compilation in memory. > A friend of mine can duplicate your PR too. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
ifconfig msk0 up hang and eating 100%CPU
"ifconfig msk0 up" hang and I can't kill it, also ping any host via another working interface - ping hang. What I can do for debug it process ? FreeBSD 9.0-CURRENT #4: Wed Oct 27 01:00:31 MSD 2010 root@:/usr/obj/usr/src/sys/SAM amd64 >top last pid: 58489; load averages: 6.55, 4.98, 2.76 up 0+01:53:08 11:37:46 602 processes: 6 running, 594 sleeping, 1 zombie, 1 lock CPU: 0.2% user, 0.0% nice, 25.6% system, 0.3% interrupt, 73.9% idle Mem: 354M Active, 200M Inact, 765M Wired, 700K Cache, 76M Buf, 2622M Free Swap: PID USERNAMETHR PRI NICE SIZERES STATE C TIME WCPU COMMAND 57179 root 1 -320 14340K 1588K CPU11 8:29 100.00% ifconfig ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Strange hang HPET in current
In my box (amd64, current 20.oct.10 ) some time hang by 5-10 minutes with random subsystem, may hang disk access,network,very often tty. In most no output in log, sometimes with messages "calcru: .". After 5-10 minutes it continue work again. When I disabled HPET in bios - problem gone. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re[2]: ifconfig msk0 up hang and eating 100%CPU
Wed, 27 Oct 2010 11:52:18 +0400 письмо от "Ilya A. Arhipov" : > dmesg | grep msk > and procstat -kk pid > 27.10.10, 11:45, "Andrey Smagin" : > > "ifconfig msk0 up" hang and I can't kill it, also ping any host via another > working interface - ping hang. > >? What I can do for debug it process ? > >? > >? FreeBSD 9.0-CURRENT #4: Wed Oct 27 01:00:31 MSD 2010 > root@:/usr/obj/usr/src/sys/SAM? amd64 > >? > >? >top > >? last pid: 58489;? load averages:? 6.55,? 4.98,? > 2.76??? up > 0+01:53:08? 11:37:46 > >? 602 processes: 6 running, 594 sleeping, 1 zombie, 1 lock > >? CPU:? 0.2% user,? 0.0% nice, 25.6% system,? 0.3% interrupt, 73.9% idle > >? Mem: 354M Active, 200M Inact, 765M Wired, 700K Cache, 76M Buf, 2622M Free > >? Swap: > >? > >??? PID USERNAME??? THR PRI NICE?? SIZE??? RES STATE?? C?? TIME?? WCPU > COMMAND > >? 57179 root? 1 -32??? 0 14340K? 1588K CPU1??? 1?? 8:29 100.00% > ifconfig > >? > >? ___ > >? freebsd-current@freebsd.org mailing list > >? http://lists.freebsd.org/mailman/listinfo/freebsd-current > >? To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > >? > >? ran trafshow 5 times dmesg | grep msk msk0: promiscuous mode enabled msk0: promiscuous mode disabled msk0: promiscuous mode enabled msk0: promiscuous mode disabled msk0: promiscuous mode enabled msk0: promiscuous mode disabled msk0: promiscuous mode enabled msk0: promiscuous mode disabled msk0: promiscuous mode enabled msk0: promiscuous mode disabled ns# procstat -kk 57179 PIDTID COMM TDNAME KSTACK 57179 100366 ifconfig - ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
arp -nf list; work about 35 minutes
I have file with list of static ARP entries for about 65000 IPs. arp -nf list eating ~80% CPU and work very long time. It is a normal or something misconfigured ? FreeBSD-current from 5dec2010 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re[2]: About "panic: bufwrite: buffer is not busy???"
On week -current I have same problem, my box paniced every 2-15 min. I resolve problem by next steps - unplug network connectors from 2 intel em (82574L) cards. I think last time that mpd5 related panic, but mpd5 work with another re interface interated on MB. I think it may be em related panic, or em+mpd5. Wed, 16 Feb 2011 12:08:30 -0500 письмо от Andrew Boyer : > Moving this to -current and -stable and following up... > > Something is broken with coredumps on stable/8 amd64. I tried a vanilla > 8.2-RC3 and yesterday's csup of stable/8; neither can dump a core with 'sysctl > debug.kdb.panic=1'. > > For the 8.2-RC3 / amd64 / GENERIC install, I used the memstick image, > installed on ad7 (a 250GB SATA drive), used the default partition map, and set > dumpdev to AUTO. > > I added enough tracing to show that the second panic is due to the syncer > process flushing buffers to the other filesystems in parallel with the dump. > I've seen this panic and a similar one 'buffer not locked' coming from > ffs_write(). One time out of about 30 the core ran to completion, but slowly > (~1MB/sec). Other times the dump just locks up completely with no other > output. > > Does anyone know what might have changed to expose this problem? > > I don't ever see it under 7.1. > > Thanks, > Andrew > > On Feb 3, 2011, at 12:11 AM, Eugene Grosbein wrote: > > > On 02.02.2011 00:50, Gleb Smirnoff wrote: > > > >> E> Uptime: 8h3m51s > >> E> Dumping 4087 MB (3 chunks) > >> E> chunk 0: 1MB (150 pages) ... ok > >> E> chunk 1: 3575MB (915088 pages) 3559 3543panic: bufwrite: buffer is not > busy??? > >> E> cpuid = 3 > >> E> Uptime: 8h3m52s > >> E> Automatic reboot in 15 seconds - press a key on the console to abort > >> Can you add KDB_TRACE option to kernel? Your boxes for some reason can't > >> dump core, but with this option we will have at least trace. > > > > I see Mike Tancsa's box has "bufwrite: buffer is not busy???" problem too. > > Has anyone a thought how to fix generation of crashdumps? > > > > Eugene Grosbein > > > > > > ___ > > freebsd-...@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" > > -- > Andrew Boyer abo...@averesystems.com > > > > > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re[2]: About "panic: bufwrite: buffer is not busy???"
Sun, 20 Feb 2011 10:30:52 -0500 письмо от Mike Tancsa :
> On 2/20/2011 9:33 AM, Andrey Smagin wrote:
> > On week -current I have same problem, my box paniced every 2-15 min. I
> resolve problem by next steps - unplug network connectors from 2 intel em
> (82574L) cards. I think last time that mpd5 related panic, but mpd5 work with
> another re interface interated on MB. I think it may be em related panic, or
> em+mpd5.
>
> The latest panic I saw didnt have anything to do with em. Are you sure
> your crashes are because of the nic drive ?
I not shure crash because nic driver, I say only because my box after unplug 2
em nic's
have uptime from moment of unplug to right now moment. About all last week I
tried
understand source of panic. My box :
Phenom x4
12GB
2 re nic
2 em nic
through re0 em1 em2 work mpd5
re0 pptp client
em0 pppoe client
em1 l2tp client
> The latest I saw was on Friday.
>
> # kgdb /usr/obj/usr/src/sys/router/kernel.debug vmcore.11
> (kgdb) bt
> #0 doadump () at pcpu.h:231
> #1 0xc04a51f9 in db_fncall (dummy1=1, dummy2=0, dummy3=-106856,
> dummy4=0xc6b9696c "") at /usr/src/sys/ddb/db_command.c:548
> #2 0xc04a55f1 in db_command (last_cmdp=0xc096f73c, cmd_table=0x0,
> dopager=1) at /usr/src/sys/ddb/db_command.c:445
> #3 0xc04a574a in db_command_loop () at /usr/src/sys/ddb/db_command.c:498
> #4 0xc04a764d in db_trap (type=12, code=0) at
> /usr/src/sys/ddb/db_main.c:229
> #5 0xc068ba7e in kdb_trap (type=12, code=0, tf=0xc6b96b94) at
> /usr/src/sys/kern/subr_kdb.c:546
> #6 0xc088056f in trap_fatal (frame=0xc6b96b94, eva=52) at
> /usr/src/sys/i386/i386/trap.c:937
> #7 0xc0880830 in trap_pfault (frame=0xc6b96b94, usermode=0, eva=52) at
> /usr/src/sys/i386/i386/trap.c:859
> #8 0xc0880d4a in trap (frame=0xc6b96b94) at
> /usr/src/sys/i386/i386/trap.c:532
> #9 0xc086716c in calltrap () at /usr/src/sys/i386/i386/exception.s:166
> #10 0xc0657a16 in uihold (uip=0x0) at /usr/src/sys/kern/kern_resource.c:1248
> #11 0xc0654ec9 in crcopy (dest=0xce3ee800, src=0xce3ee600) at
> /usr/src/sys/kern/kern_prot.c:1873
> #12 0xc0654fd1 in crcopysafe (p=0xc90cc810, cr=0xce3ee800) at
> /usr/src/sys/kern/kern_prot.c:1950
> #13 0xc0656d7f in seteuid (td=0xc9196b80, uap=0xc6b96cec) at
> /usr/src/sys/kern/kern_prot.c:615
> #14 0xc06985ff in syscallenter (td=0xc9196b80, sa=0xc6b96ce4) at
> /usr/src/sys/kern/subr_trap.c:315
> #15 0xc0880884 in syscall (frame=0xc6b96d28) at
> /usr/src/sys/i386/i386/trap.c:1061
> #16 0xc08671d1 in Xint0x80_syscall () at
> /usr/src/sys/i386/i386/exception.s:264
> #17 0x0033 in ?? ()
>
> (kgdb) frame 10
> #10 0xc0657a16 in uihold (uip=0x0) at /usr/src/sys/kern/kern_resource.c:1248
> 1248{
> (kgdb) list
> 1243 * Place another refcount on a uidinfo struct.
> 1244 */
> 1245void
> 1246uihold(uip)
> 1247struct uidinfo *uip;
> 1248{
> 1249
> 1250refcount_acquire(&uip->ui_ref);
> 1251}
> 1252
> (kgdb) p *uip
> Cannot access memory at address 0x0
> (kgdb) p uip
> $1 = (struct uidinfo *) 0x0
> (kgdb)
>
> >
> >
> > Wed, 16 Feb 2011 12:08:30 -0500 письмо от Andrew Boyer
> :
> >
> >> Moving this to -current and -stable and following up...
> >>
> >> Something is broken with coredumps on stable/8 amd64. I tried a vanilla
> >> 8.2-RC3 and yesterday's csup of stable/8; neither can dump a core with
> 'sysctl
> >> debug.kdb.panic=1'.
> >>
> >> For the 8.2-RC3 / amd64 / GENERIC install, I used the memstick image,
> >> installed on ad7 (a 250GB SATA drive), used the default partition map, and
> set
> >> dumpdev to AUTO.
> >>
> >> I added enough tracing to show that the second panic is due to the syncer
> >> process flushing buffers to the other filesystems in parallel with the
> dump.
> >> I've seen this panic and a similar one 'buffer not locked' coming from
> >> ffs_write(). One time out of about 30 the core ran to completion, but
> slowly
> >> (~1MB/sec). Other times the dump just locks up completely with no other
> >> output.
> >>
> >> Does anyone know what might have changed to expose this problem?
> >>
> >> I don't ever see it under 7.1.
> >>
> >> Thanks,
> >> Andrew
> >>
> >> On Feb 3, 2011, at 12:11 AM, Eugene Grosbein wrote:
> >>
> >>> On 02.02.2011 00:50, Gleb Smirnoff wrote:
> >>>
> >>>> E> Uptime: 8h3m51s
> >>>> E> Dumping 4087 MB (3 chunks)
> >>>> E> chunk 0: 1MB (150 pages) ... ok
> >>>> E
current repeateble crash in 2 places
today current crash with loaded mpd5 1st place: ipwf_chk ipfw_check_hook pfil_run_hooks ip_output tcp_output repeated tcp_mtudisc~20 times tcp_ctlinput icmp_input ip_input swi_net intr_event_execute_handlers 2nd place flowtable_lookup flowteble_lookup_mbuf ip_output tcp_output ~ repeated tcp_mtudisc20 times tcp_ctlinput icmp_input ip_input netisr_dispatch_src ng_iface_rcvdata ng_apply_itemrepeated ng_snd_item 3 ng_pppoe_rcvdata_ether times ng_apply_item ng_snd_item ether_demux ether_input em_rxeof em_msix_rx inthr_event_execute_handlers ithread_loop ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
make installworld from r238247 -> r238610 break
Hi. make installworld can't be done. for success installworld need: mkdir /usr/share/examples/libusb20/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Current r250174 repeatable panic
Today current paniced after some minutes of network load. Kernel conf is GENERIC with added ROUTETABLES=16 option. Screenshoots http://vvtlan.ru/panic1.jpg http://vvtlan.ru/panic2.jpg . ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: panic in sctp_del_addr_from_vrf() ?
I have panic like your but in sctp_add_addr_to_vrf. I think need PR. My panic screenshoot http://vvtlan.ru/panic1.jpg and second one http://vvtlan.ru/panic2.jpg Суббота, 4 мая 2013, 20:55 +08:00 от kit : > got this panic when network interfaces were being unconfigured during system shutdown. has anyone seen this? should i file a PR? thanks kit test.yahoo.com dumped core - see /home/crash/vmcore.2 Sat May 4 20:43:55 MYT 2013 FreeBSD test.yahoo.com 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r250229: Sat May 4 20:30:17 MYT 2013 kt...@test.yahoo.com:/tmp/obj/usr/src/sys/SHUTTLE amd64 panic: page fault GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: . <118>Writing entropy file:. <118>. <118>Terminated <118>May 4 20:42:00 test syslogd: exiting on signal 15 Fatal trap 12: page fault while in kernel mode cpuid = 4; apic id = 04 fault virtual address = 0x8c fault code = supervisor read data, page not present instruction pointer = 0x20:0x8066e71c stack pointer = 0x28:0xff82187fb5d0 frame pointer = 0x28:0xff82187fb620 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 474 (wpa_supplicant) trap number = 12 panic: page fault cpuid = 4 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xff82187fb190 kdb_backtrace() at kdb_backtrace+0x39/frame 0xff82187fb240 panic() at panic+0x155/frame 0xff82187fb2c0 trap_fatal() at trap_fatal+0x37a/frame 0xff82187fb320 trap_pfault() at trap_pfault+0x257/frame 0xff82187fb3c0 trap() at trap+0x43a/frame 0xff82187fb510 calltrap() at calltrap+0x8/frame 0xff82187fb510 --- trap 0xc, rip = 0x8066e71c, rsp = 0xff82187fb5d0, rbp = 0xff82187fb620 --- sctp_del_addr_from_vrf() at sctp_del_addr_from_vrf+0x7c/frame 0xff82187fb620 rt_newaddrmsg_fib() at rt_newaddrmsg_fib+0x44/frame 0xff82187fb6e0 rtinit1() at rtinit1+0x57b/frame 0xff82187fb860 in_scrubprefix() at in_scrubprefix+0x376/frame 0xff82187fb900 rip_ctlinput() at rip_ctlinput+0x143/frame 0xff82187fb930 pfctlinput() at pfctlinput+0x5c/frame 0xff82187fb960 ifioctl() at ifioctl+0x7f2/frame 0xff82187fba20 kern_ioctl() at kern_ioctl+0x22e/frame 0xff82187fba90 sys_ioctl() at sys_ioctl+0x142/frame 0xff82187fbae0 amd64_syscall() at amd64_syscall+0x2b4/frame 0xff82187fbbf0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xff82187fbbf0 --- syscall (54, FreeBSD ELF64, sys_ioctl), rip = 0x80122c26a, rsp = 0x7fffdb18, rbp = 0x7fffdb90 --- Uptime: 4m55s ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > Отправлено из мобильной Почты Mail.Ru ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: panic in sctp_del_addr_from_vrf() ?
l_mtx protects so_gencnt, numopensockets, and the per-socket
* so_gencnt field.
*/
-static struct mtx so_global_mtx;
+static struct mtx_padalign so_global_mtx;
MTX_SYSINIT(so_global_mtx, &so_global_mtx, "so_glabel", MTX_DEF);
/*
Index: sys/net/if.c
===
--- sys/net/if.c (revision 250330)
+++ sys/net/if.c (working copy)
@@ -206,7 +206,7 @@
* also to stablize it over long-running ioctls, without introducing priority
* inversions and deadlocks.
*/
-struct rwlock ifnet_rwlock;
+struct rwlock_padalign ifnet_rwlock;
struct sx ifnet_sxlock;
/*
Index: sys/net/if_var.h
===
--- sys/net/if_var.h (revision 250330)
+++ sys/net/if_var.h (working copy)
@@ -191,9 +191,9 @@
void *if_unused[2];
void *if_afdata[AF_MAX];
int if_afdata_initialized;
- struct rwlock if_afdata_lock;
+ struct rwlock_padalign if_afdata_lock;
struct task if_linktask; /* task for link change events */
- struct rwlock if_addr_lock; /* lock to protect address lists */
+ struct rwlock_padalign if_addr_lock; /* lock to protect address
lists */
LIST_ENTRY(ifnet) if_clones; /* interfaces of a cloner */
TAILQ_HEAD(, ifg_list) if_groups; /* linked list of groups per if */
@@ -832,7 +832,7 @@
#ifdef _KERNEL
-extern struct rwlock ifnet_rwlock;
+extern struct rwlock_padalign ifnet_rwlock;
extern struct sx ifnet_sxlock;
#define IFNET_LOCK_INIT() do {
\
Index: sys/net/if_llatbl.c
===
--- sys/net/if_llatbl.c (revision 250330)
+++ sys/net/if_llatbl.c (working copy)
@@ -67,7 +67,7 @@
static void vnet_lltable_init(void);
-struct rwlock lltable_rwlock;
+struct rwlock_padalign lltable_rwlock;
RW_SYSINIT(lltable_rwlock, &lltable_rwlock, "lltable_rwlock");
/*
Index: sys/net/if_llatbl.h
===
--- sys/net/if_llatbl.h (revision 250330)
+++ sys/net/if_llatbl.h (working copy)
@@ -43,7 +43,7 @@
struct llentry;
LIST_HEAD(llentries, llentry);
-extern struct rwlock lltable_rwlock;
+extern struct rwlock_padalign lltable_rwlock;
#define LLTABLE_RLOCK() rw_rlock(&lltable_rwlock)
#define LLTABLE_RUNLOCK() rw_runlock(&lltable_rwlock)
#define LLTABLE_WLOCK() rw_wlock(&lltable_rwlock)
Понедельник, 6 мая 2013, 20:50 -07:00 от kit :
>ah, it's should be fixed now as per r250300. changes that caused this panic
>have been backed out.
>
>kit
>
>--- On Tue, 5/7/13, kit < kt...@acm.org > wrote:
>
>From: kit < kt...@acm.org >
>Subject: Re: panic in sctp_del_addr_from_vrf() ?
>To: "Andrey Smagin" < samsp...@mail.ru >, freebsd-current@freebsd.org
>Date: Tuesday, May 7, 2013, 8:59 AM
>
>not sure why. for my case, padaligining one of the rwlocks solved it.
>you may want to try the patch attached and see if it works for you.
>
>anyway, i'm filing a PR if nobody has done so already.
>
>thanks
>kit
>
>On Sat, May 04, 2013 at 09:22:23PM +0400, Andrey Smagin wrote:
>>
>> I have panic like your but in sctp_add_addr_to_vrf. I think need PR. My
>> panic screenshoot http://vvtlan.ru/panic1.jpg and second one
>> http://vvtlan.ru/panic2.jpg
>>
>> Суббота, 4 мая 2013, 20:55 +08:00 от kit < kt...@acm.org >:
>> >
>> got this panic when network interfaces were being unconfigured during
>> system shutdown. has anyone seen this? should i file a PR?
>>
>> thanks
>> kit
>>
>> test.yahoo.com dumped core - see /home/crash/vmcore.2
>>
>> Sat May 4 20:43:55 MYT 2013
>>
>> FreeBSD test.yahoo.com 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r250229: Sat May
>> 4 20:30:17 MYT 2013 kt...@test.yahoo.com:/tmp/obj/usr/src/sys/SHUTTLE
>> amd64
>>
>> panic: page fault
>>
>> GNU gdb 6.1.1 [FreeBSD]
>> Copyright 2004 Free Software Foundation, Inc.
>> GDB is free software, covered by the GNU General Public License, and you are
>> welcome to change it and/or distribute copies of it under certain conditions.
>> Type "show copying" to see the conditions.
>> There is absolutely no warranty for GDB. Type "show warranty" for details.
>> This GDB was configured as "amd64-marcel-freebsd"...
>>
>> Unread portion of the kernel message buffer:
>> .
>> <118>Writing entropy file:.
>> <118>.
>> <118>Terminated
>> <118>May 4 20:42:00 test syslogd: exiting on signal 15
>>
>> Fatal trap 12: pag
2 day GENERIC-current eat 2 CPU core at 100%
I upgraded 2 day ago from 2010-current box on Intel D525MW. System very slow down after that. kern.hz=50 in systat -vmstat - 140hpet interrupts/s at top 25% in interrupts 25% in system because hyperthreading system found 4 cpu.___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re[2]: 2 day GENERIC-current eat 2 CPU core at 100%
vmstat -i interrupt total rate irq16: uhci3 205 0 irq20: hpet0 147924380 1126 irq23: uhci0 ehci0 522517 3 total148447102 1130 Tue, 7 Jun 2011 10:34:01 +0200 письмо от Hans Petter Selasky : > On Tuesday 07 June 2011 10:09:47 Andrey Smagin wrote: > > I upgraded 2 day ago from 2010-current box on Intel D525MW. > > System very slow down after that. > > kern.hz=50 > > in systat -vmstat - 140hpet interrupts/s > > at top 25% in interrupts 25% in system > > because hyperthreading system found 4 cpu. > > What does vmstat -i output? > > --HPS > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re[2]: 2 day GENERIC-current eat 2 CPU core at 100%
wak 3 3 100 17084 frevn pdpgs intrn Disks md8 da0 pass0121076 wire KB/t 0,00 0,00 0,00 32228 act tps 0 0 0790700 inact MB/s 0,00 0,00 0,00 9560 cache %busy 0 0 0 42076 free Wed, 08 Jun 2011 20:34:42 +0300 письмо от Alexander Motin : > On 07.06.2011 20:12, Andrey Smagin wrote: > > vmstat -i > > interrupt total rate > > irq16: uhci3 205 0 > > irq20: hpet0 147924380 1126 > > irq23: uhci0 ehci0 522517 3 > > total148447102 1130 > > > > Tue, 7 Jun 2011 10:34:01 +0200 письмо от Hans Petter > Selasky: > > > >> On Tuesday 07 June 2011 10:09:47 Andrey Smagin wrote: > >>> I upgraded 2 day ago from 2010-current box on Intel D525MW. > >>> System very slow down after that. > >>> kern.hz=50 > >>> in systat -vmstat - 140hpet interrupts/s > >>> at top 25% in interrupts 25% in system > >>> because hyperthreading system found 4 cpu. > >> > >> What does vmstat -i output? > > Send me please full verbose dmesg and output of the `sysctl > kern.eventtimer` and `sysctl kern.timecounter`. > > Try to switch to another timer: > sysctl kern.eventtimer.timer=LAPIC > > Try to switch to periodic timers (instead): > sysctl kern.eventtimer.periodic=1 > > -- > Alexander Motin > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re[2]: 2 day GENERIC-current eat 2 CPU core at 100%
Great thanx ! It working ! :) Thu, 09 Jun 2011 19:40:18 +0300 письмо от Alexander Motin : > Andrey Smagin wrote: > > Hi, yesterday I tried switch event timer on i8254 - it do nothing. > > I disabled hyperthreading - now eat from 50% to 100% > > All dmesg is lines: > > (noperiph:ata3:0:-1:-1): rescan already queued > > (noperiph:ata3:0:-1:-1): rescan already queued > > (noperiph:ata2:0:-1:-1): rescan already queued > > (noperiph:ata3:0:-1:-1): rescan already queued > > (noperiph:ata3:0:-1:-1): rescan already queued > > > > I boot FreeBSD from USB with no ATA - may be it is. > > These messages are not what I expected to see, but they tell me that > your problem may be SATA related. I've got the same Intel D525MW board > and think reproduced the problem. I hope I've even fixed it. :) Retry > please with fresh CURRENT sources or at least with this patch applied: > http://svn.freebsd.org/changeset/base/222897 > > > Wed, 08 Jun 2011 20:34:42 +0300 письмо от Alexander Motin > > : > >> On 07.06.2011 20:12, Andrey Smagin wrote: > >>> vmstat -i > >>> interrupt total rate > >>> irq16: uhci3 205 0 > >>> irq20: hpet0 147924380 1126 > >>> irq23: uhci0 ehci0 522517 3 > >>> total148447102 1130 > >>> > >>> Tue, 7 Jun 2011 10:34:01 +0200 письмо от Hans Petter > >> Selasky: > >>>> On Tuesday 07 June 2011 10:09:47 Andrey Smagin wrote: > >>>>> I upgraded 2 day ago from 2010-current box on Intel D525MW. > >>>>> System very slow down after that. > >>>>> kern.hz=50 > >>>>> in systat -vmstat - 140hpet interrupts/s > >>>>> at top 25% in interrupts 25% in system > >>>>> because hyperthreading system found 4 cpu. > >>>> What does vmstat -i output? > >> Send me please full verbose dmesg and output of the `sysctl > >> kern.eventtimer` and `sysctl kern.timecounter`. > >> > >> Try to switch to another timer: > >> sysctl kern.eventtimer.timer=LAPIC > >> > >> Try to switch to periodic timers (instead): > >> sysctl kern.eventtimer.periodic=1 > > -- > Alexander Motin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
AX88772A AX88772B chipset differences?
I have card based on AX88772B. I tried patch axe driver for vendor and device IDs. card detected, set up link, but no data received. What else need for patch in this driver ? Anybody have datasheet ? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re[2]: AX88772A AX88772B chipset differences?
13 июля 2011, 04:07 от YongHyeon PYUN : > On Thu, Jun 30, 2011 at 10:19:14AM -0700, YongHyeon PYUN wrote: > > On Thu, Jun 30, 2011 at 02:44:48PM +0400, Andrey Smagin wrote: > > > I have card based on AX88772B. I tried patch axe driver for vendor and > device IDs. card detected, set up link, but no data received. What else need > for patch in this driver ? Anybody have datasheet ? > > > > ASIX requires a login account to get the data sheet so it's not > > publicly available to open source developers. > > AFAIK the difference between AX88772A and AX88772B is IPv4/IPv6 > > checksum offloading support of AX88772B. The introduction of > > checksum offloading means they might have changed its RX header > > format which in turn makes current RX handler to not work. The > > other difference would be more advanced power saving used in > > AX8877B but it wouldn't be much difference to axe(4) driver once > > PHY is correctly woken in initialization phase. > > Could you show me your diff and verbose boot output to know PHY > > model and EEPROM data? > > I have a minimal patch for AX88772B. It requires more work to > support TX/RX checksum offloading, flow-control and power saving > but attached patch would be enough for most cases. > Let me know whether it works or not. Great thanx !!! It work but I not tested under heavy load. Only ping and some Mbytes via nfs. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
r224468 amd64 kernel panic on boot: No init found
Please help! Can't load system after update on r224468 mount partition is UFS, no startup settings changed, no CONF file changed. make buildworld buildkernel installworld installkernel now I loaded old r221725. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r224468 amd64 kernel panic on boot: No init found
Sorry for panic. I have another HDD with partition s1a, after update, HDD renumerated. vfs.root.mountfrom in loader.conf solved my problem 28 июля 2011, 01:02 от Andrey Smagin : > Please help! Can't load system after update on r224468 > mount partition is UFS, no startup settings changed, > no CONF file changed. > make buildworld buildkernel installworld installkernel > now I loaded old r221725. > ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
mbuf leak in 802.11 ?
My Asus EEE PC 900 hang after some hour of work. I found that all mbufs in use. If I in X - systam hang. I tried connect USB WiFi - if_run, and after some hour system also hang. I tried connect via wire ae0 interface - system work stable for now. -- Почта@Mail.Ru в твоем мобильном! Просто зайди с телефона на m.mail.ru___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: mbuf leak in 802.11 ?
system is FreeBSD 9.0-CURRENT #0 r224188___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: mbuf leak in 802.11 ?
Other WiFi NIC is run0: MAC/BBP RT2872 (rev 0x0202), RF RT2720 (MIMO 1T2R) It take from 20-600 minutes. At morning after night I found it always hang. Under WiFi load uptime shorter. Also in dmesg many messages: in_arp: source hardware address is multicast. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Kernel panic "rtfree 2"
Before all upgrade system never crash. After upgrade system month ago happens every day Kernel panic "rtfree 2" at rtfree route_output sosend_generic soo_write dofilewrite kernwrite write syscallenter syscall Xfast_syscall Now I upgraded to FreeBSD 9.0-BETA1 #32 r224760M and problem exist. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Kernel panic "rtfree 2"
12 августа 2011, 16:31 от Kip Macy : > It would help to know your configuration. Also, can you furnish us with a > core? > This is my kernel conf: cpu HAMMER ident SAM makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption options INET # InterNETworking options INET6 # IPv6 communications protocols options SCTP # Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options UFS_GJOURNAL # Enable gjournal-based UFS journaling options MD_ROOT # MD is a potential root device options NFSCL # New Network Filesystem Client options NFSD # New Network Filesystem Server options NFSLOCKD # Network Lock Manager options NFS_ROOT # NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_FREEBSD32 # Compatible with i386 binaries options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options COMPAT_FREEBSD7 # Compatible with FreeBSD7 options SCSI_DELAY=1001 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options STACK # stack(9) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options PRINTF_BUFR_SIZE=128 # Prevent printf output being interspersed. options KBD_INSTALL_CDEV # install a CDEV entry in /dev options HWPMC_HOOKS # Necessary kernel hooks for hwpmc(4) options AUDIT # Security event auditing options MAC # TrustedBSD MAC Framework options INCLUDE_CONFIG_FILE # Include this file in kernel options KDB # Enable kernel debugger support. options DDB # Support DDB. options GDB # Support remote GDB. options DEADLKRES # Enable the deadlock resolver options MALLOC_DEBUG_MAXZONES=8 # Separate malloc(9) zones options SMP # Symmetric MultiProcessor Kernel options LIBICONV options MSDOSFS_ICONV options CD9660_ICONV options IPFIREWALL options DUMMYNET options IPDIVERT options MROUTING options RADIX_MPATH options ALTQ options ALTQ_CBQ options ALTQ_RED options ALTQ_RIO options ALTQ_HFSC options ALTQ_CDNR options ALTQ_PRIQ options LIBALIAS options IPFIREWALL_FORWARD options IPFIREWALL_NAT options ROUTETABLES=16 options DEVICE_POLLING > On Fri, Aug 12, 2011 at 9:02 AM, Andrey Smagin wrote: > > Before all upgrade system never crash. > > After upgrade system month ago happens every day Kernel panic "rtfree 2" at > > rtfree > > route_output > > sosend_generic > > soo_write > > dofilewrite > > kernwrite > > write > > syscallenter > > syscall > > Xfast_syscall > > > > Now I upgraded to FreeBSD 9.0-BETA1 #32 r224760M and problem exist.___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re[2]: Kernel panic "rtfree 2"
12 августа 2011, 19:05 от Luiz Otavio O Souza : On Aug 12, 2011, at 11:32 AM, Andrey Smagin wrote: > > 12 августа 2011, 16:31 от Kip Macy : >> It would help to know your configuration. Also, can you furnish us with a >> core? >> > This is my kernel conf: > > cpu HAMMER > ident SAM > [snip] > options RADIX_MPATH Can you try it without RADIX_MPATH ?Ok, I will try without RADIX_MPATH Are you sure this problem does not exist before ? (and are you using the same kernel config as before ?)Absolutely no. Do you have any kind of routing daemon running on your system ?I have mpd5 with 4 connection to different ISP, and 4 gif tunnels to another networks. I have sh script wich use commands to change routing tables and commands to change IPFW configuration. I have no another known for me daemons wich can change routing table. This looks like the same problem reported on PR kern/155177.Yes like my problem. Unfortunately the reporter don't have the system running anymore to provide additional information. Regards, Luiz ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re[2]: Kernel panic "rtfree 2"
17 августа 2011, 04:02 от "Li, Qing" : > Hi, > > Could you please let me know if the patch fixes your crash problem ? > > Thanks, > > --Qing > > > -Original Message- > > From: Li, Qing > > Sent: Friday, August 12, 2011 6:29 PM > > To: Li, Qing; Luiz Otavio O Souza; Andrey Smagin > > Cc: freebsd-current@freebsd.org > > Subject: RE: Kernel panic "rtfree 2" > > > > Hi, > > > > Please re-enable RADIX_MPATH option in your kernel config file, and > > try the following patch: > > > > http://people.freebsd.org/~qingli/radix_mpath.c.diff > > > > and let me know if it works out for you. > > > > I performed very limited testing. > > > > Thanks, > > > > --Qing > > > > Thanks, Your patch resolve problem, I have 3 day uptime without panic ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
