from:"bugzilla\-noreply"

[Bug 228536] x11/nvidia-driver: 11.2-BETA3 - fails to operate correctly

2019-07-22 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228536

zain david  changed:

   What|Removed |Added

 CC||omarande...@gmail.com

--- Comment #14 from zain david  ---
great work.
http://www.winmilliongame.com
http://www.gtagame100.com
http://www.subway-game.com
http://www.zumagame100.com

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 227323] [patch] [spi] sys/modules/spi/mx25l cannot be built outside of kernel build environment

2019-07-10 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227323

Eugene Grosbein  changed:

   What|Removed |Added

   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2391
   ||19

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 193361] [panic] panic pagedaemon

2019-05-16 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193361

Gleb Popov  changed:

   What|Removed |Added

 CC||arr...@freebsd.org
 Resolution|--- |Overcome By Events
 Status|New |Closed

--- Comment #3 from Gleb Popov  ---
This FreeBSD version is not supported anymore, and the bug report doesn't seem
to actually contain any useful information.

Closing it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 193366] [panic] panic vnlru

2019-05-16 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193366

Konstantin Belousov  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |Overcome By Events
 CC||k...@freebsd.org

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 193366] [panic] panic vnlru

2019-05-16 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193366

Gleb Popov  changed:

   What|Removed |Added

 CC||arr...@freebsd.org

--- Comment #1 from Gleb Popov  ---
This FreeBSD version is not supported anymore, and the bug report doesn't seem
to actually contain any useful information. Should we close it?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 229694] [zfs] unkillable "zpool scrub" in [tx->tx_sync_done_cv] state for damaged data

2019-02-13 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229694

--- Comment #5 from Andriy Gapon  ---
(In reply to Eugene Grosbein from comment #3)
5 101937 zfskern txg_thread_entermi_switch+0xc5
sleepq_wait+0x2c _cv_wait+0x160 zio_resume_wait+0x4b spa_sync+0xd46
txg_sync_thread+0x25e fork_exit+0x75 fork_trampoline+0xe 

 3249 101681 zpool   -   mi_switch+0xc5
sleepq_wait+0x2c _cv_wait+0x160 txg_wait_synced+0xa5 dsl_sync_task_common+0x219
dsl_sync_task+0x14 dsl_scan+0x9e zfs_ioc_pool_scan+0x5a zfsdev_ioctl+0x6c2
devfs_ioctl_f+0x12d kern_ioctl+0x212 sys_ioctl+0x15c amd64_syscall+0x25c
fast_syscall_common+0x101

So, unfortunately, this is how ZFS works now.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 193386] [panic] resource_list_alloc: resource entry is busy

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193386

--- Comment #1 from Rodney W. Grimes  ---
Please do not put bugs on stable@, current@, hackers@, etc

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 193364] [panic] ffs_blkfree_cg: freeing free block

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193364

Rodney W. Grimes  changed:

   What|Removed |Added

 CC|sta...@freebsd.org  |

--- Comment #5 from Rodney W. Grimes  ---
Please do not put bugs on stable@, current@, hackers@, etc

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 229694] [zfs] unkillable "zpool scrub" in [tx->tx_sync_done_cv] state for damaged data

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229694

--- Comment #4 from Rodney W. Grimes  ---
Please do not put bugs on stable@, current@, hackers@, etc

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 230620] "install -d" issue

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230620

Rodney W. Grimes  changed:

   What|Removed |Added

   Assignee|sta...@freebsd.org  |b...@freebsd.org

--- Comment #3 from Rodney W. Grimes  ---
Please do not put bugs on stable@, current@, hackers@, etc
Placing this bug back on bugs@ to be triaged properly to a technical list

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 169898] ifconfig(8) fails to set MTU on multiple interfaces.

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169898

Rodney W. Grimes  changed:

   What|Removed |Added

 CC|sta...@freebsd.org  |rgri...@freebsd.org

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 169898] ifconfig(8) fails to set MTU on multiple interfaces.

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169898

Rodney W. Grimes  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|n...@freebsd.org

--- Comment #3 from Rodney W. Grimes  ---
Please do not put bugs on stable@, current@, hackers@, etc
Placing this bug on net@ as was done before eadler reset it

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 221146] [ixgbe] Problem with second laggport

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

Rodney W. Grimes  changed:

   What|Removed |Added

 CC|sta...@freebsd.org  |

--- Comment #25 from Rodney W. Grimes  ---
Please do not put bugs on stable@, current@, hackers@, etc

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 213903] Kernel crashes from turnstile_broadcast (/usr/src/sys/kern/subr_turnstile.c:837)

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903

Rodney W. Grimes  changed:

   What|Removed |Added

 CC|sta...@freebsd.org  |

--- Comment #57 from Rodney W. Grimes  ---
Please do not put bugs on stable@, current@, hackers@, etc

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213

Rodney W. Grimes  changed:

   What|Removed |Added

   Assignee|sta...@freebsd.org  |b...@freebsd.org

--- Comment #38 from Rodney W. Grimes  ---
Please do not put bugs on stable@, current@, hackers@, etc
Placing this bug back on bugs@ to be triaged properly to a technical list

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 193360] [panic] [syscons] random syscons panic

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193360

Rodney W. Grimes  changed:

   What|Removed |Added

 CC|sta...@freebsd.org  |

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 235683] [zfs] Panic during data access or scrub on 12.0-STABLE r343904 (blkptr at DVA 0 has invalid OFFSET)

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235683

Rodney W. Grimes  changed:

   What|Removed |Added

 CC|sta...@freebsd.org  |rgri...@freebsd.org

--- Comment #1 from Rodney W. Grimes  ---
Please do not put bugs on stable@, current@, hackers@, etc

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 221376] 12.0-RELEASE amd64: any kernel fail to boot - freezes just after run kernel

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221376

Rodney W. Grimes  changed:

   What|Removed |Added

 CC||rgri...@freebsd.org
   Assignee|sta...@freebsd.org  |b...@freebsd.org

--- Comment #6 from Rodney W. Grimes  ---
Please do not put bugs on stable@, current@, hackers@, etc
Placing this bug back on bugs@ to be triaged properly to a technical list

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 233006] [regression] [patch] bsdtar aborts creation of archive on ENOENT

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233006

Rodney W. Grimes  changed:

   What|Removed |Added

 CC|sta...@freebsd.org  |

--- Comment #16 from Rodney W. Grimes  ---
Please do not put bugs on stable@, current@, hackers@, etc

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 235684] security/ipsec-tools kernel panic

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235684

Rodney W. Grimes  changed:

   What|Removed |Added

 CC|sta...@freebsd.org  |

--- Comment #15 from Rodney W. Grimes  ---
Please do not put bugs on stable@, current@, hackers@, etc

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 233006] [regression] [patch] bsdtar aborts creation of archive on ENOENT

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233006

--- Comment #15 from commit-h...@freebsd.org ---
A commit references this bug:

Author: mm
Date: Tue Feb 12 23:24:47 UTC 2019
New revision: 344065
URL: https://svnweb.freebsd.org/changeset/base/344065

Log:
  MFV r344063:
  Sync libarchive with vendor.

  Relevant vendor changes:
PR #1085: Fix a null pointer dereference bug in zip writer
PR #1110: ZIP reader added support for XZ, LZMA, PPMD8 and BZIP2
  decopmpression
PR #1116: Add support for 64-bit ar format
PR #1120: Fix a 7zip crash [1] and a ISO9660 infinite loop [2]
PR #1125: RAR5 reader - fix an invalid read and a memory leak
PR #1131: POSIX reader - do not fail when tree_current_lstat() fails
  due to ENOENT [3]
PR #1134: Delete unnecessary null pointer checks before calls of free()
OSS-Fuzz 10843: Force intermediate to uint64_t to make UBSAN happy.
OSS-Fuzz 11011: Avoid buffer overflow in rar5 reader

  PR:   233006 [3]
  Security: CVE-2019-119 [1], CVE-2019-120 [2]
  MFC after:2 weeks

Changes:
_U  head/contrib/libarchive/
  head/contrib/libarchive/cpio/test/test_option_t.c
  head/contrib/libarchive/libarchive/archive_acl.c
  head/contrib/libarchive/libarchive/archive_entry.c
  head/contrib/libarchive/libarchive/archive_pack_dev.c
  head/contrib/libarchive/libarchive/archive_ppmd8.c
  head/contrib/libarchive/libarchive/archive_ppmd8_private.h
  head/contrib/libarchive/libarchive/archive_read_disk_posix.c
  head/contrib/libarchive/libarchive/archive_read_open_file.c
  head/contrib/libarchive/libarchive/archive_read_support_format_7zip.c
  head/contrib/libarchive/libarchive/archive_read_support_format_ar.c
  head/contrib/libarchive/libarchive/archive_read_support_format_cpio.c
  head/contrib/libarchive/libarchive/archive_read_support_format_iso9660.c
  head/contrib/libarchive/libarchive/archive_read_support_format_rar5.c
  head/contrib/libarchive/libarchive/archive_read_support_format_xar.c
  head/contrib/libarchive/libarchive/archive_read_support_format_zip.c
  head/contrib/libarchive/libarchive/archive_write_disk_posix.c
  head/contrib/libarchive/libarchive/archive_write_disk_set_standard_lookup.c
  head/contrib/libarchive/libarchive/archive_write_set_format_ar.c
  head/contrib/libarchive/libarchive/archive_write_set_format_cpio.c
  head/contrib/libarchive/libarchive/archive_write_set_format_cpio_newc.c
  head/contrib/libarchive/libarchive/archive_write_set_format_gnutar.c
  head/contrib/libarchive/libarchive/archive_write_set_format_shar.c
  head/contrib/libarchive/libarchive/archive_write_set_format_ustar.c
  head/contrib/libarchive/libarchive/archive_write_set_format_v7tar.c
  head/contrib/libarchive/libarchive/archive_write_set_format_zip.c
  head/contrib/libarchive/libarchive/test/test_compat_pax_libarchive_2x.c
 
head/contrib/libarchive/libarchive/test/test_compat_pax_libarchive_2x.tar.Z.uu
  head/contrib/libarchive/libarchive/test/test_read_format_zip.c
  head/contrib/libarchive/libarchive/test/test_read_format_zip_bzip2.zipx.uu
 
head/contrib/libarchive/libarchive/test/test_read_format_zip_bzip2_multi.zipx.uu
  head/contrib/libarchive/libarchive/test/test_read_format_zip_lzma.zipx.uu
 
head/contrib/libarchive/libarchive/test/test_read_format_zip_lzma_multi.zipx.uu
  head/contrib/libarchive/libarchive/test/test_read_format_zip_ppmd8.zipx.uu
 
head/contrib/libarchive/libarchive/test/test_read_format_zip_ppmd8_multi.zipx.uu
  head/contrib/libarchive/libarchive/test/test_read_format_zip_xz_multi.zipx.uu
  head/contrib/libarchive/test_utils/test_main.c
  head/lib/libarchive/Makefile
  head/lib/libarchive/tests/Makefile

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 235684] security/ipsec-tools kernel panic

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235684

--- Comment #14 from Andrey V. Elsukov  ---
(In reply to Sergey Anokhin from comment #13)
> (In reply to Andrey V. Elsukov from comment #11)
> 
> I'd preferred to try to rebuild kernel if it's no difference between turning
> off VIMAGE from kernel config and applying patch because kernel building
> more faster then "world" building. As far as I understand, you are propose
> patch for "world" component, right?

No, the patch is for kernel.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 235684] security/ipsec-tools kernel panic

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235684

--- Comment #13 from Sergey Anokhin  ---
(In reply to Andrey V. Elsukov from comment #11)

I'd preferred to try to rebuild kernel if it's no difference between turning
off VIMAGE from kernel config and applying patch because kernel building more
faster then "world" building. As far as I understand, you are propose patch for
"world" component, right?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 235684] security/ipsec-tools kernel panic

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235684

--- Comment #12 from Sergey Anokhin  ---
(In reply to Andrey V. Elsukov from comment #9)

Sure, now I'm building kernel without VIMAGE. I'll let you know about testing
result

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 233006] [regression] [patch] bsdtar aborts creation of archive on ENOENT

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233006

--- Comment #14 from commit-h...@freebsd.org ---
A commit references this bug:

Author: mm
Date: Tue Feb 12 22:29:45 UTC 2019
New revision: 344063
URL: https://svnweb.freebsd.org/changeset/base/344063

Log:
  Update vendor/libarchive/dist to git 31c0a517c91f44717a04db8b075cadda83d8

  Relevant vendor changes:
PR #1085: Fix a null pointer dereference bug in zip writer
PR #1110: ZIP reader added support for XZ, LZMA, PPMD8 and BZIP2
  decopmpression
PR #1116: Add support for 64-bit ar format
PR #1120: Fix a 7zip crash [1] and a ISO9660 infinite loop [2]
PR #1125: RAR5 reader - fix an invalid read and a memory leak
PR #1131: POSIX reader - do not fail when tree_current_lstat() fails
  due to ENOENT [3]
PR #1134: Delete unnecessary null pointer checks before calls of free()
OSS-Fuzz 10843: Force intermediate to uint64_t to make UBSAN happy.
OSS-Fuzz 11011: Avoid buffer overflow in rar5 reader

  PR:   233006 [3]
  Security: CVE-2019-119 [1], CVE-2019-120 [2]

Changes:
  vendor/libarchive/dist/.cirrus.yml
  vendor/libarchive/dist/.travis.yml
  vendor/libarchive/dist/CMakeLists.txt
  vendor/libarchive/dist/Makefile.am
  vendor/libarchive/dist/build/ci/
  vendor/libarchive/dist/build/ci/build.sh
  vendor/libarchive/dist/build/ci/cirrus_ci.sh
  vendor/libarchive/dist/build/ci/test_driver
  vendor/libarchive/dist/build/ci_build.sh
  vendor/libarchive/dist/build/ci_test_driver
  vendor/libarchive/dist/contrib/shar/tree.c
  vendor/libarchive/dist/cpio/test/test_option_t.c
  vendor/libarchive/dist/libarchive/CMakeLists.txt
  vendor/libarchive/dist/libarchive/archive_acl.c
  vendor/libarchive/dist/libarchive/archive_disk_acl_sunos.c
  vendor/libarchive/dist/libarchive/archive_entry.c
  vendor/libarchive/dist/libarchive/archive_pack_dev.c
  vendor/libarchive/dist/libarchive/archive_ppmd8.c
  vendor/libarchive/dist/libarchive/archive_ppmd8_private.h
  vendor/libarchive/dist/libarchive/archive_read_disk_posix.c
  vendor/libarchive/dist/libarchive/archive_read_open_file.c
  vendor/libarchive/dist/libarchive/archive_read_support_format_7zip.c
  vendor/libarchive/dist/libarchive/archive_read_support_format_ar.c
  vendor/libarchive/dist/libarchive/archive_read_support_format_cpio.c
  vendor/libarchive/dist/libarchive/archive_read_support_format_iso9660.c
  vendor/libarchive/dist/libarchive/archive_read_support_format_rar5.c
  vendor/libarchive/dist/libarchive/archive_read_support_format_xar.c
  vendor/libarchive/dist/libarchive/archive_read_support_format_zip.c
  vendor/libarchive/dist/libarchive/archive_write_disk_posix.c
  vendor/libarchive/dist/libarchive/archive_write_disk_set_standard_lookup.c
  vendor/libarchive/dist/libarchive/archive_write_disk_windows.c
  vendor/libarchive/dist/libarchive/archive_write_set_format_ar.c
  vendor/libarchive/dist/libarchive/archive_write_set_format_cpio.c
  vendor/libarchive/dist/libarchive/archive_write_set_format_cpio_newc.c
  vendor/libarchive/dist/libarchive/archive_write_set_format_gnutar.c
  vendor/libarchive/dist/libarchive/archive_write_set_format_shar.c
  vendor/libarchive/dist/libarchive/archive_write_set_format_ustar.c
  vendor/libarchive/dist/libarchive/archive_write_set_format_v7tar.c
  vendor/libarchive/dist/libarchive/archive_write_set_format_zip.c
  vendor/libarchive/dist/libarchive/test/CMakeLists.txt
  vendor/libarchive/dist/libarchive/test/test_compat_pax_libarchive_2x.c
  vendor/libarchive/dist/libarchive/test/test_compat_pax_libarchive_2x.tar.Z.uu
  vendor/libarchive/dist/libarchive/test/test_read_format_zip.c
  vendor/libarchive/dist/libarchive/test/test_read_format_zip_bzip2.zipx.uu
 
vendor/libarchive/dist/libarchive/test/test_read_format_zip_bzip2_multi.zipx.uu
  vendor/libarchive/dist/libarchive/test/test_read_format_zip_lzma.zipx.uu
 
vendor/libarchive/dist/libarchive/test/test_read_format_zip_lzma_multi.zipx.uu
  vendor/libarchive/dist/libarchive/test/test_read_format_zip_ppmd8.zipx.uu
 
vendor/libarchive/dist/libarchive/test/test_read_format_zip_ppmd8_multi.zipx.uu
  vendor/libarchive/dist/libarchive/test/test_read_format_zip_xz_multi.zipx.uu
  vendor/libarchive/dist/test_utils/test_main.c

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 235684] security/ipsec-tools kernel panic

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235684

--- Comment #11 from Andrey V. Elsukov  ---
Created attachment 201968
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=201968=edit
Proposed patch

Also, you can test this patch instead, it should fix panic with VIMAGE option.
The problem is due to introduced deferred PCB destroying via epoch_call().
Since this code is executed from gtaskqueue, it has no VNET context.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 235684] security/ipsec-tools kernel panic

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235684

--- Comment #10 from Sergey Anokhin  ---
(In reply to Jan Bramkamp from comment #6)

Will it ok?

(pts/1)[root@server:~]# sysctl kern.maxssiz=1073741824
kern.maxssiz: 536870912 -> 1073741824
(pts/1)[root@server:~]# /usr/local/etc/rc.d/racoon onestart
Starting racoon.
(pts/1)[root@server:~]# /usr/local/etc/rc.d/racoon onestop
Stopping racoon.
Waiting for PIDS: 5662

kernel panic

btw, I've noticed that kernel panic during stopping racoon.

# kgdb kernel /var/crash/vmcore.last
GNU gdb (GDB) 8.2.1 [GDB v8.2.1 for FreeBSD]
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-portbld-freebsd12.0".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from kernel...Reading symbols from
/usr/obj/usr/src/amd64.amd64/sys/SERVER/kernel.debug...done.
done.

Unread portion of the kernel message buffer:


Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 02
fault virtual address   = 0x28
fault code  = supervisor read data, page not present
instruction pointer = 0x20:0x80ecd31d
stack pointer   = 0x28:0xfe003fca7a40
frame pointer   = 0x28:0xfe003fca7a60
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 = 0 (softirq_2)
trap number = 12
panic: page fault
cpuid = 2
time = 1550009599
KDB: stack backtrace:
#0 0x80c531c7 at kdb_backtrace+0x67
#1 0x80c07143 at vpanic+0x1a3
#2 0x80c06f93 at panic+0x43
#3 0x8118d9ff at trap_fatal+0x35f
#4 0x8118da59 at trap_pfault+0x49
#5 0x8118d07e at trap+0x29e
#6 0x81168ac5 at calltrap+0x8
#7 0x80eca240 at ipsec_delete_pcbpolicy+0x20
#8 0x80dbaeec at in_pcbfree_deferred+0x6c
#9 0x80c4db1a at epoch_call_task+0x1ca
#10 0x80c51a54 at gtaskqueue_run_locked+0x144
#11 0x80c516b8 at gtaskqueue_thread_loop+0x98
#12 0x80bc6f23 at fork_exit+0x83
#13 0x81169abe at fork_trampoline+0xe
Uptime: 8m33s
Dumping 950 out of 8077 MB:..2%..11%..21%..31%..41%..51%..61%..71%..81%..91%

__curthread () at ./machine/pcpu.h:230
230 __asm("movq %%gs:%P1,%0" : "=r" (td) : "n"
(OFFSETOF_CURTHREAD));
(kgdb) bt
#0  __curthread () at ./machine/pcpu.h:230
#1  doadump (textdump=) at /usr/src/sys/kern/kern_shutdown.c:366
#2  0x80c06d2b in kern_reboot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:446
#3  0x80c071a3 in vpanic (fmt=, ap=0xfe003fca7790)
at /usr/src/sys/kern/kern_shutdown.c:872
#4  0x80c06f93 in panic (fmt=) at
/usr/src/sys/kern/kern_shutdown.c:799
#5  0x8118d9ff in trap_fatal (frame=0xfe003fca7980, eva=40) at
/usr/src/sys/amd64/amd64/trap.c:929
#6  0x8118da59 in trap_pfault (frame=0xfe003fca7980, usermode=0) at
/usr/src/sys/amd64/amd64/trap.c:765
#7  0x8118d07e in trap (frame=0xfe003fca7980) at
/usr/src/sys/amd64/amd64/trap.c:441
#8  
#9  0x80ecd31d in key_freesp (spp=0xf80211241880) at
/usr/src/sys/netipsec/key.c:1199
#10 0x80eca240 in ipsec_delete_pcbpolicy (inp=0xf800151aa1e8) at
/usr/src/sys/netipsec/ipsec_pcb.c:176
#11 0x80dbaeec in in_pcbfree_deferred (ctx=0xf800151aa3c0) at
/usr/src/sys/netinet/in_pcb.c:1576
#12 0x80c4db1a in epoch_call_task (arg=) at
/usr/src/sys/kern/subr_epoch.c:507
#13 0x80c51a54 in gtaskqueue_run_locked (queue=0xf80003363c00) at
/usr/src/sys/kern/subr_gtaskqueue.c:376
#14 0x80c516b8 in gtaskqueue_thread_loop (arg=) at
/usr/src/sys/kern/subr_gtaskqueue.c:557
#15 0x80bc6f23 in fork_exit (callout=0x80c51620
, arg=0xfe00025f5038, frame=0xfe003fca7c00)
at /usr/src/sys/kern/kern_fork.c:1059
#16 
(kgdb) frame 9
#9  0x80ecd31d in key_freesp (spp=0xf80211241880) at
/usr/src/sys/netipsec/key.c:1199
1199KEYDBG(IPSEC_STAMP,
(kgdb)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 235684] security/ipsec-tools kernel panic

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235684

--- Comment #9 from Andrey V. Elsukov  ---
Can you try to remove `option VIMAGE` from your kernel config? It looks like
the problem is similar to the one described in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235699

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 235684] security/ipsec-tools kernel panic

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235684

--- Comment #8 from Sergey Anokhin  ---
(In reply to Jan Bramkamp from comment #6)

Did you mean try to set kern.maxssiz into /boot/loader.conf?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 235684] security/ipsec-tools kernel panic

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235684

--- Comment #7 from Sergey Anokhin  ---
btw, perhaps it can be helpful: if port security/ipsec-tools was built with
default options (make rmconfig), so the bug doesn't reproduced

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 235684] security/ipsec-tools kernel panic

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235684

Jan Bramkamp  changed:

   What|Removed |Added

 CC||cr...@bultmann.eu

--- Comment #6 from Jan Bramkamp  ---
Can you try again with IPSEC_DEBUG and a doubled kernel stack size?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 221376] 12.0-RELEASE amd64: any kernel fail to boot - freezes just after run kernel

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221376

VVD  changed:

   What|Removed |Added

Summary|11.1-RELEASE amd64: GENERIC |12.0-RELEASE amd64: any
   |kernel compiled without any |kernel fail to boot -
   |CPUTYPE?= in /etc/make.conf |freezes just after run
   |fail to boot, but with  |kernel
   |CPUTYPE?=nocona it work |
   |fine|

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 221376] 11.1-RELEASE amd64: GENERIC kernel compiled without any CPUTYPE?= in /etc/make.conf fail to boot, but with CPUTYPE?=nocona it work fine

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221376

VVD  changed:

   What|Removed |Added

 Attachment #201961|Photo for screen from boot  |Photo of screen from boot
description|-v with kernel  |-v with kernel
   |12.0-RELEASE-p3 amd64   |12.0-RELEASE-p3 amd64

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 235684] security/ipsec-tools kernel panic

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235684

--- Comment #5 from Andrey V. Elsukov  ---
(In reply to Sergey Anokhin from comment #4)
> (In reply to Andrey V. Elsukov from comment #3)
> 
> There is a mind that if turn off
> 
> options IPSEC_DEBUG
> 
> kernel panic will disappear

Disabling IPSEC_DEBUG also reduces the requirement to kernel stack size.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 221376] 11.1-RELEASE amd64: GENERIC kernel compiled without any CPUTYPE?= in /etc/make.conf fail to boot, but with CPUTYPE?=nocona it work fine

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221376

VVD  changed:

   What|Removed |Added

Version|11.1-RELEASE|12.0-RELEASE

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 221376] 11.1-RELEASE amd64: GENERIC kernel compiled without any CPUTYPE?= in /etc/make.conf fail to boot, but with CPUTYPE?=nocona it work fine

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221376

--- Comment #5 from VVD  ---
Created attachment 201961
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=201961=edit
Photo for screen from boot -v with kernel 12.0-RELEASE-p3 amd64

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 221376] 11.1-RELEASE amd64: GENERIC kernel compiled without any CPUTYPE?= in /etc/make.conf fail to boot, but with CPUTYPE?=nocona it work fine

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221376

--- Comment #4 from VVD  ---
Created attachment 201960
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=201960=edit
dmesg from boot -v with GENERIC kernel 11.2-RELEASE-p8 amd64

11.2 GENERIC kernel from freebsd-update boot fine.
But any 12.0 kernel freezes just after start.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 235684] security/ipsec-tools kernel panic

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235684

--- Comment #4 from Sergey Anokhin  ---
(In reply to Andrey V. Elsukov from comment #3)

There is a mind that if turn off

options IPSEC_DEBUG

kernel panic will disappear

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 235684] security/ipsec-tools kernel panic

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235684

--- Comment #3 from Andrey V. Elsukov  ---
KEYDBG() macro executed only when net.key.debug is set to non-zero value. It
looks like your sysctl.conf didn't set it. Also, it looks impossible to get
page fault with fault address 0x28 in this line of code. I suspect, that you
have some sort of memory corruption. Not sure, is it hardware related or it is
overwritten by some code.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 235683] [zfs] Panic during data access or scrub on 12.0-STABLE r343904 (blkptr at DVA 0 has invalid OFFSET)

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235683

Andriy Voskoboinyk  changed:

   What|Removed |Added

 CC||a...@freebsd.org
Summary|ZFS kernel panic when   |[zfs] Panic during data
   |access to data or scrub |access or scrub on
   ||12.0-STABLE r343904 (blkptr
   ||at  DVA 0 has invalid
   ||OFFSET)
   Keywords||panic
   Assignee|b...@freebsd.org|f...@freebsd.org

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 235684] security/ipsec-tools kernel panic

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235684

--- Comment #2 from Sergey Anokhin  ---
(In reply to Andrey V. Elsukov from comment #1)

kernel config:

(pts/2)[root@server:~]# cat /usr/src/sys/amd64/conf/SERVER
#
# GENERIC -- Generic kernel configuration file for FreeBSD/amd64
#
# For more information on this file, please read the config(5) manual page,
# and/or the handbook section on Kernel Configuration Files:
#
#   
https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
#
# The handbook is also available locally in /usr/share/doc/handbook
# if you've installed the doc distribution, otherwise always see the
# FreeBSD World Wide Web server (https://www.FreeBSD.org/) for the
# latest information.
#
# An exhaustive list of options and more detailed explanations of the
# device lines is also present in the ../../conf/NOTES and NOTES files.
# If you are in doubt as to the purpose or necessity of a line, check first
# in NOTES.
#
# $FreeBSD: stable/12/sys/amd64/conf/GENERIC 340695 2018-11-20 19:37:09Z
zeising $

cpu HAMMER
ident   SERVER

makeoptions DEBUG=-g# Build kernel with gdb(1) debug
symbols
makeoptions WITH_CTF=1  # Run ctfconvert(1) for DTrace support

options SCHED_ULE   # ULE scheduler
options NUMA# Non-Uniform Memory Architecture
support
options PREEMPTION  # Enable kernel thread preemption
options VIMAGE  # Subsystem virtualization, e.g. VNET
options INET# InterNETworking
options INET6   # IPv6 communications protocols
options IPSEC   # IP (v4/v6) security
options IPSEC_SUPPORT   # Allow kldload of ipsec and tcpmd5
options TCP_OFFLOAD # TCP offload
options TCP_BLACKBOX# Enhanced TCP event logging
options TCP_HHOOK   # hhook(9) framework for TCP
options TCP_RFC7413 # TCP Fast Open
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 QUOTA   # Enable disk quotas for UFS
options MD_ROOT # MD is a potential root device
options NFSCL   # Network Filesystem Client
options NFSD# Network Filesystem Server
options NFSLOCKD# Network Lock Manager
options NFS_ROOT# NFS usable as /, requires NFSCL
options MSDOSFS # MSDOS Filesystem
options CD9660  # ISO 9660 Filesystem
options PROCFS  # Process filesystem (requires
PSEUDOFS)
options PSEUDOFS# Pseudo-filesystem framework
options GEOM_RAID   # Soft RAID functionality.
options GEOM_LABEL  # Provides labelization
options EFIRT   # EFI Runtime Services support
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 COMPAT_FREEBSD9 # Compatible with FreeBSD9
options COMPAT_FREEBSD10# Compatible with FreeBSD10
options COMPAT_FREEBSD11# Compatible with FreeBSD11
options SCSI_DELAY=5000 # 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 CAPABILITY_MODE # Capsicum capability mode
options CAPABILITIES# Capsicum capabilities
options MAC # TrustedBSD MAC Framework
options KDTRACE_FRAME   # Ensure frames are

[Bug 235684] security/ipsec-tools kernel panic

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235684

Andrey V. Elsukov  changed:

   What|Removed |Added

 CC||a...@freebsd.org

--- Comment #1 from Andrey V. Elsukov  ---
(In reply to Sergey Anokhin from comment #0)
> I see kernel panic during racoon restart.
> 
> # uname -rv
> 12.0-STABLE FreeBSD 12.0-STABLE r343904 SERVER

Please, show the content of your kernel config and what sysctl variables do you
changed against default configuration.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 235684] security/ipsec-tools kernel panic

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235684

Sergey Anokhin  changed:

   What|Removed |Added

 CC||b...@freebsd.org,
   ||sta...@freebsd.org

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 235683] ZFS kernel panic when access to data or scrub

2019-02-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235683

Sergey Anokhin  changed:

   What|Removed |Added

 CC||sta...@freebsd.org

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problem reports for sta...@freebsd.org that need special attention

2019-02-10 Thread bugzilla-noreply

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |230620 | "install -d" issue

1 problems total for which you should take action.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 233006] [regression] [patch] bsdtar aborts creation of archive on ENOENT

2019-02-03 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233006

--- Comment #13 from Martin Matuska  ---
Hi Eugene, I have modified your patch to operate only if descended into
subdirectories. It has broken the missing file test because missing files on
top-level have been ignored as well. Sometimes more files are processed at a
time, so it was necessary to process the error string a bit differently as
well.

Could you please check the libarchive pull request #1131 if it fixes your
issue? 
https://github.com/libarchive/libarchive/pull/1131

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problem reports for sta...@freebsd.org that need special attention

2019-02-03 Thread bugzilla-noreply

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |230620 | "install -d" issue

1 problems total for which you should take action.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 233006] [regression] [patch] bsdtar aborts creation of archive on ENOENT

2019-02-01 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233006

--- Comment #12 from Eugene Grosbein  ---
(In reply to lgfbsd from comment #11)

Creation of UFS snapshots of filesystems having lots of files is inefficient,
slow and was prone to deadlocks in 10.3-STABLE (I still run a couple of such
hosts and one of them deadlocked last week on UFS shapshot creation). I'm not
sure if that bug was fixed or not in modern versions.

Anyway, GNU tar had no such problem for many years and I do not see why bsdtar
should break on ENOENT.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 233006] [regression] [patch] bsdtar aborts creation of archive on ENOENT

2019-02-01 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233006

lgf...@be-well.ilk.org changed:

   What|Removed |Added

 CC||lgf...@be-well.ilk.org

--- Comment #11 from lgf...@be-well.ilk.org ---
For what it's worth, POSIX does not have language that in any way touches on
this issue.

The safe way to back up live filesystems on FreeBSD is by working on a
snapshot. dump(8) even has built-in options for doing this. That said, I don't
see any problems with the proposed change.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 233006] [regression] [patch] bsdtar aborts creation of archive on ENOENT

2019-02-01 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233006

--- Comment #10 from j...@transactionware.com ---
(In reply to Eugene Grosbein from comment #9)

Yes, I see your point: Walking the tree is different to command line specified
names being absent.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 233006] [regression] [patch] bsdtar aborts creation of archive on ENOENT

2019-02-01 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233006

--- Comment #9 from Eugene Grosbein  ---
(In reply to janm from comment #7)

The PR 205358 deals with distinct problem concerning input path. I'm talking
about files found while walking subdirectories recursively.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 233006] [regression] [patch] bsdtar aborts creation of archive on ENOENT

2019-02-01 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233006

--- Comment #8 from Eugene Grosbein  ---
(In reply to janm from comment #7)

This makes it *impossible* to create tar archive of living file system with
constantly added/removed temporary files and large directory structure. And
this is *regression* after move from GNU tar. The reference to POSIX does not
seem useful to me from practical point of view.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 233006] [regression] [patch] bsdtar aborts creation of archive on ENOENT

2019-02-01 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233006

j...@transactionware.com changed:

   What|Removed |Added

 CC||j...@transactionware.com

--- Comment #7 from j...@transactionware.com ---
This doesn't seem like a bug to me. Is there officially required Posix
behaviour? I reported the opposite of this bug some time ago:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205358

https://github.com/libarchive/libarchive/issues/708

For me, not failing when an input file can't be found is a problem. To not fail
on a file moving seems like something that should be explicitly requested with
a command line option.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 193360] [panic] [syscons] random syscons panic

2019-01-27 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193360

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 CC||go...@freebsd.org
 Status|New |Closed
 Resolution|--- |Not Enough Information

--- Comment #4 from Oleksandr Tymoshenko  ---
Provided information is not enough to analyze the problem.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problem reports for sta...@freebsd.org that need special attention

2019-01-27 Thread bugzilla-noreply

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |230620 | "install -d" issue

1 problems total for which you should take action.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problem reports for sta...@freebsd.org that need special attention

2019-01-20 Thread bugzilla-noreply

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |230620 | "install -d" issue

1 problems total for which you should take action.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problem reports for sta...@freebsd.org that need special attention

2019-01-13 Thread bugzilla-noreply

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |230620 | "install -d" issue

1 problems total for which you should take action.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problem reports for sta...@freebsd.org that need special attention

2019-01-06 Thread bugzilla-noreply

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |230620 | "install -d" issue

1 problems total for which you should take action.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problem reports for sta...@freebsd.org that need special attention

2018-12-30 Thread bugzilla-noreply

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |230620 | "install -d" issue

1 problems total for which you should take action.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problem reports for sta...@freebsd.org that need special attention

2018-12-23 Thread bugzilla-noreply

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |230620 | "install -d" issue

1 problems total for which you should take action.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problem reports for sta...@freebsd.org that need special attention

2018-12-16 Thread bugzilla-noreply

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |230620 | "install -d" issue

1 problems total for which you should take action.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problem reports for sta...@freebsd.org that need special attention

2018-12-09 Thread bugzilla-noreply

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |230620 | "install -d" issue

1 problems total for which you should take action.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 221146] [ixgbe] Problem with second laggport

2018-12-09 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

--- Comment #24 from Peter Vanek  ---
Hello guys,

Wondering if this is may be same origin as coming from

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221317

with commit

https://reviews.freebsd.org/D18468

Peter

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

2018-12-08 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213

Mark Knight  changed:

   What|Removed |Added

 Status|Open|Closed
 Resolution|--- |Overcome By Events

--- Comment #37 from Mark Knight  ---
Seems fine / resolved under FreeBSD 11.2-RELEASE-p4, so I guess this can now be
closed.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

2018-12-02 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213

--- Comment #36 from Eugene Grosbein  ---
Can you test FreeBSD 11.2? 10.4 went EoL already.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problem reports for sta...@freebsd.org that need special attention

2018-12-02 Thread bugzilla-noreply

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |230620 | "install -d" issue
Open|227213 | FreeBSD 10.4 kernel deadlocks on sysctlmemlock

2 problems total for which you should take action.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problem reports for sta...@freebsd.org that need special attention

2018-11-25 Thread bugzilla-noreply

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |230620 | "install -d" issue
Open|227213 | FreeBSD 10.4 kernel deadlocks on sysctlmemlock

2 problems total for which you should take action.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 233006] [regression] [patch] bsdtar aborts creation of archive on ENOENT

2018-11-19 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233006

Eugene Grosbein  changed:

   What|Removed |Added

Summary|bsdtar aborts creation of   |[regression] [patch] bsdtar
   |archive on ENOENT   |aborts creation of archive
   ||on ENOENT

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 233006] bsdtar aborts creation of archive on ENOENT

2018-11-19 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233006

Kubilay Kocak  changed:

   What|Removed |Added

Summary|[regression] [patch] bsdtar |bsdtar aborts creation of
   |aborts creation of archive  |archive on ENOENT
   |on ENOENT   |
   See Also||https://github.com/libarchi
   ||ve/libarchive/issues/1082

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problem reports for sta...@freebsd.org that need special attention

2018-11-18 Thread bugzilla-noreply

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |230620 | "install -d" issue
Open|227213 | FreeBSD 10.4 kernel deadlocks on sysctlmemlock

2 problems total for which you should take action.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problem reports for sta...@freebsd.org that need special attention

2018-11-11 Thread bugzilla-noreply

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |230620 | "install -d" issue
Open|227213 | FreeBSD 10.4 kernel deadlocks on sysctlmemlock

2 problems total for which you should take action.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 228536] x11/nvidia-driver: 11.2-BETA3 - fails to operate correctly

2018-11-09 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228536

Tijl Coosemans  changed:

   What|Removed |Added

 CC||core.dumped...@gmail.com

--- Comment #13 from Tijl Coosemans  ---
*** Bug 231897 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 228536] x11/nvidia-driver: 11.2-BETA3 - fails to operate correctly

2018-11-09 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228536

Tijl Coosemans  changed:

   What|Removed |Added

 CC||t...@freebsd.org
 Status|New |Closed
 Resolution|--- |Overcome By Events

--- Comment #12 from Tijl Coosemans  ---
FreeBSD 11 packages are built for 11.2 now.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic

2018-11-06 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535

--- Comment #20 from Rodney W. Grimes  ---
(In reply to D. Ebdrup from comment #18)
And has a 90+% chance of breaking again when 11.3 is release, this is a general
issue being address by some other means that are not yet in place.  Either
special "per release" kmod packages, or "kmods install source and require
kernel sources to rebuild them" are currently being looked at as possible long
term solutions to this KABI breakage issue.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic

2018-11-06 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535

Jan Jurkus  changed:

   What|Removed |Added

 CC||i...@gcecad-service.nl

--- Comment #19 from Jan Jurkus  ---
Well, I just (this evening) upgraded a server to 11.2-RELEASE and still got a
kernel panic.

Starting the old kernel, commenting out the virtualbox stuff in
/boot/loader.conf and /etc/rc.conf solved the issue.
Then I could start the new kernel and update the pacakges to the latest
versions.

Well of course it all went tits up again because of the VNC problem with
virtualbox-ose-nox11-5.2.20, that will teach me to not migrate stuff to bhyve
;-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic

2018-11-06 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535

D. Ebdrup  changed:

   What|Removed |Added

 CC||debd...@gmail.com

--- Comment #18 from D. Ebdrup  ---
To clarify, this issue is fixed as of the EOL date of 11.1, since the 11.2
packages have now been built on 11.2.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 233006] [regression] [patch] bsdtar aborts creation of archive on ENOENT

2018-11-06 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233006

Eugene Grosbein  changed:

   What|Removed |Added

Summary|[regression] bsdtar aborts  |[regression] [patch] bsdtar
   |creation of archive on  |aborts creation of archive
   |ENOENT  |on ENOENT
   Keywords||patch
 CC||sta...@freebsd.org

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problem reports for sta...@freebsd.org that need special attention

2018-11-04 Thread bugzilla-noreply

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |230620 | "install -d" issue
Open|227213 | FreeBSD 10.4 kernel deadlocks on sysctlmemlock

2 problems total for which you should take action.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problem reports for sta...@freebsd.org that need special attention

2018-10-28 Thread bugzilla-noreply

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |230620 | "install -d" issue
Open|227213 | FreeBSD 10.4 kernel deadlocks on sysctlmemlock

2 problems total for which you should take action.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problem reports for sta...@freebsd.org that need special attention

2018-10-21 Thread bugzilla-noreply

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |230620 | "install -d" issue
Open|227213 | FreeBSD 10.4 kernel deadlocks on sysctlmemlock

2 problems total for which you should take action.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 227654] [panic] repeatable crash with lagg+vlan+em

2018-10-21 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227654

Kubilay Kocak  changed:

   What|Removed |Added

   Severity|Affects Only Me |Affects Some People
 CC|sta...@freebsd.org  |

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 227654] [panic] repeatable crash with lagg+vlan+em

2018-10-20 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227654

--- Comment #5 from Eugene Grosbein  ---
I've added additional printf's to sys/net/if_ethersubr.c and found that it
panices within ether_output_frame() function.

I've added this just before PFIL_HOOKED(_link_pfil_hook) check:

if (ifp->if_index == 6) printf(""ether_output_frame: checking curvnet=%p\n",
curvnet);
if (ifp->if_index == 6) printf(""ether_output_frame: V_link_pfil_hook=%p\n",
V_link_pfil_hook);

And last lines of dmesg buffer after panic are:

ether_output_frame: checking curvnet=0
panic: vm_fault_hold: fault on nofault entry, addr: 0

So, curvnet is NULL here, hence the panic.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 227654] [panic] repeatable crash with lagg+vlan+em

2018-10-20 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227654

Eugene Grosbein  changed:

   What|Removed |Added

Version|11.1-STABLE |CURRENT

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 227654] [panic] repeatable crash with lagg+vlan+em

2018-10-20 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227654

--- Comment #4 from Eugene Grosbein  ---
This is 100% repeatable using same command sequence under 12.0-BETA1/i386
installed with all defaults inside VirtualBox VM.

This time it says:

panic: vm_fault_hold: fault on nofault entry, addr: 0

It generates nice crashdump and reboots.
I've uploaded kernel.debug (stock one from 12.0-BETA1/i386 installation image,
18M compressed) and vmcore.0.xz (9.2MB compressed) here:
http://www.grosbein.net/freebsd/crash/20181021/

Here comes kgdb script:

Script started on Sun Oct 21 02:31:58 2018
Command: kgdb kernel.debug /var/crash/vmcore.0
GNU gdb (GDB) 8.2 [GDB v8.2 for FreeBSD]
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "i386-portbld-freebsd12.0".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from kernel.debug...done.

Unread portion of the kernel message buffer:
<6>em0: link state changed to DOWN
<6>vlan61: link state changed to DOWN
panic: vm_fault_hold: fault on nofault entry, addr: 0
cpuid = 0
time = 1540062884
KDB: stack backtrace:
#0 0x112d01f at kdb_backtrace+0x4f
#1 0x10e03f7 at vpanic+0x147
#2 0x10e02ab at panic+0x1b
#3 0x14289c5 at vm_fault_hold+0x2a45
#4 0x1425f2e at vm_fault+0x5e
#5 0x16b6ef7 at trap_pfault+0xc7
#6 0x16b64af at trap+0x3cf
#7 0xffc0315d at PTDpde+0x4165
#8 0x11e0122 at ether_output+0x6a2
#9 0x124887d at arprequest+0x44d
#10 0x12493f9 at arp_ifinit+0x59
#11 0x124c5bb at arp_handle_ifllchange+0x3b
#12 0x11db275 at if_setlladdr+0x275
#13 0x11eb900 at vlan_lladdr_fn+0x30
#14 0x113eba9 at taskqueue_run_locked+0x189
#15 0x113fd57 at taskqueue_thread_loop+0x97
#16 0x10a1af1 at fork_exit+0x71
#17 0xffc033ba at PTDpde+0x43c2
Uptime: 7m21s
Physical memory: 2019 MB
Dumping 84 MB: 69 53 37 21 5

__curthread () at ./machine/pcpu.h:226
226 ./machine/pcpu.h: No such file or directory.
(kgdb) add-kld if_tap.ko
add symbol table from file "if_tap.ko.debug" at
.rodata_addr = 0x18c0c134
set_sysctl_set_addr = 0x18c0c4e0
set_modmetadata_set_addr = 0x18c0c4f8
.note.gnu.build-id_addr = 0x18c0c500
.dynsym_addr = 0x18c0c548
.gnu.hash_addr = 0x18c0cb18
.hash_addr = 0x18c0cb58
.dynstr_addr = 0x18c0ce48
.rel.dyn_addr = 0x18c0d348
.text_addr = 0x18c0f000
.data_addr = 0x18c12000
set_sysinit_set_addr = 0x18c12270
set_sysuninit_set_addr = 0x18c12278
.dynamic_addr = 0x18c13000
.bss_addr = 0x18c14000
(y or n) y
Reading symbols from if_tap.ko.debug...done.
(kgdb) add-kld if_lagg.ko
add symbol table from file "if_lagg.ko.debug" at
.rodata_addr = 0x18c15138
set_sysctl_set_addr = 0x18c16038
set_modmetadata_set_addr = 0x18c16054
.note.gnu.build-id_addr = 0x18c16060
.dynsym_addr = 0x18c160a8
.gnu.hash_addr = 0x18c16798
.hash_addr = 0x18c167e8
.dynstr_addr = 0x18c16b68
.rel.dyn_addr = 0x18c171e8
.text_addr = 0x18c1a000
.data_addr = 0x18c24000
set_vnet_addr = 0x18c24270
set_sysinit_set_addr = 0x18c242a0
set_sysuninit_set_addr = 0x18c242ac
.dynamic_addr = 0x18c25000
.bss_addr = 0x18c26000
(y or n) y
Reading symbols from if_lagg.ko.debug...done.
(kgdb) bt full
#0  __curthread () at ./machine/pcpu.h:226
td = 
#1  doadump (textdump=) at /usr/src/sys/kern/kern_shutdown.c:366
error = 
coredump = 
#2  0x010e0073 in kern_reboot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:446
once = 
#3  0x010e0444 in vpanic (
fmt=0x179ab2c "%s: fault on nofault entry, addr: %#lx", 
ap=0x16a1462c "U\327p\001") at /usr/src/sys/kern/kern_shutdown.c:872
buf = "vm_fault_hold: fault on nofault entry, addr: 0", '\000' 
td = 0x7369700
newpanic = 
bootopt = 260
other_cpus = 
#4  0x010e02ab in panic (
fmt=0x179ab2c "%s: fault on nofault entry, addr: %#lx")
at /usr/src/sys/kern/kern_shutdown.c:799
ap = 
--Type  for more, q to quit, c to continue without paging--c
#5  0x014289c5 in vm_fault_hold (map=0x2bd5000, vaddr=0, fault_type=, fault_flags=0, m_hold=0x0) at /usr/src/sys/vm/vm_fault.c:586
hardfault = 
nera = 
faultcount = 
wired = 0
prot = 7 '\a'
result = 0
rv = 
behind = 
ahead = 
error = 
locked = 
vp = 
fs =

Problem reports for sta...@freebsd.org that need special attention

2018-10-14 Thread bugzilla-noreply

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |230620 | "install -d" issue
Open|227213 | FreeBSD 10.4 kernel deadlocks on sysctlmemlock

2 problems total for which you should take action.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 221146] [ixgbe] Problem with second laggport

2018-10-12 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

Maciej Suszko  changed:

   What|Removed |Added

 CC||mac...@suszko.eu

--- Comment #23 from Maciej Suszko  ---
Same problem here on Dell PowerEdge R740xd running 11.2-RELEASE-p4, sources
modified to include latest mrsas drviers (DELL PERC H740P).

root@host:~ # uname -a
FreeBSD host 11.2-RELEASE-p4 FreeBSD 11.2-RELEASE-p4 #0 r338999M: Fri Sep 28
19:27:30 UTC 2018 root@host:/usr/obj/usr/src/sys/GENERIC  amd64

root@host:~ # dmesg -a| grep '^ix[01]'
ix0:  port
0x4020-0x403f mem 0x9d90-0x9d9f,0x9da04000-0x9da07fff at device 0.0
numa-domain 0 on pci5
ix0: Using MSI-X interrupts with 9 vectors
ix0: Ethernet address: xx:xx:xx:xx:xx:98
ix0: PCI Express Bus: Speed 5.0GT/s Width x8
ix0: netmap queues/slots: TX 8/2048, RX 8/2048
ix1:  port
0x4000-0x401f mem 0x9d80-0x9d8f,0x9da0-0x9da03fff at device 0.1
numa-domain 0 on pci5
ix1: Using MSI-X interrupts with 9 vectors
ix1: Ethernet address: xx:xx:xx:xx:xx:9a
ix1: PCI Express Bus: Speed 5.0GT/s Width x8
ix1: netmap queues/slots: TX 8/2048, RX 8/2048
ix0: link state changed to UP
ix0: flags=8843 metric 0 mtu 1500
ix1: flags=8802 metric 0 mtu 1500
ix1: flags=8802 metric 0 mtu 1500
ix1: link state changed to UP
ix1: link state changed to DOWN
ix1: link state changed to UP

I can attach ix1 to lagg0 later, after system boot... doing this within rc.conf
(in pair with ix0) does not work, ix1 shows 'no carrier' and it doesn't change
it's state after removing from lagg0, interface down/up.

root@host:~ # ifconfig ix0
ix0: flags=8843 metric 0 mtu 1500
   
options=e407bb
ether xx:xx:xx:xx:xx:98
hwaddr xx:xx:xx:xx:xx:98
nd6 options=29
media: Ethernet autoselect (10Gbase-Twinax
)
status: active

root@host:~ # ifconfig ix1
ix1: flags=8843 metric 0 mtu 1500
   
options=e407bb
ether xx:xx:xx:xx:xx:98
hwaddr xx:xx:xx:xx:xx:9a
nd6 options=29
media: Ethernet autoselect (10Gbase-Twinax
)
status: active

root@host:~ # ifconfig lagg0
lagg0: flags=8843 metric 0 mtu 1500

options=e407bb
ether xx:xx:xx:xx:xx:98
nd6 options=29
media: Ethernet autoselect
status: active
groups: lagg 
laggproto lacp lagghash l2,l3,l4
laggport: ix0 flags=1c
laggport: ix1 flags=1c

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problem reports for sta...@freebsd.org that need special attention

2018-10-07 Thread bugzilla-noreply

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |230620 | "install -d" issue
Open|227213 | FreeBSD 10.4 kernel deadlocks on sysctlmemlock

2 problems total for which you should take action.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problem reports for sta...@freebsd.org that need special attention

2018-09-30 Thread bugzilla-noreply

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |230620 | "install -d" issue
Open|227213 | FreeBSD 10.4 kernel deadlocks on sysctlmemlock

2 problems total for which you should take action.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problem reports for sta...@freebsd.org that need special attention

2018-09-23 Thread bugzilla-noreply

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |230620 | "install -d" issue
Open|227213 | FreeBSD 10.4 kernel deadlocks on sysctlmemlock

2 problems total for which you should take action.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problem reports for sta...@freebsd.org that need special attention

2018-09-16 Thread bugzilla-noreply

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |230620 | "install -d" issue
Open|227213 | FreeBSD 10.4 kernel deadlocks on sysctlmemlock

2 problems total for which you should take action.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic

2018-09-09 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535

--- Comment #17 from rkober...@gmail.com ---
(In reply to Dennis Clarke from comment #15)
just tried this and I need to slightly modify the instructions:
$ svnlite update -r 469570 /usr/ports/emulators/virtualbox-ose-kmod
$ svn update -r 469570 /usr/ports/emulators/virtualbox-ose
$ make -C /usr/ports/emulators/virtualbox-ose-kmod package
$ pkg add /usr/ports/packages/All/virtualbox-ose-kmod-5.2.12.txz

That file may be copied to other system and installed with "pkg add". Be sure
to delete any installed version of virtualbox-ose-kmod already installed with:
# pkg delete -f virtualbox-ose-kmod
before adding the newly built package.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic

2018-09-09 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535

--- Comment #16 from rkober...@gmail.com ---
(In reply to Dennis Clarke from comment #15)
Now I am completely baffled. I just checked the archive and there was never a
5.2.12_1. I see no way that the package virtualbox-ose-5.2.12_1 could exist.

That said, you need to get the kmod port for 5.2.12. To do that:
$ svn update -r 469570 /usr/ports/emulators/virtualbox-ose-kmod

That will downgrade the port to a version that matches the package for
virtualbox-ose. (PORTREVISION should not matter.) Then you can build the port.
If you need it on multiple system, do a "make package" so that you will have a
package you can just copy to other systems and install with "pkg add
/usr/ports/packages/All/virtualbox-ose-kmod-5.2.12.txz". This assumes that you
have not set any environmental variable that overrides the default location.

This is a fairly ugly mess that should never have happened. When it did, I
think the proper action would have been to build a package of 5.2.12 on an 11.2
system an put it somewhere on the ftp server. (The same applies to the nVidia
driver which has a similar issue.) This would have been documented in the
errata.

But I have no say in this and what you see is what ports-manager chose to do.

I can make a package you need available, but, if I was you, I would not trust a
driver from an unknown source. Let me know if you want it, though.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problem reports for sta...@freebsd.org that need special attention

2018-09-09 Thread bugzilla-noreply

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |230620 | "install -d" issue
Open|227213 | FreeBSD 10.4 kernel deadlocks on sysctlmemlock

2 problems total for which you should take action.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic

2018-09-09 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535

--- Comment #15 from Dennis Clarke  ---
(In reply to rkoberman from comment #12)

virtualbox-ose has been a real pain to deal with for the last few weeks
here.  At least for me and my team of sysadmins who are doing experiments
with FreeBSD RELEASE 11.2. I can report that I have seen the panic-on-boot
loop "feature" and it is fun. 

Well the package for virtualbox-ose is broken on the RELEASE version 
of 11.2 and so yes it is a problem and will remain a problem until some
future date. Near future we hope.  One may perform the experiment, as I
have, repeatedly, and see a kernel panic repeatedly.

One must build the virtualbox-ose-kmod bits from ports and then overwrite 
the existing pkg which was installed via dependencies for virtualbox-ose.

The entirely repeatable process :

1) install RELEASE 11.2 

2) at first boot you may su - and as root do very very few things :

# /usr/sbin/pkg query -e '%a = 0' '%o'
The package management tool is not yet installed on your system.
Do you want to fetch and install it now? [y/N]: y
Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/FreeBSD:11:amd64/quarterly,
please wait...
Verifying signature with trusted certificate pkg.freebsd.org.2013102301... done
Installing pkg-1.10.5_1...
Extracting pkg-1.10.5_1: 100%
ports-mgmt/pkg
# 

Get on with the process of an update to the ports data

# /usr/sbin/portsnap fetch update
Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found.
Fetching snapshot tag from your-org.portsnap.freebsd.org... done.
.
.
.

Then do the portsnap extract.

3) Full stop right here and we have a fresh RELEASE 11.2 system with not much
on it : 

# /usr/sbin/pkg query -e '%a = 0' '%o'
ports-mgmt/pkg
# 

4)  install virtualbox-ose BEFORE attempting to build virtualbox-ose-kmod

# pkg install virtualbox-ose 
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 125 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
virtualbox-ose: 5.2.12_1
qt5-x11extras: 5.10.1
qt5-gui: 5.10.1
.
.
.  a lot of stuff gets dragged in and that includes broken virtualbox-ose-kmod:
5.2.12

.
.
.

5) manually build virtualbox-ose-kmod in ports to replace the broken 5.2.12 pkg 

# cd /usr/ports/emulators/virtualbox-ose-kmod/
# make install clean  

  a few items to watch for : 

   Be sure to select libsigsegv for GNU m4 
   Disable DTRACE Build with DTrace probes
   gmp-6.1.2  enable CPU optimizations 


6) at some point in the reasonably near future you will have
   two virtualbox-ose version pkgs thus : 

virtualbox-ose-5.2.12_1General-purpose full virtualizer for x86
hardware
virtualbox-ose-kmod-5.2.18 VirtualBox kernel module for FreeBSD

Note the different versions. 

After a minor edit to /boot/loader.conf and /etc/rc.conf one may reboot and 
have a workable mixed version virtualbox-ose.  Sort of.  The kernel module
version
isn't really a perfect match but seems to work thus far.   I have attempted to
build all of virtualbox-ose from ports, repeatedly, over and over there are
little
bugs in the process that stop the build.  One gets fixed and another pops up.

I don't think your average user or sysadmin out there will be able to easily
get
around this mess.  So when is the next big release ?  Because I don't see how
this can be marked as "fixed".  At best there is a hack workaround.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic

2018-09-09 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535

--- Comment #14 from rkober...@gmail.com ---
(In reply to Kubilay Kocak from comment #13)
I will open a bug report on this. I will admit that I never read the Errata
item. I just made foolish assumptions. Sigh.

Looking forward to three weeks from now when 11.1 goes EOL and a functioning
virtualbox-ose-kmod package for 11.2 will be available. (Well, the first
package build after that date.)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic

2018-09-09 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535

--- Comment #13 from Kubilay Kocak  ---
(In reply to rkoberman from comment #12)

The text from comment 10 was copied verbatim from the published 11.2-RELEASE
Errata notes. If the instructions are incorrect (or incomplete), please re-open
this issue, describing the exact correction to be made

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic

2018-09-04 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535

--- Comment #12 from rkober...@gmail.com ---
(In reply to Kubilay Kocak from comment #10)
No, virtualbox-ose is not the problem and there is no reason to build it. It is
virtualbox-ose-kmod that requires a build against an 11.2-RELEASE kernel. It is
small, takes seconds to build and install.

NOTE! You must have sources for 11.2-RELEASE on you system when you build it.
The version of the kmod must match the version of virtualbox-ose exactly.

If you install the package of virtualbox-ose and then build and install
virtualbax-ose-kmod of the same version, you will be ready to go.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic

2018-09-04 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535

Dennis Clarke  changed:

   What|Removed |Added

 CC||dcla...@blastwave.org

--- Comment #11 from Dennis Clarke  ---
The build process for virtualbox-ose is fraught with problems. At least from
'ports' where multiple little bugs seem to exist.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 193367] [panic] sleeping thread

2018-09-03 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193367

Eugene Grosbein  changed:

   What|Removed |Added

 Status|In Progress |Closed
 Resolution|--- |FIXED

--- Comment #22 from Eugene Grosbein  ---
Feedback timeout. Also, this is believed to be fixed in all supported branches.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 193367] [panic] sleeping thread

2018-09-03 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193367

Rene Ladan  changed:

   What|Removed |Added

 CC||r...@freebsd.org

--- Comment #21 from Rene Ladan  ---
Maintainer reset.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

1 2 3 4 >

1 - 100 of 342 matches

Mail list logo