DragonFlyBSD bugtracker: Issueshttps://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082022-08-08T19:15:54ZDragonFlyBSD bugtracker
Redmine DragonFlyBSD - Bug #3323 (New): virtio (if_vtnet...) not detected on Hetzner cloud (AMD system)https://bugs.dragonflybsd.org/issues/33232022-08-08T19:15:54Zmneumann
<p>`pciconf -lv` lists a "Virtio network device"</p>
<p><img src="https://bugs.dragonflybsd.org/attachments/download/1724/clipboard-202208082105-nspru.png" alt="" loading="lazy" /></p>
<p>But it does not show up under `ifconfig`. Also the virtio SCSI harddisk is not detected.</p>
<p>Just curious if I am doing anything wrong.</p> DragonFlyBSD - Bug #3282 (New): unexpected errno value from fopen()https://bugs.dragonflybsd.org/issues/32822021-06-14T15:40:25Zbhaiblebruno@clisp.org
<p>fopen(".", "w") fails with errno = EEXIST.<br />Per POSIX <a class="external" href="https://pubs.opengroup.org/onlinepubs/9699919799/functions/fopen.html">https://pubs.opengroup.org/onlinepubs/9699919799/functions/fopen.html</a><br />one would expect one of EISDIR, EINVAL, EACCES.</p>
<p>How to reproduce: Run this program.</p>
<pre>
#include <errno.h>
#include <stdio.h>
int main ()
{
FILE *fp = fopen (".", "w");
if (fp == NULL)
{
perror ("fopen");
}
}
</pre> DragonFlyBSD - Bug #3239 (New): unable to SIGKILL glitched emacshttps://bugs.dragonflybsd.org/issues/32392020-05-26T10:30:35Zpiecuch
<p>You can make emacs unresponsive and the kernel will not be able to kill it, even with SIGKILL.</p>
<p>How to reproduce:<br />1) install emacs<br />2) echo 'exec top' > /tmp/test.sh; chmod +x /tmp/test.sh<br />3) Run emacs, run eshell (Alt + x, then type eshell, hit enter)<br />4) run /tmp/test.sh in eshell</p>
<p>This will make emacs unresponsive and the kernel will not be able to kill it.</p> DragonFlyBSD - Bug #3231 (New): wifi drops on 5.8https://bugs.dragonflybsd.org/issues/32312020-04-06T12:08:09Ztse
<p>Since upgrading to 5.8, my wifi occasionally drops out, and `doas service netif restart` does not bring it back. A reboot does though</p>
<p>I've tried it with each of:<br />#wpa_supplicant_program="/usr/sbin/wpa_supplicant" <br />#wpa_supplicant_program="/raven/sbin/wpa_supplicant" <br />wpa_supplicant_program="/usr/local/sbin/wpa_supplicant"</p>
<p>`doas service netif restart`:</p>
<p>```<br />iwm0: could not initiate scan<br />iwm0: could not initiate scan<br />iwm0: could not initiate scan<br />iwm0: could not initiate scan<br />iwm0: could not initiate scan<br />iwm0: iwm_start_fw: Unable to init nic<br />iwm0: iwm_start_fw: failed 16<br />iwm0: Failed to start INIT ucode: 16<br />iwm_run_init_ucode: failed 16<br />iwm_init_hw failed 16<br />iwm0: could not initiate scan<br />iwm0: could not initiate scan<br />iwm0: could not initiate scan<br />iwm0: iwm_start_fw: Unable to init nic<br />iwm0: iwm_start_fw: failed 16<br />iwm0: Failed to start INIT ucode: 16<br />iwm_run_init_ucode: failed 16<br />iwm_init_hw failed 16<br />iwm0: could not initiate scan<br />iwm0: could not initiate scan<br />iwm0: could not initiate scan<br />iwm0: could not initiate scan<br />iwm0: could not initiate scan<br />```</p>
<p>```<br />Mar 30 15:03:23 beloved kernel: iwm0: <Intel(R) Dual Band Wireless AC 7260> mem 0xf7900000-0xf7901fff at device 0.0 on pci4</p>
<p>Mar 30 15:03:23 beloved kernel: iwm0: hw rev 0x140, fw ver 17.352738.0, address ac:fd:ce:84:65:b6<br />```</p>
<p>Something like this also doesn't work, and produces the below output</p>
<p>```<br />doas service netif stop<br />doas kldunload if_iwm<br />doas kldunload iwm7260<br />doas kldunload iwm7260fw<br />doas kldload if_iwm<br />doas kldload iwm7260fw<br />doas service netif start<br />```</p>
<p>```<br />beloved kernel: iwm0: device timeout<br />beloved kernel: iwm0: iwm_pcie_set_cmd_in_flight: Failed to wake NIC for hcmd<br />beloved kernel: iwm0: iwm_pcie_set_cmd_in_flight: Failed to wake NIC for hcmd<br />beloved kernel: iwm0: iwm_bring_down_firmware: Failed to remove station: 5<br />beloved kernel: iwm0: iwm_pcie_set_cmd_in_flight: Failed to wake NIC for hcmd<br />beloved kernel: iwm0: iwm_mac_ctxt_send_cmd: Failed to send MAC context (action:2): 5<br />beloved kernel: iwm0: iwm_bring_down_firmware: Failed to change mac context: 5<br />beloved kernel: iwm0: iwm_pcie_set_cmd_in_flight: Failed to wake NIC for hcmd<br />beloved kernel: iwm0: iwm_bring_down_firmware: Failed to update smart FIFO: 5<br />beloved kernel: iwm0: iwm_pcie_set_cmd_in_flight: Failed to wake NIC for hcmd<br />beloved kernel: iwm0: Failed to remove station. Id=0<br />beloved kernel: iwm0: iwm_bring_down_firmware: Failed to remove station id: 5<br />beloved kernel: iwm0: iwm_pcie_set_cmd_in_flight: Failed to wake NIC for hcmd<br />beloved kernel: iwm0: iwm_update_quotas: Failed to send quota: 5<br />beloved kernel: iwm0: iwm_bring_down_firmware: Failed to update PHY quota: 5<br />beloved kernel: iwm0: iwm_pcie_set_cmd_in_flight: Failed to wake NIC for hcmd<br />beloved kernel: iwm0: iwm_mac_ctxt_send_cmd: Failed to send MAC context (action:2): 5<br />beloved kernel: iwm0: iwm_bring_down_firmware: Failed to change mac context: 5<br />beloved kernel: iwm0: iwm_pcie_set_cmd_in_flight: Failed to wake NIC for hcmd<br />beloved kernel: iwm0: Failed to send binding (action:3): 5<br />beloved kernel: iwm0: iwm_bring_down_firmware: Failed to remove channel ctx: 5<br />beloved kernel: iwm0: iwm_pcie_set_cmd_in_flight: Failed to wake NIC for hcmd<br />beloved kernel: iwm0: iwm_mac_ctxt_send_cmd: Failed to send MAC context (action:2): 5<br />beloved kernel: iwm0: iwm_bring_down_firmware: Failed to change mac context: 5<br />beloved kernel: iwm0: iwm_pcie_set_cmd_in_flight: Failed to wake NIC for hcmd<br />beloved kernel: iwm0: iwm_bring_down_firmware: failed to update power management<br />beloved kernel: iwm0: iwm_start_fw: Unable to init nic<br />beloved kernel: iwm0: iwm_start_fw: failed 16<br />beloved kernel: iwm0: Failed to start INIT ucode: 16<br />beloved kernel: iwm_run_init_ucode: failed 16<br />beloved kernel: iwm_init_hw failed 16<br />beloved kernel: iwm0: could not initiate scan<br />beloved last message repeated 7 times<br />beloved last message repeated 24 times<br />beloved last message repeated 12 times<br />beloved kernel: pf_test6: kif NULL, if_xname wlan0<br />beloved kernel: pf_test: kif NULL, if_xname wlan0<br />beloved kernel: iwm0: detached<br />beloved kernel: iwm0: <Intel(R) Dual Band Wireless AC 7260> mem 0xf7900000-0xf7901fff at device 0.0 on pci4<br />beloved kernel: iwm0: iwm_start_fw: Unable to init nic<br />beloved kernel: iwm0: iwm_start_fw: failed 16<br />beloved kernel: iwm0: Failed to start INIT ucode: 16<br />beloved kernel: iwm0: detached<br />beloved kernel: iwm0: <Intel(R) Dual Band Wireless AC 7260> mem 0xf7900000-0xf7901fff at device 0.0 on pci4<br />beloved kernel: iwm0: iwm_start_fw: Unable to init nic<br />beloved kernel: iwm0: iwm_start_fw: failed 16<br />beloved kernel: iwm0: Failed to start INIT ucode: 16<br />```</p> DragonFlyBSD - Bug #3184 (New): tsleep(9) return value when PCATCH specifiedhttps://bugs.dragonflybsd.org/issues/31842019-04-03T13:49:49Ztkusumikusumi.tomohiro@gmail.com
<p>tsleep(9) with PCATCH causes the function to check for signals before and after sleeping, as mentioned in man page.<br /><a class="external" href="https://www.dragonflybsd.org/cgi/web-man?command=tsleep&section=9">https://www.dragonflybsd.org/cgi/web-man?command=tsleep&section=9</a></p>
<p>But PCATCH also lets signal wake up the process, and when this happens tsleep(9) returns 0 instead of EINTR.<br /><a class="external" href="https://github.com/DragonFlyBSD/DragonFlyBSD/blob/master/sys/kern/kern_synch.c#L628">https://github.com/DragonFlyBSD/DragonFlyBSD/blob/master/sys/kern/kern_synch.c#L628</a></p>
<p>Is above returning 0 expected behavior ?</p>
<p>From process perspective, there is no clear distinction between above and regular wakeup, hence unable to tell one from another.<br />It's clearer if it also returns EINTR or something non zero.</p> DragonFlyBSD - Bug #3132 (New): unifdef minedhttps://bugs.dragonflybsd.org/issues/31322018-04-27T03:34:07Zbcallah
<p>Hi --</p>
<p>The included diff unifdefs the code in bin/mined. The #ifdef'd out paths probably would not even compile with the current #includes anyway.<br />No binary change. I have been running this on OpenBSD/amd64 and OpenBSD/armv7 for a while now. The DragonFly build is also happy with this.</p> DragonFlyBSD - Bug #2840 (New): wrong voltage is reportedhttps://bugs.dragonflybsd.org/issues/28402015-09-12T01:09:37Zyellowrabbit2010
<p>lm0: <Winbond W83627DHG Hardware Monitor> at port 0x290-0x297 on isa0<br />hw.sensors.lm0.volt0: 0.76 VDC (VCore)<br />hw.sensors.lm0.volt1: 6.55 VDC (+12V)<br />hw.sensors.lm0.volt2: 3.31 VDC (+3.3V)<br />hw.sensors.lm0.volt3: 3.31 VDC (+3.3V)<br />hw.sensors.lm0.volt4: -22.93 VDC (-12V)<br /> ^<sup>^^</sup>^^^^^^^</p> DragonFlyBSD - Bug #2708 (New): unable to send TCP nor UDP on age(4) interfacehttps://bugs.dragonflybsd.org/issues/27082014-08-09T19:23:03Zdermistedermiste@kilob.yt
<p>On a fresh install, when using an age(4) interface, I can acquire a DHCP lease, ping my gateway and 8.8.8.8, but impossible to send TCP nor UDP.</p>
<p>How to reproduce:<br />1) dhclient age0<br />2) ping -c 8 8.8.8.8 # works<br />3) dig <a class="external" href="http://www.dragonflybsd.org">www.dragonflybsd.org</a><br /> => tcpdump on router shows packet going out, but nothing going back in<br />4) ssh 192.168.72.1<br /> => on router, running 'tcpdump -s 1500 -ni eth0 host 192.168.72.205' shows<br /> 19:21:48.844767 IP truncated-ip - 36905 bytes missing! 192.168.72.205.1026 > 192.168.72.1.22: Flags [S], seq 1807181392:1807218297, win 57344, options [mss 1460,nop,wscale 5,nop,nop,sackOK,nop,nop,TS val 189796 ecr 0], length 36905</p>
<ol>
<li>uname -a<br />DragonFly 3.8-RELEASE DragonFly v3.8.1-RELEASE <a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: install: net/bridge/*.h: No such file or directory (Closed)" href="https://bugs.dragonflybsd.org/issues/16">#16</a>: Mon Jun 16 21:36:15 PDT 2014 <a class="email" href="mailto:justin@pkgbox64.dragonflybsd.org">justin@pkgbox64.dragonflybsd.org</a>:/usr/obj/build/home/justin/src/sys/X86_64_GENERIC x86_64</li>
</ol>
<ol>
<li>pciconf -a<br />hostb0@pci0:0:0:0: class=0x060000 card=0x81781043 chip=0x27708086 rev=0x81 hdr=0x00<br />pcib1@pci0:0:1:0: class=0x060400 card=0x27718086 chip=0x27718086 rev=0x81 hdr=0x01<br />pcib2@pci0:0:28:0: class=0x060400 card=0x81791043 chip=0x27d08086 rev=0x01 hdr=0x01<br />pcib3@pci0:0:28:2: class=0x060400 card=0x81791043 chip=0x27d48086 rev=0x01 hdr=0x01<br />uhci0@pci0:0:29:0: class=0x0c0300 card=0x81791043 chip=0x27c88086 rev=0x01 hdr=0x00<br />uhci1@pci0:0:29:1: class=0x0c0300 card=0x81791043 chip=0x27c98086 rev=0x01 hdr=0x00<br />uhci2@pci0:0:29:2: class=0x0c0300 card=0x81791043 chip=0x27ca8086 rev=0x01 hdr=0x00<br />uhci3@pci0:0:29:3: class=0x0c0300 card=0x81791043 chip=0x27cb8086 rev=0x01 hdr=0x00<br />ehci0@pci0:0:29:7: class=0x0c0320 card=0x81791043 chip=0x27cc8086 rev=0x01 hdr=0x00<br />pcib4@pci0:0:30:0: class=0x060401 card=0x81791043 chip=0x244e8086 rev=0xe1 hdr=0x01<br />isab0@pci0:0:31:0: class=0x060100 card=0x81791043 chip=0x27b88086 rev=0x01 hdr=0x00<br />atapci1@pci0:0:31:1: class=0x01018a card=0x81791043 chip=0x27df8086 rev=0x01 hdr=0x00<br />atapci2@pci0:0:31:2: class=0x01018f card=0x26011043 chip=0x27c08086 rev=0x01 hdr=0x00<br />none0@pci0:0:31:3: class=0x0c0500 card=0x81791043 chip=0x27da8086 rev=0x01 hdr=0x00<br />vgapci0@pci0:4:0:0: class=0x030000 card=0x2500174b chip=0x5b601002 rev=0x00 hdr=0x00<br />vgapci1@pci0:4:0:1: class=0x038000 card=0x2501174b chip=0x5b701002 rev=0x00 hdr=0x00<br />age0@pci0:2:0:0: class=0x020000 card=0x82261043 chip=0x10481969 rev=0xb0 hdr=0x00<br />atapci0@pci0:1:9:0: class=0x018000 card=0x31141095 chip=0x31141095 rev=0x02 hdr=0x00<br />re0@pci0:1:11:0: class=0x020000 card=0x43001186 chip=0x43001186 rev=0x10 hdr=0x00</li>
</ol>
<ol>
<li>dmesg<br />Copyright (c) 2003-2014 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 v3.8.1-RELEASE <a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: install: net/bridge/*.h: No such file or directory (Closed)" href="https://bugs.dragonflybsd.org/issues/16">#16</a>: Mon Jun 16 21:36:15 PDT 2014<br /> <a class="email" href="mailto:justin@pkgbox64.dragonflybsd.org">justin@pkgbox64.dragonflybsd.org</a>:/usr/obj/build/home/justin/src/sys/X86_64_GENERIC<br />TSC clock: 2400065469 Hz, i8254 clock: 1193215 Hz<br />CPU: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz (2400.01-MHz K8-class CPU)<br /> Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6<br /> Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE><br /> Features2=0xe3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM><br /> AMD Features=0x20000800<SYSCALL,LM><br /> AMD Features2=0x1<LAHF><br /> Thermal and PM Features=0x1<SENSOR><br /> MONITOR/MWAIT Features=0x3<CST,INTBRK><br />real memory = 1072954368 (1023 MB)<br />avail memory = 984633344 (939 MB)<br />lapic: divisor index 0, frequency 133333593 Hz<br />Initialize MI interrupts<br />VMM: PROCBASED_ACTIVATE_SECONDARY_CONTROLS not supported by this CPU<br />FQ scheduler policy version 1.1 loaded<br />wdog: In-kernel automatic watchdog reset enabled<br />kbd1 at kbdmux0<br />disk scheduler: set policy of md0 to noop<br />md0: Malloc disk<br />ACPI: RSDP 0x00000000000FB110 000014 (v00 ACPIAM)<br />ACPI: RSDT 0x000000003FFA0000 000040 (v01 A_M_I_ OEMRSDT 06000708 MSFT 00000097)<br />ACPI: FACP 0x000000003FFA0200 000081 (v01 A_M_I_ OEMFACP 06000708 MSFT 00000097)<br />ACPI: DSDT 0x000000003FFA0590 0059A4 (v01 A0603 A0603000 00000000 INTL 20060113)<br />ACPI: FACS 0x000000003FFAE000 000040<br />ACPI: APIC 0x000000003FFA0390 000080 (v01 A_M_I_ OEMAPIC 06000708 MSFT 00000097)<br />ACPI: OEMB 0x000000003FFAE040 00006B (v01 A_M_I_ AMI_OEM 06000708 MSFT 00000097)<br />ACPI: HPET 0x000000003FFA5F40 000038 (v01 A_M_I_ OEMHPET 06000708 MSFT 00000097)<br />ACPI: MCFG 0x000000003FFA5F80 00003C (v01 A_M_I_ OEMMCFG 06000708 MSFT 00000097)<br />ACPI: SSDT 0x000000003FFAE0B0 0001C6 (v01 AMI CPU1PM 00000001 INTL 20060113)<br />ACPI: SSDT 0x000000003FFAE280 00013A (v01 AMI CPU2PM 00000001 INTL 20060113)<br />cryptosoft0: <software crypto> on motherboard<br />aesni0: No AESNI support.<br />padlock0: No ACE support.<br />rdrand0: No RdRand support.<br />acpi0: <A_M_I_ OEMRSDT> on motherboard<br />ACPI: All ACPI Tables successfully acquired<br />ACPI FADT: SCI testing interrupt mode ...<br />ACPI FADT: SCI select level/high<br />ACPI: Executed 1 blocks of module-level executable AML code<br />objcache_reclaimlist<br />objcache_reclaimlist<br />objcache_reclaimlist<br />objcache_reclaimlist<br />acpi0: Power Button (fixed)<br />Warning: ACPI is disabling APM's device. You can't run both<br />acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0<br />acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0<br />acpi_hpet0: frequency 14318180<br />pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0<br />pci0: <ACPI PCI bus> on pcib0<br />pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0<br />pci4: <ACPI PCI bus> on pcib1<br />vgapci0: <VGA-compatible display> port 0xe000-0xe0ff mem 0xe7fe0000-0xe7feffff,0xe8000000-0xefffffff irq 16 at device 0.0 on pci4<br />vgapci1: <VGA-compatible display> mem 0xe7ff0000-0xe7ffffff at device 0.1 on pci4<br />pcib2: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0<br />pci3: <ACPI PCI bus> on pcib2<br />pcib3: <ACPI PCI-PCI bridge> irq 18 at device 28.2 on pci0<br />pci2: <ACPI PCI bus> on pcib3<br />age0: <Attansic Technology Corp, L1 Gigabit Ethernet> mem 0xe7ec0000-0xe7efffff irq 18 at device 0.0 on pci2<br />age0: 1280 Tx FIFO, 2364 Rx FIFO<br />miibus0: <MII bus> on age0<br />atphy0: <Atheros F1 10/100/1000 PHY> on miibus0<br />atphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, auto<br />age0: MAC address: 00:1b:fc:72:c2:37<br />uhci0: <Intel 82801G (ICH7) USB controller USB-A> port 0x7000-0x701f irq 20 at device 29.0 on pci0<br />usbus0: <Intel 82801G (ICH7) USB controller USB-A> on uhci0<br />uhci1: <Intel 82801G (ICH7) USB controller USB-B> port 0x7400-0x741f irq 17 at device 29.1 on pci0<br />usbus0: 12Mbps Full Speed USB v1.0<br />ugen0.1: <Intel> at usbus0<br />uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0<br />usbus1: <Intel 82801G (ICH7) USB controller USB-B> on uhci1<br />uhci2: <Intel 82801G (ICH7) USB controller USB-C> port 0x7800-0x781f irq 18 at device 29.2 on pci0<br />usbus1: 12Mbps Full Speed USB v1.0<br />ugen1.1: <Intel> at usbus1<br />uhub1: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1<br />usbus2: <Intel 82801G (ICH7) USB controller USB-C> on uhci2<br />uhci3: <Intel 82801G (ICH7) USB controller USB-D> port 0x8000-0x801f irq 19 at device 29.3 on pci0<br />usbus2: 12Mbps Full Speed USB v1.0<br />ugen2.1: <Intel> at usbus2<br />uhub2: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus2<br />usbus3: <Intel 82801G (ICH7) USB controller USB-D> on uhci3<br />ehci0: <Intel 82801GB/R (ICH7) USB 2.0 controller> mem 0xe7cffc00-0xe7cfffff irq 20 at device 29.7 on pci0<br />usbus4: EHCI version 1.0<br />usbus3: 12Mbps Full Speed USB v1.0<br />ugen3.1: <Intel> at usbus3<br />uhub3: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus3<br />usbus4: <Intel 82801GB/R (ICH7) USB 2.0 controller> on ehci0<br />pcib4: <ACPI PCI-PCI bridge> at device 30.0 on pci0<br />pci1: <ACPI PCI bus> on pcib4<br />atapci0: <SiI 3114 SATA150 controller> port 0xa000-0xa00f,0xa400-0xa403,0xa800-0xa807,0xb000-0xb003,0xb400-0xb407 mem 0xe7dff800-0xe7dffbff irq 17 at device 9.0 on pci1<br />usbus4: 480Mbps High Speed USB v2.0<br />ata2: <ATA channel 0> on atapci0<br />ata3: <ATA channel 1> on atapci0<br />ata4: <ATA channel 2> on atapci0<br />ata5: <ATA channel 3> on atapci0<br />re0: <D-Link DGE-528(T) Gigabit Ethernet Adapter> port 0xb800-0xb8ff mem 0xe7dffc00-0xe7dffcff irq 22 at device 11.0 on pci1<br />re0: Hardware rev. 0x10000000; PCI32 33MHz<br />miibus1: <MII bus> on re0<br />rgephy0: <8211B/RTL8169S/8110S media interface> on miibus1<br />rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto<br />uhub0: 2 ports with 2 removable, self powered<br />ugen4.1: <Intel> at usbus4<br />uhub4: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus4<br />re0: MAC address: 00:19:5b:5d:26:28<br />isab0: <PCI-ISA bridge> at device 31.0 on pci0<br />isa0: <ISA bus> on isab0<br />atapci1: <Intel ICH7 UDMA100 controller> port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0<br />ata0: <ATA channel 0> on atapci1<br />ata1: <ATA channel 1> on atapci1<br />uhub1: 2 ports with 2 removable, self powered<br />atapci2: <Intel ICH7 SATA300 controller> port 0x8400-0x840f,0x8800-0x8803,0x9000-0x9007,0x9400-0x9403,0x9800-0x9807 irq 23 at device 31.2 on pci0<br />ata6: <ATA channel 0> on atapci2<br />uhub2: 2 ports with 2 removable, self powered<br />uhub3: 2 ports with 2 removable, self powered<br />disk scheduler: set policy of ad12 to noop<br />ad12: 76323MB <WDC WD800JD-08MSA1 10.01E01> at ata6-master SATA150<br />ata7: <ATA channel 1> on atapci2<br />pci0: <serial bus, SMBus> (vendor 0x8086, dev 0x27da) at device 31.3 irq 23<br />acpi_button0: <Power Button> on acpi0<br />ppc0: <ECP parallel printer port> port 0x778-0x77f,0x378-0x37f irq 7 drq 3 on acpi0<br />ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode<br />ppc0: FIFO with 16/16/9 bytes threshold<br />ppbus0: <Parallel port bus> on ppc0<br />plip0: <PLIP network interface> on ppbus0<br />lpt0: <Printer> on ppbus0<br />lpt0: Interrupt-driven port<br />ppi0: <Parallel I/O> on ppbus0<br />atkbdc0: <Keyboard controller (i8042)> port 0x64,0x60 irq 1 on acpi0<br />atkbd0: <AT Keyboard> irq 1 on atkbdc0<br />kbd0 at atkbd0<br />sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 on acpi0<br />sio0: type 16550A<br />cpu0: <ACPI CPU> on acpi0<br />ACPI: Dynamic OEM Table Load:<br />ACPI Error: Method parse/execution failed [\\_PR_.CPU1._OSC] (Node 0xffffffe003347230), AE_ALREADY_EXISTS (20140424/psparse-553)<br />cpu_cst0: <ACPI CPU C-State> on cpu0<br />cpu_pst0: <ACPI CPU P-State> on cpu0<br />clockmod0: <CPU clock modulation> on cpu0<br />coretemp0: <CPU On-Die Thermal Sensors> on cpu0<br />cpu1: <ACPI CPU> on acpi0<br />ACPI: Dynamic OEM Table Load:<br />ACPI Error: Method parse/execution failed [\\_PR_.CPU2._OSC] (Node 0xffffffe0033474b8), AE_ALREADY_EXISTS (20140424/psparse-553)<br />cpu_cst1: <ACPI CPU C-State> on cpu1<br />cpu_pst1: <ACPI CPU P-State> on cpu1<br />clockmod1: <CPU clock modulation> on cpu1<br />coretemp1: <CPU On-Die Thermal Sensors> on cpu1<br />orm0: <Option ROMs> at iomem 0xc0000-0xccfff,0xcd000-0xcdfff on isa0<br />pmtimer0 on isa0<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 />lm0: <Winbond W83627DHG Hardware Monitor> at port 0x290-0x297 on isa0<br />wbsio0: <Winbond LPC Super I/O W83627DHG rev 0x23> at port 0x2e-0x2f on isa0<br />wbsio0: hardware monitor iobase is 0x290<br />wbsio0: lm0 is already attached at 0x290<br />sio2: can't drain, serial port might not exist, disabling<br />ppc1: cannot reserve I/O port range<br />hpt27xx: no controller detected.<br />CAM: Configuring 8 busses<br />CAM: finished configuring all busses<br />uhub4: 8 ports with 8 removable, self powered<br />no B_DEVMAGIC (bootdev=0)<br />Device Mapper version 4.16.0 loaded<br />dm_target_error: Successfully initialized<br />dm_target_zero: Successfully initialized<br />Mounting root from ufs:da8s1a<br />no disk named 'da8s1a'<br />setrootbyname failed<br />ffs_mountroot: can't find rootvp<br />Root mount failed: 6</li>
</ol>
<p>Manual root filesystem specification:<br /> <fstype>:<device> Specify root (e.g. ufs:da0s1a)<br /> ? List valid disk boot devices<br /> panic Just panic<br /> abort Abort manual input</p>
<p>mountroot> ufs:ad12s2a<br />Mounting root from ufs:ad12s2a<br />DMA space used: 588k, remaining available: 16384k<br />Mounting devfs</p> DragonFlyBSD - Bug #2577 (New): virtio-blk iops performance is cpu limited on high end deviceshttps://bugs.dragonflybsd.org/issues/25772013-08-01T20:59:44Zgjs278gjs278@yahoo.com
<p>Qemu 1.5.2 on Gentoo AMD64 kernel 3.10.4 host with an i7 980x processor at 4.2ghz</p>
<p>qemu-system-x86_64 -machine accel=kvm -cpu host -drive file=/dev/fioa3,if=virtio,cache=none,aio=native -balloon virtio -smp 6 -m 6144M</p>
<p>/dev/fioa3 is a 160gb slc fusion-io card</p>
<p>DragonFlyBSD 3.4.2-RELEASE is the guest OS</p>
<ol>
<li>/tmp/rr1 /dev/vbd0<br />Device /dev/vbd0 bufsize 512 limit 10.800GB nprocs 32<br />randrand 1.001s 24293 loops = 41.202uS/loop<br />randrand 1.002s 24384 loops = 41.072uS/loop<br />randrand 1.001s 24633 loops = 40.640uS/loop</li>
</ol>
<ol>
<li>/tmp/rr1 /dev/vbd0 4096<br />Device /dev/vbd0 bufsize 4096 limit 10.800GB nprocs 32<br />randrand 1.001s 24333 loops = 41.119uS/loop<br />randrand 1.002s 24389 loops = 41.052uS/loop<br />randrand 1.001s 24367 loops = 41.093uS/loop</li>
</ol>
<ol>
<li>/tmp/rr1 /dev/vbd0 16384<br />Device /dev/vbd0 bufsize 16384 limit 10.800GB nprocs 32<br />randrand 1.001s 21006 loops = 41.619uS/loop<br />randrand 1.002s 21167 loops = 41.348uS/loop<br />randrand 1.001s 20520 loops = 48.850uS/loop</li>
</ol>
<p>cpu usage on the host nears 100% while /tmp/rr1 is running. at nprocs 32, the device should be capable of at least 100k iops. the same 25k limit is seen using an ssd array as well.</p> DragonFlyBSD - Bug #2493 (New): vidcontrol: invalid video mode namehttps://bugs.dragonflybsd.org/issues/24932013-01-20T07:06:58ZSvarovsvarov@yahoo.com
<p>Hello.</p>
<p>I tried to change foreground/background color of the virt. console (ttyv1) with command `vidcontrol lightwhite black` but haven't got any success. The program reports "vidcontrol: invalid video mode name". The syntax seems to be correct because on FreeBSD (latest) it works fine.</p>
<p>Do I miss something or it's a bug?</p>
<p>Regards, Dmitry.
==================================<br />PC: Netbook Eee PC 900AX<br />OS: DragonFlyBSD 3.2.1<br />----------------------------------<br />I am sorry for my english, it's still very poor.<br />Hope that my message is understandable.</p> DragonFlyBSD - Bug #2412 (New): wlan0 fails to get address via dhclienthttps://bugs.dragonflybsd.org/issues/24122012-08-27T08:09:25Znonsolosoft
<p>I'm not able to connect via Atheros 2413 to TP-Link wifi router.<br />In attachment there is the shell session log.</p> DragonFlyBSD - Bug #2224 (New): v2.13.0.291.gaa7ec - Panic on fq while installing worldhttps://bugs.dragonflybsd.org/issues/22242011-11-18T00:57:18Ztuxillo
<p>Hi,</p>
<p>While installing world into an image file (vnconfig) I got this panic:</p>
<p>Unread portion of the kernel message buffer:<br />Xdblfault() at Xdblfault+0x93<br />fq_dispatch() at fq_dispatch+0x76<br />fq_queue() at fq_queue+0x271<br />dsched_queue() at dsched_queue+0x1cc<br />diskstrategy() at diskstrategy+0x6c<br />dev_dstrategy_chain() at dev_dstrategy_chain+0xc8<br />devfs_spec_strategy() at devfs_spec_strategy+0x14d<br />vop_strategy() at vop_strategy+0x8c<br />vn_strategy() at vn_strategy+0xe3<br />hammer_io_direct_read() at hammer_io_direct_read+0x1aa<br />hammer_vop_strategy_read() at hammer_vop_strategy_read+0x4cb<br />hammer_vop_strategy() at hammer_vop_strategy+0x45<br />vop_strategy() at vop_strategy+0x8c<br />vn_strategy() at vn_strategy+0xe3<br />breadnx() at breadnx+0x9c<br />hammer_vop_write() at hammer_vop_write+0x4f2<br />vop_write() at vop_write+0x88<br />vnstrategy() at vnstrategy+0x1fd<br />dev_dstrategy() at dev_dstrategy+0x12f<br />dsched_strategy_async() at dsched_strategy_async+0x5d<br />fq_dispatch() at fq_dispatch+0x76<br />fq_dispatcher() at fq_dispatcher+0x3ad<br />boot() called on cpu#3<br />Uptime: 22h2m30s<br />Physical memory: 6019 MB<br />Dumping 2114 MB: 2099 2083 2067 2051 2035 2019 2003 1987 1971 1955 1939 1923 1907 1891 1875 1859 1843 1827 1811 1795 1779 1763 1747 1731 1715 1699 1683 1667 1651 1635 1619 1603 1587 1571 1555 1539 1523 1507 1491 1475 1459 1443 1427 1411 1395 1379 1363 1347 1331 1315 1299 1283 1267 1251 1235 1219 1203 1187 1171 1155 1139 1123 1107 1091 1075 1059 1043 1027 1011 995 979 963 947 931 915 899 883 867 851 835 819 803 787 771 755 739 723 707 691 675 659 643 627 611 595 579 563 547 531 515 499 483 467 451 435 419 403 387 371 355 339 323 307 291 275 259 243 227 211 195 179 163 147 131 115 99 83 67 51 35 19 3</p>
<p>I got the coredump available on demand.</p>
<p>Cheers,<br />Antonio Huete</p> DragonFlyBSD - Bug #2154 (New): vkernel copyout() doesn't return EFAULT on errorhttps://bugs.dragonflybsd.org/issues/21542011-10-20T10:53:37Zvsrinivasvsrinivas@ops101.org
<p>copyout() is documented as returning 0 or EFAULT; the vkernel version doesn't do<br />so, it returns a VM error code, which needs translating.</p> DragonFlyBSD - Bug #1941 (New): wlan config crashhttps://bugs.dragonflybsd.org/issues/19412010-12-25T03:54:21Zabandon.every.hope
<p>Hello-<br />Found a potential bug configuring wlan using rc.conf. The following was<br />added to rc.conf on a fresh desktop install:</p>
<p>wlans_ral0="wlan0" <br />ifconfig_wlan0="WPA DHCP"</p>
<p>The associated wpa_supplicant.conf from /etc:</p>
<p>network={<br /> ssid="stuff" <br /> psk="secretstuff" <br />}</p>
<p>With these edits in the listed files the machine poops its pants on boot<br />(during network config, of course) and gives a:</p>
<p>"ad8: WARNING - SETFEATURES SET TRANSFER MODE ..."</p>
<p>At this point it's unrecoverable.</p>
<p>It looks like adding "ifconfig_ral0="up"" in rc.conf before the other<br />two lines listed below avoids the crash. I have configured other wlan<br />setups in the past and I don't remember having to explicitly make sure<br />the device was up. Maybe it is just the device?</p>
<p>The device from dmesg:<br />ral0: <Ralink Technology RT2561S> mem 0xcfef8000-0xcfefffff irq 10 at<br />device 10.0 on pci1</p>
<p>-ed</p> DragonFlyBSD - Bug #1850 (New): volume-add on hammer root fs panichttps://bugs.dragonflybsd.org/issues/18502010-09-24T03:56:43ZJohannes.Hofmann
<p>Hi,</p>
<p>expanding a hammer root filesystem with hammer volume-add (which is<br />pretty cool btw) leads to a panic on shutdown:</p>
<p>panic: assertion: (bp->b_flags & B_LOCKED) 0 && iou->io.running <br />0 in hammer_io_deallocate</p>
<p>After a reboot everything is ok.<br />The problem can be reproduced in a vkernel.</p>
<pre><code>Johannes</code></pre>
<p>PS: One minor issue: The values df reports seem a bit off after<br /> the volume-add. They also are fine after a reboot.</p>
<p>Program received signal SIGTRAP, Trace/breakpoint trap.<br />Debugger (msg=0x8294114 "panic") at /usr/src/sys/platform/vkernel/i386/db_interface.c:334<br />334 in_Debugger = 0;<br />(gdb) bt<br />#0 Debugger (msg=0x8294114 "panic") at /usr/src/sys/platform/vkernel/i386/db_interface.c:334<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> 0x080e3bfd in panic (fmt=0x827b38c "assertion: %s in %s") at /usr/src/sys/kern/kern_shutdown.c:743<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> 0x08224a05 in hammer_io_deallocate (bp=0x5071f260) at /usr/src/sys/vfs/hammer/hammer_io.c:1093<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> 0x0812b79d in buf_deallocate (bp=0x5071f260) at /usr/src/sys/sys/buf2.h:239<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> brelse (bp=0x5071f260) at /usr/src/sys/kern/vfs_bio.c:1273<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> 0x0813f901 in vinvalbuf_bp (bp=0x5071f260, data=0x544659dc) at /usr/src/sys/kern/vfs_subr.c:424<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> 0x0813c8ae in buf_rb_tree_RB_SCAN (head=0x567de51c, scancmp=0x813c7bc <buf_rb_tree_SCANCMP_ALL>, <br /> callback=0x813f7e9 <vinvalbuf_bp>, data=0x544659dc) at /usr/src/sys/kern/vfs_subr.c:141<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> 0x0813f2b3 in vinvalbuf (vp=0x567de4c8, flags=1, slpflag=0, slptimeo=0) at /usr/src/sys/kern/vfs_subr.c:334<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> 0x0813f434 in vclean_vxlocked (vp=0x567de4c8, flags=8) at /usr/src/sys/kern/vfs_subr.c:1142<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> 0x0813f622 in vgone_vxlocked (vp=0x567de4c8) at /usr/src/sys/kern/vfs_subr.c:1349<br /><a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: make buildworld broken (Closed)" href="https://bugs.dragonflybsd.org/issues/10">#10</a> 0x0814212b in vflush_scan (mp=0x545c3fc0, vp=0x567de4c8, data=0x54465b4c) at /usr/src/sys/kern/vfs_mount.c:1252<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: libstand cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/11">#11</a> 0x081422aa in vmntvnodescan (mp=0x545c3fc0, flags=2, fastfunc=0, slowfunc=0x81420ac <vflush_scan>, data=0x54465b4c)<br /> at /usr/src/sys/kern/vfs_mount.c:1068<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: /sys/net cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/12">#12</a> 0x081424cd in vflush (mp=0x545c3fc0, rootrefs=0, flags=2) at /usr/src/sys/kern/vfs_mount.c:1184<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Buildworld error/panic (Closed)" href="https://bugs.dragonflybsd.org/issues/13">#13</a> 0x08213aa3 in devfs_unmount (mp=0x545c3fc0, mntflags=524288) at /usr/src/sys/vfs/devfs/devfs_vfsops.c:142<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: zombie processes waiting for a lock, smth to worry about? (Closed)" href="https://bugs.dragonflybsd.org/issues/14">#14</a> 0x08150d79 in vfs_unmount (mp=0x545c3fc0, mntflags=524288) at /usr/src/sys/kern/vfs_vfsops.c:123<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: savecore -z patch (Closed)" href="https://bugs.dragonflybsd.org/issues/15">#15</a> 0x08145e40 in dounmount (mp=0x545c3fc0, flags=524288) at /usr/src/sys/kern/vfs_syscalls.c:755<br /><a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: install: net/bridge/*.h: No such file or directory (Closed)" href="https://bugs.dragonflybsd.org/issues/16">#16</a> 0x0813e3ae in vfs_umountall_callback (mp=0x545c3fc0, data=0x0) at /usr/src/sys/kern/vfs_subr.c:1714<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: Minor typos (Closed)" href="https://bugs.dragonflybsd.org/issues/17">#17</a> 0x081427fb in mountlist_scan (callback=0x813e39b <vfs_umountall_callback>, data=0x0, how=<value optimized out>)<br /> at /usr/src/sys/kern/vfs_mount.c:900<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: extern uint64_t tsc_frequency missing (Closed)" href="https://bugs.dragonflybsd.org/issues/18">#18</a> 0x0813d9d3 in vfs_unmountall () at /usr/src/sys/kern/vfs_subr.c:1703<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: usched questions and a patch (Closed)" href="https://bugs.dragonflybsd.org/issues/19">#19</a> 0x080e3503 in boot (howto=8) at /usr/src/sys/kern/kern_shutdown.c:376<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: No detection of 8169S Gb interface (Closed)" href="https://bugs.dragonflybsd.org/issues/20">#20</a> 0x080e3801 in sys_reboot (uap=0x54465c94) at /usr/src/sys/kern/kern_shutdown.c:204<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: /etc/network.subr list_net_interfaces() fix (Closed)" href="https://bugs.dragonflybsd.org/issues/21">#21</a> 0x08271b77 in syscall2 (frame=0x54465d40) at /usr/src/sys/platform/vkernel/i386/trap.c:1221<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: RealTek 8169S/8110S support. (Closed)" href="https://bugs.dragonflybsd.org/issues/22">#22</a> 0x08271f42 in user_trap (frame=0x54465d40) at /usr/src/sys/platform/vkernel/i386/trap.c:410<br />#23 0x0827263e in go_user (frame=0x54465d38) at /usr/src/sys/platform/vkernel/i386/trap.c:1427<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: waitpid() with WUNTRACED flag? (was Re: Hang on ctrl+Z after the MPSAFE tsleep/wakeup commit) (Closed)" href="https://bugs.dragonflybsd.org/issues/24">#24</a> 0x0827290e in pmsg4 () at /usr/src/sys/platform/vkernel/i386/fork_tramp.s:103</p>