DragonFlyBSD bugtracker: Issueshttps://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082009-07-20T01:24:37ZDragonFlyBSD bugtracker
Redmine DragonFlyBSD - Bug #1430 (New): Buggy w(1)?https://bugs.dragonflybsd.org/issues/14302009-07-20T01:24:37Zhasso
<p>With single user logged in from X (kdm is in use):</p>
<p>$ w<br />w: /dev/:0: No such file or directory<br /> 9:21PM up 2 days, 3:21, 0 users, load averages: 0.00, 0.02, 0.00<br />USER TTY FROM LOGIN@ IDLE WHAT<br />$</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 #1293 (New): 2.2.1-REL Installer Requesthttps://bugs.dragonflybsd.org/issues/12932009-02-20T11:43:06Zmk
<p>I would like the option (when installing a Hammer FS) to choose if I <br />want to use PFS's or not, and if so, which directories I want to map to <br />PFS's.</p>
<p>Thanks, MK</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 #1198 (New): DDB loops panic in db_read_byteshttps://bugs.dragonflybsd.org/issues/11982009-01-05T22:50:04Zcorecode
<p>I have some panic which I can't debug because there is a flurry of panic<br />messages on my screen. The offender is:</p>
<p>sys/platform/pc32/i386/db_interface.c:208</p>
<p>I see that ddb uses longjmp, but seems that doesn't work here somehow.</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 #731 (New): system freeze on "slice too large"https://bugs.dragonflybsd.org/issues/7312007-07-15T20:11:05Zcorecode
<p>hey,</p>
<p>i've now had twice a nasty freeze (kind of) with something like this (hand transcribed):</p>
<p><code>dscheck(#ad/0x20021): slice too large 2/2</code><br />..</p>
<p>then vinum tells me that it put "build" down and continues:</p>
<p>fatal: build.p0.s0 read error, offset 33831591936 for 4096 bytes<br />build.p0.s0: user buffer offset 10209280000 for 4096 bytes</p>
<p>(more slice too large follow)</p>
<p>then, the namecache does</p>
<p>blocked on 0xd4fb7b58 "corecode"</p>
<p>and repeats it every 30 seconds or so. system is unoperable at this point.</p>
<p>breaking to the debugger works, but dumpsys does not work:</p>
<pre>
dumping to dev #ad/0x20023, blockno 2130432
dump failed, reason: area improper
</pre>
<p>i'm running:<br /><pre>
DragonFly sweatshorts.home.corecode.ath.cx 1.9.0-DEVELOPMENT DragonFly 1.9.0-DEVELOPMENT #14: Sun Jun 17 11:03:58 CEST 2007 corecode@sweatshorts.home.corecode.ath.cx:/usr/build/obj/usr/build/src/sys/SWEATSHORTS i386
</pre></p>
<p>i've attached relevant outputs.</p>
<p>thanks,<br /> simon</p> DragonFlyBSD - Bug #679 (New): Netgraph backward compatibility for old *LEN constantshttps://bugs.dragonflybsd.org/issues/6792007-06-05T07:56:01Znant
<p>Maintain the old *LEN netgraph constants around for some time to allow<br />the building of earlier mpd (Multi-link PPP Daemon).</p>
<p>Pointed out by: Alexander Motin <<a class="email" href="mailto:mav@freebsd.org">mav@freebsd.org</a>><br />Obtained from: FreeBSD</p>
<p>BTW: Do we need a BURN_BRIDGES kernel option?</p>
<p>Thanks,<br />Nuno</p> DragonFlyBSD - Bug #600 (New): /sys/libkern/karc4randomhttps://bugs.dragonflybsd.org/issues/6002007-04-11T17:14:04Zrobin_carey5
<p>What is the point of keeping/using the in-kernel arc4<br />random number generator when you already have a very<br />good/superior IBAA/L15 random number generator.</p>
<p>If you need a u_int32_t quantity then simply add a<br />function to /sys/kern/kern_nrandom.c to produce a<br />u_int32_t.</p>
<p>--</p>
<p>Some issues with /sys/libkern/karc4random.c :</p>
<p>(a) If you intend to keep /sys/libkern/karc4random.c I<br />recommend you make a modification to it to improve<br />performance: Every time the karc4_random() function is<br />called it calls getmicrotime(), to check the time, and<br />it also checks the number of runs made, to see if it<br />should reseed itself. You can make a big performance<br />improvement by removing this call to getmicrotime()<br />and instead simply checking the number of runs to<br />determine when it should reseed itself.</p>
<p>(b) The karc4random.c file uses u_int8_t types for<br />arc4_i, arc4_j and arc4_t so there is no need for the<br />% 256 operation - another performance improvement.</p>
<p>(c) In arc4_init() you are throwing away 256*4 bytes<br />of output, when you only need to throw away the first<br />256 bytes of output.</p>
<p>Sincerely,<br />R Carey.</p>
<pre><code>_<em><i></em></i>__<em>_</em>_______________________________________________<br />Yahoo! Answers - Got a question? Someone out there knows the answer. Try it<br />now.<br /><a class="external" href="http://uk.answers.yahoo.com/">http://uk.answers.yahoo.com/</a></code></pre> 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> DragonFlyBSD - Bug #341 (New): Vinum erroneously repors devices as busyhttps://bugs.dragonflybsd.org/issues/3412006-10-05T22:58:36Zcorecode
<p>Most of the time vinum reports devices as busy when they are not. At least I<br />can't find a different way than to use stop -f.</p>