[DragonFlyBSD - Bug #2622] VAIO FIT15E fn keys support
Issue #2622 has been updated by swildner. Can you fetch and apply the following patch: http://leaf.dragonflybsd.org/~swildner/0001-WIP-spic-4-driver.patch and put in your kernel config: device spic0 at isa? irq 0 port 0x10a0 and rebuild the kernel / reboot. After that, please tell me if using the Fn keys that don't work will generate messages on the console, and if so, which specific message for which key is printed. I am not sure if acpi_sony.ko will have to be loaded at the same time, so if it doesn't work without, please try with it loaded too. Thanks, Sascha Bug #2622: VAIO FIT15E fn keys support http://bugs.dragonflybsd.org/issues/2622#change-11691 * Author: nonsolosoft * Status: New * Priority: Normal * Assignee: * Category: Wish * Target version: Sony Vaio Fit15E is not supported by acpi_sony.ko so it's not possibile from keyboard to reduce brightness, activate of deactive trackpad, volume and so on. Here there is a acpidump -d -v : http://paste.scsys.co.uk/287740 I'll appreciate anyone able to add support of this laptop to dragonflybsd. Thank you in advance, \ferz ---Files dmesg.ubuntu (53.1 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2575] (Closed) Dell PERC 4e/Di causes crash on boot
Issue #2575 has been updated by swildner. Status changed from In Progress to Closed Fixed in master and 3.4 branch. Bug #2575: Dell PERC 4e/Di causes crash on boot http://bugs.dragonflybsd.org/issues/2575 Author: justin Status: Closed Priority: Normal Assignee: Category: Target version: Booting up an older Dell 2950 with the DragonFly 3.4.2 release ISO, with a PERC 4e/Di RAID controller, causes a crash. Here's what's left on the console. hptrr: no controller detected hpt27xx: no controller detected. amr0: delete logical drives supported by controller amrp1.amr0.pci2.pcib2.pci1.pcib1.pci0.pcib0.acpi0.nexus0.root0 amrp1 [tentative] on amr0 Fatal trap 12: page fault while in kernel mode cpuif = 0; lapic->id = fault virtual address = 0xe68 fault code = supervisor write data, page not present instruction pointer = 0x8:0x8031822b stack pointer = 0x10:0x824ec9f0 frame pointer = 0x10:0x824eca50 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 current thread = pri 12 kernel: type 12 trap, code=2 CPU0 stopping CPUs: 0x000e stopped Stopped at amr_cam_attach+0x19:movq $0,0xe70(%rax) db> trace amr_cam_attach() at amr_cam_attach+0x19 0x8031822b device_doattach() at device_doattach+0x3e 0x80522960 device_probe_and_attach() at device_probe_and_attach+0x1d2 0x80522f8e bus_generic_attach() at bus_generic_attach+0x1a 0x805230eb amr_startup() at amr_startup+0x10b 0x80316bee run_interrupt_driven_config_hooks() at run_interrupt_driven_config_hooks+0x120 0x8051e600 mi_startup() at mi_startup+0xb1 0x804ce50f -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2575] (In Progress) Dell PERC 4e/Di causes crash on boot
Issue #2575 has been updated by swildner. Status changed from New to In Progress I've pushed a fix to master, please try it out. http://lists.dragonflybsd.org/pipermail/commits/2013-August/130544.html Bug #2575: Dell PERC 4e/Di causes crash on boot http://bugs.dragonflybsd.org/issues/2575 Author: justin Status: In Progress Priority: Normal Assignee: Category: Target version: Booting up an older Dell 2950 with the DragonFly 3.4.2 release ISO, with a PERC 4e/Di RAID controller, causes a crash. Here's what's left on the console. hptrr: no controller detected hpt27xx: no controller detected. amr0: delete logical drives supported by controller amrp1.amr0.pci2.pcib2.pci1.pcib1.pci0.pcib0.acpi0.nexus0.root0 amrp1 [tentative] on amr0 Fatal trap 12: page fault while in kernel mode cpuif = 0; lapic->id = fault virtual address = 0xe68 fault code = supervisor write data, page not present instruction pointer = 0x8:0x8031822b stack pointer = 0x10:0x824ec9f0 frame pointer = 0x10:0x824eca50 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 current thread = pri 12 kernel: type 12 trap, code=2 CPU0 stopping CPUs: 0x000e stopped Stopped at amr_cam_attach+0x19:movq $0,0xe70(%rax) db> trace amr_cam_attach() at amr_cam_attach+0x19 0x8031822b device_doattach() at device_doattach+0x3e 0x80522960 device_probe_and_attach() at device_probe_and_attach+0x1d2 0x80522f8e bus_generic_attach() at bus_generic_attach+0x1a 0x805230eb amr_startup() at amr_startup+0x10b 0x80316bee run_interrupt_driven_config_hooks() at run_interrupt_driven_config_hooks+0x120 0x8051e600 mi_startup() at mi_startup+0xb1 0x804ce50f -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2571] page fault with "dhclient wlan0" (if_ath)
Issue #2571 has been updated by swildner. On Fri, 19 Jul 2013 08:22:11 +0200, Ferruccio Zamuner via Redmine wrote: > First I execute: > > ifconfig wlan0 create wlandev ath0 > wpa_supplicant -i wlan0 -c /etc/wpa_supplicant > > The network is associated, then I run: > > dhclient wlan0 > > and http://db.tt/saNg6Ty3 > > Fatal trap 12: page fault while in kernel mode > Stopped at ath_tx_start+0x976: movl 0x10(%edx),%edx Can you try again with latest freshest? See http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/01d73edb6561f0dfcded4d4a1bd551baf7fcb568, not sure if that's the issue. Sascha Bug #2571: page fault with "dhclient wlan0" (if_ath) http://bugs.dragonflybsd.org/issues/2571 Author: nonsolosoft Status: New Priority: Normal Assignee: Category: Target version: First I execute: ifconfig wlan0 create wlandev ath0 wpa_supplicant -i wlan0 -c /etc/wpa_supplicant The network is associated, then I run: dhclient wlan0 and http://db.tt/saNg6Ty3 Fatal trap 12: page fault while in kernel mode Stopped at ath_tx_start+0x976: movl 0x10(%edx),%edx with trace: http://db.tt/0zPGmorM uname -a DragonFly lap.diff.org 3.5-DEVELOPMENT DragonFly v3.5.0.479.gf14c0-DEVELOPMENT #93: Wed Jul 17 21:48:21 CEST 2013 f...@lap.diff.org:/usr/obj/usr/src/sys/GENERIC i386 -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2566] No space available for static Thread Local Storage
Issue #2566 has been updated by swildner. On Thu, 06 Jun 2013 16:32:19 +0200, Eric Christeson via Redmine wrote: > I first noticed it after building a quickworld from master on Monday, > June 3. The previous known good was Thursday, May 30. My feeling (although I have no clear idea about what happened exactly) is that it is a quickworld issue across the libc version bump. libc in master is libc.so.8. I didn't try a quickworld myself but all boxes I upgraded with a full build do not have this issue. Sascha Bug #2566: No space available for static Thread Local Storage http://bugs.dragonflybsd.org/issues/2566 Author: eric.j.christeson Status: New Priority: Normal Assignee: Category: Target version: I noticed some of my cron jobs not running and upon investigation I found this in /var/log/messages: cron: in try_dlopen(): /usr/lib/security/pam_opie.so.2: /usr/lib/libc.so.7: No space available for static Thread Local Storage su seems to have a similar problem: su: in try_dlopen(): /usr/lib/security/pam_opie.so.2: /usr/lib/libc.so.7: No space available for static Thread Local Storage As a work-around I edited /etc/pam.d/system and commented out the first two auth lines that include pam_opie.so and pam_opieaccess.so obviously if you're not using opie, this won't affect much. I first noticed it after building a quickworld from master on Monday, June 3. The previous known good was Thursday, May 30. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2563] (Closed) Requeue packet for 10G Intel NIC runs out of resources
Issue #2563 has been updated by swildner. Status changed from New to Closed Closing. It was fixed in master & release. Bug #2563: Requeue packet for 10G Intel NIC runs out of resources http://bugs.dragonflybsd.org/issues/2563 Author: ltpig402a Status: Closed Priority: Normal Assignee: Category: Target version: When ixgbe_xmit() returned error to ixgbe_start_locked() due to resource outage, the packet should be re-queued at the head of the packet queue -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2089] (Closed) Fatal trap 9: GPF in kernel mode
Issue #2089 has been updated by swildner. Status changed from New to Closed Closing, it was fixed recently. Bug #2089: Fatal trap 9: GPF in kernel mode http://bugs.dragonflybsd.org/issues/2089 Author: weingart Status: Closed Priority: Normal Assignee: Category: Target version: dfly-x86_64-2.10.1_REL.iso: Running on proxmox 1.8 (linux kvm style VM) tryroot cd0 cd9660: RockRidge Extension Fatal trap 9: general protection fault while in kernel mode instruction pointer = 0x8:0xfff...80701772 stack pointer = 0x10:0xfff...e001716bf0 frame pointer = 0x10:0xfff...e00c39eaf0 ... Stopped at cpu_heavy_restore+0x32: movq 0x320(%rdx),%rdi Trace shows: cpu_heavy_restore() tsleep() vm_pageout_thread() at vm_pageout_thread+0x221 Registers show: can't get rdx... scrolls off screen, and cant seem to get backscroll working. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2528] (Closed) In VirtualBox one of possible network interfaces fails to attach
Issue #2528 has been updated by swildner. Status changed from New to Closed Bug #2528: In VirtualBox one of possible network interfaces fails to attach http://bugs.dragonflybsd.org/issues/2528 Author: kworr Status: Closed Priority: Low Assignee: Category: Target version: After updating to current HEAD and recompiling machine fails to boot trapping at device detection: lnc0: port 0xd000-0xd01f mem 0xf008-0xf00f,0xf000-0xffff irq 19 at device 3.0 on pci0 lnc0: 16 receive buffers, 4 transmit buffers Fatal trap 12: page fault while in kernel mode cpuid = 0; lapic->id = fault virtual address = 0x74 fault code = supervisor write data, page not present instruction pointer = 0x8:0x80767f8f stack pointer = 0x10:0x824e5570 frame pointer = 0x10:0x824e5570 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 current thread = pri 12 kernel: type 12 trap, code=2 CPU0 stopping CPOUs: 0x000e stopped Stopped at lance_stop+0x19: movl $0,0x74(%rdx) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2543] (Closed) man rmdir(2) : add EINVAL to the error section
Issue #2543 has been updated by swildner. Status changed from New to Closed Fix pushed (cd6a8264ce320929480ebadd227f0a8de0763a3d). Thanks! Bug #2543: man rmdir(2) : add EINVAL to the error section http://bugs.dragonflybsd.org/issues/2543 Author: jorisgio Status: Closed Priority: Normal Assignee: Category: Target version: rmdir can return EINVAL if the directory is a mount point : See sys/kern/vfs_syscalls.c:3997 /* * Do not allow directories representing mount points to be * deleted, even if empty. Check write perms on mount point * in case the vnode is aliased (aka nullfs). */ if (nd->nl_nch.ncp->nc_flag & (NCF_ISMOUNTPT)) return (EINVAL); -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2543] man rmdir(2) : add EINVAL to the error section
Issue #2543 has been updated by swildner. POSIX has this to say about EINVAL and EBUSY: [EBUSY] The directory to be removed is currently in use by the system or some process and the implementation considers this to be an error. [EINVAL] The path argument contains a last component that is dot. So I think that we should actually return EBUSY instead of EINVAL for the attempt to rmdir() a directory that is a mount point. Also, I'm not sure if we handle the "last component that is dot" case correctly yet. Bug #2543: man rmdir(2) : add EINVAL to the error section http://bugs.dragonflybsd.org/issues/2543 Author: jorisgio Status: New Priority: Normal Assignee: Category: Target version: rmdir can return EINVAL if the directory is a mount point : See sys/kern/vfs_syscalls.c:3997 /* * Do not allow directories representing mount points to be * deleted, even if empty. Check write perms on mount point * in case the vnode is aliased (aka nullfs). */ if (nd->nl_nch.ncp->nc_flag & (NCF_ISMOUNTPT)) return (EINVAL); -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2538] (Closed) mkisofs hardlink detection broken on HAMMER
Issue #2538 has been updated by swildner. Status changed from New to Closed Disregard what I wrote. Mkisofs is fine and I let myself get fooled by wrongly calculating what takes which space on the ISO. Bug #2538: mkisofs hardlink detection broken on HAMMER http://bugs.dragonflybsd.org/issues/2538 Author: swildner Status: Closed Priority: Normal Assignee: swildner Category: Target version: Running mkisofs on a directory with hard links will count each hard link as a separate file when that directory is on a HAMMER file system and the .iso will be larger than if the directory had been on a UFS. It seems mkisofs's hard link detection (it goes by identical inodes, I guess) isn't working on HAMMER. A very unpleasant side effect of this is that our ISOs are much larger than they could be. In fact, the x86_64 ISO is already exceeding the 750MB mark. This is because /usr/pkg/libexec/git-core has a large number of hard links (over 100) for a >2MB file. I don't think HAMMER is really at fault here and the only thing I can think of right now (without having looked at cdrtools source) is that it could have to do with HAMMER's inodes being 64 bit (?) vs. 32 on UFS. Regards, Sascha -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2540] (Closed) mined editor man page out of conventional order
Issue #2540 has been updated by swildner. Status changed from New to Closed Bug #2540: mined editor man page out of conventional order http://bugs.dragonflybsd.org/issues/2540 Author: eadler Status: Closed Priority: Low Assignee: swildner Category: Target version: mandoc -Tlint reports a minor problem with the mined.1 man page. See attached diff. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2541] (Closed) mined has alignment issues on some architectures
Issue #2541 has been updated by swildner. Status changed from New to Closed Bug #2541: mined has alignment issues on some architectures http://bugs.dragonflybsd.org/issues/2541 Author: eadler Status: Closed Priority: Normal Assignee: swildner Category: Target version: if the alignment of char* does not match the alignment of LINE* mined may fail unexpectedly. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2541] mined has alignment issues on some architectures
Issue #2541 has been updated by swildner. Assignee set to swildner grab Bug #2541: mined has alignment issues on some architectures http://bugs.dragonflybsd.org/issues/2541 Author: eadler Status: New Priority: Normal Assignee: swildner Category: Target version: if the alignment of char* does not match the alignment of LINE* mined may fail unexpectedly. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2540] mined editor man page out of conventional order
Issue #2540 has been updated by swildner. Assignee set to swildner grab Bug #2540: mined editor man page out of conventional order http://bugs.dragonflybsd.org/issues/2540 Author: eadler Status: New Priority: Low Assignee: swildner Category: Target version: mandoc -Tlint reports a minor problem with the mined.1 man page. See attached diff. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2539] (Closed) mined editor man page out of conventional order
Issue #2539 has been updated by swildner. Status changed from New to Closed Bug #2539: mined editor man page out of conventional order http://bugs.dragonflybsd.org/issues/2539 Author: eadler Status: Closed Priority: Low Assignee: Category: Target version: -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2538] mkisofs hardlink detection broken on HAMMER
Issue #2538 has been updated by swildner. Assignee set to swildner Further testing results are inconclusive yet and we're still checking out under which circumstances the issue is present. Bug #2538: mkisofs hardlink detection broken on HAMMER http://bugs.dragonflybsd.org/issues/2538 Author: swildner Status: New Priority: Normal Assignee: swildner Category: Target version: Running mkisofs on a directory with hard links will count each hard link as a separate file when that directory is on a HAMMER file system and the .iso will be larger than if the directory had been on a UFS. It seems mkisofs's hard link detection (it goes by identical inodes, I guess) isn't working on HAMMER. A very unpleasant side effect of this is that our ISOs are much larger than they could be. In fact, the x86_64 ISO is already exceeding the 750MB mark. This is because /usr/pkg/libexec/git-core has a large number of hard links (over 100) for a >2MB file. I don't think HAMMER is really at fault here and the only thing I can think of right now (without having looked at cdrtools source) is that it could have to do with HAMMER's inodes being 64 bit (?) vs. 32 on UFS. Regards, Sascha -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2538] mkisofs hardlink detection broken on HAMMER
Issue #2538 has been reported by swildner. Bug #2538: mkisofs hardlink detection broken on HAMMER http://bugs.dragonflybsd.org/issues/2538 Author: swildner Status: New Priority: Normal Assignee: Category: Target version: Running mkisofs on a directory with hard links will count each hard link as a separate file when that directory is on a HAMMER file system and the .iso will be larger than if the directory had been on a UFS. It seems mkisofs's hard link detection (it goes by identical inodes, I guess) isn't working on HAMMER. A very unpleasant side effect of this is that our ISOs are much larger than they could be. In fact, the x86_64 ISO is already exceeding the 750MB mark. This is because /usr/pkg/libexec/git-core has a large number of hard links (over 100) for a >2MB file. I don't think HAMMER is really at fault here and the only thing I can think of right now (without having looked at cdrtools source) is that it could have to do with HAMMER's inodes being 64 bit (?) vs. 32 on UFS. Regards, Sascha -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2536] (Closed) ndis panic: assertion "IS_SERIALIZED(((ifsq)->ifsq_hw_serialize))"
Issue #2536 has been updated by swildner. Status changed from New to Closed I've pushed it. Bug #2536: ndis panic: assertion "IS_SERIALIZED(((ifsq)->ifsq_hw_serialize))" http://bugs.dragonflybsd.org/issues/2536 Author: herrgard Status: Closed Priority: Normal Assignee: Category: Target version: Hi, I can panic my box using ral+ndis. Create wlan0 the usual way, then uses wpa_supplicant and dhclient. Quickest way to panic is ping -f 192.168.0.1 (or something you can reach fast). DragonFly v3.3.0.1455.g8053c-DEVELOPMENT x86_64 (april 1st) I am unable to get a dump. Box freezes on call dumpsys. Trace: panic: assertion "IS_SERIALIZED(((ifsq)->ifsq_hw_serialize))" failed in ifsq_devstart at /usr/src/sys/net/if.c:368 panic() panic() ifsq_devstart() if_devstart() ndis_starttask() (null)() x86_64_call2() Thanks, Max -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2530] (Closed) Re: Bugs Digest, Vol 7, Issue 25
Issue #2530 has been updated by swildner. Status changed from New to Closed Bug #2530: Re: Bugs Digest, Vol 7, Issue 25 http://bugs.dragonflybsd.org/issues/2530 Author: FilippoMo Status: Closed Priority: Normal Assignee: Category: Target version: 1. [DragonFlyBSD - Bug #2521] (Closed) new dialog locks up on Which snapshot will have this bug fixed? sincerely Filippo -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2452] (Closed) sporadic make -j X buildworld failure
Issue #2452 has been updated by swildner. Status changed from New to Closed It is likely due to a dirty source tree in combination with bmake pickyness, which to me looks more like a bug than a feature. So closing for now. Feel free to re-open if the issue is still observed. Bug #2452: sporadic make -j X buildworld failure http://bugs.dragonflybsd.org/issues/2452 Author: sepherosa Status: Closed Priority: Normal Assignee: dragonflybsd1 Category: Target version: make -j 8 buildworld on Xeon 3430 (4threads) --- libc_r.a --- building static c_r library rm -f libc_r.a ar cq libc_r.a `lorder uthread_accept.o uthread_aio_suspend.o uthread_atfork.o uthread_attr_destroy.o uthread_attr_get_np.o uthread_attr_init.o uthread_attr_getdetachstate.o uthread_attr_getinheritsched.o uthread_attr_getschedparam.o uthread_attr_getschedpolicy.o uthread_attr_getscope.o uthread_attr_getstack.o uthread_attr_getstackaddr.o uthread_attr_getstacksize.o uthread_attr_setcreatesuspend_np.o uthread_attr_setdetachstate.o uthread_attr_setinheritsched.o uthread_attr_setschedparam.o uthread_attr_setschedpolicy.o uthread_attr_setscope.o uthread_attr_setstack.o uthread_attr_setstackaddr.o uthread_attr_setstacksize.o uthread_bind.o uthread_cancel.o uthread_clean.o uthread_close.o uthread_closefrom.o uthread_concurrency.o uthread_cond.o uthread_condattr_destroy.o uthread_condattr_init.o uthread_connect.o uthread_creat.o uthread_create.o uthread_detach.o uthread_dup.o uthread_dup2.o uthread_equal.o uthread_execve.o uthread_exit.o uthread_faccessat.o uthread_fchflags.o uthread_fchmod.o uthread_fchmodat.o uthread_fchown.o uthread_fchownat.o uthread_fcntl.o uthread_fd.o uthread_find_thread.o uthread_flock.o uthread_fork.o uthread_fpathconf.o uthread_fstat.o uthread_fstatat.o uthread_fstatfs.o uthread_fsync.o uthread_gc.o uthread_getdirentries.o uthread_getpeername.o uthread_getprio.o uthread_getschedparam.o uthread_getsockname.o uthread_getsockopt.o uthread_info.o uthread_init.o uthread_ioctl.o uthread_jmp.o uthread_join.o uthread_kern.o uthread_kevent.o uthread_kill.o uthread_kqueue.o uthread_listen.o uthread_main_np.o uthread_mattr_init.o uthread_mattr_kind_np.o uthread_msync.o uthread_multi_np.o uthread_mutex.o uthread_mutex_prioceiling.o uthread_mutex_protocol.o uthread_mutexattr_destroy.o uthread_nanosleep.o uthread_once.o uthread_open.o uthread_pause.o uthread_pipe.o uthread_poll.o uthread_priority_queue.o uthread_read.o uthread_readv.o uthread_recvfrom.o uthread_recvmsg.o uthread_resume_np.o uthread_rwlock.o uthread_rwlockattr.o uthread_select.o uthread_self.o uthread_sem.o uthread_sendfile.o uthread_sendmsg.o uthread_sendto.o uthread_setprio.o uthread_setschedparam.o uthread_setsockopt.o uthread_shutdown.o uthread_sig.o uthread_sigaction.o uthread_sigmask.o uthread_sigpending.o uthread_sigprocmask.o uthread_sigsuspend.o uthread_sigwait.o uthread_single_np.o uthread_sleep.o uthread_socket.o uthread_socketpair.o uthread_spec.o uthread_spinlock.o uthread_stubs.o uthread_suspend_np.o uthread_switch_np.o uthread_system.o uthread_tcdrain.o uthread_unlinkat.o uthread_vfork.o uthread_wait.o uthread_wait4.o uthread_waitpid.o uthread_write.o uthread_writev.o uthread_yield.o _atomic_lock.o | tsort -q` /usr/obj/usr/src/ctools_x86_64_x86_64/usr/libexec/binutils222/elf/nm: 'uthread_accept.o': No such file /usr/obj/usr/src/ctools_x86_64_x86_64/usr/libexec/binutils222/elf/ar: uthread_accept.o: No such file or directory *** [libc_r.a] Error code 1 make: stopped in /usr/src/lib/libc_r 1 error make: stopped in /usr/src/lib/libc_r *** [_SUBDIR_all_libc_r] Error code 2 make: stopped in /usr/src/lib 1 error make: stopped in /usr/src/lib A failure has been detected in another branch of the parallel make make: stopped in /usr/src/lib *** [lib__L] Error code 2 make: stopped in /usr/src .CURDIR='/usr/src' .OBJDIR='/usr/obj/usr/src/world_x86_64/usr/src' .MAKE='make' MAKE_VERSION='20121010' LD_LIBRARY_PATH='' MACHINE_ARCH='x86_64' MACHINE='x86_64' MAKEFILE='/usr/src/Makefile.inc1' .TARGETS='_generic_libs' .ERROR_TARGET='lib__L' .ERROR_META_FILE='' .MAKE.LEVEL='1' .MAKE.MODE='' 1 error make: stopped in /usr/src .CURDIR='/usr/src' .OBJDIR='/usr/obj/usr/src/world_x86_64/usr/src' .MAKE='make' MAKE_VERSION='20121010' LD_LIBRARY_PATH='' MACHINE_ARCH='x86_64' MACHINE='x86_64' MAKEFILE='/usr/src/Makefile.inc1' .TARGETS='_generic_libs' .ERROR_TARGET='lib__L' .ERROR_META_FILE='' .MAKE.LEVEL='1' .MAKE.MODE='' *** [libraries] Error code 2 make: stopped in /usr/src .CURDIR='/usr/src' .OBJDIR='/usr/obj/usr/src/world_x86_64/usr/src' .MAKE='make' MAKE_VERSION='20121010' LD_LIBRARY_PATH='' MACHINE_ARCH='x86_64' MACHINE='x86_64' MAKEFILE='/usr/src/Makefile.inc1' .TARGETS='libraries' .ERROR_TARGET='libraries' .ERROR_META_FILE='' .MAKE.LEVEL='0' .MAKE.MODE='' 1 error make: stopped in /usr/src .CURDIR='/usr/src' .OBJDIR='/usr/obj/usr/src/world_x86_64/usr/src' .MAKE='make' MAKE_VERSION='20121010' LD_LIBRARY_PATH='' MACHINE_ARC
[DragonFlyBSD - Bug #2530] Re: Bugs Digest, Vol 7, Issue 25
Issue #2530 has been updated by swildner. Due to network problems, snapshot building isn't running at the moment. It is expected to be back shortly. The next new snapshots should have this fix included. Bug #2530: Re: Bugs Digest, Vol 7, Issue 25 http://bugs.dragonflybsd.org/issues/2530 Author: FilippoMo Status: New Priority: Normal Assignee: Category: Target version: 1. [DragonFlyBSD - Bug #2521] (Closed) new dialog locks up on Which snapshot will have this bug fixed? sincerely Filippo -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #403] (Closed) error with selecting of timezone
Issue #403 has been updated by swildner. Status changed from New to Closed Assignee deleted (0) I think this should be fixed by http://leaf.dragonflybsd.org/mailarchive/commits/2012-11/msg00174.html Closing for now, feel free to re-open if the problem is still there. Bug #403: error with selecting of timezone http://bugs.dragonflybsd.org/issues/403 Author: redliner Status: Closed Priority: Normal Assignee: Category: Target version: Hrm. I don't understand this ticket. Why is the message empty? Could you please provide details for this? -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2531] camcontrol fails to disable APM
Issue #2531 has been updated by swildner. OK, I've pushed (and MFC'd) a fix that allows turning off APM for disks at least with nata(4). I think in order to have have this for AHCI attached disks too (via camcontrol(8)), we'd have to integrate ATA into CAM like FreeBSD did. But I'm not 100% sure about this. Bug #2531: camcontrol fails to disable APM http://bugs.dragonflybsd.org/issues/2531 Author: m.lombardi85 Status: New Priority: Normal Assignee: Category: Target version: I installed dragonfly BSD on an AMD64 laptop but I have a problem. The hard disk is continuously spinning up and down every few seconds; on FreeBSD I normally execute the following command to disable APM #camcontrol cmd ad0 -c "EF 85 00 00 00 00 00 00 00 00 00 00" but unfortunately it fails on dragonfly with the following error message: camcontrol: error sending command -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #73] (Closed) outb|inb warnings patch
Issue #73 has been updated by swildner. Status changed from Feedback to Closed There are no warnings anymore in the files affected by the two leftover patches (the rest were already removed some months ago). I guess this is due to compiler differences (GCC 4.4 and 4.7 both seem to get along fine with the current code). Bug #73: outb|inb warnings patch http://bugs.dragonflybsd.org/issues/73 Author: slynko Status: Closed Priority: Low Assignee: Category: Target version: Hi, this patch fix warnings produced by macros like outb (see the comment to outb macro in sys/i386/include/cpufunc.h) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #67] (Closed) isa_compat warning patch
Issue #67 has been updated by swildner. Description updated Status changed from New to Closed Assignee deleted (0) COMPAT_OLDISA (and along with it, isa_compat.c) was removed a few months ago. http://leaf.dragonflybsd.org/mailarchive/commits/2012-12/msg00010.html Bug #67: isa_compat warning patch http://bugs.dragonflybsd.org/issues/67 Author: slynko Status: Closed Priority: Low Assignee: Category: Target version: Hi, 1) Add express type cast -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2523] (Closed) route show is stuck in an infinite loop
Issue #2523 has been updated by swildner. Status changed from New to Closed Bug #2523: route show is stuck in an infinite loop http://bugs.dragonflybsd.org/issues/2523 Author: jorisgio Status: Closed Priority: Normal Assignee: Category: Target version: netstat -r prints the routing table, but "route show" does not terminate. As far as i understand, netname is called with a host address instead of a network address, the ip of my nic. Here is a backtrace : Starting program: /usr/src/sbin/route/route show Routing tables Internet: Destination Gateway Flags ^C Program received signal SIGINT, Interrupt. netname (sa=0x80069d0a8) at route.c:465 465 mask = (long)mask >> subnetshift; (gdb) bt #0 netname (sa=0x80069d0a8) at route.c:465 #1 0x0040493e in p_sockaddr (sa=0x80069d0a8, flags=0, width=31) at show.c:343 #2 0x0040464f in p_rtentry (rtm=0x80069d000) at show.c:240 #3 0x0040444d in show (argc=1, argv=0x7798) at show.c:174 #4 0x004006ed in main (argc=1, argv=0x7798) at route.c:192 -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2462] (Closed) These locale symlinks need to be removed
Issue #2462 has been updated by swildner. Status changed from In Progress to Closed Issue fixed with the locale and i18n files upgrade (see 45a9a2ebaf2f5483318be2a12c19b4c477512c7a). Bug #2462: These locale symlinks need to be removed http://bugs.dragonflybsd.org/issues/2462 Author: marino Status: Closed Priority: Normal Assignee: swildner Category: Target version: The following symlinks point to nothing. IMO they should be removed from build and added to Make upgrade to remove from world /usr/share/locale/ca_ES.UTF-8/LC_MESSAGES: No such file or directory /usr/share/locale/ca_ES.UTF-8/LC_MONETARY: No such file or directory /usr/share/locale/ca_ES.UTF-8/LC_NUMERIC: No such file or directory /usr/share/locale/eu_ES.ISO8859-15/LC_TIME: No such file or directory /usr/share/locale/eu_ES.UTF-8/LC_TIME: No such file or directory /usr/share/locale/hy_AM.UTF-8/LC_NUMERIC: No such file or directory /usr/share/locale/kk_KZ.UTF-8/LC_NUMERIC: No such file or directory /usr/share/locale/sr_YU.UTF-8/LC_NUMERIC: No such file or directory /usr/share/locale/zh_CN.GBK/LC_TIME: No such file or directory -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2513] Installer w/ UFS set subpartitions too big
Issue #2513 has been updated by swildner. On Thu, 21 Feb 2013 14:41:09 +0100, Kurt Hindenburg via Redmine wrote: > > Issue #2513 has been updated by khindenburg. > > > Yes I get that during installation though Do you get it too if you set the disk controller to SATA or SAS instead of IDE for the x86_64 attempt? S. Bug #2513: Installer w/ UFS set subpartitions too big http://bugs.dragonflybsd.org/issues/2513 Author: khindenburg Status: New Priority: Normal Assignee: swildner Category: Target version: Running Oracle VM VIrtualBox 4.2.6 on MacOSX + dfly-i386-3.2.2_REL.iso Installing into entire disk + UFS + default sub-partitions - the following error popups (brevity): The space allocated in subpartitions (13507) exceeds HD size (12355) per IRC made bug report -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2513] Installer w/ UFS set subpartitions too big
Issue #2513 has been updated by swildner. Another guy (in our IRC channel) had issues with installing DragonFly/x86_64 on VirtualBox on the Mac. Looks like he got it installed, though, and it crashed later (disk detached out of the blue). What is the x86_64 issue you are seeing? Is it similar to his (http://djdomics.free.fr/pub/DragonFlyBSD/df64vbox.tiff)? If it is different, can you give us a screen shot of your x86_64 crash? Bug #2513: Installer w/ UFS set subpartitions too big http://bugs.dragonflybsd.org/issues/2513 Author: khindenburg Status: New Priority: Normal Assignee: swildner Category: Target version: Running Oracle VM VIrtualBox 4.2.6 on MacOSX + dfly-i386-3.2.2_REL.iso Installing into entire disk + UFS + default sub-partitions - the following error popups (brevity): The space allocated in subpartitions (13507) exceeds HD size (12355) per IRC made bug report -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2359] (Closed) patch diff to fix confusing behaviour
Issue #2359 has been updated by swildner. Status changed from New to Closed Thanks, I've pushed it, a bit differently though. It will now still show failure with -C but no longer claim to have saved the rejects. Bug #2359: patch diff to fix confusing behaviour http://bugs.dragonflybsd.org/issues/2359 Author: logan1 Status: Closed Priority: Low Assignee: Category: Target version: When applying an erroneous patch with -C, patch prints messages about saving to a rej file, which does not occur. Attached diff fixes this behaviour -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2513] Installer w/ UFS set subpartitions too big
Issue #2513 has been updated by swildner. Assignee set to swildner OK thanks, I've reproduced the partition size issue. The installer simply recommends wrong defaults here. After a bit of downsizing it will install. I will take a look at it. Regarding the hang, It installed fine (and booted after that) here using your settings. I set the type to "FreeBSD", dunno if another type gives different results. But this is vbox 4.2.6 on a Windows host. What exactly do you mean with hangs? The twiddle stops spinning? Are you able to switch to vty0 (with ALT-F1) which shows the files as they are copied? Bug #2513: Installer w/ UFS set subpartitions too big http://bugs.dragonflybsd.org/issues/2513 Author: khindenburg Status: New Priority: Normal Assignee: swildner Category: Target version: Running Oracle VM VIrtualBox 4.2.6 on MacOSX + dfly-i386-3.2.2_REL.iso Installing into entire disk + UFS + default sub-partitions - the following error popups (brevity): The space allocated in subpartitions (13507) exceeds HD size (12355) per IRC made bug report -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2513] Installer w/ UFS set subpartitions too big
Issue #2513 has been updated by swildner. Can you give some more details on how the VM's controller and disk are configured? Bug #2513: Installer w/ UFS set subpartitions too big http://bugs.dragonflybsd.org/issues/2513 Author: khindenburg Status: New Priority: Normal Assignee: Category: Target version: Running Oracle VM VIrtualBox 4.2.6 on MacOSX + dfly-i386-3.2.2_REL.iso Installing into entire disk + UFS + default sub-partitions - the following error popups (brevity): The space allocated in subpartitions (13507) exceeds HD size (12355) per IRC made bug report -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2439] (Closed) ccdconfig fails loading ccd.ko during bootup
Issue #2439 has been updated by swildner. Status changed from New to Closed I've expanded the message ccdconfig gives when it fails kldloading ccd(4). On HAMMER systems, /boot (having the kernel modules) isn't yet mounted when ccdconfig(8) runs via /etc/rc.d/ccd. Bug #2439: ccdconfig fails loading ccd.ko during bootup http://bugs.dragonflybsd.org/issues/2439 Author: solskogen Status: Closed Priority: Normal Assignee: swildner Category: Target version: Hopefully, the subject is enough. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2509] Redefinition of DIRBLKSIZ in restore(8)
Issue #2509 has been reported by swildner. Bug #2509: Redefinition of DIRBLKSIZ in restore(8) http://bugs.dragonflybsd.org/issues/2509 Author: swildner Status: New Priority: Normal Assignee: Category: Target version: I noticed that sbin/restore/interactive.c includes both and , both of which define DIRBLKSIZ, but to different values. In : #define DIRBLKSIZ 1024 In : #define DIRBLKSIZ DEV_BSIZE It seems to be a poor choice of names and ends up being 512 just by the ordering of includes in interactive.c. Venkatesh told me to file a bug (so he doesn't forget), which I hereby did. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2501] (Closed) UFS panic: assertion "lock_held(&lk)" failed in worklist_remove
Issue #2501 has been updated by swildner. Status changed from New to Closed Closing this for now, since with Venkatesh's fix (9d106dfa699e433e63b3876290375371060b91f9) the panic no longer occurs under these conditions. Bug #2501: UFS panic: assertion "lock_held(&lk)" failed in worklist_remove http://bugs.dragonflybsd.org/issues/2501 Author: swildner Status: Closed Priority: Normal Assignee: vsrinivas Category: Target version: Just got this when (I _think_) the box was removing a larger tree in /usr/obj. core.txt is here: http://87.78.98.243/tmp/core.txt.21 Full dump is in ~swildner/crash/crash21.txz on leaf. Regards, Sascha -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2505] i386 buildkernel cc1: error: too many filenames given /usr/obj/usr/src/world_i386/usr/include: No such file or directory
Issue #2505 has been updated by swildner. On Mon, 04 Feb 2013 08:12:36 +0100, David Shao via Redmine wrote: > > Issue #2505 has been reported by davshao. > > > Bug #2505: i386 buildkernel cc1: error: too many filenames given > /usr/obj/usr/src/world_i386/usr/include: No such file or directory > http://bugs.dragonflybsd.org/issues/2505 > > Author: davshao > Status: New > Priority: Normal > Assignee: > Category: > Target version: > > > On a i386 build updating from > > commit e2a099cf1b1188b60aecc18de449444f7dca0f6a > Date: Fri Feb 1 13:47:37 2013 -0800 > > kernel - Fix kernel panic caused by rename race > > to > > commit 6de060a4493ce25dda4287f3ab00041b698ba2b8 > Date: Sun Feb 3 13:32:01 2013 +0100 > > Unbreak world with NO_GCC44 > > with /etc/make.conf > > CFLAGS+=-g > STRIP= A shorter way for this is to just set DEBUG_FLAGS=-g in make.conf (the STRIP isn't needed in this case). S. Bug #2505: i386 buildkernel cc1: error: too many filenames given /usr/obj/usr/src/world_i386/usr/include: No such file or directory http://bugs.dragonflybsd.org/issues/2505 Author: davshao Status: New Priority: Normal Assignee: Category: Target version: On a i386 build updating from commit e2a099cf1b1188b60aecc18de449444f7dca0f6a Date: Fri Feb 1 13:47:37 2013 -0800 kernel - Fix kernel panic caused by rename race to commit 6de060a4493ce25dda4287f3ab00041b698ba2b8 Date: Sun Feb 3 13:32:01 2013 +0100 Unbreak world with NO_GCC44 with /etc/make.conf CFLAGS+=-g STRIP= # make buildworld && make buildkernel ends with an error: ===> bus/cam/cam @ -> /usr/src/sys/bus/cam/cam/../../.. echo "#define SCSI_DELAY 15000" > opt_scsi.h rm -f .depend > .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I. -I@ -I/usr/obj/usr/src/sys/GENERIC -I/usr/obj/usr/src/sys/GENERIC/include -I@/../include -I/usr/obj/usr/src/world_i386/usr/include -std=c99 -std=gnu99 -std=c99 /usr/src/sys/bus/cam/cam/../cam.c /usr/src/sys/bus/cam/cam/../cam_periph.c /usr/src/sys/bus/cam/cam/../cam_queue.c /usr/src/sys/bus/cam/cam/../cam_sim.c /usr/src/sys/bus/cam/cam/../cam_xpt.c /usr/src/sys/bus/cam/cam/../cam_extend.c /usr/src/sys/bus/cam/cam/../scsi/scsi_all.c /usr/src/sys/bus/cam/cam/../scsi/scsi_cd.c /usr/src/sys/bus/cam/cam/../scsi/scsi_ch.c /usr/src/sys/bus/cam/cam/../scsi/scsi_da.c /usr/src/sys/bus/cam/cam/../scsi/scsi_pass.c /usr/src/sys/bus/cam/cam/../scsi/scsi_pt.c /usr/src/sys/bus/cam/cam/../scsi/scsi_sa.c /usr/src/sys/bus/cam/cam/../scsi/scsi_ses.c /usr/src/sys/bus/cam/cam/../scsi/scsi_targ_bh.c /usr/src/sys/bus/cam/cam/../scsi/scsi_target.c cc1: error: too many filenames given. Type cc1 --help for usage cc1: fatal error: /usr/obj/usr/src/world_i386/usr/include: No such file or directory compilation terminated. cc1: error: too many filenames given. Type cc1 --help for usage cc1: fatal error: /usr/obj/usr/src/world_i386/usr/include: No such file or directory compilation terminated. cc1: error: too many filenames given. Type cc1 --help for usage cc1: fatal error: /usr/obj/usr/src/world_i386/usr/include: No such file or directory compilation terminated. cc1: error: too many filenames given. Type cc1 --help for usage cc1: fatal error: /usr/obj/usr/src/world_i386/usr/include: No such file or directory compilation terminated. ... cc1: fatal error: /usr/obj/usr/src/world_i386/usr/include: No such file or directory compilation terminated. mkdep: compile failed *** Error code 1 Stop. make: stopped in /usr/src/sys/bus/cam/cam *** Error code 1 Stop. make: stopped in /usr/src/sys/bus/cam *** Error code 1 Stop. make: stopped in /usr/src/sys/bus *** Error code 1 Stop. make: stopped in /usr/src/sys *** Error code 1 Stop. make: stopped in /usr/obj/usr/src/sys/GENERIC *** Error code 1 Stop. make: stopped in /usr/src .CURDIR='/usr/src' .OBJDIR='/usr/obj/usr/src' .MAKE='make' MAKE_VERSION='20121010' LD_LIBRARY_PATH='' MACHINE_ARCH='i386' MACHINE='i386' MAKEFILE='/usr/src/Makefile.inc1' .TARGETS='buildkernel' .ERROR_TARGET='buildkernel' .ERROR_META_FILE='' .MAKE.LEVEL='1' .MAKE.MODE='' *** Error code 1 -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2501] UFS panic: assertion "lock_held(&lk)" failed in worklist_remove
Issue #2501 has been updated by swildner. I should add that this is a i386 box. Bug #2501: UFS panic: assertion "lock_held(&lk)" failed in worklist_remove http://bugs.dragonflybsd.org/issues/2501 Author: swildner Status: New Priority: Normal Assignee: vsrinivas Category: Target version: Just got this when (I _think_) the box was removing a larger tree in /usr/obj. core.txt is here: http://87.78.98.243/tmp/core.txt.21 Full dump is in ~swildner/crash/crash21.txz on leaf. Regards, Sascha -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2501] UFS panic: assertion "lock_held(&lk)" failed in worklist_remove
Issue #2501 has been reported by swildner. Bug #2501: UFS panic: assertion "lock_held(&lk)" failed in worklist_remove http://bugs.dragonflybsd.org/issues/2501 Author: swildner Status: New Priority: Normal Assignee: vsrinivas Category: Target version: Just got this when (I _think_) the box was removing a larger tree in /usr/obj. core.txt is here: http://87.78.98.243/tmp/core.txt.21 Full dump is in ~swildner/crash/crash21.txz on leaf. Regards, Sascha -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2484] virtio hangs boot of i386 Ideapad with acpi disabled
Issue #2484 has been updated by swildner. On Thu, 10 Jan 2013 00:47:30 +0100, David Shao via Redmine wrote: > > Issue #2484 has been reported by David Shao. > > > Bug #2484: virtio hangs boot of i386 Ideapad with acpi disabled > http://bugs.dragonflybsd.org/issues/2484 > > Author: David Shao > Status: New > Priority: Normal > Assignee: > Category: > Target version: > > > For a Lenovo Ideapad netbook (i386) with acpi disabled using master > commits through > commit 1d0de3d37b9efb6301b10515fd12d922c8602093 > Date: Tue Jan 8 19:21:35 2013 +0100 > > kernel/vfs: Remove some unused variables. > > boot hangs after devices: > > md0: invalid primary partition table: no magic > Math emulator present > hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2 > hpt27xx: RocketRAID 27xx controller driver v1.0 (Jan 9 2013 12:15:05) > > and before > > IOAPIC: rman cpu0 0 - 1 > IOAPIC: rman cpu0 3 - 95 > IOAPIC: rman cpu0 97 - 191 > IOAPIC: rman cpu1 24 - 95 > IOAPIC: rman cpu1 97 - 191 > npx0.nexus0.root0 > npx0: [tentative] on motherboard > npx0: INT 16 interface > > The boot problem was bisected to be after: Here's what I know about this bug: * It seems to occur on i386 only. * The boot hanging occurs randomly. The box I have that exhibits the bug boots in 70-80% of the cases and hangs in 20-30%. So I think you had a wrong impression during bisecting when it booted. Just go and try booting a few times with a state that hung, and you will see that eventually it will boot. Matt had the same issue once on an Atom box and committed a fix to alc(4) which he thought was related to the issue, when in fact it was not, just because it happened to boot after that. The fix was OK nevertheless (just not related). :) * The bug is not related to hptrr or hpt27xx drivers. The messages those drivers give are informational and don't indicate that any such adapter was found. In a booting dmesg you will notice that later on they both say that no matching adapter was found. Also, if hpt* drivers are removed from the kernel config, the boot hanging will continue (just with the "Math emulator present" as the last message). If _any_ messages are related to it, it is the IOAPIC: rman stuff (which it doesn't get to when not booting), but I'm not sure if something in ioapic is related to the issue. * The bug has nothing to do with virtio either. It started before we imported that. Best regards, Sascha Bug #2484: virtio hangs boot of i386 Ideapad with acpi disabled http://bugs.dragonflybsd.org/issues/2484 Author: davshao Status: New Priority: Normal Assignee: vsrinivas Category: Target version: For a Lenovo Ideapad netbook (i386) with acpi disabled using master commits through commit 1d0de3d37b9efb6301b10515fd12d922c8602093 Date: Tue Jan 8 19:21:35 2013 +0100 kernel/vfs: Remove some unused variables. boot hangs after devices: md0: invalid primary partition table: no magic Math emulator present hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2 hpt27xx: RocketRAID 27xx controller driver v1.0 (Jan 9 2013 12:15:05) and before IOAPIC: rman cpu0 0 - 1 IOAPIC: rman cpu0 3 - 95 IOAPIC: rman cpu0 97 - 191 IOAPIC: rman cpu1 24 - 95 IOAPIC: rman cpu1 97 - 191 npx0.nexus0.root0 npx0: [tentative] on motherboard npx0: INT 16 interface The boot problem was bisected to be after: commit 42fdf81ee882d38808efe2772a68a9c4991a5f76 Date: Sun Jan 6 20:01:27 2013 +0800 and before: commit f31f6d84db329735c062a41c0f729843cd4d0b6f Date: Mon Jan 7 09:48:18 2013 +0100 kernel/hammer: Remove unused variables and add __debugvar. In addition a workaround is to disable kernel options for virtio for a custom kernel config: # VirtIO support # devicevirtio # VirtIO core # devicevirtio_blk # VirtIO disk driver # devicevirtio_pci # VirtIO transport over PCI bus Attached is a dmesg for the booting configuration with acpi and virtio disabled. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2493] vidcontrol: invalid video mode name
Issue #2493 has been updated by swildner. Hmm, in DragonFly it expects a mode first, as in: vidcontrol 80x50 lightwhite blue Are you sure it works without a mode in FreeBSD? After a quick peek at their source it didn't look like it would, but maybe the peek was too quick. :) Sascha Bug #2493: vidcontrol: invalid video mode name http://bugs.dragonflybsd.org/issues/2493 Author: Svarov Status: New Priority: Normal Assignee: Category: Target version: Hello. I tried to change foreground/background color of the virt. console (ttyv1) with command `vidcontrol lightwhite black` but haven't got any success. The program reports "vidcontrol: invalid video mode name". The syntax seems to be correct because on FreeBSD (latest) it works fine. Do I miss something or it's a bug? Regards, Dmitry. == PC: Netbook Eee PC 900AX OS: DragonFlyBSD 3.2.1 -- I am sorry for my english, it's still very poor. Hope that my message is understandable. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2467] Intel 945GME agp Fatal trap 12 with ACPI disabled
Issue #2467 has been updated by Sascha Wildner. David, you wrote: vgapci10: port 0xe080-0xe087 mem 0xe000-0xefff,0xf000-0xf03f irq 16 at device 2.0 on pci0 Is that '10' a typo? If not, can we see this box' whole dmesg, please? :) Bug #2467: Intel 945GME agp Fatal trap 12 with ACPI disabled http://bugs.dragonflybsd.org/issues/2467 Author: David Shao Status: In Progress Priority: Normal Assignee: Francois Tigeot Category: Target version: ACPI disabled on a Lenovo Ideapad netbook: MPTABLE: 0:31 INTB routed to irq 19 vgapci0.pci0.pcib0.legacy0.nexus0.root0 vgapci0: [tentative] port 0x1800-0x1807 mem 0xf060-0xf063,0xd000-0xdfff,0xf050-0xf057 irq 16 at device 2.0 on pci0 agp0.vgapci0.pci0.pcib0.legacy0.nexus0.root0 agp0: [tentative] on vgapci0 vgapci0: Reserved 0x1000 bytes for rid 0x18 type 3 at 0xd000 Fatal trap 12: page fault while in kernel mode cpuid = 0; lapic.id = fault virtual address = 0x78 fault code = supervisor write, page not present instruction pointer= 0x8:0xc052b97e stack pointer = 0x10:0xc0ef5984 frame pointer = 0x10:0xc0ef59a8 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process= 0 (swapper) current thread = pri 12 <- SMP: XXX kernel: type 12 trap, code=2 CPU0 stopping CPUs: 0x0002 stopped Stopped at agp_generic_attach+0x13f: movl %esi,0x78(%eax) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2463] (Closed) __thread storage class for errno may break Firefox 17.0esr C++ compilation
Issue #2463 has been updated by Sascha Wildner.
Status changed from Feedback to Closed
Bug #2463: __thread storage class for errno may break Firefox 17.0esr C++
compilation
http://bugs.dragonflybsd.org/issues/2463
Author: David Shao
Status: Closed
Priority: Normal
Assignee:
Category:
Target version:
Executing the commands on the file cpperrno.cpp
$ c++ cpperrno.cpp
$ ./a.out
produces the output:
errno = 22
on NetBSD amd64, FreeBSD amd64, and Linux amd64 (Ubuntu 12.04 LTS).
However on DragonFly the output is an error message:
$ c++ cpperrno.cpp
/tmp//ccTk4OGn.o: In function `(anonymous namespace)::__error()':
cpperrno.cpp:(.text+0x10): undefined reference to `(anonymous namespace)::errno'
This matters because the file cpperrno.cpp is a minimal example demonstrating
build breakage of current pkgsrc devel/xulrunner for Firefox 17.0esr, as
reported in a followup to PR pkg/47233.
The difference appears to be that on DragonFly in file sys/sys/errno.h, there
is the declaration:
#if !defined(_KERNEL) || defined(_KERNEL_VIRTUAL)
extern __thread int errno;
Obviously there are reasons to use storage class keyword __thread for errno;
nonetheless, the breakage of compilation for Firefox 17.0esr on no platform but
DragonFly indicates some alternative solution must be devised for porting C++
userland programs.
/* begin cpperrno.cpp */
namespace {
#pragma GCC visibility push(default)
#include
#pragma GCC visibility pop
void innamespace() {
errno = EINVAL;
}
} /* end namespace */
extern "C" {
void seterrno() {
innamespace();
}
} /* end extern */
#include
#include
int main() {
seterrno();
printf("errno = %d\n", errno);
return errno;
}
/* end cpperrno.cpp */
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2461] (Closed) INT64_MAX, INT64_MIN long long definition conflicts on x86_64 with firefox 17.0esr build
Issue #2461 has been updated by Sascha Wildner.
Status changed from Feedback to Closed
Bug #2461: INT64_MAX,INT64_MIN long long definition conflicts on x86_64 with
firefox 17.0esr build
http://bugs.dragonflybsd.org/issues/2461
Author: David Shao
Status: Closed
Priority: Normal
Assignee:
Category:
Target version:
On current pkgsrc master, 3.3-DEVELOPMENT x86_64, building devel/xulrunner,
associated with firefox 17.0esr, fails processing a C++ header file with an
error message:
In file included from ../../dist/include/mozilla/FunctionTimer.h:11,
from
/usr/pkgsrc/devel/xulrunner/work/mozilla-esr17/xpcom/glue/FileUtils.cpp:20:
../../dist/include/mozilla/TimeStamp.h: In static member function 'static
mozilla::TimeDuration mozilla::TimeDuration::FromTicks(double)':
../../dist/include/mozilla/TimeStamp.h:137: error: call of overloaded
'FromTicks(long long int)' is ambiguous
../../dist/include/mozilla/TimeStamp.h:123: note: candidates are: static
mozilla::TimeDuration mozilla::TimeDuration::FromTicks(int64_t)
../../dist/include/mozilla/TimeStamp.h:129: note: static
mozilla::TimeDuration mozilla::TimeDuration::FromTicks(double)
gmake[4]: *** [FileUtils.o] Error 1
The relevant lines from the original TimeStamp.h located under
devel/xulrunner/work/mozilla-esr17/xpcom/ds appear to be:
static TimeDuration FromTicks(int64_t aTicks) {
TimeDuration t;
t.mValue = aTicks;
return t;
}
static TimeDuration FromTicks(double aTicks) {
// NOTE: this MUST be a >= test, because int64_t(double(INT64_MAX))
// overflows and gives LL_MININT.
if (aTicks >= double(INT64_MAX))
return TimeDuration::FromTicks(INT64_MAX);
// This MUST be a <= test.
if (aTicks <= double(INT64_MIN))
return TimeDuration::FromTicks(INT64_MIN);
return TimeDuration::FromTicks(int64_t(aTicks));
}
// Duration in PRIntervalTime units
int64_t mValue;
A patch explictly casting in the above header file TimeStamp.h both INT64_MAX
and INT64_MIN to int64_t allows building to at least proceed past the previous
error.
Grepping for INT64_MAX and INT64_MIN under /usr/include reveals definitions:
#define INT64_MAX 0x7fffLL
#define INT64_MIN (-0x7fffLL-1)
The compiler being used is:
$ cc --version
cc (DragonFly) 4.4.7 2012.03.13
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2461] (Feedback) INT64_MAX, INT64_MIN long long definition conflicts on x86_64 with firefox 17.0esr build
Issue #2461 has been updated by Sascha Wildner.
Status changed from New to Feedback
Thanks, I've pushed a fix. Please try and report back.
Bug #2461: INT64_MAX,INT64_MIN long long definition conflicts on x86_64 with
firefox 17.0esr build
http://bugs.dragonflybsd.org/issues/2461
Author: David Shao
Status: Feedback
Priority: Normal
Assignee:
Category:
Target version:
On current pkgsrc master, 3.3-DEVELOPMENT x86_64, building devel/xulrunner,
associated with firefox 17.0esr, fails processing a C++ header file with an
error message:
In file included from ../../dist/include/mozilla/FunctionTimer.h:11,
from
/usr/pkgsrc/devel/xulrunner/work/mozilla-esr17/xpcom/glue/FileUtils.cpp:20:
../../dist/include/mozilla/TimeStamp.h: In static member function 'static
mozilla::TimeDuration mozilla::TimeDuration::FromTicks(double)':
../../dist/include/mozilla/TimeStamp.h:137: error: call of overloaded
'FromTicks(long long int)' is ambiguous
../../dist/include/mozilla/TimeStamp.h:123: note: candidates are: static
mozilla::TimeDuration mozilla::TimeDuration::FromTicks(int64_t)
../../dist/include/mozilla/TimeStamp.h:129: note: static
mozilla::TimeDuration mozilla::TimeDuration::FromTicks(double)
gmake[4]: *** [FileUtils.o] Error 1
The relevant lines from the original TimeStamp.h located under
devel/xulrunner/work/mozilla-esr17/xpcom/ds appear to be:
static TimeDuration FromTicks(int64_t aTicks) {
TimeDuration t;
t.mValue = aTicks;
return t;
}
static TimeDuration FromTicks(double aTicks) {
// NOTE: this MUST be a >= test, because int64_t(double(INT64_MAX))
// overflows and gives LL_MININT.
if (aTicks >= double(INT64_MAX))
return TimeDuration::FromTicks(INT64_MAX);
// This MUST be a <= test.
if (aTicks <= double(INT64_MIN))
return TimeDuration::FromTicks(INT64_MIN);
return TimeDuration::FromTicks(int64_t(aTicks));
}
// Duration in PRIntervalTime units
int64_t mValue;
A patch explictly casting in the above header file TimeStamp.h both INT64_MAX
and INT64_MIN to int64_t allows building to at least proceed past the previous
error.
Grepping for INT64_MAX and INT64_MIN under /usr/include reveals definitions:
#define INT64_MAX 0x7fffLL
#define INT64_MIN (-0x7fffLL-1)
The compiler being used is:
$ cc --version
cc (DragonFly) 4.4.7 2012.03.13
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2463] (Feedback) __thread storage class for errno may break Firefox 17.0esr C++ compilation
Issue #2463 has been updated by Sascha Wildner.
Status changed from New to Feedback
I've changed accordingly.
David, can you please try with devel/xulrunner and report results?
Bug #2463: __thread storage class for errno may break Firefox 17.0esr C++
compilation
http://bugs.dragonflybsd.org/issues/2463
Author: David Shao
Status: Feedback
Priority: Normal
Assignee:
Category:
Target version:
Executing the commands on the file cpperrno.cpp
$ c++ cpperrno.cpp
$ ./a.out
produces the output:
errno = 22
on NetBSD amd64, FreeBSD amd64, and Linux amd64 (Ubuntu 12.04 LTS).
However on DragonFly the output is an error message:
$ c++ cpperrno.cpp
/tmp//ccTk4OGn.o: In function `(anonymous namespace)::__error()':
cpperrno.cpp:(.text+0x10): undefined reference to `(anonymous namespace)::errno'
This matters because the file cpperrno.cpp is a minimal example demonstrating
build breakage of current pkgsrc devel/xulrunner for Firefox 17.0esr, as
reported in a followup to PR pkg/47233.
The difference appears to be that on DragonFly in file sys/sys/errno.h, there
is the declaration:
#if !defined(_KERNEL) || defined(_KERNEL_VIRTUAL)
extern __thread int errno;
Obviously there are reasons to use storage class keyword __thread for errno;
nonetheless, the breakage of compilation for Firefox 17.0esr on no platform but
DragonFly indicates some alternative solution must be devised for porting C++
userland programs.
/* begin cpperrno.cpp */
namespace {
#pragma GCC visibility push(default)
#include
#pragma GCC visibility pop
void innamespace() {
errno = EINVAL;
}
} /* end namespace */
extern "C" {
void seterrno() {
innamespace();
}
} /* end extern */
#include
#include
int main() {
seterrno();
printf("errno = %d\n", errno);
return errno;
}
/* end cpperrno.cpp */
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2462] (In Progress) These locale symlinks need to be removed
Issue #2462 has been updated by Sascha Wildner. Status changed from New to In Progress Assignee set to Sascha Wildner The real fix is to upgrade the localization files and i18n databases (which adds the missing files those symlinks should resolve to). I have it done locally but it needs some more testing. I'll push something in the next time. Bug #2462: These locale symlinks need to be removed http://bugs.dragonflybsd.org/issues/2462 Author: John Marino Status: In Progress Priority: Normal Assignee: Sascha Wildner Category: Target version: The following symlinks point to nothing. IMO they should be removed from build and added to Make upgrade to remove from world /usr/share/locale/ca_ES.UTF-8/LC_MESSAGES: No such file or directory /usr/share/locale/ca_ES.UTF-8/LC_MONETARY: No such file or directory /usr/share/locale/ca_ES.UTF-8/LC_NUMERIC: No such file or directory /usr/share/locale/eu_ES.ISO8859-15/LC_TIME: No such file or directory /usr/share/locale/eu_ES.UTF-8/LC_TIME: No such file or directory /usr/share/locale/hy_AM.UTF-8/LC_NUMERIC: No such file or directory /usr/share/locale/kk_KZ.UTF-8/LC_NUMERIC: No such file or directory /usr/share/locale/sr_YU.UTF-8/LC_NUMERIC: No such file or directory /usr/share/locale/zh_CN.GBK/LC_TIME: No such file or directory -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2460] (Closed) Topology code fails, only one cpu detected
Issue #2460 has been updated by Sascha Wildner. Status changed from New to Closed Happily resolved with some BIOS tweaking, so closing. Bug #2460: Topology code fails, only one cpu detected http://bugs.dragonflybsd.org/issues/2460 Author: James Thomas Status: Closed Priority: Normal Assignee: Category: Target version: Hi all, The box in question is an HP Proliant DL580 G2 with four 32 bit Xeon MP 2.8GHz cpus, all of which are available at POST. BIOS, disk array, and LOSI firmwares have all been updated. I did a fresh install from the 3.2.1 release cd this morning, did 'make src-create' in /usr and then built world, kernel, then installed kernel, world, and upgrade. Here's a verbose dmesg.boot: http://pastebin.com/FdLXWRr5 Thank you, James -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2442] Possible bmake regression link_elf_obj_obj: symbol atomic_cmpset_int undefined
Issue #2442 has been updated by Sascha Wildner. On Tue, 30 Oct 2012 08:23:04 +0100, Francois Tigeot via Redmine wrote: > > Issue #2442 has been updated by Francois Tigeot. > > > The new build infrastructure is apparently sensitive to > .o/.So/.so/.po/.a files located in /usr/src I don't think it's related to that. Our snapshots have the same atomic* problem and their source is freshly cloned and checked out upon every build. Sascha Bug #2442: Possible bmake regression link_elf_obj_obj: symbol atomic_cmpset_int undefined http://bugs.dragonflybsd.org/issues/2442 Author: David Shao Status: New Priority: Normal Assignee: Category: Target version: Something in master after (not inclusive) commit 861cfd512d0fe6d53d680a10c0989a580290ef22 kernel/linprocfs: Add dependency on the linux module and through (inclusive) commit a3775bf244235f5b1b580b0aab954df19e770863 Update files for OpenSSH-6.1p1 import has caused a regression such that in dmesg: Mounting devfs link_elf_obj_obj: symbol atomic_cmpset_int undefined linker_load_file: Unsupported file type KLD radeon.ko: depends on drm - not available or version mismatch linker_load_file: Unsupported file type It is therefore suspected that this is caused by something in the make to bmake transition. The one system tested so far where this regression has been observed is an Asus M5A87 motherboard AMD64 x86_64, chipset AMD 870 / SB850, MSI R4350 Radeon graphics card. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2439] ccdconfig fails loading ccd.ko during bootup
Issue #2439 has been updated by Sascha Wildner. Assignee set to Sascha Wildner grab Bug #2439: ccdconfig fails loading ccd.ko during bootup http://bugs.dragonflybsd.org/issues/2439 Author: Christer Solskogen Status: New Priority: Normal Assignee: Sascha Wildner Category: Target version: Hopefully, the subject is enough. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #1967] Kernel Patches to support virtio
Issue #1967 has been updated by Sascha Wildner. Description updated Assignee deleted (0) In discussion with vsrinivas (who is working on virtio currently), I've pushed the first patch. Thanks! Bug #1967: Kernel Patches to support virtio http://bugs.dragonflybsd.org/issues/1967 Author: Tim Bisson Status: Closed Priority: Low Assignee: Category: Target version: Hi, Here are the proposed kernel changes which allow the virtio drivers (ported from FreeBSD) to build: * 0001-make-device_probe_child-public.patch makes device_probe_child() public, used by virtio_pci.c: http://gitorious.org/dbd-virtio-drivers-freebsd-port/dbd-virtio-drivers-freebsd-port/blobs/master/pci/virtio_pci.c#line693 * 0001-Pull-in-FreeBSD-sglist.patch is the scatter/gather library used by virtio-net. Thanks, Tim -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
