Bug #764

i got a core dump on vfsync_bp when building gnome.

Added by d.ubuntu almost 6 years ago. Updated over 3 years ago.

Status:Closed Start date:
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:-

Description

i got a core dump on vfsync_bp when building gnome. here is what
/var/log/messages says:

Aug 6 01:41:19 dhcppc1 kernel: Warning: vfsync_bp skipping dirty buffer
0xc216c400

Aug 6 01:56:28 dhcppc1 kernel: Warning: vfsync_bp skipping dirty buffer
0xc2022c00

Aug 6 02:09:41 dhcppc1 kernel: Warning: vfsync_bp skipping dirty buffer
0xc20d8400

Aug 6 02:10:12 dhcppc1 kernel: Warning: vfsync_bp skipping dirty buffer
0xc20d8400

Aug 6 02:23:51 dhcppc1 kernel: pid 15584 (conftest), uid 0: exited on signal
11 (core dumped)


Related todos

History

Updated by dillon almost 6 years ago

:i got a core dump on vfsync_bp when building gnome. here is what
:/var/log/messages says:

Those warnings are unrelated to the core dump.

:Aug 6 02:10:12 dhcppc1 kernel: Warning: vfsync_bp skipping dirty buffer
:0xc20d8400
:
:Aug 6 02:23:51 dhcppc1 kernel: pid 15584 (conftest), uid 0: exited on signal
:11 (core dumped)

-Matt
Matthew Dillon
<dillon@backplane.com>

Updated by d.ubuntu almost 6 years ago

What does the vfsync_bp skipping dirty buffer means?
"Matthew Dillon" <dillon@apollo.backplane.com> skrev i meddelandet
news:200708060627.l766RxIN015222@apollo.backplane.com...
>
> :i got a core dump on vfsync_bp when building gnome. here is what
> :/var/log/messages says:
>
> Those warnings are unrelated to the core dump.
>
> :Aug 6 02:10:12 dhcppc1 kernel: Warning: vfsync_bp skipping dirty buffer
> :0xc20d8400
> :
> :Aug 6 02:23:51 dhcppc1 kernel: pid 15584 (conftest), uid 0: exited on
> signal
> :11 (core dumped)
>
> -Matt
> Matthew Dillon
> <dillon@backplane.com>

Updated by tuxillo over 3 years ago

For the "kernel: Warning: vfsync_bp skipping dirty buffer ..." messages see:
http://leaf.dragonflybsd.org/mailarchive/users/2009-07/msg00037.html

The report is incomplete, the program coredump is on a conftest, probably during
configure stage in some package, and the report is unrelated to vfsync_bp as
Dillon said.

Closing this issue.

Also available in: Atom PDF