test
I got a reply in my inbox with a copy sent to the list, but I don't have the copy sent to the list yet. Pierre -- lo ponse be lo mruli po'o cu ga'ezga roda lo ka dinko
Don't response - test
Can't see new mails in my box from 15.9.
HEADS UP: ndis(4) updated, please test
Hello, I just pushed an upgrade of ndis(4) and have this to say about it: First of all, be warned that USB adapter support is unstable, which means, it might attach, it might even ifconfig up or something similar but will likely panic on either. But I plan to look into that. PCI adapters (and maybe PC Card adapters), on the other hand, work like a charm (at least those four which Max Herrgard and I tested), if (and most likely only if) you turn off ioapic via loader.conf: hw.ioapic_enable=0. As I wrote in the commit message, I don't know why this is so, and it is kinda hard to debug because the symptom is that the box will freeze completely after a short while without doing so. This was observed on two different boxes with all cards tested. That said, if you are still interested, here are some instructions to get you started: * You'll need to upgrade world and kernel to current master. * You'll need the Windows drivers for the card, obviously. Actually, Windows XP drivers (either 32 bit or 64 bit, depending on your DragonFly architecture). Server 2003 drivers might work but it is not tested. Specifically, you will need the .sys and .inf files for the card. You'll also need firmware files if they are needed for the card (ending in .bin). Check the CD-ROM that came with the card or look on the net. You might find that they come as a .cab or .exe file. In this case cabextract or unshield from pkgsrc might help to extract them. Also, 7zip is sometimes able to extract those files. Another Windows program that has shown good results is the Universal Extractor. If all that fails, please mail me or poke me on the #dragonflybsd IRC channel on EFNet and we might be able to figure it out (I might have it already or we can install it in a VM and locate the files, for example). Getting hold of the drivers can sometimes be the most difficult part of getting going with ndis(4). * Once you have the files, run ndisgen foo.inf foo.sys on them (replace foo accordingly). ndisgen(8) is an interactive script. Follow the instructions, remember to specify the firmware files too (if needed) and if all goes well, it will compile the driver/firmware module(s) for you. Sometimes it will error on a specific line of the .inf file. Go and check that line in the editor. Errors can have various reasons. Sometimes it's a missing newline at the end of the file's last line, sometimes a missing semicolon, sometimes something else. If you can't figure out what to fix, again, mail me or contact me in IRC, or here. * After a successful run of ndisgen you'll find one or more .ko files in the current dir. Move the one named *_sys.ko to /boot/kernel and move any remaining *.ko files (should be there if there was firmware to convert) to /compat/ndis. Now you are ready to use the driver the usual way. kldload it, set up the wlan and test. For example, given a valid wpa_supplicant config, the following might work: In /boot/loader.conf: foo_sys_load=yes #replace foo with your module name In /etc/rc.conf: wlans_ndis0=wlan0 ifconfig_wlan0=up DHCP WPA It might be wise to first load the module manually and play with it a little bit. If all attaches and sets up properly, you will very likely notice that the box will freeze after a while. If this happens (and I've never seen it not happening), add hw.ioapic_enable=0 to /boot/loader.conf. The card should then work. In any case: I'm interested in all results you people have with it. Have fun, Sascha
test: please delete
Re: How to test and debug Dragonfly BSD?
Hi again, I have acquainted myself with list of tasks and bugs.: ( http://www.dragonflybsd.org/docs/developer/gsocprojectspage/ , http://www.dragonflybsd.org/docs/developer/ProjectsPage/ , http://www.dragonflybsd.org/docs/developer/researchprojectspage/ , http://bugs.dragonflybsd.org/ ) Some of them are assigned to a developer. Does it mean that if task/bug isn't assigned to any person nobody works on it or just web-page is not updated too often? I would like to avoid duplicating work. For example: Make DragonFly NUMA-aware or Update our interrupt routing and PCI code. I try find something for me, what helps me get to know more about dfbsd and its architecture. P.S. Off topic question.: Is it safe to entrust my data to hammer files system? I don't have experience with it but i see it still under heavy development. P.S.2 Did i mention that English is not my mother tongue, so i apologize for grammar mistakes and misspell. ... on IRC too. :) Greetings Marcin 2010/11/9 Alex Hornung ahorn...@gmail.com: On 09/11/2010 05:31, Marcin Ropa wrote: There are tons of code. Is there any README, describing which functionality I may expected in which subdirectory? Where is core of the system, where main structures are initialized and everything begins when the system starting. Just take a look at the directory structure in the source tree, I think it's pretty obvious how things fit together. (Almost) every top level directory in userland has a name that corresponds to its name on the destination installation, e.g. usr.bin is the stuff that goes into /usr/bin. Some notable exceptions are: contrib - which is contributed (3rd party) code. The Makefiles are still in the normal directories (i.e. sbin) but the sources for these are here gnu - contains the the Makefiles for gnu-licensed programs (the code resides in contrib) crypto - contains sources that are of restricted exportability, at least historically. nrelease - contains stuff to build ISOs and IMGs tools - contains useful stuff like our git template, iirc test - contains all sorts of random junk, including test cases, small scripts, files for test commits, ... and finally: sys - Contains the kernel and bootloader code In sys the most important directories that you should know about are, kern - main kernel functionality sys - main kernel include files dev - contains all sorts of device drivers, nicely categorized in the subfolders net - Contains network related stuff (but not hardware drivers) platform - platform/architecture dependent code that is not portable bus - Contains PCI, ISA and CAM (maybe you know it from FreeBSD, maybe not; it's a neat abstraction layer for SCSI stuff, for example, above the HBAs) For more help, just ask on the IRC. Hope this helps, Alex Hornung
Re: How to test and debug Dragonfly BSD?
On Fri, Nov 12, 2010 at 3:19 PM, Marcin Ropa marcinr...@gmail.com wrote: P.S. Off topic question.: Is it safe to entrust my data to hammer files system? I don't have experience with it but i see it still under heavy development. MyDesktop as well as Company backup Server runs on Hammer Version 4 :-) --Siju
Re: How to test and debug Dragonfly BSD?
Thanks all for yours replies. Indeed I have to join irc channel - thanks for suggestion, and start this fascinating adventure. :) First off i need reinstall dfbsd on my workstation with hammer files system (yes, i have it installed on my desktop and I'm going to use it as development environment). Then I will try test all you mentioned in yours posts. I hope i will able to install Vbox or qemu or maybe VMware on dfbsd. There are tons of code. Is there any README, describing which functionality I may expected in which subdirectory? Where is core of the system, where main structures are initialized and everything begins when the system starting. I believe it will be good place to understand what is under hood of the OS. Thanks again Marcin
Re: How to test and debug Dragonfly BSD?
Thanks Alex for your description. I've found it useful for my 'code digging'. Now I have to only spend many (probably) weeks :) to understand what is going on in sources. If I run into another problem i will try catch you (and others) on dfbsd's irc channel. Greetings Marcin 2010/11/9 Alex Hornung ahorn...@gmail.com: On 09/11/2010 05:31, Marcin Ropa wrote: There are tons of code. Is there any README, describing which functionality I may expected in which subdirectory? Where is core of the system, where main structures are initialized and everything begins when the system starting. Just take a look at the directory structure in the source tree, I think it's pretty obvious how things fit together. (Almost) every top level directory in userland has a name that corresponds to its name on the destination installation, e.g. usr.bin is the stuff that goes into /usr/bin. Some notable exceptions are: contrib - which is contributed (3rd party) code. The Makefiles are still in the normal directories (i.e. sbin) but the sources for these are here gnu - contains the the Makefiles for gnu-licensed programs (the code resides in contrib) crypto - contains sources that are of restricted exportability, at least historically. nrelease - contains stuff to build ISOs and IMGs tools - contains useful stuff like our git template, iirc test - contains all sorts of random junk, including test cases, small scripts, files for test commits, ... and finally: sys - Contains the kernel and bootloader code In sys the most important directories that you should know about are, kern - main kernel functionality sys - main kernel include files dev - contains all sorts of device drivers, nicely categorized in the subfolders net - Contains network related stuff (but not hardware drivers) platform - platform/architecture dependent code that is not portable bus - Contains PCI, ISA and CAM (maybe you know it from FreeBSD, maybe not; it's a neat abstraction layer for SCSI stuff, for example, above the HBAs) For more help, just ask on the IRC. Hope this helps, Alex Hornung
How to test and debug Dragonfly BSD?
Hello, A few weeks ago I decided to spend my free time working on dfbsd and i started digging in code. I have experience as developer but there everything is new for me and probably I will have to spend many time before i will be helpful for the project. :) I have my first question.: How do you organize your work on DragonFly BSD? I am not going to ask you about your editor but how do you run, test and debug your code. Do you use VirtualBox, qemu or seperate machine? Does VirtualBox run on dfbsd or you run VirtualBox on another system, e.g.: FreeBSD and this is your development platform? I know you are busy, but if you find time please give me some hints how to organize work on operating system. thanks a lot and Greeting Marcin
Re: How to test and debug Dragonfly BSD?
DragonflyBSD got Virtual Kernels, those are a tool to run kernels over kernel and debug them. In the documentation site: http://www.dragonflybsd.org/docs/documentation/ there is a section for developer where you can read about codeing standards, tools, repository handling, most what you need is there :-) VBox doesnt run in DFBSD as far as i know and it had some tricks to make DFBSD work in a VBox too, there is a reported bug to oracle that never was fixed and give troubles time to time (if you use it with no-acpi, probably the only issue you will have is a necesity for reboot after turn on, it works for me that way, no idea why, turn on, it halts, soft reset, it workssome kind of Vudu for sure). Also, check the irc, most the developers are there most the time :-) Enjoy the project, there is a lot of fascinating things going on Damian On Mon, Nov 8, 2010 at 17:07, Marcin Ropa marcinr...@gmail.com wrote: Hello, A few weeks ago I decided to spend my free time working on dfbsd and i started digging in code. I have experience as developer but there everything is new for me and probably I will have to spend many time before i will be helpful for the project. :) I have my first question.: How do you organize your work on DragonFly BSD? I am not going to ask you about your editor but how do you run, test and debug your code. Do you use VirtualBox, qemu or seperate machine? Does VirtualBox run on dfbsd or you run VirtualBox on another system, e.g.: FreeBSD and this is your development platform? I know you are busy, but if you find time please give me some hints how to organize work on operating system. thanks a lot and Greeting Marcin -- http://dfbsd.trackbsd.org.ar
Re: How to test and debug Dragonfly BSD?
Hi Sdävtaker, Apparently your experience differs from mine. I've been running Dragonfly i386 and Dragonfly x86_64 within Virtualbox for a year now, and it works great. I've had no issues whatsoever, and that's on host machines of both windows and Solaris. We've even found and fixed a couple of bugs in Dfly due to running it inside vbox. I think your vbox information might be a bit obsolete, or maybe there is something wrong with your instance of it. It requires no tricks. I recommend that one picks FreeBSD or 64-bit FreeBSD as the OS when they create the machine. Regards, John On 11/8/2010 9:25 PM, Sdävtaker wrote: DragonflyBSD got Virtual Kernels, those are a tool to run kernels over kernel and debug them. In the documentation site: http://www.dragonflybsd.org/docs/documentation/ there is a section for developer where you can read about codeing standards, tools, repository handling, most what you need is there :-) VBox doesnt run in DFBSD as far as i know and it had some tricks to make DFBSD work in a VBox too, there is a reported bug to oracle that never was fixed and give troubles time to time (if you use it with no-acpi, probably the only issue you will have is a necesity for reboot after turn on, it works for me that way, no idea why, turn on, it halts, soft reset, it workssome kind of Vudu for sure). Also, check the irc, most the developers are there most the time :-) Enjoy the project, there is a lot of fascinating things going on Damian On Mon, Nov 8, 2010 at 17:07,Marcin Ropa marcinr...@gmail.com wrote: Hello, A few weeks ago I decided to spend my free time working on dfbsd and i started digging in code. I have experience as developer but there everything is new for me and probably I will have to spend many time before i will be helpful for the project. :) I have my first question.: How do you organize your work on DragonFly BSD? I am not going to ask you about your editor but how do you run, test and debug your code. Do you use VirtualBox, qemu or seperate machine? Does VirtualBox run on dfbsd or you run VirtualBox on another system, e.g.: FreeBSD and this is your development platform? I know you are busy, but if you find time please give me some hints how to organize work on operating system. thanks a lot and Greeting Marcin
Re: How to test and debug Dragonfly BSD?
last time i checked was like 1, maybe 2 months ago, i will try again with 2.8 to see what happens. Damian On Mon, Nov 8, 2010 at 17:33, John Marino dragonfly...@marino.st wrote: Hi Sdävtaker, Apparently your experience differs from mine. I've been running Dragonfly i386 and Dragonfly x86_64 within Virtualbox for a year now, and it works great. I've had no issues whatsoever, and that's on host machines of both windows and Solaris. We've even found and fixed a couple of bugs in Dfly due to running it inside vbox. I think your vbox information might be a bit obsolete, or maybe there is something wrong with your instance of it. It requires no tricks. I recommend that one picks FreeBSD or 64-bit FreeBSD as the OS when they create the machine. Regards, John On 11/8/2010 9:25 PM, Sdävtaker wrote: DragonflyBSD got Virtual Kernels, those are a tool to run kernels over kernel and debug them. In the documentation site: http://www.dragonflybsd.org/docs/documentation/ there is a section for developer where you can read about codeing standards, tools, repository handling, most what you need is there :-) VBox doesnt run in DFBSD as far as i know and it had some tricks to make DFBSD work in a VBox too, there is a reported bug to oracle that never was fixed and give troubles time to time (if you use it with no-acpi, probably the only issue you will have is a necesity for reboot after turn on, it works for me that way, no idea why, turn on, it halts, soft reset, it workssome kind of Vudu for sure). Also, check the irc, most the developers are there most the time :-) Enjoy the project, there is a lot of fascinating things going on Damian On Mon, Nov 8, 2010 at 17:07,Marcin Ropa marcinr...@gmail.com wrote: Hello, A few weeks ago I decided to spend my free time working on dfbsd and i started digging in code. I have experience as developer but there everything is new for me and probably I will have to spend many time before i will be helpful for the project. :) I have my first question.: How do you organize your work on DragonFly BSD? I am not going to ask you about your editor but how do you run, test and debug your code. Do you use VirtualBox, qemu or seperate machine? Does VirtualBox run on dfbsd or you run VirtualBox on another system, e.g.: FreeBSD and this is your development platform? I know you are busy, but if you find time please give me some hints how to organize work on operating system. thanks a lot and Greeting Marcin -- http://dfbsd.trackbsd.org.ar
Re: How to test and debug Dragonfly BSD?
Hi Marcin, first off I'd recommend you join the IRC channel on efnet, #dragonflybsd. Most committers hang out there and it's the easiest way to get some initial help (and probably any help). There are a number of solutions that people use to develop DragonFly, ranging from purely virtual using VMWare, VirtualBox or kvm/qemu (kqemu?) to dedicated physical test machines. I personally have an installation on my laptop and also develop using VMWare on my desktop. As someone already mentioned, DragonFly offers vkernels which are a nice way to develop kernel stuff without any complications as machines not booting, etc... everything except hardware drivers, of course. Debugging of kernel issues usually occurs via a kernel core dump or, sometimes, by debugging a vkernel with gdb. Hope that helps, Alex Hornung On 8 November 2010 20:07, Marcin Ropa marcinr...@gmail.com wrote: Hello, A few weeks ago I decided to spend my free time working on dfbsd and i started digging in code. I have experience as developer but there everything is new for me and probably I will have to spend many time before i will be helpful for the project. :) I have my first question.: How do you organize your work on DragonFly BSD? I am not going to ask you about your editor but how do you run, test and debug your code. Do you use VirtualBox, qemu or seperate machine? Does VirtualBox run on dfbsd or you run VirtualBox on another system, e.g.: FreeBSD and this is your development platform? I know you are busy, but if you find time please give me some hints how to organize work on operating system. thanks a lot and Greeting Marcin
SMP users needed to test patch
Hello everyone! I'd like to mark mq*() syscall as MPSAFE, but before that I need someone to test them in an SMP capable machine running SMP kernel. I only have UP machines around. So, if anyone is able and kind enough, here are some directions on how to do it. I assume s\he is running HEAD. cd /usr/src fetch http://leaf.dragonflybsd.org/~beket/mq-mpsafe.diff git apply mq-mpsafe.diff make buildkernel make installkernel reboot git clone git://gitweb.dragonflybsd.org/~beket/pcca-tests.git cd pcca-tests/mqueue.h make make -k run cd etc make sysctl -w kern.mqueue.mq_prio_max=200 ./t_mq_parallel_threads ./t_mq_parallel_fork If you encounter problems you can mail me off-list to sort them out. I know that it's messy, so no hard feelings if no one volunteers :) Thank you for considering. Best regards, Stathis Kamperis
Re: SMP users needed to test patch
On Wed, 4 Nov 2009, Stathis Kamperis wrote: Hello everyone! I'd like to mark mq*() syscall as MPSAFE, but before that I need someone to test them in an SMP capable machine running SMP kernel. I only have UP machines around. So, if anyone is able and kind enough, here are some directions on how to do it. I assume s\he is running HEAD. cd /usr/src fetch http://leaf.dragonflybsd.org/~beket/mq-mpsafe.diff git apply mq-mpsafe.diff make buildkernel make installkernel reboot Reached this far and currently face the issue which has effectively disabled networking. intr 2 at 40001/4 hz, livelock limit engaged Details posted in a separate thread. thanks Saifi.
Re: SMP users needed to test patch
2009/11/4 Saifi Khan saifi.k...@datasynergy.org: On Wed, 4 Nov 2009, Stathis Kamperis wrote: Hello everyone! I'd like to mark mq*() syscall as MPSAFE, but before that I need someone to test them in an SMP capable machine running SMP kernel. I only have UP machines around. So, if anyone is able and kind enough, here are some directions on how to do it. I assume s\he is running HEAD. cd /usr/src fetch http://leaf.dragonflybsd.org/~beket/mq-mpsafe.diff git apply mq-mpsafe.diff make buildkernel make installkernel reboot Reached this far and currently face the issue which has effectively disabled networking. intr 2 at 40001/4 hz, livelock limit engaged Details posted in a separate thread. thanks Saifi. Thank you Saifi! I very much appreciate the time you've put into this. Did you by any chance try without my patch and SMP/APIC set in your kernel configuration file ? Best regards, Stathis Kamperis
Re: SMP users needed to test patch
On Wed, 4 Nov 2009, Stathis Kamperis wrote: 2009/11/4 Saifi Khan saifi.k...@datasynergy.org: On Wed, 4 Nov 2009, Stathis Kamperis wrote: Hello everyone! I'd like to mark mq*() syscall as MPSAFE, but before that I need someone to test them in an SMP capable machine running SMP kernel. I only have UP machines around. So, if anyone is able and kind enough, here are some directions on how to do it. I assume s\he is running HEAD. cd /usr/src fetch http://leaf.dragonflybsd.org/~beket/mq-mpsafe.diff git apply mq-mpsafe.diff make buildkernel make installkernel reboot Reached this far and currently face the issue which has effectively disabled networking. intr 2 at 40001/4 hz, livelock limit engaged Details posted in a separate thread. thanks Saifi. Thank you Saifi! I very much appreciate the time you've put into this. Did you by any chance try without my patch and SMP/APIC set in your kernel configuration file ? Unfortunately no ! Let me try and revert the patch i applied and rebuild the kernel. Will post an update on this. thanks Saifi.
Re: SMP users needed to test patch
On Wed, 4 Nov 2009, Stathis Kamperis wrote: Did you by any chance try without my patch and SMP/APIC set in your kernel configuration file ? Commented out the following option and 'recompiled' the kernel. ### options APIC_IO Did not see any of the 'livelock' notifications. So, i ventured out and cloned in the 'pcca-test'. On running 'make' in the mqueue.h/ make gcc -Wall -W -Wformat-nonliteral -Wcast-align -Wpointer-arith -Wbad-function-cast -Wmissing-prototypes -Wstrict-prototypes -Wmissing-declarations -Winline -Wundef -Wnested-externs -Wcast-qual -Wshadow -Wwrite-strings -Wno-unused-parameter -Wfloat-equal -Wswitch -Wbad-function-cast -g -lrt t_mq_ambig.c -o t_mq_ambig /usr/libexec/binutils217/elf/ld: cannot find -lrt *** Error code 1 Stop in /home/saifi/dragonflybsd/pcca-tests/mqueue.h. Does this imply that i need to buildworld as well ? i suppose 'librt' is POSIX real time extensions. Here is the 'dmesg', (it it helps). ... Copyright (c) 2003-2009 The DragonFly Project. Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. DragonFly d15a49f-DEVELOPMENT #1: Thu Nov 5 13:21:29 IST 2009 r...@amd64x2.datasynergy.org:/usr/obj/usr/src/sys/AMD64-P-MQ Calibrating clock(s) ... TSC clock: 2310389259 Hz, i8254 clock: 1193136 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ (2310.50-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x60fb1 Stepping = 1 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT Features2=0x2001SSE3,CX16 AMD Features=0xea500800SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow! AMD Features2=0x11fLAHF,CMP,SVM,ExtAPIC,CR8,Prefetch Cores per package: 2 L1 2MB data TLB: 8 entries, fully associative L1 2MB instruction TLB: 8 entries, fully associative L1 4KB data TLB: 32 entries, fully associative L1 4KB instruction TLB: 32 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 2MB unified TLB: 0 entries, disabled/not present L2 4KB data TLB: 512 entries, 4-way associative L2 4KB instruction TLB: 512 entries, 4-way associative L2 unified cache: 512 kbytes, 64 bytes/line, 1 lines/tag, 16-way associative real memory = 2013003776 (1965824K bytes) Physical memory chunk(s): 0x1000 - 0x0009bfff, 634880 bytes (155 pages) 0x01007000 - 0x77fa, 1996132352 bytes (487337 pages) avail memory = 1879461888 (1835412K bytes) lapic: divisor index 0, frequency 100455852 Hz SMP: CPU0 apic_initialize(): lint0: 0x0700 lint1: 0x00010400 TPR: 0x008f SVR: 0x01ff DragonFly/MP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x80050010, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x80050010, at 0xfee0 Warning: APIC I/O disabledAPIC_IO disabled Finish MP startup SMP: AP CPU #1 Launched! SMP: CPU1 apic_initialize(): lint0: 0x0001 lint1: 0x00010400 TPR: 0x008f SVR: 0x01ff Active CPU Mask: 0003 objcache(exec-args): too small for ncpus, adjusting cluster_limit 16-32 Preloaded elf kernel /kernel at 0x80fde000. Preloaded elf obj module /modules/acpi.ko at 0x80fde290. start scheduler helpers on cpus: 0 1 start dummy scheduler helpers on cpus: 0 1 wlan: 802.11 Link Layer kbd: new array size 4 kbd1 at kbdmux0 crypto: crypto core sched_ithd: stray interrupt 7 on cpu 1 md0: Malloc disk ACPI: RSDP 0xfb840 00014 (v0 ACPIAM) ACPI: RSDT 0x77fc 00040 (v1 _ASUS_ Notebook 04000730 MSFT 0097) ACPI: FACP 0x77fc0200 00084 (v2 A_M_I_ OEMFACP 04000730 MSFT 0097) ACPI: DSDT 0x77fc05c0 04D44 (v1 A0557 A0557000 INTL 20051117) ACPI: FACS 0x77fce000 00040 ACPI: APIC 0x77fc0390 00070 (v1 A_M_I_ OEMAPIC 04000730 MSFT 0097) ACPI: MCFG 0x77fc0400 0003C (v1 A_M_I_ OEMMCFG 04000730 MSFT 0097) ACPI: SLIC 0x77fc0440 00176 (v1 _ASUS_ Notebook 04000730 MSFT 0097) ACPI: OEMB 0x77fce040 00060 (v1 A_M_I_ AMI_OEM 04000730 MSFT 0097) ACPI: HPET 0x77fc5310 00038 (v1 A_M_I_ OEMHPET0 04000730 MSFT 0097) ACPI: SSDT 0x77fc5350 00248 (v1 A_M_I_ POWERNOW 0001 AMD 0001) acpi0.nexus0.root0 acpi0: _ASUS_ Notebook [tentative] on motherboard acpi0: Power Button (fixed) Warning: ACPI is disabling APM's device. You can't run both pci_open(1):mode 1 addr port (0x0cf8) is 0x8000c060 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=05] [hdr=00] is there (id=03ea10de) AcpiOsDerivePciId: bus 0 dev 1 func 0 ACPI timer looks BAD min = 5, max = 12, width = 7 ACPI timer looks BAD min = 5, max = 793, width = 788 ACPI timer looks GOOD min = 5, max = 6, width = 1 ACPI timer looks BAD min
Re: SMP users needed to test patch
2009/11/4 Saifi Khan saifi.k...@datasynergy.org: On Wed, 4 Nov 2009, Stathis Kamperis wrote: Did you by any chance try without my patch and SMP/APIC set in your kernel configuration file ? Commented out the following option and 'recompiled' the kernel. ### options APIC_IO Did not see any of the 'livelock' notifications. Alright, thanks. I suppose that those livelock events are irrelevant to my work then. So, i ventured out and cloned in the 'pcca-test'. On running 'make' in the mqueue.h/ make gcc -Wall -W -Wformat-nonliteral -Wcast-align -Wpointer-arith -Wbad-function-cast -Wmissing-prototypes -Wstrict-prototypes -Wmissing-declarations -Winline -Wundef -Wnested-externs -Wcast-qual -Wshadow -Wwrite-strings -Wno-unused-parameter -Wfloat-equal -Wswitch -Wbad-function-cast -g -lrt t_mq_ambig.c -o t_mq_ambig /usr/libexec/binutils217/elf/ld: cannot find -lrt *** Error code 1 Stop in /home/saifi/dragonflybsd/pcca-tests/mqueue.h. Oh, you must be running 2.4.x, right? The librt has been born in 2.5.x :) So there isn't much you can do. thanks Saifi. No, I thank you. Best regards, Stathis Kamperis
AHCI driver enhancement on master branch for DVD probe/test
People with issues probing DVD drives over AHCI please test with the latest master branch and report if the problem has been resolved or not. Use a verbose boot and try to capture any 'ahcix.x' lines if it still doesn't work. Also please post if you previously had a non-working DVD drive which now works. This only applies to the AHCI driver the SILIcon Image driver. -Matt Matthew Dillon dil...@backplane.com
Re: amd64 - invitation to test
Now, that GSoC is over, I have some spare time to say thanks. I'd like to thank all the people who have tested the amd64 port, namely Matthew Dillon and Antonio Huete Jimenez. Thanks for all the bugs you've found and fixed.
Re: amd64 - invitation to test
Jordan Gordeev wrote: Now, that GSoC is over, I have some spare time to say thanks. I'd like to thank all the people who have tested the amd64 port, namely Matthew Dillon and Antonio Huete Jimenez. Thanks for all the bugs you've found and fixed. Thanks to you for your great work! If every SoC works out as well as your last two did, we'd be very happy. cheers simon
Re: amd64 - invitation to test
On Tue, Aug 18, 2009 at 8:57 AM, Simon 'corecode' Schubertcorec...@fs.ei.tum.de wrote: Jordan Gordeev wrote: Now, that GSoC is over, I have some spare time to say thanks. I'd like to thank all the people who have tested the amd64 port, namely Matthew Dillon and Antonio Huete Jimenez. Thanks for all the bugs you've found and fixed. Thanks to you for your great work! If every SoC works out as well as your last two did, we'd be very happy. cheers simon Jordan, I would like to echo Simon's words. Congratulations on a successful SoC and thank you for all of your hard work. Sam
Re: amd64 - invitation to test
I'd like to echo Simon's words too. You have really gotten us over the hump on amd64. We always expected there would be a lot of issues. FreeBSD is still having issues, after all, and they've had their 64-bit port in their tree for twice as long as we have. Sure we didn't have the vkernel working, and I think the 32-bit compat support was a bit out of reach in the first place, and yes I would like to see the vkernel operational in a near-term time frame... but AMD64 is also far FAR more stable now then it was before and you got SMP working! That is a big deal in my book. Our amd64 stuff is now to the point where mere mortals can actually run it and help track down bugs. So I consider the GSOC a success even if all the goals were not met by the deadline. You should here some the horror stories posted on the GSOC mentor list :-). DragonFly GSOC projects are more trial-by-fire then other vendors but we also offer a ton more support on IRC then I think virtually anyone else. As someone who has actually had to hire programmers in the past, I guarantee the experience will be a major benefit to our GSOC students. Universities just don't prepare students for the real world when it comes to Computer Science. -Matt
Re: amd64 - invitation to test
The master development branch in the our main repo now has all of Jordan's AMD64 work, plus additional work in the last few days which gets SMP working and which stabilizes native buildworlds and installworlds done from a 64 bit environment, including the boot code. Modules will compile but cannot yet be loaded. -Matt
10TB test completed w/ AHCI
The AHCI driver passed its 10TB test (with 5x2TB drives behind a PM). So both the SILI 3132 driver and the AHCI driver have now passed their storage tests. There are still two outstanding bug reports, one related to a particular DVD writer which doesn't work w/cdrecord and one related to AHCI not working on a fancy Intel server motherboard. Basically, though, the driver works and in places where it does work it works quite well. -Matt
Re: amd64 - invitation to test
Aggelos Economopoulos wrote: Jordan Gordeev wrote: It's time public testing of the amd64 port begins. The code is available in my git repo at git://leaf.dragonflybsd.org/~smtms/dragonfly.git in branches amd64 and amd64+hacks. The amd64+hacks branch contains what amd64 contains + some band aid to keep the system working even when a proper fix to a known problem is not yet developed. Great! You can now begin to find and report (and fix) bugs. Does it work in an emulator and if so, which ones are known to work? Do you plan to offer a CD image we can install from (not necessarily using the installer, the old cpdup method is fine at this stage)? It is known to work in qemu. See Matt's instructions for using /usr/src/test/amd64. It should work in any emulator that supports DragonFly. It sure works on real hardware. I do not plan to offer a CD image. I'm unable to imagine the use case. The amd64 port is a work in progress, so one should be able to build and re-build from source, and the lack of CD image shouldn't be a problem. Can we build amd64 world and kernel on an amd64 installation? You can. However, I'm yet to test if world and kernel built on amd64 actually work. :-)
Re: amd64 - invitation to test
Jordan Gordeev wrote: It's time public testing of the amd64 port begins. The code is available in my git repo at git://leaf.dragonflybsd.org/~smtms/dragonfly.git in branches amd64 and amd64+hacks. The amd64+hacks branch contains what amd64 contains + some band aid to keep the system working even when a proper fix to a known problem is not yet developed. Great! You can now begin to find and report (and fix) bugs. Does it work in an emulator and if so, which ones are known to work? Do you plan to offer a CD image we can install from (not necessarily using the installer, the old cpdup method is fine at this stage)? Can we build amd64 world and kernel on an amd64 installation? Nice work, Aggelos
Re: amd64 - invitation to test
There is a build system Makefile in /usr/src/test/amd64 that you can use. That can create the whole environment from scratch and all you need to do is hook it up to Jordan's git repo. It takes a long time to generate the environment since it has to run two buildworlds and generate a disk image for qemu to use. It will also build the qemu binary needed to run the environment. Once everything is built initially the engineering test cycle on just a kernel rebuild is very fast. I'm not sure if Jordan merged his sources from HEAD yet so you might have to transplant the Makefile from HEAD into his repo checkout. -Matt Matthew Dillon dil...@backplane.com
Re: [issue1357] A cloned tap device patch (for a person to test KQEMU 1.4.0pre1 for QEMU 0.10.1)
Hi Sephe, Sorry for the slow res too. The response mail to sub...@... failed some reasons, also it took me a few days to realize :-) I'll test your 3 patches for a while and your patches (including 'closed-out' flag operation) work well with qemu/kqemu environment. BTW, I guess we need a small patch for qemu to open correct tap device node (ex /dev/tap*0*), as I attached, but it is another story. I'm appreciate if someone can take care of the patch, if need. thanks a lot for your assistance. -Naoya On Mon, May 18, 2009 at 7:40 AM, Sepherosa Ziehau (via DragonFly issue tracker) sub...@crater.dragonflybsd.org wrote: Sepherosa Ziehau sepher...@gmail.com added the comment: On Sun, May 17, 2009 at 12:06 PM, Sepherosa Ziehau sepher...@gmail.com wrote: On Thu, May 14, 2009 at 1:11 PM, Naoya Sugioka naoya.sugi...@gmail.com wrote: Hi Sephe, Thank you for your comment. Here I made a patch which includes you pointed. I hope you will review this patch too. - Naoya Sorry for the delay, I will review it today. Could you test following three patches: http://leaf.dragonflybsd.org/~sephe/0001-tap-4-Add-ifclone-support.patch http://leaf.dragonflybsd.org/~sephe/0002-tap-4-Correct-reversed-logic.patch http://leaf.dragonflybsd.org/~sephe/0003-tap-4-More-fixes-to-tapuponopen.patch The first one is an adjusted version of your submitted patch. Best Regards, sephe _ DragonFly issue tracker b...@lists.dragonflybsd.org http://bugs.dragonflybsd.org/issue1357 _ net.c.diff Description: Binary data
Re: A cloned tap device patch (for a person to test KQEMU 1.4.0pre1 for QEMU 0.10.1)
Here is what I saw on messages when booting guest Linux. May 5 11:03:28 pata kernel: ata0: FAILURE - oversized DMA transfer attempt 98304 65536 May 5 11:03:28 pata kernel: acd0: setting up DMA failed Any comments are welcome. thank you. -Naoya On 5/5/09, Naoya Sugioka naoya.sugi...@gmail.com wrote: Hello, As some of you already know, I wrote a kqemu patch for DragonFly, but I found very simple problem to use it. I cannot create tap0 cloned interface by ifconfig comamnd now, so I made a patch. Attachment is a suggested patch to create tap cloned tap device (only tap device) only applicapable with HEAD. I 'd like to post this patch to share with community and get a feedback from. I'm start using this to use QEMU/KQEMU as a virtual server of DragonFly/FreeBSD. Unfortuantelly, I saw DMA address error when using wirh Linux guest though... thank you, -Naoya
Stress test stops
Hi, I followed the stress test guide[1] using ./run.sh all.cfg. After some time it suddenly stopped. The last line said something like parant 18, scm 9. Since I got no answer on IRC I triggered a panic. The results can be found here: http://reezer.freeshell.org/dragonfly/ [1] from http://wiki.dragonflybsd.org/index.cgi/HowToStressTest
Re: Stress test stops
:Hi, : :I followed the stress test guide[1] using ./run.sh all.cfg. :After some time it suddenly stopped. The last line said something :like parant 18, scm 9. Since I got no answer on IRC I triggered :a panic. The results can be found here: :http://reezer.freeshell.org/dragonfly/ : :[1] from http://wiki.dragonflybsd.org/index.cgi/HowToStressTest Ok, I'm downloading the cores now. -Matt Matthew Dillon [EMAIL PROTECTED]
Re: Stress test stops
:Hi, : :I followed the stress test guide[1] using ./run.sh all.cfg. :After some time it suddenly stopped. The last line said something :like parant 18, scm 9. Since I got no answer on IRC I triggered :a panic. The results can be found here: :http://reezer.freeshell.org/dragonfly/ : :[1] from http://wiki.dragonflybsd.org/index.cgi/HowToStressTest The vmcore is not readable, I can't download it. Could you fix the perms on it? -Matt Matthew Dillon [EMAIL PROTECTED]
Re: Stress test stops
Matthew Dillon wrote: The vmcore is not readable, I can't download it. Could you fix the perms on it? Oops, it's fixed now. -- Christian
Re: Stress test stops
: :Hi, : :I followed the stress test guide[1] using ./run.sh all.cfg. :After some time it suddenly stopped. The last line said something :like parant 18, scm 9. Since I got no answer on IRC I triggered :a panic. The results can be found here: :http://reezer.freeshell.org/dragonfly/ : :[1] from http://wiki.dragonflybsd.org/index.cgi/HowToStressTest Everything is stuck waiting for VM pages to free up, and the pageout demon is stuck in wdrain which means it is waiting for in-progress writes to the device driver to complete. Hmm. The pageout demon is locked up trying to flush to a MFS filesystem (your /tmp) and because of that it can't actually flush out any VM pages to a real disk. The MFS filesystem itself is stuck in the page-fault code, resulting in a deadlock. There is no easy fix for this at the moment, short of not running a stress test on a large MFS filesystem. The pageout daemon would have to be split into a light-weight and heavy-weight version, similar to how I split the bufdaemon into two threads. Alternatively the MFS code would need to be redone. -Matt Matthew Dillon [EMAIL PROTECTED]
CARP test ISO available
This is an ISO built from yesterday's RELEASE sources. The CARP patch has been applied and CARP is compiled into GENERIC. More info in the page below: http://rnrdoctor.sytes.net/~szg/dfly/ If there is a problem with the site or the download, please contact me off-list. Happy Testing! :-D -- Gergo Szakal MD [EMAIL PROTECTED] University Of Szeged, HU Faculty Of General Medicine /* Please do not CC me with replies, thank you. */
jira bug tracking system test instance available
Alright! I set up one jira test instance at http://jira.corecode.ath.cx/. It's running on chlamydia, so expect it to be slow now and then because this box chronically has too few memory. Try it! I will add the people i know to the administrator/developer groups (when I got time). If *you* want to try out these groups, just drop me a line. In any case, please provide feedback! cheers simon -- Serve - BSD +++ RENT this banner advert +++ASCII Ribbon /\ Work - Mac +++ space for low $$$ NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \ PGP.sig Description: This is a digitally signed message part
