[Bug 241646] netgraph/ng_bridge: Kernel panic after r353030 (ng_bridge_timeout())

2019-11-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241646 Kubilay Kocak changed: What|Removed |Added Keywords||crash, regression Assign

[Bug 241651] linuxkpi doesn't handle uninitialized PCI devices

2019-11-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241651 Bug ID: 241651 Summary: linuxkpi doesn't handle uninitialized PCI devices Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Se

[Bug 241635] tr(1) produces ridiculous error message

2019-11-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241635 --- Comment #3 from Ronald F. Guilmette --- I have read and understood your comments. I still contend that it is a dumb and inappropriate error message. If nothing else it is dumb because it is rather spectacularly uninformative, and prov

Evolution of Yahoo Groups

2019-11-01 Thread Yahoo via freebsd-bugs
___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 241646] netgraph/ng_bridge kernel panic after r353030

2019-11-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241646 Bug ID: 241646 Summary: netgraph/ng_bridge kernel panic after r353030 Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severi

[Bug 241635] tr(1) produces ridiculous error message

2019-11-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241635 --- Comment #2 from Conrad Meyer --- See also: "illegal, adj: contrary to or forbidden by official rules, regulations, etc" or "illegal, adj: prohibited by ... accepted rules." -- You are receiving this mail because: You are the assignee

[Bug 241635] tr(1) produces ridiculous error message

2019-11-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241635 Conrad Meyer changed: What|Removed |Added Status|New |Closed Resolution|---

[Bug 241269] syslogd fails to log anything if there is a unicode character in the hostname of a machine

2019-11-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241269 --- Comment #5 from Sverre --- It doesn't actually have to be an emoji either.. ℬ, ⨊, ... even the norwegian letters like å,æ,ø makes it fail.. and the swedish variants ä, ö .. It's a nice way to disable all logging if you got root on a box

[Bug 241269] syslogd fails to log anything if there is a unicode character in the hostname of a machine

2019-11-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241269 --- Comment #4 from Sverre --- Actually it seems that it's enough to have some emoji char in your hostname - it doesn't have to be all emoji... so awef🐒awef.domain.blah will also make syslogd fail to log... I think it's the part where it st

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev)

2019-11-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #10 from Michael --- Created attachment 208767 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=208767&action=edit Attachment 11 (Fatal trap 12) -- You are receiving this mail because: You are the assignee for the bug

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev)

2019-11-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #9 from Michael --- Created attachment 208766 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=208766&action=edit Attachment 10 (boot-4) -- You are receiving this mail because: You are the assignee for the bug. __

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev)

2019-11-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #8 from Michael --- Created attachment 208765 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=208765&action=edit Attachment 9 (boot-3) -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev)

2019-11-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #7 from Michael --- Created attachment 208764 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=208764&action=edit Attachment 8 (boot-2) -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev)

2019-11-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #6 from Michael --- Created attachment 208763 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=208763&action=edit Attachment 7 -- You are receiving this mail because: You are the assignee for the bug.

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev)

2019-11-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #5 from Michael --- Created attachment 208762 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=208762&action=edit Attachment 6 (work condition) -- You are receiving this mail because: You are the assignee for the bug.

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev)

2019-11-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #4 from Michael --- Created attachment 208761 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=208761&action=edit Attachment 5 (enable SR-IOV on port) -- You are receiving this mail because: You are the assignee for t

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev)

2019-11-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #3 from Michael --- Created attachment 208760 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=208760&action=edit Attachment 4 (ZFS) -- You are receiving this mail because: You are the assignee for the bug. __

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev)

2019-11-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #2 from Michael --- Created attachment 208759 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=208759&action=edit Attachment 3 (FS) -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev)

2019-11-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #1 from Michael --- Created attachment 208758 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=208758&action=edit Attachment 2 (VM setup) -- You are receiving this mail because: You are the assignee for the bug. _

[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev)

2019-11-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 Bug ID: 241639 Summary: Fatal trap 12: page fault ... current process = 0 (vmbusdev) Product: Base System Version: CURRENT Hardware: amd64 OS: Any