Issue #3205 has been updated by t_dfbsd.
The test fails on HEAD too.
Bug #3205: Go compiler net test failing
http://bugs.dragonflybsd.org/issues/3205#change-13800
* Author: t_dfbsd
* Status: In Progress
* Priority: High
* Assignee: tuxillo
* Category:
*
Issue #3205 has been updated by t_dfbsd.
When I upgraded to b7d3e1, I did a full world+kernel build/install and ran pkg
upgrade -f after (no problems).
Bug #3205: Go compiler net test failing
http://bugs.dragonflybsd.org/issues/3205#change-13799
* Autho
Issue #3205 has been updated by t_dfbsd.
Steps to reproduce:
1. Install go compiler from dports
2. git clone https://go.googlesource.com/go
3. cd go/src
4. ./make.bash
5. ../bin/go test -count 1 net
Bug #3205: Go compiler net test failing
http://bugs.dra
Issue #3205 has been updated by t_dfbsd.
I'm not on HEAD, but I'm only 5 commits behind and they look unrelated. I'll
try that though. I'll get you the steps to reproduce.
Bug #3205: Go compiler net test failing
http://bugs.dragonflybsd.org/issues/3205#c
Issue #3205 has been updated by tuxillo.
Status changed from New to In Progress
Assignee set to tuxillo
Can you provide the steps to reproduce it? I'll try to bisect it. Also, are you
sure you've updated world+kernel to latest?
Bug #3205: Go compiler net
Issue #3205 has been reported by t_dfbsd.
Bug #3205: Go compiler net test failing
http://bugs.dragonflybsd.org/issues/3205
* Author: t_dfbsd
* Status: New
* Priority: High
* Assignee:
* Category:
* Target version:
---
Issue #3204 has been updated by tkusumi.
Status changed from Feedback to Closed
Bug #3204: tmux(1) is broken
http://bugs.dragonflybsd.org/issues/3204#change-13795
* Author: tkusumi
* Status: Closed
* Priority: High
* Assignee: tuxillo
* Category:
* Targe
Issue #3203 has been updated by tkusumi.
Status changed from New to Closed
Bug #3203: Don't assume pthread_t is a pointer
http://bugs.dragonflybsd.org/issues/3203#change-13794
* Author: tkusumi
* Status: Closed
* Priority: Normal
* Assignee:
* Category:
Issue #3204 has been updated by tuxillo.
Status changed from In Progress to Feedback
master packages uploaded, please test.
Bug #3204: tmux(1) is broken
http://bugs.dragonflybsd.org/issues/3204#change-13793
* Author: tkusumi
* Status: Feedback
* Priority
Issue #3204 has been updated by tuxillo.
Status changed from New to In Progress
Assignee set to tuxillo
Priority changed from Normal to High
There have been some changes in master that broke the ABI compatibility with
the current master packages, see
http://lists.dragonflybsd.org/pipermail/user
Issue #3204 has been reported by tkusumi.
Bug #3204: tmux(1) is broken
http://bugs.dragonflybsd.org/issues/3204
* Author: tkusumi
* Status: New
* Priority: Normal
* Assignee:
* Category:
* Target version:
tmux(1)
Issue #3198 has been updated by ftigeot.
Among the three choices, I'd say get the R7 240.
- R5 230: are rebadged models and variants of your existing chips. they will
most likely exhibit the same issue.
- RX550: it's a new generation and equires the amdgpu driver.
A port of the driver is almos
Issue #3203 has been reported by tkusumi.
Bug #3203: Don't assume pthread_t is a pointer
http://bugs.dragonflybsd.org/issues/3203
* Author: tkusumi
* Status: New
* Priority: Normal
* Assignee:
* Category:
* Target version:
--
Issue #3202 has been reported by mneumann.
Bug #3202: Cannot boot from HAMMER2
http://bugs.dragonflybsd.org/issues/3202
* Author: mneumann
* Status: New
* Priority: Normal
* Assignee:
* Category: Kernel
* Target version: master
---
Issue #3198 has been updated by yellowrabbit2010.
Thanks for your work.
As I understand it, you have video cards of this type that do not show any
glitches.
At a local store I can purchase R7 240, R5 230 or RX 550.
Bug #3198: OpenGL app crash with Rade
Issue #3198 has been updated by ftigeot.
Status changed from In Progress to Resolved
I sadly wasn't able to find the source of the crash among the differences we
still have with Linux in the drm code.
It could well be an existing bug in the drm/ttm code of the Linux version we
are using right
Issue #3187 has been updated by dillon.
Assignee set to dillon
I am going to guess that it is an interaction with the encrypted swap that is
causing the problem.
Try turning off encryption on your swap partition (in your /etc/fstab), reboot,
and see if the problem reoccurs.
-Matt
---
Issue #3199 has been updated by tse.
Sorry, using `ide` does expose two new disks in /dev/serno, but attempting to
format the first gives
/home/tse# newfs_hammer2 /dev/serno/50026B725502A482
Volume /dev/serno/50026B725502A482 siz
Issue #3199 has been updated by tse.
The hang on shutdown is caused by doing `doas reboot`. Any other command does
a clean shutdown -- i.e. `sudo reboot`, `doas poweroff`, etc
So there is something wrong with `doas reboot`?
I still don't know what caused the hard disk to be inaccessible. App
Issue #3198 has been updated by yellowrabbit2010.
File core.txt.3 added
Very fast crash in the FreeCAD when trying to open a file with a model.
<118>Aug 16 08:17:07 fly kernel: [drm] Initialized radeon 2.45.0 20080528
panic: BUG in ttm_bo_add_to_lru at /usr/src/sys/dev/drm/drm/../ttm/ttm_bo.c:173
Issue #3198 has been updated by yellowrabbit2010.
File core.txt.2 added
Quick crash of KiCad when trying to open the PCB editor.
panic: BUG in ttm_bo_add_to_lru at /usr/src/sys/dev/drm/drm/../ttm/ttm_bo.c:173
cpuid = 0
Trace beginning at frame 0xf803ab7bb198
ttm_bo_add_to_lru() at ttm_bo_add_
Issue #3198 has been updated by yellowrabbit2010.
File messages added
After about half an hour working with Chromium, at the moment when I moved the
mouse, the Xorg died:(
kernel: ttm_bo_wait(): ret = 1
Bug #3198: OpenGL app crash with Radeon driver
ht
Issue #3198 has been updated by yellowrabbit2010.
File core.txt.0 added
v5.7.0-241-g7cc1c1be6e
Improvement is obvious! I was able to launch several glxgears and a cuberender.
Also, chromium did not crash.
Good (always repeatable) kernel panics with MPV with VDPAU as output.
I still need to che
Issue #3198 has been updated by ftigeot.
Status changed from New to In Progress
I have pushed a new branch to leaf with a possible fix:
drm_ttm_radeon_4_7_10_rebased_v2
Can you check if this improve the situation on your hardware ?
Bug #3198: OpenGL app
Issue #3198 has been updated by ftigeot.
The pager read error appears to always be from this chunk of code in
ttm/ttm_bo_vm.c around line 550:
```
/*
* Wait for buffer data in transit, due to a pipelined
* move.
*/
if (test_bit(TTM_BO_PRIV_FLAG_MOVING,
Issue #3187 has been updated by t_dfbsd.
File dmesg.boot added
File fstab added
Adding some machine info:
Samsung 1TB SSD containing:
- 60GB encrypted swap (via fstab crypt option)
- encrypted root
Data drives:
- 10TB SATA encrypted primary
- 8TB SATA encrypted backup (hammer-mirrored PFSes fro
Issue #3200 has been updated by peeter.
The machine is intel i7 skylake (i7-6700).
Bug #3200: master: weston screen freezes
http://bugs.dragonflybsd.org/issues/3200#change-13774
* Author: peeter
* Status: New
* Priority: Normal
* Assignee:
* Category:
Issue #3200 has been updated by peeter.
OK this bug has now become my daily companion. Can't find the deadlock.
Bug #3200: master: weston screen freezes
http://bugs.dragonflybsd.org/issues/3200#change-13773
* Author: peeter
* Status: New
* Priority: Norm
Issue #3197 has been updated by justin.
tse wrote:
> Feel free to change the wording or anything else; or ask for any changes.
This works well - I imagine 95% of the use cases are going to be "upgrade
within current version" or "move to next release" so I want that to be as
little guesswork a
Issue #3200 has been reported by peeter.
Bug #3200: master: weston screen freezes
http://bugs.dragonflybsd.org/issues/3200
* Author: peeter
* Status: New
* Priority: Normal
* Assignee:
* Category:
* Target version:
--
Issue #3199 has been reported by tse.
Bug #3199: PFS label not found panic
http://bugs.dragonflybsd.org/issues/3199
* Author: tse
* Status: New
* Priority: Normal
* Assignee:
* Category:
* Target version:
Are the
Issue #3198 has been updated by yellowrabbit2010.
You're right. I got the same commit (fca8eb81f38c6d4b27e5fa79e030f0647dee0739)
as the first one demonstrating a bug in glxgears.
And you are probably right as well in the fact that this commit is not the
cause of failures, it just makes the pro
Issue #3198 has been updated by ftigeot.
I have pushed drm_ttm_radeon_3_19_8_bisect_vmfault to leaf and bisected what I
could myself.
(It can be necessary to comment out drm/i915 from the tree to build
successfully)
The first bad commit in that branch is fca8eb81f38c6d4b27e5fa79e030f0647dee073
Issue #3197 has been updated by tse.
File upgrade3 added
Hiya,
I think this gives you what you asked for:
Upgrading to HEAD can be equally done with '-r 0' or '-r unstable' or even '-r
master' and '-r 273ce6e304'
Upgrading to the latest release can be done with '-r 1' '-r stable' or even '-r
Issue #3198 has been updated by yellowrabbit2010.
The first commit on which the glxgears error occurs (vm_fault: pager read
error) is 7dcf36dc33228b5b368783d7b6f7ada00ee671d6 on master (Thu Jun 20,
drm/radeon: Upgrade to Linux 3.19.8).
Is there a branch with individual changes?
---
Issue #3197 has been updated by tse.
Or something like '-r stable' and '-r unstable' would be easy to add
Bug #3197: DragonFly upgrades
http://bugs.dragonflybsd.org/issues/3197#change-13767
* Author: tse
* Status: New
* Priority: Normal
* Assignee:
* Ca
Issue #3197 has been updated by tse.
File upgrade2 added
Yup, lets leave the Makefile
> Let's go even simpler - if a branch isn't named, as either RELEASE, HEAD, or
> (Git commit ID), assume that it's an update of whatever branch is currently
> in place. No menus or choices needed.
For myself
Issue #3197 has been updated by justin.
tse wrote:
> If people don't pass a [ -r RELEASE ], then the script will give the release
> options to select from
Let's go even simpler - if a branch isn't named, as either RELEASE, HEAD, or
(Git commit ID), assume that it's an update of whatever branch
Issue #3197 has been updated by tse.
You're right, some people will want HEAD, and seeing @yellowrabbit do a commit
bisect, a one liner upgrade to named commit would also be nice
I wanted to avoid required flags, so people don't have to re-look them up, but
an optional flag like [ -r HEAD | CO
Issue #3197 has been updated by justin.
tse wrote:
> 4.8 looks good to me. Feel free to re-download and try it out
I am not sure how to describe this exactly, but I'm thinking it would be better
as an action - upgrade --release for the current release version, 'upgrade
--bleedingedge' or simil
Issue #3198 has been updated by yellowrabbit2010.
File IMG_20190727_194932_HDR.jpg added
Thanks! Yes, the trick with disabled acceleration allows to work without
failures on the kernel 4685ca1cc305dbcd40d614ecc70f60a6a71ba453 :)
I, on the other hand, built the working kernels until March 20, 2
Issue #3198 has been updated by ftigeot.
I managed to dig up an old Radeon HD5450 which appears to exhibit the bug.
There is no fix yet, but a workaround.
Disabling acceleration in xorg.conf will stop the crashes from happening.
Adding the line Option "NoAccel" "TRUE" in a Device section should
Issue #3198 has been updated by yellowrabbit2010.
File IMG_20190724_210557_HDR-min.jpg added
File vga.txz added
Unfortunately, this commit is already bad:(
I will try to build a working kernel of an earlier version.
Bug #3198: OpenGL app crash with Radeon
Issue #3198 has been updated by ftigeot.
Thanks for this bug report.
The issue looks to be hardware-specific though; I cannot reproduce it at will
on any of my machines.
The branch drm_ttm_radeon_4_4_180_v1 on leaf contains the individual changes
leading to the Linux 4.4.180 update.
Can you b
Issue #3198 has been updated by yellowrabbit2010.
I use the core of the March version -> I use the kernel from March
Bug #3198: OpenGL app crash with Radeon driver
http://bugs.dragonflybsd.org/issues/3198#change-13757
* Author: yellowrabbit2010
* Status
Issue #3198 has been reported by yellowrabbit2010.
Bug #3198: OpenGL app crash with Radeon driver
http://bugs.dragonflybsd.org/issues/3198
* Author: yellowrabbit2010
* Status: New
* Priority: High
* Assignee:
* Category: Driver
* Target version:
Issue #3197 has been updated by tse.
File upgrade added
4.8 looks good to me. Feel free to re-download and try it out
Notes:
The script uses 'fetch depth=1' which reduces the initial download by ~250MB.
But developers who want full history can do '/usr/upgrade; cd /usr/src; git
fetch --unshal
Issue #3197 has been updated by tse.
File upgrade added
Hiya,
I realize this is quite a simple script, and possibly misses useful features
(?). Originally posted to @users, but mailing list line-wraping didn't keep the
script fully intact, so copy/paste/test wouldn't of worked
Also, the respo
Issue #3197 has been reported by tse.
Bug #3197: DragonFly upgrades
http://bugs.dragonflybsd.org/issues/3197
* Author: tse
* Status: New
* Priority: Normal
* Assignee:
* Category: Feature request
* Target version:
Issue #3196 has been reported by tuxillo.
Bug #3196: test issue after redmine upgrade (2)
http://bugs.dragonflybsd.org/issues/3196
* Author: tuxillo
* Status: New
* Priority: Normal
* Assignee:
* Category:
* Target version:
-
Issue #3195 has been updated by tuxillo.
Status changed from New to Closed
closing (test 9 :)
Bug #3195: test issue after redmine upgrade
http://bugs.dragonflybsd.org/issues/3195#change-13751
* Author: tuxillo
* Status: Closed
* Priority: High
* Assignee
Issue #3195 has been updated by tuxillo.
test 8
Bug #3195: test issue after redmine upgrade
http://bugs.dragonflybsd.org/issues/3195#change-13750
* Author: tuxillo
* Status: New
* Priority: High
* Assignee:
* Category:
* Target version:
--
Issue #3195 has been updated by tuxillo.
test 3 (sorry!)
Bug #3195: test issue after redmine upgrade
http://bugs.dragonflybsd.org/issues/3195#change-13744
* Author: tuxillo
* Status: New
* Priority: High
* Assignee:
* Category:
* Target version:
-
Issue #3195 has been updated by tuxillo.
test 3 (sorry!)
Bug #3195: test issue after redmine upgrade
http://bugs.dragonflybsd.org/issues/3195#change-13744
* Author: tuxillo
* Status: New
* Priority: High
* Assignee:
* Category:
* Target version:
-
Issue #3195 has been updated by tuxillo.
test 3 (sorry!)
Bug #3195: test issue after redmine upgrade
http://bugs.dragonflybsd.org/issues/3195#change-13744
* Author: tuxillo
* Status: New
* Priority: High
* Assignee:
* Category:
* Target version:
-
Issue #270 has been updated by tuxillo.
Description updated
Category set to Other
Status changed from New to Resolved
Assignee changed from 0 to tuxillo
Target version set to master
This doesn't happen anymore with 'gnome-mplayer' as it is called now in DPorts.
--
Issue #270 has been updated by tuxillo.
Description updated
Category set to Other
Status changed from New to Resolved
Assignee changed from 0 to tuxillo
Target version set to master
This doesn't happen anymore with 'gnome-mplayer' as it is called now in DPorts.
--
Issue #270 has been updated by tuxillo.
Description updated
Category set to Other
Status changed from New to Resolved
Assignee changed from 0 to tuxillo
Target version set to master
This doesn't happen anymore with 'gnome-mplayer' as it is called now in DPorts.
--
Issue #270 has been updated by tuxillo.
Description updated
Category set to Other
Status changed from New to Resolved
Assignee changed from 0 to tuxillo
Target version set to master
This doesn't happen anymore with 'gnome-mplayer' as it is called now in DPorts.
--
Issue #3195 has been updated by tuxillo.
test 2
Bug #3195: test issue after redmine upgrade
http://bugs.dragonflybsd.org/issues/3195#change-13741
* Author: tuxillo
* Status: New
* Priority: High
* Assignee:
* Category:
* Target version:
--
Issue #3195 has been updated by tuxillo.
test 2
Bug #3195: test issue after redmine upgrade
http://bugs.dragonflybsd.org/issues/3195#change-13741
* Author: tuxillo
* Status: New
* Priority: High
* Assignee:
* Category:
* Target version:
--
Issue #3195 has been updated by tuxillo.
test 2
Bug #3195: test issue after redmine upgrade
http://bugs.dragonflybsd.org/issues/3195#change-13741
* Author: tuxillo
* Status: New
* Priority: High
* Assignee:
* Category:
* Target version:
--
Issue #3183 has been updated by t_dfbsd.
Status changed from New to Closed
Closing this ticket. The Go team found a bug in the crypto/tls build test. From
comments:
"crypto/tls: deflake localPipe in tests
The localPipe implementation assumes that every successful net.Dial
results in exactly on
Issue #3194 has been updated by benjolitz.
Addendum: this is really funny, but may be useful in determining what the exact
issue is.
I had an error in my init that caused the ``hammer mirror-stream`` for a PFS to
be launched *twice*.
Bug #3194: Hammer
Issue #3194 has been updated by benjolitz.
File IMG_0165.HEIC added
attached photo of what I transcribed from.
Bug #3194: Hammer kernel crash on mirror-stream of PFS after upgrade (assertion
"cursor->flags & HAMMER_CURSOR_ITERATE_CHECK" failed in hammer_
Issue #3194 has been reported by benjolitz.
Bug #3194: Hammer kernel crash on mirror-stream of PFS after upgrade (assertion
"cursor->flags & HAMMER_CURSOR_ITERATE_CHECK" failed in hammer_btree_iterate)
http://bugs.dragonflybsd.org/issues/3194
* Author: be
Issue #3183 has been updated by t_dfbsd.
Thw Go team has posted an update on this bug:
https://github.com/golang/go/issues/29583
Bug #3183: Go builder: failures connecting to locally created webservice during
build tests
http://bugs.dragonflybsd.org/is
Issue #2971 has been updated by liweitianux.
Status changed from Feedback to Resolved
peeter, thank you for providing more information on this issue.
By the way, I've been running DragonFly BSD with HAMMER1 on an old machine for
the last ~2 years, and never see such an issue or similar ones.
A
Issue #2971 has been updated by peeter.
I should note that this was not a memory issue. I tested memory very
thoroughly. Also, the system has been running very reliably over the recent 1.5
yrs, definitely not a memory problem.
--
Bug #2971: kernel 4.7
Issue #2971 has been updated by peeter.
Hello
I believe you can close this. I have no means of testing any more, I've long
migrated to HAMMER2. Also, DragonFly has undergone many changes since the
report.
Cheers
Peeter
--
Bug #2971: kernel 4.7: b
Issue #2404 has been updated by herrgard.
Description updated
Status changed from New to Closed
Puffs removed with commit ee3ebee6341d385ab1e8f63b026efd8eeb72a25f so closing
this.
Bug #2404: cp from dir mounted with mount_psshfs fails on mmap -1 errno 22
Issue #2707 has been updated by liweitianux.
Status changed from Feedback to Resolved
Has been resolved by profmakx.
Bug #2707: physical memory corruption with intel gpu 4500HD
http://bugs.dragonflybsd.org/issues/2707#change-13729
* Author: jorisgio
* St
Issue #2789 has been updated by liweitianux.
Status changed from New to Resolved
This issue has been answered.
The 'cryptodev' module (built-in by default) must be loaded for using tcplay(8).
Bug #2789: re: Tcplay ---> Could not open /dev/crypto
http://b
Issue #3048 has been updated by liweitianux.
Status changed from New to Resolved
Well, natacontrol(8) only controls nata(4) devices, such as 'ad*', 'cd*',
'acd*', but cannot control virtio(4) as well as ahci(4) devices.
Bug #3048: natacontrol & virtio
ht
Issue #2971 has been updated by liweitianux.
Status changed from New to Feedback
Hello. Any new findings to this issue?
Buildworld has been run many times on HAMMER, and we haven't gotten another
similar issue report. The memory issue suggested by sephe may better explain
this issue.
--
Issue #2983 has been updated by liweitianux.
Status changed from New to Resolved
This issue has been answered and I don't think it's relevant now, due to the
significantly updated graphical stack in DragonFly BSD as well as Xorg/drivers
in DPorts.
Bug #
Issue #3045 has been updated by liweitianux.
Status changed from New to Resolved
This issue has been answered.
Sephe suggested not to use 'fastforwarding'.
Bug #3045: net.inet.ip.fastforwarding causes PF NAT to break/duplicate packets
http://bugs.dragonf
Issue #3081 has been updated by liweitianux.
Status changed from New to Resolved
This is a dports/3rd-party problem that may be not really related to DragonFly
BSD. Also, this issue was answered but got no feedback. I regard this issue
has been resolved.
-
Issue #3127 has been updated by liweitianux.
Status changed from In Progress to Resolved
The reporter said this issue had been resolved.
Bug #3127: DragonFly 5.1: panic: assertion "count & TOK_COUNTMASK" failed in
_lwkt_reltokref at /usr/src/sys/kern/lwk
Issue #3047 has been updated by samuel.
That issue was possibly/probably related to filling up all available disk
space (60GB at the time)
I have tried to avoid that possibility since then, and brought some
external drives for dfly
So I've not seen it again... but also I've worked hard to not s
Issue #3027 has been updated by liweitianux.
Category changed from Other to installer
Priority changed from High to Normal
Related issue: #2316
Bug #3027: installer: password do not allow special characters
http://bugs.dragonflybsd.org/issues/3027#change-
Issue #2318 has been updated by liweitianux.
Description updated
Status changed from New to Resolved
This issue has been resolved. What's more, the audio subsystem has been synced
with FreeBSD since then.
Bug #2318: snd_emu10k1 produces only stuttering
Issue #2405 has been updated by liweitianux.
Description updated
Status changed from New to Resolved
PUFFS and mount_psshfs have been removed.
Bug #2405: Permission issue with mount_psshfs and user mount
http://bugs.dragonflybsd.org/issues/2405#change-137
Issue #2446 has been updated by liweitianux.
Status changed from Feedback to Resolved
This issue has been resolved.
Bug #2446: make buildkernel fails for DragonflyBSD 3.2.1 or later if INVARIANTS
option is not defined in the kernel config file.
http://bu
Issue #2669 has been updated by liweitianux.
Status changed from New to Resolved
No response from the reporter.
Current DragonFly BSD shouldn't have such keyboard issues, so this issue can be
closed.
Bug #2669: Install ISO of 3.6.2-REL doesn't see keybo
Issue #2628 has been updated by liweitianux.
HostAP was removed from base. WPA-suuplicant is still in base but needs an
update.
Bug #2628: Vendor branch update for WPA-Supplicant and HostAPD
http://bugs.dragonflybsd.org/issues/2628#change-13712
* Autho
Issue #2633 has been updated by liweitianux.
Status changed from New to Resolved
The audio subsystem has been synced with FreeBSD. So this issue can be closed.
Bug #2633: Audio overhaul, bring OSS up to FreeBSD
http://bugs.dragonflybsd.org/issues/2633#ch
Issue #2656 has been updated by liweitianux.
Status changed from In Progress to Resolved
This bug was obsoleted by bug #2657 (A duplicate of this bug but has more info).
Bug #2656: Needs acl to migrate our servers
http://bugs.dragonflybsd.org/issues/2656#
Issue #2953 has been updated by swildner.
As I read the standard, open() should return EEXIST as soon as the file exists
and O_EXCL and O_CREAT are passed, without further conditions.
Bug #2953: open(2) returns "Permission denied" instead of "File exist
Issue #2817 has been updated by liweitianux.
Status changed from New to Resolved
This issue was answered and can be closed.
Bug #2817: Permission checking for utimes(2) and friends are not properly
honoured
http://bugs.dragonflybsd.org/issues/2817#change
Issue #2856 has been updated by liweitianux.
Status changed from New to Resolved
The reported issue was answered and is not relevant now.
Bug #2856: build failed for some dport packages due to automake update
http://bugs.dragonflybsd.org/issues/2856#chang
Issue #2884 has been updated by liweitianux.
Status changed from In Progress to Resolved
The installer by default prepares the disk with a "/boot" partition, so this
issue should have been resolved (at least with recent several releases).
Bug #2884: the
Issue #3015 has been updated by liweitianux.
Status changed from New to Resolved
The code is actually right, but not obvious. I've improved the code against
NetBSD and make this code clearer.
Bug #3015: sbin/gpt/show.c:133: do we always find what we are
Issue #2935 has been updated by liweitianux.
Status changed from New to Resolved
I've updated the jail(8) man page. Resolved this.
Bug #2935: jail.allow_raw_sockets and jail.chflags_allowed undocumented
http://bugs.dragonflybsd.org/issues/2935#change-136
Issue #2951 has been updated by liweitianux.
Status changed from New to Resolved
This issue has been fixed in 2016.
Bug #2951: clock_gettime always repots 0 sec, 0 nsec
http://bugs.dragonflybsd.org/issues/2951#change-13698
* Author: zhtw
* Status: Resolv
Issue #3047 has been updated by liweitianux.
Hello. Do you have similar issues with recent DragonFly BSD? Thank you.
Bug #3047: HAMMER critical write error
http://bugs.dragonflybsd.org/issues/3047#change-13697
* Author: samuel
* Status: New
* Priority:
Issue #3055 has been updated by liweitianux.
Hello. Is this issue resolved with the latest master/release? The HAMMER2 has
gained significant improvements. Thank you.
Bug #3055: HAMMER2 crash + LK_RELEASE fail
http://bugs.dragonflybsd.org/issues/3055#
Issue #3096 has been updated by liweitianux.
Status changed from New to Feedback
Hi, the VM subsystem has been significantly improved recently (also released as
5.6). Are you running the latest DragonFly BSD and do you have the same
issues? Thank you.
Issue #3124 has been updated by liweitianux.
Any feedback or more info about this issue? Otherwise, I'd like to close this
bug later.
By the way, DragonFly BSD works well with UEFI (on real machines or VirtualBox
or VMWare).
Bug #3124: DragonFlyBSD 5.
Issue #3150 has been updated by liweitianux.
Status changed from New to Resolved
We're working on updating radeon and bringing in amdgpu. However, there is no
plan for nouveau at the moment.
Nvidia GPU works with UEFI framebuffer (with Xorg scfb driver), better than
VESA.
---
401 - 500 of 2596 matches
Mail list logo
