https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221676
--- Comment #9 from commit-h...@freebsd.org ---
A commit references this bug:
Author: phil
Date: Wed May 23 01:20:32 UTC 2018
New revision: 334068
URL: https://svnweb.freebsd.org/changeset/base/334068
Log:
Import libxo-0.9.0:
- Add xo_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228302
--- Comment #11 from Kaho Toshikazu ---
(In reply to sandreas from comment #9)
These sysctl don't have relation to WOL. Please don't touch them.
> dev.igb.0.wake=1
> dev.em.0.wake=1
Try `ifconfig igb0 up wol` to add "up" option.
How abo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228334
SF changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228412
--- Comment #4 from v...@mpeks.tomsk.su ---
Created attachment 193617
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=193617&action=edit
kgdb output
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228412
--- Comment #3 from v...@mpeks.tomsk.su ---
(In reply to Andrey V. Elsukov from comment #2)
> Also can you run `kgdb /boot/kernel/kernel /var/crash/vmcore.5`
> and show the output of these commands:
typescript attached.
> Your trace looks
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228302
--- Comment #10 from sandreas ---
(In reply to sandreas from comment #9)
Sorry... Markdown did not work... here are the direct links...
LAN Enabled: https://abload.de/img/lan_enabledtvs5s.jpg
PCI Power on Enabled: https://abload.de/img/pc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228302
--- Comment #9 from sandreas ---
Ok, i re-checked every possible setting that i found.
1.) Hardware / Mainboard should support wake on lan according to the manual
(http://asrock.pc.cdn.bitgravity.com/Manual/C236%20WSI.pdf), Page 4 (10 in
P
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227963
Andrey V. Elsukov changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228412
Andrey V. Elsukov changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206721
--- Comment #21 from j...@pfsense.org ---
(In reply to Roman Bogorodskiy from comment #20)
I see it less as "a workaround for misconfigured DHCP servers" and more as
preserving current expected behavior. I didn't even know my ISP DHCP server
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206721
--- Comment #20 from Roman Bogorodskiy ---
(In reply to jimp from comment #19)
Overall, I'd prefer the current behavior by default: there are environments
where it's necessary to respect MTU value supplied by the (properly configured)
DHCP
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228068
--- Comment #1 from preynold.free...@gmail.com ---
Created attachment 193614
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=193614&action=edit
Patch to set tos interval value when tclass is set
This patch seems to fix the issue f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228302
Kaho Toshikazu changed:
What|Removed |Added
CC||k...@elam.kais.kyoto-u.ac.j
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228412
--- Comment #1 from v...@mpeks.tomsk.su ---
ifconfig before shutdown:
re0: flags=8843 metric 0 mtu 1500
description: Outside
options=8209b
ether 54:04:a6:b4:9a:66
hwaddr 54:04:a6:b4:9a:66
inet 78.140.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224247
--- Comment #12 from Nick Hilliard ---
r321309 was 11.1-RELEASE, dated 2017-07-20. The fix was commit r327337, dated
2017-12-29. Looks like she may have tested the wrong version :-(
--
You are receiving this mail because:
You are the as
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224247
l...@donnerhacke.de changed:
What|Removed |Added
Resolution|FIXED |---
Status|Closed
16 matches
Mail list logo
