[DragonFlyBSD - Bug #2650] (In Progress) ALTQ CFQ panic when changing bandwidth settings

Issue #2650 has been updated by tuxillo. Status changed from New to In Progress Apparently this was already reported and solved in 5a24ba58db9ae867d4df58157fdb10edd94cb4b4. Will try to verify it anyways. Bug #2650: ALTQ CFQ panic when changing bandwidth

[DragonFlyBSD - Bug #1465] (Closed) gdb does not remove breakpoints on detach

Issue #1465 has been updated by tuxillo. Status changed from Feedback to Closed Bug #1465: gdb does not remove breakpoints on detach http://bugs.dragonflybsd.org/issues/1465#change-11834 * Author: corecode * Status: Closed * Priority: Normal * Assignee:

[DragonFlyBSD - Bug #1469] (In Progress) Hammer history security concern

systems have damaged your Master Boot Record, you can reinstall it with boot0cfg(8). See man boot0cfg for details. $ cd /mnt $ cat snap-20140224-0138/mydir/secret.txt mysecretpass $ cat mydir/secret.txt cat: mydir/secret.txt: Permission denied I also think the first proposal of only allowing owners

[DragonFlyBSD - Bug #847] processes getting stuck on mount point

Issue #847 has been updated by tuxillo. File mount_nfs01.diff added Hi, Attached a (draft) patch for mounting NFS with 'intr' by default. Cheers, Antonio Huete Bug #847: processes getting stuck on mount point

[DragonFlyBSD - Bug #1255] (Closed) creating hammer pfs is more complicated than expected

Issue #1255 has been updated by tuxillo. Status changed from In Progress to Closed Hi, With the following commit: commit 5f22d366f0149afba788dcc6ad06e551840ec1ed Author: Thomas Nikolajsen tho...@dragonflybsd.org Date: Wed Apr 20 00:18:20 2011 +0200 hammer.8: improve general description

[DragonFlyBSD - Bug #2473] Kernel crash when trying to up the wpi0 device (Dfly v3.3.0.758.g47388-DEVELOPMENT)

Issue #2473 has been updated by swildner. I mean when someone did e.g. ifconfig wpi0 up instead of ifconfig wlan0 up. Bug #2473: Kernel crash when trying to up the wpi0 device (Dfly v3.3.0.758.g47388-DEVELOPMENT)

[DragonFlyBSD - Bug #2091] wpi causes kernel crash

Issue #2091 has been updated by swildner. Duplicates Bug #2473: Kernel crash when trying to up the wpi0 device (Dfly v3.3.0.758.g47388-DEVELOPMENT) added Bug #2091: wpi causes kernel crash http://bugs.dragonflybsd.org/issues/2091#change-11845 * Author:

[DragonFlyBSD - Bug #2091] (Closed) wpi causes kernel crash

Issue #2091 has been updated by swildner. Description updated Status changed from New to Closed Assignee deleted (0) Closing this one, please see my comment in the similar/identical #2473. Bug #2091: wpi causes kernel crash

[DragonFlyBSD - Bug #1682] (Closed) math.h constants, aren't constant

Issue #1682 has been updated by swildner. Description updated Status changed from Feedback to Closed This no longer fails. Closing. Bug #1682: math.h constants, aren't constant http://bugs.dragonflybsd.org/issues/1682#change-11848 * Author: Beket *

[DragonFlyBSD - Bug #2588] (Closed) xz(1) broken on DragonFly 3.5

Issue #2588 has been updated by swildner. Status changed from New to Closed Closing this for now. It seems to not have been a general issue. Please reopen if there are any issues still. Bug #2588: xz(1) broken on DragonFly 3.5

[DragonFlyBSD - Bug #2635] Stablize drm/radeon KMS drivers for new xorg

Issue #2635 has been updated by jorisgio. File core.txt.8 added File dmesg added Hi, With kernel v3.7.1.747.g4fd11-DEVELOPMENT, I have a new panic. See core files : http://leaf.dragonflybsd.org/~joris/vmcore.ttm http://leaf.dragonflybsd.org/~joris/kern.ttm The radeonkms module loads and

[DragonFlyBSD - Bug #911] (Feedback) kldload/kernel linker can exceed malloc reserve and panic system

Issue #911 has been updated by tuxillo. File 64MB_X64.jpg added Status changed from In Progress to Feedback Hi, 64MB is very low mem capacity nowadays, at least for the platforms we support. Real kernels can't even boot with low mem profiles. For example, i386 can't boot on 32MB and x86_64

[DragonFlyBSD - Bug #2454] (Closed) Kernel Panic accessing ext2fs

Issue #2454 has been updated by tuxillo. Description updated Category set to VFS subsystem Status changed from Feedback to Closed Target version set to 3.8.0 Hi, Panic reported was fixed. To know more on how to use ext2fs on DragonFly BSD, check this:

[DragonFlyBSD - Bug #2333] (Feedback) submit and this site are silently tied together

Issue #2333 has been updated by tuxillo. Description updated Category set to Bugtracker Status changed from New to Feedback Assignee set to tuxillo Hi Justin, Do you mean Submit should be opened even for anonymous users? How will we control the spam then? Also I don't know if individual

[DragonFlyBSD - Bug #908] (Closed) mention msleep() in porting_drivers.txt

Issue #908 has been updated by tuxillo. Description updated Category set to Documentation Status changed from In Progress to Closed Target version set to 3.8.0 Hi, MSLEEP/TSLEEP conversion is already mentioned in doc/porting_drivers.txt Closing this one. Cheers, Antonio Huete

[DragonFlyBSD - Bug #1886] (Feedback) ath/wpa_supplicant/dhclient lost connection

Issue #1886 has been updated by tuxillo. Category set to Networking Status changed from In Progress to Feedback Target version set to 3.8.0 Hi guys, Can anybody please provide a coredump when this issue happens? If not, Are there instructions on how to trigger it? Does it happen with other

[DragonFlyBSD - Bug #2333] submit and this site are silently tied together

Issue #2333 has been updated by memmerto. A gross hack would be to filter all inbound submit@ mail through a generic spam processing suite (eg, spamassassin + postgrey) and if clean inject it into redmine. This should keep most of the legitimate spam out while letting valid submit@ traffic

[DragonFlyBSD - Bug #159] (Rejected) ipsec-tools patch

Issue #159 has been updated by tuxillo. Category set to Other Status changed from In Progress to Rejected Target version set to 3.8.0 Hi, This should be reported to https://github.com/DragonFlyBSD/DPorts By the way, latest failure could be found in:

[DragonFlyBSD - Bug #953] (Closed) dma.c: some errors

Issue #953 has been updated by tuxillo. Category set to Other Status changed from In Progress to Closed Target version set to 3.8.0 Hi, Since point 3 is the only remaining one and it's reported in https://github.com/corecode/dma/issues/15 , I'm closing this issue. Cheers, Antonio Huete

[DragonFlyBSD - Bug #223] (Closed) use bus_dma in i386/isa/clock.c

Issue #223 has been updated by tuxillo. Status changed from Feedback to Closed Hi, There are no warnings at all. In fact it is built with -Werror: [...] cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual