Thanks for paying attention to this issue! [root@router2 ~]# pstat -d ld acpi_nalloc ; date acpi_nalloc at 0xffffffff81e0bf68: 10762059 Sun Apr 5 12:49:02 EEST 2015
[root@router2 ~]# pstat -d ld acpi_nalloc ; date acpi_nalloc at 0xffffffff81e0bf68: 10762059 Sun Apr 5 12:50:41 EEST 2015 Also uploaded sendbug output there https://www.dropbox.com/s/g1lp3wcft2wriyg/sendbug.txt?dl=0 On Sun, Apr 5, 2015 at 12:16 AM, Ted Unangst <t...@tedunangst.com> wrote: > Evgeniy Sudyr wrote: >> How can I help identify this bug, so developers can fix it :) > > Run sudo pstat -d ld acpi_nalloc; then wait some time and run it again. Though > this looks like it could be a bug not in the OpenBSD ACPI code, but in the > interpreted AML code. > > Debugging this over email is probably going to be hard. But if you use > sendbug, it will include the output of acpidump, which may be helpful. > > >> >> On Sat, Apr 4, 2015 at 6:49 PM, Ted Unangst <t...@tedunangst.com> wrote: >> > Evgeniy Sudyr wrote: >> >> ACPI175742 18750K 18796K 78644K 572114 0 0 >> > >> > This looks rather high. I suspect a leak in the acpi code. > > -- -- With regards, Eugene Sudyr
