DragonFlyBSD bugtracker: Issueshttps://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082020-08-19T03:06:01ZDragonFlyBSD bugtracker
Redmine DragonFlyBSD - Submit #3244 (Resolved): Additional Intel I219-LM and I219-V Ethernet PCI device n...https://bugs.dragonflybsd.org/issues/32442020-08-19T03:06:01Zdavshao
<p>NetBSD current sys/dev/pci/pcidevs.h has additional PCI device numbers for Intel I219-LM and Intel I219-V Ethernet. Simply adding these numbers has been verified to enable em0 on an Asus Prime H470-Plus mATX motherboard for I219-V11 0x0D4D. Also NetBSD current had no problem activating its wm0 Ethernet device for this motherboard.</p>
<p>Note that Phoronix had an article "DragonFlyBSD vs. FreeBSD vs. Ubuntu 20.04 On Intel's Core i9 10900K Comet Lake" that noted on-board Ethernet was not functional on either FreeBSD 12 or DragonFly BSD, and that claimed that even for Linux, 5.6 or later was required. That claim may be incorrect for at least obtaining some minimal functionality on DragonFly for very little effort.</p>
<p>Attached is a patch adding the numbers from NetBSD. The naming of the devices using "CNP", which I believe is an abbreviation for previous generation codename Cannon Point chipsets, is arguably incorrect; however, I was unable to locate any code name at all for current series 400 Intel chipsets. In any case, for at least one device, the Cannon Point handler appears to work unchanged.</p> DragonFlyBSD - Bug #2893 (Closed): Don't clean /usr/obj/usr error: conflicting types for 'unctrl'https://bugs.dragonflybsd.org/issues/28932016-03-13T00:58:20Zdavshao
<p>Update through (I have been using full buildworlds after latest updates including cleaning /usr/obj/usr):</p>
<p>commit b34d3b9b8fa26892a7eb1f0fbf9a053d72798cd8<br />Date: Thu Mar 10 10:43:31 2016 +0200</p>
<pre><code>nrelease: Allow to build snapshots on tmpfs.</code></pre>
<p>After installation,</p>
<p>cd /usr/obj<br />mv usr usr.prev</p>
<p>because it appears one needs a functioning /usr/obj/usr to build anymore.</p>
<p>Now update through:</p>
<p>commit 3eec877432eb8056a5450dd96fad6f6abad016b9<br />Date: Fri Mar 11 20:11:40 2016 +0100</p>
<pre><code>ncurses: Upgrade version 5.9 (20110402) => 6.0 (20160305)</code></pre>
<p>cd /usr/src<br />make buildworld</p>
<p>Not long into the build, reproduced on 2 separate machines so far:</p>
<p>echo tic: /usr/obj/usr/src/btools_x86_64/usr/lib/libc.a /usr/obj/usr/src/btools_x86_64/usr/lib/priv/libprivate_ncurses.a >> .depend<br />cc -O -pipe -g -D_XOPEN_SOURCE_EXTENDED -DENABLE_WIDEC -DSET_NCURSES_CH_T=cchar_t -DSET_NEED_WCHAR_H=1 -I/usr/src/usr.bin/tic/../../contrib/ncurses/progs -I. -I/usr/src/usr.bin/tic/../../contrib/ncurses/include -I/usr/src/usr.bin/tic/../../lib/libncurses/include -I/usr/src/usr.bin/tic -I/usr/obj/usr/src/btools_x86_64/usr/src/usr.bin/tic -std=gnu99 -Wmissing-include-dirs -Wsystem-headers -Wall -Wformat-security -Winit-self -Wno-pointer-sign -Wextra -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wold-style-definition -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c /usr/src/usr.bin/tic/../../contrib/ncurses/progs/tic.c -o tic.o<br />In file included from /usr/src/usr.bin/tic/../../contrib/ncurses/progs/progs.priv.h:121:0,<br /> from /usr/src/usr.bin/tic/../../contrib/ncurses/progs/tic.c:42:<br />/usr/src/usr.bin/tic/../../lib/libncurses/include/unctrl.h:60:38: error: conflicting types for 'unctrl'<br /> NCURSES_EXPORT(NCURSES_CONST char <strong>) NCURSES_SP_NAME(unctrl) (SCREEN</strong>, chtype);<br /> ^<br />In file included from /usr/include/curses.h:1971:0,<br /> from /usr/src/usr.bin/tic/../../contrib/ncurses/progs/progs.priv.h:121,<br /> from /usr/src/usr.bin/tic/../../contrib/ncurses/progs/tic.c:42:<br />/usr/src/usr.bin/tic/../../lib/libncurses/include/unctrl.h:57:38: note: previous declaration of 'unctrl' was here<br /> NCURSES_EXPORT(NCURSES_CONST char *) unctrl (chtype);</p>
<ul>
<li>Error code 1</li>
</ul>
Stop.<br />make<sup><a href="#fn3">3</a></sup>: stopped in /usr/src/usr.bin/tic<br />sh /usr/src/tools/install.sh -o root -g wheel -m 555 tic /usr/obj/usr/src/btools_x86_64/usr/bin<br />install: tic: No such file or directory
<ul>
<li>Error code 71</li>
</ul>
<p>The /etc/make.conf used is:</p>
<p>CFLAGS+=-g<br />STRIP=</p>
<p>WITH_PKGNG=yes<br />DISABLE_VULNERABILITIES=yes</p>
<p>WITH_VIM_OPTIONS=yes</p>
<p>On one machine, moving back /usr/obj/usr allows<br />make quickworld<br />to complete successfully. However I have not attempted to install this world yet.</p> DragonFlyBSD - Bug #2835 (New): /usr/include/c++/5.0/bits/c++locale.h likes _POSIX_C_SOURCE>=200809https://bugs.dragonflybsd.org/issues/28352015-08-04T15:05:55Zdavshao
<p>Using current master DragonFly, trying to build dports devel/ncurses or pkgsrc devel/ncurses fails with:</p>
<p>c++ -DHAVE_CONFIG_H -I. -I../../c++ -I../include -I../../c++/../include -D_BSD_TYPES -D__BSD_VISIBLE -D_POSIX_C_SOURCE=200112L -D_XOPEN_SOURCE=600 -DNDEBUG -pipe -g -O2 -fno-strict-aliasing -fPIC -DPIC -c ../../c++/cursesmain.cc -o ../obj_s/cursesmain.o<br />In file included from /usr/include/c++/5.0/bits/localefwd.h:40:0,<br /> from /usr/include/c++/5.0/ios:41,<br /> from /usr/include/c++/5.0/ostream:38,<br /> from /usr/include/c++/5.0/iostream:39,<br /> from ../../c++/cursesmain.cc:39:<br />/usr/include/c++/5.0/bits/c++locale.h: In function 'int std::__convert_from_v(int* const&, char*, int, const char*, ...)':<br />/usr/include/c++/5.0/bits/c++locale.h:61:47: error: 'locale_t' was not declared in this scope<br /> _<em>c_locale __old = (</em>_c_locale)uselocale((locale_t)__cloc);<br /> ^<br />/usr/include/c++/5.0/bits/c++locale.h:61:62: error: 'uselocale' was not declared in this scope<br /> _<em>c_locale __old = (</em>_c_locale)uselocale((locale_t)__cloc);</p>
<p>I suspect the responsible change may be:</p>
<p>commit d1732c039257d5ff06e218b885a2d1ee92daa355<br />Date: Thu Jul 30 22:22:02 2015 +0200</p>
<pre><code>gcc50: Remove generic versions of added files</code></pre>
<p>where in particular<br />.../libstdc++-v3/config/locale/generic/c_locale.h <br />was removed.</p>
<p>c++/5.0/bits/c++locale.h contains<br />#include <clocale></p>
<p>/usr/include/c++/5.0/clocale contains<br />#include <locale.h></p>
<p>/usr/include/locale.h contains</p>
<p>#if __POSIX_VISIBLE >= 200809<br />#include <xlocale/_locale.h><br />#endif</p>
<p>locale_t appears to be defined in /usr/include/xlocale/_locale.h</p>
<p>And I believe __POSIX_VISIBLE is defined in cdefs.h where it is set depending on the value of _POSIX_C_SOURCE.</p>
<p>At least on pkgsrc devel/ncurses, the build was able to be completed when its configure was hacked similar to the following:</p>
<p>cf_POSIX_C_SOURCE=200809L<br />cf_XOPEN_SOURCE=700</p>
<p>Now the obvious workaround is simply to use the built-in ncurses. However I am wondering if in general the new recommendation for userland software is to edit their aclocal.m4's or whatever else they use defining</p>
<p>_POSIX_C_SOURCE=200809<br />_XOPEN_SOURCE=700</p>
<p>for DragonFly. And do they need to test the version of DragonFly?</p>
<p>Or would it be possible to put the deleted generic files back?</p> DragonFlyBSD - Bug #2823 (Closed): Intel Q9400 PC fails to boot waiting for the following device ...https://bugs.dragonflybsd.org/issues/28232015-06-07T15:37:49Zdavshao
<p>For one Intel Core 2 Q9400 machine, booting fails with console output listed below. The same problem has not been observed on a couple of newer generation Intel-based PCs. Bisection seems to indicate the problem began between, inclusive, master commit</p>
<p>commit 6f1a15dc79a822710cc37e99f6a8bd9910e5e3f1<br />Date: Sat Jun 6 16:17:41 2015 -0700</p>
<pre><code>sysctl - SMP performance work</code></pre>
<p>and</p>
<p>commit bb06d795144b04574aa0b5fdb94e95ab77360a1a<br />Date: Sun Jun 7 04:16:12 2015 +0200</p>
<pre><code>&lt;sys/sysctl.h&gt;: Include &lt;sys/lock.h&gt; only for the kernel (unbreaks world).</code></pre>
<p>Attached is a full verbose dmesg from a successful boot with a previous kernel.</p>
<p>Console output for unsuccessful boot:</p>
<p>CAM: finished configuring all busses<br /><b>WARNING</b> waiting for the following device to finish configuring:<br /> xpt: func=0xffffffff8029ea32 arg=0<br /><b>WARNING</b> waiting for the following device to finish configuring:<br /> xpt: func=0xffffffff8029ea32 arg=0<br /><b>WARNING</b> waiting for the following device to finish configuring:<br /> xpt: func=0xffffffff8029ea32 arg=0<br /><b>WARNING</b> waiting for the following device to finish configuring:<br /> xpt: func=0xffffffff8029ea32 arg=0<br /><b>WARNING</b> waiting for the following device to finish configuring:<br /> xpt: func=0xffffffff8029ea32 arg=0<br />Giving up, interrupt routing is probably hosed<br />no B_DEVMAGIC (bootdev=0)<br />ATA PseudoRAID loaded<br />Mounting root from hammer:serno/WD-WMATV8216330.s1d<br />no disk named 'serno/WD-WMATV8216330.s1d'<br />hammer_mountroot: can't find devvp<br />kthread 0xffffffe056318c80 syncer3 has exited<br />Root mount failed:6</p>
<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></p>
<p>Dmesg output for earlier kernel, successful boot:</p>
<p>sl0: bpf attached<br />hpt27xx: no controller detected.<br />hptrr: no controller detected.<br />CAM: Configuring bus: ahci0<br />CAM: Configuring bus: ahci0<br />CAM: Configuring bus: ahci0<br />CAM: Configuring bus: ahci0<br />CAM: Configuring bus: ahci0<br />CAM: Configuring bus: ahci0<br />CAM: Configuring 6 busses<br />CAM: Finished configuring bus: ahci0<br />CAM: Finished configuring bus: ahci0<br />CAM: Finished configuring bus: ahci0<br />CAM: Finished configuring bus: ahci0<br />CAM: Finished configuring bus: ahci0<br />CAM: Finished configuring bus: ahci0<br />CAM: finished configuring all busses<br />pass0 at ahci0 bus 1 target 0 lun 0<br />pass0: <SATA WDC WD1002FBYS-0 03.0> Fixed Direct Access SCSI-4 device <br />pass0: Serial Number WD-WMATV5981256<br />pass0: 300.000MB/s transfers<br />pass1 at ahci0 bus 2 target 0 lun 0<br />pass1: <SATA WDC WD1002FBYS-0 03.0> Fixed Direct Access SCSI-4 device <br />pass1: Serial Number WD-WMATV8216330<br />pass1: 300.000MB/s transfers</p> DragonFlyBSD - Bug #2794 (Closed): /usr/share/mk/sys.mk" line 66: Malformed conditionalhttps://bugs.dragonflybsd.org/issues/27942015-02-25T19:16:00Zdavshao
<p>After using a full buildworld, buildkernel, installkernel, installworld for current master, use of make fails with:</p>
<p>make: "/usr/share/mk/sys.mk" line 66: Malformed conditional ((${CCVER:Mgcc4<sup><a href="#fn89">89</a></sup>} || ${CCVER:Mgcc5*}))</p>
<p>This may be related to:</p>
<p>commit 7431acdac28b044e8c36042bc91009824a095ce8<br />Date: Wed Feb 25 04:55:09 2015 +0100</p>
<pre><code>gcc50: Exclude -Wunused-local-typedefs from C++ flags for now.</code></pre>
<p>Since /usr/share/mk/sys.mk appears to be affected, can full instructions be given for the fix that has to apparently be manually applied to each system.</p> DragonFlyBSD - Bug #2762 (Closed): 8461f85162cfc9... <sys/signal.h>: Use __POSIX_VISIBLE stack_t ...https://bugs.dragonflybsd.org/issues/27622015-01-07T19:51:02Zdavshao
<p>commit 8461f85162cfc9b0f8f8fff2dbf5d7278f441765<br />Date: Wed Jan 7 03:34:37 2015 +0100</p>
<pre><code>&lt;sys/signal.h&gt;: Use __POSIX_VISIBLE, __XSI_VISIBLE and __BSD_VISIBLE.</code></pre>
<p>puts the definition of stack_t inside an #if ... #endif and then unconditionally includes sys/ucontext.h. But ucontext.h defines a struct that uses stack_t.</p>
<p>This can be observed building either dports or pkgsrc png.</p> DragonFlyBSD - Bug #2688 (New): 67613368bdda7 Fix wrong checks for U4B presence Asrock Z77M diffi...https://bugs.dragonflybsd.org/issues/26882014-06-29T02:06:55Zdavshao
<p>For an Asrock Z77M motherboard, Intel Core i3-3225 CPU PC, detection of a USB keyboard was already somewhat erratic, but following 67613368bdda7 Fix wrong checks for U4B presence it has become almost impossible. The motherboard is UEFI, but I am using legacy support modes for hard drives and USB to emulate older booting using BIOS. The following summarizes the differences I can see between two verbose dmesg's, one asrock_z77m_verbose_good.txt with 67613368bdda7 reverted, the other asrock_z77m_verbose_bad.txt with current master. The USB keyboard and USB mouse are attached using a USB hub but similar behavior has been observed not using a hub. Nothing similar has been noticed with the same system using other OSes such as FreeBSD i386 current, FreeBSD 10 stable, FreeBSD 10 releng, NetBSD 6.99.x, OpenBSD 5.5-current, etc.</p>
<p>Both have</p>
<p>kbd: new array size 4<br />kbd1 at kbdmux0</p>
<p>Both have</p>
<p>pci0: <serial bus, USB> (vendor 0x8086, dev 0x1e31) at device 20.0 irq 16<br />pci0: <simple comms> (vendor 0x8086, dev 0x1e3a) at device 22.0 irq 16<br />ehci0.pci0.pcib0.acpi0.nexus0.root0<br />ehci0: <Intel Panther Point USB 2.0 controller> [tentative] mem 0xf7f18000-0xf7f183ff irq 16 at device 26.0 on pci0</p>
<p>Only the reverted good boot has:</p>
<p>ehci0: <Intel Panther Point USB 2.0 controller> [tentative] mem 0xf7f18000-0xf7f183ff irq 16 at device 26.0 on pci0<br />ehci0: Reserved 0x400 bytes for rid 0x10 type 3 at 0xf7f18000<br />usbus0: waiting for BIOS to give up control</p>
<p>Then both have:</p>
<p>usbus0: EHCI version 1.0<br />usbus0.ehci0.pci0.pcib0.acpi0.nexus0.root0<br />usbus0: <Intel Panther Point USB 2.0 controller> [tentative] on ehci0<br />usbus0: <Intel Panther Point USB 2.0 controller> [attached!] on ehci0<br />ehci0: <Intel Panther Point USB 2.0 controller> [attached!] mem 0xf7f18000-0xf7f183ff irq 16 at device 26.0 on pci0</p>
<p>Later both dmesgs have:</p>
<p>ehci1.pci0.pcib0.acpi0.nexus0.root0<br />ehci1: <Intel Panther Point USB 2.0 controller> [tentative] mem 0xf7f17000-0xf7f173ff irq 23 at device 29.0 on pci0</p>
<p>Only the reverted good dmesg has:</p>
<p>ehci1: Reserved 0x400 bytes for rid 0x10 type 3 at 0xf7f17000</p>
<p>Both have:</p>
<p>ugen0.1: <Intel> at usbus0<br />uhub0: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus</p>
<p>Only the reverted good dmesg has:</p>
<p>usbus1: waiting for BIOS to give up control</p>
<p>Then both have:</p>
<p>usbus1: EHCI version 1.0<br />usbus1.ehci1.pci0.pcib0.acpi0.nexus0.root0<br />usbus1: <Intel Panther Point USB 2.0 controller> [tentative] on ehci1<br />usbus1: <Intel Panther Point USB 2.0 controller> [attached!] on ehci1<br />ehci1: <Intel Panther Point USB 2.0 controller> [attached!] mem 0xf7f17000-0xf7f173ff irq 23 at device 29.0 on pci0</p>
<p>Later both have:</p>
<p>usbus1: 480Mbps High Speed USB v2.0<br />ugen1.1: <Intel> at usbus1<br />uhub1: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1<br />uhub0: 2 ports with 2 removable, self powered<br />uhub1: 2 ports with 2 removable, self powered<br />ugen0.2: <vendor 0x8087> at usbus0<br />uhub2: <vendor 0x8087 product 0x0024, class 9/0, rev 2.00/0.00, addr 2> on usbus0<br />...<br />ugen1.2: <vendor 0x8087> at usbus1<br />uhub3: <vendor 0x8087 product 0x0024, class 9/0, rev 2.00/0.00, addr 2> on usbus1<br />uhub2: 6 ports with 6 removable, self powered</p>
<p>But then only the reverted good dmesg has:</p>
<p>uhub3: 8 ports with 8 removable, self powered<br />ugen1.3: <vendor 0x1a40> at usbus1<br />uhub4: <vendor 0x1a40 USB 2.0 Hub MTT, class 9/0, rev 2.00/1.00, addr 3> on usbus1<br />uhub4: MTT enabled<br />uhub4: 7 ports with 7 removable, self powered<br />...<br />ugen1.4: <vendor 0x04d9> at usbus1<br />ukbd0: <vendor 0x04d9 USB Keyboard, class 0/0, rev 1.10/1.01, addr 4> on usbus1<br />kbd2 at ukbd0<br />kbd2: ukbd0, generic (0), config:0x0, flags:0x3d0000<br />uhid0: <vendor 0x04d9 USB Keyboard, class 0/0, rev 1.10/1.01, addr 4> on usbus1<br />...<br />ugen1.5: <Logitech> at usbus1<br />...<br />ums0: <Logitech USB Laser Mouse, class 0/0, rev 2.00/31.00, addr 5> on usbus1<br />ums0: 8 buttons and [XYZT] coordinates ID=0</p> DragonFlyBSD - Bug #2672 (Closed): Continuous console [ACPI Debug] on Lenovo S10 Intel Atom n270https://bugs.dragonflybsd.org/issues/26722014-05-12T02:59:25Zdavshao
<p>For current master through</p>
<p>commit c9ed7d9ef60d6ffb82c02ec4822a68a29703a389<br />Date: Sun May 11 21:16:54 2014 +0200</p>
<pre><code>kernel/acpi: Improve the disabling of Debug object dumping.</code></pre>
<p>on a Lenovo S10 Intel Atom n270, i386, there is continuous output to console</p>
<p>[ACPI Debug] String [0x11] "Current temp is: " <br />[ACPI Debug] Integer 0x00000036</p> DragonFlyBSD - Bug #2652 (New): 189a0ff3761b47 ... ix: Implement MSI-X support locks up Lenovo S1...https://bugs.dragonflybsd.org/issues/26522014-03-03T21:20:17Zdavshao
<p>For a i386 Lenovo S10 Intel Atom n270 netbook, bisection indicates using<br />189a0ff3761b47 ... ix: Implement MSI-X support and enable multiple TX rings<br />locks up the machine on booting at the point:</p>
<p>...<br />md0: invalid primary partition table: no magic<br />Math emulator present<br />hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2<br />hpt27xx: RocketRAID 27xx controller driver v1.0 (Feb 28 2014 21:38:19)</p>
<p>Attached is a full verbose dmesg from the same machine running with master<br />previous to the above commit. The machine only fully boots with<br />acpi disabled using hint.acpi.0.disabled=1, but even with acpi enabled the<br />lockup with the problematic commit occurs sooner than the normal lockup<br />with acpi enabled. "Normally" on this machine booting with acpi halts at</p>
<p>acpi0.nexus0.root0<br />acpi0: <LENOVO CB-01> [tentative] on motherboard<br />ACPI: All ACPI Tables successfully acquired<br />ACPI FADT: SCI testing interrupt mode ...<br />ACPI FADT: SCI testing level/high<br />IOAPIC: irq 9, gsi 9 edge/high -> level/high</p> DragonFlyBSD - Bug #2511 (Closed): /usr/libexec/binutils222/elf/ld.bfd: error in /usr/lib/crt1.o(...https://bugs.dragonflybsd.org/issues/25112013-02-08T17:14:02Zdavshao
<p>Using current master src through:</p>
<p>commit e1dad499f942b88618bab2f62bdd2f7ae9f58209<br />Date: Thu Feb 7 20:05:52 2013 +0100</p>
<pre><code>games/atc: Fix a logic bug.</code></pre>
<ol>
<li>make buildworld && make CCVER=gcc44 buildkernel</li>
</ol>
<p>and using current pkgsrc, updating graphics/cairo on i386 has in config.log messages such as:</p>
<p>configure:32959: checking for cairo's pthread feature<br />configure:33070: cc -o conftest -O2 -g -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -pthread -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -L/usr/pkg/lib -Wl,-R/usr/pkg/lib -L/usr/lib -Wl,-R/usr/lib conftest.c -lrt -lm -lpthread -lrt >&5<br />/usr/libexec/binutils222/elf/ld.bfd: error in /usr/lib/crt1.o(.eh_frame); no .eh_frame_hdr table will be created.<br />configure:33070: $? = 0<br />configure:33189: cc -o conftest -O2 -g -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -pthread -I/usr/pkg/include -I/usr/include -I/usr/pkg/include/freetype2 -L/usr/pkg/lib -Wl,-R/usr/pkg/lib -L/usr/lib -Wl,-R/usr/lib conftest.c -lrt -lm >&5<br />/usr/libexec/binutils222/elf/ld.bfd: error in /usr/lib/crt1.o(.eh_frame); no .eh_frame_hdr table will be created.<br />configure:33189: $? = 0</p>
<p>cairo build on i386 seems to not detect pthread and to build one has to set -DCAIRO_NO_MUTEX=1 in CFLAGS.</p>
<p>Attached is the full config.log</p>
<p>Perhaps related, pkgsrc x.org does not appear to function on x86_64 or i386 even using a simple window manager such as openbox, but I have not had time to complete a full rebuild due to massive changes in pkgsrc versions the past week.</p> DragonFlyBSD - Bug #2467 (Resolved): Intel 945GME agp Fatal trap 12 with ACPI disabledhttps://bugs.dragonflybsd.org/issues/24672012-12-04T17:40:50Zdavshao
<p>ACPI disabled on a Lenovo Ideapad netbook:</p>
<p>MPTABLE: 0:31 INTB routed to irq 19<br />vgapci0.pci0.pcib0.legacy0.nexus0.root0<br />vgapci0: <VGA-compatible display> [tentative] port 0x1800-0x1807 mem 0xf0600000-0xf063ffff,0xd0000000-0xdfffffff,0xf0500000-0xf057ffff irq 16 at device 2.0 on pci0<br />agp0.vgapci0.pci0.pcib0.legacy0.nexus0.root0<br />agp0: <Intel 945GME SVGA controller> [tentative] on vgapci0<br />vgapci0: Reserved 0x10000000 bytes for rid 0x18 type 3 at 0xd0000000</p>
<p>Fatal trap 12: page fault while in kernel mode<br />cpuid = 0; lapic.id = 00000000<br />fault virtual address = 0x78<br />fault code = supervisor write, page not present<br />instruction pointer = 0x8:0xc052b97e<br />stack pointer = 0x10:0xc0ef5984<br />frame pointer = 0x10:0xc0ef59a8<br />code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1<br />processor eflags = interrupt enabled, resume, IOPL = 0<br />current process = 0 (swapper)<br />current thread = pri 12<br /> <- SMP: XXX<br />kernel: type 12 trap, code=2</p>
<p>CPU0 stopping CPUs: 0x00000002<br /> stopped<br />Stopped at agp_generic_attach+0x13f: movl %esi,0x78(%eax)</p> DragonFlyBSD - Bug #2461 (Closed): INT64_MAX,INT64_MIN long long definition conflicts on x86_64 w...https://bugs.dragonflybsd.org/issues/24612012-11-24T21:46:24Zdavshao
<p>On current pkgsrc master, 3.3-DEVELOPMENT x86_64, building devel/xulrunner, associated with firefox 17.0esr, fails processing a C++ header file with an error message:</p>
<p>In file included from ../../dist/include/mozilla/FunctionTimer.h:11,<br /> from /usr/pkgsrc/devel/xulrunner/work/mozilla-esr17/xpcom/glue/FileUtils.cpp:20:<br />../../dist/include/mozilla/TimeStamp.h: In static member function 'static mozilla::TimeDuration mozilla::TimeDuration::FromTicks(double)':<br />../../dist/include/mozilla/TimeStamp.h:137: error: call of overloaded 'FromTicks(long long int)' is ambiguous<br />../../dist/include/mozilla/TimeStamp.h:123: note: candidates are: static mozilla::TimeDuration mozilla::TimeDuration::FromTicks(int64_t)<br />../../dist/include/mozilla/TimeStamp.h:129: note: static mozilla::TimeDuration mozilla::TimeDuration::FromTicks(double)<br />gmake<sup><a href="#fn4">4</a></sup>: *** [FileUtils.o] Error 1</p>
<p>The relevant lines from the original TimeStamp.h located under devel/xulrunner/work/mozilla-esr17/xpcom/ds appear to be:</p>
<pre><code>static TimeDuration FromTicks(int64_t aTicks) {<br /> TimeDuration t;<br /> t.mValue = aTicks;<br /> return t;<br /> }</code></pre>
<pre><code>static TimeDuration FromTicks(double aTicks) {<br /> // NOTE: this MUST be a >= test, because int64_t(double(INT64_MAX))<br /> // overflows and gives LL_MININT.<br /> if (aTicks >= double(INT64_MAX))<br /> return TimeDuration::FromTicks(INT64_MAX);</code></pre>
<pre><code>// This MUST be a <= test.<br /> if (aTicks <= double(INT64_MIN))<br /> return TimeDuration::FromTicks(INT64_MIN);</code></pre>
<pre><code>return TimeDuration::FromTicks(int64_t(aTicks));<br /> }</code></pre>
<pre><code>// Duration in PRIntervalTime units<br /> int64_t mValue;</code></pre>
<p>A patch explictly casting in the above header file TimeStamp.h both INT64_MAX and INT64_MIN to int64_t allows building to at least proceed past the previous error.</p>
<p>Grepping for INT64_MAX and INT64_MIN under /usr/include reveals definitions:<br />#define INT64_MAX 0x7fffffffffffffffLL<br />#define INT64_MIN (-0x7fffffffffffffffLL-1)</p>
<p>The compiler being used is:<br />$ cc --version<br />cc (DragonFly) 4.4.7 2012.03.13</p> DragonFlyBSD - Bug #2409 (Closed): assertion "cpuid < ncpus" failed in ioapic_abi_legacy_intr_co...https://bugs.dragonflybsd.org/issues/24092012-08-24T17:28:00Zdavshao
<p>Using i386 through dcece5c7521207769edc2756956f76ef8b485ce1 mutex.9: Misc updates and minor improvements,<br />problem has existed a while on Pentium 4, Asus P4B266 motherboard, since lapic overhaul,<br />required to<br />set hw.apic_io_enable=0<br />for without have kernel panic, partial trace:</p>
<pre><code>powerspec 2 supports D0 D1 D2 D3 current D0<br /> map[10]: type Memory, range 32, base 0xdd800000, size 12, enabled<br />pcib2: requested memory range 0xdd800000-0xdd800fff: good<br />pcib2: matched entry for 2.4.INTB<br />pcib2: slot 4 INTB hardwired to IRQ 22<br />panic: assertion "cpuid < ncpus" failed in ioapic_abi_legacy_intr_config at<br /> /usr/src/platform/pc32/apic/ioapic_abi.c:921<br />cpuid = 0<br />Trace beginning at frame 0xc0f485a4<br />panic(ffffffff,0,c07a6724,c0f485d8,c0939900) at panic+0x1a8 0xc03d32b0<br />panic(c07a6724,c07dcbc1,c0869f0f,c0869730,399,0,0,0,1d,16,1,c0f4863d,a) at panic+0x1a8 0xc03d32b0<br />ioapic_abi_legacy_intr_config(16,2,2,c0f48648,c03f1d8e) at ioapic_abi_legacy_intr_config+0x23a 0xc0769fca<br />nexus_config_intr<br />bus_generic_config_intr<br />bus_generic_config_intr<br />bus_generic_config_intr<br />bus_generic_config_intr<br />bus_generic_config_intr<br />acpi_pcib_route_interrupt<br />acpi_pcib_pci_route_interrupt<br />pci_assign_interrupt_method<br />pci_assign_interrupt<br />pci_add_resources<br />pci_add_child<br />pci_add_children<br />acpi_pci_attach<br />device_doattach<br />device_probe_and_attach<br />bus_generic_attach<br />acpi_pcib_attach<br />acpi_pcib_pci_attach<br />device_doattach<br />device_probe_and_attach<br />bus_generic_attach<br />acpi_pci_attach<br />device_doattach<br />device_probe_and_attach<br />bus_generic_attach<br />acpi_pcib_attach<br />acpi_pcib_acpi_attach<br />device_doattach<br />device_probe_and_attach<br />bus_generic_attach<br />acpi_attach<br />device_doattach<br />device_probe_and_attach<br />bus_generic_attach<br />nexus_attach<br />device_doattach<br />device_probe_and_attach<br />root_bus_configure<br />configure(0,f44c00,f44c00,f5500,f55000) at configure+0xb 0xc074ecd0<br />mi_startup(f44000,0,0,0,0) at mi_startup+0x89 0xc03a9930<br />begin() at begin+0x42 0xc016a68b<br />Debugger("panic")</code></pre>
<p>CPU0 stopping CPUs: 0x00000000<br /> stopped<br />Stopped at Debugger+0x3f: movb $0,in_Debugger.4994</p> DragonFlyBSD - Bug #2408 (Closed): Fatal trap 12: page fault Stopped at bsd4_setrunqueue on Penti...https://bugs.dragonflybsd.org/issues/24082012-08-24T03:06:45Zdavshao
<p>On a Pentium 4 Asus P4B266 motherboard using<br />set hw.apic_io_enable=0<br />some commit between<br />26dd35c9bbbbeffac40d091e7df63b02e7e2f078 rtld: Perform reloc before filtree dependency object init<br />and<br />b148267406ef2d0543d5d87d15c283b2d314516f kernel - Attempt to fix i386 wire_count panic (98)<br />produces a panic on boot:</p>
<p>Mounting root from ufs:/dev/serno/WD-WCAL75015619.s1a<br />DMA space used: 232k, remaining available: 16384k</p>
<p>Fatal trap 12: page fault while in kernel mode<br />cpuid = 0; lapic.id = 00000000<br />fault virtual address = 0xc<br />fault code = supervisor read, page not present<br />instruction pointer = 0x8 :0xc03dacaf<br />stack pointer = 0x10:0xc0f4cd08<br />frame pointer = 0x10:0xc0f4cd44<br />code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1<br />processor eflags = interrupt enabled, resume, IOPL = 0<br />current process = 0 (swapper)<br />current thread = pri 12 (CRIT)<br /> <- SMP: XXX<br />kernel: type 12 trap, code = 0</p>
<p>CPU0 stopping CPUs: 0x00000000<br /> stopped<br />Stopped at bsd4_setrunqueue+0x1df: andl 0xc(%eax),%ecx</p>
<p>db> trace<br />bsd4_setrunqueue(c308b1d8,c05ed5d,c04a24c,e8,0) at bsd4_setrunqueue+0x1df 0xc03dacaf<br />start_forked_proc(c093bae0,cd6da460,c0f4cd98,c03a9a10,0) at start_forked_proc+0x90 0xc03c0e7b<br />kick_init(0,f48c00,f48c00,f59000,f59000) at kick_init+0x1b 0xc03a9915<br />mi_startup(f48000,0,0,0,0) at mi_startup+0x89 0xc03a9a10<br />begin() at begin+0x42 0xc016a7db</p> DragonFlyBSD - Bug #2393 (Closed): ETIME not defined in /usr/include/errno.h, current pkgsrc libd...https://bugs.dragonflybsd.org/issues/23932012-07-02T15:48:30Zdavshao
<p>/usr/include/errno.h from latest DEVEL-3.1 does not appear to define ETIME. ETIME appears to be associated with STREAMS as an option in the POSIX standard; therefore, if STREAMS is not implemented, there may be good reason for it to not be defined.</p>
<p>Even if ETIME is to be deliberately not defined, there needs to be some recommendation on what its value should be for porting applications such as libdrm 2.4.37.</p>