DragonFlyBSD bugtracker: Issueshttps://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082010-05-27T06:39:15ZDragonFlyBSD bugtracker
Redmine DragonFlyBSD - Bug #1774 (New): New IP header cleanup branch available for testinghttps://bugs.dragonflybsd.org/issues/17742010-05-27T06:39:15Zdillon
<p>My leaf repo now has a branch called 'iphdr'. Here's the git remote setup:</p>
<pre>
[remote "dillon"]
url = git://leaf.dragonflybsd.org/~dillon/dragonfly.git
fetch = +refs/heads/*:refs/remotes/dillon/*
</pre>
<pre>
$ git fetch dillon
$ git branch iphdr dillon/iphdr
$ git checkout iphdr
</pre>
<p>I have done basic testing with ipfw, pf, ipv4 fragmentation, ipv4 TCP, a little bridging, if_tap, and ipv4 UDP.<br />Tons of other things haven't been tested yet. ipv6, bpf filters, carp, more extensive ipfw2 and pf, and so forth. Donn't bother with IPSEC, it has other issues which will have to be solved in the next stage.<br />Only do testing if you have some experience with the interfaces in question.<br />This branch contains the network byte ordering and adjustment fixes for ip_len, ip_off, and a large chunk of the protosw cleanup. I am going to leave the branch alone except for bug fixes.</p>
<p>--</p>
<p>I am now starting work on another branch that will contain a rewrite of the whole ether/ip demux and dispatch mechanic. All protocols will become per-cpu and there will be just one protocol support thread for each cpu. NETISRs will go away and be replaced with a more direct netmsg queueing operation. The toeplitz hash will be integrated into the demux mechanic (probably integrated with ip_lengthcheck()), so the cpu switch will occur even before a protocol is handed the packet. Fast-forwarding will still occur in the demux and be able to bypass netmsg queueing.</p>
<p>Hopefully when all is said and done the combination of the stage 1 fixes now available and this stage 2 work will give us a huge degree of flexibility with regards to managing packet mbufs, including an ability to trivially requeue them (something IPSEC and other tunnel implementations need to be able to do).</p>
<p>This second stage will probably take a week at least.</p>
<p>-Matt</p> DragonFlyBSD - Bug #1695 (New): NFS-related system breakdownhttps://bugs.dragonflybsd.org/issues/16952010-03-14T06:22:19ZAnonymous
<p>Hi all.</p>
<p>I do a cp(1) from /mnt/nfs (which is a zfs fileystem NFS-exported by an<br />opensolaris installation) to my /home/beket directory (HAMMER fs).</p>
<p>After a few MBs having being copied, cp(1) process stalls in 'getblk' state.<br />Also it is unkillable by ^C. From that point there's downhill.</p>
<p>Many commands will block if I issue them, such as 'mount' or 'df'. I can still<br />view top(1) update its contents but the system is on the edge. dmesg shows<br />sparse messages 'nfs server 10.0.0.1:/export/nfs: not responding' or<br />'[diagnostic]: $address block on cache_something ""'. If I break into the<br />debugger, I get nothing unusual. scgetc < sckbdevent < kbd_xxxx < taskqueue_yyyy<br />etc.</p>
<p>I tried to kill X and the system hang to the point that a cold reset was<br />necessary. I once managed to resume after typing 'c' in db> prompt, but that<br />doesn't always succeed.</p>
<p>This situation is, I think, 100% reproducible. Also, I don't have problems<br />copying stuff from|to a linux NFS client.</p>
<p>Cheers</p> DragonFlyBSD - Bug #1634 (New): panic: spin_lock: 0xe4ad1320, indefinitive wait!https://bugs.dragonflybsd.org/issues/16342009-12-22T09:25:14Zelekktretterr
<p>Our dragonfly box has got a panic last night. it runs master from last week.</p>
<p>I wrote down some text from the panic:</p>
<p>mp_lock = 00000002; cpuid = 2</p>
<p>Trace beginning at frame 0xe42d3b88</p>
<p>panic(...)<br />panic(...)<br />exponential_backoff(ff010000, 1 ,3c, e4ad1320, c727dbb)<br />spin_lock_wr_contested(e4ad1320, 0000000)<br />crfree(e4ad12b0,2, e42f3cc4, c00ef73, e42f3c00)<br />nlookup_done(e42f3c00, e4960720, c0304fe3, 0, c0384b5c)<br />sys_lstat(e32f3cf0,6,0,0dd9fce18)<br />syscall2(e42f3d440)</p>
<p>Whoever can understand this, can you tell me what happened and how can<br />this be fixed?</p>
<p>Also, is there any way to automate this: when panic occurs, automatically<br />start a memory dump process and then automatically reboot? I've been going<br />to the data center way too many times recently to investigate why the box<br />has crashed and it would be very helpful.</p>
<p>Petr</p> DragonFlyBSD - Bug #1594 (New): Kernel panic during boot from Live CD on Dell E6400https://bugs.dragonflybsd.org/issues/15942009-11-03T21:52:42Zbodie
<p>Hi all,</p>
<p>I'm trying to install 2.4.1 release on laptop Dell E6400. I have problems to<br />install FreeBSD or DragonflyBSD on it for about last 6 months. Everytime kernel<br />panic and I end in ddb, but keyboard is not working then. I can use this Live CD<br />or install it on hdd when I disable ACPI. In NetBSD or OpenBSD it's working and<br />on OpenBSD suspend/resume is not running.</p>
<p>I can't post much more details. Just what you can see in attachment as keyboard<br />is not working and I don't have serial console or USB -> RS232 converter.</p> DragonFlyBSD - Bug #1559 (New): kernel traphttps://bugs.dragonflybsd.org/issues/15592009-10-06T00:00:08Zphma
<p>This always happens when booting the 2.5.1 kernel I just compiled in normal <br />mode. It doesn't happen in safe mode. I can't get a kernel dump. It's a Dell <br />Latitude laptop.</p>
<p>phma<br />----<br />ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto<br />xl0: MAC address: 000bdb02db25<br />cbb0: TI1420 PCI Card Bus bridge at device 1.0 on pci2<br />cardbus0:CardBus bus or cbb0<br />pccard0: 16-bit pccard bus or cpp0<br />kernel trap 12 with interrupts disabled<br />Fatal trap 12 page fault while in kernel mode<br />fault virtual address =0xb23f<br />faultcode=supervisor read, page not present<br />ip=0x8:0xc00fc42f<br />sp 0x10:0xc089282c<br />fp 0x10:0xc089288c<br />code seg base 0x0 limit 0xfffff type 0x1b<br />dpl0 pres 1 def32 1 gran 1<br />eflags=resume IOPL=0<br />current process 0 (swapper)<br />current thread pri 12<br />kerneltype 12 trap code=0<br />Stopped at 0xc00fc42f cmpb %cs:0xb23f,%bh<br />trace<br />kernbase(b0a,c053966e,b,0,c08928d8) at 0xc00fc42f</p> DragonFlyBSD - Bug #1525 (New): boehm-gc problemshttps://bugs.dragonflybsd.org/issues/15252009-09-22T00:58:47Zhasso
<p>Although devel/boehm-gc builds on DragonFly, there are problems - its own <br />testuite doesn't run. The test for garbage collecting functionality either <br />segfaults or hangs and if boehm-gc is built with threading support (making it <br />treat DragonFly as FreeBSD), threading test does the same.</p>
<p>Note, that boehm-gc is used by in many software pieces (mainly various <br />programming languages) and is probably onw of reasons why so many languages <br />actually fail to run on DragonFly.</p>
<p>How to test:</p>
<p>fetch <a class="external" href="http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc-7.1.tar.gz">http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc-7.1.tar.gz</a><br />tar zxf gc-7.1.tar.gz<br />cd gc-7.1<br />./configure --disable-threads<br />gmake<br />gmake check</p> DragonFlyBSD - Bug #1463 (New): Mountroot before drives are initializedhttps://bugs.dragonflybsd.org/issues/14632009-08-25T15:58:13Zelekktretterr
<p>Hi,</p>
<p>As per Sachas comment about splitting my previous bug report into separate<br />ones. here is an issue that has been bugging me on this box. (HP Proliant<br />DL180 G5)</p>
<p>It seems that mountroot is ran before da0 (and cd0) gets initialized on<br />this box. mountroot then complains that da0s1 is missing.</p>
<p>Here is a verbose dmesg:</p>
<p><a class="external" href="http://leaf.dragonflybsd.org/mailarchive/bugs/2009-08/msg00128.html">http://leaf.dragonflybsd.org/mailarchive/bugs/2009-08/msg00128.html</a>.</p>
<p>Note that this problem seems to happen randomly when booting from live cd.<br />But happens all the time when booting from disk.</p>
<p>Petr</p> DragonFlyBSD - Bug #1313 (New): Signal code in kernel needs major overhaul (signal queues, si_cod...https://bugs.dragonflybsd.org/issues/13132009-03-13T15:04:10Zhasso
<p>Although our siginfo structure has a si_code member, we don't use it and <br />don't even have a defines related to it.</p>
<p><a class="external" href="http://www.opengroup.org/onlinepubs/009695399/basedefs/signal.h.html">http://www.opengroup.org/onlinepubs/009695399/basedefs/signal.h.html</a></p> DragonFlyBSD - Bug #1246 (New): bad resolution (monitor desync) with livedvdhttps://bugs.dragonflybsd.org/issues/12462009-01-28T04:14:28ZPrzem0l
<p>hi AGAIN,</p>
<p>i`ve turned clocks on my quad q6600 to stock speed and i`ve set up fresh install<br />on pure HDD (not a virtual machine).</p>
<p>OFC after installation, next boot (with manually typed: startx) shows me an<br />installation desktop.</p>
<p>I did all steps correctly, so what is the problem? I have Gigabyte P35-DS3, 8 GB<br />RAM, Quad Q6600, GF8800GT 512, Chieftec 750W.</p>
<p>gtz to DF team - good job (finally GUI edition).</p> DragonFlyBSD - Bug #1194 (New): SCSI errors while trying to copy photos from my camerahttps://bugs.dragonflybsd.org/issues/11942009-01-01T19:52:07Zelekktretterr
<p>petr@elevator:/mnt/camera/dcim> cp -rf 100_pana /home/petr/photos/Photos_1<br />cp: /home/petr/photos/Photos_1/p1000029.jpg: Bad address<br />cp: /home/petr/photos/Photos_1/p1000030.jpg: Bad address<br />cp: /home/petr/photos/Photos_1/p1000031.jpg: Bad address<br />cp: /home/petr/photos/Photos_1/p1000032.jpg: Bad address<br />cp: /home/petr/photos/Photos_1/p1000033.jpg: Bad address<br />cp: /home/petr/photos/Photos_1/p1000034.jpg: Bad address<br />cp: /home/petr/photos/Photos_1/p1000035.jpg: Bad address<br />cp: /home/petr/photos/Photos_1/p1000036.jpg: Bad address<br />cp: /home/petr/photos/Photos_1/p1000037.jpg: Bad address<br />cp: /home/petr/photos/Photos_1/p1000038.jpg: Bad address<br />cp: /home/petr/photos/Photos_1/p1000039.jpg: Bad address<br />cp: /home/petr/photos/Photos_1/p1000040.jpg: Bad address<br />cp: /home/petr/photos/Photos_1/p1000043.jpg: Bad address<br />cp: /home/petr/photos/Photos_1/p1000048.jpg: Bad address</p>
<p>100_pana is a folder on my cameras SD card.</p>
<p>Dmesg:<br />vm_fault: pager read error, pid 955 (cp)<br />(da0:umass-sim0:0:0:0): <abbr title="10">WRITE</abbr>. CDB: 2a 0 0 1e a3 0 0 0 40 0<br />(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error<br />(da0:umass-sim0:0:0:0): SCSI Status: Check Condition<br />(da0:umass-sim0:0:0:0): DATA PROTECT asc:27,0<br />(da0:umass-sim0:0:0:0): Write protected<br />(da0:umass-sim0:0:0:0): Unretryable error<br />vnode_pager_getpages: I/O read error<br />vm_fault: pager read error, pid 955 (cp)<br />(da0:umass-sim0:0:0:0): <abbr title="10">WRITE</abbr>. CDB: 2a 0 0 1e a3 0 0 0 40 0<br />(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error<br />(da0:umass-sim0:0:0:0): SCSI Status: Check Condition<br />(da0:umass-sim0:0:0:0): DATA PROTECT asc:27,0<br />(da0:umass-sim0:0:0:0): Write protected<br />(da0:umass-sim0:0:0:0): Unretryable error<br />vnode_pager_getpages: I/O read error<br />vm_fault: pager read error, pid 955 (cp)<br />(da0:umass-sim0:0:0:0): <abbr title="10">WRITE</abbr>. CDB: 2a 0 0 1e a3 0 0 0 40 0<br />(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error<br />(da0:umass-sim0:0:0:0): SCSI Status: Check Condition<br />(da0:umass-sim0:0:0:0): DATA PROTECT asc:27,0<br />(da0:umass-sim0:0:0:0): Write protected<br />(da0:umass-sim0:0:0:0): Unretryable error<br />(da0:umass-sim0:0:0:0): <abbr title="10">WRITE</abbr>. CDB: 2a 0 0 1e a3 0 0 0 40 0<br />(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error<br />(da0:umass-sim0:0:0:0): SCSI Status: Check Condition<br />(da0:umass-sim0:0:0:0): DATA PROTECT asc:27,0<br />(da0:umass-sim0:0:0:0): Write protected<br />(da0:umass-sim0:0:0:0): Unretryable error<br />(da0:umass-sim0:0:0:0): <abbr title="10">WRITE</abbr>. CDB: 2a 0 0 1e a3 0 0 0 40 0<br />(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error<br />(da0:umass-sim0:0:0:0): SCSI Status: Check Condition<br />(da0:umass-sim0:0:0:0): DATA PROTECT asc:27,0<br />(da0:umass-sim0:0:0:0): Write protected<br />(da0:umass-sim0:0:0:0): Unretryable error<br />(da0:umass-sim0:0:0:0): <abbr title="10">WRITE</abbr>. CDB: 2a 0 0 1e a3 0 0 0 40 0<br />(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error<br />(da0:umass-sim0:0:0:0): SCSI Status: Check Condition<br />(da0:umass-sim0:0:0:0): DATA PROTECT asc:27,0<br />(da0:umass-sim0:0:0:0): Write protected<br />(da0:umass-sim0:0:0:0): Unretryable error<br />(da0:umass-sim0:0:0:0): <abbr title="10">WRITE</abbr>. CDB: 2a 0 0 1e a3 0 0 0 40 0<br />(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error<br />(da0:umass-sim0:0:0:0): SCSI Status: Check Condition<br />(da0:umass-sim0:0:0:0): DATA PROTECT asc:27,0<br />(da0:umass-sim0:0:0:0): Write protected<br />(da0:umass-sim0:0:0:0): Unretryable error</p>
<p>The images that spew this error actually dont get copied over and theres MANY <br />of them.</p>
<p>Petr</p> DragonFlyBSD - Bug #1193 (New): kernel doesn't recognize cdrom drivehttps://bugs.dragonflybsd.org/issues/11932009-01-01T06:50:08Znonsolosoft
<p>Hi,</p>
<p>on such server dfbsd cdrom doesn't boot, or better, it stop to boot on <br />Mounting root from cd9660:/dev/acd0a<br />no disk named 'acd0a'<br />setrootbyname failed</p>
<p>I've tried with both LATEST-Devel (27/12/2008) and 2.0.1 Release.</p>
<p><a class="external" href="http://manuals.fujitsu-siemens.com/open.php?ID=3419">http://manuals.fujitsu-siemens.com/open.php?ID=3419</a></p>
<p>Happy New Year, \ferz</p> DragonFlyBSD - Submit #1192 (New): KKASSERTs in sys/kern/uipc_{msg,socket}.c are too stricthttps://bugs.dragonflybsd.org/issues/11922008-12-30T06:05:00Zrumcic
<p>The code for nfs root mounts does not use kmalloc-ed space for some vars, while<br />some KKASSERTs in the mentioned files only check for the supplied pointers if<br />they were kmalloc-ed or not.<br />The attached patch adds a check if the supplied pointers are not in user stack<br />(if they are in kernel stack) ... since kmalloc-ed space also resides in the<br />addresses not in user stack, maybe kva_p should be removed (is it used<br />anywhere else?)?<br />-- <br />Regards,<br />Rumko</p> DragonFlyBSD - Bug #1185 (New): need a tool to merge changes into /etchttps://bugs.dragonflybsd.org/issues/11852008-12-20T07:47:08Zwa1ter
<p>I run mergemaster occasionally because it catches files that<br />make upgrade misses. Today it misses about half a dozen or<br />so, including aliases, ftpusers, /usr/Makefile, and maybe a<br />few others I can't remember.</p>
<p>Thanks.</p> DragonFlyBSD - Bug #989 (New): installer/fdisk trouble with wrapped valueshttps://bugs.dragonflybsd.org/issues/9892008-04-14T00:50:05ZDiscodestroyer
<p>Hi there,</p>
<p>I installed DF 2 days ago (the 1.12.1 release). I've choosen a primary partition for the installation (/dev/hda2 in linux slang) and installed the bootlocker on ad0.</p>
<p>After the reboot my laptop hung immediately. I couldn't even see the BIOS password dialog anymore. Whenever I try to reach my bios setup via F2 it crashes on the way.</p>
<p>Without the harddisk it is possible to boot the notebook without any problems.</p>
<p>I bought an external HD case and tried to mount the HD with a live CD: no partition table...</p>
<p>I can't find any reports for that issue, so I thought I will let you know.</p>
<p>Do you need any further information about my hardware?</p>
<p>And is there a way to recover the table?</p>
<p>greets from Germany.</p>
<p>HennR<br />-- <br />GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen!<br />Jetzt dabei sein: <a class="external" href="http://www.shortview.de/?mc=sv_ext_mf@gmx">http://www.shortview.de/?mc=sv_ext_mf@gmx</a></p> DragonFlyBSD - Bug #599 (New): 1.9.0 reproducable panichttps://bugs.dragonflybsd.org/issues/5992007-04-11T10:24:26Zpavalos
<p>Here's a panic I'm getting with some pretty serious network (www) load, then <br />doing a netstat -an:</p>
<p>Unread portion of the kernel message buffer:<br />panic: m_copydata, negative off -1<br />mp_lock = 00000000; cpuid = 0; lapic.id = 00000000<br />boot() called on cpu#0</p>
<p>syncing disks... 5<br />done<br />Uptime: 12d22h0m32s</p>
<p>(kgdb) bt<br />#0 dumpsys () at thread.h:83<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> 0xc01954bb in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:370<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: K&R -> ANSI cleanup status (Closed)" href="https://bugs.dragonflybsd.org/issues/2">#2</a> 0xc01957c0 in panic (fmt=Variable "fmt" is not available.<br />) at /usr/src/sys/kern/kern_shutdown.c:767<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: freebsds pipe-reverse test fails on dfly (Closed)" href="https://bugs.dragonflybsd.org/issues/3">#3</a> 0xc01c3a32 in m_copydata (m=0x0, off=0, len=0, cp=0xee9534b0 "\001\001<br />\b\n\006¦*$\035\bͬ") at /usr/src/sys/kern/uipc_mbuf.c:1014<br /><a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: Rework of nrelease (Closed)" href="https://bugs.dragonflybsd.org/issues/4">#4</a> 0xc020fc25 in tcp_output (tp=0xdae0c720) <br />at /usr/src/sys/netinet/tcp_output.c:690<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: sys/dev cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/5">#5</a> 0xc02152bf in tcp_timer_persist (xtp=0xdae0c720) <br />at /usr/src/sys/netinet/tcp_timer.c:363<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: sys/emulation cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/6">#6</a> 0xc01a6423 in softclock_handler (arg=0xc0386a80) <br />at /usr/src/sys/kern/kern_timeout.c:307<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: /sys/boot cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/7">#7</a> 0xc019d037 in lwkt_deschedule_self (td=Variable "td" is not available.<br />) at /usr/src/sys/kern/lwkt_thread.c:207<br />Previous frame inner to this frame (corrupt stack?)</p>
<p>The kernel and vmcore is being uploaded to leaf. The source is from March 28.</p>
<p>--Peter</p>