DragonFlyBSD bugtracker: Issueshttps://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082009-01-29T02:22:01ZDragonFlyBSD bugtracker
Redmine DragonFlyBSD - Bug #1249 (Feedback): panic: ffs_vfree: freeing free inodehttps://bugs.dragonflybsd.org/issues/12492009-01-29T02:22:01Zrumcic
<p>As far as I know, it happened while another partition was being fsck-ed, but<br />other than that, there shouldn't have been much activity on the machine at the<br />time.</p>
<p>Unread portion of the kernel message buffer:<br />dev = #ad/0x20045, ino = 15, fs = /home<br />panic: ffs_vfree: freeing free inode<br />mp_lock = 00000000; cpuid = 0<br />Trace beginning at frame 0xdd0dd98c<br />panic(dd0dd9b0,c8520000,f1977000,c852012d,dd0dd9d8) at panic+0x14d<br />panic(c051a302,7,dd0dd9f4,0,0) at panic+0x14d<br />ffs_freefile(dd0ddae8,f,0,43ff) at ffs_freefile+0x186<br />handle_workitem_freefile(0,dd0ddce8,c5e4ab0c,dd0ddc8c,c02c5a67) at<br />handle_workitem_freefile+0x89<br />process_worklist_item(c5cfe400,49809881,c05a9ca0,0,c5be98c4) at<br />process_worklist_item+0x18c<br />softdep_process_worklist(0,c5cfe400,dd0ddd84,c02d5c86,0) at<br />softdep_process_worklist+0xa5<br />bio_ops_sync(0,49809881,c5cfe100,ff800000,c) at bio_ops_sync+0x2d<br />sched_sync(0,0,0,0,0) at sched_sync+0x16e<br />kthread_exit() at kthread_exit<br />boot() called on cpu#0<br />Uptime: 15m30s</p>
<p>dumping to dev #ad/0x20041, blockno 2107648<br />dump 3070 3069 3068 3067 3066 3065 3064 3063 3062 3061 3060 3059 3058 3057 3056 <br /><snip><br /> 4 3 2 1 0</p>
<p>GNU gdb 6.7.1<br />Copyright (C) 2007 Free Software Foundation, Inc.<br />License GPLv3+: GNU GPL version 3 or later <<a class="external" href="http://gnu.org/licenses/gpl.html">http://gnu.org/licenses/gpl.html</a>><br />This is free software: you are free to change and redistribute it.<br />There is NO WARRANTY, to the extent permitted by law. Type "show copying" <br />and "show warranty" for details.<br />This GDB was configured as "i386-dragonfly".<br />(kgdb) bt<br />#0 dumpsys () at ./machine/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> 0xc02874e9 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:376<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> 0xc02877ae in panic (fmt=0xc051a302 "ffs_vfree: freeing free inode")<br />at /usr/src/sys/kern/kern_shutdown.c:801<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> 0xc03ced7b in ffs_freefile (pvp=0xdd0ddae8, ino=15, mode=17407)<br />at /usr/src/sys/vfs/ufs/ffs_alloc.c:1700<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> 0xc03d58b8 in handle_workitem_freefile (freefile=0xc5a63e20)<br />at /usr/src/sys/vfs/ufs/ffs_softdep.c:3044<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> 0xc03d4f88 in process_worklist_item (matchmnt=0x0, flags=<value optimized<br />out>) at /usr/src/sys/vfs/ufs/ffs_softdep.c:735<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> 0xc03d689f in softdep_process_worklist (matchmnt=0x0)<br />at /usr/src/sys/vfs/ufs/ffs_softdep.c:622<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> 0xc02d44f4 in bio_ops_sync (mp=0x0) at /usr/src/sys/kern/vfs_mount.c:1227<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: make upgrade broken (Closed)" href="https://bugs.dragonflybsd.org/issues/8">#8</a> 0xc02d5c86 in sched_sync () at /usr/src/sys/kern/vfs_sync.c:243<br /><a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: panic with HEAD (Closed)" href="https://bugs.dragonflybsd.org/issues/9">#9</a> 0xc027ac23 in suspend_kproc (td=Cannot access memory at address 0x8<br />) at /usr/src/sys/kern/kern_kthread.c:158<br />Backtrace stopped: previous frame inner to this frame (corrupt stack?)<br />-- <br />Regards,<br />Rumko</p> DragonFlyBSD - Bug #1144 (Feedback): Incorrect clock under KVMhttps://bugs.dragonflybsd.org/issues/11442008-10-01T12:01:50Zmsylvan
<p>Using kvm-74-3.fc10.x86_64 on Fedora 10 beta.</p>
<p>Host machine is set to EST/EDT. The guest FreeBSD 7 installation reports the<br />correct time (whether UTC or local), but the DragonFly 2.0.1 installer, and the<br />installed system, is ahead by 4 hours.</p>
<p>It appears that, for some reason, the DragonFly/KVM combo is wrongly<br />compensating, presumably assuming (wrongly) that the host clock is set to<br />localtime (UTC-4) and thus adding four hours to it. Any difference in the way<br />the DragonFly and FreeBSD kernels handle the system clock?</p> DragonFlyBSD - Bug #1127 (Feedback): cdrom drive not detectedhttps://bugs.dragonflybsd.org/issues/11272008-08-22T22:48:07Ztgr
<p>Hi, I've got a bit of a problem with the install CD. I've tested this on<br />2.0 and 2.1.0-DEV (i.e. the daily iso downloadable on 2008.08.22). This<br />happens way before I can make any sort of FS, but the same machine's<br />booted up XP, Kubuntu and FBSD5.4.</p>
<p>Anyway, what I can see on the bootup screen of that machine now is as<br />follows:</p>
<p><quote><br />iso_mountroot: can't find rootvp<br />Root mount failed: 6<br />Mounting root from cd9660:acd0<br />no disk named 'acd0'<br />setrootbyname failed<br />iso_mountroot: can't find rootvp<br />Root mount failed: 6<br />Mounting root from cd9660:acd1<br />no disk named 'acd1'<br />setrootbyname failed<br />iso_mountroot: can't find rootvp<br />Root mount failed: 6<br />Mounting root from cd9660:/dev/acd0a<br />no disk named 'acd0a'<br />setrootbyname failed<br />iso_mountroot: can't find rootvp<br />Root mount failed: 6<br /></quote></p>
<p>When I then type "panic", the following appears:</p>
<p><quote><br />panic: panic from console<br />Trace beginning at frame 0xc872ca8<br />panic(c05ce64a,c06bc720,c05d0be3,c0872cd8,6) at panic+0x99<br />panic(c05d0be3,c05ce4a6,696e6170,c0560063,8) at panic+0x99<br />vfs_mountroot_ask(c4360b70,c06702dc,d7886c3c,87d000,c0872d98) at<br />vfs_mountroot_ask+0xd7<br />vfs_mountroot(0,87d000,86fc00,87d000,0) at fvs_mountroot+oxcf<br />mi_startup(86f000,d,c06b2a38,c0872c24,c0872c0c) at mi_startup+0x99<br />begin() at begin+0x42<br />Debugger("panic")<br />Stopped at Debugger+0x44: movb $0,in_Debugger.0<br /></quote></p>
<p>I've run this twice in a row just to verify all the values, in case they<br />changed. They didn't.</p>
<p>If there is any more information I can provide, please do tell. This<br />system is not in use in any other way, all data on the HDs etc is<br />discardable, so anything goes.</p> DragonFlyBSD - Bug #1101 (Feedback): ohci related panichttps://bugs.dragonflybsd.org/issues/11012008-08-01T20:14:06Zpolachok
<p>panic: ohci_abort_xfer: not in process context<br />Trace beginning at frame 0xcc50ed1c<br />panic(cc50ed40, c1697f80, c1a65c80, c1ad6ec8,cc50ed60) at panic+0x8c<br />ohci_abort_xfer(c1697f80, cc50ed84, c045f6ab, c1ad6ec8, c0625364) at<br />ohci_abort_xfer+0xc2<br />ohci_timeout_task(c1ad6ec8, c0625364, ff800000, c0625364,0) at<br />ohci_timeout_task+0x29<br />usb_task_thread(c066400,0,0,0,0) at usb_task_thread+0x9b<br />kthread_exit at kthread_exit<br />Debugger("panic")<br />Stopped at Debugger+0x34 movb $0, in_Debugger.3949</p>
<p>2 usb devices connected: usb flash drive (umass0) and ucom0 (Motorola<br />phone), ppp up and running via ucom.</p> DragonFlyBSD - Bug #979 (Feedback): Failure-prone USB mass storage (SB600? msdosfs? CAM?)https://bugs.dragonflybsd.org/issues/9792008-03-23T00:52:39Zfloid
<p>I'm still very behind when it comes to keeping track of development, so pardon<br />if this is known. I always need to do more testing, but some feedback will help<br />me narrow down the test cases.</p>
<p>Symptoms:</p>
<p>Using 1.12.0-RELEASE, copying from a FAT-formatted 2GB CF card in a reader with<br />a "Genesys" chipset hangs after the first ~82MB have been copied. A "hang" is<br />determined as iostat showing 0 throughput and cp not responding to ^C.</p>
<p>ehci.ko is <strong>not</strong> loaded, so ohci alone was involved here.</p>
<p>Hardware considerations:</p>
<p>SMP kernel (Athlon 64 x2)<br />SB600<br />The reader is part of a Mitsumi floppy combo device<br /> (A slim conventional floppy and USB card reader crammed into one 3.5" box.)</p>
<p>Relevant portion of usbdevs -v:<br />Controller /dev/usb4:<br />addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), <abbr title="0x0000">ATI</abbr>,<br />rev 1.00<br /> port 1 addr 2: full speed, power 500 mA, config 1, USB Reader(0x070e),<br />Genesys(0x05e3), rev 93.25<br /> port 2 powered</p>
<p>...</p>
<p>The following from CAM was found in dmesg. I <strong>believe</strong> this was printed before<br />I rudely pulled the card, however I cannot be sure. (Have we considered<br />timestamping dmesg yet?) There was nothing else new in dmesg.</p>
<p>(da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 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): UNIT ATTENTION asc:28,0<br />(da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed<br />(da0:umass-sim0:0:0:0): Retrying Command (per Sense Data)</p>
<p>Similarly, cp has produced some odd output, but since the card was pulled and<br />the hung cp was left sitting for 24 hours before I got around to reporting this,<br />I'm not sure what happened here. :}</p>
<p>%cd /home/floid/Photos/<br />%cp /mnt/dcim/101olymp/* .<br />cp: ./pa091308.jpg: Bad address<br />cp: ./pa091307.jpg: Bad address<br />cp: /mnt/dcim/101olymp/pa091306.jpg: Input/output error<br />cp: /mnt/dcim/101olymp/pa091303.jpg: Input/output error<br />cp: /mnt/dcim/101olymp/pa091302.jpg: Cross-device link<br />^C</p>
<p>Adding to my confusion, the Linux (Ubuntu 7.10) machine I would attempt to read<br />the card with has a similar hardware configuration (another SB600, another card<br />reader that's also Genesys Logic-based) and its own intractable problems with<br />USB in general! On review, I see that Linux ("2.6.22-14-generic <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> SMP" i686)<br />made it exactly 32MB into the card before a majority of its USB support locked<br />up. Unfortunately that's been happening whenever anyone breathes near that<br />machine, and proprietary VMWare and fglrx modules are involved, so it'll be a<br />while before I can fsck or chkdsk the filesystem structure on the CF card itself!</p>
<p>(The media should be fine, since the camera has had no complaints.)</p>
<p>===</p>
<p>Should I be suspecting the filesystem, CAM (I've noticed Peter Avalos's work on<br />CAM locking but haven't tried it yet), or the basic hardware support?</p> DragonFlyBSD - Bug #911 (Feedback): kldload/kernel linker can exceed malloc reserve and panic systemhttps://bugs.dragonflybsd.org/issues/9112008-01-11T06:31:28Zcorecode
<p>hey,</p>
<p>I just booted with hw.physmem=64m and got a panic when trying to load a module:</p>
<p>panic: kld: malloc limit exceeded</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> 0xc018450c in boot (howto=256) at /usr/build/src/sys/kern/kern_shutdown.c:375<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> 0xc0184661 in panic (fmt=Variable "fmt" is not available.<br />) at /usr/build/src/sys/kern/kern_shutdown.c:800<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> 0xc0182129 in kmalloc (size=78, type=0xc02f5600, flags=2)<br /> at /usr/build/src/sys/kern/kern_slaballoc.c:445<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> 0xc01678b4 in linker_make_file (pathname=0xc641b000 "./nvidia.ko", priv=0xc63ea028, <br /> ops=0xc02f5bc8) at /usr/build/src/sys/kern/kern_linker.c:369<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> 0xc016a773 in link_elf_load_module (filename=0xc641b000 "./nvidia.ko", result=0xc83efc7c)<br /> at /usr/build/src/sys/kern/link_elf.c:604<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> 0xc01684e0 in linker_load_file (filename=0xc641b000 "./nvidia.ko", result=0xc83efca8)<br /> at /usr/build/src/sys/kern/kern_linker.c:272<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> 0xc016871c in sys_kldload (uap=0xc83efcf0) at /usr/build/src/sys/kern/kern_linker.c:724</p>
<p>the problem seems to be that M_LINKER already used 10% of all memory (allegedly). In this case kmalloc() simply panics if passing M_WAITOK without M_NULLOK. This is quite unfortunate. Shouldn't we try to stay alive and print a warning and block, hoping that the problem will resolve itself?</p>
<p>cheers<br /> simon</p> DragonFlyBSD - Bug #901 (Feedback): route show needs to get data from all cpushttps://bugs.dragonflybsd.org/issues/9012007-12-31T00:07:48Zcorecode
<p>when executing `route show' on my MP system, I will get varying results. <br />Additionally, it will print all temporary route entries as well, even for hosts<br />outside the local network.</p> DragonFlyBSD - Bug #847 (Feedback): processes getting stuck on mount pointhttps://bugs.dragonflybsd.org/issues/8472007-11-23T07:03:06Zcorecode
<p>Hey,</p>
<p>I just experienced the infamous ``cache_lock: blocked on 0xd591d418 ""'' message. Checking why the process got stuck revealed that the lock is actually being held by another process which is in the process of doing a lstat(2) on /mnt, a nfs mount which server went away. The stuck process is doing the same, fwiw.</p>
<p>So here it is not a namecache bug, but rather an artifact of nfs being stuck. Anoying nevertheless. Anybody have a clue how to fix that? Yea, mount with -intr. Why don't we do that per default?</p>
<p>cheers<br /> simon</p> DragonFlyBSD - Bug #846 (Feedback): USB bugs:usb mouse can't used!https://bugs.dragonflybsd.org/issues/8462007-11-22T01:43:40Zfrankning
<p>I had use DFB 1.8.0,then my usb mouse can use.When I update to 1.10 and new <br />version, the usb mouse cant't use.Someone can help me? Thanks!</p>
<p>Following is my dmesg:</p>
<p>Copyright (c) 2003, 2004, 2005, 2006, 2007 The DragonFly Project.<br />Copyright (c) 1992-2003 The FreeBSD Project.<br />Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994<br /> The Regents of the University of California. All rights reserved.<br />DragonFly 1.11.0-DEVELOPMENT <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>: Tue Nov 13 00:12:24 CST 2007<br /> frank@:/usr/obj/usr/src/sys/NETONE<br />TSC clock: 1666701140 Hz, i8254 clock: 1193164 Hz<br />CPU: Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz (1666.74-MHz 686-class CPU)<br /> Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6</p>
<p>Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMO<br />V,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE><br /> Features2=0xe39d<SSE3,RSVD2,MON,DS_CPL,EST,TM2,SSSE3,CX16,XTPR,RSVD15><br /> Hyperthreading: 2 logical CPUs<br />real memory = 937951232 (915968K bytes)<br />avail memory = 899067904 (877996K bytes)<br />APIC_IO: MP table broken: ExtINT entry corrupt!<br />APIC_IO: MP table broken: IRQ 15 not ISA when IRQ 14 is!<br />Programming 24 pins in IOAPIC #0<br />DragonFly/MP: Multiprocessor motherboard<br /> cpu0 (BSP): apic id: 0, version: 0x00050014, at 0xfee00000<br /> cpu1 (AP): apic id: 1, version: 0x00050014, at 0xfee00000<br /> io0 (APIC): apic id: 2, version: 0x00178021, at 0xfec00000<br />APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0<br />SMP: AP CPU <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> Launched!<br />objcache(exec-args): too small for ncpus, adjusting cluster_limit 16->32<br />Preloaded elf kernel "/kernel" at 0xc078e000.<br />Preloaded elf module "/modules/acpi.ko" at 0xc078e2b0.<br />Pentium Pro MTRR support enabled<br />md0: Malloc disk<br />pcibios: BIOS version 2.10<br />Using $PIR table, 19 entries at 0xc00fde90<br />ACPI: RSDP <code> 0x0xf74f0/0x0014 (v 0 PTLTD )<br />ACPI: RSDT </code> 0x0x37e8ec8c/0x0034 (v 1 HPQOEM SLIC-MPC 0x06040000 LTP <br />0x00000000)<br />ACPI: FACP <code> 0x0x37e95ef2/0x0074 (v 1 ATI Bonefish 0x06040000 ATI <br />0x000F4240)<br />ACPI: DSDT </code> 0x0x37e8f69b/0x6857 (v 1 ATI SB450 0x06040000 MSFT <br />0x03000000)<br />ACPI: FACS <code> 0x0x37e96fc0/0x0040<br />ACPI: APIC </code> 0x0x37e95f66/0x005E (v 1 PTLTD APIC 0x06040000 LTP <br />0x00000000)<br />ACPI: MCFG <code> 0x0x37e95fc4/0x003C (v 1 PTLTD MCFG 0x06040000 LTP <br />0x00000000)<br />ACPI: SSDT </code> 0x0x37e8ecc0/0x0535 (v 1 PmRef CpuPm 0x00003000 INTL <br />0x20050228)<br />npx0: <math processor> on motherboard<br />npx0: INT 16 interface<br />Using XMM optimized bcopy/copyin/copyout<br />acpi0: <HPQOEM SLIC-MPC> on motherboard<br />acpi0: Power Button (fixed)<br />Warning: ACPI is disabling APM's device. You can't run both<br />acpi_ec0: <Embedded Controller: GPE 0x10> port 0x66,0x62 on acpi0<br />acpi_timer0: <32-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0<br />cpu0: <ACPI CPU> on acpi0<br />cpu1: <ACPI CPU> on acpi0<br />cpu1: Failed to attach throttling P_CNT<br />acpi_tz0: <Thermal Zone> on acpi0<br />acpi_acad0: <AC Adapter> on acpi0<br />acpi_cmbat0: <Control Method Battery> on acpi0<br />acpi_button0: <Power Button> on acpi0<br />acpi_lid0: <Control Method Lid Switch> on acpi0<br />acpi_button1: <Sleep Button> on acpi0<br />atkbdc0: <Keyboard controller (i8042)> port 0x64,0x60 irq 1 on acpi0<br />atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0<br />kbd0 at atkbd0<br />acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0%<br />Warning: ACPI idle hook not yet supported for SMP<br />psm0: <PS/2 Mouse> irq 12 on atkbdc0<br />psm0: model IntelliMouse, device ID 3<br />legacypci0 on motherboard<br />pcib0: <Host to PCI bridge> on legacypci0<br />pci0: <PCI bus> on pcib0<br />pcib1: <PCI to PCI bridge (vendor=1002 device=5a3f)> at device 1.0 on pci0<br />pci1: <PCI bus> on pcib1<br />pci1: <ATI model 5a62 graphics accelerator> at 5.0 irq 10<br />pcib2: <PCI to PCI bridge (vendor=1002 device=5a36)> at device 4.0 on pci0<br />pci2: <PCI bus> on pcib2<br />pci2: <unknown card> (vendor=0x14e4, dev=0x4312) at 0.0 irq 10<br />pcib3: <PCI to PCI bridge (vendor=1002 device=5a37)> at device 5.0 on pci0<br />pci5: <PCI bus> on pcib3<br />atapci0: <ATI IXP400 SATA150 controller> port 0x8400-0x840f,0x8410-<br />0x8413,0x8420-0x8427,0x8430-0x8433,0x8440-0x8447 irq 2 at device 18.0 on pci0<br />ata2: <ATA channel 0> on atapci0<br />ad4: 95396MB <FUJITSU MHV2100BH PL 00000029> at ata2-master SATA150<br />ata3: <ATA channel 1> on atapci0<br />ohci0: <ATI SB400 USB Controller> mem 0xc0504000-0xc0504fff irq 5 at device <br />19.0 on pci0<br />usb0: OHCI version 1.0, legacy support<br />usb0: <ATI SB400 USB Controller> on ohci0<br />usb0: USB revision 1.0<br />uhub0: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0<br />uhub0: 4 ports with 4 removable, self powered<br />ohci1: <ATI SB400 USB Controller> mem 0xc0505000-0xc0505fff irq 5 at device <br />19.1 on pci0<br />usb1: OHCI version 1.0, legacy support<br />usb1: <ATI SB400 USB Controller> on ohci1<br />usb1: USB revision 1.0<br />uhub1: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1<br />uhub1: 4 ports with 4 removable, self powered<br />pci0: <USB controller> at 19.2 irq 5<br />pci0: <unknown card> (vendor=0x1002, dev=0x4372) at 20.0<br />atapci1: <ATI IXP400 UDMA133 controller> port 0x8460-0x846f,0x376,0x170-<br />0x177,0x3f6,0x1f0-0x1f7 irq 9 at device 20.1 on pci0<br />ata0: <ATA channel 0> on atapci1<br />acd0: DVDR <TSSTcorpCD/DVDW TS-L632D/GAH1> at ata0-master UDMA33<br />ata1: <ATA channel 1> on atapci1<br />pci0: <unknown card> (vendor=0x1002, dev=0x437b) at 20.2 irq 9<br />isab0: <PCI to ISA bridge (vendor=1002 device=4377)> at device 20.3 on pci0<br />isa0: <ISA bus> on isab0<br />pcib4: <PCI to PCI bridge (vendor=1002 device=4371)> at device 20.4 on pci0<br />pci8: <PCI bus> on pcib4<br />fwohci0: vendor=1180, dev=832<br />fwohci0: <1394 Open Host Controller Interface> mem 0xc0200000-0xc02007ff irq 2 <br />at device 7.0 on pci8<br />fwohci0: OHCI version 1.0 (ROM=1)<br />fwohci0: No. of Isochronous channel is 4.<br />fwohci0: EUI64 00:60:b0:00:00:1e:fe:b6<br />fwohci0: Phy 1394a available S400, 1 ports.<br />fwohci0: Link S400, max_rec 2048 bytes.<br />firewire0: <<abbr title="FireWire">IEEE1394</abbr> bus> on fwohci0<br />fwe0: <Ethernet over FireWire> on firewire0<br />fwe0: MAC address: 02:60:b0:1e:fe:b6<br />sbp0: <SBP-2/SCSI over FireWire> on firewire0<br />fwohci0: Initiate bus reset<br />fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode<br />firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)<br />firewire0: bus manager 0 (me)<br />pci8: <unknown card> (vendor=0x1180, dev=0x0822) at 7.1 irq 10<br />pci8: <unknown card> (vendor=0x1180, dev=0x0843) at 7.2 irq 10<br />pci8: <unknown card> (vendor=0x1180, dev=0x0592) at 7.3 irq 10<br />rl0: <RealTek 8139 10/100BaseTX> port 0xa000-0xa0ff mem 0xc0201400-0xc02014ff <br />irq 11 at device 8.0 on pci8<br />miibus0: <MII bus> on rl0<br />rlphy0: <RealTek internal media interface> on miibus0<br />rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto<br />rl0: MAC address: 00:19:bb:00:95:5d<br />orm0: <Option ROMs> at iomem 0xc0000-0xcefff,0xcf000-0xcffff,0xdf000-0xdffff on <br />isa0<br />pmtimer0 on isa0<br />fdc0: ready for input in output<br />fdc0: cmd 3 failed at out byte 1 of 3<br />vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0<br />sc0: <System console> at flags 0x100 on isa0<br />sc0: VGA <16 virtual consoles, flags=0x300><br />sio0: can't drain, serial port might not exist, disabling<br />sio1: can't drain, serial port might not exist, disabling<br />ppc0: parallel port not found.<br />Mounting root from ufs:/dev/ad4s1a<br />cd0 at ata2 bus 0 target 0 lun 0<br />cd0: <TSSTcorp CD/DVDW TS-L632D GAH1> Removable CD-ROM SCSI-0 device <br />cd0: 33.000MB/s transfers<br />cd0: Attempt to query device size failed: NOT READY, Medium not present - tray <br />closed<br />cpu0: Performance states changed<br />cpu0: Cx states changed</p> DragonFlyBSD - Bug #806 (Feedback): boot error on MacBookhttps://bugs.dragonflybsd.org/issues/8062007-09-12T04:00:13Ztralamazza
<p>Hi,<br /> I'm trying to boot Dragonfly (1.10.1_REL) on a MacBook (1st gen). After the <br />booting process starts it enters a loop and displays "<db>" indefinitely.</p>
<p>On a side note Freebsd has a related project on google SoC: <br /><a class="external" href="http://wiki.freebsd.org/AppleMacbook">http://wiki.freebsd.org/AppleMacbook</a></p>
<p>thanks</p> DragonFlyBSD - Bug #570 (Feedback): 1.8.x: ACPI problemshttps://bugs.dragonflybsd.org/issues/5702007-03-03T11:46:01Zqhwt+dfly
<p>So if you enable ACPI and boot, it won't respond to keyboard no matter<br />whether you choose to boot into single- or multi-user mode?</p>
<p>So ... your keyboard does not work when you boot straight into the<br />single user mode, whether with or without ACPI driver enabled, right?<br />If not, I have no idea what this part really means:<br /> > But If I boot to non-ACPI-mode, everything works<br /> > just fine, but I can't get to sigle user mode, because prompt freezes<br /> > there too...</p>
<p>If the message buffer(which dmesg command shows you) survives across<br />reboot, I'd like to look at it after you boot with ACPI driver enabled<br />and booted with `boot -v' from the boot loader prompt (did I ask if<br />keyboard works when you go into the boot loader prompt?).</p>
<p>Cheers.</p> DragonFlyBSD - Bug #385 (Feedback): Mail archive address removalhttps://bugs.dragonflybsd.org/issues/3852006-11-22T22:22:03Zjustin
<p>Here's a question for everyone: I had originally the mail archive to<br />completely remove mail addresses, but it seems to mostly be annoying -<br />contacting someone from an archived email would be a dead end unless you<br />happened to already know the person's email address. Meanwhile, the<br />DragonFly lists are archived other places like MARC and Gmane, and<br />addresses are at best mildly obfusticated there.</p>
<p>Opinions? If anyone is significantly bothered by this, I'll keep the<br />addresses completely hidden.</p> DragonFlyBSD - Bug #293 (Feedback): Various updates to the handbookhttps://bugs.dragonflybsd.org/issues/2932006-08-11T04:26:06Zvictor
<p>Hi,</p>
<p>there are 3 patches attached:</p>
<p>book.diff - Updates the copyright info relating to FreeBSD at the header<br /> of the handbook.</p>
<p>dfbsd-updating - Update cvsup port path to the current pkgsrc version in<br /> the chapter "Updating DragonFly".</p>
<p>basics.diff - Update various paths relating to pkgsrc and hier(7). Also<br /> make it use the new entity for pkgsrc <br /> tree/collection/framework.</p> DragonFlyBSD - Bug #285 (Feedback): interrupt latency with re without ip address configuredhttps://bugs.dragonflybsd.org/issues/2852006-08-07T06:00:07Zthomas.nikolajsen
<p>Playing sound using pcm(4)/snd(4) gives bad quality: hiss and hops, like sound isn't playing for very short time periods.</p>
<p>This is experienced:<br /> - not having SMP in kernel config (eg GENERIC)<br /> - from dfly-1.5 26th December '05 (24th is ok using kernels from chlamydia);<br />including HEAD.</p>
<p>dfly-1.4 is ok, including 1.4.4.</p>
<p>Using audio/mpg123 for MP3, 'cp test.raw /dev/dspW' or pcmplay for decoded sound.<br />Buffering audio data with mpg123 -b doesn't sound like making any difference.</p>
<p>CPU load doesn't sound like making any difference.<br />Problem experienced on several systems, using snd_via8233 and snd_ich.</p>
<p>No X11 used.</p>
<pre><code>-thomas</code></pre> DragonFlyBSD - Bug #243 (Feedback): weird behavior in the shellhttps://bugs.dragonflybsd.org/issues/2432006-07-15T14:49:02Zswildner
<p>Hi,</p>
<p>I'm not sure if this is a 'real' bug but I'm curious if anyone knows the <br />cause. Check this:</p>
<p>zoot# echo $PATH<br />/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/pkg/bin:/usr/pkg/sbin:/usr/pkg/xorg/bin:/home/s/bin<br />zoot# pwd<br />/usr/src/sys/dev/disk/md<br />zoot# .<br />/usr/sbin/.: Permission denied.<br />zoot# cd /<br />zoot# .<br />/usr/sbin/.: Permission denied.</p>
<p>In other words: The strange thing is that whereever I type . on the csh <br />prompt, I get the /usr/sbin/.: message regardless of what my current <br />directory is.</p>
<p>On a Solaris system I get ".: Permission denied." which is what I'd <br />expect rather.</p>
<p>So, can anyone enlighten me why DragonFly behaves like that?</p>
<p>Sascha</p>